Comment 102 for bug 1838151

Hi everyone,

small progress report :

I tried the pipewire trick and it didn't work out for me, while it initially seemed to work: auto switch to the HSP/HPF profile didn't work and after a manual switch the headset would drop out during a conversation.
I reverted to pulseaudio and invested a bit more time, now I am _almost_ there :

I had to add the following to ~/.config/pulse/default.pa

.include /etc/pulse/default.pa
.nofail
unload-module module-bluetooth-policy
.fail
.ifexists module-bluetooth-policy.so
load-module module-bluetooth-policy auto_switch=2
.endif

.ifexists module-bluetooth-discover.so
load-module module-bluetooth-discover
.endif

to get the autoswitch to work.

I am happy to report that in slack (from snap) the audio now behaves just right and friends tell me I no longer sound like a robot.
Unfortunately this still doesn't work with zoom and there seems to be multiple issues. They probably come from zoom itself but I am unsure what to report to them.

according to https://gavv.github.io/articles/pulseaudio-under-the-hood/#autodetecting-properties it should be possible to make pulseaudio understand that it has to switch profiles by changing /usr/share/applications/Zoom.desktop and adding Telephony to the categories. I have not been able to make this work without auto_switch=2

Here are two scenarios that fail:
after a fresh boot (so all the stars are aligned), start zoom, create a new meeting, start the recording, say a few words, stop the recording, stop the meeting, open the resulting audio or video file
the sound is bad when it is expected to be good.

After a fresh boot (so all the stars are aligned), start zoom, go to settings-> audio, after doing this my headset is non functional and I must shut it down and start it back up to restore functionality.

can someone help me determine what zoom is doing wrong ?

I will also try a few other apps in the coming weeks