Nook turns off - Nook Color Q&A, Help & Troubleshooting

Rooted, using Cyanogen... will turn off randomly when the screen times out, when I hit the N button nothing... any idea's?

How's about hit the power button instead of the N button

Try connecting it to your computer, mine does the same thing, and the only way to get it to respond is to connect it to my PC and hit the power button.

My does the same thing.

Mine does this too. Just flashed it with using http://forum.xda-developers.com/showthread.php?t=1030227 yesterday.
Any fixes?

I just took miui and put nightlies on there so let's see
Sent from my HTC Vision using XDA App

Idk why you post 2 threads but for me if i turn wifi off before i put my nook to sleep i don't get SOD (screen of death) which is what your experiencing. Give that a try.

mine did the same....
which build is stable and without this problem?

Maybe you should check the dates on the threads... I thought I had this one deleted...I found pressing the power button and not the nook button prevents it from happening so ill try that out also
Sent from my HTC Vision using XDA App

Related

Phone stuck in screen off, please help.

Obviously, I'm using a rooted DX. I have liberty 1.5 installed. I also use Droid X overclock. Many times a day, when the screen is off, and I try to unlock the phone, the screen never wakes up, I try pressing different buttons but it just remains unresponsive. Meanwhile , I can see that the phone is still working (the clock, the unlock button, etc. ). It takes like 2-3 minutes, then the phone reboots.
Could the reason be the fact that I make the phone underclock (400,800) when the screen is off?? so it doesn't have enough power to wake up??
PS: NOOB
Sent from my DROIDX using XDA App
http://www.droidforums.net/forum/liberty-rom-dx/126295-reboot-freeze-up-issues.html
Thanks a lot. Apparently I'm not the only one having this issue. Too bad, liberty is a good ROM other than this issue.
Sent from my DROIDX using XDA App

[Q] MT4G won't sleep with Sense

Hi
I have a rooted stock ROM/Theme MT4G which I noticed last week that it stopped going to sleep. If I set the timeout to 15 seconds (or anything) then right after the timeout is reached the screen sleeps and then within a second immediately comes back on (to the lock screen). It keeps doing that no matter what settings I try. This of course kills the battery life with my screen being nearly 100% of use.
I thought it was related to an app update so I removed nearly everything I could to no avail. Thinking that it was something related to the ROM I decided to try a different ROM. I installed CM7RC2 and low and behold the same problem persisted. I had to disable trackball wake for this problem to go away. I then tried several other ROMs and the problem still remained. I've attempted the various Royal* ROMs and the same problem persisted. Any Sense based ROM was problematic since I had no way of disabling Trackball Wake so I'm now running CM7 (nighties).
The other snag I'm having is that I too have the problematic power button but in my case I have to REALLY press hard to operate the power button which of course is annoying.
Anyone have any suggestions or experience with this sort of problem?
Thanks.
Did you check out the Cyanogen mod 7 in settings ?
I did. That's what I'm running now.what exactly are you suggesting? Thanks.
Sent from my HTC Glacier using XDA App
I have the same exact issue, ive been trying to get some devs to add the disable trackpad wake option in sense roms but so far nothing so right now i use either royalginger or royalmiui im on miui but i really miss sense :/
I had the same thing. I booted into recovery and wiped data and cache and flashed again and everything worked.
Sent from my glacier using XDA Premium App
Nicgraner said:
I had the same thing. I booted into recovery and wiped data and cache and flashed again and everything worked.
Sent from my glacier using XDA Premium App
Click to expand...
Click to collapse
Yeah ive tried that be4 with no luck
Nicgraner said:
I had the same thing. I booted into recovery and wiped data and cache and flashed again and everything worked.
Sent from my glacier using XDA Premium App
Click to expand...
Click to collapse
I must have done that a bunch of times already but nothing worked except CM7 because I can disable the trackpad wake function. I wish Sense based ROMs allows for disabling the trackpad...that would be greatly appreciated. An even more helpful feature is the ability to remap the buttons.
Is it possible your trackpad is defective? DO you notice other odd behavior that could be related to it?
If your using google voice its the application doing that you can fix this on cm 7 by moving the application to the Sd card.
Sent from my HTC Glacier using XDA Premium App
I believe this is a real hardware issue... It seemed that the optical sensor in the trackpad is broken and it's always sending signal to the kernel telling that it detected activity but in reality nothing was going on, so the kernel can never go into power saving mode.
Sense UI is a CLOSED SOURCE software, there's nothing you can do to patch it.
Since ALL MT4G are still under the 1 year Manufacturer's warranty, you should call T-Mobile/HTC to get it fixed or just get a replacement....
Ok I found a solution for us mt4g owners with the messed up trackpads, you are gonna have to flash virtuous unity rom v. 2.39 and then apply this patch:
http://dl.dropbox.com/u/28766802/Virtuous/trackpad_disabled.zip
This patch was made by one of the developers of the rom chrisch1974 specially for this issue, so good luck =D
Same problem, but found work-around
My phone (MT4G) has the same issue but I know why it happened. I got caught in the rain and although I had the phone in my pocket, it got wet. Everything works except that. I left in a bag of rice overnight to no avail.
Anyway, when I press the power button to send it to sleep mode, it just comes back to the lock screen. If I let it time out, it goes out but comes right back to the lock screen. Sounds familiar?
What works for me is holding the home button (the one with the sensor) and, while still holding the home button, pressing the power button once. It is then that I let go of the home button.
Works, but sometimes I have to repeat this charade a couple of times before it sticks. Usually have to repeat it when I don't fully press the home button.
Anyway, hopefully this will help someone that is stuck with this phone and is unable to get a replacement.

