Macbook Pro 13" 2020 Battery Life

Uninstall Sophos by following the developer's instructions. Anti-virus apps, cleaning/optimizer apps, and third party security software are not needed on a Mac and usually causes more problems than they solve since they interfere with the normal operation of macOS.

At the end of the working day charge the battery to 100%, unplug it and then shut down the MacBook until tomorrow. Let the battery rest for the night.

Before shutting down the MacBook, go to System settings > login items > disable and delete all that's there. Also, System settings > Battery > Options > disable "Wake for network access"

By the way, your MacBook battery's original battery charge is 5,103 (mAh), so with your battery's full charge capacity being 4534, your battery health should be 89%. You can also check this with coconut battery app or through the Terminal.

in Terminal do,

ioreg -l -w0 | grep Capacity

In the result look for

“MaxCapacity” =

“DesignCapacity” =

Divide (“MaxCapacity”/“DesignCapacity”) x 100 and you'd know the health of your battery.

In my Intel 15" MBP,

it is (6746/7336) x 100 = 92%. Mine is a 2018 15" Intel MBP. It has 230 cycles. The MBP is actually 4 years and 10 months young.

ameloblastoma wrote:

I uninstalled Sophos and followed the steps above, and good news - battery did not drain overnight!

Bad news- it's draining very fast while I'm using it (1% every 3 minutes or so).

Battery seems healthy at 89%

https://discussions.apple.com/content/attachment/196a1d3b-adcb-413b-ac91-0d0627e39791

I also re-ran EtreCheck

<EtreCheck Report.log>

Thoughts on next steps?

I appreciate everyone's help!

Ok— thanks for corroborating you are on an Intel machine

I still see a <SophosUpdater.app > (?)

you have 2 backup cloud sync apps running—

I would try disabling those and compare your results— these third party sync software have been known to cause issue

IDriveforMac

OneDrive

On your Intel Mac—you can try resetting the  System Management Controller  Reset the SMC of your Mac

for power management.

The rule of thumb—if you are near the mains leave it plugged in, if you need the portability then run on the battery only—this is how you help optimize your battery charging and extend the working life of your battery by reducing the cycle count.

HWTech wrote:

For an Apple Silicon M-series Mac @chdsl's option is the only one which will work,

but may need to be parsed some more since it may include a lot of other junk.

re: SoC

less garbage to troll through here

ioreg -l| grep -e "CurrentCapacity" -e "MaxCapacity" -e "CycleCount" 

Perhaps there is an issue related to your main user account. You can compare the differences to figure it out. In my own personal experience battery drain tends to be associated with cloud file syncing services such as iCloud.

We cannot do a proper analysis while Sophos is installed because it is always interfering with the normal operation of macOS at a very low level.....that is what that type of apps does. That low level interference can cause all sorts of issues with macOS including performance issues which can make the laptop work harder than necessary which would drain the battery quicker than normal. This is why every regular forum contributor insists that these types of apps are completely uninstalled before proceeding any further with troubleshooting. We are after all just other regular users volunteering our time to assist people. We don't have the luxury of dealing with systems with these types of apps installed when they are unnecessary with such a high incidence of causing all sorts of problems.

Effective defenses against malware and other threats - Apple Community

chdsl wrote:

In my Intel 2018 MBP,

https://discussions.apple.com/content/attachment/44f9209c-a555-4678-9094-11f7ab8d3cdc

As you see, there's 4% mismatch with what the Terminal show and the what Apple shows at the top. In your Silicon Mac, it says that FCC is 100%, but whether it is so is anybody's guess.

No idea why Apple does this, but the command line values output are correct on the Intel Macs....the macOS GUI interface is wrong. Third party apps like Coconut Battery concur in that assessment.

And Apple broke the output results for "pmset" on the Apple Silicon Macs.....the 100% FCC is one of those broken parts. AFAIK, that 100% FCC never changes, but I haven't really looked to closely since that value has no meaning for me as I need the actual mAh value as it is more precise when trying to troubleshoot battery issues.

chdsl wrote:

“MaxCapacity” =

“DesignCapacity” =

Divide (“MaxCapacity”/“DesignCapacity”) x 100 and you'd know the health of your battery.

certainly much cleaner ways to distill this information...if it is in question(?)

 pmset  -g  rawbatt

02/25/2024 13:07:09

AC; Not Charging; 76%; Cap=6080: FCC=7925; Design=8790; Time=0:00; 0mA; Cycles=218/1000; Location=0;

Polled boot=02/23/2024 21:31:35; Full=02/25/2024 13:00:00; User visible=02/25/2024 13:07:00

