[TESTING] Updated 5/14/11 New Kernel - Temp Test - SOD Fix!

[ndno]

Originally Posted by fishingmedic

Alright, just tried this again, put a brand new clean FRX04 build w/ the latest rootfs that was just released last night and this kernel, let it boot, and just sit for a few, at which time, without me touching it, it booted back to winmo. Before I do anything further (like run the freaking phone over with my truck...) do you want me to attempt to get a log on it or will one have not even been created as I'm not sure exactly how far the process went?

Edit: I changed a couple of things in the startup.txt and played around with it a bit and giving it another shot. Maybe I should try with the actual package first, then after it boots, go back to winmo, swap in the new rootfs and test kernel?

Edit part 2: Still reboots back to winmo and reboots back before I can get a log or anything. forget it, I just threw it at my neighbor, I'm going back to a freaking flip phone... lol. I'm gonna try booting just FRX04 out of the box and then make changes with rootfs and kernel.

So far so good with clean FRX04...

Fish, seems like you have been getting a lot of resets to WinMo issue lately, with Tiad8's build and FRX04. Hmmm... I had that issue the first time I tried FRX04 with 1253 OC'ed on first boot but it works fine after the first boot. I'm currently using FRX04, with 2/9 rootfs, and this kernel OCed at 614Mhz and it's pretty solid. Got the panel 14 type in my dmesg. When my phone goes to sleep, I still have to press the button several times to really wake it up. I'm using an app called nolock because I can't stand the slider to unlock screen that occurs everytime my phone wakes up; saves me a couple precious seconds so I can use my phone right away .

