Related
Hey guys just like we all i suffered from the insane battery drain in CM7 with my lovely Vibrant. But yesterday night i found a cure that gives me now great battery life - almost like a 2.2 rom.
What i did?
I googled around and found this post:
1. Open up the dialpad, and type:
*#*#4636#*#*
(the numbers are for 'info'; don't press call, it should automatically go to a 'Testing' menu)
2. Go into 'Phone information'
3. Press Menu, and select 'Select radio band' (this will result in a force close, but that's what we want.. just keep going.)
4. Go back into 'Phone information' and scroll down to the bottom'. It will probably still say 'CDMA auto (PRL)', but the problem is this is probably a visual glitch. Or it might say 'Unknown'. Either way, switch it to something else, then switch it back to 'CDMA auto (PRL)'. Then you can turn off the radio and turn it back on with the button right underneath that.
5. At this point, the fix has been applied, but it would be a good idea to clear the battery stats to get a fresh start. So boot into recovery and do that, then reboot. The fix *should* stick after this reboot, but I think it didn't when I first did it. But assuming it does, then you're golden. It will be like this for all other reboots. If it does not, then just do it again. You can tell if it worked if when you go into battery usage, and go into cell standby, the TWS% is much lower. I charged mine completely overnight after applying this fix and have been off the charger now for over a half hour and TWS% is still at 0% (even though cell standby is at 46% (but that's not a problem at all..), and my battery is still at 100%
My Vibrant gives me now GSM/CDMA auto (PRL) as network type.
So let me know whether it works for you too or not.
For me its asesome, since i can enjoy CM7 all day long ;-)
Seems to be working fine for me, would I have to do this for every nightly.
Sent from my SGH-T959
great find +1 the battery life of cm7 drove me away to a JVQ rom but imma try this find and use it!
I don't know if the cure will work for me, too. I found out that my device doesn't enter deep sleep, so even when I'm thinking it's sleeping, it is not.
The process Android System keeps it awaken. At least it did in #54 and other recent builds. It completly depletes my battery like me drinking lemonade.
Does it sleep for you?
I like this. I can actually stream music while charging without slowly losing charge.
I'm going to try this and see what happens
Hope this gets run through Atinm.
kleineschatz said:
Hey guys just like we all i suffered from the insane battery drain in CM7 with my lovely Vibrant. But yesterday night i found a cure that gives me now great battery life - almost like a 2.2 rom.
What i did?
I googled around and found this post:
1. Open up the dialpad, and type:
*#*#4636#*#*
(the numbers are for 'info'; don't press call, it should automatically go to a 'Testing' menu)
2. Go into 'Phone information'
3. Press Menu, and select 'Select radio band' (this will result in a force close, but that's what we want.. just keep going.)
4. Go back into 'Phone information' and scroll down to the bottom'. It will probably still say 'CDMA auto (PRL)', but the problem is this is probably a visual glitch. Or it might say 'Unknown'. Either way, switch it to something else, then switch it back to 'CDMA auto (PRL)'. Then you can turn off the radio and turn it back on with the button right underneath that.
5. At this point, the fix has been applied, but it would be a good idea to clear the battery stats to get a fresh start. So boot into recovery and do that, then reboot. The fix *should* stick after this reboot, but I think it didn't when I first did it. But assuming it does, then you're golden. It will be like this for all other reboots. If it does not, then just do it again. You can tell if it worked if when you go into battery usage, and go into cell standby, the TWS% is much lower. I charged mine completely overnight after applying this fix and have been off the charger now for over a half hour and TWS% is still at 0% (even though cell standby is at 46% (but that's not a problem at all..), and my battery is still at 100%
My Vibrant gives me now GSM/CDMA auto (PRL) as network type.
So let me know whether it works for you too or not.
For me its asesome, since i can enjoy CM7 all day long ;-)
Click to expand...
Click to collapse
I hope this works, but when i first went to phone info and did radio band, it asked for country, i choose usa, it didnt FC thou, then when my setting was already GSM/CDMA (prl) . I will report back tommorow how it goes. thanks
I'm guessing the same would apply to MIUI?
It definitely seems to be doing something. My signal hasn't dropped below the full four bars yet, which is weird considering it's normally around 1 or 2. The phone also seems to go to sleep faster, but that could be placebo.
Sent from my SGH-T959 using XDA App
duboi97 said:
I'm guessing the same would apply to MIUI?
Click to expand...
Click to collapse
yes i tried this it didnt seem to work for me i dont think i got it to stick on im gona try it again
didnt get Force closed at the select radio band. Now what should I do?
on Miui I had to select Turn Radio Off first, then it forced closed and now it seems to stick when I change radio bands. Just turn on/off radio a few times and it should help.
ferhanmm said:
on Miui I had to select Turn Radio Off first, then it forced closed and now it seems to stick when I change radio bands. Just turn on/off radio a few times and it should help.
Click to expand...
Click to collapse
Thanks! Finally I got it to force closed and I did everything else. But I went into cell standby I saw my TWS% is 71 when my cell standby is only 21%. Is that a problem?
SuperJMN said:
I don't know if the cure will work for me, too. I found out that my device doesn't enter deep sleep, so even when I'm thinking it's sleeping, it is not.
The process Android System keeps it awaken. At least it did in #54 and other recent builds. It completly depletes my battery like me drinking lemonade.
Does it sleep for you?
Click to expand...
Click to collapse
I had this same problem. Apparently alot of others did too, but no one seems to have a solution that I have seen.
Sent from my SGH-T959 using XDA App
Effect of USB Charging on CPU Idle Utilization CM7
First, this test was performed on nightly #55 with KB5 baseband. I have performed this on KA7 as well and found the results to be similar.
I am very sensitive to my battery utilization. In turn, I am also a very frequent charger. Even if I'm at 80%, I feel I must plug my phone in as soon as possible. Because of this, there is hardly a time where my phone is on during a session in which it had never been on usb. This changed, however, this last weekend. I was playing around with KA7 vs KB5, and was away from my computer and charger. Later, when I reviewed my cpu utilization during idle time, I was shocked to see that the phone was just sipping the battery. Less than 1% utilization in System panel.
My initial reaction was "KA7 is amazing." However, the next morning, battery usage appeared to be the same as normal. On a hunch, I wondered if it was possible that it was the charging that is causing issue. As we all know, when the phone is plugged in, cpu utilization is fairly high (~30%), and some even report the battery getting hot (in some cases, even to reboot the phone). But -- is it possible that even after you unplug, there is some lingering "stuff" happening that will not go away, regardless of how long you idle?
What I did was simply charge my phone fully, unplug, reboot. I consistently find that my phone will go in and out of very low cpu utilzation state when I do this. If I go into airplane mode, I will even see full sleep state with no green bars in System panel (not that I would do this, as I like to USE my phone).
I am very curious if some of you may be able to try this experiment and report back. If this is confirmed, I wonder if there may be a way to determine what is getting stuck and robbing our cpu cycles after the phone is unplugged from charging.
Attached are four screenshots:
syspanel_pre_reboot_8hr.jpg: showcasing the long overnight charge, followed by very low activity, yet with >3% cpu utilization while idle. (by wall charge, though this has shown to be the case via computer usb charging as well)
syspanel_pre_reboot_2hr.jpg: a closer look at the idle time after the charge.
syspanel_post_reboot_8hr.jpg: A big picture view of the charging, the reboot, and the subsequent idle time. The first thing I did once the phone booted was download and install several app updates from market. I wanted to stress the phone before letting it fall back to idle.
syspanel_post_reboot_2hr.jpg: here you can see the lower idle cpu utilization on the phone. Initially there is activity as I updated apps from the market, and then it fell to hover around ~1%.
This behavior can be replicated and repeated on my phone every time. I was hoping someone with logcat experience may be able to help me define a filter so that we can see exactly what processes plugging the phone into usb starts, compared to which it terminates when unplugged. If we were to find this, I would suspect it could be added to the code itself.
THAT is what I'm experiencing TOO.
I have tried that fix. When entering the "select radio band" it doesn't force close. I just see "EURO Band" , "USA Band" etc...
also on the bottom it says "GSM only".
Is the fox already applied for me?
I'm using TRIGGER (CM7 based).
ginzberg said:
First, this test was performed on nightly #55 with KB5 baseband. I have performed this on KA7 as well and found the results to be similar.
I am very sensitive to my battery utilization. In turn, I am also a very frequent charger. Even if I'm at 80%, I feel I must plug my phone in as soon as possible. Because of this, there is hardly a time where my phone is on during a session in which it had never been on usb. This changed, however, this last weekend. I was playing around with KA7 vs KB5, and was away from my computer and charger. Later, when I reviewed my cpu utilization during idle time, I was shocked to see that the phone was just sipping the battery. Less than 1% utilization in System panel.
My initial reaction was "KA7 is amazing." However, the next morning, battery usage appeared to be the same as normal. On a hunch, I wondered if it was possible that it was the charging that is causing issue. As we all know, when the phone is plugged in, cpu utilization is fairly high (~30%), and some even report the battery getting hot (in some cases, even to reboot the phone). But -- is it possible that even after you unplug, there is some lingering "stuff" happening that will not go away, regardless of how long you idle?
What I did was simply charge my phone fully, unplug, reboot. I consistently find that my phone will go in and out of very low cpu utilzation state when I do this. If I go into airplane mode, I will even see full sleep state with no green bars in System panel (not that I would do this, as I like to USE my phone).
I am very curious if some of you may be able to try this experiment and report back. If this is confirmed, I wonder if there may be a way to determine what is getting stuck and robbing our cpu cycles after the phone is unplugged from charging.
Attached are four screenshots:
syspanel_pre_reboot_8hr.jpg: showcasing the long overnight charge, followed by very low activity, yet with >3% cpu utilization while idle. (by wall charge, though this has shown to be the case via computer usb charging as well)
syspanel_pre_reboot_2hr.jpg: a closer look at the idle time after the charge.
syspanel_post_reboot_8hr.jpg: A big picture view of the charging, the reboot, and the subsequent idle time. The first thing I did once the phone booted was download and install several app updates from market. I wanted to stress the phone before letting it fall back to idle.
syspanel_post_reboot_2hr.jpg: here you can see the lower idle cpu utilization on the phone. Initially there is activity as I updated apps from the market, and then it fell to hover around ~1%.
This behavior can be replicated and repeated on my phone every time. I was hoping someone with logcat experience may be able to help me define a filter so that we can see exactly what processes plugging the phone into usb starts, compared to which it terminates when unplugged. If we were to find this, I would suspect it could be added to the code itself.
Click to expand...
Click to collapse
i usually reboot after i charge when i wake up then i send a few texts and work the phone a bit my battery life isnt too bad
romitkin said:
I have tried that fix. When entering the "select radio band" it doesn't force close. I just see "EURO Band" , "USA Band" etc...
also on the bottom it says "GSM only".
Is the fox already applied for me?
I'm using TRIGGER (CM7 based).
Click to expand...
Click to collapse
no i have the same problem for some reason i cant get this fix to work either
Gave it a try, will see what happens. Battery life is now the only bummer on CM, if this solves it, I'll be a happy guy.
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
I never had any problems with batterylife on my Nook until the last couple of days when I noticed it drains the battery on standby. So after checking the settings I noticed the wifi sleep policy was set to "Never". I set it back to "When screen turns off", but the next morning it was back to "Never".
The only change I can think of is that I used a new live wallpaper. But I can't see how that would do any difference since the app had zero permissions granted.
And after changing the wall paper back to a normal one, it's still getting reset to "Never".
What's going on?
yeah, I noticed this also on my NC and my HTC Aria. Both are running CM7. My battery life is good on my NC but it's really starting to suck on my Aria. I'll set wifi to "When screen turns off" and at waking up it would reset it self to "Never". This was never a problem before, not sure why this is happening.
Still haven't found a solution for this, so bump
as soon as my S5 phone hits the first low battery warning at 15%, the WIFI automatically turns on
makes no sense since that would drain the battery even faster
already checked all setting to make sure any auto switches are off
anyone else heard of this problem and know how to keep the wifi from turning on by itself?
nobody?
ok in case anyone else runs into this, i figured it out
after nobody replied i figured it had to be an app i had that not too many people use
after uninstalling one by one when my phone was hovering around the 15% mark, the culprit turned out to be:
prey anti-theft....a useful app, but now useless
Just got my Priv yesterday, and loving it so far, BUT I noticed all day today so far my phone has been sitting next to me on a desk and the screen keeps randomly turning on. I went to Settings -> Display and disabled "Ambient display" and "Lift to wake" thinking that might be triggering it, but no luck. The display keeps randomly turning itself on and draining massive amounts of battery. Has anybody else had this problem or do I have a lemon of a device?
EDIT: I also noticed my device does not sleep "After 30 seconds of inactivity" like I set it to, or any amount of time I set it to for that matter. Anybody else have this problem as well?
I had the screen randomly waking issue too. I had to turn off Lift to wake for that to stop happening.
I also get the issue where the screen doesn't sleep even if I set the screen to sleep after 15 seconds.
You are not alone. lol
Ok so it's not a hardware issue on my end that's the good news I guess. The bad news is this issue is killing my battery life so it might be a deal breaker unless we can find solution.
tdesbien31 said:
Ok so it's not a hardware issue on my end that's the good news I guess. The bad news is this issue is killing my battery life so it might be a deal breaker unless we can find solution.
Click to expand...
Click to collapse
You wouldn't happen to have an Android Wear watch that's connected to your phone at all, would you?
Or possibly trusted devices or places setup at all?
tdesbien31 said:
Just got my Priv yesterday, and loving it so far, BUT I noticed all day today so far my phone has been sitting next to me on a desk and the screen keeps randomly turning on. I went to Settings -> Display and disabled "Ambient display" and "Lift to wake" thinking that might be triggering it, but no luck. The display keeps randomly turning itself on and draining massive amounts of battery. Has anybody else had this problem or do I have a lemon of a device?
EDIT: I also noticed my device does not sleep "After 30 seconds of inactivity" like I set it to, or any amount of time I set it to for that matter. Anybody else have this problem as well?
Click to expand...
Click to collapse
Check to see if the wake screen for new notification alerts are set. I had a similar issue when I first got the device but after turning this off and the lift to wake option my battery life has gotten much much better
So I restarted my device and the issue went away, then toggeled the Airplane mode on while I was in school (I'm a teacher) and turned it off when I was leaving school and noticed I had the same problem again.
Can one of you test to see if toggling the Airplane mode on your phone makes the screen timeout no longer work?
tdesbien31 said:
So I restarted my device and the issue went away, then toggeled the Airplane mode on while I was in school (I'm a teacher) and turned it off when I was leaving school and noticed I had the same problem again.
Can one of you test to see if toggling the Airplane mode on your phone makes the screen timeout no longer work?
Click to expand...
Click to collapse
Just checked mine. Screen timeout working as it should when Airplane Mode activated. Hope you figure out what the problem might be. Good luck
After I got the PRIV I also noticed it woke up too easily. After disabling the 'Double-tap to wake' option (don't know the exact name) that didn't happen anymore.