Is there a way to remedy this? If I let my NC fall asleep while it's running a non-stock launcher ( I've tried LauncherPro, Go Launcher, and I'm currently using Zeam) it won't wake up. I have to power it back on to bring it back to life. Is this a normal problem that people have been having? I've looked through other threads but haven't seen anyone mention it.
Sent from my LogicPD Zoom2 using XDA App
Never happened to me and I have been using a 3rd party launcher since early december. I would do a factory reset then update then root with auto nooter
http://forum.xda-developers.com/showthread.php?t=880785
Unlikely anything to do with third party launchers, read that thread. And this wiki page covers it. http://www.nookdevs.com/NookColor_Issues
i have a fix for you and anyone who might have this problem
The problem lies with the soft menu keys not the launcher. My nook would reset after every sleep with wifi on. It was really worrying me. Somhow i realized it had to do with the soft keys that come with the autonooter. Remove that apk and install from the market button savior. It will save your nook
Let me know if it worked for you. I haven't had any problems after this change.
I'm using Button Savior and still get very frequent random reboots.
The only thing that seems to have stopped my reboots is the Settings Profile Lite that turns off wifi when my screen is off. I'm at 1 day 22 hrs 44 min and counting. Before that, I was consistently rebooting at least once every 24 hours, if not more.
I'm trying the Settings Profile Life method. I'll let the internet know how it went.
Sent from my LogicPD Zoom2 using XDA App
eyecrispy said:
The only thing that seems to have stopped my reboots is the Settings Profile Lite that turns off wifi when my screen is off. I'm at 1 day 22 hrs 44 min and counting. Before that, I was consistently rebooting at least once every 24 hours, if not more.
Click to expand...
Click to collapse
Interesting find.... I'm going to take this idea another direction and see if I can recreate it with Tasker.
Use SpareParts to set WiFi sleep to never. If using SetCPU and the problem still persists, you may wish to (temporarily) uninstall to see if the problem goes away. If so, it was likely the program, settings used, profiles, etc. My NC doesn't do this when it goes to sleep with the WiFi on running Zeam. The battery stats often show 3 days before I end up charging it. If I didn't use it as much as I do, it would likely show up as longer.
I installed Settings Profile Life. It's been working great. I haven't had a reboot since. Thanks for the advice.
Sent from my LogicPD Zoom2 using XDA App
natoe33 said:
I installed Settings Profile Life. It's been working great. I haven't had a reboot since. Thanks for the advice.
Sent from my LogicPD Zoom2 using XDA App
Click to expand...
Click to collapse
I fear that we are only dealing with the smoke and not the fire when controlling the Wifi in this manner.
I had a semi-brick that took a whole day to fix and re-do. Upon re-rooting, I used AutoNooter and a modified version of the Auto Config script that excluded : (copied from my other post)
-YouTube removal (not sure why we are even removing it and I have a suspicion that removal may be causing the issues... Was YouTube only included in the Autonooter to allow entry of Google Account?)
-SoftKeys removal & LauncherPro installation
-Boot Animation change
-A bunch of the installed apps including Facebook, taskkiller, quickboot, vol master.
I've been reboot free for 21+ hours now, where I used to get them about once an hour or so. (BTW, I haven't touched the wifi settings, I have SoftKeys 3.0.0 running, no setCPU, haven't visited The Store, and I use ADW Launcher EX)
cal3thousand said:
I fear that we are only dealing with the smoke and not the fire when controlling the Wifi in this manner.
Click to expand...
Click to collapse
Oh, absolutely. Setting Profiles is just a Band-Aid. The underlying problem is still there and AFAIK no progress has been made in identifying it. I expect it's being caused by one of the many unnecessary things have been rolled into the automatic rooting scripts but have no way to identify it since my NC has turned into a very late Christmas gift that I still don't have yet.
In any case, I think the rooting scripts need to be greatly simplified down to the bare essentials to get root and nothing else, and then have optional additional scripts to add the various other things that some people want and others don't. So long as the rooting and feature-additions are being combined into a single package, it's going to be pretty hard to narrow this down.
RoboRay said:
Oh, absolutely. Setting Profiles is just a Band-Aid. The underlying problem is still there and AFAIK no progress has been made in identifying it. I expect it's being caused by one of the many unnecessary things have been rolled into the automatic rooting scripts but have no way to identify it since my NC has turned into a very late Christmas gift that I still don't have yet.
In any case, I think the rooting scripts need to be greatly simplified down to the bare essentials to get root and nothing else, and then have optional additional scripts to add the various other things that some people want and others don't. So long as the rooting and feature-additions are being combined into a single package, it's going to be pretty hard to narrow this down.
Click to expand...
Click to collapse
So use the script to root it, not auto-nooter, and see if it also happens. You, or someone..... For me, I'm getting a pretty steady 2 days of uptime, and it's still 100% stable while using it, so it's good enough for me.
Related
I have tried searching the forums but have found nothing yet, so I was hoping someone could help me. I am currently using Enomther's rom, but this has happened on every rom I've tried (Desire, Cyan, etc.). My problem is the Nexus One is running 100% of the time. In comparison, the screen was on for 5.2% of the time. And I have definitely noticed the battery. Even if in standby, it loses 10-20% battery an hour. By the time I make it home from school, I have about 20% battery left, with almost no usage whatsoever. I've checked to see if it's any apps that won't close, but my highest used app was only a few minutes according to spare parts. Cpu usuage is barely visible as well in spare parts.
List of Apps:
Advanced Task Killer
AK Notepad
Any Cut
Astrid
ASTRO
aTrackDog
Barcode Scanner
Battery Graph
Beautiful Widgets
Call Meter NG
Classic Simon
Mathpad
Contacts Clean-up
Dictionary.com
eBuddy
Engadget
FMyLife Official
FotMob 4.6
Funny Jokes
Google Sky Map
Google Translate
GPS Status
jkAppSwitch
Maps
Meebo IM
Metamorph
MountUSB
Movies
MyBackup Pro
Opera Mini 5 Beta
Paypal
Picsay
Pkt Auctions eBay
Places Directory
Quick System Info
Quick Uninstaller
Replica Island
Robo Defense
Rom Manager
Screebl Lite
SetCpu
Shazam
ShopSavvy
SMS Backup & Restore
Solitaire
Speed Test
Timeriffic
Titanium Backup
TTS Serivce Extended
Tube Downloader
Urban Dictionary
Urbanspood
WikiMobile
Wireless Tether For Root Users
World War
XDA
Zedge
Looks like an application is holding the wake lock. Instant Messengers are good candidates for draining the battery. In my experience, Meebo loses connection frequently, and eBuddy has a mode to keep the connection, but it drains the battery very fast (AFAIR it has a mode that's easier on the battery by checking for messages every 15 minutes, but that's not all that instant anymore).
Good job you have AnyCut installed.
Use it to place a shortcut to the 'Testing' app (or dial *#*#4636#*#*), and use that to look at your battery history.
This will be able to confirim if your N1 is indeed staying awake, and if you use the 'partial wake usage' drop down box, it will tell you what's keeping it that way.
For partial wake usage, the only thing that pops out Android System which has a full bar. Nothing else is above a sliver.
Since you have titanium backup, why not make a backup, completely wipe your phone, and see if the problem persists? Then, add components at a time and see when the problem reappears. ie ROM -> a few apps -> a few apps -> etc. This will narrow down your search and hopefully pinpoint the problem.
You also might wanna look at logcat (e.g. via aLogCat), sometimes there are a lot of messages of runaway applications.
Here's my logcat
pastebin.com/2fj74zPn
No spare parts?
Downlaod it and try setting the end button behavious to go to sleep.
Seems like an obvious thing, but its worth a shot if you haven't already tried it.
izmar said:
No spare parts?
Downlaod it and try setting the end button behavious to go to sleep.
Seems like an obvious thing, but its worth a shot if you haven't already tried it.
Click to expand...
Click to collapse
Yep, of course I have spare parts. I set that, but what exactly is the end button?
Edit* I've uninstalled every app on my phone, and yet the problem still persists. Running 100% of the time. What the heck is wrong with my phone?
panzival said:
Yep, of course I have spare parts. I set that, but what exactly is the end button?
Edit* I've uninstalled every app on my phone, and yet the problem still persists. Running 100% of the time. What the heck is wrong with my phone?
Click to expand...
Click to collapse
I think your best bet us to just wipe everything, and reinstall the rom. That should get things going smoothly.
do you have trackball succession mod? that may be the reason.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
SiNJiN76 said:
do you have trackball succession mod? that may be the reason.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
No, but I did have trackball wake enabled. Would that matter? Also, I've installed Cyan and the problem seems to be gone, although battery still isn't great :/
I would figure that trackball wake will keep waking your phone when you accidentally hit the trackball when the phone is in your pocket or bags?
panzival said:
No, but I did have trackball wake enabled. Would that matter? Also, I've installed Cyan and the problem seems to be gone, although battery still isn't great :/
Click to expand...
Click to collapse
One thing to check that I've run in to twice (unfortunately) is constant "syncing" of email. I only noticed it because the email app constantly showed the syncing circle (not in the notification bar, in the app). Clearning the storage/settings for email cleared it up, but it took a few days to find out what was causing it to never sleep.
Grooby97 said:
I would figure that trackball wake will keep waking your phone when you accidentally hit the trackball when the phone is in your pocket or bags?
Click to expand...
Click to collapse
Yes but my phones running 100% of the time and my screens running 1/20 of that time. Surely my screen on time would increase as well? As well I'm sitting in class half the day and know for sure that I'm not hitting the trackball.
krohnjw said:
One thing to check that I've run in to twice (unfortunately) is constant "syncing" of email. I only noticed it because the email app constantly showed the syncing circle (not in the notification bar, in the app). Clearning the storage/settings for email cleared it up, but it took a few days to find out what was causing it to never sleep.
Click to expand...
Click to collapse
Thanks, I'm going to look into this. Would this correspond to UID 10014 or Media having extremely high network usage as well? I just noticed these two things constantly have full network usage bars but don't know exactly what either are. How would I clear the settings/storage? I'm using a Desire Rom now if it matters.
What is going on here? It either freezes when:
1) slide-to-unlocking
2) switching between programs
3) google sync icon shows up in notification bar
4) in apps
Need to pull battery all the time! What's going on?
I've had this ever since the FRF50! I'm so annoyed and want to go back to 2.1, but I do love the battery life I'm getting with FRF91.
Any help please?
Sorry, realized I posted this in the wrong forum. Can MODS transfer the thread to Q&A?
I'm getting freezes on the same situations you have posted. However not with the same frequency as you. Mine is 1-2 daily.
Sent from my Nexus One using XDA App
strange, my phone is stock and ive had none of these issues, i actually thought my battery life had worsened since 91. It seems like the green meter doesnt drain as quick but the actual percentage drains faster than ever for me, at least i think so
This should unusual and should not be happening. Wipe everything and reflash.
That's Strange... I haven't had any freezes since installing the FRF91 OTA.
galaxys said:
That's Strange... I haven't had any freezes since installing the FRF91 OTA.
Click to expand...
Click to collapse
Yepp, same here! Never had a single freeze/lock-up since I manually updated to FRF91 from EPF21.
Hardware Issue
Seem to me you either have a defective apps or widget, a defective SD or a hardware issue like defective video ram or something like that, you could try to use a benchmark app like quadrant this may help pinpoint the exact subsystem that cause crash (video, cpu, ram) and try running stock OS with almost nothing loaded ...
This is assuming you are running from a clean install, When you have issue it's always a good idea to clean install (full wipe etc...)
Try to go to bootloader (press and hold trackball when power on), then go to recovery and clear out cache.
Mine is stock and sometimes it freeze when I tried to unlock. I had to turn the screen off and on 1-2 times to make it work again
Following your advice and let me monitor for a day or so. If doesn't work I will wipe everything and reflash.
Thanks!
mingkee said:
Try to go to bootloader (press and hold trackball when power on), then go to recovery and clear out cache.
Click to expand...
Click to collapse
Sent from my Nexus One using XDA App
wipe everything and flash both FRF91 and the latest gapps.
1. How many app you have and 2 are they on your SD? If you have alot of apps ittaking up your internal space causing you to freeze.
Sent from my Nexus One using XDA App
I actually installed spare parts the same day i installed stock frf91, so i am not sure who is the culprit. It didnt happen today, but froze yesterday and the day before.
turned off all the animations (transition/window) to get maximum speed out of my n1 using spare-parts maybe thats causing the craziness no?
Same here, 2 or 3 times per days.
I have found that cpu is burned by com.android.email ! This apps eat all cpu power when there is no wifi/data connections available and it try to sync mail...
The phone become unresponsive or very slow until connection return or I kill the app.
Xialis said:
Same here, 2 or 3 times per days.
I have found that cpu is burned by com.android.email ! This apps eat all cpu power when there is no wifi/data connections available and it try to sync mail...
The phone become unresponsive or very slow until connection return or I kill the app.
Click to expand...
Click to collapse
I have same issues with that process. Setting both gmail and exchange to PUSH solves the problem.
still froze twice today....wiped + reflashed FRF91..now resetting up my phone .... hope this will stop the freezes...will report back
Xialis said:
Same here, 2 or 3 times per days.
I have found that cpu is burned by com.android.email ! This apps eat all cpu power when there is no wifi/data connections available and it try to sync mail...
The phone become unresponsive or very slow until connection return or I kill the app.
Click to expand...
Click to collapse
I think I found a solution.
Go to email account, settings
Auto check->off
DarkDvr said:
I have same issues with that process. Setting both gmail and exchange to PUSH solves the problem.
Click to expand...
Click to collapse
Thanks, It works
I was wondering if anyone else's Captivate has shut down automatically? It happened 3 times yesterday the screen goes into standby mode but if you try waking it up you had to pull the battery.
Last night I let it completely drain then completely charged it. When I picked it up it read 99% battery immediately. I went to get ready for work and check my email and it was shut off. I had to restart it again. Since then it seems as if the battery is lasting longer.
random shutting down
Okay so i had this problem but it only arises for me when i do a few things. i have spent hours scratching my head about what it could be and through process of elimination i found on my phone it was one of two things.
1.) make sure that if you are using the auto kill feature in ATK that its not set to anything above safe
2.) if your using setcpu with profiles selected and have a very low profile for when the screen is off then try ramping that profile up a little bit to give the phone a chance to run background processes a little easier and actually wake up when you want it to!
hope it helps and if you give me info about what is going on then that should help us help you.
ice3186 said:
Okay so i had this problem but it only arises for me when i do a few things. i have spent hours scratching my head about what it could be and through process of elimination i found on my phone it was one of two things.
1.) make sure that if you are using the auto kill feature in ATK that its not set to anything above safe
2.) if your using setcpu with profiles selected and have a very low profile for when the screen is off then try ramping that profile up a little bit to give the phone a chance to run background processes a little easier and actually wake up when you want it to!
hope it helps and if you give me info about what is going on then that should help us help you.
Click to expand...
Click to collapse
I havent been using ATK at all. Also does SetCPU really work with the hummingbird processor? When it boots it always kicks down to 19.2 which is obviously too low. I removed it just in case. I also set it back to the default settings. I would really enjoy SetCPU to save battery if it works of course. I thought it only works on HTC devices and Motorola devices?
i had setCPU on my phone yesterday and it was freezing like you describe when trying to bring it out of standby. I pulled the battery twice before i said F-it and took the program off. If you were using setCPU i'd say that was your problem.
domin8 said:
i had setCPU on my phone yesterday and it was freezing like you describe when trying to bring it out of standby. I pulled the battery twice before i said F-it and took the program off. If you were using setCPU i'd say that was your problem.
Click to expand...
Click to collapse
I deleted SetCPU and I thought it might be Screebl so I disabled it. Sure as hell it just went to a black screen and shut off again. God this is beyond annoying. I dont want to have to bring back this great phone but I need the phone to work.
We've also got to think, Samsung just released this phone. The more we do to it from the market, the more things are gonna happen.
Most devs haven't had the time to really test and relay bugs from this phone that would cause other errors.
madjsp said:
We've also got to think, Samsung just released this phone. The more we do to it from the market, the more things are gonna happen.
Most devs haven't had the time to really test and relay bugs from this phone that would cause other errors.
Click to expand...
Click to collapse
Yes but if I am correct none of these issues will be fixed until they decide to release FroYo?
EDIT: I just tried removing the MicroSD to see if that resolved the issue. Shocker...it didnt...
spyz88 said:
I was wondering if anyone else's Captivate has shut down automatically? It happened 3 times yesterday the screen goes into standby mode but if you try waking it up you had to pull the battery.
Last night I let it completely drain then completely charged it. When I picked it up it read 99% battery immediately. I went to get ready for work and check my email and it was shut off. I had to restart it again. Since then it seems as if the battery is lasting longer.
Click to expand...
Click to collapse
This has happened to me once. Came out of a meeting, pulled it out of my pocket, and couldn't get it to wake from sleep. I have not installed SetCPU, so it's not that. Not sure what the root cause was.
What apps do you have installed would probably be the more relevant question. And what have you changed?
Mine is doing the same **** and it is driving me NUTZ!!! I thought SetCPU first so I uninstalled and rebooted. Phone is still doing it. Please someone figure this out quickly. I am going through my apps one by one and uninstalling them to try to pinpoint the problem. Subscribing to the thread.
Interesting.... I haven't heard this happen to me yet so its probably an application or process your guys all have in common.
Sent from my SAMSUNG-SGH-I897 using XDA App
I have a feeling it is setcpu. I just did a reboot after installing and now it is not happening. Cross my fingers!
I'm having the same issue and I never had setCPU installed. sucks..
-Teklock
Like a lot of you, I started uninstalling my apps one by one when this happened. It stopped restarting after I finally uninstalled Launcher Pro. After that, the phone stayed on the whole night last night. It's weird because it worked with Launcher Pro for a good 2 days.
I'm also experiencing this issue, ad i've only downloaded a few apps.
Has anyone exchanged their phone over this yet?
Teklock said:
I'm having the same issue and I never had setCPU installed. sucks..
-Teklock
Click to expand...
Click to collapse
I reflashed to stock firmware and I'm still having an issue. I noticed that if you take the battery cover off the battery and push on it then it seems like it has a little give to it. Can anyone who is not having this problem confirm? Also, anyone who has this issue, please see if your battery has a little give to it.
It should be on the side WITHOUT the contacts. Also, if this doesn't work I'm bringing the phone back. I already had a problem with the first one and since this is my 2nd exchange AT&T wont exchange it anymore. They told me I need to go through the warranty. They are out of their minds the phone isn't even a week old. Never had these problems with HTC...
EDIT: I uninstalled ADW Launcher as a test to see if thats it.
EDIT 2: Make sure the battery door is covered tightly. I pushed mine all the way down until it clicks. Hold it down and then close the slider. I think this actually might fix the issue.
Anyone figure out why this keeps on happening? I've reflashed the stock as well and it still occurs randomly.
Strange this dosnt happen to me, and i installed setcpu(performance governor 1ghz/800mhz) but uninstalled it after seeing that it ****'s up gles 2 rendering...
I found this thread via Google search, and I just wanted to add that my phone started doing this last night, however, I have not added anything to my phone, nor is it modded in any way. It's completely stock. The only thing I have done thus far was remove all of the extra home pages and rearrange some app icons, and that was on Thursday and Friday. It does it both when it goes to sleep normally or if I hit the sleep/power button.
I narrowed mine down to SetCPU being underclocked while asleep. Bumped up the minimum clock and took off the profile I had set, phone hasn't rebooted in 4 days.
Hey guys, my nookcolor has been randomly rebooting since i rooted it. Never while i was using it, i just sometimes hear the bootup sound, and look to find that my book is now on.
Im just concerned this will affect my battery, and i also don't want it rebooting while im using it.
I noticed it doing this one time, but right after i powered it off. In use, it has never rebooted on me (yet)..
This is why we so desperately need a custom ROM. Remove the B&N bloat, and start with a clean 2.2 (or even 2.3 now) base, and really open her up..
Divine_Madcat said:
I noticed it doing this one time, but right after i powered it off. In use, it has never rebooted on me (yet)..
This is why we so desperately need a custom ROM. Remove the B&N bloat, and start with a clean 2.2 (or even 2.3 now) base, and really open her up..
Click to expand...
Click to collapse
I still want to use the B&N stuff. Any rom that emits them, I will not be installing.
I think it likely that there are NC users in both camps-
Those who want the B&N stuff and those who don't.
I am one of those who don't; the Nook for Android software does better for reading ePub, imo and I am rarely near a B&N store.
Right now we have root and Market plus B&N and I would guess (could easily be wrong) that the first custom roms will be pure Android with no B&N.
We will probably end up with an option to set while flashing: retain B&N customizations or straight Android.
I base this guess on what I have seen in the other roms for various devices (mainly Droid) I have looked at.
Same here. If I want to read B&N books, I could still use their Android app on a custom ROM.
After switching to Cyanogen on my phone, it's been quite relaxing to not have to worry about provider updates bricking the thing or otherwise screwing up the rooted customizations (or just randomly resetting the thing back to factory defaults because I started up one of their apps and it got confused). Not to mention that the CM team does a far better job supporting the device than the manufacturer and my service provider does.
And yes, like other Android devices, there will probably be ROMs in both categories: completely built from scratch with no B&N portions at all, and improvements on the B&N system to add more functionality.
Fair enough for those that are interested in the reader portions - i have to admit, i bought this as a tablet, with literally 0% in it as an e-reader; i already have a Sony 505 for that. I may use it on occasion, but only as an afterthought.
However, this topic is really drifting - perhaps we should just bring it back to the rebooting issue?
Yeah, I installed the Uptime Widget on my NC today and picked it up a few ago and its uptime was 1:30; max 15h (from before it rebooted 90 minutes ago). I'll keep running it.
What we need to do is get a logcat when it happens.. So maybe overnight I'll leave it running or something. It just rebooted on me and I was semi-watching it, didn't even notice but Uptime Widget was reset to 7m up, 15:30 max..
I have started up a logcat and I'm going to leave it running while I get ready to go out for the day.. Although I just installed and fiddled with Google Earth, which failed badly, so I wonder if it caused some problem. Also saw it happen after playing with Google Maps, so I wonder about Location stuff maybe doing it.. Dunno. I just launched Maps a few ago and it's been up since. Hopefully a logcat will capture some info.
I have noticed that I've seen some crashes that don't show the Crash dialog.... TweetDeck is particularly bad about crashing viewing some Facebook posts, and in this case it just goes black for half a second then back to the list of posts. A logcat shows it crashed. But I don't know the two are related (not having the crash dialog stuff and the reboots that is).
I had it reboot on me twice last night, one time I didn't know about it until I picked it up later and noticed the uptime widget was down to some 30 minutes, and another time right before bed I hit the power button and about 10s later I saw the boot up text and a reboot happen.
Still haven't caught it on logcat.
My doesn't reboot spontaneously, but it does "lock up" and won't turn on with the power button from standby occasionally. If I remember to use the Nook Button to wake from standby, I don't seem to have this issue. If I use the power button, and it won't wake, I need to hold it down for ~15 seconds and it reboots.
AFIAK, it has done this since I purchased it (I rooted after about 1 hour with the NC in my hands).
Mine has never reboot WHILE I'm using it, it's sneaky about it. But I suppose I'd much prefer it reboot while I'm not using it than while I'm using it; I have yet to have it do a full reboot while using it.
Trying to set up a Delicious account.. yeah, that rebooted the Java VM. But only time I've made it reboot at all.
Hahah, damnit, it just rebooted after it went to sleep. I seriously think it has something to do with going to sleep. I've been sleeping it and waking it repeatedly on adb logcat and it won't crash. Figures.
I had this same issue a while ago. I don't have the logcat from it, but from what I could tell is was some sort of error coming from the system dimming the brightness before turning the screen off. I had Extended Controls installed and was using the widget to adjust my brightness. Whenever the screen would dim before turning off I would get a reboot. I have since uninstalled it and have had no issues with reboots. I'm not sure if this is the issue youre facing but thats my story.
isolated_epidemic said:
I had this same issue a while ago. I don't have the logcat from it, but from what I could tell is was some sort of error coming from the system dimming the brightness before turning the screen off. I had Extended Controls installed and was using the widget to adjust my brightness. Whenever the screen would dim before turning off I would get a reboot. I have since uninstalled it and have had no issues with reboots. I'm not sure if this is the issue youre facing but thats my story.
Click to expand...
Click to collapse
Actually not using any of those on mine.. I have Beautiful Widgets in ADW and Beautiful Widgets + Note Widget in WidgetLocker.. Not adjusting the backlight at all either, in fact I don't think I have at all since getting it now that I think about it.
I have the same issue: rooted Nook Color reboots occasionally and it does seem to do it whenever I put it to sleep or it goes to sleep by itself (when the screen dims). It hasn't rebooted while in use, but it does reboot occasionally when left alone. Have no idea why.
From apps that control dimming I have Advanced Task Killer installed besides the stock app that controls dimming... Could it be the issue? I will uninstall Advanced Task Killer and see if that help.
Otherwise I love my rooted NC. It's fast, beautiful and works great as an E-reader and an Android tablet.
to summarize: Do you think it's the hardware issue or software. I've heard of people who have non-rooted (stock) Nook Color having the same rebooting problem, but apparently it doesn't have to do with rooting. Do you think it will adversely affect the Nook?
If anyone finds a solution please post here. It would be tremendously appreciated.
Thanks and have great holidays.
mastroiani said:
I have the same issue: rooted Nook Color reboots occasionally and it does seem to do it whenever I put it to sleep or it goes to sleep by itself (when the screen dims). It hasn't rebooted while in use, but it does reboot occasionally when left alone. Have no idea why.
From apps that control dimming I have Advanced Task Killer installed besides the stock app that controls dimming... Could it be the issue? I will uninstall Advanced Task Killer and see if that help.
Otherwise I love my rooted NC. It's fast, beautiful and works great as an E-reader and an Android tablet.
to summarize: Do you think it's the hardware issue or software. I've heard of people who have non-rooted (stock) Nook Color having the same rebooting problem, but apparently it doesn't have to do with rooting. Do you think it will adversely affect the Nook?
If anyone finds a solution please post here. It would be tremendously appreciated.
Thanks and have great holidays.
Click to expand...
Click to collapse
I suspect it's a software thing, as it doesn't randomly reboot in use, it ONLY seems to happen going into standby, and I have YET to make it happen connected USB for adb.
You know actually, I think alogcat can log automatically now, maybe I should try that.. but it'd have to run for a day or so, as I only see this happen like twice a day at most.
Do you have setcpu installed? I was getting random reboots when I had it on conservative. Switched to ondemand for all profiles, and no more reboots!
wvcachi said:
Do you have setcpu installed? I was getting random reboots when I had it on conservative. Switched to ondemand for all profiles, and no more reboots!
Click to expand...
Click to collapse
I myself had not played with SetCPU at all. So had you in the past and set it to conservative, and switched it back, or you switched it from its defaults? Reminds me, per my observation that it never has rebooted while on AC or USB, was there a default profile when plugged in that it's set to ondemand vs conservative? This could start making some weird kind of sense. I'll try it, but using something called CPU Tuner since it's free..
EDIT: I looked on USB and on Battery, both times was conservative, so looks like that's the default... Does the Nook have an automatic switching utility like cpuspeed in it? Hmm.. /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor is the file if anyone else wants to look.
BTW, has anyone on 1.0.1 auto-nooted etc not seen these random sneaky ninja power-off reboots? I swear mine waits until I'm not looking and reboots. I've only SEEN it do it once or twice, but in the last 5 or so days it's rebooted at least 10 times while powered off. Again NEVER while I'm using it, so I'm at least thankful for that. If it were rebooting while using it that would not be acceptable.
I have the Uptime Widget, kinda wished I had an uptime graph to see if there is a pattern.. I'm about 99% sure it never happens when plugged in AC or USB.
EDIT2: IT IS CLEARLY MOCKING ME. It just rebooted after I peeked at the governor files and let it idle to sleep.
I have the same random reboot problem since I upgraded to 1.0.1 and used auto-nooter. I only see it when it goes to sleep...or so I thought. This morning I heard it reboot and i hadn't touched it since last night. FYI, it was not plugged in when it happened. Thankfully it never reboots while in use.
Oh...ad i havent used any CPU clocking tools. Also...never saw this on 1.0. So weird but I am sure someone smarter than I will figure it out.
UPDATE- Just got out of the shower and while getting dresses...heard the Book reboot twice within a minute or two.
Wondering if its an app that is causing a fatal crash when it tries to update.
Sent from my Nooxus One using Tapatalk
I haven't had a random reboot in 3.5 hours and i have used the Nook on and off. I did remove my email account from the Google email app (not gmail) and its been good for awhile now. I will update if this changes but I am feeling confident this fixed the random reboot.
Sent from my Nooxus One using Tapatalk
rckymtnrfc said:
I haven't had a random reboot in 3.5 hours and i have used the Nook on and off. I did remove my email account from the Google email app (not gmail) and its been good for awhile now. I will update if this changes but I am feeling confident this fixed the random reboot.
Sent from my Nooxus One using Tapatalk
Click to expand...
Click to collapse
I've had one unexpected reboot today that I know of, I think this has helped, although I keep finding my Wifi turned off, even though this program I installed is only set to turn it off when the battery is extremely low. So I changed that profile and it hasn't turned itself off since, so seems to me maybe the battery reporting is a little wonky sometimes.
I've been watching, and I'll keep an eye out, but I think wvcachi is onto something.
BTW, the Nook has been primarily idle for the last 5 hours, just popped it on a few times to read an email, check on something, or see if it reboots so I haven't used it a bunch but it's lost a whopping 2% battery in that time. I also disabled the Phone stuff too, per this thread:
http://forum.xda-developers.com/showthread.php?t=883908
I am at 6.5 hours now....no rebooting so far.
Sent from my Nooxus One using Tapatalk
As stated, screen will not go off via timeout or power button tap. Power button is recognized and will bring up shut down menu like normal.
Device is rooted (thanks DG) and had been running well for over a week. Defrosted all apps from tibu in case I got over zealous but no better. A factory reset has not cleared it up either. Hoping the oneclick from the root package will correct the issue, but thats not until I get home later this evening.
Has anyone experienced / recovered from this issue?
Smart stay is turned off
I've had noticeable lag like a few seconds and sometimes I wonder if it's going to shut off but it always does. Better set a dark lock screen wallpaper to conserve your battery
Sent from my SAMSUNG-SM-N900A using xda app-developers app
I know this is kind of basic, but what is your setting here:
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Thanks for the thoughts.
I had already gone through the standard - double check the settings, remove recent apps. When all that failed and a factory reset still didn't clear it up I was beginning to worry about some kind of hardware damage (don't see how since I treat it better than my child ).
Fortunately the one click from the root seems to have restored proper operation. Back to rooting and rebuilding!
3496255310
papashex said:
Thanks for the thoughts.
I had already gone through the standard - double check the settings, remove recent apps. When all that failed and a factory reset still didn't clear it up I was beginning to worry about some kind of hardware damage (don't see how since I treat it better than my child ).
Fortunately the one click from the root seems to have restored proper operation. Back to rooting and rebuilding!
Click to expand...
Click to collapse
I'm having the same problem, I rooted through vroot.... what do you mean one click fixed it little my incite would be helpful....
thank you
Mine just did this, scared the hell out of me It also didn't go into deep sleep before it started. (Not rooted).
Pulled the battery, waited 30 seconds, plugged it back in.... same thing. Waited a few minutes, seems to have sorted itself out.
Scary....
This is definitely a software bug and it is related to the Headphone detection bug that people are having too (it's actually the same bug causing both issues). This happens to me quite often after I restart my phone. It's kind of like the phone hangs during the startup process. I've also noticed that the wifi/bluetooth status that was present before restarting the phone (i.e. whether they on/off) doesn't get applied until the bug sorts itself out.
For me sometimes this works: open an app like Chrome and then hit the home button to get back to your launcher. This works 95% of the time for me. I'm wondering if it has something to do with not having Touchwiz set as the default launcher.
I'm experiencing this same problem. If I don't manually turn the screen off by tapping the power button, the screen will not timeout.