Bluetooth audio problems Catalina

d_fuser, I found that in settings for bluetooth they still have EnablePressuredExit set to True (allows to kill bluetooth audio when memory is under pressure). So setting is still there and might be your system under much bigger pressure and kernel kills it anyway. However I tried to take all possible memory and didn't get that problem anymore. Or maybe you have something else. Can you open Console.app application and search for string "bluetooth" right after loosing sound. Maybe we understand what happens for you.

d_fuser, XPC error - it means coreaudiod can't communicate with bluetoothaudiod (at least I think so :D ) and then removes all devices that are from bluetooth. Can you open Console app and leave it working and when happened, search for a line "bluetoothaudiod" then, to check what killed it or what happened with it at all?

This is the log output when audio drops out. (All within one second.) "MDR-1000X" are the bluetooth headphones.

kernel	memorystatus: killing_idle_process pid 5932 [bluetoothaudiod] jetsam_reason->osr_code: 9
bluetoothd	BTDClient XPC connection for process bluetoothaudiod (5932) is becoming invalidated
bluetoothd	Removing (<BTDClient: 0x7fd805746340>) for process bluetoothaudiod (5932)
coreaudiod	XPC Error remove all devices
coreaudiod	Remove all devices
mediaremoted	Client <MRDMediaRemoteClient 0x7fd7XXX1d390, bundleIdentifier = bluetoothaudiod, pid = 5932> invalidated.
mediaremoted	Removing client <MRDMediaRemoteClient 0x7fd7XXX1d390, bundleIdentifier = bluetoothaudiod, pid = 5932>
mediaremoted	[AVRoutingServer] Setting (null) to application picked routes for client <MRDMediaRemoteClient 0x7fd735f1d390, bundleIdentifier = bluetoothaudiod, pid = 5932>
coreaudiod	BluetoothHALPlugIn_StopIO: triggered by (null) (0) - OUTPUT - MDR-1000X
coreaudiod	stopIO activeIO:1 relatedDevice activeIO:0 (output)
coreaudiod	stopIO:0 activeIO:0 (output)
AirPlayXPCHelper	Deactivate 04-5d-XX-72-XX-08
bluetoothaudiod	VID:0xFFFF PID:0x0000 (0x0000FFFF) FW:0x0000 (0x00000000FFFF)
bluetoothaudiod	Device supports A2DP sink
bluetoothaudiod	[init] entry
bluetoothaudiod	[init] virtual address = 0x10f6b6000
bluetoothaudiod	Create endpoints connected devices:1
bluetoothaudiod	Wifi is on 2.4GHz? 0
bluetoothaudiod	AAC Enabled
bluetoothaudiod	[init] entry
bluetoothaudiod	[init] virtual address = 0x10f6cf000
bluetoothaudiod	[init] entry
bluetoothaudiod	[init] virtual address = 0x10f700000
bluetoothaudiod	[createEndpoints] No SBC / AAC Rate Limits
bluetoothaudiod	[init] entry
bluetoothaudiod	[init] virtual address = 0x10f731000
bluetoothaudiod	Device supports AVRCP target
bluetoothaudiod	MediaRemote server initializing...
bluetoothaudiod	1 clients have now registered for Now Playing Notifications
bluetoothaudiod	Device supports HFP
mediaremoted	Adding client <MRDMediaRemoteClient 0x7fd7XXX1d390, bundleIdentifier = bluetoothaudiod, pid = 6020>
bluetoothaudiod	Set current codec (null)->SCO
bluetoothaudiod	Device supports HSP
bluetoothaudiod	Set current codec (null)->SCO
bluetoothaudiod	Created audio device MDR-1000X
bluetoothaudiod	XPC: BTStopIO for MDR-1000X
bluetoothaudiod	Stop IO - set output activeBeforeSleep = NO
bluetoothaudiod	Already stopped - return immediately
bluetoothaudiod	Update activity signaled:0
bluetoothaudiod	sendAudioStatus isAudioActive:0
bluetoothaudiod	Setting cached activePlayerPath (null) -> origin-XXX/client-com.google.Chrome-462 (Google Chrome)/player-MediaRemote-DefaultPlayer
bluetoothaudiod	Quitting now
coreaudiod	XPC Error remove all devices
coreaudiod	Remove all devices

Thanks for looking into this!

This isn’t the problem many users had. I have read about «excessive memory paging»... maybe this happens because you have too little RAM and a nearly full hard disc combined?

bluetoothaudiod (5932) is becoming invalidated

Otherwise, maybe you should try to reinstall?

It looks very close to what I had before the update.

kernel	memorystatus: killing_idle_process pid 5932 [bluetoothaudiod] jetsam_reason->osr_code: 9

