yashsingh1/xdaforums huggingface dataset:
[Nook Color General] thereddog:
I just flashed my NC back to stock with the 8x reboot method. It flashes to 1.0.0. While I was downloading 1.0.1 on my computer, I noticed that the Nook went to sleep and actually rebooted. I was having issues while it was rooted, and I figured it was the cause of it.

Now I'm not so sure what the cause is. (I haven't noticed any reboots after uploading 1.0.1 though..)

Edit: Just rebooted itself even having 1.0.1 on it..
[Nook Color General] frenzisor:
Glad it worked. My nook feels a lot happier now.
[Nook Color General] GorillaPimp:
Yeah I like having apps download or sync while the device isn't in use. I tried uninstalling softkeys and that doesn't work either. I'm down to one reboot every 29-31 hours which is okay but annoying.

So you're 100% reboot free with wifi disabled on standby? How long has it been? Do you power cycle your NC often? What's your longest uptime without reboot?

Could you possibly tell me what mods you've used on your device? Auto-nooter, scripts?

Do people who haven't rooted have random reboots? (I only went unrooted a week and can't remember if it did or didn't reboot.)

Thanks for updating the wiki and these threads.
[Nook Color General] jadambpharm:
I've been running this (wifi off fix) since i made my original post about the fix and still have yet to have a reboot. i rebooted it myself a few times the other day. i had at least a couple of days with no reboots before rebooting it myself. mod-wise, i did autonooter, one of the auto-config scripts, cell service mod, screen density mod, installed cwm recovery, had soft keys, now have button savior, and just about every other mod that's out there. 100% reboot free :-)
[Nook Color General] khaytsus:
My uptime is 2 days right now, as it's been two days since I went from using CPU Tuner to not using it, so I uninstalled it and rebooted the NC to make sure it wasn't being used. And I turn on the NC quite a lot looking at little things.

I updated to 1.0.1, ran auto-noot, and have since then installed a bunch of different apps. I use Softkeys as my Home, which in turn really launches ADW, but lets me double-press the Nook key for the softkey popup so I can access the menus/back button from any app even if it hides the status bar.

Not much else I can say.. Several people have said the NC stock, unrooted does reboot, so I suspect if used the same way the NC out of the box would reboot.
[Nook Color General] eyecrispy:
Just had something strange happen. got done using my NC and turned screen off and put it down. Looked down a min later and saw Droid splash screen. Thought it rebooted but my uptime still showing over 3 days. So, did it actually reboot? Ideas?

Sent from my XDA app on my Nook Color
[Nook Color General] khaytsus:
The Java VM crashed and rebooted, but not the device.
[Nook Color General] eyecrispy:
Oh ok. That makes sense. Wow. And all I was doing was checking Facebook.

Sent from my XDA app on my Nook Color
[Nook Color General] cal3thousand:
Only one day

I had a full day without a reboot

then it went 12 hours

now i got 2 in the last 2 hours.

Only things I did differently today was use ADB wireless and I also turned off USB automounting. The USB automounting thing seemed to increase the reboot frequency. And since the uptime widget resets, these are not just kernel panics.

Anyone else shut off automounting and getting reboots often?
[Nook Color General] cal3thousand:
Tasker Confirmation

OK... until I or should I say "we" extinguish the fire, I'm going to deal with the smoke.

I made 2 tasker profiles that seem to thwart the reboots by turning off wifi when the display is off and then turning it back on when the display is back on.

I will report back here on its effectiveness as I get more time running.
[Nook Color General] Canadoc:
Was getting frequent reboots until in spare parts app i changed wifi sleep to never. Now no reboots in over 35 hours.
[Nook Color General] eyecrispy:
I'm at 4 days 7 hrs. The JVM crashed twice while I was on Facebook but no full reboot in days. And tthe last one I did was intentional.

Sent from my XDA app on my Nook Color
[Nook Color General] TainT:
I have two Nook Colors. Both where rooted immediately after getting them so i dont know if they would have had issues prior to rooting. The first one I rooted the hard way. The second one using auto-nooter. The auto-nooter one suffers from the crazy "sleepy" re-boots. As a matter of fact I cant set it down for more then 10 minutes or so without it rebooting.

I just did the spare-parts set wi-fi sleep policy to never trick and its no help.

*fingers crossed while I un-install news and weather widgets*

