https://bugs.freedesktop.org/show_bug.cgi?id=92102
Tanu Kaskinen <ta...@iki.fi> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |luiz.de...@gmail.com
--- Comment #1 from Tanu Kaskinen <ta...@iki.fi> ---
Apparently the a2dp profile doesn't initially get connected. It's not
PulseAudio's job to connect the profiles, but something is connecting the hsp
profile, so I wonder why a2dp doesn't get connected at the same time... The
same or similar problem was reported recently in IRC, but we didn't find the
culprit at that time. Even though this doesn't appear to be a PulseAudio bug,
I'd be very interested to know what the solution is, if you figure out one.
I'll add Luiz von Dentz to CC... Luiz, do you have any idea where to start
debugging, if only the hsp profile gets connected when turning on a headset,
but a2dp starts only working when an explicit "connect" command is given in
bluetoothctl?
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
_______________________________________________
pulseaudio-bugs mailing list
pulseaudio-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/pulseaudio-bugs