But here it looks like even worse situation, might be too low memory at all for new Catalina OS (I have at least 8 and when I work it's often almost fully filled).

OK, my experience after .3 came out:

Still happening, but much less often, and switching back outputs is simple.

No idea what is happening.

For those who haven't updated yet, I just trashed everything before and after the update. Ev-er-y-thing. Restart, NVRAM. Most of it probably unnecessary, but something in there helped.

What doesn't help is the stupid amount of interference and issues I have with any transmitted signals, but that's because of my house and probably the lead or asbestos in the walls.

gpharry wrote:

...

Anyway: I think I'll wait for next releases (both Catalina and iOS) and eventually downgrade in worst case...

Giampaolo

Hi folks. Nothing's changed here. Still having bluetooth disconnection on catalina (maybe a little less ... but I couldn't swear) and still struggling with iOS/car's connection's issues.

Honestly I don't care if it happens (the problem ...) less or more frequent than 10.15.x The fact is: user experience is by far no longer what it used to be!

I started to think that way when I had to replace my 2017 MacBook Pro keyboard for the second time and despite the fact that Apple admitted the flaw, no replace policy to replace the whole laptop came out ...

Preparing backups for Mojave's downgrade ... :-(

Sadly,

Giampaolo

So you can switch back? That’s an improvement at least. I had that option with .2 already.

Do as Virtustilus suggested, leave your Console open (type bluetooth, coreaudiod, kernel or something? I actually don’t remember how it works) og watch what happens during the switches, if you can’t figure that out, and try to interpret what happened or post the codes. I have no idea how you can detect switches.

I have problems with switches myself sometimes, but I think that is related to a neighbour’s airplay device (no access). But I think I can fool Music when restarting and play a music video right away, so it doesn’t try to connect to the stranger’s device and switches to internal speakers with no option to the bluetooth unit. My airplay device is off, but it is an alternative. I don’t know, but I have no other idea.

It is unreasonable to think that switching has anything to the problem that many had. This is not a memory or a kernel task problem. So my problems are non-existing.

I tried to figure out the 4GB RAM issue, since I am using about 5,5-6 GB RAM, including cached memory (buffer memory), but I still think 4 GB RAM is enough for normal use, if you run one or two programs at the same time. But is it enough to avoid Bluetooth issues? RAM is cheap, but not everyone can upgrade. I don’t know if additional 4GB of RAM will work either or if it is worth it. Mojave isn’t running better than Catalina, but the system requirements are lower. And security is lower.

My experience after 10.15.3 came out:

The problem still exists and I am very surprised (not really) that Apple still ignores the issue. Bluetooth audio switches 2-3 times an hour. My device is MBP 2018 13" 8gb (Catalina 10.15.3).

I had this problem during the call with my business partners.

Such situations could be harmful to my reputation... Thanks Apple, I can't trust you anymore.

Upgraded to Catalina 10.15.3. No go.

0) MBP 2016 15 inch, 16GB, big SSD.

1) Able to connect to to the Sound BlasterX Katana

2) Able to select it as the output, however

3) Sound never comes out. It used to work prior to Catalina.

4) Sennheiser PCX550 still works great as does Plantronics Voyager

5) IOS 13.3.1 iPhone X still working fine too blasting out my Amazon Prime music via the SBX Katana.

It (10.15.3) is slightly better in that sound stops coming out of the internal speakers now. So it seems like the computer thinks it's sending sound somewhere. Maybe some driver has the sound turned down or has decided to mute? Who knows?

Tried the various actions of deleting stuff, resetting, re-pairing etc. etc. But no go.

Installed windows (for games). And I can say bluetooth works worse there :D I can't use BT sound + BT mouse + BT keyboard together, because sound starts to crackling. So connected keyboard and mouse by wires and now I can use it windows. I think I will no return to windows back anytime soon (at least win10). Just every system became even worse last years (pc and mac), or it's just how we feel changes in general (like in the past everything was better :D). Mac for work and I can't downgrade (because I need last the most fresh software), Win for games and nothing else.

...PC for games and nothing else. Bluetooth has its drawback. Crackling (or stuttering) is not dependent on the operating system nor the mac’s/computer’s hardware. In other words, crackling occurs both with pc and mac separately. In fact, the crackling occurs in the same games, independently of system requirements.

You cannot buy a place in «heaven».

Glad I could help.

I also wrote a shell script, that frequently checks the audio output and automatically reconnects the bluetooth audio if the connection is lost. If anyone is interested, let me know..

I don't remember when last time I had crackling in Mac, I think about 3 or more years ago, when I didn't have BT 4 yet )) But in windows it's happening with any software (not games even), like video in google chrome for example ) The hardware is the same. Difference in drivers I think and in processing sound buffers in BT audio part of OS.