<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Refused to switch profile to headset_head_unit when trying to use bluetooth headset microphone" href="https://bugs.freedesktop.org/show_bug.cgi?id=93898#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Refused to switch profile to headset_head_unit when trying to use bluetooth headset microphone" href="https://bugs.freedesktop.org/show_bug.cgi?id=93898">bug 93898</a> from <a class="email" href="mailto:tanuk@iki.fi" title="Tanu Kaskinen <tanuk@iki.fi>"> Tanu Kaskinen</a> <pre>This bug was again brought up on the mailing list, and as I re-read your report, I noticed an important difference between the two devices: the working one has both "Headset" (HSP) and "Handsfree" (HFP) profiles, but the broken one only has "Handsfree". The native backend in PulseAudio only supports HSP, so if the headset only supports HFP, that's not going to work. Should we implement HFP in PulseAudio? I'm not sure. It was debated a lot whether it makes architectural sense to even implement HSP in an audio server, and HFP is an even more complicated protocol than HSP. In any case, I'm not volunteering to do the implementation. One possibility would be to tell everybody to use oFono, but at least when PulseAudio 6.0 was released, the oFono backend didn't support headsets (it only supported the scenario where PulseAudio is on the headset/handsfree device, i.e. wrong direction). I don't remember if the lack of headset support with oFono was due to lacking functionality in oFono or PulseAudio or both, and if it was due to lacking functionality in oFono, I don't know if the missing stuff has been implemented since then.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>