[Q] Kindle Fire does not suspense when sleep but shuts down instead - Kindle Fire Q&A, Help & Troubleshooting

I cannot find any info about this in google or XDA so here goes.
I am having a strange problem with my kindle fire. Even with stock rom without root and everything, my kindle fire randomly shuts down when i press the power button to suspend it. It does not occur everytime. Sometimes when I press the power it wakes up, sometimes when I press the power button it starts from boot screen.
Seeing this, I went to root it, install TWRP Recovery and FireFireFire. I tried a CM7 rom. The same thing happens. Sometimes it wakes up sometimes it just boots up as though it has completely shut down.
Tried again, this time I installed the latest Reloaded ICS Rom and flashed the latest intersectRaven's Kernel. The same thing happens. I tried to play around with the CPU settings. The most stable i got was with setcpu and speed of 300mhz when screen off. Default Min 600 Max 1200 with ondemand governor. But even with this, the shut down when screen off still happens randomly.
There is also one interesting observation. The shut down during sleep does not happen when I have the charger plug in. While charging, whenever the screening is off and i power it up, it was up normally.
Is my kindle screwed?
Sorry for the long post. I gather that it will be more useful for anyone that is helping to have more details regarding my problem

This happens tto the kindle when it runs software not specifically designed for the Kindle Fire. The chance is always there with many apps, programs and software not obtained from the amazon appstore or a developer for kindle fire software. To solve this, whenever your kindle acts up like this, hard reset (hold power for 20 seconds) it should start working again. As of now, i have no permanent fix but this works for me.
Sent from my Kindle Fire using XDA

I'm getting a similar behavior. Just upgraded to latest cm10 ROM with same results. The problem I am having is that occasionally when the kindle sits and sleeps for a bit it will turn itself off requiring me to hold the power and restart it. It is annoying to any the least. I plan to go thru the apps to see if one is causing it. Does anyone know where i can check log files for this? I'm still a bit new...

This could be related to a dirty flash. I think some of the older versions of Jelly bean had some strange problems but that is long since sorted. Try a clean flash with an updated version of CM10 to see if a dirty flash is your issue.
•1. Transfer Rom zip and matching gapps zip to sdcard.
•2. Enter recovery.
•3. Create a backup.
•4. Wipe factory reset.
•5. Wipe cache.
•6. Wipe dalvik.
•7. Wipe system.
•8. Flash Rom zip.
•9. Flash gapps zip.
•10. Select reboot, then system if prompted.
•11. Enjoy!

Moved
If you tag the thread title with a [Q], it should be obvious that it belongs into Q&A section .

OP, did you ever find a solution?

Bowsa2511 said:
OP, did you ever find a solution?
Click to expand...
Click to collapse
For the original Kindle Fire OS, I never managed to find a solution for that. When the screen is off after a while, the kindle seems to be switched off on its own (no off animation, just like power to the device is cut off) and it goes into boot mode when I switch on the power.
For custom rom, i have been running hashcode's rom. Some release from his rom managed to solve my problem. Recently when I try to update to the latest version, the same problem came back. I suspect it could be due to the kernel issues with my kindle. Maybe the motherboard of the Kindle is faulty and compatible with some kernel???
The latest one that worked wa build 20121224 running android 4.12 with Kernel 3.0.31.
I still don't understand what happened and I am really interested to find out the root cause. Maybe I will do a logcat (not sure how now) when I am free.

andlcool said:
For the original Kindle Fire OS, I never managed to find a solution for that. When the screen is off after a while, the kindle seems to be switched off on its own (no off animation, just like power to the device is cut off) and it goes into boot mode when I switch on the power.
For custom rom, i have been running hashcode's rom. Some release from his rom managed to solve my problem. Recently when I try to update to the latest version, the same problem came back. I suspect it could be due to the kernel issues with my kindle. Maybe the motherboard of the Kindle is faulty and compatible with some kernel???
The latest one that worked wa build 20121224 running android 4.12 with Kernel 3.0.31.
I still don't understand what happened and I am really interested to find out the root cause. Maybe I will do a logcat (not sure how now) when I am free.
Click to expand...
Click to collapse
I'm having the same experience... older builds of hashcode were fine, but now I have it fully charged and then leave it idle for maybe 6 hours. When I try to wake it up, nothing happens. I have to hold the power button for a long time, and finally it will boot up. When it finally boots up, it's only at 60% battery... a MUCH quicker drain than before.
It sounds like at least with my device, whatever is causing the random shutdown or freeze (it could just be frozen and be refusing to wake up, right?) seems to be causing battery drain.
Anyone have any troubleshooting steps they might try? is logcat the only one?
Otherwise, I'll try wiping everything sometime soon and seeing if that helps.

