I've recently tried a cheap high capacity battery, over twice the capacity of the original one (but, of course, twice as fat and heavy). While the battery charges to it's 4.2V and discharges down to about 3.5V properly (tested manually, with the multimeter), the phone keeps reporting the battery as 1230mAh, tracking it accordingly. This causes the phone to go from 100% down to 15% at about the speed it would with the original battery and then remain at 15% for a full day. Similarly, charging the battery makes it go to 100% twice as fast as it should, yet the battery keeps charging after it reaches those virtual 100%, up to the proper 4.2V, with the proper current (NOT trickle charging).
I've already tried the obvious (fully charge, delete the stats file, fully use the charge, then full recharge again), it didn't really help, it only distributed the estimation a tiny little bit.
Any solutions ? Is there a proper way to manually override the battery capacity either with or without recalibration ?
27 views and not a single freaking answer ? How familiar
bump.
InfX said:
27 views and not a single freaking answer ? How familiar
bump.
Click to expand...
Click to collapse
Maybee battery curent widget... inside you have settings/monitoring/battery capacity...
But with that attitude I'm almoust sorry to help you
I am familiar with that widget, overriding the capacity setting there only changes the displayed capacity in the app, it doesn't affect the estimations at all. Sorry, i should have mentioned trying this.
PS: What attitude ? Bumping a thread that got buried on a third page after just 2 days, without a single answer, while most other threads that bury it could be answered using a search button ?! I can assure you, i may do it once again after a week+ or something and then i'll just forget about it, you can check my others threads And yea, they usually remain either unanswered, or self-answered after all (rare, but if it happens, i post my findings in the thread)
PPS: If you consider it such a "bad attitude" just don't bother helping. Thanks.
Battery reading is indeed not 100% perfect. But what ever change we would make. It is not gonna give you extra battery life. Until some one fix it there is no way to read it 100% correct. So that is the whole story.
jan-willem3 said:
Battery reading is indeed not 100% perfect. But what ever change we would make. It is not gonna give you extra battery life. Until some one fix it there is no way to read it 100% correct. So that is the whole story.
Click to expand...
Click to collapse
Well, i don't bet on it to be 100% correct, but it should be something relatively close to the reality, while in case of this particular battery it's nowhere near that.
It assumes 1230mAh, calibrated or not, and i am 100% sure it takes this value from somewhere. In any case, it should be possible to patch, the question is where/how. Since i am not exactly an Android/Linux guru, the only things i did to find it out are searching this forum and doing simple google searches, finding nothing beyond the usual calibration thing. I though maybe someone may know something, that's why i posted the thread. I guess i was wrong about it.
PS: I guess i'll either abandon this, or start my own research, beginning at the source code of the ROM/kernel i use
InfX said:
I've recently tried a cheap high capacity battery, over twice the capacity of the original one (but, of course, twice as fat and heavy). While the battery charges to it's 4.2V and discharges down to about 3.5V properly (tested manually, with the multimeter), the phone keeps reporting the battery as 1230mAh, tracking it accordingly. This causes the phone to go from 100% down to 15% at about the speed it would with the original battery and then remain at 15% for a full day. Similarly, charging the battery makes it go to 100% twice as fast as it should, yet the battery keeps charging after it reaches those virtual 100%, up to the proper 4.2V, with the proper current (NOT trickle charging).
I've already tried the obvious (fully charge, delete the stats file, fully use the charge, then full recharge again), it didn't really help, it only distributed the estimation a tiny little bit.
Any solutions ? Is there a proper way to manually override the battery capacity either with or without recalibration ?
Click to expand...
Click to collapse
i think you just need a rom/kernel that support extended batteries.
Sent from my HTC HD2 using XDA Premium App
j4n87 said:
i think you just need a rom/kernel that support extended batteries.
Sent from my HTC HD2 using XDA Premium App
Click to expand...
Click to collapse
Tytung R10 does. All those kernels only support "official HTC extended battery" though, and i have yet to find out what does it really mean (read - what's the technical difference between the official and unofficial one). Note that the battery is charged/discharged properly, its just the stats/percentage remaining that go haywire.
mhh, just made some researches...
Stumbled over these threads:
Crazy, that there is a different behaviour if you have an orig. HTC or not...
http://forum.xda-developers.com/showthread.php?t=756513
http://forum.xda-developers.com/showthread.php?t=948181
Also read somewhere, that you really need to charge your phone to fully 100%, so that current widget shows 0ma...and then let the phone a few more hours at the charger, (DONT remove your charger) then manually delete the batterstats file in /data/system, turn off the device, REMOVE the charger, then boot the device.
Good luck
For those really interested to know what the technical difference between those bats... its the thermistor values range. Thats it.
The different batteries are identified by that thermistor value, all the batteries parameters are in the "ds2746_param_config.h", the table i am interested in modifying is the FL_25, one that defines the full battery capacity.
Sadly, this, most probably, requires a kernel recompilation, something i can't do, not without setting up all the required environment first Or, maybe it's possible to just patch the kernel image with hexeditor, i'll probably take a look.
PS: Thanks for everyone for trying to help.
EDIT: patching zImage would be harder than just recompiling it
not saying this is the right answer or that you haven't already tried but it didn't half help me out as i was only getting 8 hours before i used it, and i only got around 15 hours when i used to use wm, also left a print screen of what i get after i use the features in THIS page...
Sent from my HTC HD2 using XDA Premium App
Related
I remember that someboy have already said it, but i've not found on the forum a solution.
disconnecting the charger means an immediately pass from 100% to 99%.
why this bug?
how can we solve it?
thanks
Hmmm i think you must connect charger
Sent from my GT-I9000 using Tapatalk
ilbulgaro89 said:
I remember that someboy have already said it, but i've not found on the forum a solution.
disconnecting the charger means an immediately pass from 100% to 99%.
Click to expand...
Click to collapse
This seems to be a much more common behaviour since 2.2.1 ROMs came out.
However a pattern is still to be extracted from this: for example, when i charge the phone while powered off, and then boot it, once boot is completed i was able to see 100% for 1-2 minutes even after finally unplugging the charger.
why this bug?
Click to expand...
Click to collapse
One guess is that Samsung changed "the mathematics of charging" the phone, at least while charging with phone on, and may have done something wrong with displayed charging levels, but not necessarily with battery life itself.
Another guess is that your "2.2-calibrated" battery is somehow different/seen differently from a proper "2.2.1-calibrated" battery. Could be a matter of recalibration, or a combination with the previous point.
how can we solve it?
Click to expand...
Click to collapse
At the moment is unknown.
This issue, and many others related to battery, it's currently being analyzed much more deeply in this thread.
For example, a user has just found out that 3rd party applications like Juice Plotter properly recognise 100% level even after unplugging the charger. This is interesting.
So it's still a work in progress.
It's just displaying it different. Battery meters are not accurate, that's just the way it is.
If the charger really kept your battery at 100% while it was on the charger then your battery would wear out very quickly. In reality it allows it to drop to around 90% after hitting 100%. The battery meter just stays at 100% for a bit on most phones so clueless users don't think something is wrong and wear their battery down by repeatedly forcing it to 100%.
Stop worrying over little 1 or 2% differences in battery readings, they are nowhere near accurate enough to judge such small differences.
It is interesting though, that this problem doesn't occur to me. I'm on JPY based Darky's rom v7, and the battery is reported as 100% for I don't know how long, after plugging in. I could confirm exactly how long but atm I'm testing to see how many days I can push out of the battery
Also, it doesn't seem like a problem to me. I think that maybe Samsung altered the algorithm for calculating battery level, because, pure technicly, a battery cannot house 100% while not plugged in.
Sent from my GT-I9000 using XDA App
Well they did change how they show the battery status in 2.2.1
You still has same capacity.
Think its better it show this way then 100% for 20 minutes before it moved to 99%.
**Using my own JPX kernel, z4mod, 345MB Ram and ext2 filesystem**
I came across this article recently
http://www.androidpolice.com/2010/1...bump-charging-and-inconsistent-battery-drain/
this explains things well, check it out
ilbulgaro89 said:
I remember that someboy have already said it, but i've not found on the forum a solution.
disconnecting the charger means an immediately pass from 100% to 99%.
why this bug?
how can we solve it?
thanks
Click to expand...
Click to collapse
I'm sure this is a ROM specific issue. ON JPX Rom (I think), the charge used to reduce from 100% to 97% instantaneously after removing the charger. This however, was resolved after I flashed to the newer JPY firmware.
Apologies first -- I don't have the answer to the title of the thread. Rather, I'm posting this thread to (hopefully) get to the bottom of this whole matter, because there is just way, way too much floating around about this in way too many threads.
So, this is a request to the smarties out there, devs, engineers, et. al., to explain the precise, actual meaning and mechanism of "bat stats" on the Epic (and perhaps Android in general?).
So please, if you don't know with certainty about something related to this, don't post what you've heard, speculate, (informed) guess, etc. Let's keep this discussion to unquestionably known facts.
Here's what I do know as fact: Wiping Bat Stats in CWM does nothing more than delete a file in the /system filesystem (I don't remember the file atm, but someone else will surely speak up and fill in that detail). That's it. Nothing more.
This file is recreated and data written to it on subsequent boot.
That's all I know.
What I'd like to know, to complete the picture, is what is in this file, what this data means, how it's used by the device in managing the battery. If anyone knows the specific, actual specs and mechanism/algorithm for this, please explain.
After that, we can figure out, once and for all, what "calibrating" the battery means, and how best to do it. Further, it may be then as simple as keeping a copy of one's batstat file on their SD card, and simply putting it back after any reflash, obviating the need to go through some painful "calibration" procedure.
http://en.wikipedia.org/wiki/Lithium_ion_battery
There's no reason to "calibrate" a lithium battery. End of story.
mrzood said:
http://en.wikipedia.org/wiki/Lithium_ion_battery
Click to expand...
Click to collapse
And that was helpful, and relevant, how?
This thread is not about LiION battery technology; it's about the Bat Stats functionality of the Epic 4G, the technical details of it, and how it applies to battery "calibration".
The underlying battery technology could be NiMH, and the questions would be the same.
What he linked is correct. You asked about battery stats and calibration. There is no need to, " Calibrate" a LION. However, I am interested in the battery stats. I use three different batteries with my phone and get different usages with each.
dwallersv said:
And that was helpful, and relevant, how?
This thread is not about LiION battery technology; it's about the Bat Stats functionality of the Epic 4G, the technical details of it, and how it applies to battery "calibration".
The underlying battery technology could be NiMH, and the questions would be the same.
Click to expand...
Click to collapse
So calibration is a placebo? Apple suggests it just to appease the idiots?
mrzood said:
http://en.wikipedia.org/wiki/Lithium_ion_battery
There's no reason to "calibrate" a lithium battery. End of story.
Click to expand...
Click to collapse
What this article mentions in one place is about "conditioning" the battery which is different. LiOn batteries should fully discharge and recharge with no "memory effect". In other words, you can run them half way down and recharge, or 99% of the way down and recharge and the battery should charge to the same total power.
However, what the original poster is talking about is the phone's battery "stats" - how it reads the battery to determine how much charge is left and reports "25% remaining" or whatever. That can absolutely be changed, because I have seen it get screwed up. For example, I flashed a ROM this fall (don't remember which at this point, and it probably does not matter) and I seemed to be getting amazing battery life. In the first 6 hours of having the phone on, it dropped only 25%, which was great for me. However, I went into a movie and when I came out about 2 hours later the phone was dead. The first 25% took 6 hours and the last 75% took approx 2 hours. THAT was a problem with the battery stats being screwed up.
However, exactly how that is determined is something I do not understand either...
You're actually calibrating the rom's battery stats and to the people splitting hairs about the term "calibrating battery" get over yourselves.
What I understand about this is you have a variable amount of amperage this is one value at full and another at empty (or as empty as android gets). It tracks this against runtine and I think a couple of other variables to determine overall capacity. Each Phone and battery are slightly different. So it is a file that tracks this and is used to determine % or capacity. The recalibration is usually done best by getting a full charge and wipeing battery stats then running it dead to set your full and empty points.
Not super technical but a decent quick answer I hope.
Sent from my DROIDX using XDA App
Right, theres lots of talk and confusion about the extended batteries.
Are they a complete scam?
Do they offer any improvements?
Are non-branded 1230mAh batteries as good as HTC OEM?
Im going to try and answer these questions, with empirical data
I have built a little rig that draws a constant current (112mA), its hooked up to my computer which times and logs the voltage over the battery.
It is set up to measure the "usable" charge, i.e i start discharging the battery at 4.2v and cut the load at 3.2v. 3.2v seems to be the voltage that the DHD considers it's battery to be empty.
This way I am measuring real world capacity rather than "ideal capacity" which is likely to be over estimated by the manufacturer.
Im testing a non OEM battery as we speak, however, if anyone has any extended capacity / non OEM batteries they would like testing, please let me know!
I'd rather not have to purchase batteries to test, so consider this a request for some test units. I will of course return them once the test is finished
J
Ok, the first test run has completed...
Non OEM Battery (Rated 1230mAh)
Initial voltage - 4260mv
End voltage - 3196mv
Current drain - 112mA
Time Elapsed - 35,125 sec
Total measured capacity - 1,093mAh
This is quite a way short of what the manufacturer claimed but it isn't a hugely surprising result, there was still charge left in the battery at the end of the test, but that charge could not be used by your handset, the phones firmware will shut down the phone well before it hits the minimum voltage of ~3.0v to prevent damage to the battery.
1,093mAh is the use you would see from this battery if it were in your phone.
Next up, official HTC battery.
Finally some real investigation to settle our (probably correct) suspicions
Very interesting, looking forward to the next results! Keep up the good work!
Very very interesting. Thanks for your work! Looking forward to further results!
Via the XDA app for the HTC Inspire
BatteryBoss v2! I like it
nice approach in testing the battery's capacity.
would like to see how a mugen would perform....
Are you sure about the 3.2V minimum. My phone shuts down at 3.5 (ish) and I can't seem to make it go lower. I've read that this might be kernel dependant, so can anyone with ARHD3.2 ROM (and the kernel that goes with it) confirm that they can get to 3.2V?
No im not sure, i did test some weeks ago and i seems to remember it being 3.2...
I did post a request in the Dev forum 2 days ago for some input on the matter but one of the mods decided to delete it.
Id be interested in any info/feedback anyone has on the matter.
When i plugged my phone in to charge last night it was at ~3.5v and ~10% showing remaining.
Excellent thread. Looking forward to more objective results.
JamesBarnes said:
I did post a request in the Dev forum 2 days ago for some input on the matter but one of the mods decided to delete it.
Click to expand...
Click to collapse
How stupid! Some of the mods here are power drunk.
Sent from my Desire HD using Tapatalk
Technically speaking DEV section is not the right place for that. Anyway I posted a tread here in GENERAL but noone replied with actual numbers.
I've been thinking won't be simpler to use the log from current widget to calculate the usable battery capacity? You have the drain/charge current and the time. Multiply those together and you have the capacity in mAh.
Sent from my Desire HD using XDA App
OK, using current widget you can calculate the actual battery capacity that the phone uses. The first results are a bit unaccurate, because I used an old log file that had 5 min intervals. I don't know if the current widget logs the max/min or mean value that is in the interval, but if it's the mean, then using the date from a full charge (1% - 100%) the usable capacity of my battery is 1083 mAh. The plausable value means the method works, it just needs a precise measurement.
Tonight I'll try to take a more accurate measurement, because as I said with 5 min intervals it could corrupt the actual values. Also the log I used was with a charge during which I used my phone, so there were a lot of fluctuations on the charge current during the fast charge.
P.S. Sorry for hijacking the thread but if it's possible for everyone to measure the capacity, it could be easier to evaluate the claims of the non-OEM batteries and actually see if they are any good.
After many different methods,hundreds of post by others. No method of full charge works for everyone. Well I decided to find out from the source, I contacted HTC,Google,Qualicom and Samsung. So first off there,s alot of misinformation about the battery stats bin. What really happens when you wipe battery stats??? NOTHING!!! That's right absolutely nothing. As quoted by all companies I,ve contacted heres the real deal.(batterystats.bin) is used to maintain, across reboot,low level data about your device and operations of apps during charging. Its only used to record things like this app held a wake time of ? Or your screen was using 40% recources for x amount of time. The stats bin actually has nothing at all to do with current or maximum level of charge allowable. So if you do wipe the battery stats bin what happens? The reporting that occurs in the stats bin might be allowed to report faster due to being cleaned. So then how do I get a full charge. Well sorry to say the's no real good way short of constant monitoring of your charge. lets look at what a L'ion battery really does. A lion battery is basically the same as nicad or lead acid.the difference is the amount of charge per cell. Most L'ion battery hold a Max charge of 4.2v +/- 50mV a cell. That being said leaving your battery charging over night not only wastes power but actually oxidizes the cells causing the battery to not fully charge. Our batteries will charge more effectively by not full charging to 100% every time. Getting a good battery monitor widget like the one by 3c is your best friend, when your at 0ma your pretty much done.. So to wrap this up and still give you proper info here we go!!! Screen time out and LCD density drain most of your battery. Using task managers to kill apps actually uses more battery because Android will re open apps as it chooses, there's no need to kill an app unless you know why your doing it android does a great job of resource management. Also remember any mods or tweaks you use might add extra strain on your battery. Multiple launchers,live wallpapers,not backing out of apps properly especially games. The main things to consider when your battery loses charge fast is, does my rom use more resources than stock, do I have to many active apps, do I not know how to properly exit applications. ALL THIS INFO IS FACT AND CAN BE VERIFIED BY A LITTLE RESEARCH ON YOUR PART!
Sent from my A500 using xda premium
Same thing HTC told me.
Sent from my A500 using xda premium
Yes, the wiping battery stats in recovery does NOTHING. Glad to see this reported. I've read much about this on Google+, with actual Google engineers and employees and developers debunking this. It only deletes your phones record of battery use (essentially), i.e. has absolutely zero effect on battery use, only record/reporting.
Sent from my PC36100 using xda premium
While this is correct an SBC kernel will allow your phone to get a higher charge and hold it there while undervolting will lessen the amount of power used therefore giving u better battery life.
While fully charging a battery will potentially lessen the life of a battery, it could take years for a noticeable effect... And in reality, how many people will continue having the evo once their contract is up, and the recent/upcoming lte releases become free with upgrade down the road...
Not to mention letting the phone discharge too low is not great for a battery either...
I concur on battery stats not needing to be wiped...
Nice post overall, and some really good information presented, thank you for sharing.
ca1ne said:
While fully charging a battery will potentially lessen the life of a battery, it could take years for a noticeable effect... And in reality, how many people will continue having the evo once their contract is up, and the recent/upcoming lte releases become free with upgrade down the road...
Not to mention letting the phone discharge too low is not great for a battery either...
I concur on battery stats not needing to be wiped...
Nice post overall, and some really good information presented, thank you for sharing.
Click to expand...
Click to collapse
Yeah I def wanna throw some props your way on the SBC kernels. Thanks a lot,it's been working great so far.
Sent from my A500 using xda premium
PyreKing said:
After many different methods,hundreds of post by others. No method of full charge works for everyone. Well I decided to find out from the source, I contacted HTC,Google,Qualicom and Samsung. So first off there,s alot of misinformation about the battery stats bin. What really happens when you wipe battery stats??? NOTHING!!! That's right absolutely nothing. As quoted by all companies I,ve contacted heres the real deal.(batterystats.bin) is used to maintain, across reboot,low level data about your device and operations of apps during charging. Its only used to record things like this app held a wake time of ? Or your screen was using 40% recources for x amount of time. The stats bin actually has nothing at all to do with current or maximum level of charge allowable. So if you do wipe the battery stats bin what happens? The reporting that occurs in the stats bin might be allowed to report faster due to being cleaned. So then how do I get a full charge. Well sorry to say the's no real good way short of constant monitoring of your charge. lets look at what a L'ion battery really does. A lion battery is basically the same as nicad or lead acid.the difference is the amount of charge per cell. Most L'ion battery hold a Max charge of 4.2v +/- 50mV a cell. That being said leaving your battery charging over night not only wastes power but actually oxidizes the cells causing the battery to not fully charge. Our batteries will charge more effectively by not full charging to 100% every time. Getting a good battery monitor widget like the one by 3c is your best friend, when your at 0ma your pretty much done.. So to wrap this up and still give you proper info here we go!!! Screen time out and LCD density drain most of your battery. Using task managers to kill apps actually uses more battery because Android will re open apps as it chooses, there's no need to kill an app unless you know why your doing it android does a great job of resource management. Also remember any mods or tweaks you use might add extra strain on your battery. Multiple launchers,live wallpapers,not backing out of apps properly especially games. The main things to consider when your battery loses charge fast is, does my rom use more resources than stock, do I have to many active apps, do I not know how to properly exit applications. ALL THIS INFO IS FACT AND CAN BE VERIFIED BY A LITTLE RESEARCH ON YOUR PART!
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Thanks for the information! I wonder how this will be received by those who've been doing this battery stats wiping religiously when flashing ROMs. Interesting to get some information from the SOURCE!
Also, I've always used the sbc kernels, and have had no battery issues (and I let the phone charge all night, every night). I'm sure it'll mess up my battery eventually, but I got my current one free anyway from Sprint (extended one), so oh well. No loss!
PyreKing said:
After many different methods,hundreds of post by others. No method of full charge works for everyone. Well I decided to find out from the source, I contacted HTC,Google,Qualicom and Samsung. So first off there,s alot of misinformation about the battery stats bin. What really happens when you wipe battery stats??? NOTHING!!! That's right absolutely nothing. As quoted by all companies I,ve contacted heres the real deal.(batterystats.bin) is used to maintain, across reboot,low level data about your device and operations of apps during charging. Its only used to record things like this app held a wake time of ? Or your screen was using 40% recources for x amount of time. The stats bin actually has nothing at all to do with current or maximum level of charge allowable. So if you do wipe the battery stats bin what happens? The reporting that occurs in the stats bin might be allowed to report faster due to being cleaned. So then how do I get a full charge. Well sorry to say the's no real good way short of constant monitoring of your charge. lets look at what a L'ion battery really does. A lion battery is basically the same as nicad or lead acid.the difference is the amount of charge per cell. Most L'ion battery hold a Max charge of 4.2v +/- 50mV a cell. That being said leaving your battery charging over night not only wastes power but actually oxidizes the cells causing the battery to not fully charge. Our batteries will charge more effectively by not full charging to 100% every time. Getting a good battery monitor widget like the one by 3c is your best friend, when your at 0ma your pretty much done.. So to wrap this up and still give you proper info here we go!!! Screen time out and LCD density drain most of your battery. Using task managers to kill apps actually uses more battery because Android will re open apps as it chooses, there's no need to kill an app unless you know why your doing it android does a great job of resource management. Also remember any mods or tweaks you use might add extra strain on your battery. Multiple launchers,live wallpapers,not backing out of apps properly especially games. The main things to consider when your battery loses charge fast is, does my rom use more resources than stock, do I have to many active apps, do I not know how to properly exit applications. ALL THIS INFO IS FACT AND CAN BE VERIFIED BY A LITTLE RESEARCH ON YOUR PART!
Sent from my A500 using xda premium
Click to expand...
Click to collapse
This is good info - I can confirm that. Sometimes we advise our customers to wipe out the stats, because this differs from phone to phone. Dell Streak 5 for example, has the .bin file hardcoded somehow to the OEM battery capacity, so the charge indication is not shown properly if the battery is bigger than the OEM (if I'm not mistake). But in general, yes, wiping the .bin file won't increase battery life.
There is a good article on this from Lifehacker on Task Killers. Google "Android Task Killers Explained: What They Do and Why You Shouldn't Use Them"
When changing roms, is it advisable to wipe the battery stats?
I have been heavily using my N7, unplugged, for the past 3 hours and the battery status is still at 100%. I have rebooted 3x to see if the battery status system would reset, but to no avail.
Earlier today my N7 gave me the 14% low charge warning and then jumped to 0% and triggered automatic shutdown during the 30 second walk to get to the charger.
SpareParts is currently showing my battery voltage as 3 mV ... which certainly can't be correct.
It seems to me that my battery is in need of recalibration. I tried searching the issue, but the signal-to-noise is really low due to the previous fad of deleting batterystats.bin (despite it having zero effect).
Is there any way to force an actual recalibration? I also recognize it is within the realm of possibility that my device has a hardware failure; however, I thought I would check for simple remedies first.
Thanks.
If you have root access go onto the Google play store and look up battery calibration...it is the first app
Sent from my Nexus 7 using XDA Premium HD app
Thanks for your reply.
That app is the Android equivalent of a placebo. If you check the store, the description clearly states, "This program does it by removing the batterystats.bin system file."
Unfortunately, that file has nothing to do with battery calibration. That also means that the CWM "wipe battery stats" function does nothing for calibration either.
Da faq then how do u calibrate the battery?
Sent from my Nexus 7 using XDA Premium HD app
Right, this goes back to the low signal to noise ratio. Every FAQ about battery calibration that I have found discusses removing batterystats.bin (either manually or with an app).
As I said before, that has nothing to do with battery calibration.
Therefore, I decided to ask here to see if anyone knows how to *actually* recalibrate the battery.
I had the same issue. Battery stuck at the critial battery " ! " sign the day after I rooted (just FYI, using wugfresh toolkit), and before flashing anything new. So that was pretty weird. I thought it was some kind of hardware failure too, and was about to prise open the back to check the battery. Because even charging didn't help. It said "charging", but was stuck at 0% for ages. I gave it one last shot and this is what I did -
1) used an app to remove the batterystats.bin file (It probably didn't calibrate the battery like you said. Maybe it doesn't improve performance, and this step may be completely useless, but I'm just laying it out how I did it)
2) I turned off the device and charged it from the PC (someone who had a similar issue said he tried this and it worked for him. I don't know if there's any technical basis to it - but I'm no dev and so I thought I'd give it a shot)
3) It charged on the PC for a few hours (device was off throughout). Finally I disconnected and restarted, and it was fine again. Fully charged, and draining as normal.
So that's how it worked for me. Now the funny thing is I flashed a new ROM today (codefirex SR6), and soon after I rebooted I got the same critical battery " ! " warning. And just as I was thinking "oh no, not again" it switched back to 91% which was where I was before flashing the new ROM. I played around with it for a bit, then went back to recovery to flash another kernel. On reboot - back to critical battery warning. This time it didnt switch back to 90% even after a few minutes.
So I am now repeating the 3 steps above and seeing if it works.
Also, after all this, I feel on my device atleast, it so far doesnt lool like a hardware fault (because I fixed it the first time without having to touch the battery or its connections, because I saw the icon change from " ! " to the normal state of 90% battery the first time I flashed codefirex)
It looks like a software bug. But that's just me speculating.The technical aspects are beyond me, and I am going purely by what I saw.
I'll be watching this space carefully!! I really want to know how others have fixed this problem, and/or if it's a widespread issue.
Cheers
Update: So I switched it back on after about 20 minutes - and no change. Still showing battery at charging, 0%
Another interesting thing - I BetterBatteryStats is not reading anything. I set a custome reference to see what's happening, but it shows 0 seconds, no stats etc etc.. even after I refreshed and tried. So it's not able to read whatever it reads to generate those stats.
I've powered down again, and am leaving it to charge for longer. Maybe a couple of hours. So that my 90% battery should definitelt be fully charged by then.
At the moment I don't want to create a new post for this issue, so I'll update with my findings later.
This tirade isn't directed at anyone on this thread, I'm just generally dismayed that this snake oil still perpetuates despite clear and convincing verification that it does nothing...
I can't believe that people still believe in the snake oil that these apps peddle. Battery calibration apps are 100% worthless. You cannot calibrate your battery by manipulating batterystats.bin, and any dev that tells you otherwise is simply ignorant of how Android operates. The file contains no information whatsoever pertaining to battery charge indication. You'd achieve the same results by rubbing a baked potato over your device as you would using a calibration app.
This myth was debunked officially a full year ago by Google's Android team. .
The one and only way an end user can ‘”calibrate” the battery's internal fuel gauge would be to FPO a full charge/discharge cycle on the battery. This should not be done frequently, as it negatively affects the longevity of the battery, though.
Sent from my Nexus 7 using Tapatalk HD
Your rant is extraneous, which you would have understood had you read the thread. If you happened to have read the thread and decided to rant regardless, then I'm perplexed why you believed that your rant would contribute to the discussion.
najaboy said:
This tirade isn't directed at anyone on this thread, I'm just generally dismayed that this snake oil still perpetuates despite clear and convincing verification that it does nothing...
I can't believe that people still believe in the snake oil that these apps peddle. Battery calibration apps are 100% worthless. You cannot calibrate your battery by manipulating batterystats.bin, and any dev that tells you otherwise is simply ignorant of how Android operates. The file contains no information whatsoever pertaining to battery charge indication. You'd achieve the same results by rubbing a baked potato over your device as you would using a calibration app.
This myth was debunked officially a full year ago by Google's Android team. .
The one and only way an end user can ‘”calibrate” the battery's internal fuel gauge would be to FPO a full charge/discharge cycle on the battery. This should not be done frequently, as it negatively affects the longevity of the battery, though.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Dang dude take your Xanax. But you are right that a full charge cycle is all the calibration that ever needs to be done. But the value of that to somehow correct the display is doubtful. On some devices it might be helpful, but the fuel gauge capabilities on android are pretty basic from what I have read.
Sent from my N7 using XDA Premium
Dirty AOKP 3.2 & m-kernel+ a33
ezas said:
But you are right that a full charge cycle is all the calibration that ever needs to be done.
Click to expand...
Click to collapse
I did that twice this weekend. Just now, my N7 jumped from 20% to 0% and shut itself down again. As a bonus, because it's now dying directly from ~20% I don't even get a low charge warning at all. I think I will explore the warranty replacement route for my device.
Too bad, because it's just a battery calibration issue.
Try rebooting into recovery, go to advanced menu and wipe battery stats, then reboot.
EDIT: NVM, I think we established wiping battery stats isn't re-calibrating.
Southrice said:
Try rebooting into recovery, go to advanced menu and wipe battery stats, then reboot.
EDIT: NVM, I think we established wiping battery stats isn't re-calibrating.
Click to expand...
Click to collapse
Haha, thanks anyway. It's amazing how this concept circulated in the online echo chamber and became "well established knowledge"... yet turned out to be nothing but a myth.
Between my searches and all the responses so far, I'm left to conclude there is no way to recalibrate the battery. Not even doing a full charge/discharge cycle helps (besides, if it's so automatic and behind the scenes, how would one even tell?)