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

[bugsyounot]

So I was running the new kernel for a while, it was working well, but then it rebooted right after I finished a phone call on my Sprint RHOD400. :P

[ndno]

Originally Posted by Recursion

2. Rebooted. LED is green, hard key LEDs won't turn off.

As arrrghhh said, the buttons remaining lit is a residual from WinMo if they are already on. Just push the power button in WinMo to put it to sleep (leds will turn off) then push it again to wake up WinMo, then boot to Android.

[steveoski]

ok I just started testing this kernel last night and here is my thoughts. My phone hasn't been insta wakin. I have to hit the button a few times but when it does light up the screen does seem to turn on much faster. Now I don't have to hit it multiple times everytime but def more than a few.

Oh one thing that I forgot is that the phones green light comes on immediately as the phone goes to sleep. I seen someone else post something about that. I have the same issue. Well I donno ifits an issue but it def hits deep sleep fast seems to good to be true.

I have a rhod400 on sprint
Using froyox latest

Sent from my FROYO X using Tapatalk

[Counterfeit]

Started using this kernel at about 11pm last night. Insta sleep for sure..about 30% of the time I have to hit the power multiple times to get it to turn on. Not too bad..I like how it goes to deep sleep when plugged in even! Sweeeet. Using FRX04 with an XDA rootfs for key functionality. It slept the whole not plugged in and woke up just fine.

Sent from my MSM using Tapatalk

[arrrghhh]

Originally Posted by Counterfeit

Started using this kernel at about 11pm last night. Insta sleep for sure..about 30% of the time I have to hit the power multiple times to get it to turn on. Not too bad..I like how it goes to deep sleep when plugged in even! Sweeeet. Using FRX04 with an XDA rootfs for key functionality. It slept the whole not plugged in and woke up just fine.

Sent from my MSM using Tapatalk

Originally Posted by steveoski

ok I just started testing this kernel last night and here is my thoughts. My phone hasn't been insta wakin. I have to hit the button a few times but when it does light up the screen does seem to turn on much faster. Now I don't have to hit it multiple times everytime but def more than a few.

Oh one thing that I forgot is that the phones green light comes on immediately as the phone goes to sleep. I seen someone else post something about that. I have the same issue. Well I donno ifits an issue but it def hits deep sleep fast seems to good to be true.

I have a rhod400 on sprint
Using froyox latest

Sent from my FROYO X using Tapatalk

Ok, I explained this (perhaps poorly) in the first post. WisTilt2 gave me another test kernel (not for distro, sorry ) that simply blinks green when ARM11 collapses, and solid green when microp collapses. With GPS enabled, I only get blinking LED. Charging, USB, etc... blinking LED.

So the ARM11 is properly collapsing, but unfortunately in the kernel that has been released the solid green LED shows either ARM11 collapse or microp collapse. WisTilt2 said he had more work to do on mircop-related collapse, as in the 'lots of other PM-stuff still to fix'. So that's the low-down... the sleep LED previously only represented microp collapse, and now it represents both - or either or....

[fishingmedic]

Arrrghhh, should I not try to set up a new build w/ the latest test kernel? I'm trying the new kernel and deleted the data/img and accidentally the touchscreen settings so it was creating both, and as soon as it finishes booting and settles down, it boots back to winmo. Do you want me to try to get any errors out of this, or just try resetting it up w/ a non test kernel?

[arrrghhh]

Originally Posted by fishingmedic

Arrrghhh, should I not try to set up a new build w/ the latest test kernel? I'm trying the new kernel and deleted the data/img and accidentally the touchscreen settings so it was creating both, and as soon as it finishes booting and settles down, it boots back to winmo. Do you want me to try to get any errors out of this, or just try resetting it up w/ a non test kernel?

So you're still getting reboots to WinMo no matter what? We should setup a chat sometime bro, I'm not having those kinds of problems at all...

[jae18708]

Where are the logs found that you all are posting? I would love to contribute my logs but don't know where they're located in the phone (or how to create them?). Perhaps it should be explained in the first page. I think more people would be willing to help out. If I happened to overlook the instructions, I apologize, I only got about 3 hrs of sleep last night... damn calc professor!

Peace

Sent from my Touch Pro2 using Tapatalk Pro

[fishingmedic]

Originally Posted by arrrghhh

So you're still getting reboots to WinMo no matter what? We should setup a chat sometime bro, I'm not having those kinds of problems at all...

So far it's going better now, no reboots after trying one last time (I think the phone knew I was complaining to you and decided to straighten up....lol). I just wasn't sure if it was because of the test kernel or not. I'm setting everything up again, i.e. emails, apps, etc and we'll see what happens. I also realized I had it OC'ing on first boot and removed that, so maybe that was it. Who knows at this point, but so far so good. And yeah, we'll chat soon, but my wifes pissing and moaning the same way everyones is in the Nand thread, lol... women just don't understand boys and their toys!

[jae18708]

I dont know if this is kernal or rootfs.. but I just switched to this kernel and noticed when device is unlocked on the lock screen, the menu button unlocks the device.

Sent from my Touch Pro2 using Tapatalk Pro