<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#c31">Comment # 31</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:github@laroche.pro" title="Enzo Laroche <github@laroche.pro>"> Enzo Laroche</a> <pre>(In reply to Tanu Kaskinen from <a href="show_bug.cgi?id=93898#c27">comment #27</a>) > 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 is truncated but show the bluetooth pairing. Line 1 is my pulseaudio doing nothing and between line 1 and 2 is where I switch my headset on and it pair. (In reply to Tanu Kaskinen from <a href="show_bug.cgi?id=93898#c27">comment #27</a>) > 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. My bad. had a brainfart on this one :P (In reply to Tanu Kaskinen from <a href="show_bug.cgi?id=93898#c27">comment #27</a>) > 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". Device A0:14:3D:1F:09:17 Name: metalheadset V2.05 Alias: metalheadset V2.05 Class: 0x00240408 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb) UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) UUID: Vendor specific (8b6814d3-6ce7-4498-9700-9312c1711f63) Modalias: bluetooth:v0043pA003d0000 (In reply to Tanu Kaskinen from <a href="show_bug.cgi?id=93898#c28">comment #28</a>) > James sent a new version of the patch set: > <a href="https://patchwork.freedesktop.org/patch/177864/">https://patchwork.freedesktop.org/patch/177864/</a> > <a href="https://patchwork.freedesktop.org/patch/177863/">https://patchwork.freedesktop.org/patch/177863/</a> > <a href="https://patchwork.freedesktop.org/patch/177865/">https://patchwork.freedesktop.org/patch/177865/</a> Seems like an awful lot of work to get it to merge with the master branch :( (In reply to Tanu Kaskinen from <a href="show_bug.cgi?id=93898#c28">comment #28</a>) > > HSP is mono output and input, A2DP is stereo output only. > Can confirm that, my headset switch to mono whenever I receive a call on my phone.</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>