I have installed CM 10.1. Occasionally the screen will not turn on when I press the power button. I have to hold down the button for 10-20 seconds to reset the device to get it to power on. Happens at least 3-4 times a day. Anyone else have this issue or ideas on how to fix it? Thanks.
Stuke00 said:
I have installed CM 10.1. Occasionally the screen will not turn on when I press the power button. I have to hold down the button for 10-20 seconds to reset the device to get it to power on. Happens at least 3-4 times a day. Anyone else have this issue or ideas on how to fix it? Thanks.
Click to expand...
Click to collapse
No one else has seen this issue?
Many ROMs have their little quirks here and there, this could be one. I use hashcode's ROMs so this is just speculation though.
I had this issue with twa_priv's rom. If I keep at the button, pushing it multiple times at different intervals, it would eventually come on. Interestingly, if I went into the developer options and put the CPU at the full 1200MHz, it didn't happen.
Not having this issue with CM (though I'm running 10.2) so not sure there.
This was a common occurrence in cm10.1 with TWA_priv's build I believe. This is called a Sleep of Death or SoD. I thought that was cleared up, but maybe not. If there is a newer version of the ROM that you are on, I recommend trying that. There is no way to recover from an SoD except to force power off like you did, and start back up.
Sent from my Nexus 7 using Tapatalk
Related
I have had my Htc Evo rooted for a long time now. This problem recently just started and I'm not sure if it's because my phone is rooted or maybe it's just an electrical or hardware problem. The top right button to lock the phone or to wake it up from sleep doesn't register all the time. I sometimes have to push it several times for it to work. Do you think I should restore my phone? Maybe it's because it's rooted? Something got corrupted? I'm leaning more towards hardware problems..
Any ideas?
Thanks!
steveojp said:
I have had my Htc Evo rooted for a long time now. This problem recently just started and I'm not sure if it's because my phone is rooted or maybe it's just an electrical or hardware problem. The top right button to lock the phone or to wake it up from sleep doesn't register all the time. I sometimes have to push it several times for it to work. Do you think I should restore my phone? Maybe it's because it's rooted? Something got corrupted? I'm leaning more towards hardware problems..
Any ideas?
Thanks!
Click to expand...
Click to collapse
Are you just having trouble waking the phone up with the power button, or is it all functions of the power button are acting weird? Does it put the phone to sleep fine? I've had it happen a few times, where the phone wouldn't wake up by pushing that button. That was attributed to the ROM i was using at the time, and also having the min clock setting at 128.
If your case is different, and the button isn't working properly for all of it's functiopns, and not just waking up the phone, it could be a hardware issue, or the button mechanism could be hanging up or something.
k2buckley said:
Are you just having trouble waking the phone up with the power button, or is it all functions of the power button are acting weird? Does it put the phone to sleep fine? I've had it happen a few times, where the phone wouldn't wake up by pushing that button. That was attributed to the ROM i was using at the time, and also having the min clock setting at 128.
If your case is different, and the button isn't working properly for all of it's functiopns, and not just waking up the phone, it could be a hardware issue, or the button mechanism could be hanging up or something.
Click to expand...
Click to collapse
All the functions of the power button is acting weird..sometimes I have to push the button like 10 times for it to wake up so I can unlock my phone. Sometimes I have to push it 5 times or more to turn it off. It's weird though how this randomly started doing this. I was hoping it was the Rom. I'm running Fresh I've never had any problems with it. That's why I leaned more towards the hardware. Is there any way to go around pushing the power button to wake up the phone? Do you think I should restore my phone to see if it maybe fixes the problem?
Thanks!
steveojp said:
All the functions of the power button is acting weird..sometimes I have to push the button like 10 times for it to wake up so I can unlock my phone. Sometimes I have to push it 5 times or more to turn it off. It's weird though how this randomly started doing this. I was hoping it was the Rom. I'm running Fresh I've never had any problems with it. That's why I leaned more towards the hardware. Is there any way to go around pushing the power button to wake up the phone? Do you think I should restore my phone to see if it maybe fixes the problem?
Thanks!
Click to expand...
Click to collapse
If it was me, I would make a nand backup of your current setup, and then try flashing a different rom, and seeing if the problem persists. If it continues, I'd then unroot and return to stock setup. If it happens on stock setup, I'd then take it to Sprint to have it looked at.
Sent from my PC36100 using XDA App
k2buckley said:
If it was me, I would make a nand backup of your current setup, and then try flashing a different rom, and seeing if the problem persists. If it continues, I'd then unroot and return to stock setup. If it happens on stock setup, I'd then take it to Sprint to have it looked at.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Alright, I'll do that. Thanks
bump for update from OP
Power BUtton Problems with Waking etc.
Not sure if you ever resolved your issue, but I have the EVO 3D, NOT rooted but with the latest updates, and ever since the last OTA update that moved me to software level 2.08.651.2, I have had issues with the phone not waking on an inbound call until I hit the power button and then wait about 8 seconds for the screen to come on. I have Factory Restored it 3 times, which seems to fix the problem temporarily, but it always comes back.
I just did a warranty replacement claim to see if that will finally resolve the issue. I even found a post where someone said the stock batteries are somewhat loose, so I took a business card and taped it to the bottom of the battery, opposite of the charging posts so that the fit would be better, still no luck.
steveojp said:
Alright, I'll do that. Thanks
Click to expand...
Click to collapse
Hi, new here but I've been lurking for a while.
I followed Powerpoint's guide to instal CM10 on my KF2
http://forum.xda-developers.com/showthread.php?t=2105077
Everything was running great and has been since I first loaded version 3 a few weeks ago, and last week i went to version 4 of powerpoint's rom with no problems. Then a couple days ago after i had been browsing the internet on it for maybe 30 minutes, I set it down and when i came back the screen was off and wouldn't turn back on. so i figured the battery was just dead, so i plugged it in to the wall charger. At first the charge/power light wouldn't come on at all. Then after several plugs and unplugs the orange light started to come on but would only stay illuminated for 30 seconds-ish. So I tried it on my phone charger and the orange light came on and stayed on, so i decided to let it charge overnight. The next morning the light was still glowing orange so I unplugged it and tried turning it on, but still nothing happens. But when I plugged it back in afterwards the light came on green. now it has been plugged in for almost a day with the green light on but it still wont turn on.
Anyone else have this problem? Any ideas what i can try? for obvious reasons i can't exactly ship it back to amazon lol
p.s. I have a final on friday and the text book for that class is on the kindle. So urgent responses will be greatly appreciated.
Nevermind guys, I figured it out. Power button for 20 and it booted right up
Sent from my EVO using xda app-developers app
docnougat said:
Nevermind guys, I figured it out. Power button for 20 and it booted right up
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I've had this a couple of times on both 10.1 ROMs. As you stated the only way I got it working was to hold the power button for 20 secs, then power on normally.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
It just happened to me again, seems to be a recurring problem. Anyone have a clue what's causing this?
on a side note, perhaps this problem could be dealt with simply by installing a battery management app like juicedeffender. any thoughts?
docnougat said:
It just happened to me again, seems to be a recurring problem. Anyone have a clue what's causing this?
on a side note, perhaps this problem could be dealt with simply by installing a battery management app like juicedeffender. any thoughts?
Click to expand...
Click to collapse
Wow, for once I can completely and knowledgeably help with almost no guess work!
The issue is Sleep of Death.
The cause is unknown, and due to the nature of how to reset it, it's been difficult to get logs. It happened to FMK not too long ago and last I heard he was going to get the logs (to find what causes this) and get those to Hashcode to look at potential fixes.
It's not battery related....well in the sense that, if it happened, you reset the device, and looked at the battery, it should be at a similar level to what it was before.
TO FIX
You guys were right on fixing it mostly.
If you ever press power a few times and it won't turn it, don't bother fretting about it. Just do the hard reset, which is holding the button down for 10 seconds. After you do that the device will reset to the point where if you just press the power button once, it will boot up like normal.
I would hold it down for about 15 seconds just in case, or if you have headphones it, you can here when it does the reset and can get used to the timing.
I would say....in a few weeks with the device, I've had the issue around 5-6 times.
I've also NEVER had it happen while I'm doing things, so it hasn't caused issues besides making me a wait a bit before using the device, which is good. If it happened during doing things I would want this fixed ASAP, but so far, no major issues.
agreed, if it was happening while i was trying to do stuff it would be problem. As it is though, I just consider it a minor inconvenience. Glad to know I'm not the only one experiencing this though.
iytrix said:
Wow, for once I can completely and knowledgeably help with almost no guess work!
The issue is Sleep of Death.
The cause is unknown, and due to the nature of how to reset it, it's been difficult to get logs. It happened to FMK not too long ago and last I heard he was going to get the logs (to find what causes this) and get those to Hashcode to look at potential fixes.
It's not battery related....well in the sense that, if it happened, you reset the device, and looked at the battery, it should be at a similar level to what it was before.
TO FIX
You guys were right on fixing it mostly.
If you ever press power a few times and it won't turn it, don't bother fretting about it. Just do the hard reset, which is holding the button down for 10 seconds. After you do that the device will reset to the point where if you just press the power button once, it will boot up like normal.
I would hold it down for about 15 seconds just in case, or if you have headphones it, you can here when it does the reset and can get used to the timing.
I would say....in a few weeks with the device, I've had the issue around 5-6 times.
I've also NEVER had it happen while I'm doing things, so it hasn't caused issues besides making me a wait a bit before using the device, which is good. If it happened during doing things I would want this fixed ASAP, but so far, no major issues.
Click to expand...
Click to collapse
I wouldn't call it a fix. I would call that a workaround. We need a fix, and I think if anyone could get an effing log to hashcode of it happening, we could fix the problem. I think it is a kernel problem, what with the recent merges and such. I think something is incorrectly copying from kf1 to kf2... if anyone understands what I'm trying to say, it makes sense..
fmkilo said:
I wouldn't call it a fix. I would call that a workaround. We need a fix, and I think if anyone could get an effing log to hashcode of it happening, we could fix the problem. I think it is a kernel problem, what with the recent merges and such. I think something is incorrectly copying from kf1 to kf2... if anyone understands what I'm trying to say, it makes sense..
Click to expand...
Click to collapse
I wonder if pulling the log cat via adb would work, I.e. wait till it goes wrong' then connect it to a PC to pull the log. The issue is its very random and being at a PC to do it when it goes wrong could be tricky.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
chronicfathead said:
I wonder if pulling the log cat via adb would work, I.e. wait till it goes wrong' then connect it to a PC to pull the log. The issue is its very random and being at a PC to do it when it goes wrong could be tricky.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
or you could have kmsg being written to a file during it...
the hard reset (power button for 20s) clears memory
I have a stock GN running 4.2.1 paranoid android rom and mine shuts itself down periodically. I'll hit the power button to turn the screen on and NOTHING. I don't have to do a battery pull to restart it but if I hold the Power button down 4 or 5 seconds it reboots and runs like nothing happened. When it's happened I haven't been on wi-fi either. I don't have that many apps running and can't figure out why it does it. It happened last night. Mine is never plugged in when it happens either. It makes me 1/2 crazy trying to figure out why it keeps shutting itself down. When it's running it works great without any real issues.... then the damn thing shuts itself down again. Let me know if anyone can find a reason for this strange behavior. I don't want to take it back for a random issue like this. Who knows the next one I get may be worse.
Sent from my Galaxy Nexus using Tapatalk 2
sounds like a SOD (sleep of death?)
what kernel are you running with the paranoid rom?
I installed a new rom, and this is still happening.
Sometimes I press the power button on my kindle to wake it up, and it doesn't do anything. But I never turned it off, and I know it didn't run out of batteries. So I have to hold down the power button for a while to forcibly shut it down and then turn it back on.
This is getting annoying since it happens at least once a day, but I don't know how to troubleshoot this.
And yes, I wiped everything before flashing, and I'm using a recent version of TWRP.
Artel said:
I installed a new rom, and this is still happening.
Sometimes I press the power button on my kindle to wake it up, and it doesn't do anything. But I never turned it off, and I know it didn't run out of batteries. So I have to hold down the power button for a while to forcibly shut it down and then turn it back on.
This is getting annoying since it happens at least once a day, but I don't know how to troubleshoot this.
And yes, I wiped everything before flashing, and I'm using a recent version of TWRP.
Click to expand...
Click to collapse
What ROM are you using and what ROM were you using before?
soupmagnet said:
What ROM are you using and what ROM were you using before?
Click to expand...
Click to collapse
SmoothRom and twa priv's cm 10.1
From 4.21 version, My KF always could not turn on from standby, even with the latest ROM. Have to long push power button to force off than turn on. Does it conflict with some apps? Full wipe could not solve. Please advise. Thanks
Sent from my Amazon Kindle Fire using xda app-developers app
Artel said:
I installed a new rom, and this is still happening.
Sometimes I press the power button on my kindle to wake it up, and it doesn't do anything. But I never turned it off, and I know it didn't run out of batteries. So I have to hold down the power button for a while to forcibly shut it down and then turn it back on.
This is getting annoying since it happens at least once a day, but I don't know how to troubleshoot this.
And yes, I wiped everything before flashing, and I'm using a recent version of TWRP.
Click to expand...
Click to collapse
I've been having this issue for a while now. I don't think it has anything to do with the ROM because there are MANY threads with this same question on the official Amazon boards and they are all running the original Kindle software.
It seems like something is causing the kindle to hang while the screen is off and the processor keeps working because I see significant battery drain when I reboot (especially if it happens overnight). The interesting thing I saw today was that it's due to a battery calibration bug on the Fire that it hangs when the battery reaches 100% charge and then freezes when the device stops charging. This SEEMS to coincide with what I am seeing, but I haven't looked into it yet.
Regardless, this issue has been coming up in forums for several years and there appears to be no fix that I have found, at least... but it IS annoying!
Hello guys,
I tried to search for a similar issues but I couldn't find anything similar so please bear with me.
My KF sometimes shuts down overnight. In the morning then I have troubles to switching it on again (clicking the power button, holding it for longer periods of time...). It usually helps for the tablet being connected to the charger, but it takes a few tries to turn it on. After I managed to turn it on again, for example yesterday, it had 80% of battery left.
I am using CM nighties and this is happening already for some time.
I am also using juice defender, I am not sure if that is relevant.
Do you have any suggestion, what could be the cause of this? Maybe a suggested alternative rom? Or some logs I can check? I think the powering on troubles bother me more than the shutting off overnight since I always think it won't come back on anymore.
Also, not sure if relevant. If I try to turn it on and it doesn't, sometimes the button flashes orange. After a few tries it turns green and powers on. Not sure if I am now not only confusing times, when it was simply out of juice.
P.S. On a different note, just curious, does anyone know how if there is a rom with working mic already?
Thanks in advance.
jkb
Yes, I sometimes have the same issue with the power button - in fact it happened to me this morning where I went from about 60% charge to 16% with a sudden power drop.
Not sure why this happens. I thought it was a bad battery so I changed it but am still getting the problem every now and then.
Sent from my Nexus 7 using xda premium
the only thing that i can think of is that during the middle of the night a soft-reboot happens and it cant boot back up into the system. this would cause it to sit there and continually try to boot up. this would use a lot of cpu and a lot of power. as for why that drains battery while being plugged in, well i cant help you on that.
Thanks for the input. I've wiped dalvik, cache and the system and installed hashcodes AOSP Jelly Bean (http://forum.xda-developers.com/showthread.php?t=2041694) and at least it survived this night without shutting down so maybe this helped. If I come across the same issue, I will update this thread with new info.
Thanks again,
jkb
Check this out:
amazon.com/gp/help/customer/forums/kindleqna/ref=cm_cd_pg_pg139?ie=UTF8&cdForum=Fx1GLDPZMNR1X53&cdPage=139&cdThread=Tx2JSJNEOWHGOIT
Sounds like a hardware issue, and Amazon has been replacing those of customers who buy new from them.
Mine has this issue too. I KNOW it has battery power, and is still on, but the screen won't turn on. Only solution is to plug in power, then hold down the power button until it shuts down hard. Then turn back on.
I'm returning mine because of it.
Thanks for the info. I am still hoping this is a software issue.Regrettably I am outside o the US and thus replacing it is nearly impossible. I will see, if the issue returns with the new rom and will update the thread if it happens again, just for your information.
jokob.sk said:
Thanks for the info. I am still hoping this is a software issue.Regrettably I am outside o the US and thus replacing it is nearly impossible. I will see, if the issue returns with the new rom and will update the thread if it happens again, just for your information.
Click to expand...
Click to collapse
Try going to the WiFi settings and selecting 'never' for keeping WiFi on during sleep. This seemed to work for me.... So far it hasn't happened again.
Sent from my Nexus 7 using xda premium
I think this is the bug I am experiencing:
Shutdown bug stalls out the shutdown. Looks like the device is off, but it's still powered draining battery. Currently requires long power button press to fully shutdown after the screen is black (about 15-20 seconds).
from the 3.4 kernel thread (http://forum.xda-developers.com/showthread.php?t=2264563). I am not sure if cm 10.1 nighties contain this kernel, but the description is pretty much spot on.I couldn't test the fix (holding the button for 15-20 seconds), since I already changed roms, but if someone experiences the issue again, he can post if this works and which rom and kernel they are using.
This happens to my Kindle Fire device as well. It just randomly shuts off and it won't come back on until I do a hard shutdown then turn it back on. I currently have AOSP Jelly Bean 4.2.2_r1 on it.
pwrdbykimchi said:
This happens to my Kindle Fire device as well. It just randomly shuts off and it won't come back on until I do a hard shutdown then turn it back on. I currently have AOSP Jelly Bean 4.2.2_r1 on it.
Click to expand...
Click to collapse
Yes, it happened again to me with the same ROM, but it happens less often. I will try the updated kernel once it is finished.
On May 27, 2013, Hashcode listed the known issues of the current kernel on his website:
Sound / MIC debugging
Deep sleep issues with “omapdss_dpi” device
SmartReflex shutdown loop fix.
Charging driver / OTG improvrments
Click to expand...
Click to collapse
Looks like they've been identified and are being resolved. :good: