[pulseaudio-tickets] [Bug 87081] Bluetooth cannot select a2dp profile automatically in 6.0 RC1
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Dec 9 02:26:52 PST 2014
https://bugs.freedesktop.org/show_bug.cgi?id=87081
--- Comment #5 from Tanu Kaskinen <tanuk at iki.fi> ---
BlueZ 5 doesn't have the Audio interface, which we use with BlueZ 4 for
synchronization (the Audio interface becomes connected after both A2DP and HSP
have become connected, so we wait until the Audio interface become connected
before loading the device module).
We've had problems with this before, and I think it became clear last time that
it's really not a good idea to implement a synchronization point like BlueZ 4
has done. Bluetooth devices can and sometimes do advertise their supported
devices asynchronously, in a way that makes it simply impossible for bluetoothd
to know when all profiles have been initialized.
The problem was solved by extending module-card-restore so that if it tries to
restore a profile that isn't available when the card is initially created,
restoring the profile will be done at the time the profile is added. Maybe this
dynamic profile adding has broken at some point?
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/pulseaudio-bugs/attachments/20141209/065fe9ee/attachment.html>
More information about the pulseaudio-bugs
mailing list