I don't think this is the charge limiter. It should be switched off by this point, if not by setting enabled to 0 then definitely by setting the limit to 0.
The only thing I can think of is that the percentage is wrong. Here's the situation: the TWL chip is SUPPOSED to stop charging when it reaches a certain threshold automatically. My original one did this, as well other users have reported that theirs did this (albeit usually as a bug report
). Anywho, that is entirely expected behavior. The problem, first, was that not all Pandora's would stop charging as they were supposed to: some slight variance of the boards kept the detected charge rate from dropping below the expected threshold long enough to stop the charging, which resulted in more energy being dumped into the battery than it could safely store, slowly damaging it over time. The second problem was that, even those that did stop charging would not restart again until the battery was quite low, resulting in people waking up in the morning with 70-80% charge remaining; many a bug report was filed. The charge limiter fixes both problems.
Now, on the other hand, there's the bq chip. While the twl charges the battery, the bq keeps track of that charge and reports an estimated maximum and remaining amp hours. If it has miscalculated the maximum (and it's a learning chip, so this value can go up and down over time, depending on usage and the actual abilities of the battery) to be 5% higher than the actual maximum, then it could be that the battery is actually full, the twl is doing the thing it was designed to do and shutting off the charge, just that the bq has an improper measurement of the battery capacity now for some reason. I've been experimenting with how to get the bq chip to quickly recalibrate. I've cycled my battery more times in the last week than I have in the month before, but I think I'm finally onto something
When I've got the details worked out, I'll post a how-to on recalibrating the bq chip. I'm not certain why it would have become uncalibrated in the first place though. It's kinda weird, but since none of it happened before HF6 there's a good chance it has to do with the safety limits.