1327
Comment:
|
3027
Noted reason why GNOME Display Manager attempts to capture the A2DP sinc, on session start (accessibility)
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
A2DP is the technology that allows connecting high quality audio bluetooth devices to your system. | A2DP is the technology that allows connecting high quality audio bluetooth devices, such as headphones and speakers, to your system. |
Line 3: | Line 3: |
== Packages == | == Requirements == |
Line 5: | Line 5: |
To connect your headphones, you need a working host device, and the following packages: | To connect your headphones, you need a working bluetooth device, and the following packages: |
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 11: | Line 11: |
It is also highgly recommended to install a graphical pairing tool. '''bluetooth-agent''' is already included with gnome, but you can also use '''blueman'''. | Once you have installed these packages, it may be necessary to restart the bluetooth and pulseaudio services: |
Line 13: | Line 13: |
Don't forget to restart bluetooth service: | On Jessie or newer (Systemd) {{{ systemctl restart bluetooth }}} |
Line 15: | Line 18: |
On Wheezy or older (SysVinit) | |
Line 19: | Line 23: |
On any {{{ killall pulseaudio }}} |
|
Line 22: | Line 30: |
Pair your device as usual and give it the "trust" attribute. | 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 [[DebianPkg:gnome-bluetooth|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 [[DebianPkg:blueman|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. |
Line 26: | Line 44: |
Using '''pavucontrol''', 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. | Using '''pavucontrol''' from the [[DebianPkg:pavucontrol|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. |
Line 28: | Line 46: |
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. 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. |
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. |
Line 43: | Line 53: |
== 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, as GDM needs pulseaudio in the gdm session for accessibility. For example, the screen reader requires it. 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 }}} In order to auto-connect a2dp for some devices, add this to '''/etc/pulse/default.pa''': {{{ load-module module-switch-on-connect }}} Reboot. 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:
On Jessie or newer (Systemd)
systemctl restart bluetooth
On Wheezy or older (?SysVinit)
service bluetooth restart
On any
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, as GDM needs pulseaudio in the gdm session for accessibility. For example, the screen reader requires it.
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
In order to auto-connect a2dp for some devices, add this to /etc/pulse/default.pa:
load-module module-switch-on-connect
Reboot.
Now the sound device (bluetooth headset) should be accessible through pavucontrol and standard audio device manager.