Database Info

[Q] Battery drain on Galaxy S with Teamhacksung Build 13

Hey guys,
I'm having trouble with the battery for my Galaxy S depleting really quickly (about 10% per hour).
I'm running ICS with teamhacksung's latest build (13) and platypus 3.08 NEO 3.0 kernel.
I thought initially that it was a kernel problem (I was running FUGU, which isn't on the preferred list of hacksung), so yesterday I wiped the whole thing, upgraded from build 12 to 13, flashed the kernel, wiped all of the caches and restarted.
The battery seemed fine and it decreased about 10% in 8 hours on standby, which is more than acceptable.
Then I was wokenup at 5 am by the phone telling me it needed charging (it had dropped 70%+ charge in 5 hours). By looking at the battery stats (attached below) it says that 70% of the battery is drawn by the OS, upon closer inspection it seems as though the system is draining when it becomes actives, and it looks as though it's becoming active on a regular interval. I thought this might be due to Appkiller, but I've since disabled it and it still seems to be draining pretty quickly.
The only other thing I can think of is that when I receive an email or sms, the settings and back buttons light up and stay on. Could that be the drain?
Anyone have an idea?
Thanks a mil
Cheers
Paul

Update: Swype to blame
Hi guys, I think I've solved it. If I don't post here again then I am right.
The problem is Swype. I installed it on ICS and it works great, but when I try to download additional languages, it seems to get stuck in a loop of attempting to download and failing. This results in the phone constantly being on and never going to sleep more which depletes the battery in a matter of hours, and of more than 170mb of mobile data raked up in a couple of days.
I haven't reinstalled Swype yet, I want to see if the battery lasts today before I do, but I will try to reinstall it without the additional languages and see if it works like that.
Cheers
Paul

Yes, confirmed, it was the installation of additional Languages in Swype.
Cheers

Thanks a lot for your question + solution. Using devil 1.1 kernel and Teamhacksung build v16 I had exactly the same problems. Now I removed Swype, which didn't want to download the Dutch language pack anyway.

[Q] cm9 kang rom battery file

So, I was using kang's cm9 for a while now, and the the battery messed up something - it turned off while still having half battery displayed, and wouldn't turn on till charging began. I remember from other roms, there was a config file we used to delete when stuff like this happened. Does anyone know which battery file would that be in CM9 Kang?

What are you running Kernel-wise? Faux with DS driver? Otherwise, boot to CWM and under advanced wipe battery stats. Which Kang are you using?

First off, if you're using Faux's DS kernel then that means you were actually out of battery since the DS kernel has bad battery readings. Make sure you're on the fourth update (selfkang3).

IRASadPanda said:
First off, if you're using Faux's DS kernel then that means you were actually out of battery since the DS kernel has bad battery readings. Make sure you're on the fourth update (selfkang3).
Click to expand...
Click to collapse
Exactly... If you are on ds kernel you will have really funky batt readings.. He states it himself in the op.
Sent from my LG-P999 using XDA App

I've never messed with kernels.
Under "Kernel Version": 2.6.32.55-cyanogenmod
[email protected]))
Under "CyanogenMod version": 9.0.0-RC0-SelfKANG1-G2x
Under "Build date": Mon Deb 13 16:27:34 WET 2012
Under "Build number": IML74K
So, I am not running the latest beta? I haven't had time to keep with it. Where can I find the latest one?

I've been using the newest KANG for a while now, and the battery life is significantly better than CM7 was. Leaving the phone in standby all night would drain the battery about 30% or so, now it drains 5-10% at best. I've never had the battery readings become all 'funky'. The phone lasts a full drain from 100-0% if I let it, and it takes days to do so.

JaiaV said:
I've been using the newest KANG for a while now, and the battery life is significantly better than CM7 was. Leaving the phone in standby all night would drain the battery about 30% or so, now it drains 5-10% at best. I've never had the battery readings become all 'funky'. The phone lasts a full drain from 100-0% if I let it, and it takes days to do so.
Click to expand...
Click to collapse
cool story, is that the rom i am using?

aplsux said:
Under "CyanogenMod version": 9.0.0-RC0-SelfKANG1
Click to expand...
Click to collapse
Ah ha! Find a post from the 20th or the 21st and get SelfKANG3 it has auto brightness and that may help you with general battery life, as far as the odd readings have you wiped battery stats? Though assuming you've charged it by now from what I understand your battery stats would have been erased by now. In anycase, do get SK3.
Sent from my LG-P999 using xda premium

