<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#c27">Comment # 27</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>(In reply to Enzo Laroche from <a href="show_bug.cgi?id=93898#c25">comment #25</a>) > <a href="https://gist.github.com/NainKult/b3557abb1274ce0b45c4a905b43a30b4#file">https://gist.github.com/NainKult/b3557abb1274ce0b45c4a905b43a30b4#file</a>- > gistfile1-txt-L86 I'm not sure that log contains everything from the point where you connect the headset. When you connect the headset, bluetoothd should send a NewConnection dbus message to pulseaudio, and that will be visible in the pulseaudio log. Your log doesn't show that. If a more complete log doesn't show that either, then bluetoothd apparently doesn't send the message, which is why in pulseaudio's opinion HSP isn't available. > It think it does support both HSP/HFP > backend-native.c: Registering Profile /Profile/HSPHSProfile > 00001108-0000-1000-8000-00805f9b34fb That log message only tells that pulseaudio registered itself to bluetoothd as a HSP implementation. It doesn't tell anything about what your headset supports. You can use bluetoothctl to query the features of the headset. Run "bluetoothctl" and then in the prompt enter "info A0:14:3D:1F:09:17".</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>