Database Users

Erratic/laggy touchscreen performance

I've been getting very strange/unwanted touchscreen issues for a while now. It seems to happen randomly and for hours at a time. When I press the power button to wake the phone and turn the screen on, I can't even drag the unlock slider to unlock the phone. It takes numerous wake/sleep power button presses until I can get the screen to respond to my finger. Sometimes I'll be typing and it will go crazy and highlight buttons back and forth quickly, usually two or three letters almost always off to the left side of the screen. When this happens I am unable to get it to stop or register any other screen presses. I have to press the power button and then press it again to wake it and I'm stuck at the unlockable lock screen. Only after repeated attempts does it finally get through and the problem will go away for a while, only to come back later.
I have used the program 'Dotty' to track the touch points and I noticed that it will sometimes show a multicolored touch point off to the left of the screen and it will jump around, and it won't detect any other new touch points.
Soooo I think my screen touch sensor is messed up somehow. Does anyone else have this happen? Seems to have started when I flashed the kernel to get rid of the 30 fps cap. I have recently flashed Fresh 3.1.0.1 and still have this problem, different kernel with that rom correct? I'll try to get a video up sometime to show this in action...

Yes, I've been having the exact same issue. I even did a hard reset, with the assumption that it was an app. My plan was to add them back slowly until I got the issue, the problem was it happened as soon as the phone rebooted on the reflash. I have no idea what the issue is, but its very frustrating.
I'm running 2.2 stock...

Some people have reported touch screen problems with netarchy's kernel. There is usually a revision to correct this problem for people who are experiencing it. I suggest you carefully read over the OP in that thread and determine what kernel is right for you. There is usually a version specifically for Fresh users also.

MIGHT i ask what widgets are you running??
i talked about it before when running the pre-official ota rom.
it was my htc music widget (half sized one) i had running on the home screen.. caused lag like a mofo, couldnt swipe most of the time, capacitive buttons wouldnt react, pressing the app drawer button wouldnt respond till 5 seconds later...
AS A MATTER OF FACT.
im running fresh 3.1.0.1 + latest kernel + music widget on home screen.. LAAAGGG like before. removing it makes things snappier again.
YEP. Its happening again.
when i ran the STOCK Official rooted rom, with music widget on home screen didnt produce this lag and poor touch input, even with kernel it didnt produce this problem.

Mine is fine, no screen problems!!! stock rooted rom!!

my atrix locks up

i have had my atrix for 4 days now and its locked up 3 times were i had to take the battery out to restart it anyone else have this problem anyone no how to fix it or should i return it for a new one

kga943 said:
i have had my atrix for 4 days now and its locked up 3 times were i had to take the battery out to restart it anyone else have this problem anyone no how to fix it or should i return it for a new one
Click to expand...
Click to collapse
Did you install any applications from the market? Is your phone freezing while a certain application is open or does it freeze even on the homescreen? If you have a lot of applications installed try to deinstall and look if it becomes better. If not try a factory reset. If it still freezes than return it for a new one.

Would you mind saying what you were doing when it locks up?
If it's during Music, it doesn't actually lock up, it just shows a black screen for about half a minute. Everything still functions, it just doesn't show.

Two times trying to answer a call the screen would not unlock nothing would work I had to take the battery out and just todayit was sitting on my desk and it would not turn on when I tried to use it
The green message light was on very dim and I had to take the battery out
Sent from my MB860 using XDA App

I have a feeling there is a bad batch of units out there.
Try factory reset and see if it continues to lock up, if it does, return it for another.

kga943 said:
Two times trying to answer a call the screen would not unlock nothing would work I had to take the battery out and just todayit was sitting on my desk and it would not turn on when I tried to use it
The green message light was on very dim and I had to take the battery out
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Sounds like a broken phone. Try a factory reset (if you return it they anyway ask if you did that) and if that won't help get a new one....

kga943 said:
Two times trying to answer a call the screen would not unlock nothing would work I had to take the battery out and just todayit was sitting on my desk and it would not turn on when I tried to use it
The green message light was on very dim and I had to take the battery out
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Same thing happened to me yesterday, the light was very dim green and the phone did not respond until I pulled the battery. It hasn't happened again.
I've already had to replace my Atrix for another issue. Right now my confidence in this phone is not very high, but it is brand new. Lots of issues will probably pop up and be fixed via software updates- at least I hope thats the case.

It really feels like all the issues people are having with this phone are software related. Maybe motorolla will just cave and give us gingerbread with no blur

I've had the same problem while playing music...over the past 3 days after about 30 minutes of tunes it'll lock up and after another 5 reset itself...i've done the reset after the second and it still does it...i'm bout to take it back and exchange it...i expect glitches but damn.
Motorola Atrix (stock)
AT&T Fuze (Energy.RAPHAEL.21916.Sense2.5.Cookie.2.0.sencity)

I have had the issue happen 2 me twice in 3 days, the last time was when adding the note widget to screen. It was not completely locked up just the touch screen, i could press the power off button but the touch screen would not let me shutdown

something you might want to try if a factory reset doesn't work would be a reinstall from the recovery menu.
power your phone off
hold the down volume key and the power button
release the power button once the phone begins to boot
keep holding the down volume button until you see "fastboot" at the top of the screen
now be careful, the down volume button navigates through the boot options and the up volume selects one
so press the down volume button until you come across "android recovery"
once you see it press the up volume button to select it
once you get to the screen with the exclamation mark tap the bottom right of the touchscreen, this should pop up the recovery menu
select wipe data/factory reset
let the phone do it's thing
good luck
I've seen this resolve some audio codec issues that were causing the phone's mic to not work, dunno if it'll work for your issue but it can't hurt to try.
best of luck
bl4ck0ut

I have found a fix for my lockup issue. If the screen is on and lockup (no touch screen) press the power button 2, turns off the display and turns it back on and everything continues to work fine.

mrlinux11 said:
I have found a fix for my lockup issue. If the screen is on and lockup (no touch screen) press the power button 2, turns off the display and turns it back on and everything continues to work fine.
Click to expand...
Click to collapse
I have the same problem (screen randomly locks up once or twice a day, buttons dead) and have found the above "solution" to work perfectly, also. The problem however is that pressing the power button twice and unlocking the phone is not exactly elegant especially if the screen locks while you are trying to answer an incoming call.
I changed my battery settings to "performance mode" as I read somewhere that that might help. I will let you know if that seems to resolve the issue.

Changing battery setting doesn't seem to do anything. I still get my share of frozen/locked up screens a few times a day. Still have not figured out how to replicate the behavior. It really does seem random.

I've been suffering from this as well, I'm going to try to exchange my phone and see if that helps.

Exchanged my phone today. So far I haven't seen any locked/frozen screen issues. I am relieved. Maybe there are just a few bad units out there.
Also for what it is worth ... the lady at AT&T told me that taking out the battery while the phone is on would fix it. Since I never figured out how to replicate the behavior I couldn't verify that her suggestion would indeed actually fix the problem and demanded an exchange anyways.

atrix does lock up and have glitches
lock up glitch:
While in standby (screen black), it locks up. You obviously don't know when exactly it happens as it's lying around in standby. When you press the powerbutton to wake it up, nothing happens. You can try what you want, long press, several presses, just dead phone. As if the battery losts juice, but 2 times it happened and the battery was above 50%.
Tired to connect the charger while in that lock-up state. Nothing happens The notification light remains black as well.
The 2nd time this happened to me, I had the idea to call myself and see if just the powerbutton has a glitch and the phone is actually running just remaining in standby with a black screen. But nope, the phone didn't ring or wake up.
Only way to recover is to take the battery out.
I didn't mess with my phone and was very careful in which apps I installed. The only ones I have are very populoar 4+star apps:
extended controls
easy profiles
the other apps are most of the time not even running:
photoaf, vignette, imdb, nytimes, fb, skype, pandora, screen filter, droid light, prozoom5x camera
No games at all installed...
The 2nd glitch that happened to me a couple of times is that the finger print sensor is not working: It doesn't display any message as in " did not verify, too short, ..." it's just dead, the only way to get in is to punch in the number code.
This is typically fixed after switching the phone off fully.
Of course skype also doesn't work on my atrix (well known mic issue)

It happened to me as well. I had installed some apps but when it froze it had been off (the screen that is) so it was sitting then when I tried to open it by pressing the power button the green light came on but it would not wake. I removed the battery, replaced it then it did the same thing again (including the green light). I removed and installed the battery once more then it was fine. It must have been something in the backround but not sure as to what that was. Hasnt happened again though.

