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:
Related
I can't turn on the device while its plugged in and charging while its turned off. I would have to take out the batteries everytime. Is this a bug or is it suppose to be like this?
Sent from my Galaxy Nexus using Tapatalk
i have the same problem with all coocked rom but no with stock
i can turn it on... just hold the power button for a few seconds.
melterx12 said:
i can turn it on... just hold the power button for a few seconds.
Click to expand...
Click to collapse
Tried holding it for 2 minutes yet nothing happens. Don't think it is rom problem?
Sent from my Galaxy Nexus using Tapatalk
Good thing I read through this q n a, I'm going crazy too. When I power off (to reboot after installing tons of apps, to refresh etc.) I get the battery charged icon and freezes there. Only battery pull works. I'm on Android Revolution 2.1.0 unlocked and rooted. I guess bug? Annoying, feel like I'm going to tear the cover every time and damage the screen
This happened to me too, and the battery charging icon caused burn-in. Fortunately, it went away after a day or so.
Same bug here. We'll have to hold tight and wait for a fix or run stock.
On my Fascinate you could hold the vol up and power button to get soft boot the phone, but the GNex does not seem to have this feature. I hate pulling the battery.
Same issue for me ... I think we have to open a bug tracking. This is a very annoying problem.
Android 4.0.2
Kernel 3.0.8-gaaa2611
Since my phone is new to me I wanted to power down and get a full charge.. but I can report this bug as well. /cry
Did any of you use a different rom prior to ARHD? I wonder if its something in the kernel or the OS. What allows the phone to show that animation when turned off? That could hint at what modification breaks offline charging.
I have this problem too running a revolution rom. The phone charges fine but I have to pull the battery to boot up. It's a strange one!
does this happen to stock rom? the one shipped with the phone?
zeke1988 said:
does this happen to stock rom? the one shipped with the phone?
Click to expand...
Click to collapse
No!
The bug happens with custom roms. Infact I went back to the stock rom and (even if rooted) I can charge the phone when it's turned off without having problems.
I am certain the phone still charges to 100% but it appears to be frozen. The only way to boot back up is a battery pull.
Any more info on this from anyone? I saw a 4.0.3 rom yesterday that claims to fix the issue so maybe that's the way forward.
Same here, on bigxie's ROM, if I try to boot with phone plugged in from being dead, freezes right at battery charging icon, have to battery pull. Very annoying.
just4747 said:
Very annoying.
Click to expand...
Click to collapse
I agree.... infact I will not use custom roms until the bug will be closed!
This seems to be more prevalent in 4.0.3 roms. I have a deodexed 4.0.2 rom from bigxie which charges just fine when powered off. However any 4.0.3 rom will not let me charge while off.
Not sure if it's an unintented bug but we'll have to see when the full update hits gnex officially.
ihyln said:
This seems to be more prevalent in 4.0.3 roms.
Click to expand...
Click to collapse
I don't think so. I had the bug in a 4.0.2 custom rom
Fixed in 4.0.3 ROM/Kernel.
RMatt1992 said:
Fixed in 4.0.3 ROM/Kernel.
Click to expand...
Click to collapse
what and where? GSM usually doesn't apply to us CDMA/LTE users especially if it's a rom/kernel issue.
Might be related to a custom recovery. Do you guys all have ClockworkMod in common? I have a stock recovery and don't have such problems.
First, I can charge. And the charge rate seems normal. That's not the problem.
Before this problem emerged, when I powered off my phone and plugged it in, it'd turn on the display and I'd see the standard large, completely empty battery, then it'd be blank for a few seconds and an animated charging icon would appear. I've lost this animated icon, and, worse, when I unplug the phone it's not in the usual off state, ready to boot immediately after a longish press of the power button. Now, the display is black, but clearly (in a dark room) powered on. And it's necessary to press the power button for about ten seconds to get it to boot. Before it does, the display does finally shut down, then the boot sequence starts.
I am such a ROM slut that I'm not sure which ROM (or maybe TWRP?) caused this. Stupid, I know, but I just didn't notice how bad the situation was initially until I'd lost track of exactly when it started. I have seen a similar report in the thread discussing Whitehawkx's unofficial AOKP ROM, but it's not perfectly clear that it's the same problem. So I don't want to associate the issue with that ROM at this point. I do recall that one of the many ICS ROMs I briefly cavorted with changed the power-off charging icon to something different than stock/usual. Maybe that had something to do with this problem.
In any case, my great luck with ROMs has finally run out. I've never before caused a problem with my phone I couldn't undo until now. I'd very much appreciate advice from a knowledgeable user or developer about how to get the original power-off, large battery animation back. And the old behavior too, of course.
Thanks very much in advance for any suggestions.
rrrrrichard said:
First, I can charge. And the charge rate seems normal. That's not the problem.
Before this problem emerged, when I powered off my phone and plugged it in, it'd turn on the display and I'd see the standard large, completely empty battery, then it'd be blank for a few seconds and an animated charging icon would appear. I've lost this animated icon, and, worse, when I unplug the phone it's not in the usual off state, ready to boot immediately after a longish press of the power button. Now, the display is black, but clearly (in a dark room) powered on. And it's necessary to press the power button for about ten seconds to get it to boot. Before it does, the display does finally shut down, then the boot sequence starts.
I am such a ROM slut that I'm not sure which ROM (or maybe TWRP?) caused this. Stupid, I know, but I just didn't notice how bad the situation was initially until I'd lost track of exactly when it started. I have seen a similar report in the thread discussing Whitehawkx's unofficial AOKP ROM, but it's not perfectly clear that it's the same problem. So I don't want to associate the issue with that ROM at this point. I do recall that one of the many ICS ROMs I briefly cavorted with changed the power-off charging icon to something different than stock/usual. Maybe that had something to do with this problem.
In any case, my great luck with ROMs has finally run out. I've never before caused a problem with my phone I couldn't undo until now. I'd very much appreciate advice from a knowledgeable user or developer about how to get the original power-off, large battery animation back. And the old behavior too, of course.
Thanks very much in advance for any suggestions.
Click to expand...
Click to collapse
You're probably in any type of AOSP ROM which have this issue.
alphadog32 said:
You're probably in any type of AOSP ROM which have this issue.
Click to expand...
Click to collapse
I tried tdj's ROM and the problem disappeared. Thanks for the hint. Back with cm9 though. I just can't stand the TW look despite the high quality of tdj's work.
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 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!
Hey All,
I'm currently on the CM11 04/22 nightly, and have made it all the way up to the 04/27 nightly to try and resolve this issue and have not been able to. Basically - the sudden death issue has been hitting me very hard - I can't use my phone at all.
I understand the 04/11 nightly is stable and doesn't have this issue, howevery CyanogenMod does not have this on their website.
Does anyone have this install available? (CM-11-Nightly-20140411-D2LTE.zip)
Thanks so much in advance
SLiK
please explain what you mean by sudden death? thanks
rkant18 said:
please explain what you mean by sudden death? thanks
Click to expand...
Click to collapse
I'll be using the phone (say checking my Instagram or reading a book on Play Books) and the screen may be on for about 5-6 minutes. The phone will suddenly shut off on its own. I'll start it up and then shut down again when the phone is loading. It will also sometimes say it has 1-2% battery when it really has 45% (which is what it shows when I plug the phone in).
Hope this clears it up.
SLiK786 said:
I'll be using the phone (say checking my Instagram or reading a book on Play Books) and the screen may be on for about 5-6 minutes. The phone will suddenly shut off on its own. I'll start it up and then shut down again when the phone is loading. It will also sometimes say it has 1-2% battery when it really has 45% (which is what it shows when I plug the phone in).
Hope this clears it up.
Click to expand...
Click to collapse
I had the same issue a week back. Was the most frustrating thing ever...
I finally narrowed it down to the power button. It actually had to do with the power button switch which is soldered to the motherboard. The power button was super sensative, therefore being engagded at all times, causing the phone to hard shutdown every time I tried to turn the phone on.
How I fixed it:
1. Opened my phone up
2. Broke the switch off
3. Done
Now I use my phone without a functioning power button but it was a quick and free fix so it doesnt bother me.
If I decide to do so in the future, I can also solder a new switch back and get the power button working again.
DO NOTE: This might now be the issue you may be facing, so do your research
Finally, I watched this YT video which showed me how to break the power button switch and eventually fix my phone: https://www.youtube.com/watch?v=3Glllc7bEJs
Good Luck
imcol said:
I had the same issue a week back. Was the most frustrating thing ever...
I finally narrowed it down to the power button. It actually had to do with the power button switch which is soldered to the motherboard. The power button was super sensative, therefore being engagded at all times, causing the phone to hard shutdown every time I tried to turn the phone on.
How I fixed it:
1. Opened my phone up
2. Broke the switch off
3. Done
Now I use my phone without a functioning power button but it was a quick and free fix so it doesnt bother me.
If I decide to do so in the future, I can also solder a new switch back and get the power button working again.
DO NOTE: This might now be the issue you may be facing, so do your research
Finally, I watched this YT video which showed me how to break the power button switch and eventually fix my phone:
Good Luck
Click to expand...
Click to collapse
I'm fairly confident that this isn't the power switch. And if it were I'm not sure how comfortable I would feel breaking the power switch off.
The thing that begs me to think this is a software issue is that I'll have 45% battery, the phone will die, and then I'll try to turn the phone on again only for it to tell me I have 1% battery left. I'll put the phone on charge (after it dies again) and it will say charging - 45%.
Anyway I've rolled back a few updates and it seems to be fairly usable now...
Try cleaning the USB port real well and don't use a cheap cable. Use a needle and make sure there is no lint packed in there. These things can cause the phone to cycle itself even when not plugged in. I've fixed several doing exactly what you describe.