So I noticed that my battery seems to drain rather quickly, so I checked everything, and i realized that after I closed the lid while it's docked, the screen will turn off, but once it is fully shut, it will turn back on to the lock screen and stay there. Has anyone else noticed this, and if they have, has anyone found a solution?
I am having the same issue. Though mine does not happen all the time. I also have the random reboot issue when docked, not sure if these are related or not.
I noticed this when I had the netformer kernel installed. Switched to the clemsyn kernel and the problem went away.
May want to check and make sure you have Stay Awake unchecked in settings-application-development. I found that mine was doing the same, would close it would shut go dim, but not shut off. Thought it was probably because the dock is constantly "charging" the tablet. Turning this off has made a noticable increase in battery life.
Related
Debating about whether to install CM7, but there have been a few problems with it. I'm having a tough time finding the current state of the following issues:
1. Sleep of Death - Nook goes to sleep and doesn't wake up, forcing a reboot. There seems to be some debate over whether this is solved. One of the threads indicates that it's not a problem if you turn wifi off with the screen. Can anyone confirm?
2. Battery drain - Battery drains at 2%-3% per hour in sleep mode. I believe this is resolved. Can anyone confirm?
3. Premature Battery Death - Battery dies at various points over 0%. There seem to be various utilities for resetting battery stats, etc., but I can't figure out whether or not this is resolved.
4. Screen stays on when plugged in - Forced to hit the screen off button when plugging in the Nook. I've seen recent complaints about this one, so I'm assuming it's not resolved.
I did go through the threads and am confused about whether these issues still exist, so I figured I would try the Q&A section. If someone with CM7 wouldn't mind jumping in, that would be great. Thanks!
1. Maybe, I'm a lucky one but I haven't had problem with SoD regardless wifi on or off. I've been using nb100 and up, and now at 138
2. Using 138, i got 2-3% drop overnight, about 8 or 10 hours. With 120, zero dropped
3. Not experienced yet since I never let it down to sub-5
4. Mine seems act the opposite way: screen off, plug in to charge, screen automatically on, have to press power button to put screen off again.
1. I haven't seen this in recent nightlies.
2. Fixed; NC now deep sleeps when unplugged, even with WiFi on.
3. Fixed as far as I know.
4. Mine acts like yours and votinh's both; these are not mutually exclusive. If you plug in while on, the screen eventually dims instead of going off. If you plug in while off, the device turns on, sometimes just the backlight. I'd call this one minor, especially in relation to the other issues.
511pf said:
Debating about whether to install CM7, but there have been a few problems with it. I'm having a tough time finding the current state of the following issues:
1. Sleep of Death - Nook goes to sleep and doesn't wake up, forcing a reboot. There seems to be some debate over whether this is solved. One of the threads indicates that it's not a problem if you turn wifi off with the screen. Can anyone confirm?
2. Battery drain - Battery drains at 2%-3% per hour in sleep mode. I believe this is resolved. Can anyone confirm?
3. Premature Battery Death - Battery dies at various points over 0%. There seem to be various utilities for resetting battery stats, etc., but I can't figure out whether or not this is resolved.
4. Screen stays on when plugged in - Forced to hit the screen off button when plugging in the Nook. I've seen recent complaints about this one, so I'm assuming it's not resolved.
I did go through the threads and am confused about whether these issues still exist, so I figured I would try the Q&A section. If someone with CM7 wouldn't mind jumping in, that would be great. Thanks!
Click to expand...
Click to collapse
1) I get SOD about once a day regardless of how I have it set up. It does happen less with wifi on sleep only but at work I need to push data, so my wifi is on all the time and...it's an issue, not terrible but annoying none the less.
2) Battery drain, I get about 36 hours if I use it lightly, but I tend to charge it nightly because I can't take a chance of heavy use at work and loosing it.
3) PDB, never had this problem.
4) The screen turns off by just hitting the screen off button. This isn't a big a deal actually, since you gotta plug the thing in, another button isn't a big deal. I have katecca screen lock and off in my bar at the bottom, so it's easy to turn off. I also have the nook power off widget but I haven't used it much.
That's great. Thanks a lot for the responses. Really helpful.
I have only had it CM7 on my nook for one day, so im not sure about the battery issue. But i know i put it down around 10pm last night with less then half a battery and i got home from work around 3pm and it had about 25% batt left.
Besides that sometimes when i plug it in it stays lit up. but thats a "meh who cares" to me at least.
Running 7.1.0 RC1 with Dal's OC, On Demand, with lowered Voltage on the steps
1) I've only had one SOD ever (knock on wood), it seems to be mostly cleared up
2) Battery drain has not been a problem for me. On .29 it was more only 1%/hr for battery drain.
3) I haven't experienced early battery death at all
4) It isn't a big deal, especially if you charge with the provided outlet adapter for quick charge. Don't see this preventing you from installing CM7.
If these stats are correct from ASI (I'm hoping they are, they sound right), I'm at 76% after 3 days, 19 hours uptime, and 7 hours of it without sleep.
I say go for it. Even if it is off SD (mines on emmc) it is still a much better experience than stock/rooted. I doubt anything will make me change from CM7, unless ICS becomes a viable option in the future.
Just a follow up on this. I installed CM7 and have not had a Sleep of Death, have normal battery drain comparable to stock rooted, and have not had premature battery death. The screen does come on when I plug the Nook in, but like everyone mentioned, I just turn it off and it's no big deal.
So far, my wifi actually reconnects more reliably than on stock rooted 1.1. I'm overclocked to 1200 Mhz, with no voltage or other adjustments.
Following up again - I get a SOD or a reboot about every five times I turn off the screen in CM7. I tried to use Tasker to turn wifi off with the screen, which has solved the problem for some people but this made no difference at all. I was running a nightly from late July and updated to another from late August (173?) but the problem hasn't gone away. I may try Stock 1.2 rooted.
511pf said:
Following up again - I get a SOD or a reboot about every five times I turn off the screen in CM7. I tried to use Tasker to turn wifi off with the screen, which has solved the problem for some people but this made no difference at all. I was running a nightly from late July and updated to another from late August (173?) but the problem hasn't gone away. I may try Stock 1.2 rooted.
Click to expand...
Click to collapse
I had no SODs from almost a week with n165; I upgraded to n171, got an SOD first time I put it down for a while, so I reflashed n165 and I'm sticking with it until I hear of something I need.
WiFi always on.
As always, YMMV.
Sent from my NookColor using XDA Premium App
Just a little update:
Since using nb169, I got a few SoD, did update again to nb173, still got hit occasionally.
I never have this kind of issue before but lately.
The changes I made
a. Played around with ADW Launcher setting (especially Desktop Animation)
b. Recently installed Simi Clock and updated some apps (such Nook app)
c. Recently having 8GB uSD card plugged in.
For some reason, I don't think a. and b. causing problem but c.
can you run cm7 with the 1.2 or 1.3 updates from b&n? im on a autonooter 1.1 and have been wanting to move up to something better especially if i can have flash finally.
miss_october said:
can you run cm7 with the 1.2 or 1.3 updates from b&n? im on a autonooter 1.1 and have been wanting to move up to something better especially if i can have flash finally.
Click to expand...
Click to collapse
CM7 is custom Gingerbread-based ROM, it has nothing to do with stock ROM and there is absolutely no relationship between the two (except they are both Android OS)
votinh said:
CM7 is custom Gingerbread-based ROM, it has nothing to do with stock ROM and there is absolutely no relationship between the two (except they are both Android OS)
Click to expand...
Click to collapse
thanks for the response
One last (I think) follow up. I installed stock rooted 1.2 thinking it CM7 causing me problems over the last month. Turns out I had the same problem on CM7.
I read my Nook before I go to sleep, so it's often dark in the room. I turn the brightness WAY down. The problem ended up being the Adjbrightness "Lock brightness so other applications can't change" setting. It has something to do with screen dimming when turning off the screen. This setting being on was causing frequent reboots both on CM7 and stock rooted 1.2. I ended up going to ScreenFilter instead, and the problem has completely gone away at least so far.
511pf said:
Debating about whether to install CM7, but there have been a few problems with it. I'm having a tough time finding the current state of the following issues:
1. Sleep of Death - Nook goes to sleep and doesn't wake up, forcing a reboot. There seems to be some debate over whether this is solved. One of the threads indicates that it's not a problem if you turn wifi off with the screen. Can anyone confirm?
2. Battery drain - Battery drains at 2%-3% per hour in sleep mode. I believe this is resolved. Can anyone confirm?
3. Premature Battery Death - Battery dies at various points over 0%. There seem to be various utilities for resetting battery stats, etc., but I can't figure out whether or not this is resolved.
4. Screen stays on when plugged in - Forced to hit the screen off button when plugging in the Nook. I've seen recent complaints about this one, so I'm assuming it's not resolved.
I did go through the threads and am confused about whether these issues still exist, so I figured I would try the Q&A section. If someone with CM7 wouldn't mind jumping in, that would be great. Thanks!
Click to expand...
Click to collapse
I try to stay up to date with the latest nightlies.
1) This is not completely solved. It's rare now (I think it was issues with WiFi), but it has still happened to me recently.
2) Battery drain was fixed with kernels that support Deep Sleep correctly. Not any 7.0.x builds, only 7.1.x+ (RC1) and nightlies have fixed kernel. So this shouldn't be an issue (unless you have a rogue app that is keeping the CPU active, which would prevent Deep Sleep. The "CPU Spy" app will let you see if this is working correctly).
3) This is better, but still a problem. My Nook Color will just switch off at 4% battery now. It use to switch off when I was a lot higher. It's not supposed to do that. It's supposed to gracefully shutdown when low. I have several iOS and Apple devices, so I'm use to things shutting down correctly when low. My Nook Color always just randomly powers off.
4) This isn't a big deal. The screen comes on when charging, but you can turn it off if you want. It stays dim, and the Nook Color charges fine. Dalingrin (the kernel developer guy) said leaving the screen on was a fix to some nasty crash.
#3 is the biggest issue to me, as I've been in the middle of something when my Nook Color randomly powered off. Clearing battery stats, rebooting, etc - none of that makes it perfect.
#1 use to be the biggest problem, but it's very rare for me now.
#2 has been fixed, and #4 doesn't bother me.
stolenmoment said:
I had no SODs from almost a week with n165; I upgraded to n171, got an SOD first time I put it down for a while, so I reflashed n165 ...
Click to expand...
Click to collapse
I misspoke; n165 SOD's on me too, so I conclude that I dl'd 165 and didn't flash it; I reflashed n161 and have been stable since.
I keep WiFi on for email and podcast updates.
I've always got an 8G uSD card in.
Sent from my NookColor using XDA Premium App
In trying not to be a noob, I searched the various subforums for the transformer looking for something similar and didn't find anything so here goes with my first new thread. Note there are plenty of battery drain ones, and while I do have that, that's not what my question is about.
I just recently sent my TF dock for repair of the mobiledock battery saving mode setting not working properly. A key press could always wake the device regardless of setting. Got it back from RMA, and sure enough the keyboard doesn't wake the device, and the touchpad wakes it only if touch it right away. So that's fixed.
But then I noticed that when I went into Applications->Battery use, the summary was wrong, and odd. After a bit of fooling around, what appears to be happening is that the graph only records when it is disconnected from the keyboard. It's been on for a few days now and the graph only shows 4 mins.
It's a B50 version of tablet and dock. It's running 8.6.5.9 and the mobileDock is EP101-0213.
Now, I know that the history/summary was working before I RMA'ed it, and I know that it wasn't working after I got it back, and it still isn't working after the update to 8.6.5.9.
As a side note, the battery drain is about 3.5%/hr when idle and docked. I have installed CPU spy and see that while it is indeed going to deep sleep, it isn't staying asleep. Some app is keeping it awake, I just don't know which app it is.
So it happened again. Fully charge the TF for a trip. When I get to my distination (8hrs later) turn on the TF and its dead. No power and no chargers. This thing is pissing me off!
Anyone know why or how I can fix? I do have the wifi off when screen is off.
How is that possible?
Did you not shut down your TF?
hipertec said:
So it happened again. Fully charge the TF for a trip. When I get to my distination (8hrs later) turn on the TF and its dead. No power and no chargers. This thing is pissing me off!
Anyone know why or how I can fix? I do have the wifi off when screen is off.
Click to expand...
Click to collapse
It looks like you are having the reboot during deep sleep issue that started with the upgrade to ICS. The reboots can be stuck with the screen enabled and the processor actively trying to complete the boot, which drains your battery.
Short term, I would avoid leaving the TF powered up unattended for long periods.
That will prevent the total battery drain. For a longer term work around, you can try an app called Wake Lock, which you can set to prevent the TF from going into deep sleep, and eliminate the deep sleep reboots, which has helped some users, including me.
The app should be set to restart on Reboot, and select the Partial Lock, then select the Acquire Lock setting, on the red bar, which will switch to green, and indicate that it has acquired. You can also set it to show its icon in the Notification are, so that you have a visual assurance that it is working. Then just exit the app, and it will work in the background.
You can monitor that it is preventing Deep Sleep, using the CPUspy app.
I would then watch carefully to see that you aren't experiencing any more reboots during Deep Sleep.
Long term, ASUS is researching instability with ICS, and we hope to get a true fix. Until then, use of Wake Lock may help you.
Others may have other opinions and explanations, and they may be right, but this has cured my problem for the last 11days. Good luck.
Sent from my Galaxy Nexus using Tapatalk
horndroid said:
How is that possible?
Did you not shut down your TF?
Click to expand...
Click to collapse
No shut down. I would charge the TF to 100%. turn the screen on to see if its 100% charged and that's it. Then 8hrs or so later when I want to go use the TF, its dead. Can't even turn on.
Can this be the reboot issue or an application that is running and not letting my TF go to deep sleep? Help!
hipertec said:
No shut down. I would charge the TF to 100%. turn the screen on to see if its 100% charged and that's it. Then 8hrs or so later when I want to go use the TF, its dead. Can't even turn on.
Can this be the reboot issue or an application that is running and not letting my TF go to deep sleep? Help!
Click to expand...
Click to collapse
Your response makes no sense. You say TF was shut down then you say TF might not be going into deep sleep. If you power the TF down it will go off and use NO battery. you will get some battery internal discharge but TF will not come on an use battery. Try the same test shutting it off.
Ok...try again. I would charge the TF. Then check by pressing the power button. The screen goes on and shows 100%. Then press the power button to turn the screen off ( not turning it completely off).
When I want to use the TF, it won't turn on, as if its completely dead.
Suggestion?
its either a) you get a RR and get stuck in a bootloop, b) you got some app running that drains the battery, such as Winamp or c) your device is broken (not likely).
There are many threads already posted addressing this issue. Please Learn to correctly use the search function
•••THREAD CLOSED•••
Hi,
The screen on my Nexus 4 has started to stay awake. I've noticed my battery drain a lot quicker over the last couple of days and I also noticed that every time I pulled my phone out the screen was lit so I've taken it out and watched it. It just stays awake all the time. If I turn the screen off the minute a message or anything comes in the screen wakes and stays awake so near impossible to keep it off for any length of time.
I do have the developer screen enabled and had stay awake whilst charging option enabled. I disabled that to make sure that this wasn't causing the screen to stay awake thinking it was somehow on the charger when it wasn't however the problem persists even with that option unchecked.
I have the screen timeout in display set to 30 secs.
Anybody else experiencing this or no how to solve?
The phone is stock and unrooted though I plan on rooting later today.
ktz84 said:
Hi,
The screen on my Nexus 4 has started to stay awake. I've noticed my battery drain a lot quicker over the last couple of days and I also noticed that every time I pulled my phone out the screen was lit so I've taken it out and watched it. It just stays awake all the time. If I turn the screen off the minute a message or anything comes in the screen wakes and stays awake so near impossible to keep it off for any length of time.
I do have the developer screen enabled and had stay awake whilst charging option enabled. I disabled that to make sure that this wasn't causing the screen to stay awake thinking it was somehow on the charger when it wasn't however the problem persists even with that option unchecked.
I have the screen timeout in display set to 30 secs.
Anybody else experiencing this or no how to solve?
The phone is stock and unrooted though I plan on rooting later today.
Click to expand...
Click to collapse
Does it stay awake but go very dim? I have this issue too.
can it be caused by the screen protector blocking the light sensor somehow?
Can you install BBS (BetterBatteryStats) and see what's keeping your phone awake?
Sounds like a FULL_WAKE_LOCK is constantly being imposed on your phone.
Questions
Is it only when you put it for 30s?
What's around your pocket when you put your phone in it?
Do you have any attachments onto your phone? e.g. skin protectors, cases...etc
Does this occur on any screen or just your home screen and the developer options screen?
Though some questions may be obvious, the best method is to be thorough with the situation. Answering these questions will help us better help you.
My phone shut itself down about an hour ago (plenty of battery left as I had to charge it earlier and was at 50% when it did come back on). It took several minutes before it would respond to getting turned back on again. I've got 2 messages since and the screen is now tuning off as it should. I had turned the phone off a few times to see if it rectified yesterday however that didn't work.
The problems wasn't anything to do with me having it in my pocket as the problem still existed when I had it sitting on my desk. I have no screen protectors or case and I never put it in any pocket that has anything else in it as I don't want to ruin too quickly.
So not sure what's going. All seems very odd. Hopefully not a sign that the phone is on the way out but looks ok for now. Will have to watch and see what happens over the next few days.
Thanks to all who took the time to respond. Hopefully I won't need to bother you again on this issue but not convinced just yet
Got a weird problem with my AT&T stock non-rooted S4. About 4 or 5 times since I got it on release day when I charge my phone and I get the notification that it's fully charged the screen won't turn back off. I use a Belkin Conserve socket that is set to shut off after 3 hours and I've woken up after charging to find the phone dead. I've managed to catch this happen once and when the fully charged notification comes on the screen won't go to sleep, it just stays on and flickers a little bit. For all but one of these instances I had blocking mode on so I'm not disturbed by email or text notifications in the middle of the night. It did happen one time when I didn't have blocking mode on. I use a pin lock for my lockscreen and usually have BeyondPod playing overnight (only one hour long podcast while it's still charging) if that makes a difference. Is the function that enables the screen to stay on when you're looking at it malfunctioning? Any help? I've attached two screenshots of battery life when this happens.
Tryptonite said:
Got a weird problem with my AT&T stock non-rooted S4. About 4 or 5 times since I got it on release day when I charge my phone and I get the notification that it's fully charged the screen won't turn back off. I use a Belkin Conserve socket that is set to shut off after 3 hours and I've woken up after charging to find the phone dead. I've managed to catch this happen once and when the fully charged notification comes on the screen won't go to sleep, it just stays on and flickers a little bit. For all but one of these instances I had blocking mode on so I'm not disturbed by email or text notifications in the middle of the night. It did happen one time when I didn't have blocking mode on. I use a pin lock for my lockscreen and usually have BeyondPod playing overnight (only one hour long podcast while it's still charging) if that makes a difference. Is the function that enables the screen to stay on when you're looking at it malfunctioning? Any help? I've attached two screenshots of battery life when this happens.
Click to expand...
Click to collapse
So in settings under the Developer Options, there is a setting "Stay awake" if checked screen will never sleep while charging. Now I see that your Belkin shuts off the power but your phones still detects the usb plugged into a power source.
I think things happen in this order: you hookup your phone to charge and shut off your screen, phone charges to 100% and screen lights up saying fully charged, it stays on because of that setting, Belkin kills the power, it is still hooked up to USB so ... you get the rest.
I would find that setting and disable it.
if your next question is "I don't see developers option" it is hidden by default in android 4.2.2 so to make it available, go to Settings > About phone and tap tap tap Build number seven times. Return to the previous screen to find Developer options. Or Indiana Jones might pop up and give you the cup to get eternal life !!!
Thanks for the reply Commodore64 but I already checked that setting when it happened the first time and it's not checked.
No one else has had this problem?
Tryptonite said:
No one else has had this problem?
Click to expand...
Click to collapse
I have this problem as well as my wife's S4. around 3am, I notice our room is bright with our two phones' screens on. It will stay on until the morning.
In the developer's section of the settings, the stay on when plugged in is NOT checked.
Also, on our phones, we notice the phones overheating because the screen is on for hours at a time at night.
I've just spent an hour looking through the internet, and while many report this, they are simply being dismissed by others as in having "checked" the setting in developer section.
Also, when the batttery does get fully charged, the "Battery if full, unplug the power" notification also rings the default notification ringtone. I've installed phoneweaver to set my phone to no sound overnight, but it only stops the sound, the screen still stays on and phone gets really hot.
This is turning out to be a huge problem for us.
pyrophilus said:
I have this problem as well as my wife's S4. around 3am, I notice our room is bright with our two phones' screens on. It will stay on until the morning.
In the developer's section of the settings, the stay on when plugged in is NOT checked.
Also, on our phones, we notice the phones overheating because the screen is on for hours at a time at night.
I've just spent an hour looking through the internet, and while many report this, they are simply being dismissed by others as in having "checked" the setting in developer section.
Also, when the batttery does get fully charged, the "Battery if full, unplug the power" notification also rings the default notification ringtone. I've installed phoneweaver to set my phone to no sound overnight, but it only stops the sound, the screen still stays on and phone gets really hot.
This is turning out to be a huge problem for us.
Click to expand...
Click to collapse
Do you use a PIN (number) lock? I did but switched to the pattern unlock and it hasn't happened since. Also, I've been trying to charge only during the day or evening, not overnight. Maybe, since I charge during the day and I use it periodically while it charges it doesn't go into a "deep sleep" like it would if it charges while sleeping and the full charge notification would keep it awake. I don't know exactly why but it hasn't happened since. Hope this helps.
Power Button Not Working SGS4 Not Sleeping SOLVED
For whatever it's worth, see http://forum.xda-developers.com/showthread.php?p=48871706#post48871706 - maybe that will be helpful.