A2DP support is not included in the binary packages of bluez-utils
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| bluez-utils (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: bluez-utils
I compiled the sources for bluez-utils 3.15-0ubuntu1 as published on launchpad. One of the big enhancements in the latest releases of bluez-utils is support for A2DP. This is an audio protocol used by some bluetooth headsets to provide better quality audio than the basic voice support. As they stand right now, the packaged sources for bluez-utils do not turn on the compilation of support for A2DP.
The solution would be to turn on the A2DP support during compilation and to include the necessary binaries and control files in the binary packages.
The addition of A2DP support in bluez-utils is not merely a technical novelty. It provides a replacement for bluetooth-alsa and as such has the following advantages over bluetooth-alsa:
1. It is much easier to configure and use than bluetooth-alsa. While we cannot yet talk of "plug and play", it is still a significant step towards supporting bluetooth headsets in Ubuntu in a user friendly way.
2. Bluetooth-alsa has serious technical defects. It introduces such a delay in the audio that it was practically impossible for me to listen to the audio track of a movie through my headset: the video and audio were utterly out of sync. In contrast, bluez-utils 3.15 introduces no such delay: watching movies with the audio in sync worked right out of the box for me.
Related branches
| Marcel Holtmann (holtmann) wrote | #1 |
| Daniel Holbach (dholbach) wrote | #2 |
| Changed in bluez-utils: | |
| status: | New → Fix Released |
| Sami Haahtinen (ressu) wrote | #3 |
I tried to talk to the Debian guys to make them clean up the package and actually enable the new services (they are off by default even if they are stable enough). So far I haven't seen a fixed up Debian package.
The main issue is DEB_CONFIGURE_
The old hidd, pand, dund etc. can be installed but should not be started by the init script. The init script actually only needs to start hcid with the -s option to enable the built-in SDP server and then hid2hci to switch HID proxy devices into HCI mode. The services will be automatically started on request or can be marked as autostart via their /etc/bluetooth/
I am also releasing today bluez-utils-3.16 that should include the support for mono headsets and will make the device setup easier. It will be as simple as adding something like the following to your .asoundrc:
pcm.bluetooth {
type bluetooth
device 00:11:22:33:44:55
}
When connecting to the "bluetooth" (you could use !default instead to make it default) device then it will automatically create the devices. No need to deal with D-Bus by yourself. This is helpful until we have full integration of audio device setup via bluetooth-wizard.