pedroosan said:
lock up glitch:
While in standby (screen black), it locks up. You obviously don't know when exactly it happens as it's lying around in standby. When you press the powerbutton to wake it up, nothing happens. You can try what you want, long press, several presses, just dead phone. As if the battery losts juice, but 2 times it happened and the battery was above 50%.
Tired to connect the charger while in that lock-up state. Nothing happens The notification light remains black as well.
The 2nd time this happened to me, I had the idea to call myself and see if just the powerbutton has a glitch and the phone is actually running just remaining in standby with a black screen. But nope, the phone didn't ring or wake up.
Only way to recover is to take the battery out.
I didn't mess with my phone and was very careful in which apps I installed. The only ones I have are very populoar 4+star apps:
extended controls
easy profiles
the other apps are most of the time not even running:
photoaf, vignette, imdb, nytimes, fb, skype, pandora, screen filter, droid light, prozoom5x camera
No games at all installed...
The 2nd glitch that happened to me a couple of times is that the finger print sensor is not working: It doesn't display any message as in " did not verify, too short, ..." it's just dead, the only way to get in is to punch in the number code.
This is typically fixed after switching the phone off fully.
Of course skype also doesn't work on my atrix (well known mic issue)
Click to expand...
Click to collapse
strange, skype worked for me... oh well.
did you ever find a solution for the lockup issue, have the same thing, very frustrating but not as frequent as you thankfully.

My Atrix started to freeze up when I undervolted the CPU using SetCPU and I would have to pull the battery out and restart it. I increased the voltage settings and it hasn't locked up since, so if you have undervolted your CPU and your phone is locking up, you should increase the voltages.

error: curcial_oj_early_suspend MyTouch 4G screen keep turning off random

MyTouch 4G keep turning off the display seemingly at random intervals and it stays off many times for long periods before it starts to behave normal. All other functions such as phone, alerts, receiving mail etc work normal while it is still in that state. In addition to the above, I also see quite a bit of curcial_oj_early_late_resume errors and a few others using OS Monitor to view the message log.
Here is what i have found out from 2 months of trying to fix it:
1. All buttons are always lit while this happens as if the screen was actually on (being used) - it even turns off the screen in the middle of using an application.
2. It receives calls, mails and messages as usual but the screen stays black. If I play with it, swiping to answer call, sometimes I am able to answer the call and talk normal.
3. At it worst times I stays blank/black even before the splash-screen and even if I try booting into recovery mode.
4. However, most of the time the blank screen appears just right after the splash-screen and the phone continue to boot normal.
5. Right after periods that it stays up long enough for me to see and flash a new ROM, it will behave for a while ... even hours normal ... then it starts acting up.
6. I tested it once while it was in boot mode and the screen stayed on for a very very long time without any problems (guess ruling out heat related?)
7. Even with different ROM versions it still occurs.
8. When it first happened was due to a battery drain (battery was changed to rule that out).
9. It behaves like a radical energy manager turning off the screen (why?) until a condition is meet. (recently used SetCPU to lower processor speed to minimum just in case of heat related ... did not work)
10. Power button has no effect on halting the problem once it is acting up
11. Problem seem to occur quicker after a ROM install as time progresses.
What has been done : (what OS routine or setting could survive this? ...)
1. Many complete wipes and re-installs (10+) via clockworkmod manually or ROM manager. (Many different Cyanogenmod ROM versions tried)
2. Changed battery.
3. SD card Format and tried different SD card. Also tried without SD card or SIM.
4. Tried different versions of busybox.
5. Lowered CPU speed to a constant 245Mhz
6. check if it is triggered by pressure, movement, or light ... (proximity sensor appears to work perfectly ok when I do take a call)
7. Sometimes the only way i can get the screen back on is to keep calling the phone and playing around with using the proximity sensor to trigger the wake. Takes hours of trying before that works though.
8. Tried "stay awake while plugged in" setting ... did not work
9. Tried running without adding any apps except those that came with ROM ... didn't work
10. Increased the screen time-out interval ... (even from ROM install it seem to ignore this time-out) ... if the screen stays inactive for 3 sec it shuts off the screen ... keep doing so until the interval get longer and longer
11. Used and Android antivirus to scan ... no problems found
12. Recently changed to Virtuous Unity which helped be bring it back from display off state with a press of the power button (pressing once to stop it -all button lights go out, and once more to bring the display up) ... but still turns off display frequently.
... few other things tried, but you get the idea.
Oh yea, I perm rooted from a while back and it worked perfectly for months before this started happening ... it started before I even considered to flash my first ROM.