arrrghhh, besides ADB, DroidExplorer or the other debugging methods you guys are using, is there a way we can set up a telnetd or sshd daemon with which we log into? The builtin terminal is good but the lack of some keys (>, |, tab, etc) makes it hard to play with (I guess I can use manekineko's rootfs with the added key functions).

[rpierce99]

Originally Posted by ndno

Fish, seems like you have been getting a lot of resets to WinMo issue lately, with Tiad8's build and FRX04. Hmmm... I had that issue the first time I tried FRX04 with 1253 OC'ed on first boot but it works fine after the first boot. I'm currently using FRX04, with 2/9 rootfs, and this kernel OCed at 614Mhz and it's pretty solid. Got the panel 14 type in my dmesg. When my phone goes to sleep, I still have to press the button several times to really wake it up. I'm using an app called nolock because I can't stand the slider to unlock screen that occurs everytime my phone wakes up; saves me a couple precious seconds so I can use my phone right away .

arrrghhh, besides ADB, DroidExplorer or the other debugging methods you guys are using, is there a way we can set up a telnetd or sshd daemon with which we log into? The builtin terminal is good but the lack of some keys (>, |, tab, etc) makes it hard to play with (I guess I can use manekineko's rootfs with the added key functions).

The most effective way to guarantee a good wake is to touch the screen after you've hit the power button and waiting about a second.

If you prefer the END=HOME button layout check out F22's ROOTFS over on XDA, it also adds in the missing keys for effectively running shell commands.

[ndno]

Originally Posted by rpierce99

The most effective way to guarantee a good wake is to touch the screen after you've hit the power button and waiting about a second.

If you prefer the END=HOME button layout check out F22's ROOTFS over on XDA, it also adds in the missing keys for effectively running shell commands.

Thanks, I'll keep that in mind. Does F22's rootfs have the system_server bug fix in it?

[arrrghhh]

Originally Posted by ndno

Thanks, I'll keep that in mind. Does F22's rootfs have the system_server bug fix in it?

Indeed it does, he just updated it last night.

There is ssh into the phone, search for 'dropbear'.

Plus, you can get a full-featured shell using adb... just need to enable it.

/bin/sh

should do it.

[tacotoy]

Originally Posted by arrrghhh

I guess I'm missing something here.

So when the phone is sleeping... it wakes on a phone call.

When the phone isn't sleeping, it doesn't wake for the phone call? I haven't really had any failed wakes on incoming calls, unless the processor was being slaughtered by some other process (not only system_server can cause issues, just that system_server issues would run without stopping).

We have the same phone, what build are you running? Overclocking? Need... more... info...

Originally Posted by rpierce99

It sounds like tacotoy is saying the phone rings, but the screen never comes on with the slide to answer, so he can't answer the call.

The only time I've experienced that is when system_server was running rampant. If you haven't already I'd try dropping the newly fixed rootfs on the system and seeing if you get any better results.

you got it right, when the phone is sleeping it will ring, the screen will never come up but it will vibrate and ring. if i get a call while i am using the phone ( i e screen is on) then i can answer it just fine.

running the latest panel reint, and mannieko's modded rootfs with FRX04. i oc, but i have been oc'ing since it was available. this issue started once i loaded the most recent panel reint kernel. ill boot back to winmo and see if that makes a difference


edit: after booting back and then rebooting with no oc it works fine for a bit, but if i get a bunch of programs running, close them down ( ie eat up available memory) then it doesn't work, so seems like there is a memory leak. so over time as programs autoload then it prevents the phone from waking to answer the phone. oc'ing just seems to exacerbate the issue

[highlandsun]

Originally Posted by ndno

arrrghhh, besides ADB, DroidExplorer or the other debugging methods you guys are using, is there a way we can set up a telnetd or sshd daemon with which we log into? The builtin terminal is good but the lack of some keys (>, |, tab, etc) makes it hard to play with (I guess I can use manekineko's rootfs with the added key functions).

Do a "ps" sometime, you'll see there's already a telnetd running, listening on your usb0 interface. It's built in to busybox and always started by the init script so it's always there.

Sent from my MSM using Tapatalk

[arrrghhh]

Originally Posted by tacotoy

edit: after booting back and then rebooting with no oc it works fine for a bit, but if i get a bunch of programs running, close them down ( ie eat up available memory) then it doesn't work, so seems like there is a memory leak. so over time as programs autoload then it prevents the phone from waking to answer the phone. oc'ing just seems to exacerbate the issue

Well if the phone is working hard, waking the panel isn't so easy for it.

However, it seems you are experiencing many more 'failed wakes' than anyone else - I hardly ever get failed wakes anymore, and unfortunately the problem is in the framebuffer. Not sure where they're at on fixing that piece, but WisTilt2 said his panel init code was basically done. Now we just need all the other pieces to play nice...

[steveoski]

Originally Posted by fishingmedic

Alright, just tried this again, put a brand new clean FRX04 build w/ the latest rootfs that was just released last night and this kernel, let it boot, and just sit for a few, at which time, without me touching it, it booted back to winmo. Before I do anything further (like run the freaking phone over with my truck...) do you want me to attempt to get a log on it or will one have not even been created as I'm not sure exactly how far the process went?

Edit: I changed a couple of things in the startup.txt and played around with it a bit and giving it another shot. Maybe I should try with the actual package first, then after it boots, go back to winmo, swap in the new rootfs and test kernel?

Edit part 2: Still reboots back to winmo and reboots back before I can get a log or anything. forget it, I just threw it at my neighbor, I'm going back to a freaking flip phone... lol. I'm gonna try booting just FRX04 out of the box and then make changes with rootfs and kernel.

So far so good with clean FRX04...

I'm glad you got it somewhat working I was going to suggest maybe a hard reset on the winmo side, I remember reading something awhile ago about a similiar problem and that's how the guy fixed it I donno just my 2 cents Good Luck

Sent from my FROYO X using Tapatalk

[ndno]

Originally Posted by arrrghhh

Indeed it does, he just updated it last night.

There is ssh into the phone, search for 'dropbear'.

Plus, you can get a full-featured shell using adb... just need to enable it.

/bin/sh

should do it.

Well, I finally installed ADB. Thinking it was only available with the Android SDK, I downloaded the whole Android SDK and boy, the packages it downloaded took forever (my speed is fast but the site it was retrieving packages from is slow); I had this set up on my laptop. Then I vaguely remembered that DroidExplorer already has ADB ... (it was installed on my desktop) and that was a lot easier to set up... duh! Oh well, I guess I will learn how to develop apps for Android now.

I tried telneting into the phone via the DOS prompt, using the command "adb shell" but the screen is messed up (it has extra terminal control characters). What is everyone using for telneting or sshing? putty.exe?

arrrghhh, sorry for being off topic, but since you're actively following almost every XDAndroid thread on XDA, I'll ask: have you tested viruscrazy's latest camera library/kernel? I can only get his latest libcamera.so (2/7 - not the 5MP AF one) to work with his 1/23 kernel; his latest kernel (1/28 ) or (2/7 - the 5MP AF one) gives me a PINK/PURPLE screen after the capture. I posted my dmesg log on XDA for him to check it out.

[arrrghhh]

Originally Posted by ndno

Well, I finally installed ADB. Thinking it was only available with the Android SDK, I downloaded the whole Android SDK and boy, the packages it downloaded took forever (my speed is fast but the site it was retrieving packages from is slow); I had this set up on my laptop. Then I vaguely remembered that DroidExplorer already has ADB ... (it was installed on my desktop) and that was a lot easier to set up... duh! Oh well, I guess I will learn how to develop apps for Android now.

I tried telneting into the phone via the DOS prompt, using the command "adb shell" but the screen is messed up (it has extra terminal control characters). What is everyone using for telneting or sshing? putty.exe?

arrrghhh, sorry for being off topic, but since you're actively following almost every XDAndroid thread on XDA, I'll ask: have you tested viruscrazy's latest camera library/kernel? I can only get his latest libcamera.so (2/7 - not the 5MP AF one) to work with his 1/23 kernel; his latest kernel (1/28 ) or (2/7 - the 5MP AF one) gives me a PINK/PURPLE screen after the capture. I posted my dmesg log on XDA for him to check it out.

1) I don't use telnet or ssh to get into the phone. Just usb connection...

2) I get the same issue with his newest kernel... I saw that log you posted, I need to get him one as well just haven't had the time to mess with it...