I am now on my second nook hd (upgraded from a 7" to a 10")
booth nooks have had the same issue, where i turn the screen off (sleep mode) and then for whatever reason the screen wakes up, (and the lock screen is shown) but it never goes back asleep and eventually kills the battery.
this behavior is random. and doesn't happen all the time.
Once i find the nook turned on, i can make it go back to "sleep" and it will mostly do that.
The nooks are on stock firmware, have most recent frimware and are not rooted.
the case that is used, is not a smart case.
the nook only has 2 applications installed. Astro file manager and bsplayer. using nova launcher
it is kept 99% in airplane mode.
this has been my only android device that doesnt turn off the screen when the lock screen is displayed. (on a side note this is also my only android device that is running stock firmware)
any ideas?
google hasnt been much help...
THRiLL KiLL said:
I am now on my second nook hd (upgraded from a 7" to a 10")
booth nooks have had the same issue, where i turn the screen off (sleep mode) and then for whatever reason the screen wakes up, (and the lock screen is shown) but it never goes back asleep and eventually kills the battery.
this behavior is random. and doesn't happen all the time.
Once i find the nook turned on, i can make it go back to "sleep" and it will mostly do that.
The nooks are on stock firmware, have most recent frimware and are not rooted.
the case that is used, is not a smart case.
the nook only has 2 applications installed. Astro file manager and bsplayer. using nova launcher
it is kept 99% in airplane mode.
this has been my only android device that doesnt turn off the screen when the lock screen is displayed. (on a side note this is also my only android device that is running stock firmware)
any ideas?
google hasnt been much help...
Click to expand...
Click to collapse
When I had a problem with my original nook hd+, verygreen reminded me of trying the bn rom again.
Since your on the bn rom and its fully updated, I'm going to say for you to backup, then do a factory wipe and restore. After that, leave it as-is (no apps, as little setting changes as possible) and see what happens - no nova launcher either - basic and plain untouched. While your at it take away the case too. Perhaps its adding pressure or something else in some crazy way.
If that works then its a start.
If it doesn't then try cm on sdcard and see if it still happens. That way the bn rom could be ruled out.
sandsofmyst said:
When I had a problem with my original nook hd+, verygreen reminded me of trying the bn rom again.
Since your on the bn rom and its fully updated, I'm going to say for you to backup, then do a factory wipe and restore. After that, leave it as-is (no apps, as little setting changes as possible) and see what happens - no nova launcher either - basic and plain untouched. While your at it take away the case too. Perhaps its adding pressure or something else in some crazy way.
If that works then its a start.
If it doesn't then try cm on sdcard and see if it still happens. That way the bn rom could be ruled out.
Click to expand...
Click to collapse
thanks for the suggestions.
i finally had time to wipe and do what you suggested
figured out the case is what was waking it up, but i still had the issue of it never going back to sleep.
i installed go locker. and now its working as expected no more dead batteries.. i am happy!
Related
Not sure if this discussion has already happened.
I have noticed twice since rooting my nook (with 2.12.25) that it has randomly restores back to 1.0.0 (or seemingly).
The first time it was just sitting beside me and it did one of its un-commanded restarts. I noticed that it was reloading the original 1.0.0 version. I lost everything and the nook was unresponsive after finishing. I followed all the hard reset rules and then upgraded to 1.0.1. I then autorooted again and reinstalled all apps.
Last night it did it again while I was using it. I was reading a book and then went to check email. I got an error message something like "invalid authorization" and that it was reloading the base software. I let it do its thing and go through its reboots. I also let it automatically update to 1.0.1 before I touched it. I re-registered it. Now when it loads it doesn't show the normal rooted nook boot screens. When I go into extras I see only the stock apps plus the additional ones that the auto-nooter loads (everything else gone). I tries to get me to log into LogicPD Zoom (Google) but it fails to load.
Has anyone else seems this?
Is there a way to re-load or fix the nook color install without having to go through the complete wipe process?
Once I fix is there some setting we can change to prevent it from happening again?
Thanks
After nootering the nook, I proceeded to load clockwork mod and made a backup of the OS. Now when it auto restores, I can reinstall the backup from clockwork mod by holding both Power and the Nook Key for five seconds when powering on.
Still don't seem to know how to stop the auto restoring though
Mine restarts too, has since I rooted it. Thankfully, there is no data loss, just an inconvenience. If there were a log being kept (like in other OSs), I could at least go there to find out what is crashing it.
Acts like a low memory restart, but that isn't what it is.
TJD
Wanted to add that mine does this also. It has happened 3 times in 4 weeks. Thank god for ClockWork it is not to big a deal now to restore. I wish someone could figure this out tho.
Mine actually randomly boots up (I'll have it off, then hear it start up a few hours later). Not sure it's related, but thought I'd mention it in case it turns out to be.
Sent from my PC36100 using XDA App
Mine used to restart everytime it went to sleep. Happens to alot of people. SetCPU and On Demand usually fixes it. There is like 2 or 3 of these threads in Q&A
straby187 said:
Mine used to restart everytime it went to sleep. Happens to alot of people. SetCPU and On Demand usually fixes it. There is like 2 or 3 of these threads in Q&A
Click to expand...
Click to collapse
Except they're talking about the system restoring itself, not rebooting.
It has to reboot to restore. Thought if you fix the reboot problem it would help maybe not... My bad
I'm autonooted on 1.0.0 and have never had an ota restore or update.
Sent from my Nook Color
Have you guys made sure to rename the otacerts file after rooting?
There are several active threads on this. In my case it was a faulty power button. I went ahead and exchanged the unit. Replacement is 1.01 and feels like the case is sturdier. Might be imagining that. Check my other posts on the subject. Good luck.
Sent from my NC using XDA app
First I thought that I'm crazy but now I can confirm that my NC will boot on it's own after about 5 minutes after power OFF. I have to shut down 2nd time and than it will stay OFF. Any idea what's wrong ?
Thanks
(Yes I did confirm after first shut down that it's actually OFF since no buttons will respond)
Any weather Apps running? Many of them have an option to wakeup in order to update. Check your mail, twitter and facebook apps. It has to be something you installed, I have run every update, tried all the froyo images and both Honeycomb releases and I have not seen that.
To expand on what gedster wrote, it seems kind of crazy and out there but what about any devices on your network that might send Wake on Lan requests? What if something on your network had located your NOOKcolor. I don't even know why a eReader Tablet would have a function for Wake on Lan but it's just another crazy avenue to jog down.
I do have weather app installed but I find it hard to believe that it can wake up OS that is not in standby but completely off. WIFI is also not enabled before shutdown.
Looks like the problem is there only if I used market, if market is not used it will shut down fine and it will not boot on its own.
lifeisfun said:
Looks like the problem is there only if I used market, if market is not used it will shut down fine and it will not boot on its own.
Click to expand...
Click to collapse
Seems that's unlikely if you're the only one having the issue, I'd keep digging if I were you.
Looks like you're right I can't replicate the problem every time
The timing when it will boot also varies 5, 15 and even 35 minutes.
Don't know what to do, it's hard to imagine how it can boot on it's own from
complete power off state
I can't believe I'm the only one with this problem
lifeisfun said:
I can't believe I'm the only one with this problem
Click to expand...
Click to collapse
I just posted a thread about this issue for me less than an hour ago! Funny, no one replied to mine: http://forum.xda-developers.com/showthread.php?t=940713. It was pretty long...guess I should've added a TL;DR.
It happens to me on any (or no) power source. Timing varies like yours as well. I'm going to pull my weather app based on the above recommendation, and I will try your Market theory out. Knowing someone else has this issue makes me hopeful that we can find something that we have in common as the culprit.
I did download the newest Honeycomb image yesterday and I'm going to put that SD card in and see if I can get it to turn itself back on on a Market-less, user App-less build. If successful I'll Titanium my 1.1 apps and remove everything non-system, then slowly add until I get this figured out. Keep me posted if you figure something out, I'll be sure to do the same!
In case it matters I bought mine about a week ago and the serial number starts with 20046.
EDIT: Testing with Honeycomb SD now so if that's the case here it should just stay off. I booted into Honeycomb at 9CST and turned it off at 9:01. I'll give it a couple of hours.
I used to have this same problem. I would randomly find my 1.0.1 auto-nootered 950mhz rom nook on, when I knew I had turned it off. interesting part is, this problem completely solved itself after I flashed my emmc with the custom nookie 5.9 img. so it must be an eclair issue and not a hardware issue
woot1524 said:
I used to have this same problem. I would randomly find my 1.0.1 auto-nootered 950mhz rom nook on, when I knew I had turned it off. interesting part is, this problem completely solved itself after I flashed my emmc with the custom nookie 5.9 img. so it must be an eclair issue and not a hardware issue
Click to expand...
Click to collapse
Really? I've been putting that off because I don't like the idea of not having Clockwork Recovery. I understand there are ways to do the same things using IOMonster's things but I'd really rather just have Clockwork Recovery working. Unless there's a way to get it going that I missed?
Yup, I've been having this issue as well. I really want to flash NF but I want hardware video acceleration.
oscillot said:
Really? I've been putting that off because I don't like the idea of not having Clockwork Recovery. I understand there are ways to do the same things using IOMonster's things but I'd really rather just have Clockwork Recovery working. Unless there's a way to get it going that I missed?
Click to expand...
Click to collapse
you are correct that clockwork does not work with froyo. however the bootable sd card that you would burn automatically starts up clockwork first. you can run a backup and restore, as far as i know, without having to reflash froyo. on a personal note, froyo still has some issues but overall I'm exteremly pleased so far. i really just wanted to get rid of all of the b&n stuff (mainly the status bar) along with any possible way of them pushing an update to break root. I would recommend it, but CM 7 with gingerbread will probably be out sooner rather than later.
woot1524 said:
you are correct that clockwork does not work with froyo. however the bootable sd card that you would burn automatically starts up clockwork first. you can run a backup and restore, as far as i know, without having to reflash froyo. on a personal note, froyo still has some issues but overall I'm exteremly pleased so far. i really just wanted to get rid of all of the b&n stuff (mainly the status bar) along with any possible way of them pushing an update to break root. I would recommend it, but CM 7 with gingerbread will probably be out sooner rather than later.
Click to expand...
Click to collapse
Which I guess brings us back to, why is Eclair doing this, and why does it seem to be limited to lifeisfun and myself?
I'm glad I'm no longer special
My serial # is 200503 .....
Removing all application that I have installed didn't help.
Only 100% way to shut down is to let it boot and immediately shut down.
unknown.soul said:
Yup, I've been having this issue as well. I really want to flash NF but I want hardware video acceleration.
Click to expand...
Click to collapse
Now that I understand the power of this things SD slot and that CWR can be run off of an SD, I can totally live with that. Hardware Video isn't a must for me yet, so I may take the plunge tonight after work...BTW, what are people's favorite video apps? I have been playing with VLC stream and convert, which works somewhat with my media server's samba shares. I have the share mounted to a directory on the sdcard since many apps look there exclusively.
More on topic, I couldn't get SD Honeycomb to start itself on its own. I tried booting then shutting down. 2 hrs of nothing 15mins light activity then shutting down. 2 more hours of nothing. About an hour of heavy use, seeing what could be installed, sideloading, testing, editing things like build.prop and rebooting often and trying to get swype working (don't think it's supposed to, but that's "heavy use" for me.) Powered down. Went to bed. Still not on this morning. This looks indeed to be an issue with the B&N stock Eclair.
Mine doesn't turn itself on with no interaction at all, but will turn on every time when you plug in the charger or cable hooked to USB port in computer.
I can turn it off once it is already plugged in and it will stay off, but remove and replug the charger and it is on again.
Strange.
Well, strange that only two or three of us noticed this strange problem.
Yeah, started for me after 1.1 update. Turned it off last night, tonight it was on with 40% battery! I think its 1.1 related, this didn't happen with 1.0.1 ...
I'm sure there's a condition that's causing or exasperating this issue, something common to us all. But at this point since I don't use the Nook as a video player (I actually bought it to read books, but I use Aldiko and the open epub format) I will likely flash Nookie to the eMMC and call it a day. Honestly can't wait to get a clean notification bar on this thing anyway.
I did a search and couldn't find any other topics covering the same issues I'm having, both here and a general Google search. I also called my mother, and she did indeed say I was special.
Anyway, bought a Nook HD+ two weeks ago and left everything stock for a few days before using Bokbokan's Hybrid SD/EMMC. Everything worked great and enjoyed it for a full week until my Nook started freezing and getting an odd ghosting and slow refresh on the screen.
Figured it was a rom issue so I removed the SD but even when powering it back on the screen had the same effect. And it continued into the stock rom. I de-registered and returned to stock and still had the same issue. Washed out screen, slow refresh, slight flickering an odd randomish burning which held even when the device was powered off and left off for hours. Used the HDMI adapter to see what happened and the output to the TV was fine, making me think I just had a defective screen.
So I returned it for a new one. Followed the same path. Stock a few days, then hybrid install (with the newer Bokbokan rom). Ran great for another few days until I had the screen freeze on me. Not ghosting like I had before, just lines like a disconnected ribbon cable. I reset a few times though and everything was fine. The next day it did it again but took removing the SD card and hard resetting into stock to get it to fix the screen. Then a few hours later I could only get it to boot into the stock rom with a normal screen(CM10 would always have lines and be unusable before it even started booting) , but would go out after 30 seconds. Booted into CWM from the SD card and the screen was fine so I did a factory wipe and left out the SD and booted into stock. De-registered before the screen went out and started over. Started re-registering it and the screen would start going out after the 30 seconds but then snap back to normal after another ten or on a new screen. Once it finished setting up my BN account I reset and... now it seems to be running normal... Left it sit like this for a few hours (checking it every few minutes) and I haven't had a single issue.
This seems to me to be something I'm messing up. I can't see having two defects like that in a row, when I know other people who bought the same week/store from me and haven't had any issues (also running the same Bokbokan rom). And the fact that it seems to fix itself the longer it sits in stock. I haven't dropped it. There has to be something I'm not thinking of that's causing the issues. But I'm completely out of ideas.
Is this maybe some kind of new anti-rooting thing by B&N? Does someone have a voodoo doll of my Nook? My SD card have some type of bacterial infection? Maybe a full blood moon overhead? An allergic reaction to my screen protectors?
Any ideas?
Do you have some big magnetic source or other device in your house that could be effecting your HD+? Just grasping for straws. Never heard of this before.
You might try verygreen's NEW SD scheme and see if you get the same thing.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Do you have some big magnetic source or other device in your house that could be effecting your HD+? Just grasping for straws. Never heard of this before.
You might try verygreen's NEW SD scheme and see if you get the same thing.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
My case does have a magnet in it, but this started before I got this new case.
But the way the screen looks is the way a screen looks like when it needs degaussing... But wouldn't explain why it only clears up after running a fresh stock rom for a bit.
Which has me thinking now it is something wrong with my rom. Even though both Nooks used different roms. I shall try using verygreens and see what kind of results I get.
I hate problems like this. =p
I'll report back in a bit!
[I put this message on the general Kindle Fire forum, and was told to move it here]
I have a Kindle Fire 5th Gen. A while ago I used rootjunky's supertools, apparently successfully: first downgrading the firmware to 1.2, then taking the first five options in the supertool (add google play store, root device, block OTA updates, remove lock screen ads, and install nova launcher). I added a few apps (SignBSL, SuperSU, Firefox, termux, wshell) and all seemed ok.
This all worked ok, including the wifi. Today I came back to the device after not using it for a while and found that when turned on it loops between the 'lock' screen and the 'fire' screen. I turned off the house wifi, and then found the looping stopped. Disabling wifi makes it start up OK; as soon as wifi is enabled it becomes unusable again. There is no problem with any other devices on the wifi, it is definitely the Kindle Fire that has the problem.
I can connect to the device through ADB, get a shell, and su in the shell. But I don't know what I'm looking for - I haven't done anything with Android before. My first thought was to look in /var/log, but I soon found that doesn't exist.
Can anyone advise how to go from here?
Thanks
Graham
navtis123 said:
[I put this message on the general Kindle Fire forum, and was told to move it here]
I have a Kindle Fire 5th Gen. A while ago I used rootjunky's supertools, apparently successfully: first downgrading the firmware to 1.2, then taking the first five options in the supertool (add google play store, root device, block OTA updates, remove lock screen ads, and install nova launcher). I added a few apps (SignBSL, SuperSU, Firefox, termux, wshell) and all seemed ok.
This all worked ok, including the wifi. Today I came back to the device after not using it for a while and found that when turned on it loops between the 'lock' screen and the 'fire' screen. I turned off the house wifi, and then found the looping stopped. Disabling wifi makes it start up OK; as soon as wifi is enabled it becomes unusable again. There is no problem with any other devices on the wifi, it is definitely the Kindle Fire that has the problem.
I can connect to the device through ADB, get a shell, and su in the shell. But I don't know what I'm looking for - I haven't done anything with Android before. My first thought was to look in /var/log, but I soon found that doesn't exist.
Can anyone advise how to go from here?
Thanks
Graham
Click to expand...
Click to collapse
I would not spend time trying to debug the WiFi issue. Given you have root + ADB access recover whatever personal files you need and then reload FireOS (preferably 5.1.2; 5.3.1 will also work) from the stock recovery menu. Fixing radio issues is akin to tossing sawdust in the transmission. It will likely come back to bite you later.
OK, I've gone back to 5.1.2 and repeated the process. It's all working again now, but since I don't know why it stopped working before am afraid it can just happen again at random - it's better to have a reason for things!
Thanks for the advice anyway.
Left it on for half an hour and its gone back to the original behaviour: on the screen saver, then the fire screen, back to the screen saver, then the fire screen. It doesn't stay long enough on the screen saver to open it and turn the wifi off, I have to get it to disconnect by taking it out of range or turning the house wifi off.
navtis123 said:
OK, I've gone back to 5.1.2 and repeated the process. It's all working again now, but since I don't know why it stopped working before am afraid it can just happen again at random - it's better to have a reason for things!
Thanks for the advice anyway.
Click to expand...
Click to collapse
navtis123 said:
Left it on for half an hour and its gone back to the original behaviour: on the screen saver, then the fire screen, back to the screen saver, then the fire screen. It doesn't stay long enough on the screen saver to open it and turn the wifi off, I have to get it to disconnect by taking it out of range or turning the house wifi off.
Click to expand...
Click to collapse
Rolling back to stock eliminated many possibilities and suggests the likely root case is hardware based assuming you (or Amazon) did not install/update any apps after restoring 5.1.2. Possible one of the chips is overheating triggering a boot loop. If the device is still in warranty Amazon will exchange it. If not you can attempt to load FireOS 5.3.1 (latest rootable version). Given the symptoms that should not make a difference but you have nothing to loose. Just don't go lower than 5.1.2 as device will brick.
Also try moving to a different location (friends house, coffee shop, etc) to see if the AP makes a difference. Not common but certain multi-band APs have been known to trigger device instability.
Wow. This just gets weirder and worse(r). We've been running first CM 11 and then CM 12.1 on this HD for awhile and all was fine. Suddenly the battery indicator became wonky, dropping from 50-ish% to 1%, precipitating a shutdown unless the tablet was immediately plugged in. Then suddenly the battery indicator would return to normal and you could unplug the tablet.
Next, after running a backup on the CM 12.1 ROM the tablet started crashing during boot (the cyan android phase) UNLESS it was plugged in to the power supply (USB to computer is not sufficient). This, despite a good charge level on the battery. After a minute or so when the boot was complete, you could unplug the tablet and go on your way.
Today the screen flashing began. Makes the tablet completely unusable. Sometimes you can calm it down for awhile by connecting via USB to computer, sometimes not. This thing is freaking me out. I just recently took the tablet all the way back to stock and resintalled CM 12.1 from scratch, including building a new SD card from new files. Before someone asks, it's a class 4 card. I've always been fine with Class 10 or UHD cards when working with my Nook Tablet, but for some reason I decided to play it "safe" with the HD and hunted around for a lower class. Maybe a mistake?
Finally I took the tablet back to stock again today, completed the sign-in process to the old B&N account and everything is fine. No screen flashing, no funny business with the battery indicator, no problem booting without the power cable.
I just ordered a "new" (out of box) replacement for the tablet on ebay, but it doesn't seem like this is an actual hardware issue.
What scares me now is a potential repeat of this process with the new tablet. I've never had any experiences like this with my old Nook Tablet. I'm at a complete loss.
Help!
Edit: OK, we seem to have tracked down the general source of the screen flashing. The backup we have been restoring is from July 2017 so quite a few apps want updating. We noticed things would be fine for awhile and then the flashing would start. At one point "Unfortunately Google Play Services has stopped" kept popping up. I began to suspect either a bad or incompatible update was messing with the system. So...we did another restore of the same backup but immediately turned off auto-updates from the PlayStore. Three days later and no display flashing. One small victory.
Could the shutdown during the boot animation be caused by a corrupted file? I don't see how since it boots OK when plugged in, just not on battery, but I'm willing to pursue any possibility.
Edit.Edit: Well, well.... We got a "new" open-box HD from ebay and I started working on it. I noticed in making new SD cards that one I had been working with was not properly set to 0x0C FAT32 LBA. I fixed that. This time the tablet will boot into the OS without being plugged in! Yay! Still have to test that on the old one after I finish building a duplicate system.
I'm restoring apps and everything is fine until suddenly the flashing starts up again. But now I know when it did. The offender seems to be the 0.15 version of Lithium Epub reader. I managed to uninstall that via ADB (with screen flashing you can't do much with the tablet except ADB). Voila, no more screen flashing. I found a copy of version 0.13 and installed that. No flashing screen. Needless to say I've set the app to not auto-update.
Edit.Edit.Edit: Well, $40 later we now have a second Nook HD and both are running fine. Hard to imagine that the goof that somehow happened to the SD card would manifest as only being able to complete boot when plugged in, but that must be it. Returning to stock (tried that...) and reflashing with the newly prepared SD card did the trick. Moral: sweat the small stuff.