[Pkg-bluetooth-maintainers] Bug#772717: bluez: A2DP cannot work immediately after boot.

[Stefan Nagy]

I guess I'm affected by this bug, my report (originally reported against
pulseaudio) was merged with this one. I tested this with two different
notebooks (internal bluetooth adapters: Intel Wireless-N 1030 / Qualcomm
Atheros AR5B22).

In my original report I attached a bluetoothd log file.

> If I reconnect the
> bluetooth dongle (tested on a csr dongle with id 0a12:0001 and a broadcom
> BCM2046B1 dongle with id 0a5c:21e2, which is a multi-head device, along with a
> pair of pseudo-hci kb and mouse), or restart the bluetooth daemon, a2dp devices
> can work like a charm (adding audio sink to pulseaudio works fine). If I
> connect the dongle to a cardbus usb host controller (rather than the host
> controller embedded in motherboard), which will only be powered and work after
> the kernel being booted, a2dp devices work fine.
> 
>         It seems a2dp does not work properly if the dongle is powered before
> the kernel being booted.

Does it always work for you (adding audio sink to pulseaudio) when you
restart the bluetooth daemon? In my case sometimes it works (~80%),
sometimes it doesn't (~20%).