Related
Does anyone elses G1 not wake up when Menu is pressed? Sometimes I have to press it like 6 times before the phone wakes up, does anyone know why?
Mine does this as well. I just thought it was learning from it's owner (I take more than 5-6 pokes to wake me up too).
My only guess is that something is running in the background in order to slow it down and the number of presses has little to do with it.
momentarylapseofreason said:
Mine does this as well. I just thought it was learning from it's owner (I take more than 5-6 pokes to wake me up too).
My only guess is that something is running in the background in order to slow it down and the number of presses has little to do with it.
Click to expand...
Click to collapse
Yea, i was thinkin the same, i should try runnin a ton of apps and find out if [email protected] the problem
mine does the same things sometimes. gets annoying at times. usually i just open and close the keyboard
Mine recently started this, it must be something we downloaded, plus I have the following problems too, they all started at the same time:
1) When someone calls, the screen stay blank for a while so the phone rings but the screen is off so I dont see whos calling
2) The background keeps changing back to the original blue picture thing
3) The WiFi keeps turning off and drians the battery, nothing I do stops it from turning on. I have all sorts of software running, I even ask Locale to turn it off if its between 12.01am to 11pm and still WiFi keeps poping up.
4) Battery drains FAST lately.
I uninstalled a long list of software and problem is not solved.
Brooklynite!
brooklynite said:
Mine recently started this, it must be something we downloaded, plus I have the following problems too, they all started at the same time:
1) When someone calls, the screen stay blank for a while so the phone rings but the screen is off so I dont see whos calling
2) The background keeps changing back to the original blue picture thing
3) The WiFi keeps turning off and drians the battery, nothing I do stops it from turning on. I have all sorts of software running, I even ask Locale to turn it off if its between 12.01am to 11pm and still WiFi keeps poping up.
4) Battery drains FAST lately.
I uninstalled a long list of software and problem is not solved.
Brooklynite!
Click to expand...
Click to collapse
Shop Savvy?
I also started having the wake up problem and quicker then normal battery drain. I have an ADP1 phone which I updated to 1.1 a few days before noticing issue
I think that the theory of something sucking clock cycles is a good one. I noticed my CPU Usage (when nothing was running other then System Monitor) went from 0-40% to 20-70%.
I couldn't be bothered with the finer points of troubleshooting, so I took the thermo-nuclear approach and did a factory wipe.
Just before the mystery CPU cycle and wake up issue, I hadn't installed any new apps, BUT I did update a bunch of existing apps. After the factory wipe, I left off installing the following list:
Watts
StreamFurious
DroidFTP
Telnet
e-VoiceRecorder
VoiceRecorder
Constitution
Barcode Scanner
Astro
RingDroid
SlovoEd Classic English Dictionary
Things are fine now.
both of my g1's do this, and have done this out of the box, anyone turn off there screen with the keyboard out, and then close the screen and the screen comes back on with the lock screen up and then having to turn the screen back off? annoying
try the swapper app?
or turn phone off and back on, it might becuase you are usingahome or openhome or dxtop or sweeterhome, these app may slow down the interface a bit, try downloading droid sans tweak lite and fool around with that..
goodluck i also get this sometimes
brooklynite said:
Mine recently started this, it must be something we downloaded, plus I have the following problems too, they all started at the same time:
1) When someone calls, the screen stay blank for a while so the phone rings but the screen is off so I dont see whos calling
2) The background keeps changing back to the original blue picture thing
3) The WiFi keeps turning off and drians the battery, nothing I do stops it from turning on. I have all sorts of software running, I even ask Locale to turn it off if its between 12.01am to 11pm and still WiFi keeps poping up.
4) Battery drains FAST lately.
I uninstalled a long list of software and problem is not solved.
Brooklynite!
Click to expand...
Click to collapse
I'm having same issue as the OP and issued #1, 3 and 4 from the above post.
Hmm, im not experiencing any of the above posted issues, it may be a particular app that u have installed. I only have the wakeup issue sometimes, most likely when the phone is running slow from the browser or another memory draining app, but no app in particular.
Hmm, when mine fails to wake up, I never waited long enough for it to come back, just reseated the battery for a reboot.
Of the other problems, I have the "screen-black-for-a-few-before-caller-picture-shows-up" issue.
JayBachatero said:
I'm having same issue as the OP and issued #1, 3 and 4 from the above post.
Click to expand...
Click to collapse
what firmware do you have?
btw, dont count on Locale to turn off your stuff all the time, its not very accurate imo, at times its great, but thanks to the crappy g1 battery, they have a choice, constantly check time/location/.ect and drain the battery in a hour flat, or periodically check it and reduce battery drain, do you have any wifi programs that keep wifi on when phone sleeps (such as wifi lock and so on)? if so use the program on the market that writes up a log of its actions and see if its acting up
as for #1 (sorry im unorganized) my phone does that too, i believe its because i have 2 programs that run when the phone rings, let alone im sure locale is checking to see who is coming since thats a condition, which would make 3, and then i have a mp3 that plays when the phone rings, and i have a class 4 sd card (i know, i know), the way that programs work is that it has to go line by line of the code, if it is slowed down, or it has to execute other items before continuing that are slow to execute, than everything has a delay, but yeah from time to time i have this issue, phoneplus was a program that made me miss a few calls (1/4th of the time)
i think 3 and 4 are directly related, could be wrong
I was having the same problem right after I installed the app "Contact Owner"
No amount of reboots fixed the problem. Uninstalled and everything was back to normal.
@wootroot - I have stock RC30. Haven't rooted yet.
JayBachatero said:
@wootroot - I have stock RC30. Haven't rooted yet.
Click to expand...
Click to collapse
consider upgrading to the rc33 ota update yet? i had better battery life (and my battery didnt get as hot) when i used rc33
also, if youve had your phone since it first came out (rc19 i believe) and your battery used to get very hot, you might of damaged some of the cells (especially of the battery has expanded), if this is the case simply call tmobile and tell them that your noticing even after wiping the phone that your battery life is lasting shorter and shorted, even with out any programs installed from the market, i even went as far as to say that i made sure wifi was off, only 2g was on, gps was off, screen was dimmed, timeout set at 30 secs, and im still only getting a hour of life (none of which is true but it got through all the "well how about trying this and calling back if you still have a problem" bs, with the ota rc33 and the new battery, i noticed a pretty good difference
I have a modified version of this "doesnt always wake up". The phone is less than 24 hours old, it was a refurb they sent me for the last one that went dead. I used it with the rc33 it came with and found the problem, then figured it was hosed so i rooted and installed 3 of the versions of cupcake (The Dude, JF, and Haykuro) to see if they all had the issue- they do. Here is a video, hope you can see the attempted keypresses. There will be lines that appear, like the screen is broke..then, they will go away. Sometimes it takes 5 minutes to get the phone to turn on, however if I leave it on (never goes to sleep) it works flawlessly.
http://www.youtube.com/watch?v=ecQo2Ly2WUM
I get this all the time also...
Uninstalling dxTop doesn't change anything for me...it still acts the same...
I also get the problem that when someone calls me the screen stays blank for about 5 seconds and I can't tell who calling...
wake up issue
I am experiencing the same problem, with a brand new warranty replaced G1, what happens is when the phone goes to sleep it completely locks up, when I try to wake it up via menu, it does not wake. Plugging the phone in and trying ddms or adb does not work, ddms shows the phone as offline, also the device seems to get really hot when this happens, sometimes Call + Menu + Power resets it, and sometimes I have to pull the battery.
I think this may have to do with wifi turned on. Because when the screen goes off your phone switches wifi off and goes to 3G as default setting.
I think we should try leaving wifi on all the time and see if that solves the issue, im about to try that now.
It seems this is a known issue over at tmo forums
A couple questions:
When this happens to you guys is wifi enabled and connected when the phone is shut off?
What Rom, SPL, and Radio is installed?
I noticed this didnt happen to me until I enabled wifi, maybe I didnt wait long enough because its completely random, please send back your results
defcon
Hi Guys,
I'm new here, but have been following and reading these forums for quite some time now. Great Stuff!
anyhow, my problem, recently purchased a HTC P3600i PRO. Put a custom ROM on it, seemed to be running great over the last few weeks, but my problem is this. Now and then my phone pda will lock up and I'm forced to reset it. What happens is, I am still unsure as to why this happens, but lately it's started freezing up, and when I click on my start button, it shows my menu, and then when I click programs, it shows as "empty" when I know there's nothing empty, it's filled with stuff, randomly this happens to my settings window as well. Basically stuff randomly dissapears from my start menu, shortly after, 5 to 10 seconds, it locks up. The next thing I do or click on after seeing things disappearing from my menu, it freezes. I then have to do a soft reset, and after doing a soft reset, it's as if it's done a hard reset and wants me to re-configure the time, click on all 4 corners, etc.. I use have to use SPB Backup to do a full restore of my phone/settings/contacts/software etc..
Can anyone help?
Also, just to update.. I restored my phone with a backup today, and it seems to be running well again for some strange reason. Is it because it's overheating? getting hot or what? I'm not sure what it's doing. Please help
Figured it out
My backlight whilst on battery was set to brightest. figured it was overheating as it felt warm too.. I turned it right down to 3 bars from lowest, and it's fine now
Guess it my screen and battery were getting quite hot and the CPU was overheating. All resolved.
I got a HTC p3600 for about 10 months. i used to have the backlight set to minimum.
now i update my rom and it got crashes so often, almost every day, and I need soft restart the device all the time when get crash.
The worse, sometime my display picture just broken + crash, and I need more than once to restart the pda. When I restart the device sometime the display just turn black color moving from top to bottom, or sometime with colourfull dots on screen, and the device does not want to be restart.
In that case i take the battery to turn off the device.
Sometimes i need to wait some minutes until i can restart normally the system.
It usually crashes when it is connected to the computer via usb (charging the battery) and i need to use it. (i check and it is very hot)
Also, when i use wifi it tends to crash (very hot too)
Since i upgrade the rom my backlight settings are set higher...i reduce the backlight, to reduce heat and test the system stability, but i really think it is crashing due to overheating.
My wife has a completely stock Droid X and she always has the weirdest issues with her phone with it locking up, freezing or hanging up..
Sometimes the phone recovers, other times it needs to be rebooted manually.
Is this a known issue with this phone?? I have the HTC incredible and have no issues like this.
I havent had a problem or heard of this. Is she under warranty and get it swapped out? If not has she tried to do a wipe/factory reset? While off hold the power and menu key at the same time. A screen will come up. press the search button. Use the volume keys to scroll up and down. Go to wipe/factory reset and press the camera button.
My wife has a stock D2, and it sometimes likes to open up the voice search, or she will be typing a text message, and the g key will open the browser to google.com, or just randomly freeze up..... Maybe women have a different body chemistry that acts like a mini EMP that just destroys all electronics.... Everything electronic she has ever owned has major problems, yet mine last years........
Droid X freezing - having to battery pull.
I've been having similar issues with my Droid X. It will randomly, and often, lock up for a while, then come back to life usually. It's really annoying if your browsing the web and all the sudden the phone freezes for 20-30 seconds.
When it freezes completely, it will just freeze and the screen will remain on. I have to then pull off my protective cover and battery pull to reboot.
Battery pulls happen about once every 2-3 days. Freezes that recover are happening 5 or 6 times a day if not more.
The brief time I had the phone on stock, the issue was occuring. I ignored it and figured surely this won't happen after I root it. I'm now running latest Liberty ROM and it's still happening. Problem definately gets worse if I overclock. I'm wondering if the CPU can't even handle 1000 Mhz and needs to be underclocked just so this thing can run stable.
I'm going to test that out and see if the weird freezing and force closes go away. But it will suck loosing speed.
I unfortunately can't return my phone as I bought it used on Craigslist.
buckweet said:
My wife has a completely stock Droid X and she always has the weirdest issues with her phone with it locking up, freezing or hanging up..
Sometimes the phone recovers, other times it needs to be rebooted manually.
Is this a known issue with this phone?? I have the HTC incredible and have no issues like this.
Click to expand...
Click to collapse
Its likely due to the fact that the stock Droid x firmware sucks a load of ass. The factory blur is perhaps the biggest waste of time I've ever seen. I've had both my dinc and fascinate and x since launch day and the only remedy I've found to stop the x from doing this is flash livery. Only way to fix it at all.
Sent from my DROIDX using XDA App
Yeah man sounds like you have a bad device. If a data wipe/reset wont do it you must have a have bad device . Go back where you got it and ask for an exchange
Sent from my DROIDX using XDA App
deitiphobia said:
I've been having similar issues with my Droid X. It will randomly, and often, lock up for a while, then come back to life usually. It's really annoying if your browsing the web and all the sudden the phone freezes for 20-30 seconds.
When it freezes completely, it will just freeze and the screen will remain on. I have to then pull off my protective cover and battery pull to reboot.
Battery pulls happen about once every 2-3 days. Freezes that recover are happening 5 or 6 times a day if not more.
The brief time I had the phone on stock, the issue was occuring. I ignored it and figured surely this won't happen after I root it. I'm now running latest Liberty ROM and it's still happening. Problem definately gets worse if I overclock. I'm wondering if the CPU can't even handle 1000 Mhz and needs to be underclocked just so this thing can run stable.
I'm going to test that out and see if the weird freezing and force closes go away. But it will suck loosing speed.
I unfortunately can't return my phone as I bought it used on Craigslist.
Click to expand...
Click to collapse
Before reading all of this....note that this is just me providing a POTENTIAL explanation of why some people's phones seem to reboot more than others... this is not a generalization for all... It may not apply to you...
I think that random reboots (especially often) are related to potentially bad hardware, not being on the 2.3.34 OTA update...or user error (don't get mad, please let me explain this part!). I found that after moving off of 2.3.15 OTA that my phone was much more stable.
I notice from back when I first had my Droid X that I went crazy loading up lots of apps, and throwing widgets all over my home screens... I had custom themes flashed and lots of other stuff. While yes, blur does suck up more system resources than custom ROM's without it... you can run a phone with Blur without constant reboots.
The more apps that you have on the phone (even if not running) eat up resources. Along with that, the more widgets or notifications you have on your homescreens, the more resources that the phone is chewing through... With that said, you can SEEM to not be running anything on the phone, but the widgets in the background process' can be using up precious memory that cause the phone to lag or reboot.
Like I said at the beginning, if you don't have a lot of extra widgets and programs loaded, then yes, I would say that really sucks that your phone reboots. Moto's way of handling a resource issue (in most cases RAM)... is to reboot the phone to clear memory.
If you happen to have a lot loaded on your phone...try not to use a lot of widgets, and cut back on some un-needed apps... See if the phone reboots as often. Again, this is not me blaming anyone for their phone rebooting, simply my understanding of technology from personal experience.
First off, I'm on PA 3.1 and faux 3.4.
Just like the title says, the screen becomes unresponsive and the only way to fix it is to do a reboot through long press of the power button, I'd have to sit there and wait for the phone to reboot, it enters the lock screen, and immediately slide to unlock, then everything works fine afaik.
So the problem happens when I reboot the phone, and it enters the lock screen, I don't touch it and the screen turns off. I come back to the phone, pressing the power button wakes it, but the screen is never responsive.
Anyone experienced anything like this?
Could it be PA includes the touchscreen fix? AFAIK the touchscreen fix requires ~30 seconds to install after a fresh boot.
Plus there's no telling what he's modded or edited too. The Op never specified what he has done.
I had this same problem when I updated to the latest pa and flashed acid audio mod one after the other. The problem was the acid mod, the problem was gone after I deleted it.
Sent from my Nexus 4 using Tapatalk 2
I've never heard of acid audio mode, couldn't find it in titanium backup...
Have you flashed anything else other than the rom and the faux kernel? if not, Try flashing stock kernel see if that make a difference.
AftermatH101 said:
First off, I'm on PA 3.1 and faux 3.4.
Just like the title says, the screen becomes unresponsive and the only way to fix it is to do a reboot through long press of the power button, I'd have to sit there and wait for the phone to reboot, it enters the lock screen, and immediately slide to unlock, then everything works fine afaik.
So the problem happens when I reboot the phone, and it enters the lock screen, I don't touch it and the screen turns off. I come back to the phone, pressing the power button wakes it, but the screen is never responsive.
Anyone experienced anything like this?
Click to expand...
Click to collapse
Are you modifying your voltages by any chance? If your voltage is too low then your phone will become unstable. I can imagine a scenario where immediately upon start up, your phone is running at high clock speeds, and the voltages for that are just fine; but then when it goes into idle mode, the voltage for the lowest frequency step might be too low and therefore causes instability. Pressing the power button creates a demand that suddenly chokes the processor, and bam, unresponsive screen. Otherwise, it might be some startup scripts causing issues, and you should double check those (but I have no experience with startup scripts).
amartolos said:
Are you modifying your voltages by any chance? If your voltage is too low then your phone will become unstable. I can imagine a scenario where immediately upon start up, your phone is running at high clock speeds, and the voltages for that are just fine; but then when it goes into idle mode, the voltage for the lowest frequency step might be too low and therefore causes instability. Pressing the power button creates a demand that suddenly chokes the processor, and bam, unresponsive screen. Otherwise, it might be some startup scripts causing issues, and you should double check those (but I have no experience with startup scripts).
Click to expand...
Click to collapse
I don't understand how it only happens at that time... but not the hundreds of other times when I unlock the phone from idle mode.
I have the same problem. I used PA versions with FrancoKernels ( from 111 to 122 ) and i had no issues, Then i jumped to the Faux kernel cause i was reading about exreme battery stats. I used the recomended settings from his post via his app. And i UV to -100mv and i used the setting that let you wake it via touch , SleeptoWake. Still havent cleared what is it. Now i play with some settings. With -87.5mv i managed to reboot it and respond.
The one thing that i want to mention is its randomness. It happens only in reboots - turn on and not every time. I guess the problem its in my settings/Uv maybe .Respect to all developers
Waiting for others who have face it.
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.