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
I am hoping someone can help me with this. I had my nook rooted, market, youtube and gingerbread keyboard installed and working. different boot screen flashed. i plugged it in to my pc here at work to charge. when i unplugged it, it was at the startup screen with the android. The old boot screen is back. All apps are removed. it appears to still be rooted, but I cant bring up keyboard at all. All my apps and everything I installed are gone. I don't understand what happened to it. Any one have any idea? Thanks!
A wizard did it.
Seriously others have reported similar anomalies The thing to do is wipe and start over. I suggest you get titanium back up so you don't have to completely start over next time.
I figured thats what I would have to do. I don't think i would have needed to, had I not installed the gingerboard keyboard. I was just wondering if anyoen else experienced, perhaps we could pinpoint the problem and figure out what to do to avoid it. Worse part is some one wanted to see it after I told them not to waste thier money on an ipad, they come over and it doesnt work at all. Well it worked, but just as an e-reader, bleh who bought it for that, lol.
madfatter said:
I figured thats what I would have to do. I don't think i would have needed to, had I not installed the gingerboard keyboard. I was just wondering if anyoen else experienced, perhaps we could pinpoint the problem and figure out what to do to avoid it. Worse part is some one wanted to see it after I told them not to waste thier money on an ipad, they come over and it doesnt work at all. Well it worked, but just as an e-reader, bleh who bought it for that, lol.
Click to expand...
Click to collapse
Dropbox + AutoNooter are a NC's best friend.. Show the friends how easy it is to root and load up apps. Remember to share.... 2.5 NC's to every grannysmith!
norkoastal said:
Dropbox + AutoNooter are a NC's best friend.. Show the friends how easy it is to root and load up apps. Remember to share.... 2.5 NC's to every grannysmith!
Click to expand...
Click to collapse
Dropbox works very well indeed. Awesome Drop is also very good. While it offers no online storage, it doesn't require an account either. However, neither wanted to work without an External SD card. Haven't looked into they wouldn't use the internal storage. Anyone know?
Possibly it updated to 1.01? Mine was act a little strange, then all of a sudden it updated to 1.01 (even with the script in place to disable over the air updates).
I also had some sporadic reboots. Just re-rooted after the 1.01 update and it seems more stable. I also installed an uptime widget to monitor and it's been up now for 11h 30m..
In a couple more weeks it won't matter as the 2.3 build continues to progress..
amp711 said:
Possibly it updated to 1.01? Mine was act a little strange, then all of a sudden it updated to 1.01 (even with the script in place to disable over the air updates).
I also had some sporadic reboots. Just re-rooted after the 1.01 update and it seems more stable. I also installed an uptime widget to monitor and it's been up now for 11h 30m..
In a couple more weeks it won't matter as the 2.3 build continues to progress..
Click to expand...
Click to collapse
Hey can you let me know if your Read to Me functionality is working on 1.0.1?
Im on 1.0.0 still because the read to me doesn't work with the 1.0.1 update.
I also get sporadic reboots now that im rooted.
Sent from my LogicPD Zoom2 using XDA App
It was already updated. I am not sure what happened, but Its up and running again. This thing is awesome, even with the barnes and noble rom, and restrictions. It plays every game I throw at it, just as good as my Incredible. Most apps fit the screen well and its only going to get better. best 250 I ever spent. I literally carry this thing everywhere I go!
Just saw this post. Same thing just happened to me while I was in the market. Sucks... have to reroot now... argh...
Sent from my PC36100 using XDA App
Another data point: got my Nook Color December 25. It was version 1.0.0. Updated to 1.0.1 and rooted with auto-nooter-2.12.25 on December 26. All went well (including using the Shop, though I didn't buy anything) until last night. Entered the shop and got the infamous "authentication problem" message, after which my nook reset itself. When it was finished, the green 'n' icon in the lower left was on (which is odd, since it appears to have updated from 1.0.1 to 1.0.1).
When the dust had settled, the device was still rooted (I still have Market, still have NookColor Tools, still have SuperUser), but everything I'd put on since rooting was gone, and all my settings (wifi key, barnes and noble account, gmail account) were gone.
I'm reasonably familiar with linux (though only a little bit specifically with android), so I'll be happy to poke around to see if I can find anything....
Possible reason?
Search "maintenance update nook" on Google News [ sorry, I can't post links yet ]
3matthew3 said:
Search "maintenance update nook" on Google News [ sorry, I can't post links yet ]
Click to expand...
Click to collapse
No, that would be 1.0.1. Android Police tend to be late on the uptick on real news, and make up the rest...
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
Picked up my NC 1.0.1 today. Rooted without issue. After having a Google Talk conversation, I lost access to Marketplace, and all Google Apps? Can't log back in?
Anyone else having similar issues?
P.S. My wallpaper was changed as well ?!?!?!?!?!
p.p.s. My browsing history and favorites are gone too? Please tell me an update or something was just pushed out. I feel like I just wasted a few hours of my life here.
My rooted 1.0.1 nook has problems as well. Gets authorization error and resets data. After restoring through the clockwork recovery, had it up just for 5 minutes before it automatically reset again. Lost all my apps, market access, youtube, etc. Don't know if this issue has been discussed before. May just have to go back to stock.
It appears that something is amiss. I cannot sign back into any Google Services.
Can't establish a reliable data connection to the server
This could be a temporary problem or your phone may not be provisioned for data services. If it continues call Customer Care.
Click to expand...
Click to collapse
Would a simple re-rooting solve the issue?
Same here. Was using everything fine Saturday. Turned on the device and in a few minutes I got an error, something about a problem with the registration and it said it was rebooting. It did and wiped everything of my rooted install except the market. Can't login to google account now.
abexman said:
Same here. Was using everything fine Saturday. Turned on the device and in a few minutes I got an error, something about a problem with the registration and it said it was rebooting. It did and wiped everything of my rooted install except the market. Can't login to google account now.
Click to expand...
Click to collapse
I might add that I got my device it was at 1.0.0 and I rooted then reflashed to stock to upgrade to 1.0.1 and rerooted. Then I noticed after today's unexpected reboot/data wipe (the status screen during the reboot says it was wiping data) it again gave a message that it had just upgraded to 1.0.1 so I initially thought this was an issue with the device thinking the firmware upgrade was not quite done...
Mine quit working as well. Mine is a 1.0.0 that was auto-nootered. Everything was fine and I used it daily. Now it is a brick, nothing I do seems to make it boot. Every once in a while I can get the backlight to come on but nothing else and it just goes off again in a few seconds.
Rather than troubleshoot, I busted an 8 times reboot to go back to stock then re-rooted. Seemed like less headache, panic and stress.
If your NC dosen't boot at all. Try doing a dd of snowfox's boot.img in dev section. See thread for more info. You'll need to boot into NF from SD.
Sent from my HTC Desire using XDA App
scottfish said:
Rather than troubleshoot, I busted an 8 times reboot to go back to stock then re-rooted. Seemed like less headache, panic and stress.
Click to expand...
Click to collapse
I have tried rerooting, and restoring through clockwork...it seems to always revert and bootloop. Although the reroot lasted a week and clockwork restore hasn't lasted 24hrs twice now.
Not sure what to do but My wife is ready to kill me! I'll have to go stock till someone finds a way to bust up this authorization or just wait I read some ROMs are being developed.
Have any of you disabled the otacerts.zip?
If you haven't it may be the problem.
I have and same on my wife's and neither of us have had any issue, and we use them daily.
I hadn't realized I should be doing this. I will try it. I am actually thinking that my first store purchase came w/ an update (my issue seemed to start right after a magazine trial purchase was made).
Thanks.
>DARKMAN< said:
Have any of you disabled the otacerts.zip?
If you haven't it may be the problem.
I have and same on my wife's and neither of us have had any issue, and we use them daily.
Click to expand...
Click to collapse
Thank you, I will try that. All the searching I did was for disable OTA NC and such but actually searching for OTACerts brought out many many threads that were archived on this subject... I can't wait to get home to try it!
I did not rename the ota file.... will give it a go.
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.