Difference between revisions of "Bluetooth headset"

From ArchWiki
Jump to navigation Jump to search
m
(Undo revision 595042 by Magi (talk) - not related to bluetooth or headset)
Tag: Undo
 
(154 intermediate revisions by 64 users not shown)
Line 2: Line 2:
 
[[Category:Bluetooth]]
 
[[Category:Bluetooth]]
 
[[ja:Bluetooth ヘッドセット]]
 
[[ja:Bluetooth ヘッドセット]]
[[ru:Bluetooth headset]]
+
[[zh-hans:Bluetooth headset]]
[[zh-CN:Bluetooth headset]]
 
 
{{Related articles start}}
 
{{Related articles start}}
 
{{Related|Bluetooth}}
 
{{Related|Bluetooth}}
{{Related|Bluez4}}
 
 
{{Related articles end}}
 
{{Related articles end}}
  
 
Currently, Arch Linux supports the A2DP profile (Audio Sink) for remote audio playback with the default installation.
 
Currently, Arch Linux supports the A2DP profile (Audio Sink) for remote audio playback with the default installation.
  
{{Note|Bluez5 is only supported by [[PulseAudio]] and not by [[ALSA]]. If you do not want to use PulseAudio, you need to install an older Bluez version from the AUR.}}
+
== Headset via Bluez5/PulseAudio ==
  
