Further to this, bluetooth packages were included in todays updates and since then the A2DP option has disappeared from the profile dropdown. So I assume it's a work in progress.After some weeks of successfully using A2DP device profile with the Jabra, today it decided to stop working. I've given it 30 minutes of investigation and got nowhere. I've had to go back the headset and long-distance POTS audio quality.Thanks for the reply. Yes, my Trixie is fully up-to-date. Four profiles appear for the Jabra, High Fidelity Playback (A2DP Sink, codec SBC & codec SBC-XQ) and Headset Head Unit (HSP/HFP, codec CVSD & codec mSBC). Whichever one I select, when I try to select the Jabra as an input device, I get the error message above and the profile will also have reset itself to the Headset Head Unit (HSP/HFP, codec mSBC).
Ultimately I want to use Google Meet and there the Jabra does appear as the microphone, even if I haven't managed to set it in Raspberry Pi OS. All a bit confusing, but maybe I don't need to worry as long as Google Meet recognizes it.
Statistics: Posted by andrew_pi — Wed Nov 26, 2025 9:38 am