<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><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#c26">Comment # 26</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 <span class="vcard"><a class="email" href="mailto:joakim.tjernlund@infinera.com" title="Joakim Tjernlund <joakim.tjernlund@infinera.com>"> <span class="fn">Joakim Tjernlund</span></a>
</span></b>
<pre>(In reply to Tanu Kaskinen from <a href="show_bug.cgi?id=93898#c24">comment #24</a>)
<span class="quote">> (In reply to Joakim Tjernlund from <a href="show_bug.cgi?id=93898#c21">comment #21</a>)
> > With the removed, PA went back to earlier non working state. This can from
> > the log though:
>
> It looks like you dropped some word(s) from your sentence. Was there
> something in the log you wanted to highlight? From the log it looks like the
> UUIDs changed all of a sudden, which would be weird, but maybe that's
> happening because this was the first time trying with a new version of
> bluetoothd that doesn't any more modify the UUID list from the device, and
> the old UUIDs were from some database of bluetoothd that still contained the
> UUIDs from the old bluetoothd version.
>
> Otherwise I don't see anything strange in the log.
>
> > PA still announces UUIDs: 00001108-0000-1000-8000-00805f9b34fb
>
> What do you mean by that?</span >
Lets forget about that ATM, it is a bit confusing now with several things
moving
<span class="quote">> (In reply to Enzo Laroche from <a href="show_bug.cgi?id=93898#c23">comment #23</a>)
> > By the way, can someone look at this patch and tell me if it's relevant to
> > our current situation ? I just stumbled upon it.
> >
> > <a href="https://patchwork.freedesktop.org/patch/106453/">https://patchwork.freedesktop.org/patch/106453/</a>
>
> That patch is a part of a series. The patches are relevant if you have an
> HFP-only headset. The patches shouldn't be needed if the headset supports
> HSP.
>
> The patches probably won't apply cleanly to the current master. Somebody
> tried it once, and after it failed, I made a git branch available with the
> patches applied here: <a href="https://cgit.freedesktop.org/~tanuk/pulseaudio/">https://cgit.freedesktop.org/~tanuk/pulseaudio/</a>
> (branch "hfp").
>
> The patches have been reviewed, but not applied upstream, because they had
> issues. The original author never sent an updated version of the patches. If
> someone would like to finish the work, you can see the review feedback in
> patchwork:
> <a href="https://patchwork.freedesktop.org/patch/106452/">https://patchwork.freedesktop.org/patch/106452/</a>
> <a href="https://patchwork.freedesktop.org/patch/106453/">https://patchwork.freedesktop.org/patch/106453/</a>
> <a href="https://patchwork.freedesktop.org/patch/106454/">https://patchwork.freedesktop.org/patch/106454/</a></span >
I have these ported on top of current master, the last path (RFCOMM) needs
a total rewrite though as it was a mess to begin with.
I does not work yet, but HSP isn't either so I think I have a bug elsewhere.
The few times I got HSP profile to stick, it it only showed Mono output and
no sound at all. Is the Mono stuff really expected,if not, where to look?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>