Desire HD randomly vibrated

As mentioned above, im having problems with my DHD. It mostly vibrates when im pushing it into my pocket. But no always. Also sometimes when it's already few minutes in my pocket.
When i check it i can only see blank screen, so it's really strange what causes phone to vibrate.
Any ideas?
Sent from my Desire HD using XDA App
Mine does this too, does it more if I catch the volume buttons as I put it in my pocket. All with the screen off. I can sometimes get it to do it if I mess with the volume buttons then go to unlock the screen. The phone freezes for a second, then vibrates and unlocks. Occasionally it has rebooted after doing this. No idea why.
No idea but mine started to do it last night too, I shut it down, removed and replaced the battery then restarted it and its been fine since.
Sent from my Desire HD
Disscussion is on in another thread also...
If it vibrates that means the volume up and down button has been pressed, so bug report is getting created. It will be stored in the bugreport folder in the sdcard. Once the report is done it will viberate once again...It might look a rendom viberate...
If it restarts that means power button and voulme up and down has been pressed...(It happens sometime while taking out or putting the phone into pocket).....
Hope this help....
Thanks for realy fast replys. I checked error folder and it is really full of errors.
So in time my phone case will stretch and problems will be gone.
BTW, could you please provide link to related topic?
Sent from my Desire HD using XDA App
some disscussion is here....
http://forum.xda-developers.com/showthread.php?t=863885
Also for the reboot some disscussion has been done on nightly thread of CM7.

Nook Color Won't Turn On