JaiaV said:
I've been using the newest KANG for a while now, and the battery life is significantly better than CM7 was. Leaving the phone in standby all night would drain the battery about 30% or so, now it drains 5-10% at best. I've never had the battery readings become all 'funky'. The phone lasts a full drain from 100-0% if I let it, and it takes days to do so.
Click to expand...
Click to collapse
The funky battery stats are only for Faux's DS kernel, and dang, 30% a night is not right, on GB I only lose about a % per hour I sleep, so 8% overnight.

Волк said:
Ah ha! Find a post from the 20th or the 21st and get SelfKANG3 it has auto brightness and that may help you with general battery life, as far as the odd readings have you wiped battery stats? Though assuming you've charged it by now from what I understand your battery stats would have been erased by now. In anycase, do get SK3.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
thank you Wolf. I did update to SK3, altough the fixed bugs were not very big
I could live without the auto brightness. they should fix the video first, that's my main wish. But I recognize all the hard work they put, kudos. Imagine the world without devs.

Пажалуйста, yea, the bug fixes aren't huge, but the auto brightness will help with the battery drain. Another "trick",.Which I picked up from someone else, is to create a profile in Set CPU so that the.clock speed is minimal when your screen is off.
Sent from my LG-P999 using xda premium

CM 9 Alpha 3 & 4 Battery Issues

I'm having a weird issue with the battery gauge on the CM 9 Alpha 3 and 4 ROM's. If the phone is rebooted when the battery is between ~40% to 70% it shows that the battery will drop to ~15% immediately after rebooting. I've been through calibrating and wiping the battery stats both with the calibration program and through CWM recovery. The battery is showing 3759mV at the time it's reporting 15% after the reboot. I've tried 2 batteries which are both stock batteries, one is about 6 months old and the other is 2 months old. I never noticed this as a problem before, I was running pure stock up until 2 weeks ago. I had the MIK Rom on it for a week, then put CM9 Alpha 3 last week, and Alpha 4 this morning. You can see the "display on" time and massive drop at reboot on the attachments. It also reflects the drains while I was making calls and playing throughout the day. Am I missing something or is there something else to check?
Thanks, I really like this ROM and hope this is just a glitch or me missing something.

The stock batteries are infamous for their very low charges. Get an aftermarket battery.
Sent from Spaceball One.

blackknightavalon said:
The stock batteries are infamous for their very low charges. Get an aftermarket battery.
Sent from Spaceball One.
Click to expand...
Click to collapse
I've been reading through the battery posts on here and am leaning that way. But even with that in consideration, I wouldn't think there would be such a dastric drop like that, and I didn't notice this before until I put the new ROM's on. I'm thinking about going back to another ROM and see if the problem still exists there.

txmtb said:
I'm having a weird issue with the battery gauge on the CM 9 Alpha 3 and 4 ROM's. If the phone is rebooted when the battery is between ~40% to 70% it shows that the battery will drop to ~15% immediately after rebooting. I've been through calibrating and wiping the battery stats both with the calibration program and through CWM recovery. The battery is showing 3759mV at the time it's reporting 15% after the reboot. I've tried 2 batteries which are both stock batteries, one is about 6 months old and the other is 2 months old. I never noticed this as a problem before, I was running pure stock up until 2 weeks ago. I had the MIK Rom on it for a week, then put CM9 Alpha 3 last week, and Alpha 4 this morning. You can see the "display on" time and massive drop at reboot on the attachments. It also reflects the drains while I was making calls and playing throughout the day. Am I missing something or is there something else to check?
Thanks, I really like this ROM and hope this is just a glitch or me missing something.
Click to expand...
Click to collapse
Did you use 6 axis?

Some_dude36 said:
Did you use 6 axis?
Click to expand...
Click to collapse
Nope, just the touch screen.
I know that Lion batteries do not have a linear discharge slope, but with the mV @ 3759 that should reflect ~50% I believe, which is where the % showed before the reboot. But, I didn't check the mV before the reboot. That'll probably be the next thing.

