<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Bluetooth cannot select a2dp profile automatically in 6.0 RC1" href="https://bugs.freedesktop.org/show_bug.cgi?id=87081#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Bluetooth cannot select a2dp profile automatically in 6.0 RC1" href="https://bugs.freedesktop.org/show_bug.cgi?id=87081">bug 87081</a> from <a class="email" href="mailto:tanuk@iki.fi" title="Tanu Kaskinen <tanuk@iki.fi>"> Tanu Kaskinen</a> <pre>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?</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>