[Q] Is there a way to override the battery capacity ?

[InfX]

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 ?

 

[InfX]

27 views and not a single freaking answer ? How familiar

bump.

 

[TheNT]

27 views and not a single freaking answer ? How familiar

bump.

Maybee battery curent widget... inside you have settings/monitoring/battery capacity...

But with that attitude I'm almoust sorry to help you

 

[InfX]

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.

 

[jan-willem3]

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.

 

[InfX]

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.

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

 

[j4n87]

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 ?

i think you just need a rom/kernel that support extended batteries.

Sent from my HTC HD2 using XDA Premium App

 

[InfX]

i think you just need a rom/kernel that support extended batteries.

Sent from my HTC HD2 using XDA Premium App

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.

 

[j4n87]

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

 

[InfX]

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

 

[LaneyEFC]

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