My friend got a NC yesterday so I upgraded it to 1.0.1 for him and ran Auto-Nooter 2.12.25. After playing around with it for a while we noticed the audio wasn't working, so he rebooted it. And it worked. At least until he put it to sleep. Then when he unlocked it the audio won't work anymore. This is a persistent problem. Rebooting fixes it until he lets the screen lock. I'm not having this problem and I used an older version of Auto-Nooter (2.12.18 I think?). Can anyone else confirm this issue?
It isn't a root issue, the nook needs to be replaced. I have the same problem, going in to exchange today...
How do you know for sure it's not root-related?
It's a somewhat common issue
My second NC had that issue. B&N did a "factory" reset & it was fine until I rebooted it & the problem was back. The new one doesn't have the problem.
Cheers,
kev
Related
My NC was updated OTA this morning to 1.0.1. I noticed after the update that the Read to Me functionality doesn't work. I get an error and have to force quit and even if the book loads up correctly, it doesn't read. Have already checked volume levels and such.
Here's the error:
"Activity Fava Book Reader (in application Fava Book Reader) is not responding."
Anyone else seeing this or know about this issue?
I've been having the same problem. Rooted on 1.0.1. I saw another post for a non-rooted NC that was having the same issues too.
http://bookclubs.barnesandnoble.com...o-Me-quot-books-not-reading-to-me/td-p/760638
I'm rooted on 1.0.1 using Auto-nooter and Read To Me works fine.
I'm on 1.0.1 and rooted with Auto-nooter 2.12.18 - Read To Me doesn't work anymore for me either. Any ideas?
barbo said:
I'm on 1.0.1 and rooted with Auto-nooter 2.12.18 - Read To Me doesn't work anymore for me either. Any ideas?
Click to expand...
Click to collapse
1.0.1 broke my read me functionality BEFORE I even rooted. That's why i've avoided it. My kids like using that.
Sent from my XDA app on my Nook Color
When your read to me function broke, had you side loaded the 1.0.1 update or was it the ota? Mine was sideloaded and I'm thinking that the 1.0.1 update file was some how corrupted when I downloaded it. On Christmas day, when a ton of people got a NC for Christmas and bogged down the BN website, is when downloaded the update file. So I might wipe and use a different source or a fresh download from BN.
willywayne said:
When your read to me function broke, had you side loaded the 1.0.1 update or was it the ota? Mine was sideloaded and I'm thinking that the 1.0.1 update file was some how corrupted when I downloaded it. On Christmas day, when a ton of people got a NC for Christmas and bogged down the BN website, is when downloaded the update file. So I might wipe and use a different source or a fresh download from BN.
Click to expand...
Click to collapse
mine was OTA. i hadn't even rooted it yet. i was just playing with the stock device and then it updated and the feature was gone. just kept erroring out and freezing up or pulling up the book but not reading.
Alright, I completely reset to stock (8 reboots and de-registered it). Checked the info and was back to 1.0.0. Tried the "read to me" function and it worked fine. Put it to sleep waited a few minutes woke it up and tried again with no problems. Side loaded a fresh download of the 1.0.1 update and let it update. Tried the "read to me" again and it worked fine. Put it to sleep and waited about 15 minutes and now it is broke again.
My wifes has had hers since Christmas too, updated it to 1.0.1 the same day as mine and hers still works perfectly.
I will be going to Best Buy to exchange mine for a new one in about ten minutes.
Did you check to see if any other audio was working after the 1.0.1 update? Other as in other than Read to Me?
eyecrispy said:
Did you check to see if any other audio was working after the 1.0.1 update? Other as in other than Read to Me?
Click to expand...
Click to collapse
I thought maybe you were on to something because I had sound turned off in a game. I turned it on in the game and it worked but still not in the "Read to Me". (1.0.1 update plus nootered)
I never could get the audio on Pandora to work but I have it on my phone so I never put much effort into it.
I just got back from Best Buy, updated my new NC to 1.0.1 and everything is working now, including Pandora. I will let it go for a couple days before I root it to make sure everything still works.
FWIW, I turned up my volume to nearly max and Read to Me was working. I wonder if it was a simple volume mistake or if somehow something was changed. I hope everyone else's problem is solved as well
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
I have done some research here and on Google on a really odd problem...
My wife has a NC I updated to 1.0.1 then rooted. About a week later on her way to work it restarted and unupdated (?) back to 1.0.0... So I thought it was a fluke, root was gone but most things still worked, not Youtube or market but other apps I installed while / did.
Now twice, 2 days in a row I have checked out the device, I installed Clockwork, did a backup and the next morning on the way to work (She works in manhattan, takes the train in) it is bootlooped "touch the future of reading" so last nite I ran the clockwork restore and it was fine then again this morning... same thing stuck in a boot loop.
As happy as I am about her being able to restore it on her own...it takes a while and shes at work by the time its done! and the maddening part is that I booted it multiple times the nite before in both cases...
What could be causing this? Things I haven't tried yet?
I checked the SD to make sure there weren't any update.zips or similar,
I have not formatted the SD, that I will do tonight.
I read the whole thread regarding Clockwork I didn't see anything I might have messed up...Does this have to do with uSD boot priority and maybe I have a hidden file on the SD?
And I have really searched for something similar, people have bootloops but not like mine that I can see.
Sorry for being long here but this is frustrating, I'm not all that new at this I've been voiding my warranties for a long time and this one has me stumped...
Thanks in advance for any reasons, suggestions.
EDIT: Looks like I am not alone, I am seeing more of these problems pop up now.
Did you disable OTA updates?
I'm on 1.0.0 and haven't had issues at all. Seems that folks having this issue are all on 1.0.1 (or at least from what I've noticed). So, perhaps, to go 1.0.0 and root?
eyecrispy said:
Did you disable OTA updates?
I'm on 1.0.0 and haven't had issues at all. Seems that folks having this issue are all on 1.0.1 (or at least from what I've noticed). So, perhaps, to go 1.0.0 and root?
Click to expand...
Click to collapse
I have disabled OTA but if this is a registration/ auth problem I guess it wouldn't help.
I have NOT gone the 1.0.0 then root path and that sounds like a good next step, thank you.
My rooted Nook Color reboots itself randomly sometimes, and also gets stuck in a reboot loop as well. I've been searching around and have seen several other cases of this but with no resolution.
After I first got my Nook Color, I started off by sideloading the latest B&N 1.1 update. Then I went ahead and used Auto-Nooter 3.0.0 (1.1 only). That's it really... aside from loading a few other apps from the Market like LauncherPro, BeautifulWidgets, Astro, JustPictures, & Screen ON Widget.
The first time around my Nook Color worked for about 3 weeks with no problems before the boot loop happened. I figured it was a fluke, so I restored to stock and then started back from scratch with updating and then Auto-Nooting again. This time around, it only took about 2-3 days to get back to this boot loop issue.
Anyone else come across this? You think I just have a bad Nook Color, maybe a hardware issue? Like I said, I did search around on Google and did come across a few threads where people were reporting the same thing. The only answer anyone would get was to restore and start from scratch. I just wish there was some type of debugging I can do to see what's happening....
I have the same issue with no resolution. Did you find anything? I think i'm moving to an iPad if I cant sort this today.
I recently decided to go back to complete stock. I wanted to see how a factory stock rom would deal with the battery issues and others I've had. That's where the problems really began. I followed the instructions in a current thread. I used this thread years ago to root my nook without a problem. My Nook HD+ this time would not boot from any SD card. It did not matter what image I used or what method from the mentioned thread. The SD cards are good though. I stupidly did a factory wipe/reset in CWM, mostly because I had tried everything else. I knew not to do it, but I had tried everything! My Nook would stay on the Caynoboot after this. I finally got a flash to work using the old method and CWM 6028, but this time it hung on the Nook screen. After fighting this for a while, I finally got the stock recovery and stock rom to flash. Great, it's working again as it should. The problem I have now is if I leave it alone for a bit the Nook will shut off. I can power it back on, but sometimes it takes a couple of tries. I tried to charge it this morning when the battery went down to 6%, but I could not use my Nook charger. It would shut off or start to boot past the Nook screen and then shutoff. I'm typing this now and my Nook is charging fine through my computer. Has anyone experienced the auto shutoff when leaving it alone? It's totally annoying, but it functions fine other than that. All of these problems came to life after going back to stock root. Personally, I don't feel like starting over again. I'm to nervous that something will go wrong.
My thought is this relates to all the known battery problems the Nook has. CM might eliminated some of the obvious though. Mine started 3 months after I bought it years ago. It was part of the reason I went to CM10 at the time. I thought maybe the factory rom was the issue. Do you guys think the auto shutoff and normal charging method issues are battery related? I don't think it's a hardware issue. It could be the way the rom was finally flashed, but I would expect more problems other than the above. One thing the factory rom did fix was the Nook shutting off on almost any flash video. It was always random, but this has not happened since going back to stock.