When my NC goes to sleep it is shutting down and I have to hols the power button for 15 seconds for it to boot. Also screen is very unresponsive even after turning screen off and back on. Running group 67. Any thoughts?
Sent from my ADR6300 using XDA App
Related
My rooted NC with Cyan and Phiremod7 (very stable!!) has just started having a problem today. Left alone, it has turned off by itself. Doesn't turn off when I'm using it. Don't really know how long it is taking to do that, but around 2 - 5 hours probably. Actually takes 5 - 8 seconds of holding power button in to turn back on. Usually just sleeps and a tap of the power button wakes up the screen. That function still works, tho. But what could be causing it to turn off? Could a recovery using Rom Manager be the answer? Rather fix the problem than use recovery
Sent from my NookColor using xda premium
+1 I am having the same problems too
It worked fine through the night but shut off again this morning. Had been browsing xda, pushed the power button to turn screen off, left it for a while, then later tried to turn screen back on by touching power button. Didn't work. As if it was turned off. Had to hold button in for a count to 10 seconds before it booted back up.
Sent from my NookColor using xda premium
Just uninstalled several apps that I installed recently (latest) and turned it off. Turned it back on, and it only took the usual 5 seconds holding the power button to turn on.
Keep you posted as to what it does today
Sent from my NookColor using xda premium
the power button issue is normal...it takes about that long for anyone on any CM version on a Nook Color....as for the powering off after it's sitting there for a while...i do not know what the issue there is, I am running Phiremod 7 as well and i have not had any problems with it since i flashed it which was about 1-2 months ago
Isn't this the sleep of death?
I've been having it pretty routinely now lately with several different rooms including the ics ones.
Starting to wonder if it isn't hw related.
Sent from my NookColor using Tapatalk
xc68000 said:
Isn't this the sleep of death?
Click to expand...
Click to collapse
Yes, that definitely sounds like it. The device isn't off, it's just frozen in sleep mode or while trying to wake up and it can't turn the screen back on. Holding the power button is first forcing a hard power-off and then turning the Nook back on
Is hard power off the only solution? It's happened another time since my last posting.
I'm having this same problem. I'm running Cyanogenmod 7 on my Nook Color and it either goes dead or the screen doesn't turn on if I leave it idle anywhere from 1-3 hours. It seems to happen randomly and without warning. It is very frustrating. I even reflashed to a different CM7 nightly build and it still happens. Is there any help for this problem?
Sent from my NookColor using XDA
I was having the same issue (SOD like symptoms every day or other day). I re-calibrated my battery and haven't had the issue since. Just charge up to 100% and run down to the warning by keeping a video playing and the brightness at 100%. Run it down past the warnings until it shuts off and recharge back to 100%.
gryphon101 said:
My rooted NC with Cyan and Phiremod7 (very stable!!) has just started having a problem today. Left alone, it has turned off by itself. Doesn't turn off when I'm using it. Don't really know how long it is taking to do that, but around 2 - 5 hours probably. Actually takes 5 - 8 seconds of holding power button in to turn back on. Usually just sleeps and a tap of the power button wakes up the screen. That function still works, tho. But what could be causing it to turn off? Could a recovery using Rom Manager be the answer? Rather fix the problem than use recovery
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
Definitely sounds like Sleep of Death (SOD). It happens when you leave wifi on all the time and it goes into deep sleep. Wifi and deep sleep get tangled up and it locks up. It is on but you cannot turn the screen back on. Only solution to get it going again is to turn it fully off and back on. The solution is to apply a patched wifi kernel module to your system. You can get it several places including here:
http://d01.megashares.com/?d01=8VPCE7N
Battery on my nook hd+ wont charge I am using stock system and every time I try to charge it , indicator lights turns red for a few sec and then goes green immediately.
how to solve this once for all? I have tried to unplug and plug back in for many times until the light does'nt change in color..is there a better way!!!!!!
i have the same problem,
I've seen similar behavior. While plugged in, hold the power button down 10 seconds. That's will affirmatively turn it off. Wait a few minutes then try turning on the nook, you will have to hold the power button for a couple of seconds to get it to boot. If your battery is very low, you may have to let it charge for awhile first. Just keep trying periodically and it should come back on.
Sent from my BN NookHD+ on Carbon 4.3 using xda app-developers app
When I press the power button the screen would turn on real quick than turn off it'll do this a few times than finally turn on. It only happens when it's off the charger and has been sleeping for a short while. Are there any solutions?
Sent from my One using xda app-developers app
My nook hd plus seems to be bricked.
My tablet is unable to power on, and even when connected to the USB charger it only have the green light and it does not turn orange even after a day of charging.
It does not seems to be a dead battery as I had charged it externally.
The tablet would become hot when I reconnect my battery to the tablet.
My tablet might had bricked as I tried to speed by installing ram manager, and my tablet was stuck when it was booting up.
After switching my tablet off, it is unable to be turn on.
What can I do to make it boot?
Green is fully charged and orange is when charging so it will not turn orange as long as it is plugged in. Try holding the power button 30 seconds wait 10 seconds and then hold it for 3 more does it turn on then?
Sent from my SPH-L900 using XDA Free mobile app
This is a long shot. Try holding the power and "n" buttons for three to five minutes. If/when you see the backlight come on, continue to hold both buttons until the backlight goes off again. Then try to power it on normally by pressing just the power switch. What this is supposed to do is trigger the watchdog timer.
I've got a Nook HD running CM11 M11. It won't stay powered off. I power it off, and it shuts down, but then about 30 seconds later powers back on, as if it's going through a restart instead of a power off. I've tried it several times, including once where my husband watched to verify I was selecting the correct option.
Suggestions?
JuliMonroe said:
I've got a Nook HD running CM11 M11. It won't stay powered off. I power it off, and it shuts down, but then about 30 seconds later powers back on, as if it's going through a restart instead of a power off. I've tried it several times, including once where my husband watched to verify I was selecting the correct option.
Suggestions?
Click to expand...
Click to collapse
You did not mention whether the Nook is plugged in. It will always boot up when external power is applied. You can shut it down fully when running on battery only.
Sorry. Yes, not plugged in. It turns back on when running on battery power.
JuliMonroe said:
I've got a Nook HD running CM11 M11. It won't stay powered off. I power it off, and it shuts down, but then about 30 seconds later powers back on, as if it's going through a restart instead of a power off. I've tried it several times, including once where my husband watched to verify I was selecting the correct option.
Suggestions?
Click to expand...
Click to collapse
Same problem with my Nook HD & my wife's both with CM 11
I have solved it by using QuickBoot app to shut it down. I know it really isn't solving the problem, but at least when I turn it off it stays off
Here's the link to the app
https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot
Had the same problem. Updated to the next nightly and the problem was gone