Bluetooth regression: doesn't reliably detect A2DP sink
Bluetooth Radio, Bluetooth Headset, Desktop Environment, Distribution, Version (Bluez, Kernel, and PipeWire):
- Aftershokz Opencomm headset
- bluez 5.55
- kernel 5.10.28
- pipewire 0.3.25
Description of Problem:
Updated yesterday from pipewire 0.3.24 to 0.3.25 (I'm using debian unstable), with no further changes.
Pipewire used to detect reliably both the A2DP sink and the HSP/HFP profiles. In fact, I was successfully using both A2DP with SBC-XQ and HFP with mSBC without issues (I cannot thank you enough for this!).
After the update to 0.3.25, upon the first connection I frequently can only see the HSP/HFP profiles. A2DP sink is not available.
However, if I discovered that if I restart bluez, I can sometimes get A2DP working without touching anything else.
After some experimentation, I found that changing bluez's MultiProfile to off (I had "multiple" set before) seems to make A2DP avalable more frequently for some reason, however this wasn't necessary before (and bluez wasn't changed either).
90% of the time
Steps to Reproduce:
- turn on BT headset
- device shows up, but only with HSP/HFP profile
- A2DP sink used to be always available