Database Info

battery health

I charge my battery overnight. I'm guessing this is bad for the battery but how bad? And is there some app or something that will stop the charge once it hits 100% while still plugged in? Thanks

I believe the phone has overcharge protection circutry in it already

has anyone noticed that, with the new radio, it takes longer to charge and sometimes it doesn't even reach 100%. however when i reboot it, it actually is at 100%. The the batter indicator isn't as accurate anymore.

JDMr2 said:
has anyone noticed that, with the new radio, it takes longer to charge and sometimes it doesn't even reach 100%. however when i reboot it, it actually is at 100%. The the batter indicator isn't as accurate anymore.
Click to expand...
Click to collapse
yes i have, i wanna say its because its not an official mod, but im using the jf update? maybe its build specific, which one you using jd?
i thought i was the only one to notice

I've used the sapphire radio update w/ 5.0.2Hr5 and the new ADP radio update w/ JF1.5. I noticed this with both combinations.

I am noticing this as well with JF's build
So what is the deal? Is the phone actually fully charged after 2 hours and the meter doesnt actually realize it? will this cause any problems with leaving the phone charging in the wall and overcharging?

I highly doubt it has anything to do with overcharging since it's not a hardware issue.

LOL! It's never been accurate at all with any software build or radio combination. I can charge my phone all the way and pull the battery and reboot and get an accurate reading then. The battery life and measurement has been the biggest flaw with this phone. It hasn't gotten any better with a new build or ever will, imo.

wasn't THIS bad when i had JF1.42 RC33. it was just when I updated to Haykuro's or JF's 1.5 builds. An example will be where I begin charging my phone at 5% and after 3-4 hours, it'll only be at ~65%. I reboot the phone and it automatically fixes itself to 100%. It normally only takes ~2hrs for my phone to charge to 100%.

I'm running The Dude's ADP 1.5 and I noticed also that it takes a lot longer to charge the phone.
Normally if I plug it in, it was fully charged in 2-3 hours. Now it takes more than 5hours

John5788 said:
I am noticing this as well with JF's build
So what is the deal? Is the phone actually fully charged after 2 hours and the meter doesnt actually realize it? will this cause any problems with leaving the phone charging in the wall and overcharging?
Click to expand...
Click to collapse
I am also seeing this same issue. I unplugged my phone from the charger at 11am and it was 100%. At 12:45 it was down to 87%. I fell asleep by the pool and woke up and it was at 52%, this was around 3p. I went home and charge the phone. I looked at it around 5p and it was at 72%. I rebooted the phone with Call+Menu+End(thanx JF, Dude took this out his buld) and it was at 100% when rebooted. It may be that TMOBILE branded G1's may have a underlying hardware/software issue which does not allow the OS to fully read the battery. My assumption and im just taking a stab at this is that possibly since ADP 1.5 features processor frequency change (ie, 528mhz to 384, 122 when sleeping) it may be reading the battery when at 528mhz and then when it drops to 122mhz the phone cant write to the RAM or somehow it gets lost b.c on refresh it reads 100%. I may not know anything about what I wrote but its just a stab at an idea. Maybe someone can do some testing to see what happens internally between ADP and RC33 and/or G1 & ADP.