[Q] CM7 on Nook Color has blackout issue

I have been running CM7 on my Nook Color successfully for about 6 months now, but there is an ongoing issue that drives me nuts. Any help is appreciated. The problem is that, occasionally (about 4-5 times a week), the Nook will go to screen timeout and then not be able to come back out with any combination of buttons. The "n" button, power button, volume buttons, etc. all have absolutely no effect whether you press and release or hold down. The only way to get things back is to hold down the power button for 8-10 seconds and release...then hold the power button down again until the screen flashes and the green Cyanogen logo comes up. This, to me, is forcing it to shut down and then rebooting, though I can't see what's going on onscreen until the reboot. Then it will boot normally and work like normal......until the next blackout.
This happens even if the battery meter is fully charged, mid-way, or getting low...makes no difference. It will also happen no matter what the screen was when it timed out (home screen, app screen, etc.). Any ideas?

emopdx34 said:
I have been running CM7 on my Nook Color successfully for about 6 months now, but there is an ongoing issue that drives me nuts. Any help is appreciated. The problem is that, occasionally (about 4-5 times a week), the Nook will go to screen timeout and then not be able to come back out with any combination of buttons. The "n" button, power button, volume buttons, etc. all have absolutely no effect whether you press and release or hold down. The only way to get things back is to hold down the power button for 8-10 seconds and release...then hold the power button down again until the screen flashes and the green Cyanogen logo comes up. This, to me, is forcing it to shut down and then rebooting, though I can't see what's going on onscreen until the reboot. Then it will boot normally and work like normal......until the next blackout.
This happens even if the battery meter is fully charged, mid-way, or getting low...makes no difference. It will also happen no matter what the screen was when it timed out (home screen, app screen, etc.). Any ideas?
Click to expand...
Click to collapse
This is Sleep of Death (SOD). Well known issue. It happens when you have wifi set to stay on all the time. When the screen turns off and the nook goes into deep sleep, sometimes wifi and deep sleep get tangled up and you can't turn the screen back on. Only solution is to change your wifi setting or get a patched wifi module and flash that to your system. If you want a link to that patched file just ask and I will post it.
Edit: here it is:
http://d01.megashares.com/dl/8VPCE7N/wifi_SOD_patch.zip
Sent from my NookColor running ICS and Tapatalk

Thanks for the solution
I guess I wasn't using the magic keywords to find the problem online. Thank you so much for the solution and link.

@leapinlar: Do we know if that fix will work with mrg666's new kernel?
It still reports 2.6.32.9 in about tablet but I was under the impression that was because he was too tired to change it that night.
In my case I'm just happy to set wifi to turn off when the screen turns off, (I hate, hate, double hate, loath entirely when a device I've put to sleep trys to get my attention).

MISRy said:
@leapinlar: Do we know if that fix will work with mrg666's new kernel?
It still reports 2.6.32.9 in about tablet but I was under the impression that was because he was too tired to change it that night.
In my case I'm just happy to set wifi to turn off when the screen turns off, (I hate, hate, double hate, loath entirely when a device I've put to sleep trys to get my attention).
Click to expand...
Click to collapse
The patch only works on 2.6.32.9 kernels. I don't know anything about his new kernel. Just backup your existing twlan_drv.ko in /system/lib/module by renaming it .bak before flashing, and if it does not work restore your backup.

leapinlar said:
The patch only works on 2.6.32.9 kernels. I don't know anything about his new kernel. Just backup your existing twlan_drv.ko in /system/lib/module by renaming it .bak before flashing, and if it does not work restore your backup.
Click to expand...
Click to collapse
Yeah, I did that last night and didn't get an SOD but that really doesn't tell us much. I'll try to remember to take this over to his thread.

MISRy said:
Yeah, I did that last night and didn't get an SOD but that really doesn't tell us much. I'll try to remember to take this over to his thread.
Click to expand...
Click to collapse
Well, if you flashed it and wifi still works, it is compatible. On the CM9 kernel, it worked on .9 kernel until they updated to .59 and then if you used the patch, wifi quit working.

[Q] Sometimes phone doesn't wake up

