Happens on every rom (currently on a cm10 nightly) ... phone is stable in just about every other way, but 1/50 (guessing) the unlock just goes sour.
It's as if the screen doesn't come on....
I tried raising my min cpu freq while sleeping- even at 512mhz it still did this occasionally.
Any thoughts?
pcguru000 said:
Happens on every rom (currently on a cm10 nightly) ... phone is stable in just about every other way, but 1/50 (guessing) the unlock just goes sour.
It's as if the screen doesn't come on....
I tried raising my min cpu freq while sleeping- even at 512mhz it still did this occasionally.
Any thoughts?
Click to expand...
Click to collapse
I've had this problem for quite some time as well, and I've read about it in the forums before. I believe that and the reboot in the camera app (try unlocking) are the two biggest issues right now. From what I've read in the android development forums these are likely kernel issues that won't be solved easily.
pcguru000 said:
Happens on every rom (currently on a cm10 nightly) ... phone is stable in just about every other way, but 1/50 (guessing) the unlock just goes sour.
It's as if the screen doesn't come on....
I tried raising my min cpu freq while sleeping- even at 512mhz it still did this occasionally.
Any thoughts?
Click to expand...
Click to collapse
CM10 has been notorious for this since day one. I haven't used a CM10 nightly in about 2 months, but I had quite a few BSOD's in ParanoidAndroid. I've been using tdmcode's AOKP41 for the past few days and so far I haven't had a BSOD, but from what I read in his thread in the development section I'm lucky.
One thing that makes it "less" of a hassle is that you can hold the power button until it reboots (around 10 seconds, maybe 15 or so) instead of pulling the battery.
Related
Hey there every one. When I am unlocking my phone I notice that it will flash the lock screen and then disappear and then immediately re appear. When you try to lock the phone sometimes it wont lock and the buttons will stay lit and will display the lock screen but the display wont sleep unless it times out.
This happens on all ROM's that I flash except CyanogenMod
I used both of the over clock methods but the results are the same.
Please Advise
macfan74318
macfan74318 said:
Hey there every one. When I am unlocking my phone I notice that it will flash the lock screen and then disappear and then immediately re appear. When you try to lock the phone sometimes it wont lock and the buttons will stay lit and will display the lock screen but the display wont sleep unless it times out.
This happens on all ROM's that I flash except CyanogenMod
I used both of the over clock methods but the results are the same.
Please Advise
macfan74318
Click to expand...
Click to collapse
Yeah, it sucks. Theres no real way around this but disabling the lock screen helps it from happening less frequently. But then you end up draining the battery & others by the screen coming on easily by trackpad, volume keys, and power button. Its a lose/lose situation really...
sino8r said:
Yeah, it sucks. Theres no real way around this but disabling the lock screen helps it from happening less frequently. But then you end up draining the battery & others by the screen coming on easily by trackpad, volume keys, and power button. Its a lose/lose situation really...
Click to expand...
Click to collapse
I bumped my minimum clock speed to 368 MHz, and I don't have this problem anymore. YMMV
seancneal said:
I bumped my minimum clock speed to 368 MHz, and I don't have this problem anymore. YMMV
Click to expand...
Click to collapse
Still happens to me when I try that. It occurs when you press the power button twice in succession.
Hi there,
anything new on this topic? I'm currently experiencing this annoying problem as described.
I've already tried to set the minimum clock to 368 Mhz but the bug still exists. Even setting CPU to standard clock (Max/Min @800) didn't solve the problem.
Is it possible that the reason is located already inside the overclocking kernel?
Greets
dktnecro
Generally if you're overclocking and you have lockscreen issues that are not present @ stock speeds, then it sounds to me like the overclock is too much and your system probably isn't stable.
Based on my experience overclocking computers, things can very well appear stable but if you do stress testing (8+ hours straight) things often crop up and show you that it is in fact not stable. This sounds like one of those things. And that's not good. Who knows what other corruption could occur during your use at that speed? I had the same lockscreen issues myself, and once I realized it was due to overclocking too much I ended up solving another issue I had where half of the calls I received were garbled to the person on the other end. No more lockscreen issues or garbled calls since backing off the o/c a bit.
If the issue doesn't happen at stock speeds then maybe it's just the kernel, and hopefully that isn't putting you at risk of any kind of corruption, either.
Keep in mind I really can't be 100% if overclocking will cause corruption on a phone, but based on a lot of time spend overclocking pc's I would have to guess that it can. I'm surprised that this isn't brought up more often on device forums.
I love cyanogenmod for many reasons, but everytime I try, one thing kills me.
It I hit the power button when the screen is off, it often takes 5 or 6 seconds to turn on. Has anyone else had this problem and solved it?
Mind you, this has happened under many versions of CM (but on 6.1 right now) with different kernels and sometimes having setcpu profiles.
Any ideas?
Thanks in advance.
newsoundwave said:
I love cyanogenmod for many reasons, but everytime I try, one thing kills me.
It I hit the power button when the screen is off, it often takes 5 or 6 seconds to turn on. Has anyone else had this problem and solved it?
Mind you, this has happened under many versions of CM (but on 6.1 right now) with different kernels and sometimes having setcpu profiles.
Any ideas?
Thanks in advance.
Click to expand...
Click to collapse
it normally has something to do with setcpu being clocked to low, try raising the min freq up to 245mhz
Actually, set the SetCPU minimum frequency to 384 MHz. That usually solves problems like this, or with the screen not turning on for a call, whereas 245 doesn't always.
Is anybody else having issues with their ET going to sleep and you have to pull the battery to get it come back up? I thought it might have been my setcpu settings. So I cleared them and uninstalled it. I tried the midnight rom and the starburst rom. I tried the stable and exp LosKernel. None of these got rid of this issue for me. Randomly through out the day I can try to wake the phone up to use it and nothing happens. After a minute or two I have to pull the battery. I am currently testing the stock kernel.
Thats weird, the only time that happened to me was when i had setcpu, and i tried putting "screen off" value to 200/200.
You should install setcpu again, and make screen off value 500/500, and if you dont have the issue, then try making the value 200/500, if you dont have the issue at this value, then leave it as is.
Sent from my SPH-D710 using xda premium
I agree it is weird and I am not sure why it is happening. If it stays okay with the stock kernel then I may wipe and try the viperrom.
Yep happened twice the other day... Im on stock rom with lost kernel..roooted i put setcpu to 200/1200 after waking my screen for a minute used google came back 3 min later and phone was either off or wouldnt wake .. I had to pull battery twice.
I setcpu up to 1200/1200 never happened again.
This is a nice phone but very touchy.. Seems alot weird things goin on for some Et users.
Worst of all for this phone is Los or just weak /radio signal in general ..which is a samsung issue.
Sent from my SPH-D710 using XDA Premium App
Why people still insist on screen off profiles amazes me. When you hit the power button to wake it - the phone is stuck at 200MHz, you do realize this? If snything else is going on while it's stuck at 200 or SetCPU doesn't sample the phones state fast enough, it never gets out of 200MHz and locks up. Just like any other processor does when you overload it.
All the background processes going on even when the screen is off and somebody thinks setting the CPU max to 200MHz is a good idea? That's just asking for it. Not to mention the screen off profile is known to cause this issue. Notice how Virtuous, Viper, Cyanogen, and many other developers don't use one in their native OC daemons? There's a reason why. The phone sleeps just fine without it, just let it do it's thing.
Don't use offscreen profiles (the kernel is smart enough) and avoid using task killers, as those are likely to be the second leading issue.
I am having the issue even with setcpu uninstalled. I still have not found out what is causing it.
ElAguila said:
I am having the issue even with setcpu uninstalled. I still have not found out what is causing it.
Click to expand...
Click to collapse
Just wanted to throw this out there: beware mislabeling this problem. The setcpu issue causing the phone the permanently lock up and require a bat pull is one issue, yes; slow screen wake up is a different issue. Sometimes if you hit the power button, the screen will not wake up on the first try. If you wait a few seconds and push in the button again for a second or so, the screen almost always will come after. Coming from a mo-pho, I actually had the stupid no-wake problem requiring bat pulls, so I'm extremely paranoid about by e4gt doing this -- but it really has been good about eventually waking up every single time...just try my instructions and see if it works for you, too.
Again, though -- setcpu issues may be a different problem entirely.
did you reinstall a rom and try it again or did you simply just unistall setcpu and try it. I say this because I had an issue when testing setcpu and my system still kept my cpu setting even after I unistalled the app. I had to reinstall the rom after wiping to get it to run properly again.
I think I have found the issue. I did a factory reset and installed the rom but I am getting an error now that is basically saying it can't read the internal storage card. So I think there are some actual hardware issues going on that need to be looked at by sprint.
how often has the sod been happening? I think i got it yesterday, but not sure.
Do you use setcpu?
Sent from my SPH-D710 using Tapatalk
This thread seems a little slow- has there been a solution found or are we isolated cases?
I reflashed the phone back to rooted stock and then flashed Blazer 4.1.
Got 2 SODs in the past week- one just a few minutes ago.
I tried calling the phone from another line, it rings but the screen is black and thus I couldn't answer it.
Power button and vol buttons work fine.
I had to powerdown and reboot.
Getting kinda frustating.
So I was streaming music from MOG and all was working well until my screen went off (idle). Music started to pause/buffer and kept doing so every 10 seconds. When I turn the screen back on and stare at it, it won't do it at all and I can see it load full on the seek bar. Only happens when screen goes off and phone goes idle. I'm guessing its something with the CPU throttling maybe? Is there any way I can fix this? I'm connected on WiFi 5G and I have "keep WiFi on during sleep - Always".
This seems to be a pretty common issue (I have it myself, when connecting via WiFi with adb I need to keep my display on) and I've seen two issues on file here and here. I've yet to see a fix for it yet though
Aww crap. Well that sucks. Does it happen on custom roms/kernels?
reyes.jr said:
Aww crap. Well that sucks. Does it happen on custom roms/kernels?
Click to expand...
Click to collapse
I'm running CM9 nightly with leankernel now. Although it's happened since I've gotten the phone, and I've ran probably half a dozen different ROMs and 3 different kernels, including stock. I vaguely remember reading some posts where people either said there was a fix or they were working on it, though I'm honestly not real sure.
K thanks for the info bro.
reyes.jr said:
So I was streaming music from MOG and all was working well until my screen went off (idle). Music started to pause/buffer and kept doing so every 10 seconds. When I turn the screen back on and stare at it, it won't do it at all and I can see it load full on the seek bar. Only happens when screen goes off and phone goes idle. I'm guessing its something with the CPU throttling maybe? Is there any way I can fix this? I'm connected on WiFi 5G and I have "keep WiFi on during sleep - Always".
Click to expand...
Click to collapse
I am also facing the same issue. Yesterday, I was downloading ARHD 3.0 directly on phone through wi-fi. Surprisingly the progress was 1% completion per minute in screen-off mode. But the moment, I would turn on the screen, the rate became 3-4 times faster. i.e. 3-4% completion per minute.
Deviating from topic, I have seen similar behaviour quite some time back in iPad1.
kizuki.buy said:
I am also facing the same issue. Yesterday, I was downloading ARHD 3.0 directly on phone through wi-fi. Surprisingly the progress was 1% completion per minute in screen-off mode. But the moment, I would turn on the screen, the rate became 3-4 times faster. i.e. 3-4% completion per minute.
Deviating from topic, I have seen similar behaviour quite some time back in iPad1.
Click to expand...
Click to collapse
Well glad to know I'm not in the same boat. Have any of u tried android 4.0.4?
reyes.jr said:
Well glad to know I'm not in the same boat. Have any of u tried android 4.0.4?
Click to expand...
Click to collapse
Yeah, I'm on Liquid 1.25 (4.0.4 based ROM) and it still does it. If I run a speed test and turn the screen off, let it finish and check it; it will never go much over 5 Mbit/s. When I run the test with the screen on, I will get 10-20 Mbit/s. This was of course testing on my home WiFi network.
This is pretty annoying because I download anime torrents every week and it's enough of a battery killer already just to download the thing, but now I have to leave the screen on in order for it to even finish in a reasonable amount of time. I've also tried setting the minimum clock speed to 1200 MHz in SetCPU just to see if it was a CPU throttling/bottleneck issue when the screen turns off. But it made no difference . This can't be a hard fix for Google/Devs.
At least with popcorn and franco kernels you can do
echo 1 > /sys/module/bcmdhd/parameters/wifi_pm
to put wifi on high performance mode with screen off. They say this can enable high throughput.
reyes.jr said:
Well glad to know I'm not in the same boat. Have any of u tried android 4.0.4?
Click to expand...
Click to collapse
Yes, I am using ARHD 3.0 which is based on 4.0.4
There seem to be definite improvements and it was worth the effort to update.
As far as I know, wifi goes into a low power state with screen off to conserve power/battery life.
My command put it in normal power mode, but kernel must support it
KiNG OMaR said:
As far as I know, wifi goes into a low power state with screen off to conserve power/battery life.
Click to expand...
Click to collapse
oooo, so only on WiFi does this occur? On 4g it doesn't?
This also happen to me.. Happened in 4.0.1 4.0.2 4.0.4 so far I managed to bypass the issue with wifi keep alive its a free app from play store.. You could try and comment if that works for you
Sent from my Galaxy Nexus using xda premium
Threre is no need for any custom kernel module. Im on Stock ICS 4.04 and found an easy workaround. Actually this issue is not an android bug, but an issue of streaming apps that aren't proberly coded for honeycomb and ICS.
Okay does any one have this same problem or am i just doing something wrong?
Every time i let my kindle sit with the screen off after about 30 minutes or so, and I assume it keeps going and getting stuck in sleep mode but the only way for me to get it turned back on is to do the whole power button for 20 seconds and then reboot. Am I not being patient enough with it or is there some trick to getting the screen back on that i haven't found yet? Because I've tried multiple different things and there isn't a disable sleep mode option in my rom just the option to extend the time, even though its pretty much useless. But can anyone help me with this?
what rom are you on?
Right now I'm on Hell Fire 1.1 but last week i was running CM9 Reloaded and it did the same exact thing.
I was going to give a long speech about how people need to READ before installing any new roms but considering the Hellfire thread doesn't list what works and what doesn't, I guess it's not entirely your fault
It's called "sleep of death" (SOD). Some ICS roms have problems with it and some don't. The same could be said about certain individual devices. You could boost your minimum CPU usage to 600Mhz or more, or try a different rom. Though, it should be noted that changing your CPU settings will affect battery life.
okay that makes sense i had no idea that most of the new roms have problems with it. but I'll probably try to up the min cpu usage i suppose the difference between 600 MHz and 300 MHz isn't going to be a true killer for the amount i use it but which rom or roms would you recommend? That don't have this problem I'd really like to try barebones but every time i try to flash it my Kindle goes crazy so i gave up on trying with it.