Difference between revisions of "Bluez4"

From ArchWiki
Jump to: navigation, search
m (by referencing the bluetooth device in asound.conf)
(archive obsoleted page)
(12 intermediate revisions by 6 users not shown)
Line 1: Line 1:
#REDIRECT: [[ArchWiki:Archive]]
{{Related articles start}}
{{Related|Bluetooth Mouse}}
{{Related|Bluetooth mouse configuration}}
{{Related|Bluetooth Headset}}
{{Related articles end}}
Bluez4 is a now obsolete version of the Linux bluetooth stack. Information on the current version of the bluetooth stack, Bluez5, can be found in the [[Bluetooth]] article.
== Installation ==
{{warning|Bluez4 has been deprecated. It is highly recommended that users install {{pkg|bluez}} version 5 instead.}}
Bluez4 can be installed from the {{AUR|bluez4}} package in the AUR. Ensure that the bluetooth daemon is started:
# systemctl start bluetooth
To enable the daemon at boot use the command:
# systemctl enable bluetooth
== Pairing 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: {{Pkg|python2-dbus}} {{Pkg|python2-gobject}} {{Pkg|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 {{ic|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.
== Bluez4 examples ==
=== Siemens S55 ===
{{note|It has not yet been determined whether the connection can be initiated from the phone.}}
* The steps under installation
{{hc|$ hcitool scan|
Scanning ...
        ''XX:XX:XX:XX:XX:XX''  NAME
Start the simple-agent in a second terminal:
{{hc|$ su -c bluez-simple-agent|
Agent registered
Back to the first console:
{{hc|$ obexftp -b $B -l "Address book"|<nowiki>
# 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="" />
{{hc|$ 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
{{hc|$ obexftp -b 00:01:E3:6B:FF:D7 -p a|
Sending "a"... done
=== 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 ===
{{merge|Bluetooth|I see that the example recommends {{pkg|bluez}} version 5. Is this example relevant to Bluez4 or Bluez5? If the example works with Bluez5 then it should be removed from this article and moved to the examples section of the [[Bluetooth]] article. This article should only contain content that is relevant only to Bluez4.}}
Install {{Pkg|obextool}} {{Pkg|obexfs}} {{Pkg|obexftp}} {{Pkg|openobex}} {{Pkg|bluez}}.
{{hc|# 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
{{hc|# 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
{{hc|# hcitool dev|
        hci0    00:16:41:97:BA:5E
Make sure that bluetooth on your phone is enabled and your phone is visible!
{{hc|# hcitool scan|
Scanning ...
        00:1A:1B:82:9B:6D      [quirxi]
{{hc|# hcitool inq|
Inquiring ...
        00:1A:1B:82:9B:6D      clock offset: 0x1ee4    class: 0x522204
{{hc|# 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
{{hc|# hcitool name 00:1A:1B:82:9B:6D|
{{hc|# 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)
{{hc|# 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 {{ic|/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
{{hc|# 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!
{{hc|/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:
{{hc|obexftp -v -b 00:1A:1B:82:9B:6D -B 9 -l|<nowiki>
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':
{{hc|# bluez-simple-agent hci0 00:00:DE:AD:BE:EF|
=== 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 configuration]] article.
=== Headset and ALSA devices ===
==== 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 {{ic|/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
==== Using bluez-tools from the AUR ====
You can use {{AUR|bluez-tools}} 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
{{hc|$ 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):
{{hc|# bluez-simple-agent|
Agent registered
3. Back on first console run:
{{hc|$ 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 {{ic|Ctrl+C}}
== Bluez4 - Troubleshooting ==
=== passkey-agent ===
{{hc|$ 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 {{ic|hciconfig hc0 up}}
=== Sennheiser MM400 headset connection problems ===
If your {{ic|Sennheiser MM400 Headset}} immediately disconnects after connecting as {{ic|Headset Service}} with Blueman, try to connect it as {{ic|Audio Sink}}. Afterwards you can change the headset's {{ic|Audio Profile}} to {{ic|Telephony Duplex}} with a right click in Blueman.
With this option headset functionality will be available although the headset was only connected as {{ic|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 {{ic|/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 {{ic|/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)
[http://wiki.gentoo.org/index.php?title=Bluetooth_Headset&redirect=no 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/ManagerDeviceMenu.py:134)
fail (DBusException(dbus.String(u'Stream setup failed'),),)
== See also ==
* [http://www.gentoo.org/doc/en/bluetooth-guide.xml Gentoo Linux Bluetooth guide]
* [http://en.opensuse.org/HCL:Bluetooth openSUSE Bluetooth hardware compatibility list]
* [http://linuxgazette.net/109/oregan3.html Accessing a Bluetooth phone (Linux Gazette)]
* [http://www.adamish.com/blog/#a000361 Bluetooth computer visibility]
* [http://www.elstel.org/MobilePhone.html Bluetooth for your mobile phone: Bluetooth pairing, data synchronization, photo download, Internet Dial-Up (tethering)]
* [http://www.elstel.org/MobilePhone.html Bluetooth pairing and applications for synchronizing phone numbers, SMS-messages, phone call entries, your calendar and time; tethering]

Latest revision as of 12:42, 8 September 2016

Redirect to: