Bluetooth crashes in MacOS Sonoma (M1 MacBook Pro)

I just upgraded to MacOS Sonoma. Now my bluetooth crashes every 15-45 minutes. Bluetooth turns off entirely (not just devices losing connection).


I already tried all the "bluetooth issues" troubleshooting I found online:

  • unpaired and repaired everything
  • deleted `/Library/Preferences/com.apple.bluetooth.plist`
  • reset bluetooth module with `sudo pkill bluetoothd`
  • restart computer
  • turn off wifi

Nothing has worked.


Now I notice a few Crash Reports in the Console app.


Note this does NOT represent all the times bluetooth has turned off (like I said, it probably every 15-45min), but I wonder if maybe it can provide some clues.


Any advice on how to proceed?


Attached is the full copy from the most recent crash report:


MacBook Pro 14″, macOS 14.0

Posted on Sep 29, 2023 7:29 AM

Reply
Question marked as Top-ranking reply

Posted on Dec 3, 2023 6:28 AM

Adding my journey to the log here:


Short Story: Wipe the entire drive and reinstall/downgrade to Mac OS 13 Ventura.


Long Story: Like many others here, my Bluetooth has been cutting in and out since upgrading to Sonoma. For me, it was happening several times a day. My Mac is an M1 Macbook Pro, and the connected Bluetooth devices are a Magic Trackpad, AirPods (seldom connected), and Keychron Q1 Pro. Here's a list of things I tried that haven't worked:


  • spoke with Apple support several times, including capturing and sending extensive logs to them - no dice
  • tried the Onyx approach listed in this thread - no dice
  • ran diagnostics - no issues detected
  • reinstall Mac OS 14 Sonoma without wiping entire drive - no dice
  • reinstall Mac OS 14 Sonoma with wiping entire drive - no dice
  • reinstall/downgrade to Mac OS 13 Ventura with wiping entire drive - success!


Bluetooth has been stable now for several days. At first it wanted to detect my keyboard a few times (more than was needed), but that's since disappeared. I'll be waiting at least several months before testing out Sonoma again on a different drive. Rough stuff.


Note - after running diagnostics I tried downgrading to Mac OS 13 Ventura, but wasn't possible without wiping the drive, as the installer refused to do so. That's when I worked through each of the above 'reinstall' steps.


Edit - I have also tried upgrading to the latest 14.x.x versions - no dice

184 replies

Nov 1, 2023 3:24 PM in response to watzlav

Apparently, the guys in Cupertino, who usually have such a big mouth when it comes to praising the superiority of their oh-so-great amazing products, didn't manage to fix the problem with the 14.1 update either.


2900 Euros for a computer, but a support and a culture to take care of bugs, like a cheap backyard workshop from the Far East. I can't even describe how Apple is getting on my nerves by now.

Nov 14, 2023 2:47 AM in response to watzlav

I just had a quick look through all the comments and no one really says on what Macs they are experiencing this, but to me it looks it is only affecting Macs with Apple Silicon. I have the issue on a MacStudio M1 Max.


I also have a mid 2015 MacBook Pro (Intel) running Ventura on Opencore Legacy, haven't gone over yet to Sonoma on it, as I am waiting for a few more supporting bugs to be fixed as Ventura is now running nice and stable. So I can't say if it this issue is on my Intel Mac also.


My daughter has a 2020 M1 MacBook Air with Sonoma, but she doesn't use any bluetooth devices on it, except playing music to Apple HomePods. Come to think of it, my MacStudio also plays music to HomePods with no issue, no disconnects, but Apple magic keyboard, mouse and my Beats Studio 3 headphones have the disconnect issue.

Nov 16, 2023 2:31 AM in response to Mann

If you are worried about a new OS, then you shouldn't install it. The same goes to newly minted device. There's no obligation. The Bluetooth module in your computer, is a physical module. It was good to work with the original OS that came with your computer. Your computer, the specific one, or the specific module maybe incapable to run a new OS, or simply malfunctioning. All kinds of physical parts can fail, in any kind of a device. This "problem" can be determined only at an authorised technical service, physically.


Well, you can check your Bluetooth devices in the Terminal, if they are there.

system_profiler SPBluetoothDataType


Nov 16, 2023 2:31 AM in response to chdsl

chdsl wrote:
It means either your Mac incapable to run the new macOS correctly, or your Mac has a hardware problem, or both. The Bluetooth module in your Mac is malfunctioning. Check it with an authorised technical service.

Apple disagrees, I’ve been on the phone with them and collected logs. While my specific cause of the problem is not the issue they are currently investigating, they do not think it is a hardware problem.

Nov 16, 2023 3:41 AM in response to chdsl

chdsl wrote:

If you are worried about a new OS, then you shouldn't install it. The same goes to newly minted device. There's no obligation. The Bluetooth module in your computer, is a physical module. It was good to work with the original OS that came with your computer. Your computer, the specific one, or the specific module maybe incapable to run a new OS, or simply malfunctioning. All kinds of physical parts can fail, in any kind of a device. This "problem" can be determined only at an authorised technical service, physically.

Well, you can check your Bluetooth devices in the Terminal, if they are there.
system_profiler SPBluetoothDataType

This is the most creative answer I've read so far regarding problems with Apple's software.


So you shouldn't use any other system than the one that came with the computer because that's the only way to guarantee correct functioning? Or what are you trying to say?


Isn't it always the guys in Cupertino who tell users how great the new operating system version is that they should install because


a) bugs are fixed

b) security vulnerabilities will be fixed

c) it will allow them to work even faster and better

?


And isn't it always the guys in Cupertino who tell you that the new operating system is compatible with this and that model? My MacStudio should be fully compatible - says Apple!


Couldn't it also be that the guys in Cupertino don't test their own computers and software properly before releasing it to users? Or how else can you explain the fact that Sonoma has so many problems? Is it all hardware problems? Or is it perhaps more the case that Apple itself doesn't see some problems during testing - precisely because they only occur sporadically?

Nov 16, 2023 4:06 AM in response to hotplug

@hotplug @mann @watzlav I agree with your comments. Also there is no way in **** that this is a hardware issue, then it would have been there in Ventura as well. Your device can't just magically have a hardware error the moment, a day or 2 after you have updated to a newer version of an OS. Take the iPhone, every issue on it has been OS.


Also, if you go check other posts, chdsl tells everyone it must be a hardware issue, that seems to be his standard answer, when everyone clearly states the issue appeared after an OS update. One example below.



So does chdsl also want to tell me that when MacOS Montery had the finder spring back issue, that took Apple six or seven updates to fix, was also a hardware issue. Common!!


This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Bluetooth crashes in MacOS Sonoma (M1 MacBook Pro)

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.