Not sure how to describe this other than sometimes the phone just doesn't turn on.
It's very odd, and I can't always recreate it, but sometimes I can.
Occasionally, if I get a notification and the screen comes on then after 10 seconds it will time out and turn off automatically (this is normal). At this point, if I press the power button to turn the screen back on within 5 minutes of it turning off then it doesn't come back on. The back and menu buttons light up, and the volume works, I can even answer a call with the home key and the phone works. The screen just doesn't come on.
If I press the button 4 or 5 times in a row, it eventually wakes up. Sometimes, I have to hold the power button to cause the power menu to come up, that will sometimes wake up the screen. This makes me think there is some system process hanging causing the screen not to display until it unfreezes, but I can't tell what that is.
This happens to me at least once a day and I can't figure it out.
I'm on android 4.4.2 with SHOstock-i v5.0 with MDL baseband.
I did some research, there are threads where other people were talking about almost the exact same issue, but a different rom and a different phone. Does this mean it's a hardware failure issue or some specific setting/app causing it? This is driving me crazy.
What I have tried:
Reflashing the ROM
Flashing ROM with full wipe
Throttling CPU (since disabled)
Alternative Kernel (although no one else is complaining of this issue)
Uninstalling random apps to see if it goes away (hard for me to run without any apps)

Have you tried the new 6.1? I'm running it and it is very smooth. I had similar issues on the att version of Shostock. I can't say whether the full wipe or the new rom fixed my issue, but it is running smoothly now.
You could also try running Greenify.
Sent from my SAMSUNG-SGH-I337 using Tapatalk

XGhozt said:
Not sure how to describe this other than sometimes the phone just doesn't turn on.
It's very odd, and I can't always recreate it, but sometimes I can.
Occasionally, if I get a notification and the screen comes on then after 10 seconds it will time out and turn off automatically (this is normal). At this point, if I press the power button to turn the screen back on within 5 minutes of it turning off then it doesn't come back on. The back and menu buttons light up, and the volume works, I can even answer a call with the home key and the phone works. The screen just doesn't come on.
If I press the button 4 or 5 times in a row, it eventually wakes up. Sometimes, I have to hold the power button to cause the power menu to come up, that will sometimes wake up the screen. This makes me think there is some system process hanging causing the screen not to display until it unfreezes, but I can't tell what that is.
This happens to me at least once a day and I can't figure it out.
I'm on android 4.4.2 with SHOstock-i v5.0 with MDL baseband.
I did some research, there are threads where other people were talking about almost the exact same issue, but a different rom and a different phone. Does this mean it's a hardware failure issue or some specific setting/app causing it? This is driving me crazy.
What I have tried:
Reflashing the ROM
Flashing ROM with full wipe
Throttling CPU (since disabled)
Alternative Kernel (although no one else is complaining of this issue)
Uninstalling random apps to see if it goes away (hard for me to run without any apps)
Click to expand...
Click to collapse
Not familiar with your rom but I know any rom I have tried where idle speed is set to 182 I find the occasional freeze then pushing too many buttons causes a reboot. The rom I am using now has the min set to 384 MHz and that seems to work very well, not one wake up issue or reboot. Depends if your kernel has a tweaker tool or not. Currently using googy-max kernel which comes with a tweaker.... you would need to research if it is compatible with your rom though..... this kernel set on battery profile gives me currently 1 day 20 hrs.... screen on time 2 hrs... battery left... 44% pretty good I'd say....

Gage_Hero said:
Not familiar with your rom but I know any rom I have tried where idle speed is set to 182 I find the occasional freeze then pushing too many buttons causes a reboot. The rom I am using now has the min set to 384 MHz and that seems to work very well, not one wake up issue or reboot. Depends if your kernel has a tweaker tool or not. Currently using googy-max kernel which comes with a tweaker.... you would need to research if it is compatible with your rom though..... this kernel set on battery profile gives me currently 1 day 20 hrs.... screen on time 2 hrs... battery left... 44% pretty good I'd say....
Click to expand...
Click to collapse
I don't think I can change the clock speed with my kernel. I will try that but I'm not sure that's the issue since the phone appears to be functioning even when the screen is stuck off. You might be on the something, if I press too many buttons that's usually how I can cause it to reboot/crash.

Try using cpu spy to see what the minimum clock setting is. Shostock 6.1 appears to be 384
Sent from my SAMSUNG-SGH-I337 using Tapatalk

