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

southernSTYLE · #**221** (**permalink**) 02-13-2011, 05:16 PM

First off thanks for all the hard work, you guys are awesome.

I am testing the Gingerbread on my Rhod500. And I noticed that I don't have a single issue with the panel turning on when I use the top button, but if I use the end key (which is the power button on Rhod500) I get the wakeup issue. And when I use the latest kernel from this thread I get the same issue. Is it possible that the Sprint and Verizon versions have them mapped differently? I didn't do much searching to be honest, but I'm pretty sure I'm onto something here.. (feeling kinda smart)

**ndno** · #**222** (**permalink**) 02-14-2011, 01:07 AM

arrrghhh, I've been using this with the FRX04 Froyo bundle you posted yesterday. Seems to work fine most of the times. However, I have a couple times in which the phone went to sleep (blinking green and orange) and when I try to wake it, I had to press the power button multiple times for like 30 seconds; sometimes, I would need to slide out the keyboard to wake it up; almost seemed like I had a SOD but I eventually get it to wake with more power button presses or keyboard sliding outs. This occurs when I was using an app (like tapatalk, sms, browser) and left the phone there to go do something else; when I came back it was in deep sleep; when I press the power button, it turned and stayed orange and seemed unresponsive as I mentioned above.

**arrrghhh** · #**223** (**permalink**) 02-14-2011, 10:31 AM

Quote:

Originally Posted by ndno

arrrghhh, I've been using this with the FRX04 Froyo bundle you posted yesterday. Seems to work fine most of the times. However, I have a couple times in which the phone went to sleep (blinking green and orange) and when I try to wake it, I had to press the power button multiple times for like 30 seconds; sometimes, I would need to slide out the keyboard to wake it up; almost seemed like I had a SOD but I eventually get it to wake with more power button presses or keyboard sliding outs. This occurs when I was using an app (like tapatalk, sms, browser) and left the phone there to go do something else; when I came back it was in deep sleep; when I press the power button, it turned and stayed orange and seemed unresponsive as I mentioned above.

Yup, I believe acl said it was a vsync issue with the framebuffer... I think I need to get him to clean up his framebuffer code, as I think it's also causing the problem with not being able to calibrate the screen on newer kernels...

He's swamped in NAND right now, so not sure when I can get him to work on this... but it seems the timing on the framebuffer needs some work. Thanks for the report!

**arrrghhh** · #**224** (**permalink**) 02-16-2011, 10:49 AM

I've posted a new kernel - this is for everyone (with a RHOD), especially RHOD100/AUO users who had issues with the last kernels, or with the newest GIT kernel 1258. My phone has been waking basically instantaneously, which is incredible. Let me know how it goes guys!

**ndno** · #**225** (**permalink**) 02-17-2011, 02:02 AM

I just switched over to this new kernel and boom (doh!!!), got a reboot to WinMo. This happened after I accidentally enabled airplane mode, so I disabled it and data still didn't work. So I decided to add a second APN and while entering the APN name using the soft keyboard, it booted back to WinMo. Attached is the log.

Got this line in the log:
[ 817.262115] kernel BUG at drivers/char/tty_ldisc.c:199!

After which, the kernel crash dump data appears.

Distribution used: FRX04 Official Bundle, OCed at 700Mhz. I'm using ADW Launcher. SIDE NOTE: I was using Zeam Launcher but kept getting FCs on Zeam after my TP2 went into deep sleep using the last 1253 Wistilt2 test kernel you posted; so I decided to use ADW Launcher. Not a big fan of default Launcher2.

**arrrghhh** · #**226** (**permalink**) 02-17-2011, 10:48 AM

Quote:

Originally Posted by ndno

I just switched over to this new kernel and boom (doh!!!), got a reboot to WinMo. This happened after I accidentally enabled airplane mode, so I disabled it and data still didn't work. So I decided to add a second APN and while entering the APN name using the soft keyboard, it booted back to WinMo. Attached is the log.

Interesting... I saw the infamous

Code:

[  817.262237] Unable to handle kernel NULL pointer dereference at virtual address 00000000

line right after that kernel BUG line. I'll shoot this log to WisTilt2, see what he thinks. Thanks!

**ndno** · #**227** (**permalink**) 02-17-2011, 04:00 PM

OK, pretty solid now. Been running it all morning (some emailing, some tapatalk, some texting, some other stuff) without issue. With this kernel, the led stays solid green when in deep sleep; it's not blinking green and orange like the previous test kernel, is that correct?

Hmmmm... my battery indicator always seems to be near "full" (even when it's really at 45%), didn't see this on the previous kernel.

**arrrghhh** · #**228** (**permalink**) 02-17-2011, 05:46 PM

Quote:

Originally Posted by ndno

OK, pretty solid now. Been running it all morning (some emailing, some tapatalk, some texting, some other stuff) without issue. With this kernel, the led stays solid green when in deep sleep; it's not blinking green and orange like the previous test kernel, is that correct?

Hmmmm... my battery indicator always seems to be near "full" (even when it's really at 45%), didn't see this on the previous kernel.

Battery indicator needs some work, perhaps WisTilt2 has started to work on it and some of it slipped into this kernel... not sure on that.

He pulled 1258 as a base, which set the sleep LED back to solid green. He didn't change it back.

**ndno** · #**229** (**permalink**) 02-18-2011, 01:13 AM

Got me another reboot to WinMo (while filling out a form with soft keyboard under Opera Mini). See attached log (looks like a IP stack/ppp network issue).

I actually had a SOD earlier (green LED wouldn't wake up no matter what I did) when my battery was less than 10% (this was the value when I pulled the battery and boot back to WinMo). Unfortunately, I wasn't able to find the SYSTEM_LAST_KMSG for that SOD

**arrrghhh** · #**230** (**permalink**) 02-18-2011, 04:03 PM

Got another new kernel from WisTilt2. A lot of AUO folks were having problems, I'm hoping those are now squashed with this new kernel.

On my RHOD400 I do still see occasional times where the phone doesn't wake on its own without touching the panel, and WisTilt2 is pretty confident at this stage that the issue is on the .35 framebuffer - timing issues with the vsync basically.

With that said, this new kernel should be better. Until we can sort out the issue with the fb, they won't entirely go away...

So test this kernel out guys, let me know how it goes!