I pulled the lines from battery history.txt file on the sdcard. It looks like the mV dropped around 20mV but the % dropped 40 from the reboot. I streamed videos on YouTube for about an hour and it dropped to 9. Finished it off after that and the phone shut off around 3293mV. The first lines are the reboot.
2012/06/09|17:50:16|-461mA|55%|3702mV|70.7ºF|.500|0
2012/06/09|17:51:28|-461mA|15%|3681mV|71.2ºF|.16|0
2012/06/09|18:01:19|-1mA|15%|3798mV|70.7ºF|.428|0
2012/06/09|18:11:18|-1mA|15%|3798mV|65.3ºF|.13|0
2012/06/09|18:21:18|-3mA|15%|3789mV|62.0ºF|.0|0
2012/06/09|18:31:19|-1mA|15%|3795mV|64.4ºF|.0|0
2012/06/09|18:41:19|-1mA|15%|3780mV|64.4ºF|.0|0
2012/06/09|18:51:18|0mA|15%|3801mV|64.0ºF|.0|0
2012/06/09|19:01:19|-1mA|15%|3759mV|68.9ºF|.385|0
2012/06/09|19:11:19|-2mA|15%|3792mV|64.0ºF|.75|0
2012/06/09|19:21:18|-3mA|15%|3744mV|65.6ºF|.531|0
2012/06/09|19:30:08|-3mA|15%|3783mV|63.6ºF|.200|0
2012/06/09|19:36:48|-3mA|12%|3654mV|65.6ºF|.10|0
2012/06/09|19:46:43|-1mA|10%|3771mV|63.1ºF|.113|0
2012/06/09|19:56:42|-1mA|10%|3675mV|70.8ºF|.588|0
2012/06/09|20:06:42|-3mA|9%|3729mV|66.2ºF|.303|0
2012/06/09|20:14:29|-3mA|9%|3693mV|65.4ºF|.0|0
2012/06/09|20:24:29|-2mA|9%|3666mV|70.7ºF|.1000|0
2012/06/09|20:34:29|-2mA|9%|3645mV|71.4ºF|.998|0
2012/06/09|20:36:47|-1mA|9%|3705mV|72.8ºF|.0|0
2012/06/09|20:46:47|-2mA|9%|3675mV|67.2ºF|.211|0
Sent from my myTouch_4G_Slide using Tapatalk 2

txmtb said:
I pulled the lines from battery history.txt file on the sdcard. It looks like the mV dropped around 20mV but the % dropped 40 from the reboot. I streamed videos on YouTube for about an hour and it dropped to 9. Finished it off after that and the phone shut off around 3293mV. The first lines are the reboot.
2012/06/09|17:50:16|-461mA|55%|3702mV|70.7ºF|.500|0
2012/06/09|17:51:28|-461mA|15%|3681mV|71.2ºF|.16|0
2012/06/09|18:01:19|-1mA|15%|3798mV|70.7ºF|.428|0
2012/06/09|18:11:18|-1mA|15%|3798mV|65.3ºF|.13|0
2012/06/09|18:21:18|-3mA|15%|3789mV|62.0ºF|.0|0
2012/06/09|18:31:19|-1mA|15%|3795mV|64.4ºF|.0|0
2012/06/09|18:41:19|-1mA|15%|3780mV|64.4ºF|.0|0
2012/06/09|18:51:18|0mA|15%|3801mV|64.0ºF|.0|0
2012/06/09|19:01:19|-1mA|15%|3759mV|68.9ºF|.385|0
2012/06/09|19:11:19|-2mA|15%|3792mV|64.0ºF|.75|0
2012/06/09|19:21:18|-3mA|15%|3744mV|65.6ºF|.531|0
2012/06/09|19:30:08|-3mA|15%|3783mV|63.6ºF|.200|0
2012/06/09|19:36:48|-3mA|12%|3654mV|65.6ºF|.10|0
2012/06/09|19:46:43|-1mA|10%|3771mV|63.1ºF|.113|0
2012/06/09|19:56:42|-1mA|10%|3675mV|70.8ºF|.588|0
2012/06/09|20:06:42|-3mA|9%|3729mV|66.2ºF|.303|0
2012/06/09|20:14:29|-3mA|9%|3693mV|65.4ºF|.0|0
2012/06/09|20:24:29|-2mA|9%|3666mV|70.7ºF|.1000|0
2012/06/09|20:34:29|-2mA|9%|3645mV|71.4ºF|.998|0
2012/06/09|20:36:47|-1mA|9%|3705mV|72.8ºF|.0|0
2012/06/09|20:46:47|-2mA|9%|3675mV|67.2ºF|.211|0
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
Looks about right for a stock battery. Get an aftermarket battery.
Sent from Spaceball One.

blackknightavalon said:
Looks about right for a stock battery. Get an aftermarket battery.
Sent from Spaceball One.
Click to expand...
Click to collapse
My stock battery does better than that, and never jumped between values (except with the CM 7 kang). With stock Android and now CM 9, I never have that issue :\

I saw a post in the ROM thread that user jarnom had the same thing happen with the battery gauge. I had it happen again when I was at 50% and after the reboot it was @ 6%. I tried what they did, pulled the battery and waited a minute. Powered back on, and the gauge went back to 48%. I never though about pulling the battery, but it worked to get the gauge back to where it should have been.

