Differences between revisions 7 and 8
Revision 7 as of 2015-06-13 22:01:15
Size: 2961
Editor: ?Stanislav Naumuk
Comment: I've found the way to make A2DP headsets fully working.
Revision 8 as of 2015-08-17 15:38:33
Size: 2656
Editor: AriPollak
Comment: update for jessie
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
apt-get install pulseaudio pulseaudio-module-bluetooth bluez-audio pavucontrol bluez-firmware bluez-tools apt-get install pulseaudio pulseaudio-module-bluetooth pavucontrol bluez-firmware
Line 30: Line 30:
Pair your device as usual and give it the "trust" attribute. The "trust" attribute allows the device to automicatically establish a connection to your machine when turned on and in range. Pair your device as usual and give it the "trust" attribute. The "trust" attribute allows the device to automatically establish a connection to your machine when turned on and in range.
Line 37: Line 37:

If you prefer to use the command line, just do:

{{{
bt-audio -c 00:02:3C:38:AC:B9
}}}

Where ''00:02:3C:38:AC:B9'' is the address of your paired device.
Line 54: Line 46:
Bluetooth headset is connected, but ALSA/PulseAudio fails to pick up the connected device or there's no device to pick. This happens because GDM captures a2dp sink on session start. Bluetooth headset is connected, but ALSA/PulseAudio fails to pick up the connected device or there's no device to pick. This happens because GDM captures A2DP sink on session start.
Line 56: Line 48:
Under the `[General]` heading in ''/etc/bluetooth/audio.conf'' add or uncomment the following line:

{{{
Enable=Media,Sink,Source
}}}

In order to prevent GDM from capturing the A2DP sink on session start, you have to edit ''/var/lib/gdm/.pulse/client.conf'' (or create it, if it doesn't exist):
In order to prevent GDM from capturing the A2DP sink on session start, edit ''/var/lib/gdm3/.config/pulse/client.conf'' (or create it, if it doesn't exist):
Line 69: Line 55:
After that you have to grant access to this file to '''gdm''' user: After that you have to grant access to this file to '''Debian-gdm''' user:
Line 72: Line 58:
# chown gdm:gdm /var/lib/gdm/.pulse/client.conf # chown Debian-gdm:Debian-gdm /var/lib/gdm3/.config/pulse/client.conf
Line 77: Line 63:
Now the sound device (bluetooth headset) should be accessible through '''pavucontrol''' and standart audio device manager. Now the sound device (bluetooth headset) should be accessible through '''pavucontrol''' and standard audio device manager.

A2DP is the technology that allows connecting high quality audio bluetooth devices, such as headphones and speakers, to your system.

Requirements

To connect your headphones, you need a working bluetooth device, and the following packages:

apt-get install pulseaudio pulseaudio-module-bluetooth pavucontrol bluez-firmware

Once you have installed these packages, it may be necessary to restart the bluetooth and pulseaudio services:

service bluetooth restart
killall pulseaudio

Pairing

It is also highgly recommended to install a graphical pairing tool. If you are using GNOME as your desktop environment, bluetooth-applet should already be installed from the gnome-bluetooth package.

If you are using an alternative desktop environment that does not already include graphical bluetooth tools, you can use the blueman-applet from the blueman package:

apt-get install blueman

Both of these applets will appear in the notification area of your desktop environment and will provide options for pairing and connecting to your speakers or headphones.

Pair your device as usual and give it the "trust" attribute. The "trust" attribute allows the device to automatically establish a connection to your machine when turned on and in range.

Configuring

Using pavucontrol from the pavucontrol package, it is really easy to setup A2DP for your device, and map connections to it. Your paired headphones should appear as an option to output audio.

Don't forget to put it in high quality mode (A2DP) in the configuration tab. This is necessary for some devices that have mixed mode.

Compatible devices

Any A2DP device should work out of the box.

If you still didn't bought one, the Creative WP-300 works very well and has a very very nice sound.

Troubleshooting

Bluetooth headset is connected, but ALSA/PulseAudio fails to pick up the connected device or there's no device to pick. This happens because GDM captures A2DP sink on session start.

In order to prevent GDM from capturing the A2DP sink on session start, edit /var/lib/gdm3/.config/pulse/client.conf (or create it, if it doesn't exist):

autospawn = no
daemon-binary = /bin/true

After that you have to grant access to this file to Debian-gdm user:

# chown Debian-gdm:Debian-gdm /var/lib/gdm3/.config/pulse/client.conf

Reboot.

Now the sound device (bluetooth headset) should be accessible through pavucontrol and standard audio device manager.