== Headset via Bluez5/PulseAudio ==
+
{{Merge|Bluetooth|Significant redundancy with general setup on Bluetooth page. Should be merged there. Headset-specific info would stay on this page.|Talk:Bluetooth#Merging general setup from Keyboard, Mouse, Headset pages}}
 +
 
 +
[[Install]] {{Pkg|pulseaudio-alsa}}, {{Pkg|pulseaudio-bluetooth}} and {{Pkg|bluez-utils}} providing the {{ic|bluetoothctl}} utility.
  
PulseAudio 5.x supports A2DP per default.
+
{{Note|Before continuing, ensure that the bluetooth device is not blocked by [[rfkill]].}}
Make sure the following packages are [[install]]ed: {{Pkg|pulseaudio-alsa}}, {{Pkg|pulseaudio-bluetooth}}, {{Pkg|bluez}}, {{Pkg|bluez-libs}}, {{Pkg|bluez-utils}}, {{Pkg|bluez-firmware}}. Without {{Pkg|pulseaudio-bluetooth}} you won't be able to connect after the next pairing and you won't get any usable error messages.
 
  
 +
=== Configuration via CLI ===
 
[[Start]] the {{ic|bluetooth.service}} systemd unit.
 
[[Start]] the {{ic|bluetooth.service}} systemd unit.
  
 
Now we can use the ''bluetoothctl'' command line utility to pair and connect. For troubleshooting and more detailed explanations of ''bluetoothctl'' see the [[Bluetooth]] article. Run
 
Now we can use the ''bluetoothctl'' command line utility to pair and connect. For troubleshooting and more detailed explanations of ''bluetoothctl'' see the [[Bluetooth]] article. Run
  
  # bluetoothctl
+
  $ bluetoothctl
  
 
to be greeted by its internal command prompt. Then enter:
 
to be greeted by its internal command prompt. Then enter:
  
  # power on
+
  [bluetooth]# power on
  # agent on
+
  [bluetooth]# agent on
  # default-agent
+
  [bluetooth]# default-agent
  # scan on
+
  [bluetooth]# scan on
  
 
Now make sure that your headset is in pairing mode. It should be discovered shortly. For example,
 
Now make sure that your headset is in pairing mode. It should be discovered shortly. For example,
 
  [NEW] Device 00:1D:43:6D:03:26 Lasmex LBT10
 
  [NEW] Device 00:1D:43:6D:03:26 Lasmex LBT10
shows a device that calls itself "Lasmex LBT10" and has MAC address ''00:1D:43:6D:03:26''. We will now use that MAC address to initiate the pairing:
+
shows a device that calls itself ''"Lasmex LBT10"'' and has MAC address ''"00:1D:43:6D:03:26"''. We will now use that MAC address to initiate the pairing:
  
  # pair 00:1D:43:6D:03:26
+
  [bluetooth]# pair 00:1D:43:6D:03:26
  
 
After pairing, you also need to explicitly connect the device (every time?):
 
After pairing, you also need to explicitly connect the device (every time?):
  
  # connect 00:1D:43:6D:03:26
+
  [bluetooth]# connect 00:1D:43:6D:03:26
 +
 
 +
If you are getting a connection error {{ic|org.bluez.Error.Failed}} retry by killing existing PulseAudio daemon first:
 +
 
 +
$ pulseaudio -k
 +
[bluetooth]# connect 00:1D:43:6D:03:26
  
 
If everything works correctly, you now have a separate output device in [[PulseAudio]].
 
If everything works correctly, you now have a separate output device in [[PulseAudio]].
{{Note|The device may be off by default. Select its audio profile (''OFF'', A2DP, HFP) in the "Configuration" tab of {{Pkg|pavucontrol}}.}}
+
{{Note|The device may be off by default. Select its audio profile ({{ic|OFF}}, {{ic|A2DP}}, {{ic|HFP}}) in the "Configuration" tab of {{Pkg|pavucontrol}}.}}
 
You can now redirect any audio through that device using the "Playback" and "Recording" tabs of {{Pkg|pavucontrol}}.
 
You can now redirect any audio through that device using the "Playback" and "Recording" tabs of {{Pkg|pavucontrol}}.
  
 
You can now disable scanning again and exit the program:
 
You can now disable scanning again and exit the program:
  # scan off
+
  [bluetooth]# scan off
  # exit
+
  [bluetooth]# exit
 +
 
 +
==== Setting up auto connection ====
 +
 
 +
To make your headset auto connect you need to enable PulseAudio's switch-on-connect module. Do this by adding the following lines to {{ic|/etc/pulse/default.pa}}:
 +
{{hc|/etc/pulse/default.pa|
 +
# automatically switch to newly-connected devices
 +
load-module module-switch-on-connect
 +
}}
 +
 
 +
Now make ''bluetoothctl'' trust your Bluetooth headset by running ''trust 00:1D:43:6D:03:26'' inside the ''bluetoothctl'' console to prevent errors similar to:
 +
bluetoothd[487]: Authentication attempt without agent
 +
bluetoothd[487]: Access denied: org.bluez.Error.Rejected
 +
 
 +
[bluetooth]# trust 00:1D:43:6D:03:26
 +
 
 +
By default, your Bluetooth adapter will not power on after a reboot. The former method by using {{ic|hciconfig hci0 up}} is deprecated, see the [http://www.bluez.org/release-of-bluez-5-35/ release note]. Now you just need to add the line {{ic|1=AutoEnable=true}} in {{ic|/etc/bluetooth/main.conf}} at the bottom in the {{ic|[Policy]}} section:
 +
{{hc|1=/etc/bluetooth/main.conf|2=
 +
[Policy]
 +
AutoEnable=true
 +
}}
 +
 
 +
==== Media controls ====
 +
 
 +
To use the media controls they may be forwarded to [https://specifications.freedesktop.org/mpris-spec/latest/ MPRIS2], where they can be picked up by media players that support mpris for external control. Install {{Pkg|bluez-utils}} and run
 +
 
 +
$ mpris-proxy
 +
 
 +
In order to start up mpris-proxy in the background and/or when your system starts, you may create a systemd user script
 +
 
 +
{{hc|~/.config/systemd/user/mpris-proxy.service|<nowiki>
 +
[Unit]
 +
Description=Forward bluetooth midi controls via mpris2 so they are picked up by supporting media players
 +
 
 +
[Service]
 +
Type=simple
 +
ExecStart=/usr/bin/mpris-proxy
 +
 
 +
[Install]
 +
WantedBy=default.target
 +
</nowiki>}}
 +
 
 +
Then start it
 +
 
 +
$ systemctl --user start mpris-proxy
 +
 
 +
and enable it to start at login
 +
 
 +
$ systemctl --user enable mpris-proxy
 +
 
 +
=== Configuration via GNOME Bluetooth ===
 +
{{Note| The A2DP profile will not activate using this method with pulseaudio 9/10 due to an ongoing bug, leading to possible low quality mono sound. See [[#A2DP not working with PulseAudio]] for a possible solution.}}
 +
You can use [[Bluetooth#Graphical|GNOME Bluetooth]] graphical front-end to easily configure your bluetooth headset.
 +
 
 +
First, you need to be sure that {{ic|bluetooth.service}} systemd unit is running.
 +
 
 +
Open GNOME Bluetooth and activate the bluetooth. After scanning for devices, you can connect to your headset selecting it on the device list. You can directly access to sound configuration panel from the device menu. On the sound panel, a new sink should appear when your device is connected.
 +
 
 +
=== LDAC/aptX ===
 +
[[wikipedia:LDAC_(codec)|LDAC]]/[[wikipedia:aptX|aptX]] codec support can be enabled by installing {{aur|pulseaudio-modules-bt-git}} and {{aur|libldac}}. See its [https://github.com/EHfive/pulseaudio-modules-bt project page] for configuration tips.
  
 
=== Troubleshooting ===
 
=== Troubleshooting ===
  
Many users report frustration with getting A2DP/Bluetooth Headsets to work.  
+
{{Note|Many users report frustration with getting A2DP/Bluetooth Headsets to work. see [[#Switch between HSP/HFP and A2DP setting]] for additional information.}}
 +
 
 +
==== Bad sound / Static noise / "Muddy" sound ====
 +
 
 +
If you experience bad sound quality with your headset, it could in all likelihood be because your headset is not set to the correct profile.
 +
See [[#Switch between HSP/HFP and A2DP setting]] to solve the problem.
  
 
==== Selected audio profile, but headset inactive and audio cannot be redirected ====
 
==== Selected audio profile, but headset inactive and audio cannot be redirected ====
Line 61: Line 130:
 
==== Pairing fails with AuthenticationFailed ====
 
==== Pairing fails with AuthenticationFailed ====
  
If pairing fails, you can try [https://stackoverflow.com/questions/12888589/linux-command-line-howto-accept-pairing-for-bluetooth-device-without-pin disabling SSPMode] with:
+
If pairing fails, you can try enabling or [https://stackoverflow.com/questions/12888589/linux-command-line-howto-accept-pairing-for-bluetooth-device-without-pin disabling SSPMode] with:
  # hciconfig hci0 sspmode 0
+
  # btmgmt ssp off
 +
or
 +
# btmgmt ssp on
 +
 
 +
You may need to turn off BlueTooth while you run this command.
  
 
==== Pairing works, but connecting does not ====
 
==== Pairing works, but connecting does not ====
Line 82: Line 155:
  
 
This may be due to the {{Pkg|pulseaudio-bluetooth}} package not being installed. Install it if it missing, then restart pulseaudio.
 
This may be due to the {{Pkg|pulseaudio-bluetooth}} package not being installed. Install it if it missing, then restart pulseaudio.
 +
 +
It can also be due to permission, especially if starting pulseaudio as root allows you to connect. Add your user to the ''lp'' group, then restart pulseaudio.
 +
See {{ic|/etc/dbus-1/system.d/bluetooth.conf}} for reference.
  
 
If the issue is not due to the missing package, the problem in this case is that PulseAudio is not catching up. A common solution to this problem is to restart PulseAudio. Note that it is perfectly fine to run ''bluetoothctl'' as root while PulseAudio runs as user. After restarting PulseAudio, retry to connect. It is not necessary to repeat the pairing.
 
If the issue is not due to the missing package, the problem in this case is that PulseAudio is not catching up. A common solution to this problem is to restart PulseAudio. Note that it is perfectly fine to run ''bluetoothctl'' as root while PulseAudio runs as user. After restarting PulseAudio, retry to connect. It is not necessary to repeat the pairing.
Line 91: Line 167:
 
The same load-module command can be added to {{ic|/etc/pulse/default.pa}}.
 
The same load-module command can be added to {{ic|/etc/pulse/default.pa}}.
  
If that still does not work, or you are using PulseAudio's system-wide mode, also load the following PulseAudio modules (again these can be loaded via your default.pa or system.pa):
+
If that still does not work, or you are using PulseAudio's system-wide mode, also load the following PulseAudio modules (again these can be loaded via your {{ic|default.pa}} or {{ic|system.pa}}):
  
 
  module-bluetooth-policy
 
  module-bluetooth-policy
Line 97: Line 173:
 
  module-bluez5-discover
 
  module-bluez5-discover
  
To have your headset auto connect you need to enable PulseAudio's switch-on-connect module. Add the following:
+
It's also possible there are no write permissions for the owner of /var/lib/bluetooth. If this is the case, you may get the device to work by removing and re-pairing it, but the issue will return after rebooting. Restoring write permissions fixes this issue:
{{hc|/etc/pulse/default.pa|
+
 
# automatically switch to newly-connected devices
+
chmod -R u+w /var/lib/bluetooth
load-module module-switch-on-connect
+
 
}}
+
==== Connecting works, but there are sound glitches all the time ====
 +
 
 +
This is very likely to occur when the Bluetooth and the WiFi share the same chip as they share the same physical antenna and possibly band range (2.4GHz). Although this works seamlessly on Windows, this is not the case on Linux.
  
You then need to tell ''bluetoothctl'' to trust your Bluetooth headset, or you will see errors like this:
+
A possible solution is to move your WiFi network to 5GHz so that there will be no interference. If your card/router does not support this, you can upgrade your WiFi drivers/firmware. This approach works on Realtek 8723BE and latest rtl drivers for this chip from AUR.
bluetoothd[487]: Authentication attempt without agent
 
bluetoothd[487]: Access denied: org.bluez.Error.Rejected
 
  
  [bluetooth]# trust 00:1D:43:6D:03:26
+
If nothing of the previous is possible, a less effective mitigation is to tweak the fragment size and the latency on PulseAudio output port, trying to compensate interference. Reasonable values must be chosen, because these settings can make the audio out of sync (e.g. when playing videos). To change the latency of the bluetooth headset's port (e.g. to 125000 microseconds in the following example):
 +
$ pactl set-port-latency-offset <bluez_card> headset-output '''125000'''
 +
where the identifier of the card can be found with
 +
  $ pacmd list-sinks | egrep -o 'bluez_card[^>]*'
 +
The fragment size can be set in the config file {{ic|/etc/pulse/daemon.conf}} and takes effect after a restart of PulseAudio (for more details please see [[PulseAudio/Troubleshooting#Setting the default fragment number and buffer size in PulseAudio]]).
  
After a reboot, your Bluetooth adapter will not power on by default. You need to add a udev rule to power it on:
+
Perhaps it will help to add "options ath9k btcoex_enable = 1" to the {{ic|/etc/modprobe.d/ath9k.conf}} (with the appropriate bluetooth adapter):
{{hc|/etc/udev/rules.d/10-local.rules|2=
+
{{hc|1=/etc/modprobe.d/ath9k.conf|2=
# Set bluetooth power up
+
# possibly fix for sound glitches
ACTION=="add", SUBSYSTEM=="bluetooth", KERNEL=="hci[0-9]*", RUN+="/usr/bin/hciconfig %k up"
+
options ath9k btcoex_enable = 1
 
}}
 
}}
 +
 +
Then restart.
  
 
==== Connecting works, but I cannot play sound ====
 
==== Connecting works, but I cannot play sound ====
Line 128: Line 210:
 
When using [[GDM]], another instance of PulseAudio is started, which "captures" your bluetooth device connection. This can be prevented by [[mask]]ing the pulseaudio socket for the GDM user by doing the following:
 
When using [[GDM]], another instance of PulseAudio is started, which "captures" your bluetooth device connection. This can be prevented by [[mask]]ing the pulseaudio socket for the GDM user by doing the following:
  
  $ mkdir -p ~gdm/.config/systemd/user
+
  # mkdir -p /var/lib/gdm/.config/systemd/user
  $ ln -s /dev/null ~gdm/.config/systemd/user/pulseaudio.socket
+
  # ln -s /dev/null /var/lib/gdm/.config/systemd/user/pulseaudio.socket
  
 
On next reboot the second instance of PulseAudio will not be started.
 
On next reboot the second instance of PulseAudio will not be started.
Line 156: Line 238:
 
  $ pacmd set-card-profile 2 a2dp_sink
 
  $ pacmd set-card-profile 2 a2dp_sink
  
where 2 is the index of the device retirieved through {{ic|pacmd ls}}.
+
where 2 is the index of the device retrieved through {{ic|pacmd ls}}.
 +
 
 +
==== Connecting works, sound plays fine until headphones become idle, then stutters ====
 +
 
 +
If the headphones play sound correctly until they become idle and then stutter on resume (e.g. because the sound is paused, or because no sound is played for a while), try disabling PulseAudio's automatic sink/source suspension on idle.
 +
 
 +
See [[PulseAudio/Troubleshooting#Bluetooth headset replay problems]] for steps.
  
 
==== UUIDs has unsupported type ====
 
==== UUIDs has unsupported type ====
Line 166: Line 254:
 
This message is a very common one and can be ignored.
 
This message is a very common one and can be ignored.
  
== Legacy method: ALSA-BTSCO ==
+
==== PC shows device as paired, but is not recognized by device ====
  
{{Out of date|Instructions rely on [[bluez4]].}}
+
This might be due to the device not supporting bluetooth LE for pairing.  
  
It is much easier to set up your bluetooth headset today, with bluez >= 3.16. You may want to try the out-of-box python script in [http://fosswire.com/2008/01/11/a2dp-stereo-linux/ this blog] (you need edit the script to work with gconftool-2). There is also a piece of equivalent bash script [http://lymanrb.blogspot.com/2008/05/linux.html here].
+
Try setting {{ic|1=ControllerMode = bredr}} in {{ic|/etc/bluetooth/main.conf}}. See [http://unix.stackexchange.com/questions/292189/pairing-bose-qc-35-over-bluetooth-on-fedora].
  
You need your headset's bdaddr. It is of the form ''12:34:56:78:9A:BC''. Either find it in the documentation of your headset, on the headset itself or with the '''hcitool scan''' command.
+
==== Device connects, then disconnects after a few moments ====
  
Install {{AUR|btsco}}{{Broken package link|{{aur-mirror|btsco}}}}.
+
If you see messages like the following in {{ic|journalctl}} output, and your device fails to connect or disconnects shortly after connecting:
  
To load the kernel module, type:
+
bluetoothd: Unable to get connect data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
  # modprobe snd-bt-sco
+
  bluetoothd: connect error: Connection refused (111)
There will now be an extra audio device. Use {{ic|alsamixer -cN}} (where N is most likely 1) to set the volume. You can access the device with any alsa-capable application by choosing the device ''BT headset'', or with any OSS application by using {{ic|/dev/dspN}} as the audio device.
 
  
But to actually get any sound, you have to connect your headset to the computer first.
+
This may be because you have already paired the device with another operating system using the same bluetooth adapter (e.g., dual-booting).  Some devices cannot handle multiple pairings associated with the same MAC address (i.e., bluetooth adapter).  You can fix this by re-pairing the device.  Start by removing the device:
  
=== Connecting the headset ===
+
$ bluetoothctl
 +
[bluetooth]# devices
 +
Device XX:XX:XX:XX:XX:XX My Device
 +
[bluetooth]# remove XX:XX:XX:XX:XX:XX
  
If you connect your headset for the first time, read the section about pairing first. To connect to your headset to the computer, use the command
+
Then [[restart]] {{ic|bluetooth.service}}, turn on your bluetooth adapter, make your device discoverable, re-scan for devices, and re-pair your device. Depending on your bluetooth manager, you may need to perform a full reboot in order to re-discover the device.
$ btsco -f <bdaddr>
 
for example
 
  $ btsco -f 12:34:56:78:9A:BC
 
  
==== Pairing the headset with your computer ====
+
==== Apple Airpods have low volume ====
  
The first time you connect the headset, you have to pair it with the computer. To do this, you need your headset's PIN. Depending on your headset you may have to reset the headset and repeat the pairing everytime you used the headset with another bluetooth device.
+
Edit {{ic|bluetooth.service}} by running {{ic|systemctl edit --full bluetooth.service}} and change the line:
  
There are two ways to pair your headset with the computer:
+
ExecStart=/usr/lib/bluetooth/bluetoothd
  
===== Using ''bluez-gnome'' =====
+
to:
  
{{Out of date|Package does no longer exist in the repositories.}}
+
ExecStart=/usr/lib/bluetooth/bluetoothd --noplugin=avrcp
  
Install the ''bluez-gnome'' package from the community repository. Then start the '''bt-applet''' program. Once you try to connect to the headset, a window will open and ask for the PIN.
+
Finally [[restart]] {{ic|bluetooth.service}}, [[reload]] systemd manager configuration
  
===== Using ''passkey-agent'' =====
+
Reconnect your headset.
  
Before connecting to the headset, enter the command
+
==== HSP problem: the bluetooth sink and source are created, but no audio is being transmitted ====
$ passkey-agent --default <pin>
 
where ''<pin>'' is your headset's PIN. Then try to connect to the headset.
 
  
=== Headset and ALSA Devices ===
+
You may be missing firmware or the SCO (audio protocol of HSP and HFP) routing might be wrong. See [https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Bluetooth/#index10h3] - the firmware for BCM20702 can be installed via {{AUR|bcm20702a1-firmware}} or {{AUR|bcm20702b0-firmware}}.
  
1. First if you have not already, [[install]] {{Pkg|bluez}} from the [[official repositories]].
+
== Headset via Bluez5/bluez-alsa ==
  
2. Scan for your device
+
{{Note|Bluez5 has dropped direct integration for [[ALSA]] and supports [[PulseAudio]] only. Follow the instructions below if you cannot or do not want to use PulseAudio.}}
$ hcitool (-i <optional hci#>***) scan
 
  
3. Pair your headset with your device:
+
First, ensure that your headset is correctly paired and connected to the system (see for example {{ic|bluetoothctl}}).
$ bluez-simple-agent (optional hci# ***) XX:XX:XX:XX:XX:XX
 
and put in your pin (0000 or 1234, etc)
 
  
4. Make sure your {{ic|/etc/bluetooth/audio.conf}} allows A2DP Audio Sinks. Place this line just bellow the [General] heading:
+
Then, install {{AUR|bluez-alsa-git}}, start (and enable) the {{ic|bluealsa}} service, and add your user to the {{ic|audio}} group.
Enable=Source,Sink,Media,Socket
 
  
5. Add this to your {{ic|/etc/asound.conf}} file:
+
Run the following command to check if everything is working as intended (replace MAC and FILE below):
  #/etc/asound.conf
+
  $ aplay -D bluealsa:HCI=hci0,DEV=MAC,PROFILE=a2dp FILE.wav
 
pcm.btheadset {
 
    type plug
 
    slave {
 
        pcm {
 
            type bluetooth
 
            device XX:XX:XX:XX:XX:XX
 
            profile "auto"
 
        } 
 
    } 
 
    hint {
 
        show on
 
        description "BT Headset"
 
    } 
 
}
 
ctl.btheadset {
 
  type bluetooth
 
 
  
6. Check to see if it has been added to alsa devices
+
Finally, add the following lines to your .asoundrc:
$ aplay -L
 
  
7. Now play with aplay:
+
{{hc|.asoundrc|
$ aplay -D btheadset /path/to/audio/file
+
defaults.bluealsa {
 
+
    interface "hci0"
or Mplayer:
+
    device "MAC"
$ mplayer -ao alsa:device=btheadset /path/to/audio/or/video/file
+
    profile "a2dp"
 
+
}
{{Tip|To find hci# for a usb dongle, type in
 
$ hcitool dev
 
 
}}
 
}}
  
=== Headset's multimedia buttons ===
+
You can now use the bluealsa device to reach your headset. Volume management is conducted normally via {{ic|alsamixer}}.
 
 
In order to get your bluetooth headset's multimedia buttons (play, pause, next, previous) working you need to create {{ic|/etc/modules-load.d/uinput.conf}} containing {{ic|uinput}}.
 
 
 
== Legacy method: PulseAudio ==
 
 
 
{{Out of date|Instructions rely on [[bluez4]] (references to {{ic|/etc/bluetooth/audio.conf}} and ''bluez-simple-agent'').}}
 
 
 
This one is much easier and more elegant. PulseAudio will seamlessly switch between output devices when the headset is turned on. If you have ALSA as the sound server, you need the following packages installed:
 
{{Pkg|pulseaudio}} and {{Pkg|pulseaudio-alsa}}.
 
 
 
Now, to configure the audio output to use bluetooth, just install {{Pkg|pavucontrol}} and run it to configure the audio output:
 
$ pavucontrol
 
Make sure to take a look at the [[PulseAudio]] wiki entry for setting up PulseAudio, especially if you are running KDE.
 
 
 
=== Troubleshooting ===
 
 
 
==== Audio sink fails ====
 
 
 
Bluetooth headset is connected, but ALSA/PulseAudio fails to pick up the connected device. You will get "Audio sink fails".
 
According to [http://wiki.gentoo.org/wiki/Bluetooth_Headset gentoo wiki], you have to verify than in {{ic|/etc/bluetooth/audio.conf}} there is {{ic|<nowiki>Enable=Socket</nowiki>}} under the {{ic|[General]}} section heading.
 
 
 
Just do a {{ic|# systemctl restart bluetooth}} to apply it.
 
 
 
==== Page timeout issue ====
 
 
 
If you receive this error whilst trying to pair your headset with your system using bluez-simple-agent, then you can try to restart your system and use the graphical bluez applet of your desktop environment.
 
  
 
== Legacy documentation: ALSA, bluez5 and PulseAudio method ==
 
== Legacy documentation: ALSA, bluez5 and PulseAudio method ==
Line 311: Line 345:
 
Once the required packages are installed, use this procedure to play audio with a bluetooth headset. The high level overview of the procedure is to pair the headset, connect the headset, configure the player and pulse audio controller and then play audio.
 
Once the required packages are installed, use this procedure to play audio with a bluetooth headset. The high level overview of the procedure is to pair the headset, connect the headset, configure the player and pulse audio controller and then play audio.
  
Start the bluetooth service as root:
+
[[Start]] the bluetooth service as root.
# systemctl start bluetooth
 
  
 
Verify Bluetooth is started
 
Verify Bluetooth is started
Line 487: Line 520:
 
As noted above this will work easily with audacious. YouTube videos with Chromium and Flash Player will work on some videos. If the video has ads it will not work, but if the video does not have ads it will work. Just make sure that after audacious is working with Bluetooth headset, start Chromium, and navigate to YouTube. Find a video without leading ads, and it should play the audio. If the settings icon has the a menu with two drop-down combo boxes for Speed and Quality it will play.
 
As noted above this will work easily with audacious. YouTube videos with Chromium and Flash Player will work on some videos. If the video has ads it will not work, but if the video does not have ads it will work. Just make sure that after audacious is working with Bluetooth headset, start Chromium, and navigate to YouTube. Find a video without leading ads, and it should play the audio. If the settings icon has the a menu with two drop-down combo boxes for Speed and Quality it will play.
  
== Switch between HSV and A2DP setting ==
+
== Switch between HSP/HFP and A2DP setting ==
 +
 
 +
This can easily be achieved by the following command where the {{ic|''card_number''}} can be obtained by running {{ic|pacmd list-cards}}.
 +
 
 +
$ pacmd set-card-profile ''card_number'' a2dp_sink
  
This can easily be achieved by the following command where 2 needs to be changed with the correct device number.
+
For enabling automatic profile switching from A2DP to HSP when a recording stream appears without any role set, you can append {{ic|1=auto_switch=2}} to {{ic|load-module module-bluetooth-policy}} in {{ic|/etc/pulse/default.pa}}.
  
pacmd set-card-profile 2 a2dp_sink
+
For more information about PulseAudio profiles, see [https://freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Bluetooth/#index1h2 PulseAudio Documentation].
  
 
=== A2DP not working with PulseAudio ===
 
=== A2DP not working with PulseAudio ===
Line 498: Line 535:
  
 
If PulseAudio fails when changing the profile to A2DP with bluez 4.1+ and PulseAudio 3.0+, you can try disabling the Socket interface from {{ic|/etc/bluetooth/audio.conf}} by removing the line {{ic|1=Enable=Socket}} and adding line {{ic|1=Disable=Socket}}.
 
If PulseAudio fails when changing the profile to A2DP with bluez 4.1+ and PulseAudio 3.0+, you can try disabling the Socket interface from {{ic|/etc/bluetooth/audio.conf}} by removing the line {{ic|1=Enable=Socket}} and adding line {{ic|1=Disable=Socket}}.
 +
 +
==== A2DP sink profile is unavailable ====
 +
 +
When the A2DP sink profile is unavailable it will not be possible to switch to the A2DP sink (output) with a PulseAudio front-end and the A2DP sink will not even be listed. This can be confirmed with {{ic|pactl}}.
 +
 +
  $ pactl list | grep -C2 A2DP
 +
      Profiles:
 +
              headset_head_unit: Headset Head Unit (HSP/HFP) (sinks: 1, sources: 1, priority: 30, available: yes)
 +
              a2dp_sink: High Fidelity Playback (A2DP Sink) (sinks: 1, sources: 0, priority: 40, available: no)
 +
              off: Off (sinks: 0, sources: 0, priority: 0, available: yes)
 +
          Active Profile: headset_head_unit
 +
 +
Trying to manually set the card profile with {{ic|pacmd}} will fail.
 +
 +
  $ pacmd set-card-profile bluez_card.C4_45_67_09_12_00 a2dp_sink
 +
  Failed to set card profile to 'a2dp_sink'.
 +
 +
This is known to happen from version 10.0 of Pulseaudio when connecting to Bluetooth headphones via Bluedevil or another BlueZ front-end. See [https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/525 related bug report.]
 +
 +
This issue also appears after initial pairing of Headphones with some Bluetooth controllers (e.g. {{ic|0a12:0001, Cambridge Silicon Radio}}) which might default to the {{ic|Handsfree}} or {{ic|Headset - HS}} service and will not allow switching to the A2DP PulseAudio sink that requires the {{ic|AudioSink}} service.
 +
 +
Possible solutions:
 +
 +
* For some headsets, using the headset's volume or play/pause controls while connected can trigger the A2DP profile to become available.
 +
 +
* It is possible that connecting to a headset via {{ic|bluetoothctl}} from {{pkg|bluez-utils}} will make the A2DP sink profile available. There is an automation for this every time a bluetooth device is connected: {{AUR|fix-bt-a2dp}} ([https://github.com/pastleo/fix-bt-a2dp#usage detailed usage])
 +
 +
[bluetooth]# connect ''[headset MAC here]''
 +
 +
* Manually switching to Bluetooth's {{ic|AudioSink}} service which would make the A2DP profile and its A2DP PulseAudio sink available. This can be done with blueman-manager which included in {{pkg|blueman}} or by registering the UUID of the AudioSink service with {{ic|bluetoothctl}} .
 +
 +
  $ bluetoothctl
 +
  [bluetooth]# menu gatt
 +
  [bluetooth]# register-service 0000110b-0000-1000-8000-00805f9b34fb
 +
  [bluetooth]# quit
  
 
==== Gnome with GDM ====
 
==== Gnome with GDM ====
Line 503: Line 575:
 
{{Merge|#Connecting works, but I cannot play sound|duplicate instructions}}
 
{{Merge|#Connecting works, but I cannot play sound|duplicate instructions}}
  
{{Note|Below was tested with Gnome 3.18.4 and PulseAudio 8.0}}
+
The instructions below were tested on Gnome 3.24.2 and PulseAudio 10.0 however they may still be applicable and useful for other versions.
  
If PulseAudio fails when changing the profile to A2DP while using GNOME with GDM, you need to prevent GDM from starting its own instance of PulseAudio :
+
If PulseAudio fails when changing the profile to A2DP while using GNOME with GDM, you need to prevent GDM from starting its own instance of PulseAudio:
  
* Prevent Pulseaudio clients from automatically starting a server if one isn't running by adding the following lines to {{ic|/var/lib/gdm/.config/pulse/client.conf}} :
+
* Prevent Pulseaudio clients from automatically starting a server if one is not running by adding the following:
  
{{bc|1=
+
{{hc|/var/lib/gdm/.config/pulse/client.conf|<nowiki>
 
autospawn = no
 
autospawn = no
 
daemon-binary = /bin/true
 
daemon-binary = /bin/true
}}
+
</nowiki>}}
  
* Prevent systemd from starting Pulseaudio anyway with socket activation :
+
* Prevent systemd from starting Pulseaudio anyway with socket activation:
  
{{bc|
+
$ sudo -ugdm mkdir -p /var/lib/gdm/.config/systemd/user
sudo -ugdm mkdir -p /var/lib/gdm/.config/systemd/user
+
$ sudo -ugdm ln -s /dev/null /var/lib/gdm/.config/systemd/user/pulseaudio.socket
sudo -ugdm ln -s /dev/null /var/lib/gdm/.config/systemd/user/pulseaudio.socket
 
}}
 
  
* Restart, and check that there is no Pulseaudio process for the {{ic|gdm}} user.
+
* Restart, and check that there is no PulseAudio process for the {{ic|gdm}} user using:
  
{{Note|1=Discussion about this problem can be found [https://bbs.archlinux.org/viewtopic.php?id=194006 here] and [https://bbs.archlinux.org/viewtopic.php?id=196689 here]}}
+
  $ pgrep -u gdm pulseaudio
  
== Tested headsets ==
+
Further discussion about this problem and alternative fixes can be found [https://bbs.archlinux.org/viewtopic.php?id=194006 here] and [https://bbs.archlinux.org/viewtopic.php?id=196689 here].
 
 
{| class="wikitable sortable"
 
! Model
 
! Version
 
! Comments
 
! Compatible
 
|-
 
| '''Philips SHB9150'''
 
| bluez5, pulseaudio 9
 
|
 
| {{Yes}}
 
|-
 
| '''Philips SHB9100'''
 
|
 
| Pause and resume is flaky. See [https://bbs.archlinux.org/viewtopic.php?pid=1315428#p1315428] for the underlying issue and a temporary solution to improve audio quality.
 
| {{R|Limited}}
 
|-
 
| '''Philips SHB7000'''
 
|
 
| Pause and resume is flaky.
 
| {{R|Limited}}
 
|-
 
| '''Philips SHB7100'''
 
| bluez 5.32, pulseaudio 6.0
 
| Next/previous buttons work. Pause and resume is flaky (sometimes works in VLC, not at all in Audacious). Tested only A2DP and Handsfree audio out, built-in mic was broken.
 
| {{R|Limited}}
 
|-
 
| '''Philips SHB7150'''
 
| bluez 5.32, pulseaudio 6.0
 
| Next/previous buttons work. Pause and resume work in VLC. Tested only A2DP profile.
 
| {{Yes}}
 
|-
 
| '''Philips SHB5500BK/00'''
 
| bluez 5.28, PulseAudio 6.0
 
| Pause and resume is not working.
 
| {{R|Limited}}
 
|-
 
| '''Parrot Zik'''
 
|
 
| Microphone detected but does not work (HSP profile unavailable). If the Bluetooth connection cuts, there will be a noticeable delay in audio. Work around by reinitializing the Bluetooth connection.
 
| {{R|Limited}}
 
|-
 
| '''Parrot Zik 2.0'''
 
|
 
| Microphone detected but does not work (HSP profile unavailable). If the Bluetooth connection cuts, there will be a noticeable delay in audio. Work around by reinitializing the Bluetooth connection.
 
| {{R|Limited}}
 
|-
 
| '''Parrot Zik 3.0'''
 
|
 
| Microphone detected but does not work (HSP profile unavailable). No delay issues.
 
| {{R|Limited}}
 
|-
 
| '''Sony DR-BT50'''
 
| bluez{4,5}
 
| Works for a2dp, see [http://vlsd.blogspot.com/2013/11/bluetooth-headphones-and-arch-linux.html]). Adapter: D-Link DBT-120 USB dongle.
 
| {{Yes}}
 
|-
 
| '''Sony SBH50'''
 
| bluez5
 
| Works for a2dp, Adapter: Broadcom Bluetooth 2.1 Device (Vendor=0a5c ProdID=219b Rev=03.43). Requires the {{ic|btusb}} [[modprobe|module]].
 
| {{Yes}}
 
|-
 
| '''Sony MDR-XB950BT'''
 
| pulseaudio
 
| Tested a2dp. Adapter: Grand-X BT40G. Doesn't auto-connect, need to connect manually. Other functionality works fine.
 
| {{R|Limited}}
 
|-
 
| '''Sony MUC-M1BT1'''
 
| bluez5, {{AUR|pulseaudio-git}}
 
| Both A2DP & HSP/HFP work fine.
 
| {{Yes}}
 
|-
 
| '''SoundBot SB220'''
 
| bluez5, {{AUR|pulseaudio-git}}
 
|
 
| {{Yes}}
 
|-
 
| '''Auna Air 300'''
 
| bluez5, pulseaudio-git
 
| For some reason, a few restarts were required, and eventually it just started working.
 
| {{R|Limited}}
 
|-
 
| '''Sennheiser MM 400-X'''
 
| bluez5, pulseaudio 4.0-6
 
|
 
| {{Yes}}
 
|-
 
| '''Sennheiser MM 550-X Travel'''
 
| bluez 5.27-1, pulseaudio 5.0-1
 
| Next/Previous buttons work out-of-the-box, Play/Pause does not
 
| {{Yes}}
 
|-
 
| '''Sennheiser URBANITE XL Wireless'''
 
| bluez 5.37-2, pulseaudio 7.1-3
 
| A2DP High Fidelity Playback. Play/Pause/Next/Previous works out-of-the-box.
 
| {{Yes}}
 
|-
 
| '''Audionic BlueBeats (B-777)'''
 
| bluez5, pulseaudio 4.0-6
 
|
 
| {{Yes}}
 
|-
 
| '''Logitech Wireless Headset'''
 
| bluez 5.14, pulseaudio-git
 
| part number PN 981-000381, advertised for use with iPad
 
| {{Yes}}
 
|-
 
| '''HMDX Jam Classic Bluetooth'''
 
| bluez, pulseaudio-git
 
|
 
| {{Yes}}
 
|-
 
| '''PT-810'''
 
| bluez 5.14, pulseaudio-git
 
| Generic USB-Powered Bluetooth Audio Receiver with 3.5mm headset jack and a2dp profile. Widely available as "USB Bluetooth Receiver." IDs as PT-810.
 
| {{Yes}}
 
|-
 
| '''Philips SHB4000WT'''
 
| bluez5
 
| A2DP works, HDP distorted.
 
| {{Yes}}
 
|-
 
| '''Philips AEA2000/12'''
 
| bluez5
 
|
 
| {{Yes}}
 
|-
 
| '''Nokia BH-104'''
 
| bluez4
 
|
 
| {{Yes}}
 
|-
 
| '''Creative AirwaveHD'''
 
| bluez 5.23
 
| Bluetooth adapter Atheros Communications usb: 0cf3:0036
 
| {{Yes}}
 
|-
 
| '''Creative HITZ WP380'''
 
| bluez 5.27, pulseaudio 5.0-1
 
| A2DP Profile only. Buttons work (Play, Pause, Prev, Next). Volume buttons are hardware-only. Auto-connect works but you should include the bluetooth module in "pulseaudio" to switch to it automatically. Clear HD Music Audio (This device support APTx codec but it isn't supported in linux yet). You may have some latency problems which needs pulseaudio restart.
 
| {{Yes}}
 
|-
 
| '''deleyCON Bluetooth Headset'''
 
| bluez 5.23
 
| Adapter: CSL - USB nano Bluetooth-Adapter V4.0. Tested a2dp profile. Untested microphone. Does not auto-connect (even when paired and trusted), must connect manually. Play/pause button mutes/unmutes the headphones, not the playback. Playback fwd/bwd buttons do not work (nothing visible with ''xev'').
 
| {{R|Limited}}
 
|-
 
| '''UE BOOM'''
 
| bluez 5.27, pulseaudio-git 5.99
 
| Update to latest UE BOOM fw 1.3.58. Sound latency in video solved by configuring pavucontrol. Works with UE BOOM x2.
 
| {{Yes}}
 
|-
 
| '''LG HBS-730'''
 
| bluez 5.30, pulseaudio 6.0
 
| Works out of box with A2DP profile.
 
| {{Yes}}
 
|-
 
| '''LG HBS-750'''
 
| bluez 5.30, pulseaudio-git 6.0
 
| Works out of box with A2DP profile.
 
| {{Yes}}
 
|-
 
| '''Beats Studio Wireless'''
 
| bluez 5.28, pulseaudio 6.0
 
| Works out of box. Not tested multimedia buttons.
 
| {{Yes}}
 
|-
 
| '''AKG Y45BT'''
 
| bluez 5.30, pulseaudio 6.0
 
| Pause and resume does not work. Needs {{ic|1=Enable=Socket}} in {{ic|/etc/bluetooth/audio.conf}} and {{ic|load-module module-bluetooth-discover}} in {{ic|/etc/pulse/default.pa}}.
 
| {{Yes}}
 
|-
 
| '''Bluedio Turbine/Turbine 2+'''
 
| bluez 5.3, pulseaudio 6.0
 
| HSP/HFP work fine, A2DP work fine.
 
| {{Yes}}
 
|-
 
| '''Sony SBH20'''
 
| bluez 5.30, pulseaudio 6.0
 
| Works out of box with A2DP profile.
 
| {{Yes}}
 
|-
 
| '''Nokia BH-111'''
 
| bluez 5.30, pulseaudio 6.0
 
| Works with both HSP/HFP and A2DP. Buttons work in certain apps.
 
| {{Yes}}
 
|-
 
| '''Sony MDR-ZX330BT'''
 
| bluez 5.31, pulseaudio 6.0
 
| Works out of box (HSP/HFP and A2DP). Buttons work in certain apps.
 
| {{Yes}}
 
|-
 
| '''Samsung Level Link'''
 
| bluez 5.33, pulseaudio 6.0
 
| Works out of box (HSP/HFP and A2DP). Buttons work in certain apps.
 
| {{Yes}}
 
|-
 
| '''Bernafon Soundgate 3'''
 
| bluez 5.34-2, pulseaudio 7.0-1
 
| Works (A2DP) after installing blueman-git 2.0.r53.g2a812a8-1.
 
| {{Yes}}
 
|-
 
| '''JBL E40 BT'''
 
| bluez 5.35, pulseaudio 7.0
 
| Connection works after installing blueberry and blueman. A2DP works after adding Disable=Socket to {{ic|/etc/bluetooth/audio.conf}}. Media buttons works.
 
| {{Yes}}
 
|-
 
| '''Sony SBH80'''
 
| bluez 5.36, pulseaudio 7.1
 
| Media buttons do not work. A2DP works after disabling profiles and enabling A2DP in blueman.
 
| {{Yes}}
 
|-
 
| '''Kitsound Manhattan'''
 
| bluez 5.37, pulseaudio 7.13
 
| All appears to work fine.  If Pulseaudio is run as root ( --system) rather than as a user, it often resuls in either a refusal to connect once paired, or else a complete system freeze ( asking for the access PIN )!  You have been warned. 
 
| {{Yes}}
 
|-
 
| '''JBL Everest 300'''
 
| bluez 5.37, pulseaudio 8.0
 
| Everything works correctly.  Headphones connected with HSP/HFP profile and sound quality was bad, but after switching profile in '''pavucontrol''' to A2DP sink sound quality went way up (as expected). Pairing went without issues.
 
| {{Yes}}
 
|-
 
| '''Logitech UE9000'''
 
| bluez 5.37, pulseaudio 7.1, gnome 3.18.2
 
| Audio playback works correctly after gnome/gdm fix [[#Connecting works.2C but I cannot play sound|here]]. Audio profile defaults to HSP/HFP. Microphone works in both HSP/HFP and A2DP profiles. Play/Pause and Fwd/Back functions work correctly in Spotify and VLC
 
| {{Yes}}
 
|-
 
| '''Bose AE2 SoundLink'''
 
| bluez 5.36, pulseaudio 7.1
 
| Pause and resume does not work. Microphone does not work.
 
| {{R|Limited}}
 
|-
 
| '''Jawbone Jambox'''
 
| bluez 5.38, pulseaudio 8.0
 
|
 
| {{Yes}}
 
|-
 
| '''Plantronics BackBeat FIT'''
 
| bluez5, pulseaudio 8.0
 
| Fully working on both headset and a2dp profiles. Pause button pauses the player. (Tested in mpv.)
 
| {{Yes}}
 
|-
 
| '''Aukey EP-B26'''
 
| bluez 5.39-1, pulseaudio 8.0-3
 
| Fully working on both headset(poor quality) and a2dp(good quality) profiles. Pause button pauses the player, back/forth goes to previous/next song. (Tested in mpv) Microphone works only in HSP/HFP mode.
 
| {{Yes}}
 
|}
 
  
 
== See also ==
 
== See also ==
 
  
 
Using the same device on Windows and Linux without pairing the device over and over again
 
Using the same device on Windows and Linux without pairing the device over and over again
  
 
* [http://ubuntuforums.org/showthread.php?p=9363229#post9363229 Dual booting with a Bluetooth keyboard]
 
* [http://ubuntuforums.org/showthread.php?p=9363229#post9363229 Dual booting with a Bluetooth keyboard]

Latest revision as of 20:50, 14 January 2020

Currently, Arch Linux supports the A2DP profile (Audio Sink) for remote audio playback with the default installation.

Headset via Bluez5/PulseAudio

Merge-arrows-2.pngThis article or section is a candidate for merging with Bluetooth.Merge-arrows-2.png

Notes: Significant redundancy with general setup on Bluetooth page. Should be merged there. Headset-specific info would stay on this page. (Discuss in Talk:Bluetooth#Merging general setup from Keyboard, Mouse, Headset pages)

Install pulseaudio-alsa, pulseaudio-bluetooth and bluez-utils providing the bluetoothctl utility.

Note: Before continuing, ensure that the bluetooth device is not blocked by rfkill.

Configuration via CLI

Start the bluetooth.service systemd unit.

Now we can use the bluetoothctl command line utility to pair and connect. For troubleshooting and more detailed explanations of bluetoothctl see the Bluetooth article. Run

$ bluetoothctl

to be greeted by its internal command prompt. Then enter:

[bluetooth]# power on
[bluetooth]# agent on
[bluetooth]# default-agent
[bluetooth]# scan on

Now make sure that your headset is in pairing mode. It should be discovered shortly. For example,

[NEW] Device 00:1D:43:6D:03:26 Lasmex LBT10

shows a device that calls itself "Lasmex LBT10" and has MAC address "00:1D:43:6D:03:26". We will now use that MAC address to initiate the pairing:

[bluetooth]# pair 00:1D:43:6D:03:26

After pairing, you also need to explicitly connect the device (every time?):

[bluetooth]# connect 00:1D:43:6D:03:26

If you are getting a connection error org.bluez.Error.Failed retry by killing existing PulseAudio daemon first:

$ pulseaudio -k
[bluetooth]# connect 00:1D:43:6D:03:26

If everything works correctly, you now have a separate output device in PulseAudio.

Note: The device may be off by default. Select its audio profile (OFF, A2DP, HFP) in the "Configuration" tab of pavucontrol.

You can now redirect any audio through that device using the "Playback" and "Recording" tabs of pavucontrol.

You can now disable scanning again and exit the program:

[bluetooth]# scan off
[bluetooth]# exit

Setting up auto connection

To make your headset auto connect you need to enable PulseAudio's switch-on-connect module. Do this by adding the following lines to /etc/pulse/default.pa:

/etc/pulse/default.pa
# automatically switch to newly-connected devices
load-module module-switch-on-connect

Now make bluetoothctl trust your Bluetooth headset by running trust 00:1D:43:6D:03:26 inside the bluetoothctl console to prevent errors similar to:

bluetoothd[487]: Authentication attempt without agent
bluetoothd[487]: Access denied: org.bluez.Error.Rejected
[bluetooth]# trust 00:1D:43:6D:03:26

By default, your Bluetooth adapter will not power on after a reboot. The former method by using hciconfig hci0 up is deprecated, see the release note. Now you just need to add the line AutoEnable=true in /etc/bluetooth/main.conf at the bottom in the [Policy] section:

/etc/bluetooth/main.conf
[Policy]
AutoEnable=true

Media controls

To use the media controls they may be forwarded to MPRIS2, where they can be picked up by media players that support mpris for external control. Install bluez-utils and run

$ mpris-proxy

In order to start up mpris-proxy in the background and/or when your system starts, you may create a systemd user script

~/.config/systemd/user/mpris-proxy.service
[Unit]
Description=Forward bluetooth midi controls via mpris2 so they are picked up by supporting media players

[Service]
Type=simple
ExecStart=/usr/bin/mpris-proxy

[Install]
WantedBy=default.target

Then start it

$ systemctl --user start mpris-proxy

and enable it to start at login

$ systemctl --user enable mpris-proxy

Configuration via GNOME Bluetooth

Note: The A2DP profile will not activate using this method with pulseaudio 9/10 due to an ongoing bug, leading to possible low quality mono sound. See #A2DP not working with PulseAudio for a possible solution.

You can use GNOME Bluetooth graphical front-end to easily configure your bluetooth headset.

First, you need to be sure that bluetooth.service systemd unit is running.

Open GNOME Bluetooth and activate the bluetooth. After scanning for devices, you can connect to your headset selecting it on the device list. You can directly access to sound configuration panel from the device menu. On the sound panel, a new sink should appear when your device is connected.

LDAC/aptX

LDAC/aptX codec support can be enabled by installing pulseaudio-modules-bt-gitAUR and libldacAUR. See its project page for configuration tips.

Troubleshooting

Note: Many users report frustration with getting A2DP/Bluetooth Headsets to work. see #Switch between HSP/HFP and A2DP setting for additional information.

Bad sound / Static noise / "Muddy" sound

If you experience bad sound quality with your headset, it could in all likelihood be because your headset is not set to the correct profile. See #Switch between HSP/HFP and A2DP setting to solve the problem.

Selected audio profile, but headset inactive and audio cannot be redirected

Deceptively, this menu is available before the device has been connected; annoyingly it will have no effect. The menu seems to be created as soon as the receiver recognizes the device.

Make sure to run bluetoothctl (with sudo/as root) and connect the device manually. There may be configuration options to remove the need to do this each time, but neither pairing nor trusting induce automatic connecting for me.

Pairing fails with AuthenticationFailed

If pairing fails, you can try enabling or disabling SSPMode with:

# btmgmt ssp off

or

# btmgmt ssp on

You may need to turn off BlueTooth while you run this command.

Pairing works, but connecting does not

You might see the following error in bluetoothctl:

[bluetooth]# connect 00:1D:43:6D:03:26
Attempting to connect to 00:1D:43:6D:03:26
Failed to connect: org.bluez.Error.Failed

To further investigate, have a look at the log via one of the following commands:

# systemctl status bluetooth
# journalctl -n 20

You might see a message like this:

bluetoothd[5556]: a2dp-sink profile connect failed for 00:1D:43:6D:03:26: Protocol not available

This may be due to the pulseaudio-bluetooth package not being installed. Install it if it missing, then restart pulseaudio.

It can also be due to permission, especially if starting pulseaudio as root allows you to connect. Add your user to the lp group, then restart pulseaudio. See /etc/dbus-1/system.d/bluetooth.conf for reference.

If the issue is not due to the missing package, the problem in this case is that PulseAudio is not catching up. A common solution to this problem is to restart PulseAudio. Note that it is perfectly fine to run bluetoothctl as root while PulseAudio runs as user. After restarting PulseAudio, retry to connect. It is not necessary to repeat the pairing.

If restarting PulseAudio does not work, you need to load module-bluetooth-discover.

# pactl load-module module-bluetooth-discover

The same load-module command can be added to /etc/pulse/default.pa.

If that still does not work, or you are using PulseAudio's system-wide mode, also load the following PulseAudio modules (again these can be loaded via your default.pa or system.pa):

module-bluetooth-policy
module-bluez5-device
module-bluez5-discover

It's also possible there are no write permissions for the owner of /var/lib/bluetooth. If this is the case, you may get the device to work by removing and re-pairing it, but the issue will return after rebooting. Restoring write permissions fixes this issue:

chmod -R u+w /var/lib/bluetooth

Connecting works, but there are sound glitches all the time

This is very likely to occur when the Bluetooth and the WiFi share the same chip as they share the same physical antenna and possibly band range (2.4GHz). Although this works seamlessly on Windows, this is not the case on Linux.

A possible solution is to move your WiFi network to 5GHz so that there will be no interference. If your card/router does not support this, you can upgrade your WiFi drivers/firmware. This approach works on Realtek 8723BE and latest rtl drivers for this chip from AUR.

If nothing of the previous is possible, a less effective mitigation is to tweak the fragment size and the latency on PulseAudio output port, trying to compensate interference. Reasonable values must be chosen, because these settings can make the audio out of sync (e.g. when playing videos). To change the latency of the bluetooth headset's port (e.g. to 125000 microseconds in the following example):

$ pactl set-port-latency-offset <bluez_card> headset-output 125000

where the identifier of the card can be found with

$ pacmd list-sinks | egrep -o 'bluez_card[^>]*'

The fragment size can be set in the config file /etc/pulse/daemon.conf and takes effect after a restart of PulseAudio (for more details please see PulseAudio/Troubleshooting#Setting the default fragment number and buffer size in PulseAudio).

Perhaps it will help to add "options ath9k btcoex_enable = 1" to the /etc/modprobe.d/ath9k.conf (with the appropriate bluetooth adapter):

/etc/modprobe.d/ath9k.conf
# possibly fix for sound glitches
options ath9k btcoex_enable = 1

Then restart.

Connecting works, but I cannot play sound

Make sure that you see the following messages in your system log:

bluetoothd[5556]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSource
bluetoothd[5556]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSink

If you see a message similar to this, you can go on and investigate your PulseAudio configuration. Otherwise, go back and ensure the connection is successful.

Tango-go-next.pngThis article or section is a candidate for moving to PulseAudio/Troubleshooting.Tango-go-next.png

Notes: The following seems to be general issue: [1] (Discuss in Talk:Bluetooth headset#)

When using GDM, another instance of PulseAudio is started, which "captures" your bluetooth device connection. This can be prevented by masking the pulseaudio socket for the GDM user by doing the following:

# mkdir -p  /var/lib/gdm/.config/systemd/user
# ln -s /dev/null  /var/lib/gdm/.config/systemd/user/pulseaudio.socket

On next reboot the second instance of PulseAudio will not be started.

It may happen that bluez wrongly considers an headset as not a2dp capable. In this case, search the index of the bluetooth device with

$ pacmd ls

Among the output there should be a section related to the bluetooth headset, containing something similar to

pacmd ls
index: 2
        name: <bluez_card.XX_XX_XX_XX_XX_XX>
        driver: <module-bluez5-device.c>
        owner module: 27
        properties:
                device.description = "SONY MDR-100ABN"
                device.string = "XX:XX:XX:XX:XX:XX"
                device.api = "bluez"
                device.class = "sound"
                ...

To manually set the profile, run

$ pacmd set-card-profile 2 a2dp_sink

where 2 is the index of the device retrieved through pacmd ls.

Connecting works, sound plays fine until headphones become idle, then stutters

If the headphones play sound correctly until they become idle and then stutter on resume (e.g. because the sound is paused, or because no sound is played for a while), try disabling PulseAudio's automatic sink/source suspension on idle.

See PulseAudio/Troubleshooting#Bluetooth headset replay problems for steps.

UUIDs has unsupported type

During pairing you might see this output in bluetoothctl:

[CHG] Device 00:1D:43:6D:03:26 UUIDs has unsupported type

This message is a very common one and can be ignored.

PC shows device as paired, but is not recognized by device

This might be due to the device not supporting bluetooth LE for pairing.

Try setting ControllerMode = bredr in /etc/bluetooth/main.conf. See [2].

Device connects, then disconnects after a few moments

If you see messages like the following in journalctl output, and your device fails to connect or disconnects shortly after connecting:

bluetoothd: Unable to get connect data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
bluetoothd: connect error: Connection refused (111)

This may be because you have already paired the device with another operating system using the same bluetooth adapter (e.g., dual-booting). Some devices cannot handle multiple pairings associated with the same MAC address (i.e., bluetooth adapter). You can fix this by re-pairing the device. Start by removing the device:

$ bluetoothctl
[bluetooth]# devices
Device XX:XX:XX:XX:XX:XX My Device
[bluetooth]# remove XX:XX:XX:XX:XX:XX

Then restart bluetooth.service, turn on your bluetooth adapter, make your device discoverable, re-scan for devices, and re-pair your device. Depending on your bluetooth manager, you may need to perform a full reboot in order to re-discover the device.

Apple Airpods have low volume

Edit bluetooth.service by running systemctl edit --full bluetooth.service and change the line:

ExecStart=/usr/lib/bluetooth/bluetoothd

to:

ExecStart=/usr/lib/bluetooth/bluetoothd --noplugin=avrcp

Finally restart bluetooth.service, reload systemd manager configuration

Reconnect your headset.

HSP problem: the bluetooth sink and source are created, but no audio is being transmitted

You may be missing firmware or the SCO (audio protocol of HSP and HFP) routing might be wrong. See [3] - the firmware for BCM20702 can be installed via bcm20702a1-firmwareAUR or bcm20702b0-firmwareAUR.

Headset via Bluez5/bluez-alsa

Note: Bluez5 has dropped direct integration for ALSA and supports PulseAudio only. Follow the instructions below if you cannot or do not want to use PulseAudio.

First, ensure that your headset is correctly paired and connected to the system (see for example bluetoothctl).

Then, install bluez-alsa-gitAUR, start (and enable) the bluealsa service, and add your user to the audio group.

Run the following command to check if everything is working as intended (replace MAC and FILE below):

$ aplay -D bluealsa:HCI=hci0,DEV=MAC,PROFILE=a2dp FILE.wav

Finally, add the following lines to your .asoundrc:

.asoundrc
defaults.bluealsa {
    interface "hci0"
    device "MAC"
    profile "a2dp"
}

You can now use the bluealsa device to reach your headset. Volume management is conducted normally via alsamixer.

Legacy documentation: ALSA, bluez5 and PulseAudio method

Tango-inaccurate.pngThe factual accuracy of this article or section is disputed.Tango-inaccurate.png

Reason: Describes two different methods, see the talk page for details. (Discuss in Talk:Bluetooth_Headset#bluez5_method:_overcomplicated_instructions)

ALSA, bluez5, and PulseAudio work together to allow a wireless Bluetooth headset to play audio. The following method works with a Lenovo T61p laptop and SoundBot SB220 wireless bluetooth headset. The required software stack is extensive and failure to include all components can produce errors which are difficult to understand. The following list of software packages might not be the minimum required set and needs to be examined more closely.

Bluez5 has a regression causing HSP/HFP Telephone profile to not be available. This regression is documented in the draft release notes for Pulseaudio 5.0 which say (in "Notes for packagers"): "PulseAudio now supports BlueZ 5, but only the A2DP profile. BlueZ 4 is still the only way to make HSP/HFP work." (from here)

Install Software Packages

The core software components are ALSA, Bluez5, PulseAudio. However there are additional libraries which are required. As well as a player which can play audio files. The following section lists the software packages installed in order to connect the headset and play audio over the headset.

Install ALSA and associated libraries

ALSA works with the linux kernel to provide audio services to user mode software. The following packages are used with the Bluetooth headset: alsa-utils, alsa-plugins, alsa-tools.

Install Bluez5

Bluez5 is the latest Bluetooth stack. It is required for PulseAudio to interface with wireless headsets. Required packages: bluez, bluez-utils, bluez-libs.

Install Audacious

Audacious is a program which plays audio files. It can work directly with ALSA or with PulseAudio. Required packages: audacious, audacious-plugins.

Procedure

Once the required packages are installed, use this procedure to play audio with a bluetooth headset. The high level overview of the procedure is to pair the headset, connect the headset, configure the player and pulse audio controller and then play audio.

Start the bluetooth service as root.

Verify Bluetooth is started

# systemctl status bluetooth
bluetooth.service - Bluetooth service
  Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; disabled)
  Active: active (running) since Sat 2013-12-07 12:31:14 PST; 12s ago
    Docs: man:bluetoothd(8)
Main PID: 3136 (bluetoothd)
  Status: "Running"
  CGroup: /system.slice/bluetooth.service
          └─3136 /usr/lib/bluetooth/bluetoothd

Dec 07 12:31:14 t61p systemd[1]: Starting Bluetooth service...
Dec 07 12:31:14 t61p bluetoothd[3136]: Bluetooth daemon 5.11
Dec 07 12:31:14 t61p systemd[1]: Started Bluetooth service.
Dec 07 12:31:14 t61p bluetoothd[3136]: Starting SDP server
Dec 07 12:31:14 t61p bluetoothd[3136]: Bluetooth management interface 1.3 i...ed
Hint: Some lines were ellipsized, use -l to show in full.

Start the PulseAudio daemon. This must be done after X windows is started and as a normal user.

$ pulseaudio -D

Verify the PulseAudio daemon is running.

$ pulseaudio --check -v
I: [pulseaudio] main.c: Daemon running as PID 3186

Start up bluetoothctl as root and pair and connect your headset. As a regular user, bluetoothctl will pair but not connect. Perhaps this is related to the config file (shown below) which is setup for what appears to be the root user. Note: the procedure shown below is for an initial pair and connect of the headphone. If the headset is already paired, then the procedure below can be shortened to: power on, agent on, default-agent, connect <mac address>. The mac address can be seen from the devices command output.

 $ bluetoothctl 
 [NEW] Controller 00:1E:4C:F4:98:5B t61p-0 [default]
 [NEW] Device 00:1A:7D:12:36:B9 SoundBot SB220
 [bluetooth]# show
 Controller 00:1E:4C:F4:98:5B
       Name: t61p
       Alias: t61p-0
       Class: 0x000000
       Powered: no
       Discoverable: no
       Pairable: yes
       UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
       UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
       UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
       UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
       UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
       UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
       UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
       Modalias: usb:v1D6Bp0246d050B
       Discovering: no
 [bluetooth]# power on
 [CHG] Controller 00:1E:4C:F4:98:5B Class: 0x0c010c
 Changing power on succeeded
 [CHG] Controller 00:1E:4C:F4:98:5B Powered: yes
 [bluetooth]# agent on
 Agent registered
 [bluetooth]# default-agent
 Default agent request successful

<power on your headset in pairing mode. Eventually you will see what appears to be a mac address.>

 [bluetooth]# scan on
 Discovery started
 [CHG] Controller 00:1E:4C:F4:98:5B Discovering: yes
 [CHG] Device 00:1A:7D:12:36:B9 RSSI: -61
 [bluetooth]# pair 00:1A:7D:12:36:B9
 Attempting to pair with 00:1A:7D:12:36:B9
 [CHG] Device 00:1A:7D:12:36:B9 Connected: yes
 [CHG] Device 00:1A:7D:12:36:B9 UUIDs has unsupported type
 [CHG] Device 00:1A:7D:12:36:B9 Paired: yes
 Pairing successful
 [bluetooth]# connect 00:1A:7D:12:36:B9
 [CHG] Device 00:1A:7D:12:36:B9 Connected: yes
 Connection successful
 [bluetooth]# info 00:1A:7D:12:36:B9
 Device 00:1A:7D:12:36:B9
       Name: SoundBot SB220
       Alias: SoundBot SB220
       Class: 0x240404
       Icon: audio-card
       Paired: yes
       Trusted: no
       Blocked: no
       Connected: yes
       LegacyPairing: yes
       UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
       UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
       UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
       UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
       UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)

Start up alsamixer, for simplicity un-mute all your outputs. Oddly enough some can be muted though. The ones I had muted during playback were:

  • Headphones
  • SPIDF

Start up audacious. Use the menu to select PulseAudio as your output. Somewhere I read that bluez5 requires pulseaudio-git and this jives with my experience.

Start up pavucontrol in a terminal. In the Outputs tab select the bluetooth headset.

screenshot of application settings

Miscellaneous configuration files

For reference, these settings were also done.

ALSA /etc/asound.conf

The settings shown at the top of this page was used, but the additional modification for Intel laptop sound cards.

pcm.btheadset {
  type plug
  slave {
    pcm {
      type bluetooth
      device 00:1A:7D:12:36:B9
      profile "auto"
    }
  }
  hint {
    show on
    description "BT Headset"
  }
}
ctl.btheadset {
  type bluetooth
}
options snd-hda-intel model=laptop
/etc/dbus-1/system.d/bluetooth.conf

The settings here seem to be enabled for root only. See the policy user="root" section. However, if a regular user is specified here, the system fails to start. Someone with more knowledge could explain why.

/etc/dbus-1/system.d/bluetooth.conf
<!-- This configuration file specifies the required security policies for Bluetooth core daemon to work. -->

<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
  "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>

  <!-- ../system.conf have denied everything, so we just punch some holes -->

  <policy user="root">
    <allow own="org.bluez"/>
    <allow send_destination="org.bluez"/>
    <allow send_interface="org.bluez.Agent1"/>
    <allow send_interface="org.bluez.MediaEndpoint1"/>
    <allow send_interface="org.bluez.MediaPlayer1"/>
    <allow send_interface="org.bluez.ThermometerWatcher1"/>
    <allow send_interface="org.bluez.AlertAgent1"/>
    <allow send_interface="org.bluez.Profile1"/>
    <allow send_interface="org.bluez.HeartRateWatcher1"/>
    <allow send_interface="org.bluez.CyclingSpeedWatcher1"/>
  </policy>

  <policy at_console="true">
    <allow send_destination="org.bluez"/>
  </policy>

  <!-- allow users of lp group (printing subsystem) to communicate with bluetoothd -->
  <policy group="lp">
    <allow send_destination="org.bluez"/>
  </policy>

  <policy context="default">
    <deny send_destination="org.bluez"/>
  </policy>

</busconfig>
Tested applications

As noted above this will work easily with audacious. YouTube videos with Chromium and Flash Player will work on some videos. If the video has ads it will not work, but if the video does not have ads it will work. Just make sure that after audacious is working with Bluetooth headset, start Chromium, and navigate to YouTube. Find a video without leading ads, and it should play the audio. If the settings icon has the a menu with two drop-down combo boxes for Speed and Quality it will play.

Switch between HSP/HFP and A2DP setting

This can easily be achieved by the following command where the card_number can be obtained by running pacmd list-cards.

$ pacmd set-card-profile card_number a2dp_sink

For enabling automatic profile switching from A2DP to HSP when a recording stream appears without any role set, you can append auto_switch=2 to load-module module-bluetooth-policy in /etc/pulse/default.pa.

For more information about PulseAudio profiles, see PulseAudio Documentation.

A2DP not working with PulseAudio

Socket interface problem

If PulseAudio fails when changing the profile to A2DP with bluez 4.1+ and PulseAudio 3.0+, you can try disabling the Socket interface from /etc/bluetooth/audio.conf by removing the line Enable=Socket and adding line Disable=Socket.

A2DP sink profile is unavailable

When the A2DP sink profile is unavailable it will not be possible to switch to the A2DP sink (output) with a PulseAudio front-end and the A2DP sink will not even be listed. This can be confirmed with pactl.

 $ pactl list | grep -C2 A2DP
      Profiles:
              headset_head_unit: Headset Head Unit (HSP/HFP) (sinks: 1, sources: 1, priority: 30, available: yes)
              a2dp_sink: High Fidelity Playback (A2DP Sink) (sinks: 1, sources: 0, priority: 40, available: no)
              off: Off (sinks: 0, sources: 0, priority: 0, available: yes)
         Active Profile: headset_head_unit

Trying to manually set the card profile with pacmd will fail.

 $ pacmd set-card-profile bluez_card.C4_45_67_09_12_00 a2dp_sink
 Failed to set card profile to 'a2dp_sink'.

This is known to happen from version 10.0 of Pulseaudio when connecting to Bluetooth headphones via Bluedevil or another BlueZ front-end. See related bug report.

This issue also appears after initial pairing of Headphones with some Bluetooth controllers (e.g. 0a12:0001, Cambridge Silicon Radio) which might default to the Handsfree or Headset - HS service and will not allow switching to the A2DP PulseAudio sink that requires the AudioSink service.

Possible solutions:

  • For some headsets, using the headset's volume or play/pause controls while connected can trigger the A2DP profile to become available.
  • It is possible that connecting to a headset via bluetoothctl from bluez-utils will make the A2DP sink profile available. There is an automation for this every time a bluetooth device is connected: fix-bt-a2dpAUR (detailed usage)
[bluetooth]# connect [headset MAC here]
  • Manually switching to Bluetooth's AudioSink service which would make the A2DP profile and its A2DP PulseAudio sink available. This can be done with blueman-manager which included in blueman or by registering the UUID of the AudioSink service with bluetoothctl .
 $ bluetoothctl
 [bluetooth]# menu gatt
 [bluetooth]# register-service 0000110b-0000-1000-8000-00805f9b34fb
 [bluetooth]# quit

Gnome with GDM

Merge-arrows-2.pngThis article or section is a candidate for merging with #Connecting works, but I cannot play sound.Merge-arrows-2.png

Notes: duplicate instructions (Discuss in Talk:Bluetooth headset#)

The instructions below were tested on Gnome 3.24.2 and PulseAudio 10.0 however they may still be applicable and useful for other versions.

If PulseAudio fails when changing the profile to A2DP while using GNOME with GDM, you need to prevent GDM from starting its own instance of PulseAudio:

  • Prevent Pulseaudio clients from automatically starting a server if one is not running by adding the following:
/var/lib/gdm/.config/pulse/client.conf
autospawn = no
daemon-binary = /bin/true
  • Prevent systemd from starting Pulseaudio anyway with socket activation:
$ sudo -ugdm mkdir -p /var/lib/gdm/.config/systemd/user
$ sudo -ugdm ln -s /dev/null /var/lib/gdm/.config/systemd/user/pulseaudio.socket
  • Restart, and check that there is no PulseAudio process for the gdm user using:
 $ pgrep -u gdm pulseaudio

Further discussion about this problem and alternative fixes can be found here and here.

See also

Using the same device on Windows and Linux without pairing the device over and over again