Difference between revisions of "Bluetooth (日本語)"

From ArchWiki
Jump to: navigation, search
(No difference)

Revision as of 14:42, 27 December 2013

zh-CN:Bluetooth Template:Related articles start (日本語)

  • Bluez4
  • Bluetooth マウス設定
  • Bluetooth ヘッドセット
  • </ul></div> Bluetooth は携帯電話やコンピュータなどの電子デバイス用の近距離無線通信規格です。Linux においては、Bluetooth プロトコルスタックの実装として BlueZ が標準的に使われています。


    公式リポジトリから Bluetooth プロトコルスタックの bluez とユーティリティ bluez-utils をインストールしてください。systemd によって自動的に起動される dbus デーモンが PIN ペアリングや設定の読み込みを行いますが、Bluetooth プロトコルを使うには bluetooth デーモンが必要です。

    bluetooth の systemd サービスを起動してください: # systemctl start bluetooth.

    Note: Some Bluetooth adapters are bundled with a Wi-Fi card (e.g. Intel Centrino). These require that the Wi-Fi card is first enabled (typically a keyboard shortcut on a laptop) in order to make the Bluetooth adapter visible to the kernel.

    CLI による設定


    Pairing a device from the shell is one of the most simplistic and reliable options. The exact procedure depends on the devices involved and their input functionality. What follows is a general outline of pairing a device using /usr/bin/bluetoothctl:

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

    • Turn the power to the controller on by entering power on. It is off by default.
    • Enter devices to get the MAC Address of the device with which to pair.
    • Enter device discovery mode with scan on command if device is not yet on the list.
    • Turn the agent on with agent on.
    • Enter pair MAC Address to do the pairing (tab completion works).
    • If using a device without a PIN, one may need to manually trust the device before it can reconnect successfully. Enter trust MAC Address to do so.
    • 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

    In order to have the device active after a reboot, a udev rule is needed: /etc/udev/rules.d/10-local.rules

    # Set bluetooth power up
    ACTION=="add", KERNEL=="hci0", RUN+="/usr/bin/hciconfig hci0 up"


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

    GNOME Bluetooth

    GNOME Bluetooth is a fork of the old bluez-gnome and is focused on integration with the GNOME desktop environment. The gnome-bluetooth package provides the back-end, gnome-shell provides the status monitor applet, and gnome-control-center provides the configuration front-end GUI that can be accessed by typing Bluetooth on the Activities overview, or with the gnome-control-center bluetooth command.

    Users who are not using GNOME Shell can install gnome-bluetooth-applet-gitAUR from AUR, which provides the old status monitor applet, and allows setup devices and transfer of files by clicking the Bluetooth icon. Just make sure that bluetooth-applet is autostarted with your session.

    You can also launch the following commands directly:

    • bluetooth-sendto: send files to a remote device
    • bluetooth-wizard: for new devices to be paired

    To add a Bluetooth entry to the SendTo menu in Thunar's file properties menu, see instructions here. (The command that needs to be configured is bluetooth-sendto %F)


    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. A Bluetooth icon should be visible in both Dolphin and in the system tray, from which users may configure BlueDevil and detect Bluetooth devices by clicking the icon. An interface is also available from the KDE System Settings.

    Obex を使ってファイルの送受信を行う

    Another option, rather than using KDE or Gnome Bluetooth packages, is ObexFS which allows for the mounting of phones which are treated like any other filesystem.

    Note: To use ObexFS, one needs a device that provides an ObexFTP service.

    Install obexfs and mount supported phones by running:

    $ obexfs -b devices_MAC_address /mountpoint

    For more mounting options see http://dev.zuckschwerdt.org/openobex/wiki/ObexFs

    For devices do not 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, one 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


    All examples have been moved to section bluez4. They need to be checked and fixed for use with bluez5. See section Bluez4 below.



    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 ドングル

    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 ドングル

    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 will not 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

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