Database Develop

Nook will turn on by it self after 5 minutes or so

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.

Ridiculously easy to corrupt settings - Normal?

I was just getting over the initial buyers remorse phase for my galaxy (or in my case, flashers remorse, even though I run stock JPY and it's fine, I have this urge to re-exchange it for a SLOWER stock Vodaphone Australia 2.2 version that's probably more buggy, but at least truly stock), when I drained my battery to 1% to test battery life, and shut it off manually.
On the walk back to the recharger in my room I accidentally turned it back on, and I immediately tried to turn it back off again, without letting it go past the 'GT-19000' logo in fear of the battery draining. It just restarted again and I decided to let it boot this time. Mistake. It then started to randomly vibrate and shut off apps (mainly, my live background, shake them all) left right and center then went straight back into default first-boot menu, like the very day I received the phone, or after a hard reset. The funny thing was, instead of having default values selected, it had the ones I had already put in. I thought it would be fine after that. Wrong.
I tried rebooting it again to see if it fixed itself, and it does the same with the forced closes. I uninstall my background and re-install it, and save some settings. When it boots it restores the live background back to it's stock settings (the live wallpaper I chose is still there, but the settings for it are not).
At this point I'm scratching my head so I uninstall all apps. This time on boot it doesn't throw up "force close" errors, but instead force-closes a single app or service for me on boot, with the one buzz, then three quick buzzes. Sigh... I have to factory reset my phone. One thing that particularly annoyed me was the fact I moved all my apps (AngryBirds ) to my external SD card, yet miraculously, after the reset my phone doesn't seem to think it's there anymore! Another thing I'm pondering is that if I didn't reset my phone like this, would this still have occurred?
Runs perfectly fine after the factory reset, with no errors or anything on boot as of yet. I have been compulsively rebooting it ever since just to find out, LOL!
Is this a 'normal' sort of thing to happen on the SGS, or is just through shear coincidence the combination of me restarting the phone in it's booting phase + the low battery life screwed up some boot settings while the phone was writing to it, or is it some hardware error? I can see this as particularly annoying if it were to happen every month or so. Coming from an old brick phone with something like 8000 messages on it, it'd be inconvenient to say the least to start deleting everything periodically... I guess I can use apps to back-up data when this occurs, but some apps don't even work after it's been erroring out on me. *Pulls hair out*
TL;DR:
Reset my phone while it was booting (still on the GT-I9000 screen) on a low (1%) battery and it broke my phone settings. Forced closes unknown app/service on boot with no 3rd party apps installed, but still boots to home. Force closes 3rd party apps frequently if they're installed. Factory Reset/Wipe. Problem Solved. Annoyed. RAGE.

next time something like this happens use adb logcat to figure out what is actually going wrong

