From ArchWiki
Revision as of 12:23, 16 October 2013 by TheCycoONE (talk | contribs) (Blueman: Fix note, should reference blueman here not bluedevil)
Jump to: navigation, search

zh-CN:Bluetooth Template:Article summary start Template:Article summary text Template:Article summary heading Template:Article summary wiki Template:Article summary end

Tango-view-refresh-red.pngThis article or section is out of date.Tango-view-refresh-red.png

Reason: Several generations of various deprecated tools are mentioned. bluez4 and bluez are confused. This article needs cleanup from someone who knows what commands belong in which packages. (Discuss in Talk:Bluetooth#)

Bluetooth is a standard for the short-range wireless interconnection of cellular phones, computers, and other electronic devices. In Linux, the canonical implementation of the Bluetooth protocol stack is BlueZ.


To use Bluetooth, install bluez from the official repositories. The dbus daemon, which is started automatically by systemd, is used to read settings and for PIN pairing, while the bluetooth daemon is required for the Bluetooth protocol.

Enable the bluetooth service to start it at system boot up.

Start the bluetooth systemd service.

Graphical front-ends

The following packages allow for a graphical interface to customize Bluetooth.


Note: As of 2013-10-16, blueman depends on the older bluez4, which conflicts with the current bluez (v5)

See Blueman article.

GNOME Bluetooth

GNOME Bluetooth is a fork of the old bluez-gnome and is focused on integration with the GNOME desktop environment. GNOME Bluetooth is required by gnome-shell, so you should already have it installed if you are running GNOME 3. Otherwise, it can be installed with the package gnome-bluetooth. Note that gnome-shell, gnome-bluetooth <= 3.8 depend upon bluez4. From gnome-shell 3.10 onwards, bluez will be supported. More information regarding the GNOME migration to bluez can be found here (June 2013 blog post).

Run bluetooth-applet for a nice Bluetooth applet. In newer versions, for this to work, you might need to install bluetooth-panel-applet-gitAUR. You should now be able to setup devices and send files by right-clicking the Bluetooth icon. To make the applet run on login, add it to System > Preferences > Startup Applications.

To add a Bluetooth entry to the SendTo menu in Thunar's file properties menu, see instructions here.


Note: As of 2013-09-01, bluedevil depends on the older bluez4, which conflicts with the current bluez (v5). Additionally, bluedevil-gitAUR is not updated to fix this dependency.

The Bluetooth tool for KDE is BlueDevil. It can be installed with the package bluedevil, available in the official repositories.

Make sure bluetooth daemon is running, as described above. You should get a Bluetooth icon both in Dolphin and in the system tray, from which you can configure BlueDevil and detect Bluetooth devices by clicking the icon. You can also configure BlueDevil from the KDE System Settings

Fluxbox, Openbox, other WM

Of course you can still use the preceding applications even if GNOME, Xfce or KDE are not your desktop manager. This list should help you figuring out which application does what:

  • bluetooth-applet -- tray icon with access to settings, pairing wizard, management of known devices
  • /usr/lib/gnome-user-share/gnome-user-share -- needs to be running if you're about to receive files via obexBT from a paired/bonded device

if you're receiving an error during transmission and/or there's no file received add this into


 <policy user="your_user_id">
   <allow own="org.bluez"/>
   <allow send_destination="org.bluez"/>
   <allow send_interface="org.bluez.Agent"/>
  • bluetooth-wizard - for new devices to be paired
  • bluetooth-properties - accessible also via bluetooth-applet icon
  • gnome-file-share-properties - permissions on receiving files via Bluetooth
  • bluez-sendto - GUI for sending files to a remote device

Bluez Utils

The package bluez-utils contains various commands useful to configure and troubleshoot Bluetooth from the command line.


Print name and basic information about all the Bluetooth devices installed in the system:

# hciconfig
 hci0:   Type: BR/EDR  Bus: USB
       BD Address: 90:4C:E5:DB:E9:77  ACL MTU: 1021:8  SCO MTU: 64:1
       RX bytes:484 acl:0 sco:0 events:20 errors:0
       TX bytes:323 acl:0 sco:0 commands:20 errors:0

hciconfig is part of the bluez-utils package.

To activate a device, use:

# hciconfig device-name up


To scan for remote devices:

$ hcitool scan


Many Bluetooth devices require {{Wikipedia:Bluetooth#Pairing|pairing}}. The exact procedure depends on the devices involved and their input functionality.

With bluez5

Start the bluetoothctl interactive command. There you can input help to get a list of available commands.

  • Enter devices to get the MAC Address of the device with which you want to pair.
  • Enter device discovery mode with scan on command if device is not yet on the list
  • Enter pair MAC Address to do the pairing.
  • Finally, use connect MAC_address to establish a connection.

An example session may look this way:

# bluetoothctl 
[NEW] Controller 00:10:20:30:40:50 pi [default]
[bluetooth]# agent KeyboardOnly 
Agent registered
[bluetooth]# default-agent 
Default agent request successful
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:10:20:30:40:50 Discovering: yes
[NEW] Device 00:12:34:56:78:90 myLino
[CHG] Device 00:12:34:56:78:90 LegacyPairing: yes
[bluetooth]# pair 00:12:34:56:78:90
Attempting to pair with 00:12:34:56:78:90
[CHG] Device 00:12:34:56:78:90 Connected: yes
[CHG] Device 00:12:34:56:78:90 Connected: no
[CHG] Device 00:12:34:56:78:90 Connected: yes
Request PIN code
[agent] Enter PIN code: 1234
[CHG] Device 00:12:34:56:78:90 Paired: yes
Pairing successful
[CHG] Device 00:12:34:56:78:90 Connected: no

With bluez4

The procedure on a mobile may be as follows:

  • The computer sends a connect request to the mobile.
  • A pin, determined by the computer, is prompted for at the mobile
  • The same key must be re-entered at the computer.

To pair with a device without using the gnome-bluez package, the bluez-simple-agent utility that comes with the bluez package can be used. This utility depends on three packages from the official repositories: python2-dbus python2-gobject dbus-glib.

First, scan for external devices:

$ hcitool scan

Run the script as root:

# bluez-simple-agent

The message "Agent registered" should be returned, press Ctrl+c to quit.

Below is a basic example of pairing with a specific device. The script will ask for the passcode, enter the code and confirm with enter.

# bluez-simple-agent hci0 00:11:22:33:AA:BB
Note: bluez-simple-agent is only needed once for pairing a device, not every time you want to connect.

See the Examples section below for pairing examples with various devices.

Using Obex for sending and receiving files

Another option, rather than using KDE or Gnome Bluetooth packages, is ObexFS which allows you to mount your phone and treat it as part of your filesystem. Note that to use ObexFS, you need a device that provides an ObexFTP service.

Install obexfs and then your phone can then be mounted by running

$ obexfs -b devices_MAC_address /mountpoint

For more mounting options see

For devices don't support Obex FTP service, check if Obex Object Push is supported.

# sdptool browse XX:XX:XX:XX:XX:XX

Read the output, look for Obex Object Push, remember the channel for this service. If supported, you can use ussp-push to send files to this device:

# ussp-push XX:XX:XX:XX:XX:XX@CHANNEL file wanted_file_name_on_phone


Siemens S55

This is what I did to connect to my S55. (I have not figured out how to initiate the connection from the phone)

  • The steps under installation
$ hcitool scan
Scanning ...

Start the simple-agent in a second terminal:

$ su -c bluez-simple-agent
Agent registered

Back to the first console:

$ obexftp -b $B -l "Address book"
# Phone ask for pin, I enter it and answer yes when asked if I want to save the device
<file name="5F07.adr" size="78712" modified="20030101T001858" user-perm="WD" group-perm="" />
$ obexftp -b 00:01:E3:6B:FF:D7 -g "Address book/5F07.adr"
Browsing 00:01:E3:6B:FF:D7 ...
Channel: 5
Receiving "Address book/5F07.adr"... Sending "Address book"... done
$ obexftp -b 00:01:E3:6B:FF:D7 -p a
Sending "a"... done

Logitech mouse MX Laser / M555b

To quickly test the connection:

$ hidd --connect XX:XX:XX:XX:XX:XX

For automated reconnection, use your desktop wizard to configure the bluetooth mouse. If your desktop environment doesn't includes support for this task, see the Bluetooth mouse manual configuration guide.

Motorola V900

After installing Blueman and running blueman-applet, click "find me" under connections > bluetooth in Motorola device. In blueman-applet, scan devices, find the Motorola, click "add". Click "bond" in blueman-applet, enter some PIN, enter the same PIN in Motorola when it asks. In terminal:

$ mkdir ~/bluetooth-temp
$ obexfs -n XX:XX:XX:XX:XX:XX ~/bluetooth-temp
$ cd ~/bluetooth-temp

and browse... Only audio, video, and pictures are available when you do this.

Motorola RAZ

Install obextool obexfs obexftp openobex bluez.

# lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 03f0:171d Hewlett-Packard Wireless (Bluetooth + WLAN) Interface [Integrated Module]
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
# hciconfig hci0 up
# hciconfig
hci0:   Type: BR/EDR  Bus: USB
        BD Address: 00:16:41:97:BA:5E  ACL MTU: 1017:8  SCO MTU: 64:8
        UP RUNNING
        RX bytes:348 acl:0 sco:0 events:11 errors:0
        TX bytes:38 acl:0 sco:0 commands:11 errors:0
# hcitool dev
        hci0    00:16:41:97:BA:5E

Make sure that bluetooth on your phone is enabled and your phone is visible!

# hcitool scan
Scanning ...
        00:1A:1B:82:9B:6D       [quirxi]
# hcitool inq
Inquiring ...
        00:1A:1B:82:9B:6D       clock offset: 0x1ee4    class: 0x522204
# l2ping 00:1A:1B:82:9B:6D
Ping: 00:1A:1B:82:9B:6D from 00:16:41:97:BA:5E (data size 44) ...
44 bytes from 00:1A:1B:82:9B:6D id 0 time 23.94ms
44 bytes from 00:1A:1B:82:9B:6D id 1 time 18.85ms
44 bytes from 00:1A:1B:82:9B:6D id 2 time 30.88ms
44 bytes from 00:1A:1B:82:9B:6D id 3 time 18.88ms
44 bytes from 00:1A:1B:82:9B:6D id 4 time 17.88ms
44 bytes from 00:1A:1B:82:9B:6D id 5 time 17.88ms
6 sent, 6 received, 0% loss
# hcitool name 00:1A:1B:82:9B:6D
# hciconfig -a hci0
hci0:   Type: BR/EDR  Bus: USB
        BD Address: 00:16:41:97:BA:5E  ACL MTU: 1017:8  SCO MTU: 64:8
        UP RUNNING
        RX bytes:9740 acl:122 sco:0 events:170 errors:0
        TX bytes:2920 acl:125 sco:0 commands:53 errors:0
        Features: 0xff 0xff 0x8d 0xfe 0x9b 0xf9 0x00 0x80
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy:
        Link mode: SLAVE ACCEPT
        Name: 'BCM2045'
        Class: 0x000000
        Service Classes: Unspecified
        Device Class: Miscellaneous,
        HCI Version: 2.0 (0x3)  Revision: 0x204a
        LMP Version: 2.0 (0x3)  Subversion: 0x4176
        Manufacturer: Broadcoml / Corporation (15)
# hcitool info 00:1A:1B:82:9B:6D
Requesting information ...
        BD Address:  00:1A:1B:82:9B:6D
        Device Name: [quirxi]
        LMP Version: 1.2 (0x2) LMP Subversion: 0x309
        Manufacturer: Broadcom Corporation (15)
        Features: 0xff 0xfe 0x0d 0x00 0x08 0x08 0x00 0x00
                <3-slot packets> <5-slot packets> <encryption> <slot offset>
                <timing accuracy> <role switch> <hold mode> <sniff mode>
                <RSSI> <channel quality> <SCO link> <HV2 packets>
                <HV3 packets> <A-law log> <CVSD> <power control>
                <transparent SCO> <AFH cap. slave> <AFH cap. master>

Edit your /etc/bluetooth/main.conf and enter the proper class for your phone ( Class = 0x100100 ):

# Default device class. Only the major and minor device class bits are
# considered.
#Class = 0x000100
Class =  0x100100
# systemctl start bluetooth
 :: Stopping bluetooth subsystem:  pand dund rfcomm hidd  bluetoothd
 :: Starting bluetooth subsystem:  bluetoothd

Pairing with bluez-simple-agent only has to be done once. On your Motorola phone give 0000 in as your PIN when phone asks for it!

/usr/bin/bluez-simple-agent hci0 00:1A:1B:82:9B:6D
RequestPinCode (/org/bluez/10768/hci0/dev_00_1A_1B_82_9B_6D)
Enter PIN Code: 0000
New device (/org/bluez/10768/hci0/dev_00_1A_1B_82_9B_6D)

Now you can browse the filesystem of your phone with obexftp:

obexftp -v -b 00:1A:1B:82:9B:6D -B 9 -l
Tried to connect for 448ms
Receiving "(null)"...-<?xml version="1.0" ?>
<!DOCTYPE folder-listing SYSTEM "obex-folder-listing.dtd">
<parent-folder />
<folder name="audio" size="0" type="folder" modified="20101010T132323Z" user-perm="RW" />
<folder name="video" size="0" type="folder" modified="20101010T132323Z" user-perm="RW" />
<folder name="picture" size="0" type="folder" modified="20101010T132323Z" user-perm="RW" />

Or you can mount your phone into a directory on your computer and treat it like a normal file system:

# groupadd bluetooth
# mkdir /mnt/bluetooth
# chown root:bluetooth /mnt/bluetooth
# chmod 775 /mnt/bluetooth
# usermod -a -G bluetooth arno
# obexfs -b 00:1A:1B:82:9B:6D /mnt/bluetooth/

Pairing with an iPhone using bluez-simple-agent

Assuming a bluetooth device called hci0 and an iPhone that showed up in a hcitool scan as '00:00:DE:AD:BE:EF':

# bluez-simple-agent hci0 00:00:DE:AD:BE:EF

Headset and ALSA devices

by referencing the bluetooth device in asound.conf

1. Scan for your device:

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

2. 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)

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

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

4. Check to see if it has been added to ALSA devices

$ aplay -L

5. 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

by using bluez-tools from the AUR

You can use bluez-toolsAUR from the AUR with PulseAudio to stream audio to a bluetooth headset. Find the MAC of the headset:

$ hcitool scan

Connect to the headset:

$ bt-audio -c XX:XX:XX:XX:XX:XX

Open pulseaudio volume control:

$ pavucontrol

The headset should show up in the Configuration tab.

Microsoft Bluetooth Mobile Keyboard 6000

1. Scan for your device

$ hcitool (-i optional_hci#***) scan
Scanning ...
       00:11:22:33:44:55       Microsoft Bluetooth Mobile Keyboard 6000

2. On second console run as root (do not terminate):

# bluez-simple-agent
Agent registered

3. Back on first console run:

$ bluez-simple-agent hci0 00:11:22:33:44:55
Enter PIN Code: 1234
(now enter that PIN on the keyboard and press enter)
New device (/org/bluez/5373/hci0/dev_00_11_22_33_44_55)


$ bluez-test-device trusted 00:11:22:33:44:55


$ bluez-test-input connect 00:11:22:33:44:55

No your keyboard should work. You can terminate bluez-simple-agent on second console with Ctrl+C



$ passkey-agent --default 1234
Can't register passkey agent
The name org.bluez was not provided by any .service files


$ hciconfig dev
# (no listing)

Try running hciconfig hc0 up


If you see this when trying to enable receiving files in bluetooth-properties:

Bluetooth OBEX start failed: Invalid path
Bluetooth FTP start failed: Invalid path

Then install xdg-user-dirs and issue:

$ xdg-user-dirs-update

You can edit the paths using:

$ vi ~/.config/user-dirs.dirs

Bluetooth USB Dongle

If you are using a USB dongle, you should check that your Bluetooth dongle is recognized. You can do that by inspecting /var/log/messages.log when plugging in the USB dongle (or running journalctl -f with systemd). It should look something like the following (look out for hci):

Feb 20 15:00:24 hostname kernel: [ 2661.349823] usb 4-1: new full-speed USB device number 3 using uhci_hcd
Feb 20 15:00:24 hostname bluetoothd[4568]: HCI dev 0 registered
Feb 20 15:00:24 hostname bluetoothd[4568]: Listening for HCI events on hci0
Feb 20 15:00:25 hostname bluetoothd[4568]: HCI dev 0 up
Feb 20 15:00:25 hostname bluetoothd[4568]: Adapter /org/bluez/4568/hci0 has been enabled

For a list of supported hardware please refer to the Resource section on this page.

If you only get the first two lines, you may see that it found the device but you need to bring it up. Example:

hciconfig -a hci0
hci0:	Type: USB
	BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
	RX bytes:0 acl:0 sco:0 events:0 errors:0
        TX bytes:0 acl:0 sco:0 commands:0 errors:
# hciconfig hci0 up
hciconfig -a hci0
hci0:	Type: USB
	BD Address: 00:02:72:C4:7C:06 ACL MTU: 377:10 SCO MTU: 64:8
	RX bytes:348 acl:0 sco:0 events:11 errors:0
        TX bytes:38 acl:0 sco:0 commands:11 errors:0

If this fails with an error like:

Operation not possible due to RF-kill

it could be due either to the rfkill utility, in which case it should be resolved with

# rfkill unblock all

or, it could simply be the hardware switch of the computer. The hardware bluetooth switch (at least sometimes) controls access to USB bluetooth dongles also. Flip/press this switch and try bringing the device up again.

To verify that the device was detected you can use hcitool which is part of the bluez-utils. You can get a list of available devices and their identifiers and their MAC address by issuing:

$ hcitool dev
        hci0	00:1B:DC:0F:DB:40

More detailed informations about the device can be retrieved by using hciconfig.

$ hciconfig -a hci0
hci0:   Type: USB
        BD Address: 00:1B:DC:0F:DB:40 ACL MTU: 310:10 SCO MTU: 64:8
        RX bytes:1226 acl:0 sco:0 events:27 errors:0
        TX bytes:351 acl:0 sco:0 commands:26 errors:0
        Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT 
        Name: 'BlueZ (0)'
        Class: 0x000100
        Service Classes: Unspecified
        Device Class: Computer, Uncategorized
        HCI Ver: 2.0 (0x3) HCI Rev: 0xc5c LMP Ver: 2.0 (0x3) LMP Subver: 0xc5c
        Manufacturer: Cambridge Silicon Radio (10)

Logitech Bluetooth USB Dongle

There are Logitech dongles (ex. Logitech MX5000) that can work in two modes Embedded and HCI. In embedded mode dongle emulates a USB device so it seems to your PC that your using a normal USB mouse/keyoard.

If you hold the little red Button on the USB BT mini-receiver it will enable the other mode. Hold the red button on the BT dongle and plug it into the computer, and after 3-5 seconds of holding the button, the Bluetooth icon will appear in the system tray. Discussion

hcitool scan: Device not found

  • On some Dell laptops (e.g. Studio 15) you have to switch the Bluetooth mode from HID to HCI using
# hid2hci
Note: hid2hci is no longer in the $PATH, it is under /lib/udev/hid2hci, but udev should run it automatically for you.
  • If the device won't show up and you have a Windows operating system on your machine, try booting it and enable the bluetooth adapter from windows.
  • Sometimes also this simple command helps:
# hciconfig hci0 up

rfkill unblock: Do not unblock

If your device still soft blocked and you run connman.

Try this: $ connmanctl enable bluetooth

My computer is not visible

Can't discover computer from your phone? Enable PSCAN and ISCAN:

# enable PSCAN and ISCAN
$ hciconfig hci0 piscan 
# check it worked
$ hciconfig
hci0:   Type: USB
        BD Address: 00:12:34:56:78:9A ACL MTU: 192:8 SCO MTU: 64:8
        RX bytes:20425 acl:115 sco:0 events:526 errors:0
        TX bytes:5543 acl:84 sco:0 commands:340 errors:0
Note: Check DiscoverableTimeout and PairableTimeout in /etc/bluetooth/main.conf

Try changing device class in /etc/bluetooth/main.conf as following:

# Default device class. Only the major and minor device class bits are
# considered.
#Class = 0x000100 (from default config)
Class = 0x100100

This was the only solution to make my computer visible for my phone.

Nautilus cannot browse files

If nautilus doesn't open and show this error:

Nautilus cannot handle obex: locations. Couldn't display "obex://[XX:XX:XX:XX:XX:XX]/".

Install gvfs-obexftp package.

Sennheiser MM400 headset connection problems

If your Sennheiser MM400 Headset immediately disconnects after connecting as Headset Service with Blueman, try to connect it as Audio Sink. Afterwards you can change the headset's Audio Profile to Telephony Duplex with a right click in Blueman. With this option headset functionality will be available although the headset was only connected as Audio Sink in first place and no disconnection will happen (tested with bluez 4.96-3, pulseaudio 1.1-1 and blueman 1.23-2).

My device is paired but no sound is played from it

Try to first inspect /var/log/messages.log. If you see such messages:

Jan 12 20:08:58 localhost pulseaudio[1584]: [pulseaudio] module-bluetooth-device.c: Service not connected
Jan 12 20:08:58 localhost pulseaudio[1584]: [pulseaudio] module-bluetooth-device.c: Bluetooth audio service not available

try first:

# pactl load-module module-bluetooth-device

If the module fails to work, do this workaround: Open /etc/bluetooth/audio.conf and add after [General] (on a new line)


Then restart the bluetooth daemon. Pair again your device, and you should find it in the pulseaudio settings (advanced settings for the sound)

More information on Gentoo Wiki

If after fixing this you still can't get sound, try using blueman (this is the only one that works for me), make sure that notify-osd is installed or it might show you weird error messages like this one: "Stream setup failed"

fail (/usr/lib/python2.7/site-packages/blueman/gui/manager/
fail (DBusException(dbus.String(u'Stream setup failed'),),)

See also