Note— (MaxCapacity) FCC=7925 / Design=8790

.

Please post the complete report using the instructions in this article:

How to use the Add Text Feature When Posting... - Apple Community

Andy Espo wrote:

It's not clear from reading lots of forums which numbers I should be using on Apple Silicon to calculate the battery health number. We typically do health checks during the Managed refresh process for client's Macs, and I'm looking for battery health via terminal command from Recovery Mode.

Unfortunately Apple doesn't care about these low level utilities. The output for the "pmset" command is broken on the Apple Silicon M-series Macs and doesn't have the same useful information as the Intel Macs.

@leroydouglas provided a screenshot & list of the items within the output of the "ioreg" command you need to use. If you need to pull them from the large output even with the "grep" filters, you will need to use other command line utilities to parse the items from the results.

I am in the process of writing a script to do this to kind of mimic the output of the "pmset" command, but the information output by "ioreg" on the Apple Silicon Macs keeps changing and I haven't had an urgent need to complete it yet. Here is the basic steps, notice in my "grep" filter that I'm including the "=" and double quotes or you may sometimes get two items):

applesmartbattery="$(ioreg -w0 -r -n AppleSmartBattery)"


fcc="$(echo "$applesmartbattery" | grep -E '\"AppleRawMaxCapacity\" =')"

capacity="$(echo "$applesmartbattery" | grep -E '\"AppleRawCurrentCapacity\" =' )"

design_capacity="$(echo "$applesmartbattery" | grep -E '\"DesignCapacity\" =' )"

current_capacity="$(echo "$applesmartbattery" | grep -E '\"CurrentCapacity\" =' )"



The values here match up with those from Coconut Battery as far as I can tell.

chdsl wrote:

leroydouglas wrote:

certainly much cleaner ways to distill this information...if it is in question(?)

pmset -g rawbatt.

Thanks. 👌

There are many ways to get to the result. 👍

For an Intel Mac yes. For an Apple Silicon M-series Mac @chdsl's option is the only one which will work, but may need to be parsed some more since it may include a lot of other junk. I'm trying to write a script to monitor the battery information for Apple Silicon Macs and realized just how clumsy awkward the ioreg output is with them since the information output changes when charging & discharging the battery. I'm not entirely certain that information is completely accurate although it is hard to confirm since macOS itself doesn't display 100% accurate information in the GUI even on Intel Macs.

Will be looking forward for your script. I have a feeling that all these battery health checking apps are using the ioreg script and distilling just the needed info out of it and nicely showing in an eye-catching app. All that "junk" gives the info, some apps are asking people to pay stating that some of it is an "advanced view".

I believe those other apps are using it as well. I believe the values are matching what is displayed by Coconut Battery....I was using Coconut Battery as a bit of a guide to confirm I was using correct items. macOS either gets the information in a different manner, or macOS GUI displays it incorrectly....even the battery charge level on the menu bar is off by about 3% from the command line results & Coconut Battery....command line is more accurate in that case.

I've been working on the script for the last year. I just haven't had the time or need to finish it yet. My organization's Apple Silicon Macs have not yet had any batteries that have aged enough to need to be monitored for a pending failure, although I am going to need to finish it sometime soon. I am trying to mimic the output of the "pmset" command that @leroydouglas posted. My script is very crude for parsing & displaying the information because I only have a very basic understanding of the parsing commands & options.

Hi,

Trying to get clarity on the difference between ioreg Battery Report on Intel-based Macs vs Apple Silicon-based Macs.

It's not clear from reading lots of forums which numbers I should be using on Apple Silicon to calculate the battery health number. We typically do health checks during the Managed refresh process for client's Macs, and I'm looking for battery health via terminal command from within Recovery Mode (after wipe and reinstall, no user account present).

If I run ioreg -l -w0 | grep Capacity on an Intel Mac, I get Design Capacity and Max Capacity numbers I can easily use to calculate battery health.

If I run the same command on Apple Silicon Mac, I get CurrentCapacity, AppleRawCurrentCapacity, MaxCapacity and AppleRawMaxCapacity (among other data).

If I run pmset -g rawbatt, I get (on my M1 MBP):

Not Charging; 80%; Cap=80: FCC=100; Design=6075; Time=0:00; 0mA; Cycles=113/1000; Location=0; 

 Polled boot=02/19/2024 19:46:37; Full=02/29/2024 11:50:01; User visible=02/29/2

It's not clear from reading lots of forums which numbers I should be using on Apple Silicon to calculate the battery health number. We typically do health checks during the Managed refresh process for client's Macs, and I'm looking for battery health via terminal command from Recovery Mode.

Clarity would be greatly appreciated!

Thanks