Battery health option missing on BigSur

Besides the fact that the Big Sur OSx is the worst I have ever encountered and is literally draining my laptop on every aspect possible, I made the choice to go for the upgrade. Don't ask me why.

It is a Macbook Pro Retina 13'' as well, early 2015 model. I have exactly the same issue for the battery health: i.e. not showing with 'Option' key in the status bar and also not showing in the 'Battery' section in my preferences. How did you fix this issue @Sredski?

Sredski wrote:

Hi, my battery seems to be draining very quickly so I went looking for the Battery Health option and it's not there. I can see battery options but not 'health'. I found loads of online tips but they all refer to the Health option....nada! Is it the model/ age of the Mac I have?

https://discussions.apple.com/content/attachment/bd619c96-eaf3-423d-86ff-d8f780863146

The Battery Health button appears in >SystemPreferences>Energy Saver/Battery on the newer macOS —

this feature is limited to Mac laptops with Thunderbolt 3 ports. That equates to all MacBook Pro models released since late 2016 and the Retina-capable MacBook Air models released since 2018.

What Mac do you have? The new M1 Macs do not have the option to select battery health management (basically, it's always on and you cannot turn it off). Edit: they don't have Power Nap, either, so I suspect you don't have an M1 Mac.

Sredski wrote:

Is it the model/ age of the Mac I have?

Its a Macbook pro 13"....not new.

?

>SystemPreferences>E̶n̶e̶r̶g̶y̶ ̶S̶a̶v̶e̶r/Battery on the newer macOS —

this feature is limited to Mac laptops with Thunderbolt 3 ports. That equates to all MacBook Pro models released since late 2016 and the Retina-capable MacBook Air models released since 2018.

I so agree with you about Big Sur. It's been draining my laptop, too. Suddenly it shuts down with 25% of battery still being available. No warnings either.

I cannot check my battery heath, I have no idea what is going on.

I am using MacAir 2017, 13''.

Has anyone managed to sort the battery health out?

I noticed the same issue on my Macbook Pro 13" from early 2015.

There's no option on System Preferences, but some info can be obtained by clicking on the Apple menu (upper left corner) while holding Option, then choosing System Information, Hardware -> Power.

I have the same issue with my Mac 2013 Retina and Big Sur with battery draining. I've pinned it down to Safari crashing in the background, as CrashReport constantly runs when Safari is running and when i completely close Safari it stops. It does the same with a different user logged in, so its something fundamental with Safari. I've no idea how to fix it. The indication Safari was the cause was Safari was giving the impression that my internet access was a bit slow.

This issue is bloody infuriating. My 2015 MacBook Air ran like a dream, without a single hiccup, until I upgraded to Big Sur (11.1). Now the fan runs at full tilt when I launch ANY app. The battery MAY last 2 hours when unplugged as compared with 6-8 hours pre-upgrade (2 weeks if idle). Apple's own browser is the biggest offender of both the battery drain and the non-stop fan (huh?!). I've spent countless hours scouring sites looking for causes and solutions to no avail. So now it's always plugged in and consequently runs hot and loud all the time. So freaking disappointing.

Sorry for the rant without suggestions...

Hi,

Exactly. This is my cause. Whenever safari is run this is logged every ~10s. What is CoreSimulator, and why is AppleTV relevant?

com.apple.message.domain: com.apple.crashreporter.writereport.crash

com.apple.message.signature: com.apple.CoreSimulator.CoreSimulatoService

com.apple.message.signature3: UNKNOWN

com.apple.message.result: NO

com.apple.message.signature2: com.apple.CoreSimulator.CoreSimulatorService ||| 681.17.2 (681.17.2)

com.apple.message.summarize: YES

SenderMachUUID: BFCF02ED-7765-32B2-A2DC-EBE106F2FBF8

Mar 12 07:19:35 MacBook-Pro com.apple.xpc.launchd[1] (com.apple.CoreSimulator.CoreSimulatorService[2321]): Service exited due to SIGABRT

Mar 12 07:19:35 MacBook-Pro com.apple.xpc.launchd[1] (com.apple.CoreSimulator.CoreSimulatorService): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

Mar 12 07:19:45 MacBook-Pro com.apple.xpc.launchd[1] (com.apple.CoreSimulator.CoreSimulatorService[2323]): Service exited due to SIGABRT

Mar 12 07:19:45 MacBook-Pro com.apple.xpc.launchd[1] (com.apple.CoreSimulator.CoreSimulatorService): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

Crashed Thread: 1 Dispatch queue: com.apple.CoreSimulator.SimDeviceSet.defaultCreatedDevicesQueue

Exception Type: EXC_CRASH (SIGABRT)

Exception Codes: 0x0000000000000000, 0x0000000000000000

Exception Note: EXC_CORPSE_NOTIFY

Application Specific Information:

*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Failed to get path for default_devices plist.'

terminating with uncaught exception of type NSException

abort() called

Application Specific Backtrace 1:

0 CoreFoundation 0x00007fff206056af __exceptionPreprocess + 242

1 libobjc.A.dylib 0x00007fff2033d3c9 objc_exception_throw + 48

2 CoreFoundation 0x00007fff2062e512 +[NSException raise:format:arguments:] + 88

3 Foundation 0x00007fff21427197 -[NSAssertionHandler handleFailureInFunction:file:lineNumber:description:] + 166

4 CoreSimulator 0x000000010db0c014 -[SimDeviceSet _onDefaultCreatedDevicesQueue_updateDefaultDevicesForDeveloperDir:] + 987

5 CoreSimulator 0x000000010db0bb46 -[SimDeviceSet _onDefaultCreatedDevicesQueue_updateDefaultDevicesAndPairingsForDeveloperDir:force:] + 160

6 libdispatch.dylib 0x00007fff202e75dd _dispatch_call_block_and_release + 12

7 libdispatch.dylib 0x00007fff202e87c7 _dispatch_client_callout + 8

8 libdispatch.dylib 0x00007fff202f68c1 _dispatch_lane_concurrent_drain + 1020

9 libdispatch.dylib 0x00007fff202ef165 _dispatch_lane_invoke + 529

10 libdispatch.dylib 0x00007fff202f7857 _dispatch_root_queue_drain + 326

11 libdispatch.dylib 0x00007fff202f7fb8 _dispatch_worker_thread2 + 92

12 libsystem_pthread.dylib 0x00007fff20490453 _pthread_wqthread + 244

13 libsystem_pthread.dylib 0x00007fff2048f467 start_wqthread + 15

Mar 12 07:19:03 MacBook-Pro CoreSimulatorService[2313] <Notice>: com.apple.CoreSimulator.CoreSimulatorService 681.17.2 starting.

Mar 12 07:19:03 MacBook-Pro CoreSimulatorService[2313] <Error>: Unknown arch (arm64) in /Applications/Xcode.app/Contents/Developer/Platforms/AppleTVOS.platform/Library/Developer/CoreSimulator/Profiles/DeviceTypes/Apple TV 4K.simdevicetype/Contents/Resources/profile.plist

Mar 12 07:19:03 MacBook-Pro CoreSimulatorService[2313] <Error>: Unknown arch (arm64) in /Applications/Xcode.app/Contents/Developer/Platforms/AppleTVOS.platform/Library/Developer/CoreSimulator/Profiles/DeviceTypes/Apple TV 4K.simdevicetype/Contents/Resources/profile.plist

Mar 12 07:19:03 MacBook-Pro CoreSimulatorService[2313] <Error>: Unknown arch (arm64) in /Applications/Xcode.app/Contents/Developer/Platforms/AppleTVOS.platform/Library/Developer/CoreSimulator/Profiles/DeviceTypes/Apple TV 4K (at 1080p).simdevicetype/Contents/Resources/profile.plist

Mar 12 07:19:03 MacBook-Pro CoreSimulatorService[2313] <Error>: Unknown arch (arm64) in /Applications/Xcode.app/Contents/Developer/Platforms/AppleTVOS.platform/Library/Developer/CoreSimulator/Profiles/DeviceTypes/Apple TV 4K (at 1080p).simdevicetype/Contents/Resources/profile.plist

Ok, fixed :-)

Wading through the diagnostic logs I figured it might be something to do with Xcode and its Developer interaction with Safari for the "Developer mode". So I ran Xcode for the first time in many months and it prompted me to update some components (i.e. finishing installs or compatibility updates). I then went back to Safari and now there are no CrashReporting CPU cycles and there are no more logs as I highlighted earlier every 10s. Also, my battery usage is now much more stable in the last 10+ mins rather than just ticking down. So cross fingers I got it back to "normal".

I've had similar issues with Xcode before, that updates fail if you don't open and run Xcode since the last upgrade. But I hadn't considered this time there would be such a close link between Safari and Xcode!

Hope this helps anyone.