No Joy....Re-boots Abt every 8 minutes :-(
[Nook Color General] cal3thousand:
So your non-Auto nootered one works fine? hmm.... I'd be willing to go through all that trouble to keep my wifi on and no get reboots.

BTW, as of this post I am at 2d 13hrs+ since last reboot. And the last 2 were intentional, so I would be above 3 days now with the Tasker settings turning off WiFi with the screen. I don't mind this too much as WiFi is pretty quick to turn on and connect, but having push notifications work would be a nice plus.
[Nook Color General] IM0001:
Does anyone use a task manager to close apps that are running before they sleep their device? I use ES Task Manager to kill all which gives me a fresh start almost plus is also resets the extra menu to show new apps either recently installed or removed.
[Nook Color General] khaytsus:
Turn off wifi manually before turning off the screen. If that fixes it, try setting up Setting Profiles as described in this thread.

My uptime went from 4 hours on average to 4 days on average..
[Nook Color General] TainT:
Yeah I read the whole post....thinks for the advice.

I`d rather have wi-fi working though
[Nook Color General] shareef:
My NC was rebooting on it's own every 3 or 4 hours.. I re-rooted it using auto-nooter and then upgraded to 1.0.1. After doing that, the reboots were much less frequent, but eventually it rebooted itself just after 24 hours. After that, I started manually disabling wifi before turning off the screen and now my NC has yet to reboot on its own. It's been running for more than 2 days and even longer if I hadn't rebooted it intentionally on my own. I'm convinced the "fix" was to disable wifi before turning off the screen.
[Nook Color General] spikey911:
I had 2 Nooks, both which I thought was soft keys, but turned out not to be.

My third Nook was rooted the same as the rest, has all the same stuff as the others has not rebooted ever.

Not sure if it is a hardware issue or software, but my latest Nook has a starting serial number of 2005....

Just adding to the pot...
[Nook Color General] themirthfulswami:
I had random sleep reboots as well and mine have so far vanished after removing softkeys and installing "button Savior" instead. Have 153 hours of uptime so far..
[Nook Color General] wendellc:
I had my first random reboot after about 3 weeks with my rooted NC. It happened after I pressed the power button to to close the screen and pressed it again to wake. After a few minutes after waking it with the power button it rebooted.
[Nook Color General] arda99:
I use button savior all the time but still have random reboots, seems to be fixed by switching to 54G from 11N
[Nook Color General] MadMikeSS:
I'm at 3 and a half weeks with my NC rooted with autonooter. No random reboots. Everything works like a charm. Have installed several apps from the market and have run some adb tweaks. No adverse effects yet.
[Nook Color General] christiankk:
I am getting random reboots now on my rooted NC :(
[Nook Color General] khaytsus:
Good thing you're in the right thread then...... :rolleyes: Read it now?
[Nook Color General] christiankk:
Can you elaborate on that incredibly helpful remark?
[Nook Color General] cal3thousand:
What Launcher and virtual button app are you running?
[Nook Color General] TheEditor:
Just wanted to pass along a note that the system profile fix in this thread works great. Uptime over fours days since setting it up.
[Nook Color General] eyecrispy:
I second that. I've gone over 5.5 days without issue. Would've gone longer if I hadn't rebooted manually.
[Nook Color General] khaytsus:
Same here, it's very stable with the Setting Profiles workaround.. I went 4 days and rebooted after pushing something into /system/app and tonight it was up 4.5 days when I installed a new keyboard to try and had to reboot for it to show.
[Nook Color General] MadMikeSS:
Just the default nook home launcher and softkeys that autonooter installs.

I have tried out ADWLauncher EX without any noticeable issues.

Posted from my NOOKcolor through XDA app
[Nook Color General] bonobomidwest:
I had a similar problem, that got worse and worse, and eventually lead to rebooting when i was using the unit. In a sort of fifth-element "what did you just do to make that happen" process, I tracked it down to the power button. It was no longer giving a solid "click" and actually seemed to be dislodged slightly under the case so that even slight movements would hold it down and trigger the reboot. There's several people reporting this on the vanilla nook color forums. My replacement unit (native 1.01) seems to have a less flimsy case plastic... make of that what you will.
[Nook Color General] jlmwrite:
I had my first random reboots yesterday, after a week of constant trouble-free use.

Went to check email, and noticed that neither of my gmail inboxes reflected some deletions/archives I'd done from my laptop earlier that day. I try refreshing them without success, and was just about to press 'delete account' (thinking I would remove and re-sync) when my NC suddenly rebooted itself.

Everything worked well after that, but then sometime just as I was falling asleep I heard the reboot chime. We can rule out motion or a loose key as the NC was sitting on my bedside table, and it wasn't the magnet as the case was in a drawer. I have minimal apps installed (Zeam, Button Savior, Angry Birds, one of the super lightweight battery monitor apps, and a non-weather clock widget) and the goodies that autonooter installed, and that hasn't changed recently so now I'm at a loss.
[Nook Color General] cal3thousand:
Looks like we are gonna be like this until a proper ROM can be developed OR we get more Logcat information that leads to the fault.
[Nook Color General] eyecrispy:
I believe my NC just rebooted itself. I hadn't had a reboot since the settings profile was installed. The only difference is that I flashed the new screamer kernel. Anyone else seeing this?

Sent from my Nook Color
[Nook Color General] 911jason:
Switching what to 54G from 11N?

Sorry if it's obvious, I just read through the whole thread trying to figure out what you're talking about.
[Nook Color General] khaytsus:
I guess they're talking about ancient 11mbit 802.11B. No way I'd do that, just use Setting Profiles, it hardly ever reboots then. I have 5+ day uptime now.
[Nook Color General] arda99:
I mean 802.11N or I should say 300N?

By downgrading from 802.11N to 802.11G my nook color doesn't reboot anymore, that's without Setting Profiles trick and the wifi is left on while screen is off. There are some people never encouter this issue here I guess their nooks are also on 802.11G.
[Nook Color General] 911jason:
Mine rebooted twice (back-to-back) yesterday while I was at work and had it tethered to my HTC Aria... not sure what signal it's putting out, but I can't imagine it's 802.11n.
[Nook Color General] khaytsus:
Nope, my router is G and it rebooted 6+ times a day until I used Setting Profiles.
[Nook Color General] jewnersey:
After slamming the 950 screamer oc kernel on my color, I have yet to have a reboot in about 3 days. Just thought I would throw this info into the pile.

//from the nook COLOR
[Nook Color General] daithioflionn:
still no fix?

I hoped some of the tech genius floating around here would have sorted this.
[Nook Color General] khaytsus:
There's a free, stable, and easy workaround. My NC gets 4-5+ days uptime, I'm usually rebooting it to fiddle with another keyboard or such before it reboots on its own now.
[Nook Color General] teknikk7:
4+ days here, no reboot. 900MHz Kernel.
[Nook Color General] spiffytech:
Which workaround are you referring to? Reading this thread, I see lots of people say they found a workaround, and lots of people saying those workarounds didn't work. I've tried switching to ondemand, turning wifi off when the screen goes off, killing all but the core apps, removing the weather widget, removing softkeys, and nearly everything else from this thread without success. Can I make alogcat stream to a file? I've only figured out how to save logs to a file every 10 minutes, which doesn't let me catch crashes.
[Nook Color General] cal3thousand:
Are you saying that you had reboots before and that this 900MHz kernel solved the problem?
[Nook Color General] bonzer2u:
I was about to ask the same question for future reference......

Makes me kinda wish I were clairvoyant :eek:
[Nook Color General] khaytsus:
Disabling wifi before turning off the screen. Also documented here: http://nookdevs.com/NookColor_Issues
[Nook Color General] JackOnan:
This has worked for me sofar, although I was getting reboots when it wasn't in sleep mode, usually when I would set it down and leave it on. This only started happening about 3 weeks after I rooted (1.01 update with 2.12.18 autonooter).

I think there could be several different causes for this problem. A rogue app causing a crash and reboot. A sticky power button (all the side buttons on mine are of very poor quality). And some bug with the Wifi in sleep mode which Setting Profiles seems to take care of.

Maybe the 1.1 update will address the issue.
[Nook Color General] daithioflionn:
Ive done the work around involving the wifi sleep policy. I still get reboots. Admittedly far less, its more based around when i am doing something involving the wifi and i suddenly turn it off and put it down..... REBOOT.

This 900 kernel business. Can someone clarify this for me. Apologies as I seem to have missed it in the thread.
[Nook Color General] khaytsus:
http://www.nookdevs.com/NookColor_Issues

Not wifi sleep policy; disable wifi on screen off, per the above. My NC is at 7.5 days uptime.
[Nook Color General] cal3thousand:
The OC kernel was supposed fixing some of these reboot issues. However, I think it was phantom. I clearly have a reboot issue that is ONLY aleviated by turning off wifi on screen off (I use Tasker).

I'm currently on the 1.1GHz kernel and everything is stable. But, if I change my configuration to leave wifi on... reboot city.

*awaiting Gingerbread*
[Nook Color General] mageus:
Here is what I experience:

- Leave NC and come back to it later - sometimes it has reboot.

- Put NC to sleep - the lock screen will slowly brighten from black to full brightness, then slowly dim to black again. I cannot unlock the screen. Also, the live screensaver updates very slowly in the background.

- If I press the power button several times, the screen will eventually just stay black. Holding power to reboot doesn't work, and I have to pull the SD card.

- These symptoms became more frequent over the past few days of having the NC until it now does it on every sleep.

- This makes it unusable, since you need to sleep at least once to reset the digitizer.

- Sometimes, when rebooting, it boots into the stock Nook reader software, even with the SD card is still in (no one has mentioned this symptom yet).

- Happens with Nookie 0.5.8 and 0.5.9 (on 2 different SD cards)

Setting the governors to OnDemand has worked for now (only tried sleep several times).

Considering the multiple symptoms and solutions in this thread, this sounds like an overheating problem. The fact that changing governors or disabling wifi supports this theory.

I'll repost tomorrow whether the governors fix works persistently. If not, I'll try the wifi fix.
[Nook Color General] Artood2s:
Hi everyone, I used to have this problem regularly, and learned just to live with it. But I have to say that ever since I started using the 1.1 OC (and maybe the 900 screamer too) that I have not noticed any random reboots.

That being said, I still reboot manually every 2 days or so because of some phantom RAM usage. I've tried to use the NookColor Tools app to find out what service is hogging the RAM, but it doesn't display anything too crazy (like one service using a huge amount of RAM). Does anyone know some way to monitor this?
[Nook Color General] spiffytech:
I can confirm this solves the issue, as I now have an uptime of 4 days since following the procedure described in the wiki. Note that I had no success when I tried turning off wifi when the screen went off using CPU Tuner.

However, I'm not pleased with this solution. For example, things like Pandora simply stop working if wifi shuts off when the screen does. I tried the alternate suggestion from the wiki, setting all CPU profiles to ondemand, but as the wiki states, it doesn't eliminate the reboots.

I'd really like to get to the bottom of this.
[Nook Color General] khaytsus:
12 days uptime right now on my NC ;)
[Nook Color General] locowd:
Happened to me initially but stopped once i installed a task manager. I think it was just using too much ram.
[Nook Color General] GorillaPimp:
thanks for the feedback

khaytsus - I no longer have the issue at all besides with a few app induced hiccups. My longest uptime has been 12 days and the only reason it wasn't longer was turning the device off. Thanks again for the information.
[Nook Color General] jadambpharm:
you can use an app called softlocker. this will allow you to listen to Pandora etc with the screen off.
[Nook Color General] cal3thousand:
WooHoo... hopefully

It seems (initially at least) that the 1.1.0 Update fixed my Wifi issues

Way to go B&N for the update!

Way to go Decad3nce for the prerooted update.zip! Now I can have data all the time.
[Nook Color General] uphillian:
no reboots after rereooting

I had the random reboot issue and decided to try the prerooted 1.10. That didn't work at all for me, it wouldn't complete booting, so I reverted to my previous backup. (which subsequently killed itself with an "authorization problem")

After starting from stock and not installing anything after rooting I had 1 day of uptime, no reboots, no wifi off profile or any set cpu hacks, just stock rooted. After that I started adding things back and I noticed I did something wrong the last time.

Do people with random reboots have multiple google accounts on their nooks? I have 3, but this time I added them all from youtube (last time I did the secondary accounts from the gmail app).

I'm at 2d 14h 11m right now according to the uptime widget. I'm running all the same software, my only real difference is the way I added accounts...
[Nook Color General] spiffytech:
I did not have multiple Google accounts on my NC when I had the reboot issue.
[Streak 5 Q&A, Help & Troubleshooting] marculous:
got a streak as a gift a month ago - tried to update from stock 1.6 to 2.2 using guide on streaksmart.com - didnt work. now streak is bricked. no lights, nothing. looked all over online for days now and the furthest ive got is to try to access the quallcomm chip from the laptop but i cant, and i cant run the driver on it either, as told in the bricked streak pdf by ryrules. called dell and they cant help w/o acct name that purchased device - which i cant get (but thats a whole other story). cant even get a charge from what i can tell, qdl tool cant detect usb streak. im able to admit im out of my depth on this one - can anyone out there help?
[Streak 5 Q&A, Help & Troubleshooting] stoney73:
If it helps, the dell streak service tag should be on the back of the phone when you remove the battery cover.

I phoned Dell today and they are picking up my streak for repair, no charge. And im not the first owner of the device either. Got mine from ebay. All they did was get me to boot into recovery, and try a factory reset. when it didnt complete, they just said they will fix it, for free thankfully.
[Streak 5 Q&A, Help & Troubleshooting] marculous:
I tried that - they won't transfer the device to my name w/o verification of original purchaser account name - and won't be able to issue a new free replacement w/o it. Not only do I not have that info, I might not ever be able to get it. thank you for the idea though.
[Streak 5 Q&A, Help & Troubleshooting] lufc:
What is it , Baseband 00 ,31, 21 ?

Follow this HERE
[Streak 5 Q&A, Help & Troubleshooting] Radimus:
try this:

http://forum.pocketables.net/showthread.php?t=8221
[Streak 5 Q&A, Help & Troubleshooting] marculous:
Stock att baseband 31, which I didn't find out until after won't upgrade straight to 2.2 using the method described on streaksmart.com
[Streak 5 Q&A, Help & Troubleshooting] marculous:
Now that looks promising, I will try it
[Streak 5 Q&A, Help & Troubleshooting] marculous:
i went here and dl'ed the pdf and files, but i cant get past maunally installing the fastboot driver on pc, it wont let me update the android driver - because its not recognizing the device as connected. i can get my laptop to recognize the quallcom chip, but thats as far as ive gotten. phone is off, seemingly totally dead, no lights or anything. when i get to the chip, it wont let me install or update driver - every time i try it fails. any ideas? I tried your email in the pdf.
[Streak 5 Q&A, Help & Troubleshooting] gordata:
Where are you located? Maybe I can help you out.
[Streak 5 Q&A, Help & Troubleshooting] marculous:
Texas, but I think I could maybe fix it if someone had the right step by step instruction I could follow. Is there another program besides the qdl that can help?
[Streak 5 Q&A, Help & Troubleshooting] gordata:
What version of windows are you using. I had a very hard time with windows 7 but took me like 20 minutes from start to finish with a windows XP.
[Streak 5 Q&A, Help & Troubleshooting] marculous:
32 bit vista
[Streak 5 Q&A, Help & Troubleshooting] marculous:
about to try qdl and driver as told on streakdroid
[Streak 5 Q&A, Help & Troubleshooting] marculous:
i followed video on streakdroid and

qdl gets to

wait for adb device...

error(d2)wait for adb fastboot mode timeout

please check that device is exist and driver is properly installed

download fail

now what?
[Streak 5 Q&A, Help & Troubleshooting] ronj1986:
That happened on my 1st attempt using QDL. Just unplug Streak, remove battery for @ least 1 minute, place battery & cover back on, hold the button closest to the headphone port while @ same time plugging cable back into Streak, then run again. 2nd time did everything for me. My computer did flash something about drivers installed successfully after the 1st fail, so maybe it installed what was missing. If this doesn't work, use a different USB port.
[Streak 5 Q&A, Help & Troubleshooting] Krisbo:
+1 for that advice. In addition, I wouldn't use a USB hub either.
[Streak 5 Q&A, Help & Troubleshooting] marculous:
yes, i did but when i try to update the android adb interface under device manager on my laptop by directing the driver update screen manually to C:\dell\drivers\R288920\Win7 i get an error msg that says

windows encountered a problem installing the driver software for your device

windows found driver software for your device but encountered an error while attempting to install it

the device cannot start (code 10)

seems to be a pattern im stuck in, i cant make it past here yet.

Nm - fixed it w help from irc #dellstreak - had to end up using 2 different qdl tools, but in the end - after a week long struggle w a bricked streak it finally came back on, with 2.2
[Streak 5 Q&A, Help & Troubleshooting] camwoody2:
Please help!!!!

..................................
[Streak 5 Q&A, Help & Troubleshooting] stoney73:
Dont know if you still have this problem, but I transferred registration/ownership to myself on the dell site. It just asks for your details and service tag. Which coincidentally is shown under About Phone, status at the bottom.