Red_81 said:
Try using cpu spy to see what the minimum clock setting is. Shostock 6.1 appears to be 384
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Yes, I am on v5.0 and it's set to 384. The issue might not be the clock speed.
This ROM doesn't have support for manually changing the clockspeed anyway.
Any other ideas?

I noticed we both had 32gb. Maybe the tolerances on the chip are not quite as good as the 16gb. I did play with cpu settings because waze would cause my phone to really heat up.
Sent from my SAMSUNG-SGH-I337 using Tapatalk

I have since changed to a different kernel and I have not had the issue yet (~13 hours running).
I can only assume this is a bug with the kernel until I have the issue again. My attempts to recreate it on the new kernel have failed.

XGhozt said:
Not sure how to describe this other than sometimes the phone just doesn't turn on.
It's very odd, and I can't always recreate it, but sometimes I can.
Occasionally, if I get a notification and the screen comes on then after 10 seconds it will time out and turn off automatically (this is normal). At this point, if I press the power button to turn the screen back on within 5 minutes of it turning off then it doesn't come back on. The back and menu buttons light up, and the volume works, I can even answer a call with the home key and the phone works. The screen just doesn't come on.
If I press the button 4 or 5 times in a row, it eventually wakes up. Sometimes, I have to hold the power button to cause the power menu to come up, that will sometimes wake up the screen. This makes me think there is some system process hanging causing the screen not to display until it unfreezes, but I can't tell what that is.
This happens to me at least once a day and I can't figure it out.
I'm on android 4.4.2 with SHOstock-i v5.0 with MDL baseband.
I did some research, there are threads where other people were talking about almost the exact same issue, but a different rom and a different phone. Does this mean it's a hardware failure issue or some specific setting/app causing it? This is driving me crazy.
What I have tried:
Reflashing the ROM
Flashing ROM with full wipe
Throttling CPU (since disabled)
Alternative Kernel (although no one else is complaining of this issue)
Uninstalling random apps to see if it goes away (hard for me to run without any apps)
Click to expand...
Click to collapse
I haven't experienced this with my GS4. But with my GS2 I had this problem and it seemed to happen with custom Kernels and with the min set to 182. I seen someone else mention this too .. The fact I haven't seen this yet is probably because I cant underclock being my bootloader is locked and I cant flash a custom kernel..Have you tried a different scheduler . It seemed to be worse on my gs2 when I had it set to NOOP. Hope you get this figured out because I know how frustrating it is to have as a problem..My Gs2 almost turned into a 70 mph fastball into a brick wall numerous times EDIT .. My fault I didn't see your post about it being set to 384 already

spirodave said:
I haven't experienced this with my GS4. But with my GS2 I had this problem and it seemed to happen with custom Kernels and with the min set to 182. I seen someone else mention this too .. The fact I haven't seen this yet is probably because I cant underclock being my bootloader is locked and I cant flash a custom kernel..Have you tried a different scheduler . It seemed to be worse on my gs2 when I had it set to NOOP. Hope you get this figured out because I know how frustrating it is to have as a problem..My Gs2 almost turned into a 70 mph fastball into a brick wall numerous times EDIT .. My fault I didn't see your post about it being set to 384 already
Click to expand...
Click to collapse
This might be related, but I'm not sure. The new kernel I'm on is actually set to 189Mhz - 1998Mhz and I have yet to have the issue happen again.

XGhozt said:
This might be related, but I'm not sure. The new kernel I'm on is actually set to 189Mhz - 1998Mhz and I have yet to have the issue happen again.
Click to expand...
Click to collapse
Right on .. Sounds like a kernel issue to me also ..I ran into the problem more often when I was playing music with the screen off .. Mind you that was on my tmobile gs2..It seemed to me that when any button was pressed to turn the screen on It was like it wasn't scaling through freqs enough to power on.. Hopefully your issue is resolved ... Now I know if I run into this issue in the future ill know its kernel related

I just wanted to follow up here. I noticed the issue happen again but this time it was right after I made a change. I'm using GO TaskManager EX and there is a setting in here to "Clear when turn on screen" and "Clear when turn off screen". When either of these are enabled then it causes the device to take an extra 15 seconds to wake and/or it doesn't wake at all.
Still not 100% sure if this was the original issue, but I thought I would post it in case anyone else is using this as well. Especially since it caused a similar behavior.
Major face-palm moment.