mSBC profile is proposed but switching to it faile on a supported bluetooth device Pixel Buds Pro
The bug has also been reported for Ubuntu by me: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1993668
I am opening a ticket to the wireplumber repo but please let me know if I should open it to the pipewire repo instead.
I am running Ubuntu 22.10 with Pipewire 0.3.58-2ubuntu1 and Wireplumber 0.4.12-1. I know my bluetooth headset Pixel Buds Pro already works with mSBC since they are working fine on my laptop running Ubuntu 22.10.
The buggy machine has an Aorus x670 motherboard with an AMD Zen 4 CPU (kernel is Linux 5.19.0-21-generic). The bluetooth adapter is ID 0e8d:0616 MediaTek Inc. Wireless_Device which seems to correspond to MediaTek RZ616 Bluetooth (MT7922A chip, see https://wikidevi.wi-cat.ru/MediaTek for more details).
I have no idea whether this is due to this adapter, but that's the only difference I can see compared to my working laptop machine where I can indeed use the mSBC profile with those headsets.
The headset works well with the CVSD profile but while the mSBC profile is proposed in the menu, when I switch to it (using Gnome Sounds Settings), nothing happen and after a few seconds, it goes back to the CVSD profile and also the mSBC entry in the menu disappears.
See below a few log files that could help:
-
pw-dump.log: generated withpw-dump > pw-dump.log. In that file you will see the(HSP/HFP, codec mSBC)profile for my headset but strangely enough this entry is removed after trying to switch to mSBC (when the mSBC entry is also removed from the Gnome Sound Settings menu). -
pipewire-bluez.log: generated withWIREPLUMBER_NO_PW_LOG=1 PIPEWIRE_DEBUG=4 wireplumber 2>&1 | grep --line-buffered -Ei '^\[?[EW]\]?|spa\.bluez5' > pipewire-bluez.log. Here the logs starts when my headset are connecting and then after doing the faling mSBC switch in the Gnome settings.
Let me know if you need anything else.