Difference between revisions of "Bluetooth headset"

From ArchWiki
Jump to: navigation, search
(Switch between HSV and A2DP setting)
m (ALSA-BTSCO method: Changed "wanna" to "want to")
(19 intermediate revisions by 16 users not shown)
Line 1: Line 1:
[[Category:Sound (English)]]
+
[[Category:Sound]]
This article describes how to set up a bluetooth headset with Arch Linux. Before you get started, you have to make sure that bluetooth is set up and working, especially that the ''dbus'' and ''hcid'' (started with the bluetooth start scriptlet) daemons are running.
+
[[Category:Bluetooth]]
 +
{{Article summary start}}
 +
{{Article summary text|This article describes how to set up a bluetooth headset.}}
 +
{{Article summary heading|Related}}
 +
{{Article summary wiki|Bluetooth}}
 +
{{Article summary end}}
 +
Before you get started, you have to make sure that [[Bluetooth|bluetooth]] is set up and working.
  
 
== ALSA-BTSCO method ==
 
== ALSA-BTSCO method ==
  
It is much easier to set up your bluetooth headset today, with bluez >= 3.16. You may wanna try the out-of-box python script in [http://fosswire.com/2008/01/11/a2dp-stereo-linux/ this blog] (you need edit the skript to work with gconftool-2). There's also a piece of equivalent bash script [http://lymanrb.blogspot.com/2008/05/linux.html here].
+
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's also a piece of equivalent bash script [http://lymanrb.blogspot.com/2008/05/linux.html here].
  
 
The following method is '''out-of-date''' and '''obsoleted'''.
 
The following method is '''out-of-date''' and '''obsoleted'''.
Line 12: Line 18:
 
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.
 
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.
  
Install {{AUR|btsco}} from AUR.
+
Install {{AUR|btsco}}.
  
To load the kernel module, type
+
To load the kernel module, type:
 
  # modprobe snd-bt-sco
 
  # modprobe snd-bt-sco
There will now be an extra audio device. Use '''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 ''/dev/dspN'' as the audio device.
+
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.
 
But to actually get any sound, you have to connect your headset to the computer first.
Line 44: Line 50:
  
 
=== Headset and Alsa Devices  ===
 
=== Headset and Alsa Devices  ===
1. First if you have not already, install bluez
+
1. First if you have not already, [[pacman|install]] {{Pkg|bluez}} from the [[official repositories]].
# pacman -S bluez
+
 
2. Scan for your device
 
2. Scan for your device
 
  $ hcitool (-i <optional hci#>***) scan
 
  $ hcitool (-i <optional hci#>***) scan
3. Pair your headset with your device
+
3. Pair your headset with your device:
 
  $ bluez-simple-agent (optional hci# ***) XX:XX:XX:XX:XX:XX
 
  $ bluez-simple-agent (optional hci# ***) XX:XX:XX:XX:XX:XX
 
   and put in your pin (0000 or 1234, etc)
 
   and put in your pin (0000 or 1234, etc)
4. Add this to your/etc/asound.conf file
+
4. Make sure your {{ic|/etc/bluetooth/audio.conf}} allows A2DP Audio Sinks. Place this line just bellow the [Genera] heading:
 +
Enable=Source,Sink,Media,Socket
 +
5. Add this to your {{ic|/etc/asound.conf}} file:
 
  #/etc/asound.conf
 
  #/etc/asound.conf
 
   
 
   
Line 72: Line 79:
 
  }   
 
  }   
  
5. Check to see if it has been added to alsa devices
+
6. Check to see if it has been added to alsa devices
 
  $ aplay -L
 
  $ aplay -L
  
6. Now play with aplay:
+
7. Now play with aplay:
 
  $ aplay -D btheadset /path/to/audio/file
 
  $ aplay -D btheadset /path/to/audio/file
 
+
 
 
or Mplayer:
 
or Mplayer:
 
  $ mplayer -ao alsa:device=btheadset /path/to/audio/or/video/file
 
  $ mplayer -ao alsa:device=btheadset /path/to/audio/or/video/file
Line 86: Line 93:
 
=== Headset's multimedia buttons ===
 
=== Headset's multimedia buttons ===
  
In order to get your bluetooth headset's multimedia buttons (play, pause, next, previous) working you need to add '''uinput''' to MODULES section in /etc/rc.conf:
+
In order to get your bluetooth headset's multimedia buttons (play, pause, next, previous) working you need to create {{ic|/etc/modprobe.d/uinput.conf}} containing {{ic|uinput}}.
MODULES=(fuse ipw2200 ... '''uinput''')
+
  
 
== PulseAudio method ==
 
== PulseAudio method ==
  
 
This one`s 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:
 
This one`s 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:
# pacman -S pulseaudio pulseaudio-alsa
+
{{Pkg|pulseaudio}} and {{Pkg|pulseaudio-alsa}}.
The latter package is the only one in the '''pulseaudio-gnome''' group, you could install that instead.
+
  
Now, to configure the audio output to use bluetooth, just install and run '''pavucontrol''' to configure the audio output:
+
Now, to configure the audio output to use bluetooth, just install {{Pkg|pavucontrol}} and run it to configure the audio output:
# pacman -S pavucontrol
+
 
  $ pavucontrol
 
  $ pavucontrol
  
That`s it!
+
See [[http://dev.funkynerd.com/knowledgebase/articles/5 this blog]] for futher explanations. Make sure to take a look at the [[PulseAudio]] wiki entry for setting up PulseAudio, especially if you are running KDE.
  
See [[http://www.funkynerd.com/using-a2dp-bluetooth-in-kubuntu-karmic this blog]] for futher explanations. 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'll 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.
  
 
== Switch between HSV and A2DP setting ==
 
== Switch between HSV and A2DP setting ==
Line 108: Line 123:
 
  pacmd set-card-profile 2 a2dp
 
  pacmd set-card-profile 2 a2dp
  
== Links ==
+
=== A2DP not working with pulseaudio ===
 +
 
 +
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
 +
 
 +
Disable=Socket
 +
 
 +
== Tested Headsets ==
 +
The following Bluetooth headsets have been tested with Arch Linux
 +
* Philips SHB9100 - Confirmed NOT TO WORK well. Have tried ''everything'' after a while they cut out. Pause and resume too is flakky and basically the whole wireless bluetooth experience is horrible. The following forum post[https://bbs.archlinux.org/viewtopic.php?pid=1315428#p1315428] explains an underlying issue and describes a temporary solution which can be used to improve the audio quality pending a proper fix.
 +
* Parrot Zik - Confirmed to work out of the box with firmware 1.04! The MIC however is detected, but does not work at all. Sometimes it can lag behind (not stutter) but most of the times it is not noticeable unless you playing a game, in which case I would switch to wired which resolves the issue.
 +
 
 +
== See also ==
 +
 
 
Alternative method of connecting a BT headset to Linux:
 
Alternative method of connecting a BT headset to Linux:
  
 
* [http://gablog.eu/online/node/80 GaBlog - Connect a bluetooth headset to linux]
 
* [http://gablog.eu/online/node/80 GaBlog - Connect a bluetooth headset to linux]
  
 +
Using the same device on Windows and Linux without pairing the device over and over again
  
See also:
+
* [http://ubuntuforums.org/showthread.php?p=9363229#post9363229 Dual booting with a bluetooth keyboard]
 
+
* [[Bluetooth]]
+

Revision as of 22:06, 16 September 2013

Template:Article summary start Template:Article summary text Template:Article summary heading Template:Article summary wiki Template:Article summary end Before you get started, you have to make sure that bluetooth is set up and working.

ALSA-BTSCO method

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 this blog (you need edit the script to work with gconftool-2). There's also a piece of equivalent bash script here.

The following method is out-of-date and obsoleted.

NOTE: This method is also outdated as with newer versions of BlueZ.

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.

Install btscoAUR.

To load the kernel module, type:

# modprobe snd-bt-sco

There will now be an extra audio device. Use 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 /dev/dspN as the audio device.

But to actually get any sound, you have to connect your headset to the computer first.

Connecting the headset

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

$ btsco -f <bdaddr>

for example

$ btsco -f 12:34:56:78:9A:BC

Pairing the headset with your computer

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.

There are two ways to pair your headset with the computer:

Using bluez-gnome

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.

Using passkey-agent

Before connecting to the headset, enter the command

$ passkey-agent --default <pin>

where <pin> is your headset's PIN. Then try to connect to the headset.

Headset and Alsa Devices

1. First if you have not already, install bluez from the official repositories. 2. Scan for your device

$ hcitool (-i <optional hci#>***) scan

3. Pair your headset with your device:

$ bluez-simple-agent (optional hci# ***) XX:XX:XX:XX:XX:XX
  and put in your pin (0000 or 1234, etc)

4. Make sure your /etc/bluetooth/audio.conf allows A2DP Audio Sinks. Place this line just bellow the [Genera] heading:

Enable=Source,Sink,Media,Socket

5. Add this to your /etc/asound.conf file:

#/etc/asound.conf

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

$ aplay -L

7. Now play with aplay:

$ aplay -D btheadset /path/to/audio/file

or Mplayer:

$ mplayer -ao alsa:device=btheadset /path/to/audio/or/video/file
      • To find hci# for a usb dongle, type in
$ hcitool dev

Headset's multimedia buttons

In order to get your bluetooth headset's multimedia buttons (play, pause, next, previous) working you need to create /etc/modprobe.d/uinput.conf containing uinput.

PulseAudio method

This one`s 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: pulseaudio and pulseaudio-alsa.

Now, to configure the audio output to use bluetooth, just install pavucontrol and run it to configure the audio output:

$ pavucontrol

See [this blog] for futher explanations. 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'll get "Audio sink fails". According to gentoo wiki, you have to verify than in /etc/bluetooth/audio.conf there is Enable=Socket under the [General] section heading.

Just do a # 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.

Switch between HSV and A2DP setting

This can easily be achieved by the following command where 2 needs to be changed with the correct device number.

pacmd set-card-profile 2 a2dp

A2DP not working with pulseaudio

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

Disable=Socket

Tested Headsets

The following Bluetooth headsets have been tested with Arch Linux

  • Philips SHB9100 - Confirmed NOT TO WORK well. Have tried everything after a while they cut out. Pause and resume too is flakky and basically the whole wireless bluetooth experience is horrible. The following forum post[1] explains an underlying issue and describes a temporary solution which can be used to improve the audio quality pending a proper fix.
  • Parrot Zik - Confirmed to work out of the box with firmware 1.04! The MIC however is detected, but does not work at all. Sometimes it can lag behind (not stutter) but most of the times it is not noticeable unless you playing a game, in which case I would switch to wired which resolves the issue.

See also

Alternative method of connecting a BT headset to Linux:

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