M1 MBA Battery health numbers vary from different sources

[citivolus]

That was one of the changes to bitwise that I made. Make sure you are using the jdb branch when you check out. It’s also possible that I made a mistake on pushing my changes to GitHub. If that’s the case I apologize—I’ll check when I get a chance.

just double-checked and I am using the jdb branch located at https://github.com/jamesdbailey/bitwise
and am still seeing the same problem. maybe can you double-check that this code is correct?

 

[jdb8167]

just double-checked and I am using the jdb branch located at https://github.com/jamesdbailey/bitwise
and am still seeing the same problem. maybe can you double-check that this code is correct?

Can you run bitwise --version (that’s supposed to be two dashes) and see that it reports bitwise v0.41.jdb

Edit: Damn. I need to get better at git and GitHub. You are correct, I forgot to push my local changes to GitHub and then I removed the repository and downloaded again losing my changes. I've re-added them (thanks TimeMachine) and the changes should be up on GitHub.

 

[citivolus]

Can you run bitwise --version (that’s supposed to be two dashes) and see that it reports bitwise v0.41.jdb

sh-3.2$ ./bitwise --version
bitwise v0.41.jdb

 

[citivolus]

when I run: echo 18446744073709551377 | ./bitwise > /tmp/amps

this just hangs...

 

[jdb8167]

when I run: echo 18446744073709551377 | ./bitwise > /tmp/amps

this just hangs...

From my edit:

Damn. I need to get better at git and GitHub. You are correct, I forgot to push my local changes to GitHub and then I removed the repository and downloaded again losing my changes. I've re-added them (thanks TimeMachine) and the changes should be up on GitHub.

Another Edit: You need to specify the output so echo 18446744073709551377 | ./bitwise -o d -w d

 

[citivolus]

got it working, thanks!

 

[jdb8167]

got it working, thanks!

It's an odd program. Pretty well written and easy to understand C but it doesn't seem to respect normal Unix style functionality with stdin and out. Anyway, glad you got it working and for finding my mistake. Thanks a lot. It would've been annoying to lose those changes.

 

[MacCheetah3]

Anyone understand the difference between System Report and the Third party app reports?

Here are some details.

This is definitely something I would use the values from coconutBattery for. The actual values for max capacity and design capacity are useful for figuring out what the battery is actually doing over time.

Actually, “Design Capacity" is the problem; it’s the only value that isn’t realtime or otherwise taken from the device’s battery. Instead, design capacity is exactly what it says, just what the manufacturer has targeted/expects of that specific battery model, revision. Therefore, it’s extremely unlikely your device’s battery actually started at that level (for good or bad). What makes the calculation worse, apparently, Apple and each third-party app have different sources for these “Design Capacities.” Ultimately, if you want to estimate battery health, consider age and calculate the difference of current cycles to the typical/average capable before reaching 80% (listed in the following document).

Batteries - Service and Recycling

Learn about battery service and recycling for Apple devices. All rechargeable batteries need to be serviced eventually.

www.apple.com

One more thing (about current charge percentage)...

Lost 6% battery overnight. Is this normal?

Here's the rub, the battery charge may have only dropped a percent or two because... Apple's 'smart' charging works in four ways: • (Capable of) Very fast charging up to 50% • (Capable of) Somewhat fast charging from 50% to 90% • Trickle charging at 90% and higher • Cycling charge at peak ***...

forums.macrumors.com

I set Aldente to charge to around 60%, and give the battery a bit of use now and again.

Good plan. 50% is optimum for unused cells but as close as you can get is better than leaving it sit unused at the extremes.