[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Zev.Isert:
Hi xda-dev

I'd like to ask you guys for your input on a battery issue I've been having. I know you get many a question on batteries, despite this I haven't been able to find an answer, nor anything even related to what I'm trying to fix. I'm at a point where the phone wont last a day of idle at school with it not leaving my pocket, and I don't know what I need to do to resolve this rather unique issue.

I have two S3s, and therefore two batteries. On one of the phones the screen is shattered, so I use it to charge the extra battery. To do so I wrote a tasker profile which voices the battery percentage and time charging when it detects that the screen is "on" (i.e. power button pressed). I installed the exported app factory apk to the broken S3 by swapping motherboards. This setup has been working great for me because I never had to plug my S3 in, I could simply charge one battery at home while the other was in use. That is until about 3 weeks ago now where I've begun to notice that the phone I carry with me cannot properly read the percentage of charge remaining on the battery. I believe the issue started after a return to stock rom for unlocking, or flashing leankernel. A factory reset and all caches have been cleared since.

Here are some symtoms:

It remains unable to charge the battery above ~70%, without using the charging phone,

drains very rapidly,

upon reaching 0% a reboot causes the battery to return to roughly 45%,

and finally the battery percentage may raise while the phone is

not

charging

the charge may sit at within the range of 1% to 3% for extended periods of time (see screenshot).

And here is some data:

Rooted

Custom Rom: CyanogenMod Version 10.1.0-RC5-d2att

Rom build number: cm_d2att-userdebug 4.2.2 JDQ39E eng.jenkins.20130607.100250 test-keys

Custom Kernel Version: 3.4.49-leanKernel-att_aosp_43-6.4-+imoseyon@imoseyon #56 Sun Jun 16 19:21:51 PDT-2013

CPU governor: ondemand

CPU Min/Max: 384/1512 MHz

Few apps installed as I just did a factory reset, with Google latitude location reporting set off.

While writing this post I swapped the batteries between the phone I use and the charging phone. The dead battery read 4% before I powered down, but when it was put into the charging phone it immediately voiced that that same battery had 81%. The battery that was removed from the charging phone was at 100%, but when the other phone booted that "charged" battery had 89%. That reading was taken when I started typing this post, at 5:45, and now 15 minutes later (6:00) the battery has lost 23% leaving it at 66. The draining phone sat idle while I wrote this post, as I am on my laptop, so that drop of 23% occurred with about 90% screen off time, (note that media scanner would be running since the phone just booted).

In the following screenshots you will notice the time is over 24 hours, this is because the phone has not held a 100% charge since then. Large direct jumps of power are either simple reboots or a battery change. Notice the graph increasing without the charging state being active. I chose not to include a bbs screenshot because the phone had just booted so there were no good reference points. Total screen on time is 4 hours 20 minutes, and 8tracks has had a CPU total of 1 hour 20 minutes with a keep awake of 2.5 hours.

Thanks for any help you can suggest.