Shows 94.7% when fully charged...

[Chris]

I've been reviewing the code. The only way that the maximum capacity should be set to the same as the designed capacity is if the full capacity is being reported as a negative number by the battery (like -1). So, I've added some debugging code and I'll need to post a debug version that'll log the exact data provided by the battery and then the data after processing/cleaning up.

[jimmyjake]

Hi again.
I started this thread and continue to have the same issue. Put this utility on a laptop I helped a friend purchase, and she's having similar problems. I finally uninstalled the latest version on mine with Revo Uninstaller, and installed version 3.5.1 again just to see what might happen. Much to my pleasure, everything is apparently working exactly as it should be, so I turned off the auto-update feature and will keep this one for a while. I'll also revert to this version on my friend's pc...

Hopefully, this is a fixable glitch.

Thanks.

[Chris]

Regarding automatic updating, if you decline an update, it won't prompt you again until the next version is released. If you disable auto-update, they won't get the notice when 3.5.3 or newer gets released. If you don't update, it won't keep prompting you over and over again. It's just a one-time notice.

Jimmy, I'd like to send you a debug version that you can use to log the detailed battery data from your laptop so I can use the numbers to run some tests and identify the logic error that's causing this. Please message me if you're interested.

[kwapster]

any progress on this chris? i have the same issue maybe you could send me the debug as well

[Chris]

I have a solution to this issue. I was able to replicate the issue using one my old spare batteries. The issue was that when a battery is full, it may report it's current capacity as the same as the Designed Capacity instead of the Full Capacity. In my case, the designed capacity was 86500, and the full capacity was 15000 (battery wear = 82%). When when the battery was fully charged, it was actually reporting 86500 mWh as it's current capacity instead of 15000 mWh.

A change I had made in the code was a check to make sure that the reported capacity was never higher than the batteries capacity level. So, when the battery would report 86500 as the current capacity, and that was higher than the full capacity value, it would report the designed capacity instead. That correction was causing the problem. I've removed that correction and the status popup now shows data the same way as in 3.5.1.

I'll be posting a beta version in the auto update system soon for people to test the correction (along with some other fixes).

[kwapster]

great!!!

[Chris]

The updated version is posted in the beta testing forum and is available via auto update if you have the beta check enabled.