exclamationmark said:
...
On the walk back to the recharger in my room I accidentally turned it back on, and I immediately tried to turn it back off again, without letting it go past the 'GT-19000' logo in fear of the battery draining. It just restarted again and I decided to let it boot this time. Mistake. It then started to randomly vibrate and shut off apps (mainly, my live background, shake them all) ...
Click to expand...
Click to collapse
you are not alone . after draining battery , starting it accidently up (drained) in middle of booting , killed it for me, well not killed but wouldnt boot for me and I had to the the factory reset. oh and since the nice bzz ... bzz bzz bzz I hear more often I would like to ( here was I ignored crying about it http://forum.xda-developers.com/showthread.php?t=937938 )

Yeah I'll definitely boot up logcat if it happens again. I'm just hoping this isn't a regular occurrence . As long as I don't do anything stupid like this again, I'm thinking it should be fine.
The third time this happens, it's going back to the service center, so it's got two chances left! Another thing I failed to mention was that it was chewing up like 200mb~ ram with level 1+2 ram cleared, without loading back into the homescreen, before the factory reset. Probably the stupid forced close app/service leaking >.>
Pagot, if that were me and continual factory resets were the only way to fix it (or didn't fix it) I'd flash it back to stock (or just remove root) and return it to the service center if that's an option. Sounds like something got corrupted or didn't get flashed properly. Either way I'd let THEM waste their time sorting it out because no amount of flashing is going to solve a hardware issue if it turns out to be one.

exclamationmark:
(had stock, so just root removing) but I know how our service centers work (and I would have to bring it even to our carrier) they wouldnt even talk to me if I didnt do the factory reset and the first thing they would do "reflash and factory reset"
right now I am not playing on the phone so much anymore. no lust or time so no idae if my apps are still fcing so often . And I installed speedmod and made a backup so I can revert back if something happens. So will see.
Wanted to just write about the battery down +(or) not full boot = corruption

[Q] Deathly crash issue: only solution is factory reset. SERIOUS ISSUE

Okay, I have been having a serious issue with my D3 lately. One time, my phone just randomly rebooted, and then it would get stuck at the red "Droid Eye" screen, where it would be laggy and such after a while. Eventually the screen would time out in like 2 minutes. After it turned off, I could not get it to turn back on. Basically dead, except I could still get notifications and even a phone call. But I could not act on any of them. it's like the phone's heart is still beating, but I can't turn the screen on. I pull the battery and reboot and it does it again. SOMETIMES if I keep touching the red eye screen I can get to get to the lock screen, but the wallpaper won't load and it's basically frozen. I even tried booting into safe mode and that didn't help. I took it to Verizon, they said they've a couple other people with a similar issue on the forums. They did a factory reset, and that has been the only solution to the issue. I have had it 3 times now, and this time I'm sticking with the Blur launcher and keeping only the essential apps installed. I'm assuming this is a software issue, and I'm currently trying to figure out if it is related to a certain app that was installed. Hoping they will fix this with an update! ANYBODY ELSE HAVING THIS ISSUE? if so, any leads on another fix or what it could be?

sounds like a software issue. a factory reset doesn't do anything other than change the software.
I had a similar issue on my droid 1. it was rooted and when I installed a gingerbread from I forgot who, it got stuck at the eye, kept rebooting, and occasionally, i'd get calls and it still wouldn't work. I look forward to root.
out of curiousity, did you have to take it to the store to factory reset or is there an option for it in the bootloader(I know its locked but I have no idea to what degree)

The first time I took it to the store they did it for me, but yeah there's an option in the bootloader. Just took my back to Verizon cuz this was the 4th time it's done it, they're sending me a new one! It's okay, cuz my nice screen open 'click' sound was gone on the keyboard lol

Help diagnosing freezes and random reboots

I am hoping someone has dealt with either of the following problems, and come up with a way to effectively diagnose and fix either.
The phone - 1101 build; running AT&T Stock KK4; rooted via kernel swap method (using stock KK4 kernel after swap, i.e., do not have clockwork recovery); some AT&T bloatware frozen with TiBu, otherwise stock with root
Problem #1 - roughly once a day, the phone will freeze when in sleep mode; I have had this happen with both the slide to unlock and Exchange PIN lock screen up; when I hit power to wake the phone, the screen wakes up but is unresponsive and then the screen won't shot off again; live wallpaper is frozen in place, but if the phone was plugged in, the battery icon continues with the animation loop. And if the phone is not plugged in, battery power drops rapidly in this state.
The phone isn't completely dead, because if I connect/disconnect it via USB (set to debug mode) to my laptop, the computer recognizes the phone is connected, but it is dead enough that if I call the phone, it does not recognize the missed call. The only way I can restore the phone is a battery pull. Usually it takes several minutes for the phone to come back after this, acting like it would if I had flushed the dalvik cache or installed an update.zip from recovery.
Problem #2 -also roughly once a day, at random times the screen will wake up momentarily, then clear, and I will hear the AT&T boot up sound, after a short while, the phone will run through the media scanner and any other startup launches, acting as though it had been turned on, but the battery stats show continuous uptime throughout. I have had this happen when using the phone, including when on a phone call (and the call did not drop).
I have seen problem #2 on virtually all of the AT&T GB leaks, and it seems to get more frequent the more apps that are installed. I had not seen problem #1 until recently.
The phone is out of warranty, and owned by my employer. I am not due for a new phone from them until July. I've done more master clear/reflash stock cycles than I care to admit, tried replacing/testing for disk errors the external SD card, etc..., and am afraid of doing that and having the problems come up again.
Any thoughts on how to diagnose either of these problems?

Hmm... I don't really think there is an exact diagnosis for any of these issues. Some phones are just problematic like that. The only thing I can suggest is trying a different ROM or kernel, and that might help your stability.

I have the exact same problems. Hope someone comes up with a fix. The only help I can give you is that when the phone freezes, instead of pulling the battery, you can hold the vol up & power buttons for 10 seconds and the phone will restart. Easier than pulling your phone apart, especially if you have it in a case, like I do.
Sent from my SAMSUNG-SGH-I897 using Tapatalk

korockinout13 said:
Hmm... I don't really think there is an exact diagnosis for any of these issues. Some phones are just problematic like that. The only thing I can suggest is trying a different ROM or kernel, and that might help your stability.
Click to expand...
Click to collapse
So, the way I see it, unfortunately these problems could be a function of:
Bad hardware
Misbehaving app
ROM issue
Kernel issue
I tried pretty much every leaked AT&T GB ROM and had random reboots with all of them. Seems to track with the number of apps installed, but can't prove that. I have not tried any custom ROMs or kernels.
Since this is technically not my phone, I am trying to avoid doing anything that can't really be undone if I need to turn the phone back in at some point. And I need something that can be a daily driver for work calls and Exchange email, and rely heavily on tethering when I am on the road.
Anyone with ideas on what to test, or how to capture enough log information to figure out where the problem is, would be a big help. Otherwise, I am stuck riding this out until July when I can get a new phone from my employer.

Nothing you do can't be undone, it's just a simple Odin flash away.
Be sure to back up your efs folder before flashing too much

studacris said:
Nothing you do can't be undone, it's just a simple Odin flash away.
Be sure to back up your efs folder before flashing too much
Click to expand...
Click to collapse
I've used Odin with the various GB leaks; if I go further afield (heck, performance is dicey already, how many more problems could I have with one of the ICS alphas), is it still a straight shot back to stock KK4, or are there other steps to do first?
And before I go down that road, any suggestions on diagnostics (other than yet again pulling apps off of the Captivate to see if one of them is the culprit...?)

stoobie-doo said:
I've used Odin with the various GB leaks; if I go further afield (heck, performance is dicey already, how many more problems could I have with one of the ICS alphas), is it still a straight shot back to stock KK4, or are there other steps to do first?
And before I go down that road, any suggestions on diagnostics (other than yet again pulling apps off of the Captivate to see if one of them is the culprit...?)
Click to expand...
Click to collapse
You actually might have less problems on ICS. But it all depends. You can always get back to stock with one, bootloader-free, safe flash. Diagnostics wise, there isn't really much you can do besides removing apps. I would only worry about the ones that are constantly running in the background, as they could possibly be screwing with the phone while in sleep. I think it's unlikely that this sort of testing would actually help though. I still say try something different.

stoobie-doo said:
Anyone with ideas on what to test, or how to capture enough log information to figure out where the problem is, would be a big help. Otherwise, I am stuck riding this out until July when I can get a new phone from my employer.
Click to expand...
Click to collapse
I am having the same issues except in my case I have tried to recreate the conditions and check memory and I am close to maxing it out. Part of my problem is that I come from a Palm background and I have found that Android, or at least the Cappy, is not as responsive (I was really spoiled by Cards on my Pre) I was thinking that my Android noobness is causing me to push the phone too hard and locking it up. FWIW, you might want to check memory issues

[Q] Power-On Lag/Freezeing

So i've been experiencing this issue for months now. I've had the issue since i've gotten the phone but its the past few months that its really gotten bad. So before anyone jumps the gun, i've done quite a bit of research on this and cannot find anything worthwhile, more on that soon.
So as usual, i'll pickup my phone and press the power button or the home button to turn on the screen, but at completely random times the screen will not come on at all. Sometimes the capacitive buttons will light up (maybe 15-20% of the time), but not always.
In my searches I found the following solutions to this problem:
Get a new sim card
Dont use an SD card
Get a new battery
Check the leads on the battery and phone for cleanliness
Factory reset
Remove 1 app at a time and test until it stops happening
Dont freeze any apps
Restore stock firmware
Dont use SetCPU
Turn off animations
Get rid of the lock screen
Remove custom message from lock screen
Clear cache through Recovery
Dont restore data with Titanium Backup when restoring apps
Turn off WiFi and/or Bluetooth and/or GPS
Dont use GreenPower or Greenify
Avoid stock launcher
I have tried all of the above except for removing 1 app at a time (and those that dont apply). I'm deep into that one and only have a few apps left to try. This is something that happens at least once a day, but typically 3-5 times in a day. I used to think i could make it happen by pressing the power button to turn on the screen and immediately hit it again to turn it off. It would sometimes work but that doesnt trigger it anymore.
My phone used to be rooted, but being on AT&T there was no "normal" way to flash a good recovery like CWM or TWRP and install roms, you have to use some other thing which i dont use. So i've always had stock recovery, im fully updated to the newest stock rom that is out, update came OTA which was after i removed root and used odin to flash an older stock rom back. My wife's Note 3 also has the same issue and it has never been rooted, we have gone through all of the above and still it continues to happen.
Also on a side note, my phone was swapped out because of an issue it had 3 months after i purchased the phone. I was able to get a brand new one, not refurbished. The issue had occured once or twice before the swap and an incredibly frustrating amount of times since then.
Reading through most of the other threads, everyone seems to have to remove their battery and re-insert it to get back into their phone. The ones that dont have to do that have found that removing their SD Card, getting a new one, sending the phone in, or one of the other options have worked. However for me, nothing has worked.
Does anyone have any other ideas? Is this common on the Note 3 (I've had it since release)? 70% of the time i can hold the power button for a few seconds to try and bring up the power menu and it works, but not always.. I usually just have to wait up to a minute or two (never actually counted, i use my phone for that stuff...which.. isnt..working...)

I've had wake lock lag on a few android phones. Even iPhones.
I would highly recommend rooting it on att and flash a mod that reduces it on the note 3. I talked about it here.
http://forum.xda-developers.com/showthread.php?t=2628716
Rebooting the phone always helps.

wudien said:
I've had wake lock lag on a few android phones. Even iPhones.
I would highly recommend rooting it on att and flash a mod that reduces it on the note 3. I talked about it here.
http://forum.xda-developers.com/showthread.php?t=2628716
Rebooting the phone always helps.
Click to expand...
Click to collapse
Unfortunately I cannot root my phone. I have to have my company email on my phone, and for Android devices they use Air Watch. I tried for weeks to get it working while rooted, and even used Root Cloak or something like that (with Wanam Xposed) to hide root from specific apps. Air Watch was specifically tested to work with that app but it still for some reason didn't work (new version of Air Watch perhaps with no update to Root Cloak? Just my guess). I had to remove root, factory reset and re-flash stock from Odin (that was a dual purpose flash) to remove all traces of Root so I could use Air Watch for my company email/calendar/contacts/etc again, even after unrooting and using all the cleanup tools, triangle away, and everything, it still detected my phone as rooted...
However, I don't think that's really a viable solution to the problem, that's more of a band aid. Looking at that thread and looking around, it seems to work well but I still haven't found anyone with my same issue where they used it and it worked. I would like to narrow this down to what the issue is exactly, the root cause. I think its a problem with KitKat, or at least all of 4.4.x (not sure about 4.4.4 yet).