You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the tests of the solution we faced the issue with the Health Battery check incorrectly based on the SystemProfiler there is showing different informations, and based on the looks on the code I'm trying to understand why for the Health are not using the MaxCapacity value, but are using the AppleRawMaxCapacity / DesignCapacity * 100, which on my device showing 102%, when System Profiler as showing 100%, for other few devices are showing as well differences.
I'm currently using AppleRawMaxCapacity / DesignCapacity * 100 to calculate battery health because it reflects the raw reported maximum capacity from the battery’s firmware. This gives a more accurate picture of the battery’s physical condition, especially on newer or recently calibrated devices, where it’s not uncommon to temporarily see values above 100%.
That said, I completely understand the need for consistency with what the system reports. As a compromise, we can easily cap the health percentage at 100% in the UI, while still using the raw values under the hood to retain accuracy.
Activity
almenscorner commentedon Jun 19, 2025
I'm currently using AppleRawMaxCapacity / DesignCapacity * 100 to calculate battery health because it reflects the raw reported maximum capacity from the battery’s firmware. This gives a more accurate picture of the battery’s physical condition, especially on newer or recently calibrated devices, where it’s not uncommon to temporarily see values above 100%.
That said, I completely understand the need for consistency with what the system reports. As a compromise, we can easily cap the health percentage at 100% in the UI, while still using the raw values under the hood to retain accuracy.