So I got my Nook Color a couple of days ago. I've been using CM7 off the SD card, but when I just went to turn it on nothing happens. I took the SD card out, still a no go. I even tried using a cwm from sd card thing, nada. The Nook doesn't turn on at all. any ideas?
Try plugging in the nook and leaving it for a little while. Sometimes that helps it reset itself.
Try holding down both the power and the nook button simultaneously for awhile untill it reboots sounds like the sod (sleep of death) hit you. Google it!
Sent from my NookColor using Tapatalk
Have you tried rebooting your Nook? Hold the power button for 10 seconds or so, then release it and hold it again for a couple of seconds until the screen flashes white.
I just left it alone for a while and when I picked it up a few hours later it came on. It happened again today, I turned off the screen for a minute, went to turn it back on a and nothing happened. Just a black screen. Interestingly, it was still running though, because when I hit the volume keys the tone sounded. I just held down the power button till it turned off and then turned it back on and it booted right up. Any ideas what could be causing this?
Edit: I forgot to mention I'm now running CM7 from internal memory, so its not just instability from running it from SD
JustisLewis said:
I just left it alone for a while and when I picked it up a few hours later it came on. It happened again today, I turned off the screen for a minute, went to turn it back on a and nothing happened. Just a black screen. Interestingly, it was still running though, because when I hit the volume keys the tone sounded. I just held down the power button till it turned off and then turned it back on and it booted right up. Any ideas what could be causing this?
Edit: I forgot to mention I'm now running CM7 from internal memory, so its not just instability from running it from SD
Click to expand...
Click to collapse
Read the other posts its called Sleep of Death
Sent from my NookColor using Tapatalk
koopakid08 said:
Read the other posts its called Sleep of Death
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
I was under the impression that in sleep of death the nook is inoperable, ie the volume keys wouldn't work. Is that inaccurate?
JustisLewis said:
I was under the impression that in sleep of death the nook is inoperable, ie the volume keys wouldn't work. Is that inaccurate?
Click to expand...
Click to collapse
No, for some odd reason sometimes you can hear sound and the volume keys will work. Nothing else will.
To fix SoD: set up two profiles in tasker. One for wifi off when screen is off and one for wifi on with screen on.
Sent from my LG Optimus V using Tapatalk
tasker fix, good to know, had this happen the other day to my nook
Glad I came across this thread. I updated my ROM to CM7.1 earlier this week and have been enjoying it. Came home today and couldn't get my nook color to turn on. Was starting to panic that it had died. Thankfully it was the SoD and I got it back on.
Thanks for the quick tips on how to get it back up and running.

[Q] Does anyone have a power button bug?

I am current using PA mar11 build with franco r102 kernel.
I have issues bringing the menu up when you hold the power button. My power button is not broken, because after a restart (using power toggles) it works again.
Happens randomly. I have searched the forums and have not seen anyone mention this, has anyone else experience this?
Update: Do a fresh wipe, problem will go away
What issues do you have exactly? I mean, what exactly do you see when you long-press your power button?
Sent from my Nexus 4 using xda premium
jamesc760 said:
What issues do you have exactly? I mean, what exactly do you see when you long-press your power button?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
after a long-press no menu comes out and my screen turns off like I pressed it normally.
I have the exact same problem, except that my nexus 4 isn't rooted and I can't use toggle buttons to restart. So basically I cannot restart my phone unless i let the battery running out or i reset the phone.
Weird... I just got this too... restart and it's working again... but for how long.... and I never would have noticed if I wasn't trying to take a screenshot!
Sent from my Nexus 4 using Tapatalk 2
I have exactly the same problem running slimrom 6.5 and anarkia kernel.
After a reboot the reboot menu always comes up. After a while it doesn't work anymore. Turning on/off the screen always works, the problem only affects long press.
Has anyone a sultuion for that?
br0ok1ynb0i said:
I am current using PA mar11 build with franco r102 kernel.
I have issues bringing the menu up when you hold the power button. My power button is not broken, because after a restart (using power toggles) it works again.
Happens randomly. I have searched the forums and have not seen anyone mention this, has anyone else experience this?
Thanks
Click to expand...
Click to collapse
Did anyone find a solution to this problem?
My Nexus 4 is now having this same issue
I thought I was the only one! It happened after a bit of rain with my phone in the pocket and I thought that was the cause but after holding it down and seeing it reset I see that it is not. Wonder why this is happening.
Note: I am running completely stock 4.3 at the moment with a locked bootloader, but this has also happened on 4.2.
I got this issue with franco kernel. putting back the original kernel fixed the issue for me. I was able to reproduce the problem with another nexus 4 phone. there's maybe a config to tweak or i'm messing something up.
nikwist said:
I have the exact same problem, except that my nexus 4 isn't rooted and I can't use toggle buttons to restart. So basically I cannot restart my phone unless i let the battery running out or i reset the phone.
Click to expand...
Click to collapse
Exactly same problem.. But a long press of the button for about ten to fifteen shuts down the phone in my case.. Stock 4.3 no root
I no longer have this issue. The fix: fresh wipe

Categories

Resources