JDMr2 said:
wasn't THIS bad when i had JF1.42 RC33. it was just when I updated to Haykuro's or JF's 1.5 builds. An example will be where I begin charging my phone at 5% and after 3-4 hours, it'll only be at ~65%. I reboot the phone and it automatically fixes itself to 100%. It normally only takes ~2hrs for my phone to charge to 100%.
Click to expand...
Click to collapse
I agree... it HAS gotten worse with 1.5 builds. It takes for ever to charge up to 100% (especially if you have something running in the background. it might just be the overclocking that's doing it). After rebooting, it will give a more accurate reading. I've noticed also (with all builds) that if you reboot with the charger plugged in... it will give you a false, higher battery reading than if you rebooted with it not plugged in. If you get (or suspect) a false reading, pull the battery while phone is on and let it sit idle for a couple seconds and then reinsert and power on. That should be pretty accurate but it seems most false readings happen while the phone is charging. One way to get around this without rebooting to make sure that it's fully charged is to charge the phone while its off. Just remember green light means 90% or higher and not 100% like ALL other HTC devices. That is part of the problem itself....
if the light turned green when it is charged 100%, alot of these false readings would not be happening. I know that sounds silly but the OS/hardware have to judge when its at 90% even when it's powered off. Kinda more complicated than just orange light when charging and green when fully charged (like all other HTC devices). Instead we have to go from red flashing to red to orange and to green. Maybe that makes sense to some? I don't know for sure... it's merely my long-winded theory about the crazy, ****ed up battery life for this otherwise fantastic device, lol! Sorry for the loooooooonnnnnng reply...

I have dudes. 93 and that's when I ran to the issue you guys are talking about. I happened to just install a battery widget and thoughy that's why it had to reboot for accurate reading it hasnt been long to recharge after uninstall. The other builds all seemed accurate to me. It also seems like my battery doesn't last as long with the new radio but at the samew time it seems that it quickly drops out of the 90's and 80% range but sticks in the lower ranges longer. I don't know why with all of our technology laptops and phones can do the carziest things but only for an unreasonably short amount of time...

I drained my battery letting the phone die, took the battery out, put it back in after a min or so, and began charging. It seems to have fixed the long charging issue. It fully charged my battery in ~2.5hrs. I'll report back if the battery life lasts just as long as it charges.

I think I figured out why the battery never seems to go below 100%

My original device always seems to take forever to go below 100%, and I just got a new device that has the opposite issue - it never goes above 94%. So I did some further tests, tonight.
My 94% device goes down fairly steadily once unplugged. But, the device at 100% does not. Also, when the 100% device is drained and I recharge it, it still says it's charging when its at 100% - so what does this mean?
I think that the battery calibration is off, as we already assumed. So, my 94% device is really 100% and I suspect that it would survive beyond 0% as it probably still has 6% juice left in reality. And, in the case of the 100% device, it's probably mis-calibrated to 105 or 110% (or more?). Since the UI can't show you 105%, it just shows the max of 100% until it goes below 100% which can take some time. I also suspect that the device would cut out at 5% or 10% since it's actually drained completely.
So that's the reason, I think. As to the fix, I don't know. What's weird is that these two devices are so different in terms of how the battery status is calibrated.

How can this be fixed? Or "Recalibrated?

I'm letting one of them completely drain, to see what happens.
At least the 94% one gives me an idea on what the battery life is, since I can just tack on +6%. But the one stuck at 100% is a complete mystery - it could be 5% off, 10% or even more.

Also, these run on 2 cell batteries making 7.4V nominal. All the devices before are using single cell batteries at 3.7V nominal. So Android may have issues with that voltage difference.

roebeet said:
I'm letting one of them completely drain, to see what happens.
At least the 94% one gives me an idea on what the battery life is, since I can just tack on +6%. But the one stuck at 100% is a complete mystery - it could be 5% off, 10% or even more.
Click to expand...
Click to collapse
I had the 100% battery issue before and it took a long time for it to dip below 100% (so long that it seemed unreal). Later I decided to let it drain to zero before recharging it to full again. Since then the battery indicator seemed to behave normally and discharged at a normal rate when the tablet was in use.

Have you tried deleting /data/system/batterystats.bin to wipe battery status? Mine sits on 100% for ages so I'm trying this now.
roebeet said:
My original device always seems to take forever to go below 100%, and I just got a new device that has the opposite issue - it never goes above 94%. So I did some further tests, tonight.
My 94% device goes down fairly steadily once unplugged. But, the device at 100% does not. Also, when the 100% device is drained and I recharge it, it still says it's charging when its at 100% - so what does this mean?
I think that the battery calibration is off, as we already assumed. So, my 94% device is really 100% and I suspect that it would survive beyond 0% as it probably still has 6% juice left in reality. And, in the case of the 100% device, it's probably mis-calibrated to 105 or 110% (or more?). Since the UI can't show you 105%, it just shows the max of 100% until it goes below 100% which can take some time. I also suspect that the device would cut out at 5% or 10% since it's actually drained completely.
So that's the reason, I think. As to the fix, I don't know. What's weird is that these two devices are so different in terms of how the battery status is calibrated.
Click to expand...
Click to collapse

samepic said:
I had the 100% battery issue before and it took a long time for it to dip below 100% (so long that it seemed unreal). Later I decided to let it drain to zero before recharging it to full again. Since then the battery indicator seemed to behave normally and discharged at a normal rate when the tablet was in use.
Click to expand...
Click to collapse
I tried that once, by setting it to never shutoff and letting it go over night. The next morning I charged it to green plus 30m as someone suggested in the TnTL thread, but I still had the problem of the meter sticking at 100% for a long time.
Anyways, I installed 3.0.0(TnTL) on monday and decided to also use the CWM clear battery data option, and now it seems to be dropping more as expected, but I'm not entirely sure that I did it completely correctly as by the time that I did the clear battery data option it would've been below 100% charge since I did so AFTER running the update.zip... just have to wait and see now...

Battery Stays at 100% For Ages
My battery stayed at 100% for ages the first time I charged it. Then it dropped quickly and cut out around 50%. I recharged it and it seems to be behaving more normally now. It still seemed to hang at 100% for a while, but no where near as long as the first time. I'm waiting to see at what percentage it dies this time.

my zt 180 tablet never got above 94% also. And it dropped pretty quickly and at around 40% it seemed to get a second life and slow down, but eventually it went all the way down to about 10% and then I would charge it (about 3 hours max). It too is a 7.4v supply.
My Odroid T had a 3.4 supply and it was pretty linear, showed charged at 100% and went down accordingly, though the developers had some issues with a few software releases where it did behave erraticaly and they did a few patches that fixed it.

roebeet said:
My original device always seems to take forever to go below 100%, and I just got a new device that has the opposite issue - it never goes above 94%. So I did some further tests, tonight.
My 94% device goes down fairly steadily once unplugged. But, the device at 100% does not. Also, when the 100% device is drained and I recharge it, it still says it's charging when its at 100% - so what does this mean?
I think that the battery calibration is off, as we already assumed. So, my 94% device is really 100% and I suspect that it would survive beyond 0% as it probably still has 6% juice left in reality. And, in the case of the 100% device, it's probably mis-calibrated to 105 or 110% (or more?). Since the UI can't show you 105%, it just shows the max of 100% until it goes below 100% which can take some time. I also suspect that the device would cut out at 5% or 10% since it's actually drained completely.
So that's the reason, I think. As to the fix, I don't know. What's weird is that these two devices are so different in terms of how the battery status is calibrated.
Click to expand...
Click to collapse
Warning: Slightly off topic -
I'm glad Roebeet was able to get a 2nd Gtab. Hope you found a good discount. Happy Holidays!!!
Now back to the topic discussion...

Butch1326 said:
Warning: Slightly off topic -
I'm glad Roebeet was able to get a 2nd Gtab. Hope you found a good discount. Happy Holidays!!!
Now back to the topic discussion...
Click to expand...
Click to collapse
Off-Topic x2 : yep, got used one that another XDA user had returned!
On-Topic: Still waiting for the battery to discharge, it went to sleep last night. Getting close....

roebeet said:
Off-Topic x2 : yep, got used one that another XDA user had returned!
On-Topic: Still waiting for the battery to discharge, it went to sleep last night. Getting close....
Click to expand...
Click to collapse
I also had the issue of battery showing 100% for a long time and then cutting out around at 50%. One of the posts mentioned doing a battery stat wipe in CWM after charging to 100% + 30 minutes.
I did this with a little twist of my own.
I allowed the battery to drain completely and tab to shut off. Plugged in the charger and immediately did a battery wipe in CWM. Allowed the battery to charge fully upto 100% + let it be on charger for additional time till the battery symbol in the notification bar no more showed charging sign. Again did the battery stat wipe in CWM and then rebooted the tab.
Since then i observe that the battery has been draining as it should be expected to. down to 72% after about 4+ hours of use. I will still be monitoring the battery discharge further for two or three more charge cycles. But I feel doing battery stat wipe in cwm 2 times at full drain and then again at full charge might have helped caliberate it properly.
Let me know if anyone else tries this and gets same or different observations.

Try installing this to measure your current usage over the life of the battery... (dont have a GTab and still considering). Since most likely this widget and the battery monitor are using the same API we will see if its a hardware sensor issue or a software issue...
http://www.appbrain.com/app/currentwidget/com.manor.currentwidget
I suspect its in their battery monitor and not the sensor or API... if that is the case it should be easy to debug (if you have the source). Typically these issues are due to poor polling algorithms...
Im new to android so I am unfamiliar with profiling capabilities of the platform...(Still learning)

Perhaps this will be one of the 'little fixes' that will be present in the latest FW update when VS drops it tomorrow. I have the 100% unit BTW. A fix would be nice.

Reading this thread this morning it got me thinking about my gtab battery situation. When I first got the gtab, the battery stayed at 100% for hours, then the percentage dropped like a rock. Over time, the battery dropped in more regularly, although it drops in large numbers (like from 100% to 83%, then to 67%, and so on). I'm currently running TnT Lite 3.0.
This morning I charged the battery to 100%, and while plugged in (to the AC outlet), I reset the battery stats using cwm. The battery today has been steadily going down throughout the day as I would expect. In over 8 hours, I watched the battery go down steadily from 100% to 84%. So far, so good.

my exp
Tried draining once, just let it sit, didn't fix it.
Tried again but this time I kept the screen on and watched the voltage, shutdown was near 6.8 volts. Now the meter is accurate. YMMV...

@it'sDon - it wasn't fixed in the update.
I was in the same boat as most of you. Took a very long time to go down from 100% and then zonked out completely at ~10-15%. It's now been charging for a few hours and it's been sitting at 100% for quite a while but the light is still red (so it's still charging) which means it will probably happen again looks like it's charging to some value over 100% and when it discharges, knocks out while the meter is still reading as having juice. Roebeet is 100% on the money.
I am going to try the CWM battery value reset some of you mentioned to see if it does something once my light is green, then I won't charge it and watch it like a hawk once it hits 20% to see if it shuts down at 10-15% or a value less than 3% which is acceptable I think.

I never had a problem on my stock(ish) g-tablet. That is until I installed the latest update.
I had to do a data wipe before any of the cosmetic TnT changes would show. After that the battery now seems stuck at 100%. This wasn't that way before, so I will try draining the battery, and see what happens.
Since I found that this was tied to my latest update, I think that I should call CS and complain.

My battery drain didn't make a difference, either. Still haven't pinned down a fix that works.
At least those of you with 94% max have a general idea when your battery will die. With us "100% forever" ones, we have no clue.

Actually, I may not have a problem after all. I have had my tablet on for about two hours. It is now showing the battery at 86%.

[Q] Weird battery issue

This may sound weird but I'm having an issue with my battery reading 100% for too long. I was on CM7 RC2 and then RC4 and the battery percent would drop evenly. I leave the phone on over night because I'm on call 24/7 at work and in the morning the battery would read around 93% with RC2 or RC4.
I went back to the stock rom last night because the navigation on those two RC's is a bit messed up and I noticed that my phone in the morning was still reading 100% battery.
The problem with this is, I know it's obviously not fully charged, but the green light still comes on right away when plugged in because I guess it thinks it's fully charged. Is there anyway to get an even battery drop with the stock rom?

Your battery stats are a little off, that's all. There are posts all over xda on how to recondition and recalibrate your battery. Just find a good guide and follow it, you'll be back to normal in no time.

darinmc said:
Your battery stats are a little off, that's all. There are posts all over xda on how to recondition and recalibrate your battery. Just find a good guide and follow it, you'll be back to normal in no time.
Click to expand...
Click to collapse
Thanks for the info! What I could find said to charge to full, delete battery stats and then run until the phone turned off by itself and then charge to full again. I'm currently doing that now so hopefully I'll noticed a difference.

I've read that there is a possibility letting it die completely damages the battery (something about crystals forming). I usually just run it to 1% just in case the above is true, but other than that you got it. I would have told you, but I'd just state steps, this way hopefully you got a little extra info from people with more knowledge than myself.

Bad Battery? Or just stats?

So this has happened twice now. I'm running on ARHD 4.1.0 w/ Bricked 1.0.
My battery will be running normally, normal drainage, etc., and then it'll just drop from 90 to 70% in less than an hour, and normally drain for another hour or so, and then at around 60% just die. I can't attach a screenshot since normal screenshot apps aren't working and the stock function keeps producing invalid images, otherwise I would, but it literally just looks like it got to 60% and instantly dropped to 0%, there's just a vertical line of missing percentage. I took my phone out of my pocket, expecting it to be around 40 or 50%, and it wouldn't turn on. When I hooked it up to the charger, it took a good 5 or more minutes to even respond to the power button. Do I have a bad battery or just incredibly out of whack battery stats? I have never had this problem with an android phone before, and I thought for sure one full charge overnight would fix it, but I guess not because it happened twice. Any suggestions?
Edit: I use an app called battery snap to monitor the battery level and temperature with a widget, I checked a snapshot history while it was charging and for a few seconds it was at 0.002 volts. But then it jumped back up to 3.897 or something around there. That doesn't sound very good to me.

MusicMan374 said:
So this has happened twice now. I'm running on ARHD 4.1.0 w/ Bricked 1.0.
My battery will be running normally, normal drainage, etc., and then it'll just drop from 90 to 70% in less than an hour, and normally drain for another hour or so, and then at around 60% just die. I can't attach a screenshot since normal screenshot apps aren't working and the stock function keeps producing invalid images, otherwise I would, but it literally just looks like it got to 60% and instantly dropped to 0%, there's just a vertical line of missing percentage. I took my phone out of my pocket, expecting it to be around 40 or 50%, and it wouldn't turn on. When I hooked it up to the charger, it took a good 5 or more minutes to even respond to the power button. Do I have a bad battery or just incredibly out of whack battery stats? I have never had this problem with an android phone before, and I thought for sure one full charge overnight would fix it, but I guess not because it happened twice. Any suggestions?
Edit: I use an app called battery snap to monitor the battery level and temperature with a widget, I checked a snapshot history while it was charging and for a few seconds it was at 0.002 volts. But then it jumped back up to 3.897 or something around there. That doesn't sound very good to me.
Click to expand...
Click to collapse
I don't know much about this, but I don't think battery stats have anything to do while the phone is dead. Even if it does, the phone would at least respond after a minute or two, not 5..
My suggestion is that you can order an Anker battery which is kinda cheap ($15 I think) and try.
You won't loose anything
Edit: Try wiping battery stats, do a full charge, fully discharge and fully recharge again and see if it helps (In your case I don't think this will help, but huh, let's hope ;D)
Sent from my HTC Sensation Z710e

claudenegm said:
I don't know much about this, but I don't think battery stats have anything to do while the phone is dead. Even if it does, the phone would at least respond after a minute or two, not 5..
My suggestion is that you can order an Anker battery which is kinda cheap ($15 I think) and try.
You won't loose anything
Edit: Try wiping battery stats, do a full charge, fully discharge and fully recharge again and see if it helps (In your case I don't think this will help, but huh, let's hope ;D)
Sent from my HTC Sensation Z710e
Click to expand...
Click to collapse
Thanks, I'll try it. I flashed the new cm7, since I just got tired of sense woes. I read battery life on this was amazing, and I'm hoping it was just a bug with the kernel/rom I was using. Battery stats would've been wiped when I wiped for flashing this ROM, so I'll do a full battery cycle and cross my fingers. My only thought is that maybe, if the battery stats were screwed up enough, it thought it was at 50 or 60% but really it was more like 10%. I remember having issues after I flashed the custom kernel, where before I flashed I was at 70%, and when I rebooted I was at ~10%, and I was like what the hell? So it ended up dying on me, but then I turned it back on and it said 50% or something around there. And then it functioned as normal until it died again, for real that time. Hopefully it was the kernel causing the issue. I'll run a few tests with this and see. If it is the battery, I'll try t-mobile for a warranty replacement of the battery.

The battery measurements seem to be really quirky on this phone. When the phone is idle it seems to drain anything from 50ma to 400ma for no particular reason. You cant really rely on the % too closely

Yeah, I've found the percentages to be pretty inaccurate. Hardly an hour and a half on the battery and it's down to 84%. I did play a game for like 10 minutes and the screen has probably been on for 20 or so, so that's not incredibly unreasonable. I'm just waiting for that dropoff to 0%, if that happens again I'm thinking it's hardware, because I'm running an entirely different ROM and kernel right now.

So it just happened again, went from 42 to 14 after reboot, had to remove battery and reinsert to fix. But other people have reported this issue on cm7. So, I'm thinking maybe that it's an issue with android 2.3.5 or the kernel for it, since it's happened on both arhd 4.1 and cm7, both 2.3.5 roms. I'm going to try and flash faux's cm7 kernel over it and see if it fixes it. May or may not, might be a long shot but worth a shot, I'd rather not switch roms for a third time in the same day.

[Q] Random Shutdown Issues - Bad Battery?

Hey all,
I am currently running CM9 (bhundven's 7-29 herring build) on my Galaxy S 4G, and I am having some problems with random shutdown. This has only been happening for the past few days or so (EDIT: and I have been running CM9 for about three months with no issues). It seems that the phone works perfectly fine until the charge gets to about 60% starting from a full charge, and then the phone randomly shuts off. The phone will not start back up unless I have it plugged into the wall, and the results are a little unpredictable. The first time it happened, I turned it back on and it said the battery was at 1% and charging. Now, after clearing the battery stats, it reboots to 60% battery. It seems to work perfectly fine after that, and yesterday it went all the way down to about 12% before I started charging it again. It just happened again today, and when I turned it back on it said it was at about 60%.
My charging habits are pretty bad for Li-Ion batteries; I tend to let the charge drop all the way to about 10% or 5% before I plug it in and charge it all night, way past what is necessary to get to 100%.
The battery does look a tad swollen, but I might be exaggerating.
I just wanted to know if this is a bad battery with 100% certainty, or could it be a problem with the OS or internal parts, etc. I can easily buy another battery online, and I probably will.
EDIT: Also, I have had some overheating issues with this phone, and I can often smell electrical smoke in the charger port area behind the speaker, which is why I say it might be an internal parts issue.
Thanks everyone,
cpkelley94

You need a new battery. I was having the same issue lime 3 months ago; phone was dying at half charge the when it rebooted, battery would be dead. Then when I plugged it in, it would charge in 20 minutes and the repeat the cycle. Put the battery on a table to see if its still flat. If it rocks or spins excessively, its usually an indicator of a bad cell.

Mine JUST started doing the exact same thing last week. Battery is definitely swollen. I replaced it just this evening and I'm in the process of doing a full charge from 0->100 to see how things go. I'm 99.999% sure the battery was dead. Replace yours.

Sorry for the thread necro, but I wanted to thank the OP for asking this question and to the helpful replies. We just had a heat wave here and maybe coincidentally to that, I've been having random shutdown problems. Having looked at this thread and my battery, I can tell that I definitely need to replace that. So thanks, all!