Related
I reset my battery stats 2 days ago after doing a full charge and drain and full charge again my battery is at 94% after 1 hour. My time without signal is only 3%, phone idle is 42%, and only 15 minutes without sleeping. Does this sound normal or am I being anal?
Sent From My Hero!
That kind of sounds like mine. Extrapolating the percentage loss over time for me almost always yields a rate of about 100%/24 hours discharge, +/- 3 hours depending on use. I've always been concerned about the battery, especially after hearing so many people saying they get almost 48 hours on a single charge with moderate/heavy use
My battery is new. My Hero is less than a month old, but I haven't put on a custom ROM yet. I think a custom ROM and kernel is supposed to help. Mine is rooted and running SetCPU with profiles. I found that whenever my phone felt hot (which is a lot of the time, actually), it's usually an indication that battery is draining fast. I also read many peoples' Hero's run very cool, and don't get that warm when charging. Mine can get pretty warm when charging, close to 40C, and 42-43C when using while charging. These observations have caused me to wonder if my battery is bad, or if newer Heros are somehow different from old ones. Does this sound like yours?
I've learned that the battery usage is not linear.
So dont' worry about 1 hr sampling of your battery, use a minimum of 4-6 hrs and if it still losing 5%/hour after that w/out much use, then you may have an issue, but I wouldn't worry about it.
I'm using Crunchy's buufed rom with the OC'd kernel. My temp stays pretty even but I did add auto memory manager yesterday. I wonder if that's contributing.
Sent From My Hero!
I just figured it out. The stock sms is still locking up the dialer and keeping the phone awake. I figured that was fixed in these custom roms. So I disabled all notifications on stock sms and downloaded handcent. All is well.
Sent From My Hero!
I believe your aren't supposed to use things like autokiller and auto memory manager with an Oc'd rom.
I agree on the task manager but I thought the memory manager would tweak the built in settings from conservative to aggressive. Am I wrong?
Sent From My Hero!
It still does that but I've read posts by devs saying not to use autokiller with and overclocked rom, I don't understand why either but that's what it said.
Thanks for the heads up!
Sent From My Hero!
No problemo.
Alright so I've been running the cyan nightlies, I just updated to the latest one, installed the battery fix. Everythings working fine, put my phone down for and hour and the batt is at like %75, I go under battery use and it puts the screen at 79%, is this normal? I had my screen off most of the time and when it was on it wasnt bright and if this isn't normal how can I fix it?
Have you rebooted to see if it does this after every reboot? Try rebooting normally then see if its still doing it.
If so, then reboot into recovery, wipe dalvik, then reboot normally. Check your battery stats again after a couple hours and see if it's still doing it after the dalvik wipe.
(FYI, this belongs in Q&A section)
can you link to the battery fix plz?
I have had very high display usage on every version of CM6, and you will find it is a VERY common complaint on CDMA Hero's running CM6.
Everyone says it's because Froyo is more efficient, and uses less battery overall, so your display percentage is higher.
I call B.S. on that. I have had poor battery life with the more than 20 nightly versions I have run. I have had the Hero since the day before it came out, and I have never had worse battery life. I even bought a new battery thinking my battery was dying on me, and I still won't make it through a day (7 am - 11 pm) without plugging the phone in during the day.
My guess is there is something up with the display/lights/light sensor drivers that have been implemented in CM6 that don't allow something with the display to sleep properly. Either that, or the battery usage screen is simply completely inaccurate.
I could literally reboot my phone, leave it untouched with the screen off for four hours, then turn on the screen for one minute, and the display usage would shoot up to 50-75%. There is no way one minute of screen usage is using more battery than 4 hours of phone standby using the radio, checking email/twitter/facebook/gmail.
Anyway, that's just my opinion on the matter. Other than the battery life, the newest nightlies of CM6 are simply incredible, so I just deal with the poor battery life.
@ziggy682 -- Thanks for that info. I haven't yet tried CM6 (mainly cuz I'm so dependent on some Sense apps and widgets), and now that I'm reading about some battery issues I may hold off on trying it even longer.
@omair2005 -- if you haven't found it yet, here's the new thread on collin_ph's battery tweak specifically for CM/darch ROMs: http://forum.xda-developers.com/showthread.php?t=762283
Ok, so ever since I upgraded to CM6 (which I LOVE) I've had serious battery issues and I've tried to fix it by installing Pershoot's kernel and I have SetCPU to underclock in depending on what battery life it's at. Also, I've wiped my battery stats and I've calibrated my battery already.
Today my battery was at 64% after only 3hr and 26min. I don't have GPS on, auto backlight is on, 3g/2g and sync are on. If it makes any difference I have the Korean radio installed (which btw improved my reception a lot! ). After about 9hrs and half, my nexus one died. As per usage, I wouldn't say it's much at all because I'm in class most of the time and I've only talked on the phone for about 1 min, browsed a few websites, and sent only a few texts.
I keep reading on the forums about how people are getting 1-2% lower per hour while on standby but the % I reported earlier, my battery's draining at over 9%/hr!
I really just want to be one of those people that can say that "I still have 50% left after 12 hours!" lol
So, is there anything else I can to increase battery life? Is my battery just crap? Any recommended setCPU profiles?
If you're one of the users that get really good battery life from your Nexus One, please tell me what you did to get it that high! Thanks!
Don't use setCPU to manage battery life, only to overclock. It overrides the kernel's settings. Sounds like you need to wipe and flash the rom again. Then gradually add applications you want, something is sucking battery life.
Last, buy a new battery.
CM6 has less than stellar battery life. If you check the "help with my battery life" type threads, you will see most of the OP's have CM6 as their ROM. Try another ROM, you will get better results.
adambenjamin said:
CM6 has less than stellar battery life. If you check the "help with my battery life" type threads, you will see most of the OP's have CM6 as their ROM. Try another ROM, you will get better results.
Click to expand...
Click to collapse
Quoted for lies
I'm using CM6 and I get between 22-32 hours on a single charge. I just use the kernel that comes with it and i almost always have sync on. No GPS or bluetooth though.
Are you using a battery you purchased on ebay? Or are you using the stock battery? ebay batteries last me about 9-12 hours and die. The stock battery is amazing
Exactly the same situation as you:
CM6.
N1.
Student.
Experiences massive drainage in short amounts of time with low usage.
Tried everything.
I'll now be trying Enomther, because yes I have heard CM6 users get worse battery life.
Just a viewpoint on what I'm facing. For the past week I've gone to bed with 100% battery and woken up ~7 hours later on 75%. I've tried WCDMA and GSM auto settings and neither male a difference.
evilkorn said:
Don't use setCPU to manage battery life, only to overclock. It overrides the kernel's settings. Sounds like you need to wipe and flash the rom again. Then gradually add applications you want, something is sucking battery life.
Last, buy a new battery.
Click to expand...
Click to collapse
Thanks for the advice! I'll be looking into this!
KAwAtA said:
I'm using CM6 and I get between 22-32 hours on a single charge. I just use the kernel that comes with it and i almost always have sync on. No GPS or bluetooth though.
Are you using a battery you purchased on ebay? Or are you using the stock battery? ebay batteries last me about 9-12 hours and die. The stock battery is amazing
Click to expand...
Click to collapse
I'm using the stock battery so I don't know what the problem. I just ordered another official stock battery though yesterday and I'm going to see if there are any differences.
Forge94 said:
Exactly the same situation as you:
CM6.
N1.
Student.
Experiences massive drainage in short amounts of time with low usage.
Tried everything.
I'll now be trying Enomther, because yes I have heard CM6 users get worse battery life.
Just a viewpoint on what I'm facing. For the past week I've gone to bed with 100% battery and woken up ~7 hours later on 75%. I've tried WCDMA and GSM auto settings and neither male a difference.
Click to expand...
Click to collapse
Thanks, I'm glad I'm not the only one with this problem. I thought I was being an idiot by doing something wrong...
I've calibrated my battery several times already while trying to fix this issue. Could that have killed my battery life?
1) Discharging the battery below 10-15% is bad for the battery, doing it many time will destroy the battery, making it last just about nothing.
2) Check CPU usage - download System Monitor or some other app like that, and check the running frequency of the phone. When you just run the program and don't touch the phone, it should float around 300 MHz. If you have it locked on 998MHz - you have an app that got your CPU stuck in a loop.
3) Download some app that stores battery stats, and check your discharge current and battery capacity - that way you'll know if it's your battery dead or your apps drawing the juice.
Sorry, double post.
Jack_R1 said:
1) Discharging the battery below 10-15% is bad for the battery, doing it many time will destroy the battery, making it last just about nothing.
2) Check CPU usage - download System Monitor or some other app like that, and check the running frequency of the phone. When you just run the program and don't touch the phone, it should float around 300 MHz. If you have it locked on 998MHz - you have an app that got your CPU stuck in a loop.
3) Download some app that stores battery stats, and check your discharge current and battery capacity - that way you'll know if it's your battery dead or your apps drawing the juice.
Click to expand...
Click to collapse
crap, all the guides that i've read regarding calibration told me to discharge it completely.
My CPU usage seemed normal. It was stable at around 245 and would jump up to 998 from time to time that doesn't last for more than half a second though.
My battery seems to be in good condition as it's labeled as "healthy" by my battery apps and the voltage seemed normal....
lol at this thread...
http://forum.xda-developers.com/showthread.php?t=714184
Do a nandroid back-up of CM6, and then try out the above ROM. You can always go right back to CM at any time.
For calibration, complete discharge is necessary. Doing it once is not too harmful. As long as the battery is reported "healthy" - you're ok.
There are apps that will show you the approximate capacity of your battery in numbers. Try to find one like that.
Please check discharge current and voltage over time. It doesn't make sense that a phone on 245 MHz in sleep mode will draw the current required to discharge 10%/hour.
in same boat as OP
im in the same position as the OP
student.
dont use phone for nearly 7 hrs a day
backlight on lowest, gps and bluetooth off.
ive been looking around for answers (hence why im reading this)
when class gets out ive gone from 100% to nearly 65%
running cm6 and ive wiped battery,
about to switch ROM, maybe that'll help.
adambenjamin said:
lol at this thread...
Do a nandroid back-up of CM6, and then try out the above ROM. You can always go right back to CM at any time.
Click to expand...
Click to collapse
Thanks, I'll look at that ROM and check it out when I get time (probably this weekend).
Jack_R1 said:
For calibration, complete discharge is necessary. Doing it once is not too harmful. As long as the battery is reported "healthy" - you're ok.
There are apps that will show you the approximate capacity of your battery in numbers. Try to find one like that.
Please check discharge current and voltage over time. It doesn't make sense that a phone on 245 MHz in sleep mode will draw the current required to discharge 10%/hour.
Click to expand...
Click to collapse
Cool, thanks for the advice. I'll look for an app ASAP and report what happens.
Branden10 said:
im in the same position as the OP
student.
dont use phone for nearly 7 hrs a day
backlight on lowest, gps and bluetooth off.
ive been looking around for answers (hence why im reading this)
when class gets out ive gone from 100% to nearly 65%
running cm6 and ive wiped battery,
about to switch ROM, maybe that'll help.
Click to expand...
Click to collapse
Awesome, if you find a fix let me know please.
I haven't been able to do any of the suggestions yet but (when it comes to flashing) but I do have an update that might shine more light on this issue.
Today in class I noticed that my N1 was warm when it was in my pocket but nothing was running and gps and bluetooth was off. I checked the temp of my battery it was at 36.1C while it's usually at 30-31C when I'm not doing anything.
Also, I checked spare parts this morning and found that, while I was asleep, my N1 was not asleep for half that time but my screen on for only 4% of that time (probably from my messing with it before and a little bit after sleep).
I've checked to see if anything is running in the background that might lead to this but so far none of my apps should drain my battery that much while I was asleep.
Is this normal? Shouldn't my phone be mostly in sleep mode when I'm asleep since I'm not doing anything to it? As for the battery heating up, do y'all think it's a faulty battery or the fault of the OS?
Thanks again for all of y'all's helpful replies!
Is this normal? Shouldn't my phone be mostly in sleep mode when I'm asleep since I'm not doing anything to it? As for the battery heating up, do y'all think it's a faulty battery or the fault of the OS?
Thanks again for all of y'all's helpful replies!
Click to expand...
Click to collapse
About battery heating...
I checked and mine is at 75-78F while in class. My n1 is also in a case, so for it to be that low is good. Just thought to throw that in as a comparison.
Also i've switched ROMs to help with battery, no luck there. Still experience 7-8% drop per hour.
I've been keeping my phone off now at school, which has helped, though I still lose nearly 15% while it's off.
Sent from my seXus One using XDA App. While I gripe about battery stats.
Branden10 said:
About battery heating...
I checked and mine is at 75-78F while in class. My n1 is also in a case, so for it to be that low is good. Just thought to throw that in as a comparison.
Also i've switched ROMs to help with battery, no luck there. Still experience 7-8% drop per hour.
I've been keeping my phone off now at school, which has helped, though I still lose nearly 15% while it's off.
Sent from my seXus One using XDA App. While I gripe about battery stats.
Click to expand...
Click to collapse
I understand if my battery was at 71-78F but my battery was at almost 97F just sitting in my pocket...
Hmm, I think it's weird that the battery still drops 15% when the phone is off...
adambenjamin said:
lol at this thread...
http://forum.xda-developers.com/showthread.php?t=714184
Do a nandroid back-up of CM6, and then try out the above ROM. You can always go right back to CM at any time.
Click to expand...
Click to collapse
Alright, I just flashed it with that OS. I'll let you know how it goes. Thanks!
timchoi89 said:
Alright, I just flashed it with that OS. I'll let you know how it goes. Thanks!
Click to expand...
Click to collapse
i was using the cyanogen mod 6.0 for my nexus one and had a major battery iss i would wake up for work fully charged 100 percent goes on stand by with my set cpu to the lowest possible and the task manager running... note its on standy by with the screen low powered no gps or wifi running? so its 100 percent charged and then i leave to work arrive at 6 or 6:30 and its down 10 percent or more??? please if anyone knows a good kernel or rom to use please let us know my battery is in good health and from stock.....
Jack_R1 said:
1) Discharging the battery below 10-15% is bad for the battery, doing it many time will destroy the battery, making it last just about nothing.
2) Check CPU usage - download System Monitor or some other app like that, and check the running frequency of the phone. When you just run the program and don't touch the phone, it should float around 300 MHz. If you have it locked on 998MHz - you have an app that got your CPU stuck in a loop.
3) Download some app that stores battery stats, and check your discharge current and battery capacity - that way you'll know if it's your battery dead or your apps drawing the juice.
Click to expand...
Click to collapse
im checking the cpu usage but i really dont know where and which app specificly i use but i took a few pics and will try to post them up as soon as possible....battery stats i will post that up too...please help anyone...i was using cyanogen mod now leofroyo2.1
Simple Poll.
Have you seen a decrease or increase?
Someone can explain this battery drain?
in a lot of roms based on 2.2.1 there is a big battery drain, in some other there isn't.
nagash91 said:
Someone can explain this battery drain?
in a lot of roms based on 2.2.1 there is a big battery drain, in some other there isn't.
Click to expand...
Click to collapse
Reboot after unplugging from USB and battery drain is gone. For further improvement install SetCPU and reduce min/max frequency. I am getting more or less the same lifetime as with donut ROMs.
AndDiSa said:
Reboot after unplugging from USB and battery drain is gone. For further improvement install SetCPU and reduce min/max frequency. I am getting more or less the same lifetime as with donut ROMs.
Click to expand...
Click to collapse
OK I have done.. but the problem is that when I use it 3 o 4 minutes (for example I install an application using a file explorer, then I read a message and then I come back to home) m battery get 5% lower...
In standby I lose 10% in 6 - 7 hours (I think this is normal).
AndDiSa said:
Reboot after unplugging from USB and battery drain is gone. For further improvement install SetCPU and reduce min/max frequency. I am getting more or less the same lifetime as with donut ROMs.
Click to expand...
Click to collapse
I am currently without a computer therefore immune to this USB bug. I flashed CM6.1 to this and the other g1 and both suffered substaintial amounts of battery drain so I nandroid restored back to CSDIv4 and still the lowest frequencies and settings did little to combat the descending digits. So I tried this...
Recalibrated my battery
Flashed SuperWipe.zip
Reboot
Flashed SparksMod's latest
Reboot
Wiped battery stats
Unplugged...reboot
Battery lasted 23 hours the first day never seen anything like it.
Lifes great.
Sent from my HTC Grandaddy via XDA app
Sent from my HTC Grandaddy via XDA app
I'm using TMUS-G1-Froyo CM6 remix..
and I'm using the new radio with +14mb.
The rom flies but the battery go down too fast.
I'm using setCPU with 256 - 528 mhz while screen is on, 122 - 256 mhz while screen off.
If I go to battery use in settings I see
Cell standby 45%
display 28%
phone idle 22%
android system 3%
I don't think is normal... cell standby is the battery use by cell radio..
I wonder if the new radio give a big battery drain..
nagash91 said:
I'm using TMUS-G1-Froyo CM6 remix..
and I'm using the new radio with +14mb.
The rom flies but the battery go down too fast.
I'm using setCPU with 256 - 528 mhz while screen is on, 122 - 256 mhz while screen off.
If I go to battery use in settings I see
Cell standby 45%
display 28%
phone idle 22%
android system 3%
I don't think is normal... cell standby is the battery use by cell radio..
I wonder if the new radio give a big battery drain..
Click to expand...
Click to collapse
I got real excited when I heard about the new radio and hboot even thought that its exclusion was the source of the the battery issues. Haven't been able to try it as I'm without a up-to-date PC at the moment.
It would be real nice if I could find a seasoned dev who understands battery consumption. I thought the kernal was the main culprit but I've tried two different roms with the same kernal and one has notably better battery life than the other. So confusing.
Sent from my HTC Grandaddy via XDA app
I can't use my phone with this battery drain...
I will come back to official android OTA-AOSP 1.6.. with +14mb.
So I'll test if this kernel with 14mb is a cause of battery drain.
PS: I'm not a lover of rom customizations.. I think the official roms are the best.
The other are all too heavy. I'm not a fan of cm kernel, that is too heavy for g1.
I would see an official OTA 2.2 without customizations, so every one could customize as he want, and if he want.
PS: OK I flashed AOSP 1.6 using ezBiff_kernel to have 15mb (cause I have new radio and spl, so I can flash roms only using this kernel).
Result: my battery life is similar to froyo 2.2 roms... so the problem is:
1) Kernel? (ezBiff_kernel is based on cyanomod kernel... ... ... heavy as death)
2) New radio/spl?
3) My battery (I don't think so.. it's new battery. I buy it 2 weeks ago and in the beginning it works so well.. but then I flashed new radio/spl and new kernel for 15mb..)
nagash91 said:
1) Kernel? (ezBiff_kernel is based on cyanomod kernel... ... ... heavy as death)
Click to expand...
Click to collapse
Come now.. the cm pershoot kernels are super optimized so they don't collapse under the heavy as death rom that is usually on top of it..
I get mixed results with that kernel between testing and feedback.
A test phone can idle on wifi+2g for days on the stock g1 battery even after a usb unplug.. but on more common use with syncing services its not performing as well as I'd like..
Some of it is fixed with less swap/compcache or changing clock speeds 122/480 for most the speed but lower voltage levels. Also the interactive governor may work better.. I'm testing these ideas if results are good my next kernels defaults will use them.
Cm/pershoot have some interesting new power management code from other htc devices.. So hopefully soon all will be better. (I merged most of it to my kernel but there are some loose ends.. works well untill the phone locks up.. so no public release yet)
ezterry said:
Come now.. the cm pershoot kernels are super optimized so they don't collapse under the heavy as death rom that is usually on top of it..
I get mixed results with that kernel between testing and feedback.
A test phone can idle on wifi+2g for days on the stock g1 battery even after a usb unplug.. but on more common use with syncing services its not performing as well as I'd like..
Some of it is fixed with less swap/compcache or changing clock speeds 122/480 for most the speed but lower voltage levels. Also the interactive governor may work better.. I'm testing these ideas if results are good my next kernels defaults will use them.
Click to expand...
Click to collapse
Ok sorry I talk without knowledge. I really don't know the effect of the cm kernel. I only know that all roms based on cm release, with cm kernel, are so heavy and slow.
I like your rom (2.2.1 AOSP) and I love your new way to get 14mb.
But I have this orrible problem. My phone has a lot of battery drain when I use it. With screen off, no problems.
I have never used swap or compcache in this days, and I also try different clock speeds (not over 528mhz).
The result is that when I unlock my phone, I go to settings, I see for example 95% battery. Ok, I return to home, I open a message, I return to home, I open contacts and I scroll some contacts without make calls.
Then I come back to battery settings and I see that is 92-93%..
in 2 minutes of soft use.. I think this is impossible. If I open stupids 2D games... ahah in 5-10 minutes my battery lose 10 - 20%.
I remember 1 year ago, with 1.6 (no cyanomod) my battery was good.
Now it isn't (I have a new battery).
Today I flashed aosp 1.6 with your kernel for 14mb (I have new radio&spl) but nothing... I lose a lot of battery percent as in froyo.
So I think problem is or battery calibration, or something to wipe, or cm kernel, or new radio&spl + your new kernel...
Now I'm recalibrating battery (is at 1% from 2 hours, I'm not using it.. ) then I will recharge for 8 - 9 hours and then wipe battery state, but I have done this process a lot of time without a benefit.
I'll try to remove the new radio+spl (so also using standard kernel) if my battery continue to lose percents so fast.
I'll keep you update on my "story".
PS: Sorry for my bad english!! XD
OK.. after a day of low discharging and a night of 8 hour of recharging, I wiped battery states, I wiped data-cache-ext ecc... I flashed aosp 1.6 and ezbiff kernel..
"battery drain" continue...
I will try tomorrow to reflash death-spl and old radio..
BTW, is normal for hours battery 4v at 90%?
On the back of the battery sais 3.7v... I thought 3.7 was the voltage for 100%
Update
I know this thread is a little old, but I ran into this problem as well. What I found was that the official US radio (2.22.23.02) used considerably more battery than the international one (2.22.19.26i). The other thing I noticed is that switching to "use 2G networks only" in mobile networks settings and disabling data over mobile drastically improved battery life.
I also noticed that wifi used a fair bit of juice so my recommendation is to disable wifi if you're going to be on the go for a bit, and disable data/3g if you're just going to be hanging out in the local webcafe, your/a friend's house, or some other location with wifi access for a while.
If you wanted to be ambitious and cared enough you could write a script to use as a shortcut on the home screen to do the swap automatically (detect which setting(s) are enabled and swap them to the opposite).
With those changes, you should get much better battery life. My thoughts on different Froyo flavors is that possibly different builds have different settings by default. Cyanogen comes with data and 3g enabled by default so this will quickly suck out your battery if you're running your 3g, 2g and wifi antennas all at once.
The stock build (1.6) got about the same battery life as I'm getting now with those settings applied. With either build, having all antennas on all the time will drain your battery very rapidly. Being a little more cognizant of the settings (perhaps you also had it set to 2g only on the stock build) you're using will significantly improve your battery life. And when I say significantly, I mean night and day (but the antenna version definitely does also make a difference... at least in my case).
Hi,
I don't have sufficient posts to be able to participate directly in that forum, so have no other choice but to raise my queries here.
I've just flashed over from Overcome "Hermes" to "Jupiter". All's well except that the battery performance is quite drastically affected for me.
I've been reading the improved battery life "Jupiter" gets over earlier versions of the Overcome ROMs, but I seem to be experiencing the opposite.
Already did the batt stat wipe via recovery menu. Do I need to so call "run-in" before it reflects correctly? Even if accuracy is one thing... but dropping 3% just on bootup.... is this typical of an uncalibrated battery?
Appreciate any advise here on what I should do. (Apart from a fresh wipe install )
Thanks
I appreciate the enthusiasm these coding geniuses have in rolling out update after updates in the ROMS yet I am apprehensive about the effect of these frequent flashing on the Galaxy Tab components itself. This includes the battery.
My job involves electronic repair and there is a so called number of hours before an equipment goes for a thorough check(preventive maintenance) say for example 1000 hours on a meter. Unfortunately the galaxy tab (or any tablet) does not have this. So if you frequently do a flashing on your tab you subject the electronic components to unnecessary stress,thereby affecting the life of the components like the battery.
In "normal" everyday use of the tab you will seldom do any restart/reboot of your tab,yet in flashing ROMs as many as 3 reboots is needed. As I don't know how to measure the surge in current during reboot, I can just imagine how high an initial current during startup is generated, thus putting a big strain on the battery.
Unfortunately the battery is not user detachable.
There was an author here in XDA describing himself/herself as an "flashing addict"(or something similar). I would like to appeal to everyone-please don't be a flashing addict.
As for battery issue read here
JUST MY FEW CENTS!
PCdumb said:
Hi,
I don't have sufficient posts to be able to participate directly in that forum, so have no other choice but to raise my queries here.
I've just flashed over from Overcome "Hermes" to "Jupiter". All's well except that the battery performance is quite drastically affected for me.
I've been reading the improved battery life "Jupiter" gets over earlier versions of the Overcome ROMs, but I seem to be experiencing the opposite.
Already did the batt stat wipe via recovery menu. Do I need to so call "run-in" before it reflects correctly? Even if accuracy is one thing... but dropping 3% just on bootup.... is this typical of an uncalibrated battery?
Appreciate any advise here on what I should do. (Apart from a fresh wipe install )
Thanks
Click to expand...
Click to collapse
According to the Tweaks section at the team overcome website, it will take several charge cycles before you notice an improvement after the stat wipe. Try giving it a few days before going any further.
PS Not to question your ability to follow instructions (sometimes we miss things) but did you charge to 100% with the tab off?
Yes, I did charge to 100% with the Tab off.
Now upon reading the instructions once more..... I might have conducted it slightly different from the written procedure.
I unplugged the Tab from the mains, then only booted up and wiped the batt stats before re-booting. Hmmm.... maybe I'll go try booting up while still plugged into the mains, do the batt stat wipe, and re-boot. (all while plugged into the mains). Then only unplug the charger.
Wonder is there any diff in doing so.....
Would definitely try re-doing it with the tab plugged in while doing the stat wipe. And if it doesn't seem to fix it, do go through a few cycles before reverting back to a previous ROM.
It's important to completely drain your battery before recharging it to 100% in order to complete a cycle.
Hope you fix it. Battery life results vary between tab's even if they are used very similarly, I'm running the OVERCOME Jupiter ROM with IMPROVED battery life. I keep my Bluetooth, Wifi and GPS on all the time. I also flash quite often and have not seen a decrease in overall battery life. It seams that each tab is a bit different, hardware wise, than one another. Everything from battery to board it seems is slightly different coming out of the manufacturing process.
Thanks. Will try that out.
But it just seems strange coming from Overcome ver 1.4 (Froyo) which had no batt drain problem.... to Hermes which was better in batt performance.... to Jupiter which I'm experiencing heavy drain.
As I did a NoWipe install, all apps and setting are similar (except the new market app).
I was able to run 2 movies back to back (about 3 hours total) and still have at least 40% life left (usually about 45 to 50%). Now on Jupiter, just fiddling around testing the various features for functionality, plus maybe an hour of NFS (total about 3 hours as well).... the batt drops to about 10% life.
Anyway, I'll re-do the calibration and and give it some time to "settle in". Hopefully, that is all that is needed. (I would hate to have to do a full wipe install... and re-installing all apps)
PCdumb said:
Thanks. Will try that out.
But it just seems strange coming from Overcome ver 1.4 (Froyo) which had no batt drain problem.... to Hermes which was better in batt performance.... to Jupiter which I'm experiencing heavy drain.
As I did a NoWipe install, all apps and setting are similar (except the new market app).
I was able to run 2 movies back to back (about 3 hours total) and still have at least 40% life left (usually about 45 to 50%). Now on Jupiter, just fiddling around testing the various features for functionality, plus maybe an hour of NFS (total about 3 hours as well).... the batt drops to about 10% life.
Anyway, I'll re-do the calibration and and give it some time to "settle in". Hopefully, that is all that is needed. (I would hate to have to do a full wipe install... and re-installing all apps)
Click to expand...
Click to collapse
As mentioned in the Tweaks section, perform the Stat wipe and then two full recharge cycle
recharge to 100% (while the Tab is closed) then drain the battery till it is off then repeat the cycle and you will enjoy it man
Please tell me if you need anything
bongski55 said:
I appreciate the enthusiasm these coding geniuses have in rolling out update after updates in the ROMS yet I am apprehensive about the effect of these frequent flashing on the Galaxy Tab components itself. This includes the battery.
My job involves electronic repair and there is a so called number of hours before an equipment goes for a thorough check(preventive maintenance) say for example 1000 hours on a meter. Unfortunately the galaxy tab (or any tablet) does not have this. So if you frequently do a flashing on your tab you subject the electronic components to unnecessary stress,thereby affecting the life of the components like the battery.
In "normal" everyday use of the tab you will seldom do any restart/reboot of your tab,yet in flashing ROMs as many as 3 reboots is needed. As I don't know how to measure the surge in current during reboot, I can just imagine how high an initial current during startup is generated, thus putting a big strain on the battery.
Unfortunately the battery is not user detachable.
There was an author here in XDA describing himself/herself as an "flashing addict"(or something similar). I would like to appeal to everyone-please don't be a flashing addict.
As for battery issue read here
JUST MY FEW CENTS!
Click to expand...
Click to collapse
where you were hiding this all ? i bet you were so damn angry to say all of this , i never saw you writing more than 3-4 lines , chill out buddy .
@The OP flashing custom roms means battery need to re-life back
bongski55 said:
I appreciate the enthusiasm these coding geniuses have in rolling out update after updates in the ROMS yet I am apprehensive about the effect of these frequent flashing on the Galaxy Tab components itself. This includes the battery.
My job involves electronic repair and there is a so called number of hours before an equipment goes for a thorough check(preventive maintenance) say for example 1000 hours on a meter. Unfortunately the galaxy tab (or any tablet) does not have this. So if you frequently do a flashing on your tab you subject the electronic components to unnecessary stress,thereby affecting the life of the components like the battery.
In "normal" everyday use of the tab you will seldom do any restart/reboot of your tab,yet in flashing ROMs as many as 3 reboots is needed. As I don't know how to measure the surge in current during reboot, I can just imagine how high an initial current during startup is generated, thus putting a big strain on the battery.
Unfortunately the battery is not user detachable.
There was an author here in XDA describing himself/herself as an "flashing addict"(or something similar). I would like to appeal to everyone-please don't be a flashing addict.
As for battery issue read here
JUST MY FEW CENTS!
Click to expand...
Click to collapse
Viewed purely from an engineering perspective, I'm unable to see any significant connection between the flashing of the ROM and a degradation of battery capacity. Further, in the event that the TAB was connected to a charger during the flashing, I can see absolutely no connection at all! Please help me understand your logic.
Ok Back on topic. PCdumb (dude what's with the username lol). Check your app list. It could a new app you or an old app you updated or an app you didnt use before but you use now that is being a battery hog. A small trick I learned is checking apps running services in the background. Go to Settings, applications, running services and check (why is skype working after Isigned out its not a battery drainer but I hope you got the picture).
Thanks for the advise. That was one of the 1st few things I did to check that there's nothing out of the ordinary running in the background and taking up the juice.
Mine's actually draining alot when in usage. Not too sure about when in standby.... will check later.
If after a few charge cycles and the drain is still bad, guess my only next best option is to do a full wipe, re-stock and re-install.....
I did not get any effect from Battery calibration. As expeced. Anybody did actually?
The background services instead might have an effect on power consumption, I agree. But needs numerous testing...
Batt recal did not give me better battery life. There's no difference in the battery performance after 3 recharge cycles.
My tab can at most get slightly more than 5 hours of continuous usage compared to about close to 7 hours on hermes. This is when i dial down the OC from smartass mode to conservative and also put the min freq to 200 instead of 400 which was the setting i was using all the while.
Doesn't seem to be anything else running in the background. On standby overnight, i only lose about 3% which is not too bad. But when in use, that's where the Batt drains fast. Just for comparison, i only lost 1% at most for overnight standby of about 7 hours when running hermes.
Guess I'll have to live with this if i want the speed and smoothness. Still contemplating whether to restock and do a clean flash.
PCdumb said:
Batt recal did not give me better battery life. There's no difference in the battery performance after 3 recharge cycles.
My tab can at most get slightly more than 5 hours of continuous usage compared to about close to 7 hours on hermes. This is when i dial down the OC from smartass mode to conservative and also put the min freq to 200 instead of 400 which was the setting i was using all the while.
Doesn't seem to be anything else running in the background. On standby overnight, i only lose about 3% which is not too bad. But when in use, that's where the Batt drains fast. Just for comparison, i only lost 1% at most for overnight standby of about 7 hours when running hermes.
Guess I'll have to live with this if i want the speed and smoothness. Still contemplating whether to restock and do a clean flash.
Click to expand...
Click to collapse
If you want to confirm that JUPITER is the reason that you are experiencing poor battery life, try re-installing a previous version that you feel worked better for you. Maybe reverting back to a previous version may yield better battery results, and I sure hope so, this way you will know if it's the ROM or other elements affecting the abnormal battery drain.
If you do see an increase in battery life, try flashing JUPITER again, see what the results are. I don't know if flashing and re-flashing will have a negative long term effect on your SGT, I know that I flash every time a new release is out (Stock safe, cooked ROM, Kernel) and if i'm not happy with the release i go back to a proven one by flashing another three times (stock safe, cooked ROM, Kernel) and so far I have not had any (knock on wood) abnormal battery activity.
It's worth giving it a shot (if you haven't already).
EDIT: I know, I know the proper sequence is stock safe, kernel, rom.
after week of using the Overcome ROM i can confirm that the battery performance is between 85 and 90% from the Orignial stock ROM performance
No problem since this is normal as we are using a cooked ROM
bongski55 said:
I appreciate the enthusiasm these coding geniuses have in rolling out update after updates in the ROMS yet I am apprehensive about the effect of these frequent flashing on the Galaxy Tab components itself. This includes the battery.
My job involves electronic repair and there is a so called number of hours before an equipment goes for a thorough check(preventive maintenance) say for example 1000 hours on a meter. Unfortunately the galaxy tab (or any tablet) does not have this. So if you frequently do a flashing on your tab you subject the electronic components to unnecessary stress,thereby affecting the life of the components like the battery.
In "normal" everyday use of the tab you will seldom do any restart/reboot of your tab,yet in flashing ROMs as many as 3 reboots is needed. As I don't know how to measure the surge in current during reboot, I can just imagine how high an initial current during startup is generated, thus putting a big strain on the battery.
Unfortunately the battery is not user detachable.
There was an author here in XDA describing himself/herself as an "flashing addict"(or something similar). I would like to appeal to everyone-please don't be a flashing addict.
As for battery issue read here
JUST MY FEW CENTS!
Click to expand...
Click to collapse
WOW ! This was an eye opener for me...
Thanks for clarifying this...... I didn't know this was so bad for the hardware ....
Sent from my GT-I9003 using Tapatalk
PCdumb said:
Batt recal did not give me better battery life. There's no difference in the battery performance after 3 recharge cycles.
My tab can at most get slightly more than 5 hours of continuous usage compared to about close to 7 hours on hermes. This is when i dial down the OC from smartass mode to conservative and also put the min freq to 200 instead of 400 which was the setting i was using all the while.
Doesn't seem to be anything else running in the background. On standby overnight, i only lose about 3% which is not too bad. But when in use, that's where the Batt drains fast. Just for comparison, i only lost 1% at most for overnight standby of about 7 hours when running hermes.
Guess I'll have to live with this if i want the speed and smoothness. Still contemplating whether to restock and do a clean flash.
Click to expand...
Click to collapse
After reading all this superb discussion....
I would just recommend you to go back to your older rom.....
Its forbthe best....
Sent from my GT-I9003 using Tapatalk
I do get 4 to 5 hours of continuous use with overcome Jupiter, mostly browsing the web over
WLAN or umts. Hermes release didn't gave me so much more juice, probably 5 hours.
In the background I have emai push, contacts and calendar sync and some instant messaging apps, if I switch off all that I might get an hour or so more.
PCdumb said:
...On standby overnight, i only lose about 3% which is not too bad. But when in use, that's where the Batt drains fast. Just for comparison, i only lost 1% at most for overnight standby of about 7 hours when running hermes...
Click to expand...
Click to collapse
Wow, maybe your tab is one of the ones with a battery from the bad batch, and it's finally on its way out. I upgraded from the stock AT&T Rom to Overcome Jupiter, and on Airplane Mode with all stock settings (no overclock or undervolt), mine only drops 1% in standby over 14 hours and I can get about 5 hours of video watching straight with the brightness on max before it dies!
DarkPal said:
A small trick I learned is checking apps running services in the background. Go to Settings, applications, running services and check (why is skype working after Isigned out its not a battery drainer but I hope you got the picture).
Click to expand...
Click to collapse
I also been experiencing a major increase in battery drain even after doing a couple wipes exactly according to the tweak guide. I went from about 24 hour normal use down to 6-8 hours normal use.
Checked the services as per your suggestion above and found a couple major battery drainers running. Skype and Yahoo but also Google+. What I dont understand is why Skype and Yahoo would be running even though I had not started either since at least several re-boots ago. I had Skype and Yahoo installed for quite a while Google+ is a new one. Anyway I killed all of them and now and will see what happens next.
Not sure thought that this is all there is to the issue. Recahrging is finiky as well. I can turn off the tab and let it charge all night just to find that it charged to about 70% if I re-plug it might charge to 90%-95% and then if re-plug it might get to 100%. The drain from 100% to 60%-70% is extremely fast and still quite fast from there. On one occasion after complete drain I couldnt get it to start charging at all for about 5-10 minutes. I was checking power, cables, connections and starting to panic when all of a sudden it started to charge.
Any advice on possible reasons or solution woud be appreciated. Not sure I want to go beck to stock ROM and un-root just to take it to service center for repairs.