try Calibrating your battery?
have you tried calibrating your battery? it is recomended to calibrate after your flash a new rom. first time i calibrated my bat life went up at least x2!
not here to advetise any specific app so search "battery calibration" in the market.
hope this helps?

dir3kt0r said:
have you tried calibrating your battery? it is recomended to calibrate after your flash a new rom. first time i calibrated my bat life went up at least x2!
not here to advetise any specific app so search "battery calibration" in the market.
hope this helps?
Click to expand...
Click to collapse
Yes, and no, at the same time. The actual apps that wipe the batterystats.bin file doesn't do anything but remove the file that stores the usage history of the apps. Seidler2457 pointed that out here on the site.
I did start using battery widget pro to see what it showed compared to the phone as it learns the minimum and maximum values for the battery after multiple complete discharge cycles. It estimates time left on the current charge pretty accurately using the current mA draw on the battery. I use my phone until it is dead at night, and then recharge overnight, so it has a few good complete %1 to %100 cycles on it. It's not affecting the battery life that I can tell, I'm getting the same average times out of the battery every day. Actual battery life has been really excellent on this ROM, it's just a weird issue I noticed.

hey, having a sortve similar issue except now the phones battery isnt even taking a charge ._.

anker battery is awesome just went 2 days 12 hours running cm9 alpha 4

Not to sure what all these negatives mean? This is the first night I ran battery monitor widget
Sent from my myTouch_4G_Slide using Tapatalk 2

strapped365 said:
Not to sure what all these negatives mean? This is the first night I ran battery monitor widget
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
That's the mA field, (current going to/from the battery. Next to it is the % field, then mV, and finally temp. It was showing a - value when the phone was using battery. It does that periodically when the battery is fully charged and still on the charger.

txmtb said:
That's the mA field, (current going to/from the battery. Next to it is the % field, then mV, and finally temp. It was showing a - value when the phone was using battery. It does that periodically when the battery is fully charged and still on the charger.
Click to expand...
Click to collapse
Thanks man, I was thinking good thing my ankers are in shipping right now and will be here Monday/Tuesday lol
Sent from my myTouch_4G_Slide using Tapatalk 2

I've noticed the past few days, after flashing ICS, that my battery hangs at 77% while charging. I completely discharging it right now and deleted battery stats in recovery. My phone is only two weeks old =/

I flashed Alpha 5 earlier tonight and have rebooted 8 times now to check for this issue. Every time the battery stat has come back at the same level as before the reboot, which is awesome. I'm not sure if anything was changed specifically, but the nuisance I had isn't there now. I flashed over Alpha 4 with just a cache and Dalvik wipe.

[Q] JB (bruce cm10 kang) battery won't charge following flash

I just flashed a new revision of the rom [ROM][CM10][Kang][Pyramid][Beta][28 Sept]: http://forum.xda-developers.com/showthread.php?t=1782009, actually the 9/24 version, not today's build. I flashed it over an earlier revision, probably 9/4 or thereabouts. Never had battery charging problems with this phone before. The problem, is that since then, the phone has not charge. The reason that I don't think it's a physical problem is that the charging LED comes on, and the OS thinks that it is charging (shows up in the battery settings dialog). The battery seems to be draining normally, i.e. I might get a full day out of the charge (if I'm lucky, anyway).
So...am at 23% after leaving it on the charger for a few hours during the day and thinking WTF. I just powered the phone off to see if it'll charge that way. Maybe in 15 min, I'll know if that'll work. Oh, yes, I tried wiping battery stats, no help.
I thought of posting in the rom thread, but did not intentionally because it's so hard to keep up with those dev threads (I did search first of course), and I don't know that it's a ROM issue. It may be, please let me know if you think I need to be posting there.
Any ideas? I'm also downloading the 9/28 revision and will flash that after I figure out if the phone will charge while off.

Crap! Not charging while off. That sounds like hardware to me. :<

Weird. Flashed today's ROM and it's charging. Nevermind...

Glad that version fixed it! Sounds like the kernel was freaking out!

CM10 with 4.2 Gapps - Battery Life

I find that the battery life is really bad using recent CM10 nightlies. I'm wondering if this is because of using 4.2 Gapps along with it. Has anyone else had any problems with that? There are always wakelocks, and BetterBatteryStats seems to be sh!t these days as well, as it never gives me any details anymore. I lost over 15% overnight in 7 hours when earlier I would only lose about 2%.