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%.
thunderbolt will not charge past 20 percent. It has been rooted with various skyraider roms and has used stock or recommended kernels with each. Currently it is wiped and unrooted but I can root it again if that helps.
I have tried to do battery status wipes with no sucess and i have replaced batterys and purchaced the verizon extended battery and it got into the 40s for charging percentage. weird thing is that it can be charged up to the 40 percent on the extended battery and drain to almost nothing within 15 min to a half hr. Yet I can put this battery in another phone and it will last all day... very frusterating. when i plug it in it reads around 40mA to 20mA when its "fully charged" at 20 percent. It does go into the high 200s and low 300s when charging. It also reads 3.764 volts at 20 percent.
I feel like there is software that is telling the phone to stop recieving charge because it thinks its full!
Any help would be greatly appreciated!!!
Android version 2.34
Sense 2.1
Software number 2.11.605.5
Kernel Version 2.6.35.10.g00f8966 [email protected] #1
how long have you left the device plugged? Have you tried different chargers? Don't bother with battery stat wipes or other "calibration" non-sense. They've been proven false by a google engineer's own statments. Bring the battery to a full charge in another device and then see what the voltage reading is in your phone. If it is around 4.2, then it is indeed fully charged. Run the battery down and then charge it with your phone. Check the voltage and see if it makes it back to 4.2 volts. If it never makes it back to 4.2, you have a phone or a charger problem. Charger is easy to check, phone will need to be warrantied. All this is based on the battery being good from your original post.
I'm on CM10 8/31 and I've been noticing that my battery life has been really poor lately, so I wanted to find out what the problem was. I thought about draining my battery fully and then charging it again. Once I drained the battery, I charged it, and restarted the phone after the charging began. Once the phone booted, it reported a 50% or so charge. I'm wondering if my phone is stuck at reporting battery at half capacity, and that when it charges to 100%, it's actually 50%. Anything I can do?
EDIT: Also, I should note that the battery has sometimes spiked up/down by about 20% after a reboot (including today before the drain).
This phone has a fuel gauge chip, fully discharging and recharging will not calibrate it. False readings after reboot are common, you may even notice it will climb back up as it begins to accurately reflect level.
There are apps to let you know what is causing drain. BetterBatteryStats and CPUSpy are recommended a lot.
ALBGunner04 said:
I'm on CM10 8/31 and I've been noticing that my battery life has been really poor lately, so I wanted to find out what the problem was. I thought about draining my battery fully and then charging it again. Once I drained the battery, I charged it, and restarted the phone after the charging began. Once the phone booted, it reported a 50% or so charge. I'm wondering if my phone is stuck at reporting battery at half capacity, and that when it charges to 100%, it's actually 50%. Anything I can do?
EDIT: Also, I should note that the battery has sometimes spiked up/down by about 20% after a reboot (including today before the drain).
Click to expand...
Click to collapse
Entropy doesn't frequent our forum much anymore, but he left some nuggets of wisdom behind.
As you have probably seen, he mentioned several times that generally our fuel gage doesn't need much attention. It may get a little out of whack if you have heavy usage followed by reboot, but generally the error is short-lived and goes away quickly (within an hour or so).
But apparently sometimes the fuel gage gets really confused, and in that case you can reset it (to un-confuse it) by powering down and pulling battery for 20-30 seconds. It certainly can't hurt to try.. that's what you try for any computer that was acting weird. That was discussed by Entropy here:
http://forum.xda-developers.com/showthread.php?t=1209087&highlight=+gingerbread+fuel+gauge+
By the way, here is a link to the fuel gage chip (MAX17040) used in Infuse
http://datasheets.maximintegrated.com/en/ds/MAX17040-MAX17041.pdf
It has a heuristic model of the battery. The only input is the battery voltage. So it looks at time history of voltage and provides an output signal. Exactly what the output is I’m not sure. You’d think it would be an estimate of %. But according to the circuit diagram there is no inputs to the MAX17040 other than battery voltage.
And yet our phone also knows when it’s charging. And our Infuse phone also has a sensor that enables it to measure current while charging (but not to measure current while discharging). This according to the developer of Battery Monitor Widget:
http://forum.xda-developers.com/showthread.php?p=31295223&highlight=infuse#post31295223
Why the heck would we not use sensed charging current and charging status as an input to calculating our % battery (since the signal does not go to the Max17040)? Beats me, doesn't make sense. Maybe the output of he fuel gage chip goes to the integrated power chip MAX8998 which looks at these other inputs (charging status and charging current) and develops the % estimate... I’m not sure.
Trying to be a showoff, I decided to let my Blaze drain down to near-zero so I could get a screenshot of the battery stats page in CM. Unfortunately, it shut down when it hit "0" on the battery meter, and when I plugged it in to charge a few minutes later, it came up to the battery charge screen with the icon of the grey battery, and then shut off.
I can get it into clockworkmod and download mode while on AC power or plugged into my computer, but neither will charge it. Upon reboot while off AC or USB power, the Samsung logo flashes for less than a second and then shuts off. No CM boot animation whatsoever.
A voltmeter shows 3.65 volts on the battery, but I'm assuming the available amperage is extremely low and can't provide the required juice to boot it up completely. Any ideas would be appreciated.
boot into cm, backup and flash a different rom and see if it will charge
i had to do that with a droid x i bought off ebay, someone had flashed a version of miui that had a bug which caused it to think the battery was always full and wouldnt allow the phone to charge
namaui said:
A voltmeter shows 3.65 volts on the battery, but I'm assuming the available amperage is extremely low and can't provide the required juice to boot it up completely. Any ideas would be appreciated.
Click to expand...
Click to collapse
Amps is a measurement of current.
Voltage is a measure of the charge and 3.65 volts is still a good amount. The nominal voltage for the battery is likely to be 3.2v and you're nowhere near that. For example if it took about 3 hours to run the battery down from 4.2v (full charge) to 3.65v then you should be able to run the device for maybe a couple more hours before the battery is close to being drained.
[just a guess here]
The firmware does battery management. Shuts off the device when it thinks the battery is about drained and stops charging when it thinks the battery is at about full capacity. The software is probably out of sync with the physical state of the battery (calibration) and thinks the battery is at zero when it actually has plenty left. Or it has a bug. If you can't find an easy way to wipe/reset the calibration data then I'd go with the advice above and re-flash or flash something else.
Quick7135 said:
Amps is a measurement of current.
Voltage is a measure of the charge and 3.65 volts is still a good amount. The nominal voltage for the battery is likely to be 3.2v and you're nowhere near that. For example if it took about 3 hours to run the battery down from 4.2v (full charge) to 3.65v then you should be able to run the device for maybe a couple more hours before the battery is close to being drained.
[just a guess here]
The firmware does battery management. Shuts off the device when it thinks the battery is about drained and stops charging when it thinks the battery is at about full capacity. The software is probably out of sync with the physical state of the battery (calibration) and thinks the battery is at zero when it actually has plenty left. Or it has a bug. If you can't find an easy way to wipe/reset the calibration data then I'd go with the advice above and re-flash or flash something else.
Click to expand...
Click to collapse
Thanks for the quick response, I think your guess was pretty accurate. An hour ago I cleared the battery stats in CWM, and after a few more battery pulls and reboots at the Samsung logo I left it alone while plugged into the AC charger. Came back 45 minutes later to a warm handset with a black screen and after holding the power button down for a good 15-20 seconds I booted normally into CM with a 12 percent charge.
Because I was able to get into CWM and download mode just fine (and run off battery for a few minutes), I was starting to think I broke CM. Glad I didn't get punchy and reflash.
And yes, you're right about amps, I was implying amp-hours with the wrong term.