Related
Looking to find anyone with the same issues I am having. My NC is rooted using Auto-nooter for 101. Everything went smoothly no issues at all. A day later my NC has been possessed. When reading a book NC would start to skip pages sometimes as much and 5 pages in fast progression, I would then have to swipe back to my page. Then there are times when the quick nave bar of the NC would start flashing multiple times then click a random book from the home screen or from the daily shelf and open it, when I close it it would do it again this would happen about 3 or 4 times till the screen freezes for about 7 minutes. But its not over, then the NC would automatically go into settings then back to home screen then back to settings again really fast, then again freeze. The only way (and this does work) is to "light boot" it by holding down the power button for 5 seconds (the option to shut down will pop up) then let go then press the power button once quickly on then off. The home screen will come back and the "possession" will have stopped, for awhile. This is getting really annoying, especially the reader skipping multiple pages forward on its own as I do like reading with my NC. So has anyone else have this happening? Any ideas as to what this could be? Thanks for any help or ideas. I have read the forums but it seems I am the only "lucky" one to have this issue. Again thanks.
yes, this happened to me. I went and bought a screen cover and cloth. Cleaned the screen VERY thoroughly and applied to cover. Has not happened since.
Phyllip J FRy said:
yes, this happened to me. I went and bought a screen cover and cloth. Cleaned the screen VERY thoroughly and applied to cover. Has not happened since.
Click to expand...
Click to collapse
Do you mean like an anti glare/non scratch screen protector? I have a great gadget cloth that I use all the time.
brie987 said:
Looking to find anyone with the same issues I am having. My NC is rooted using Auto-nooter for 101. Everything went smoothly no issues at all. A day later my NC has been possessed. When reading a book NC would start to skip pages sometimes as much and 5 pages in fast progression, I would then have to swipe back to my page. Then there are times when the quick nave bar of the NC would start flashing multiple times then click a random book from the home screen or from the daily shelf and open it, when I close it it would do it again this would happen about 3 or 4 times till the screen freezes for about 7 minutes. But its not over, then the NC would automatically go into settings then back to home screen then back to settings again really fast, then again freeze. The only way (and this does work) is to "light boot" it by holding down the power button for 5 seconds (the option to shut down will pop up) then let go then press the power button once quickly on then off. The home screen will come back and the "possession" will have stopped, for awhile. This is getting really annoying, especially the reader skipping multiple pages forward on its own as I do like reading with my NC. So has anyone else have this happening? Any ideas as to what this could be? Thanks for any help or ideas. I have read the forums but it seems I am the only "lucky" one to have this issue. Again thanks.
Click to expand...
Click to collapse
No, you're by far not the only one, seems to be related to bad chargers, bad cables, or bad luck... I've had it happen one time while plugged in, but some people have said they couldn't use their NC at all while plugged in.
There are several threads here already on this subject...
I had some eratic stuff going on...buttons clicking, menus popping up, etc. Cleared up after i cleaned the screen really well and stopped breating so heavily (have a cold and coughing & breath was making the screen moist).
something similar happened to me early on... My K key kept pressing itself, and random key strokes while trying to enter a password... here I think.
Is your screen dirty? I happened to be using mine with sweaty hands right then, lots of finger cheese on the screen was causing false contacts. cleaned it and was good to go.
I have had the "dirty screen" issues as well. But there was one time about a week ago when this was happening even after I cleaned the screen. I completely powered off and rebooted and all has been well since. . .
Thanks for the replies I never thought that my greasy marks would make false positive clicks on my screen. come to think of it it does happen when I am reading for a bit before it starts and eating chips while reading just conjures up those spirits, thanks.
EDIT: Alright I am now convinced that this issue is technical. Its happening again now and my screen is clean and I just reboot it. NC was just sitting and charging I started it to read and it just started jumping to settings again and the Nav bar keeps flashing on and off. This time I just let it go and it went on for 5 min even after the screen turned off. I did the old "soft boot" (check first post) and it stoped. HHHHHHHHMMMMMMMMMM. I think I have a conflict with an app. I did the "save battery by changing the phone.apk and telephony.apk, has anyone also changed this and have this problem?
I had the problem before I did the cell standby battery thing.
In another thread people were solving it by recalibrating the screen. I tried it and it worked for a while before they phantom presses started again, though I might have done it wrong to begin with.
*can't post the link but its in the nookdev wiki.
Sunrisemix said:
I had the problem before I did the cell standby battery thing.
In another thread people were solving it by recalibrating the screen. I tried it and it worked for a while before they phantom presses started again, though I might have done it wrong to begin with.
*can't post the link but its in the nookdev wiki.
Click to expand...
Click to collapse
Thank you so much for this, I did not even know of this site, happy I do now. To anyone that needs this the link is here. Again thanks.
http://nookdevs.com/Recalibrate_the_NookColor_touch_screen
Happened to me when i first got my NC while charging it. Has not happened since.
brie987 said:
Looking to find anyone with the same issues I am having. My NC is rooted using Auto-nooter for 101. Everything went smoothly no issues at all. A day later my NC has been possessed. When reading a book NC would start to skip pages sometimes as much and 5 pages in fast progression, I would then have to swipe back to my page. Then there are times when the quick nave bar of the NC would start flashing multiple times then click a random book from the home screen or from the daily shelf and open it, when I close it it would do it again this would happen about 3 or 4 times till the screen freezes for about 7 minutes. But its not over, then the NC would automatically go into settings then back to home screen then back to settings again really fast, then again freeze. The only way (and this does work) is to "light boot" it by holding down the power button for 5 seconds (the option to shut down will pop up) then let go then press the power button once quickly on then off. The home screen will come back and the "possession" will have stopped, for awhile. This is getting really annoying, especially the reader skipping multiple pages forward on its own as I do like reading with my NC. So has anyone else have this happening? Any ideas as to what this could be? Thanks for any help or ideas. I have read the forums but it seems I am the only "lucky" one to have this issue. Again thanks.
Click to expand...
Click to collapse
I had it happen one time recently while the NC was charging. I was attempting to type a FB reply and the keyboard went all wacky. For every character I hit it entered 3-4 random characters. I switched to Gmail and it did the same thing. I unplugged the NC to plug into the computer to calibrate the screen and immediately after unplugging (before calibrating) it worked perfectly. No problems since.
My God! I thought I was the only one this was happening to. It drives me CRAZY. It happens all the time.
I have hands that sweat almost nonstop, and I think they're what causes this for me. Funny thing is, I never noticed it till I rooted. Does AutoNooter install a custom kernel? That may explain it. Also, it mostly seems to happen when plugged in, which makes me think it may be an issue like on the Evo in it's early days where the screen isn't properly grounded. It was fixed by a sensitivity tweak in a software update, and that should be possible here, I'll look into it.
Someone said a screen protector helps, and I just ordered one to try it. They've helped on past devices, and may here too.
While I have not personally had these problems on either of the NCs in the family it seems pretty conclusive that two things contribute to the problem ... a) 'dirty screen' .. getting a screen protector helps ... b) using while charging .. the #1 'quality' problem reported in the forums seems to be the port/plug on the NC and circumstantial evidence points to the cable .. I don't use the NC while it's charging so don't see the behavior and do use it connected to the PC rarely and do not use the B&N cable to connect so those with the problem may want to try another cable/charger. One of my cables works fine, the other is problematic.
*2nd EDIT*
Okay now I don't feel so dumb, I renamed the otacerts.zip thing but i am still getting reset
I did find an application that is call BN authentication service. I can't uninstall it from the normal App installer, anyways to get around this? Like ADB
*EDIT*
Ha I feel so dumb, I just needed to reboot, then change the names. So after i changed the names I rebooted again and its all good now
Thanks eyecrispy
* original*
I have a rooted nook color with a stock 1.0.1 rom, CWR, and a over clocked kernal. I have only 1 real problem, I guess besides not being able to download from the marketplace - my nook keeps on getting reset by B&N! They don't unroot it, and my recovery is still intact, but it really sucks not being able to connect to their shop. It's not that I would use their shop it's just that I accidentaly press it every now and then and it resets my device. I have to back up my device once everyday to make sure nothing gets deleted because sometimes, even when I don't press the shop button, I don't even have to press anything, it resets the device after its been connected to wi-fi for a while. Like the other day, i just set it down to go to the restroom, I come back to find it at the Android setup or the quick setup selection page. When I select Android setup when I press the little android nothing happens. When I select the B&N quick setup it, i can do that no problem. So now I just turn it off from there and load my back up through CWR.
Anyways, is there anyway to stop it from connecting to the B&N authentication service or something? I have seen people with similar problems, but no one seems to have it happen to them over and over and over again.
Plenty of folks have reported this continuously happening. Have you disabled OTA updates?
Sent from my Nook Color
eyecrispy said:
Plenty of folks have reported this continuously happening. Have you disabled OTA updates?
Sent from my Nook Color
Click to expand...
Click to collapse
Really? All th threads I have read people say it happened once but after a reboot it was fine. Maybe I just missed it. If you could please tell me how to disable OTA updates that would be a big help. Thanks
*EDIT*
Found what you meant, I am trying to use Root Explorer but am having no luck. I gave it superuser permissions yet it still wont let me changes any system files
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.
Brief history: I bought my Kindle Fire HD in November 20012. It was the first android device I had, so I did not know anything about it. My first search was for rooting, thing that I could make with the help of this forum. From that moment I started reading the forum because everything was new to me and interesting. Meanwhile my rooted kindle worked fine until at some point began to turn off alone. With help of some people of this forum, I was noticed that the problem were gmail notifications. I disabled the notification and the problem was fixed for several months . . . but after that she started doing it again.
There began -also with the help of people on the forum- an odyssey of endless tests, install and uninstall apps, upgrades, downgrades, battery calibrations, etc. until I decided to install TWRP and flash CM 10.2. Of course I learned a lot in this process and I am very happy with CM 10.2.
But what which leaves me sad, very sad and frustrated, is that remain turning off arbitrarily and randomly!!!!!
It can spend two whole days working fine until battery is low, but it can also happen that its turns off every 10 minutes. It is totally independent of the battery charge, although it tends to do more when it is around 50%!
After that, sometimes I can turn-it on normally, but sometimes I have to try 10 or 20 times because she turn off again while charging system.
If I plug-it (to wall or PC) she normally turns on and does not auto turn off again (while plugged).
My latest finding is that if when she turns off itself I shake-it vigorously I can then turning on normally. It's like there's a loose connection or something like that.
As I'm outside the U.S. have no chance of sending it to Amazon.
I really appreciate if someone have some idea about this problem.
I want to thank again all those who given me very good suggestions. It is thanks to them that I learned a lot.
I edit to coment another thing. When I use Corpse Finder from SD Maid, it detect 3 files: .adobe-digital-editions; kindle and Digital Editions ( the three placed in: /storage/emulated/0). No matter how many times I clean it, they always are found in a new corpse search. I don´t know if that its relevant, but is strange to me.
The same problem, HELP US
Elgari said:
Brief history: I bought my Kindle Fire HD in November 20012. It was the first android device I had, so I did not know anything about it. My first search was for rooting, thing that I could make with the help of this forum. From that moment I started reading the forum because everything was new to me and interesting. Meanwhile my rooted kindle worked fine until at some point began to turn off alone. With help of some people of this forum, I was noticed that the problem were gmail notifications. I disabled the notification and the problem was fixed for several months . . . but after that she started doing it again.
There began -also with the help of people on the forum- an odyssey of endless tests, install and uninstall apps, upgrades, downgrades, battery calibrations, etc. until I decided to install TWRP and flash CM 10.2. Of course I learned a lot in this process and I am very happy with CM 10.2.
But what which leaves me sad, very sad and frustrated, is that remain turning off arbitrarily and randomly!!!!!
It can spend two whole days working fine until battery is low, but it can also happen that its turns off every 10 minutes. It is totally independent of the battery charge, although it tends to do more when it is around 50%!
After that, sometimes I can turn-it on normally, but sometimes I have to try 10 or 20 times because she turn off again while charging system.
If I plug-it (to wall or PC) she normally turns on and does not auto turn off again (while plugged).
My latest finding is that if when she turns off itself I shake-it vigorously I can then turning on normally. It's like there's a loose connection or something like that.
As I'm outside the U.S. have no chance of sending it to Amazon.
I really appreciate if someone have some idea about this problem.
I want to thank again all those who given me very good suggestions. It is thanks to them that I learned a lot.
I edit to coment another thing. When I use Corpse Finder from SD Maid, it detect 3 files: .adobe-digital-editions; kindle and Digital Editions ( the three placed in: /storage/emulated/0). No matter how many times I clean it, they always are found in a new corpse search. I don´t know if that its relevant, but is strange to me.
Click to expand...
Click to collapse
I HAVE THE SAME PROBLEM, I DON´T KNOW WHAT´S HAPPEN. Can you fix it?
i have heard occasionally around on the forums of peoples power buttons and such doing this after a while, if that is the case you might be able to test for it but its kinda complicated. Is it sleeping or shutting off? If it's shutting off it would be interesting to see why but you'd have to have either a logcat running on the pc the entire time, a cat of the kmsg, or something of that nature running and turn off while its doing that, then you can find the root of the problem. If it won't do it while plugged in, cm has a way to wirelessly do adb commands. I think hashcode said in his sources theres a test binary for the buttons to see if they are doing anything, but i'd have to figure out how to cross compile it by itself if thats the case, unless its precompiled.
Yes, cassualy I fix it last week. I open the Kindle, looking the wires and conectors and close again. And voila . . . fixed!
Enviado desde mi Amazon Kindle Fire HD mediante Tapatalk
[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.