This happened to me too but only a few times, my Kindle is running CM 10.1, sometimes when I try to use it the Kindle won't respond, not matter how many time I press the power button it won't turn on. But if you wait some minutes the Kindle randomly wake up.
Sent from my GT-N7100 using Tapatalk HD

sebtorres82 said:
This happened to me too but only a few times, my Kindle is running CM 10.1, sometimes when I try to use it the Kindle won't respond, not matter how many time I press the power button it won't turn on. But if you wait some minutes the Kindle randomly wake up.
Sent from my GT-N7100 using Tapatalk HD
Click to expand...
Click to collapse
I did this a while ago so I don't remember which setting I changed, but my current CPU governer is HOTPLUG and my I/O scheduler is VR. After I changed to that configuration, my battery drain problem went away, and my screen not-waking-up problem MOSTLY went away. It still happens occasionally, but I've found I can leave the tablet for a day or two and come back and it will wake up instantly 90% of the time.

Related

[Q] HELP!! New stock nexus ui crashed, stuck at boot animation

Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.
This is the hspa version.
svntsvn said:
Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.
Click to expand...
Click to collapse
The android icon you're referring to sounds like the stock recovery. In order to flash a ROM (even stock) from recovery mode, you'll need to load a custom recovery. This requires the device to be unlocked.
Not very often a stock setup needs to be restored. Generally, with the stock setup, only the /data partition is wiped (revert to factory default) and the issues are cleared. Not sure why a stock setup would need to be restore.
If you're still going to pursue reloading the system, without access to the normal android mode, the best route will be using fastboot. This can be done on a mac and the fastboot commands should be the same.
Hope that helps get a start!
This happened me earlier. I was able to factory reset it, which, unfortunately really annoyed me because I hadn't saved a backup..
Before the "Google" logo shows up, press and hold the power button and the volume up and down buttons.
Then go into recovery mode using the volume buttons.
When it reboots, you get that Droid with the hazard sign (which I know you're at, but just for the sake of others who need help) all you have to do is hold down the power button and WHILE it's held, press the volume up or down button and move to "Factory Reset". When you hold down the power button and press the volume rocker, a little menu will appear. It should only take a few minutes then.
Hope this helps. Apparently this is a WiFi issue. I'll definitely be keeping backups as of now..
I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.
svntsvn said:
I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.
Click to expand...
Click to collapse
I had the exact same problem happen last night with UI crashing and then the getting stuck at the boot animation. I was desperately searching online, looking to find a solution that didn't involve rebooting to factory setting and came across this post and did exactly what you did and it WORKED, very strange, I really wanna know what caused that!!!!
I've had the same problem with my Galaxy Nexus. I received it on December 21st, with stock 4.0.1 build. No root or unlock attempt at any time. On January 2nd I experienced this problems (UI process crash, screen not responding, reboot and stuck in boot animation).
The only solution was to do a factory reset and start over.
On January 10th same problem, same solution. Second factory reset.
I got the 4.0.2 OTA just two days after that. I thought that would resolve the problem. The phone seemed more stable, with less FC's and no trace of the UI crash. Indeed it lasted long...
Exactly until January 24th when I picked up the phone and seemed in the sleep of dead. Removed the battery, restarted the phone... and stuck in the boot animation.
Do you have any advice? Should I return the phone? Aside from those specific problems I am quite happy with the SGN and Android 4 in general. And I use it quite a lot (I have a very long train commute) without other problems.
Again...
It happened again!!
I don't know what to do anymore, this is not a usable phone when I have to reinstall and reconfigure every 3 weeks.
I may have found the problem
Well, not me exactly, but this bug report seems to fit the problem and the charging workaround. Seems to be a problem the file used to store the battery stats and draw the charge graph.
It also fits my usage (I try not to charge it up until 100%).
I can't post links to the forum, the issue is id number 24518 which you can find in code.google.com/p/android/

[Q]Rogers Galaxy S3 constantly restarting even in recovery/download mode

So tonight out of the blue, my Rogers Galaxy S3 restarted itself. This isn't totally unusual, as sometimes this will happen once or twice a day, but never has it been too bad.
First off, I've been running Cyanogenmod 10.0, and again, has been relatively problem free. The first major issue I had was a week or so ago when I woke up to my phone having seemingly restored it's default settings on its own. Apps and all my other data were intact, but widgets, app settings, etc, were all cleared.
Now tonight, my phone can rarely boot into CM, and when it does, the power menu will appear shortly thereafter before restarting itself once again. If the phone is plugged in, I can't get anything other than the charge indicator to come on the screen for more than a second. The phone also does this when trying to boot into recovery mode or download mode.
I'm at a total loss as to what to do here, so I'm going to be leaving the phone off with the battery out over night. Appreciate any feedback in the meantime.
Also having a similar problem: phone boots up, will barely enter the bootloader/TWRP/boot animation for hyperdrive ROM. Also with rogers. I believe it might be SDS but I need to re install the stock firmware and can barely boot into the bootloader without the phone dying (battery is charged though). Any help greatly appreciated!
EDIT: managed to boot up for long enough to install "eMMC check" and apparently I have a 'sane chip'.
There have been issues with the power button getting stuck. Maybe you have that issue?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Domoo said:
There have been issues with the power button getting stuck. Maybe you have that issue?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Well, after pulling most of my hair out, that does seem to be the issue. Would explain why the power menu would come up the few times it did manage to boot. I managed to get it working for a while, but the button seems to be really delicate since picking my phone up and barely touching it reset it again.
I guess now I need a solution to the power button sticking, but at least it doesn't seem to be SDS.
Okay, that makes sense. When I leave the phone completely stable it's fine.
However, I have tried unrooting and reinstalling stock firmware. However, my system status in bootloader is still custom, when I boot up the rom I still have superuser installed. I tried installing two different stock firmwares for Rogers and the same problem. Any help would be great, I really want to send this in for warranty ASAP.
EDIT: After using ODIN to install stock rom, I still had Superuser. I installed SuperSU and then preformed it'sfull unroot. After that i cleared data and cache from stock recovery and the phone is now at original status and seems to not be randomly rebooting/dying. Weird.

[Q] Bricked my Find 7

Hello,
I have had my Find 7 for only 4 months and never had any problems with updating the rom. I am using CM 11 and I do have fastboot/recovery installed and a few recent backup images to choose from.
This morning I decided to flash update with the latest nightly of CM 11 and boom, phone went completely dead. I have been trying to fastboot it but that doesn't work. I connected it to USB and computer shows nothing (because it won't turn on).
If I press the power button, the phone vibrates once, but nothing at all shows up on the screen. If I keep pressing the power button it'll give pulses of single vibrations every 10 seconds or so.
I have gone through the forum but I can't find something that will help me because the phone is dead...
I can't believe a simple CM update would cause such a thing.. if anyone has any idea, please do help!
nkomp18 said:
Hello,
If I press the power button, the phone vibrates once, but nothing at all shows up on the screen. If I keep pressing the power button it'll give pulses of single vibrations every 10 seconds or so.
Click to expand...
Click to collapse
The single vibration with no screen normally means the batteries dead, and it's possible that it's not charging when hooked up to your computer, open it up, take the battery out for 15 seconds, put it back in, then plug it into the charger for an hour or so.
nkomp18 said:
Hello,
I have had my Find 7 for only 4 months and never had any problems with updating the rom. I am using CM 11 and I do have fastboot/recovery installed and a few recent backup images to choose from.
This morning I decided to flash update with the latest nightly of CM 11 and boom, phone went completely dead. I have been trying to fastboot it but that doesn't work. I connected it to USB and computer shows nothing (because it won't turn on).
If I press the power button, the phone vibrates once, but nothing at all shows up on the screen. If I keep pressing the power button it'll give pulses of single vibrations every 10 seconds or so.
I have gone through the forum but I can't find something that will help me because the phone is dead...
I can't believe a simple CM update would cause such a thing.. if anyone has any idea, please do help!
Click to expand...
Click to collapse
Are you sure the zip you downloaded is cm11? There was an issue with yesterday's first cm12 build that resulted in bricked devices.
The device can be recovered
A problem was identified in the find7 nightlies for the 14th and they were pulled; unfortunately you and possibly a few others already installed it.
The problem has been identified and a fix has been found:
http://www.oppoforums.com/threads/guide-how-to-recover-your-bricked-find-7-7a.23067/ provides a tool and instructions on how to return a bricked find7 to stock. The linked download includes the entire stock ColorOS rom, which isn't needed to fix this problem(and is over 1gb in download size!); an edited version can be found at https://mega.co.nz/#!SQNh2ShY!UlHUE8doEBCrcSvHzomU6z0S-7b9AfTuaP_CPYr9yfQ will fix the specific issue caused by this nightly without replacing the OS or wiping your data.
Use the unbrick_cm.zip with the instructions in the oppoforums post (I also had this problem but it wouldn't work on win7 but did on xp, so there may be some compatibility issues) and you should be good to go.
Going forward the builds off download.cyanogenmod.org will include the files flashed by this tool so this shouldn't happen again.
mikeioannina said:
A problem was identified in the find7 nightlies for the 14th and they were pulled; unfortunately you and possibly a few others already installed it.
The problem has been identified and a fix has been found:
http://www.oppoforums.com/threads/guide-how-to-recover-your-bricked-find-7-7a.23067/ provides a tool and instructions on how to return a bricked find7 to stock. The linked download includes the entire stock ColorOS rom, which isn't needed to fix this problem(and is over 1gb in download size!); an edited version can be found at https://mega.co.nz/#!SQNh2ShY!UlHUE8doEBCrcSvHzomU6z0S-7b9AfTuaP_CPYr9yfQ will fix the specific issue caused by this nightly without replacing the OS or wiping your data.
Use the unbrick_cm.zip with the instructions in the oppoforums post (I also had this problem but it wouldn't work on win7 but did on xp, so there may be some compatibility issues) and you should be good to go.
Going forward the builds off download.cyanogenmod.org will include the files flashed by this tool so this shouldn't happen again.
Click to expand...
Click to collapse
Hello and thanks for this.
I followed the guide and the phone came back to life! This is amazing, however, the problem I have now is that the phone shows the Cyanogenmod loading screen and it stays like that forever.
It showed the popup that it was configuring Apps and after that it appeared to be loading the main screen, but then quickly goes back to the cyanogenmod loading screen.
It has been over 5 minutes... that can't be normal, can it?? Is it a known issue after using the unbrick tool?
nkomp18 said:
Hello and thanks for this.
I followed the guide and the phone came back to life! This is amazing, however, the problem I have now is that the phone shows the Cyanogenmod loading screen and it stays like that forever.
It showed the popup that it was configuring Apps and after that it appeared to be loading the main screen, but then quickly goes back to the cyanogenmod loading screen.
It has been over 5 minutes... that can't be normal, can it?? Is it a known issue after using the unbrick tool?
Click to expand...
Click to collapse
Go to your custom recovery, wipe /data /cache /Dalvik and /system, then flash CM+GApps. If you used the tool in my thread, you'll have to boot into COS before flashing anything.
Now it's almost perfect,
The power button only works to lock the screen, not to turn it back on again.
As you can imagine, the phone is unusable if I can't wake it up from sleep.
I tried a lot of things. First of all it's not a hardware issue because the power button works flawlessly to lock the phone or to reboot. It only fails to wake the phone up, which sounds like a software issue.
I tried the option "double tap to wake" and that does nothing. The only thing that wakes the screen is connecting it to a USB.
Any ideas?
I noticed after I followed the instructions some things changed in my phone. The OPPO logo is different when the phone loads and fastboot graphic is different. Now I get Chinese characters whereas before I believe it was an android robot.
I suspect this is causing the power button errors. Any ideas how to put it back?

Sleep/Wake problems [SOLVED]

So i was using Darthstalker v3 and arter97 kernel 9.3 with no issues.
Suddenly one day, i noticed screen flicker when waking the device, followed by hesitation. So my first step was to wipe the dalvik/cache. That apparently did not help.
I then lost my bootup logos, as well as shut down, along with the screen pretty much refusing to come on.
I used smart switch to emergency recover the stock firmware. Nothing. Then i Odined a stock untouched rom. No change. Once i actually got the phone to render the screen in recovery, so i wiped everything three times, and and flashed darthstalker v6. I also rooted the phone again just before that. I
So when the phone is powered off, the battery icon is present, and the screen wakes to that no problem. Since i set the device to never timeout while charging,
when i plug it in, the screen comes on, but as soon as i try to touch it, poof, the rendering of the screen goes. But, while this occurs, i can hear the icons being pressed,
etc. Completely stumped as to what to do. Can someone help?
[SOLVED]
strangely enough, I found a solution in a most peculiar way.
I managed to finally get into the phone by charging to 100 percent. Then, I downloaded flashify, and attempted to flash tekxodus rom, as well as selecting dalvik and cache wipe.
The flash did not work. the phone just rebooted. Then, I downloaded rom manager premium, and then rom manager attempted its prerequisite attempt to detect my recovery. (up until that point, I had twrp installed).
The detection lingered, so I pressed the back key and selected reboot into recovery. Surprisingly enough, I was back in Stock recovery.
So apparently the solution to the anomaly I encountered in the OP, is to either follow the simple steps above, or, to flash stock recovery in Odin. If that is at all possible for the user. I can confirm the above worked for me as I tried everything for the last week and this was the only method that worked.
The shutdown/startup logos are back, with no screen flicker or hesitation on sleep/wake.
msmercy42 said:
So i was using Darthstalker v3 and arter97 kernel 9.3 with no issues.
Suddenly one day, i noticed screen flicker when waking the device, followed by hesitation. So my first step was to wipe the dalvik/cache. That apparently did not help.
I then lost my bootup logos, as well as shut down, along with the screen pretty much refusing to come on.
I used smart switch to emergency recover the stock firmware. Nothing. Then i Odined a stock untouched rom. No change. Once i actually got the phone to render the screen in recovery, so i wiped everything three times, and and flashed darthstalker v6. I also rooted the phone again just before that. I
So when the phone is powered off, the battery icon is present, and the screen wakes to that no problem. Since i set the device to never timeout while charging,
when i plug it in, the screen comes on, but as soon as i try to touch it, poof, the rendering of the screen goes. But, while this occurs, i can hear the icons being pressed,
etc. Completely stumped as to what to do. Can someone help?
Click to expand...
Click to collapse
yeah i just suddenly started having this problem. my phone would reboot itself and then it would be updating apps as if i just flashed xposed or something, my phone would have issues with wifi, flickering lockscreen, and if you rub the screen while its off which wouldl show you information stream doesnt work either. Decided to dump the rom. Am going with the TEKXodus N5 with arter kernel
powerful111 said:
yeah i just suddenly started having this problem. my phone would reboot itself and then it would be updating apps as if i just flashed xposed or something, my phone would have issues with wifi, flickering lockscreen, and if you rub the screen while its off which wouldl show you information stream doesnt work either. Decided to dump the rom. Am going with the TEKXodus N5 with arter kernel
Click to expand...
Click to collapse
It's just like I told you. When I read that you had experienced the same precursors that I came across with the rom, I had a hunch you would be soon after posting the exact issues that I eventually ran into.
So when you download Tekxodus and flash, please keep me informed as to if it resolves the issue. As you are aware, stock firmware has not resolved the problem for me, but then again devices vary.
So enjoy the fix if you ever run into the above issue.
Im fine with stock, but I miss the fun of trying new roms.

Phone won't shut down; only reboot

I was running a custom KitKat ROM on my Note II, but lately it has been acting up. For example, it would randomly restart on me. And when I would go to shut it down, it wouldn't shut down. Only reboot. And if I take the battery out, as soon as I put the battery back in it would start booting up (I wouldn't even press any buttons).
So I decided to flash Cyanide Android's custom ROM 6.0.1 (Cyanide-v5.0-t0lte-Detoxified-20160828.zip). It is running wonderfully. So far, no random reboots. However, the problem still remains with when I go to shut it down, it reboots. And if I put the battery back in (after taking it out), it starts booting up.
Any ideas on where to start to pinpoint the problem?
Does the same thing happen on a stock ROM? If it does, at least you know if probably isn't a software problem.
I don't know. It started happening loooong after I started putting custom ROM's on. I didn't bother going back to stock. I doubt it's a custom ROM problem.
You'll never really know until you try a stock ROM.
audit13 said:
You'll never really know until you try a stock ROM.
Click to expand...
Click to collapse
Ok. Yes. It does it with stock ROM as well. Now what?
Strange that the problem still exists. Maybe one of custom ROMs changed something in the phone's behaviour? I'm really not sure. Sorry.
It happened randomly after having a custom ROM for at least a year. And it also does weird things like, it's on, and I go to turn the screen on, and it just won't turn on (even though the phone is on). So I have to hold in the power button to hard boot it.

Categories

Resources