Quote:
Originally Posted by rupor
|
Hmm, I find this strange..
I've played a bit (more like looked at) with embedded firmware for mp3 players (not android, so take it for what it's worth) and for each device that was supported we had a mapping of current voltage vs. expected battery life. Mapping that was done from data by volunteers running their player's battery empty time after time.
It was set at build, it wasn't something you'd calibrated yourself or reset but then again it was only supporting a dozen different devices at the time. Compared to the hundreds of cells, tablets, readers that run Android...
Not saying Miz Hackborn is full of it, obviously she is not, but surely there is a reason why the devs have routines polling the device for those stats. And for the OS to tell you it thinks you have about 3 hours left at your current usage, there must be a mapping of sort, somewhere. A reference table. That maybe could get corrupted.
It's not a question of calibrating the battery, it's the battery meter you'd be 'calibrating'.
I dunno, it just sort of makes no sense to me.
or
??