I ran into this same issue after updating to 126.96.36.199 Koli–posted in the release note comments but moving the discussion over here so as to not clutter that thread, and since this seems like the same issue.
Curious–I got my pair of headphones last spring, and the update to 3.4 didn’t cause any issues for me. So, you might be right but there seems to be some other contributing factor since it happens for some but not all. That rules out my guess that it could be related to the firejail sandboxing & permissions though, since it sounds like the same issue happened during a previous update too.
[x] Always allow connections from this device
Supported profiles: SPP, HSP, A2DP, AVRCP, HFP, PBAP, DID
I wonder what bluetooth audio profile it uses–is there any way to check that from e.g. the command line? Not really very familiar with bluetooth audio.
pactl list output and it reports the relevant sink as
bluetooth.protocol = "a2dp_sink", and in general the output seems to match what I’m seeing on my laptop (also using pulseaudio) where it works just fine. The only difference I can spot is
(laptop): headphone-output: Headphone (type: Headphones, priority: 0, available)
(sailfish): headphone-output: Headphone (priority: 0, available)
which I think isn’t anything important, might well just be differences in output due to different PA versions or so…
@spark did you ever resolve/figure out your issue, or is your headset still not working with SFOS?