View Single Post
Old 01-05-2022, 12:41 PM   #10
j.p.s
Grand Sorcerer
j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.
 
Posts: 5,806
Karma: 103362673
Join Date: Apr 2011
Device: pb360
Quote:
Originally Posted by beninma View Post
Minus someone actually hacking/disassembling the software I'm somewhat skeptical the battery calibration routines actually do anything, though maybe they do.
I don't think calibration had much, if anything, to do with you problem, but battery calibration is a thing. Battery charging and reporting is (mostly) handled by the PMIC (power management integrated circuit) in the device and the protection chip in the battery. The PMIC maintains information used to calculate state of charge.

An example of a relatively benign miscalibration I have experienced on my Oasis 2 is that once after charging the OS thought the charge was 105% (which got displayed as 100%). I think that situation is relatively common and led to lots of reports of devices staying at 100% for a significant time, then dropping faster. When the battery in such a device is allowed to discharge to a few percent then a calibration is done and it does not internally register over 100% until it again drifts out of calibration. This also explains some of the times that a battery doesn't charge past 98%.
j.p.s is online now   Reply With Quote