[pulseaudio-discuss] [PATCH v0 0/2] bluetooth: Port->profile association
david.henningsson at canonical.com
Tue May 21 06:55:51 PDT 2013
On 05/21/2013 02:58 PM, Mikel Astiz wrote:
> Hi David,
> On Tue, May 21, 2013 at 2:37 PM, David Henningsson
> <david.henningsson at canonical.com> wrote:
>> On 05/20/2013 11:48 AM, Mikel Astiz wrote:
>>> From: Mikel Astiz <mikel.astiz at bmw-carit.de>
>>> These patches address a regression existing in the master branch, which
>>> specially affects the gnome UI. More info in
>> Thanks, I have now tested them and confirmed that they solve the problem
>>> The proposed solution is fairly simple but triggers the question whether
>>> something like PA_CORE_HOOK_PORT_PROFILE_ADDED is needed in the case of late
>>> Bluetooth UUIDs. In this scenario, the port has already been created by the
>>> time a new profile needs to be registered, typically after a
>>> Bluetooth-pairing procedure (for reference, see
>> I'm not really familiar with the late UUID problem, how common is that
>> really? I have never seen it myself, but then my range of hardware is
>> limited to a simple headset and a laptop.
> It's fairly common when pairing phones but I've never seen it with
> headsets. In practice, I'd say it's hardly possible to hit this issue
> when the pairing procedure (the Bluetooth device discovery) is
> initiated from our side, which is the case for all headsets.
> Besides, obviously, it's only possible with devices that support
> multiple profiles (HSP/HFP + A2DP).
Actually, I have a phone running Android 4.0 here, so I tried pairing it
with the laptop from the phone side, but there was no bluetooth card
showing up at all on the laptop side, and all in the gnome bluetooth GUI
is a checkbox asking me for network connections.
Maybe Android 4.0 (or my version of bluez?) does not support relaying
audio to (or from?) the phone?
David Henningsson, Canonical Ltd.
More information about the pulseaudio-discuss