[TESTING] - NAND OMGB (1.2.3)

[arrrghhh]

Originally Posted by trevoroni

That one works. Thanks!
Looks like you have a newer version then the one posted on XDA.
I'll try and get a log today if it happens again.

Edit: Here's a log where the screen doesn't wake on the first try, but does on the second.

Looks like you might have some apps causing this issue (pure speculation FYI):

<4>[ 4375.224456] select 1327 (weather.android), adj 15, size 3556, to kill
<4>[ 4375.224487] send sigkill to 1327 (weather.android), adj 15, size 3556
<4>[ 4376.011291] select 1394 (facebook.katana), adj 14, size 8354, to kill
<4>[ 4376.011352] send sigkill to 1394 (facebook.katana), adj 14, size 8354
<6>[ 4376.601348] request_suspend_state: wakeup (3->0) at 4364840000000 (2011-11

Accuweather & Facebook. Do you have this problem on a fresh install, no apps? I'm just wondering if it's some app that is causing an issue. I don't use either of these apps.

[trevoroni]

Originally Posted by arrrghhh

Looks like you might have some apps causing this issue (pure speculation FYI):

Accuweather & Facebook. Do you have this problem on a fresh install, no apps? I'm just wondering if it's some app that is causing an issue. I don't use either of these apps.

I'm not sure if it happened on a fresh install, it was shortly after I installed that I loaded up the apps I use frequently.
I could try uninstalling those two for starters and see if that helps.

Would an app make a difference if it happens more regularly when the phone is charging? It fails to wake on the first try ~50% when it is plugged in as opposed to rarely ever when it is not plugged in.

[arrrghhh]

Originally Posted by trevoroni

I'm not sure if it happened on a fresh install, it was shortly after I installed that I loaded up the apps I use frequently.
I could try uninstalling those two for starters and see if that helps.

Would an app make a difference if it happens more regularly when the phone is charging? It fails to wake on the first try ~50% when it is plugged in as opposed to rarely ever when it is not plugged in.

I doubt it, but I've never had a failed wake problem on NAND. Used to happen on the time on HaRET, now it "just works".

Edit - besides, the phone isn't actually sleeping when it's on the charger, so I don't know what the hell to call that. It's not a failed wake, as the phone isn't even asleep.

Edit 2 - is this consistently reproducible? Put it on the charger, phone fails to wake? I certainly can't reproduce that. Please try on a freshly installed build, no apps - see if you still have the failed wake issue when charging. If so, I'd like to see those logs. Thanks.

[trevoroni]

Originally Posted by arrrghhh

Edit - besides, the phone isn't actually sleeping when it's on the charger, so I don't know what the hell to call that. It's not a failed wake, as the phone isn't even asleep.

I guess so. It's more of a failed panel initialization since the phone still responds to the touchscreen, via vibration of where the 'slide to unlock' should be displayed.

[arrrghhh]

Originally Posted by trevoroni

I guess so. It's more of a failed panel initialization since the phone still responds to the touchscreen, via vibration of where the 'slide to unlock' should be displayed.

Please attempt to recreate without any apps interfering. I can't recreate it, and neither can ACL...

[trevoroni]

Originally Posted by arrrghhh

Please attempt to recreate without any apps interfering. I can't recreate it, and neither can ACL...

I'll try to find some time tonight to wipe everything and see if it still happens.

[[ACL]]

Originally Posted by trevoroni

I'll try to find some time tonight to wipe everything and see if it still happens.

all is not lost. i did find a bug but not related to your issues.

<4>[ 3154.086334] Division by zero in kernel.
<4>[ 3154.086395] [<c02804b4>] (dump_stack+0x0/0x14) from [<c002df78>] (__div0+0x18/0x20)
<4>[ 3154.086486] [<c002df60>] (__div0+0x0/0x20) from [<c0142f4c>] (Ldiv0+0x8/0x10)
<4>[ 3154.086547] [<c0056f40>] (htc_get_batt_info+0x0/0x890) from [<c0058264>] (htc_battery_thread+0x54/0xa0)
<4>[ 3154.086639] [<c0058210>] (htc_battery_thread+0x0/0xa0) from [<c0061360>] (do_exit+0x0/0x7a
<4>[ 3154.086700] r7:00000000 r6:00000000 r5:00000000 r4:00000000

This code wasnt changed since the good ol days, so this buy may have been around for a while. Ill have this fixed for next kernel

Edit: for those of you having isssue.. please try and report the following. 1) test after removing gps.rhodium.so 2) did you use the new LK? 3) does this happen afer a fresh install with no additional apps. thnx

[anish88]

Originally Posted by trevoroni

I guess so. It's more of a failed panel initialization since the phone still responds to the touchscreen, via vibration of where the 'slide to unlock' should be displayed.

So this was the problem, I was having and it was on a freshly installed build. it pretty much started after I updated to the new LK. I notice the failure for the screen to respond when the phone is awake but the screen is off. AKA in situations when the phone is charging or I just recieved a text message and I push the power button while the LED is orange. IDK but it seems that the screen has a problem turning on when the phone is awake. To avoid the problem while charging, I went to setting > applications > Development > and checked Stay Awake while charging. I wonder if there is anything else I can do.