On 11 Sep 2018, at 12:25, Liam Proven wrote:

On 10/09/18 16:24, Andrei Verovski wrote:

...

I have reconditioned Lenovo Thinkpad laptop battery with new high-capacity 18650 cells from Samsung. However, even after battery stats reset with Lenovo Power Management software, battery capacity and remaining time are being displayed incorrectly, data is based on old 2200 mAh cells, now new 3500 mAh ones.

What model of Thinkpad?

I never had this problem when I put a cheap 3rd party battery in my X200, but it was a fairly old model.

Its old ThinkPad Edge. I reconditioned battery with new Samsung 18650 cells with larger 3500 mAh capacity. Could throw away all that stuff but anyway its quite interesting. BTW, chmod as root chmod u+w /sys/class/power_supply/BAT0/capacity_full_design works only until restart, then permissions and value change to default. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 9/11/18 7:31 PM, Liam Proven wrote:

On 11/09/2018 11:36, Andrei Verovski wrote:

...

Its old ThinkPad Edge. Which model, though? Edge was a series, with multiple models.

I am wondering if your firmware is current.

ThinkPad Edge 11, firmware is current.

...

I reconditioned battery with new Samsung 18650 cells with larger 3500 mAh capacity. Could throw away all that stuff but anyway its quite interesting. If I understand correctly, you cracked open your battery and replaced the actual cells in it, rather than replacing the battery?

In that case, there's probably some kind of ID chip in the battery's circuitry, and it is correctly identifying it as the same unit as the old one.

Exactly, I opened old battery enclosure and soldered new 18650 high-capacity Samsung 3500 mAh cells (old were 2200 mAh). Thermal sensor left in place. Battery has chip with EEPROM, it could be altered but I don't have appropriate hardware. EEPROM holds wrong information, so I would like to alter values in /sys/class/power_supply/BAT0/... Unfortunately, they are not root-writeable, and even chattr doesn't work on them. # lsattr: Inappropriate ioctl for device While reading flags on I can throw away this old battery and buy new one for 33 Euro, yet I'm stubborn with hackwork solution for this really interesting puzzle. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 12/09/2018 à 12:37, Liam Proven a écrit :

I think this probably _is_ solvable in software somehow but it is far beyond my knowledge, I'm afraid.

as a non really programmer hacker, I would search the driver for some clue of how it knows the battery initial value. may be lspci gives a clue? or scan the display app? If I remember well, you can change the value at (or after) boot? if so it shouldn't be so difficult to have a boot script do the same?. The /sys value have to be written at some moment just my 2c :-( jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org