I am using macbook pro 2015 with Monterey version 12.1. Almost every time when I open the screen and login in the usage of cpu surges more then 200%. It's even stranger because mac isn't connected to any device! To fix it I turn off and on the bluetooth, which doesn't seem a good solution to me. Is there any better ways to fix it?
macOS 12.2.1 (released Feb 10, 2022) fixed some Bluetooth bugs, but it's not yet clear if it fixed this issue.
A quick recap for everyone:
This issue seems to be common to 2015 models. It looks like an OS bug that will require an update from Apple.
The following do not appear to work:
What to do now:
The best option for fixing that is for us all is still to submit a bug report to apple, and reference this thread. The more people that do this, the more likely it will be fixed.
https://www.apple.com/feedback/
(click "MacBook Pro" or "MacBook Air" under "Hardware").
Also, please make sure you include the version of macOS Monterey on all future posts! Otherwise it'll make future troubleshooting of this issue difficult.
This issue seems to be common to 2015 models. Re-installing the OS in-place is unlikely to fix this issue now that macOS uses a signed & sealed system volume.
Bluetooth configuration files are stored here:
/Library/Preferences/SystemConfiguration/com.apple.Bluetooth.plist
/Library/Preferences/com.apple.Bluetooth.plist
/Users/*/Library/Preferences/ByHost/com.apple.Bluetooth.*.plist
/Users/*/Library/Containers/com.apple.preferences.sharing.SharingBluetoothService
You could try deleting all of these to reset the Bluetooth settings, but I suspect it's an OS bug that will require an update from Apple.
To that end, the best option for fixing that is for us all to submit a bug report to apple, and reference this thread. The more people that do this, the more likely it will be fixed.
https://www.apple.com/feedback/
(click "MacBook Pro" or "MacBook Air" under "Hardware").
I want to add that I was able to use my Magic Trackpad with Bluetooth off on MacBook Pro. Turning BT on/off made it actually disconnect.
A week later - I'm no longer seeing bluetoothd peaking at 200%, but now I'm getting kernel_task go to 500% when connected to external display (https://discussions.apple.com/thread/251715169)
Very messy by Apple :(
shott85 wrote:
For me, the issue disappeared after I went into Bluetooth Preferences > Advanced and disabled the following two options:
…
That is interesting, shott85.
In fact, this seems to have a very logical connection, though the details are yet to be determined.
It may help to provide this information directly to Apple, via Apple’s Feedback: Product Feedback - Apple.
Apple doesn't want to help us. I've reported the bug to Apple for a long time, but I haven't received any feedback to date. The error still exists and nothing changes.
armensanoyan Said:
"bluetoothd high cpu usage: I am using macbook pro 2015 with Monterey version 12.1. Almost every time when I open the screen and login in the usage of cpu surges more then 200%. It's even stranger because mac isn't connected to any device! To fix it I turn off and on the bluetooth, which doesn't seem a good solution to me. Is there any better ways to fix it?"
-------
Reenable Bluetooth:
Disabling, and then enabling Bluetooth is a good idea of troubleshooting. So, start with that. If you have no success, then restart your Mac.
I have exactly the same issue, on a 2015 MacBook Pro (15") running macOS 12.1 Monterey. The fans go crazy, and bluetoothd goes wild and takes up all the CPU time.
This issue has happened multiple times. It did NOT happen on macOS 12.0.1. I have rebooted multiple times since installing macOS 12.1. The advanced Bluetooth reset options previously available by option-shift-clicking the Bluetooth menu appear to have been removed in Monterey.
I experience the same on my Early 2015 Macbook Pro 13" with macOS Monterey 12.1. After sleep, when I open it and log in, the bluetoothd tends to loads the CPU >200%. But not every time.
As suggested, toggling bluetooth off-on, or using `sudo pkill bluetoothd` helps temporarily.
Same issue here, I have a Macbook Air from Early 2015 and I am running macOS Monterey 12.1. Turning the bluetooth off and on is a temporary fix that works for me.
I didn't have any issue with the latest version of macOS Big Sur.
I have the same issue on a Mid-2015 MBP 15", MacOS 12.1
Opening the lid sends the process >2xx% CPU. The possible BT connections are Airdrop being active, and an iPhone and Watch in the area. Switching off BT in the Menu Bar resolves the immediate issue.
I have this issue too since updating to macOS 12.1. My machine is 13" MacBook Pro with Retina Display (Early 2015). Disabling bluetooth is just a temporary fix. I have recently reinstalling the OS, the issue persists.
One of the suggestions was to turn off bluetooth and then back on. While doing so, two old devices were listed, one of them said the connection was "rejected." Before turning off bluetooth, I removed both of those devices, effectively clearing the device list. Upon removing both, the CPU usage immediately dropped from 216% to 0% fixing the issue for me. I never turned off bluetooth and after 3 hours and one restart, the issue has not reappeared for me. Hope this helps someone!
As a temporary solution I can suggest to write a code, which will restart your bluetooth every time your screen is unlocked. I did it by hammerspoon. Here is the code
function printf(s,...) print(s:format(...)) end
wather = hs.caffeinate.watcher.new(function(eventType)
if eventType == hs.caffeinate.watcher.screensDidUnlock then
hs.execute("/usr/local/bin/blueutil -p 0 && sleep 1 && /usr/local/bin/blueutil -p 1")
end
end)
wather:start()
Of course it's not normal, and normal is what was happening all those years. With the exception of that Bluetooth update back in 2015 that caused system notifications sound as 200% volume white noise outbursts scaring us to death.
Same situation here. MBP 15" Mid-2015, Monterey 12.1. High CPU use from bluetoothd, which disappears if I turn bluetooth off. Seems to be when coming out of sleep from the lid being closed. I've reported it via the link given on page 1.
bluetoothd high cpu usage