Related
So, I'm at a loss of what to do here. No matter what settings I seem to use I can't get good/decent battery life.
In fact, I get terrible battery life. With light to moderate usage I have to charge my phone at least two times a day, mostly three. Current widget reads that at standby I'm anywhere between 55mA-70mA and when in use 200mA-500mA. When charging it reaches 400mA-600mA
I see everyone talking about being able to get 5-10mA and I'm amazed at this. I've searched and read most "Battery saver" threads and none of it seems to work.
I was originally using Chucky rom lite and when I noticed the drain was abnormal I switched to the set up that chiasoft uses in his ReadMe for the ROM (stock 2.10ROM/2.08 radio).
Although since switching to the stock WinMo ROM I had repeated BSOD and SOD issues. To the point that it became unusable. I switched over to latest Energy ROM.I installed EBL and on both Stock and this Energy ROM. I am still having BSOD/SOD problems. Could it be the EBL? I plan on upgrading the radio to 2.12 in a few after I test out this EBL theory.
My setup as of this post is this:
WinMo ROM: Energy.BLACKSTONE.21916.Sense2.5.Nov.08 (Switched back to Stock 2.10)
Radio: 2.08.50.08_2 (Switched to 2.12)
Android: MooMoo Froyostone Sense 3.2 w/hastrain kernel
SetCPU:
998max/245min Ondemand on boot
Profiles: Screen off; Priority 100; 384max/245min ondemand
Battery <25% 576max/245min Priority 0 ondemand
Sampling 20000; Up Threshold 40
Advanced Task Killer:
Kill Level Agressive
I really don't want my LI-ON battery to die before I've even had the phone for the year. So if anyone can think of anything to help I'd be ever so grateful.
And of course, thanks to all the people who make all this possible.
(Sorry for the tl;dr post. I wanted to give as much info as possible.)
when you fully charge your batter what is your mV ? use the battery life widget to determine this. If it is not nowhere 4000mV once fully charged, you might need to consider buying a replacement battery.
btw. my mA reading is actually worst than yours. Might have to calibrate the battery again later.
mofoahh said:
when you fully charge your batter what is your mV ? use the battery life widget to determine this. If it is not nowhere 4000mV once fully charged, you might need to consider buying a replacement battery.
btw. my mA reading is actually worst than yours. Might have to calibrate the battery again later.
Click to expand...
Click to collapse
idk what it is fully charged. I'll be sure to check it later though. How do you calibrate the battery?
Also, I realized that I made an oversight on my part. When I switched to the stock WinMo rom I hadn't realized fully that it changed my Radio to 2.08 even though I posted it.
The rom chef recommends 2.10ROM/2.12 Radio, so that's what I switched to to check out that combination.
btw change it to interactive not on demand.
you charge the battery when your phone is off. Till your charge indicator turns green.
Once that is off. you can use root explorer or adb and go to rm/data/system delete the batterystats.bin leave your phone plugged in while you are deleting the batterystats.bin file
i prefer root explorer. but its not free and your device has to be rooted.
let the phone drain the battery till its dead and turn it on again to make sure it is completely dead.
charge the phone like you would usually afterwards.
mofoahh said:
btw change it to interactive not on demand.
you charge the battery when your phone is off. Till your charge indicator turns green.
Once that is off. you can use root explorer or adb and go to rm/data/system delete the batterystats.bin leave your phone plugged in while you are deleting the batterystats.bin file
i prefer root explorer. but its not free and your device has to be rooted.
let the phone drain the battery till its dead and turn it on again to make sure it is completely dead.
charge the phone like you would usually afterwards.
Click to expand...
Click to collapse
I don't have interactive in my options.
what version are you running?
mofoahh said:
what version are you running?
Click to expand...
Click to collapse
2.03 I got it through here.
Just installed 2.04 and there still isn't an interactive.
thats odd. because im on 2.0.4 also and I am able to select interactive.
btw i followed this guide for the battery conditioning.
http://forum.xda-developers.com/showthread.php?t=827762&highlight=ultimate+setcpu
and this one for my setcpu settings.
http://forum.xda-developers.com/showpost.php?p=8246854&postcount=4
mofoahh said:
thats odd. because im on 2.0.4 also and I am able to select interactive.
btw i followed this guide for the battery conditioning.
http://forum.xda-developers.com/showthread.php?t=827762&highlight=ultimate+setcpu
and this one for my setcpu settings.
http://forum.xda-developers.com/showpost.php?p=8246854&postcount=4
Click to expand...
Click to collapse
Yeah. No interactive settings. Also, that guide recommends 1190 max, but mine only goes up to 998.
Also, I finally got it to down to 7mA in standby. When I changed the radio to 2.12 and using a 2.10 stock WinMo rom.
no issues here getting 48 hours of light use, or a full 24 of moderate use...
I've yet to "condition" my battery. I'm worried it'll do more harm than good. Especially since I just got it finally to a decent mA draw. Although I'm worried my phone won't charge up to 100%. Always stop at 95.
Is conditioning really necessary/important?
easy answer... whats your full charge voltage? shuld be 4.2
if not , your looseing batt life..
t1h5ta3 said:
easy answer... whats your full charge voltage? shuld be 4.2
if not , your looseing batt life..
Click to expand...
Click to collapse
yes full charge voltage should be around 4.2. Try charging it with the phone OFF till your charge indicator is green. This way you can achieve a full charge.
By the way how the hell are you getting 48 hours on light usage?? excuse my language. What are your setcpu settings, configurations. etc.
mofoahh said:
yes full charge voltage should be around 4.2. Try charging it with the phone OFF till your charge indicator is green. This way you can achieve a full charge.
By the way how the hell are you getting 48 hours on light usage?? excuse my language. What are your setcpu settings, configurations. etc.
Click to expand...
Click to collapse
Yeah, 48 hours seems improbable. I finally got it down to 7-10mA on standby, and I think it charges up to 4.2 but I'll find out for sure tonight.
same
I had the same problem, make sure you use EBL android launcher and set to autoboot at 3 seconds. Make sure you restart your phone anytime youw ant to load android. I assure you this will work.
My HD2, like all others can be flattened in 2-3 hours with windows/android if used hard, the difference seems to be on very light usage/standby win mobile could last 4 days... with everything turned off and basically not used Android would struggle to last 2 days !
Same phone same network/signal levels etc, can only be poor power management within Android, and I think that means voltages for all the processor and comms modules, not just a simple case of turning down speeds.
What do others think ?
Update: Upon switching to WinMo:2.10 and Radio:2.12+ MooMoo's MMS fixed froystone3.2 I was achieving 6-10mA in standby. The phone would last all day with a two-three hour charging period with moderate usage. Low battery use, rare DC's. Perfect. Best build I've used so far.
I'm noticing a new problem however, and I wonder if it's happened to Chiasoft who recommended this build. I'm getting serious touch screen freezes since last night. Anytime before that the set up was working AMAZINGLY.
Now? It's almost unusable sometimes. This morning it was happening in Android so I switched to WinMo and surprisingly enough it happened in there too. So I read touch freezes are Radio problems mostly. Is this true? Should I switch to a new radio? I'm confused as to why it would just randomly start happening though and worried it would mess up my battery troubles I just solved.
Any advice?
Hmm. I noticed that it almost always freezes when I hold down the end home button to turn off the phone or data or to silence it. I can't actually use the touch screen again until I hit the button again to put it to sleep.
I wonder if it's hardware related because it was happening in WinMo that way as well.
Okay, so now the entire adroid system is acting up mostly related to the touchscreen. Like I use the calculator and it appears that i'm holding a button down. Or I try to make a call and it's not responding. It appears that when I hit end call button repeatedly it allows me to unlock the phone. But when holding down the end call button to get to the Power Off screen nothing in that menu is responsive.
It seems... software related, but I'm not sure. Any info would be helpful. I'm going to reformat my card and reinstall droid and see what happens.
So, called t-mobile. They're sending me a new replacer phone. Oh well. We'll see how that one goes.
pretzdothack said:
Okay, so now the entire adroid system is acting up mostly related to the touchscreen. Like I use the calculator and it appears that i'm holding a button down. Or I try to make a call and it's not responding. It appears that when I hit end call button repeatedly it allows me to unlock the phone. But when holding down the end call button to get to the Power Off screen nothing in that menu is responsive.
It seems... software related, but I'm not sure. Any info would be helpful. I'm going to reformat my card and reinstall droid and see what happens.
So, called t-mobile. They're sending me a new replacer phone. Oh well. We'll see how that one goes.
Click to expand...
Click to collapse
I give you only a very short suggestion
You have just to DELETE SETCPU
and delete ANY TASK KILLER (you can keep it just to close any apps that could hang, but not to "free up ram")
Android is not Windows, you dont need to free up ram, and you dont need to overclock/undervolt to gain some minutes of battlife despite stability.
Talk to any Dev and they will confirm this.
Good Luck
When I hit the power button nothing happens. This does not happen all the time. I normally have to pull batt and reboot to get anything. I am rooted,running Jt SC and Geeknik 4.4.1 kernel. I have tried multipliable roms and kernels....like I said it is only some times. I have CPU set at 400max/200min screen off. I was having problems with min set at 100. Also set cpu does not auto detect after reboots. Yesterday it was not waking up after calls and had to pull batt also. I have not installed voodoo, only non kernels. Went back to stock last night and rerooted and installed everything new this morning. Any help....very frustrated with this phone. Any help would be great. I am coming from a D1.
Bump....for the night shift.
cleskers said:
When I hit the power button nothing happens. This does not happen all the time. I normally have to pull batt and reboot to get anything. I am rooted,running Jt SC and Geeknik 4.4.1 kernel. I have tried multipliable roms and kernels....like I said it is only some times. I have CPU set at 400max/200min screen off. I was having problems with min set at 100. Also set cpu does not auto detect after reboots. Yesterday it was not waking up after calls and had to pull batt also. I have not installed voodoo, only non kernels. Went back to stock last night and rerooted and installed everything new this morning. Any help....very frustrated with this phone. Any help would be great. I am coming from a D1.
Click to expand...
Click to collapse
Don't set profiles in SetCPU. The Fascinate doesn't like them, for some reason.
Thanks. Haven't had it happen again today after I did fix permissions. Any idea why it's not auto detecting the kernel?
Sent from my SCH-I500
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
Hi there!
Is anyone having the same issue or kind of solution: I put my TF to charge over night (I don't have keyboard dock but tablet only) and when I unplug it in the morning it wont wake up but I have to force reboot it with keeping the power button pressed.
I use Revolver's latest rom (3.11) and Blades kernel. All other things are working perfectly.
Anyone experienced the same? Any solutions?
Thanx in advance!
lkbfreak said:
Hi there!
Is anyone having the same issue or kind of solution: I put my TF to charge over night (I don't have keyboard dock but tablet only) and when I unplug it in the morning it wont wake up but I have to force reboot it with keeping the power button pressed.
I use Revolver's latest rom (3.11) and Blades kernel. All other things are working perfectly.
Anyone experienced the same? Any solutions?
Thanx in advance!
Click to expand...
Click to collapse
What is battery charge level.
I do experience this occasionally (I'd say about once every week or two). I think its a somewhat common occurrence with the custom kernels on the TF.
I don't really mind that much, the benefit of having a 500mhz+ overclock on a custom kernel overshadows this small, infrequent issue.
There may be a way to resolve it, I haven't looked. I just wanted let you know its not a hardware defect unique to your own TF.
Rumbleweed said:
What is battery charge level.
Click to expand...
Click to collapse
Battery charge level is always high (when I force reboot tablet it's around 95%).
This morning I found out that it WILL wake with pressing the power button but it takes a while - the screen is responsive and you can start and close the apps but power button is not responding for some short time (a minute or so). Volume rocker does responds normally.
I think it is related to the common TF problem - sleep of death.
I also installed CPU Spy and found out that the tablet wasn't even in deep sleep while charging over night. Guess it does have something to do with kernel.
Not a big problem for me as also stated in next reply - I prefer more having possibility to overclock than occasional "not waking" problems.
THX everyone for help and support!
I read that the tf doesn't go into deep sleep when charging by default.. Asus made it that way which is why I try not to charge overnight..
I have left mine overnight (can't remember if it was charging) and it wouldn't wake once.... just once though...
sent from my HTC desire using xda premium
Did anyone ever solve the issue of the screen never turning off while charging in CM7? Still seems there in 7.2. Is there any workaround for this besides simply pressing the power button after plugging in the charger? I've turned off "stay awake" and debugging, but they didn't make any difference.
I noticed that before, but now on mirage 7.2 the screen will stay off once I turn out off. At least I have not noticed it.
Sent from my MB860 using xda app-developers app
It's not a problem of the screen staying off - they all do that. The problem is that the screen won't automatically turn off.
Turn the option ti keep screen on while plugged in off in settings/development
Sent from my SPH-D710 using xda app-developers app
doncaruana said:
I've turned off "stay awake" and debugging, but they didn't make any difference.
Click to expand...
Click to collapse
krylon360 said:
Turn the option ti keep screen on while plugged in off in settings/development
Click to expand...
Click to collapse
Isn't that the same thing I mentioned? The one I mentioned is under settings->Applications->Development. Is there a different one?
I think it must be a bug in CM7. I was able to successfully turn off the 'stay awake' toggle in CM9 and it turned the screen off after the display timeout while charging. But choosing the same setting in CM7.2 stable caused the screen to dim after the display timeout like it was getting ready to turn off, but just stayed dim and never did completely turn off while charging.
leapinlar said:
I think it must be a bug in CM7. I was able to successfully turn off the 'stay awake' toggle in CM9 and it turned the screen off after the display timeout while charging. But choosing the same setting in CM7.2 stable caused the screen to dim after the display timeout like it was getting ready to turn off, but just stayed dim and never did completely turn off while charging.
Click to expand...
Click to collapse
That's what I found as well. I found an old thread around here stating it was a kernel bug. Looks like it's one that was never fixed.
Slightly off topic, but is CM9 useable as it stands? When I played with it about a month and half ago, it was far too laggy to be used (for me at least).
doncaruana said:
Slightly off topic, but is CM9 useable as it stands? When I played with it about a month and half ago, it was far too laggy to be used (for me at least).
Click to expand...
Click to collapse
I haven't used just straight CM9 in a while, but the ParanoidAndroid based on the latest non-opengl build works great. I was having trouble with the prior PA build using opengl.
If I manually turn my screen off while charging (CM7), it immediately turns back on, and stays on. Not sure what's going on there but I'm having a number of odd issues with my Nook.