Bluetooth ヘッドセット
現在、Arch Linux のデフォルト環境ではリモートオーディオ再生の A2DP プロファイル (Audio Sink) をサポートしています。
目次
Bluez5/PulseAudio
PulseAudio 5.x はデフォルトで A2DP をサポートしています。以下のパッケージをインストールしてください: pulseaudio-alsa, pulseaudio-bluetooth, bluez, bluez-libs, bluez-utils, bluez-firmware。pulseaudio-bluetooth がないとペアリングした後に接続することができなくなります。エラーメッセージは表示されません。
Bluetooth システムを起動:
# systemctl start bluetooth
bluetoothctl コマンドラインユーティリティを使うことでペアリングと接続が行えます。bluetoothctl に関する詳細やトラブルシューティングは Bluetooth の記事を見てください。次のコマンドを実行することでコマンドプロンプトを開きます:
# bluetoothctl
そして以下を入力:
# power on # agent on # default-agent # scan on
ヘッドセットをペアリングモードにします。ヘッドセットは簡単に確認できます。例えば:
[NEW] Device 00:1D:43:6D:03:26 Lasmex LBT10
上記の場合、デバイスの名前は "Lasmex LBT10" で MAC アドレスは 00:1D:43:6D:03:26 です。この MAC アドレスを使ってペアリングを開始します:
# pair 00:1D:43:6D:03:26
ペアリングが完了したら、デバイスを明示的に接続する必要があります (every time?):
# connect 00:1D:43:6D:03:26
全てが上手くいけば、PulseAudio にアウトプットデバイスが新しく作られます。
pavucontrol の "Playback" や "Recording" タブを使うことでデバイスに音声を転送することができます。
スキャンを無効化してプログラムを終了:
# scan off # exit
トラブルシューティング
Many users report frustration with getting A2DP/Bluetooth Headsets to work.
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.
AuthenticationFailed でペアリングが失敗する
ペアリングが失敗する場合、次のコマンドで SSPMode を無効化 してみてください:
# hciconfig hci0 sspmode 0
ペアリングは成功するが、接続が失敗する
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
以下のようなコマンドを使ってログを確認してみてください:
# systemctl status bluetooth # journalctl -n 20
以下のようなメッセージが確認できる場合:
bluetoothd[5556]: a2dp-sink profile connect failed for 00:1D:43:6D:03:26: Protocol not available
おそらく pulseaudio-bluetooth パッケージがインストールされていないのが原因です。インストールしたら、pulseaudio を再起動してください。
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
To have your headset auto connect you need to enable PulseAudio's switch-on-connect module. Add the following:
/etc/pulse/default.pa
# automatically switch to newly-connected devices load-module module-switch-on-connect
You then need to tell bluetoothctl to trust your Bluetooth headset, or you will see errors like this:
bluetoothd[487]: Authentication attempt without agent bluetoothd[487]: Access denied: org.bluez.Error.Rejected
[bluetooth]# trust 00:1D:43:6D:03:26
After a reboot, your Bluetooth adapter will not power on by default. You need to add a udev rule to power it on:
/etc/udev/rules.d/10-local.rules
# Set bluetooth power up ACTION=="add", SUBSYSTEM=="bluetooth", KERNEL=="hci[0-9]*", RUN+="/usr/bin/hciconfig %k up"
接続は成功するが、音が聞こえない
システムログに以下のメッセージが記録されてないか確認してください:
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.
GDM を使っている場合、PulseAudio のインスタンスが起動して、bluetooth デバイスの接続を奪っている可能性があります。設定ファイルを作成・編集することで問題は解決します:
/var/lib/gdm/.pulse/client.conf
autospawn = no daemon-binary = /bin/true
上記のファイルを作るときは chown を使ってパーミッションを gdm:gdm に設定してください。再起動すれば問題が解決されます。
UUIDs has unsupported type
ペアリング中に bluetoothctl で以下のような出力がされることがあります:
[CHG] Device 00:1D:43:6D:03:26 UUIDs has unsupported type
このメッセージは無視してかまいません。
旧式の方法: ALSA-BTSCO
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 is also a piece of equivalent bash script here.
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.
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.
ヘッドセットを接続
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
ヘッドセットとコンピュータをペアリング
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:
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.
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.
ヘッドセットと ALSA デバイス
1. まず公式リポジトリから bluez をインストールしてください。
2. デバイスをスキャン。
$ 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 [General] 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
ヘッドセットのマルチメディアボタン
In order to get your bluetooth headset's multimedia buttons (play, pause, next, previous) working you need to create /etc/modules-load.d/uinput.conf containing uinput.
旧式の方法: PulseAudio
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: 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
Make sure to take a look at the PulseAudio wiki entry for setting up PulseAudio, especially if you are running KDE.
トラブルシューティング
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 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.
旧式のドキュメント: ALSA, bluez5, PulseAudio の方法
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)
ソフトウェアパッケージのインストール
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.
ALSA と関連ライブラリのインストール
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.
Bluez5 のインストール
Bluez5 is the latest Bluetooth stack. It is required for PulseAudio to interface with wireless headsets. Required packages: bluez, bluez-utils, bluez-libs.
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:
# systemctl start bluetooth
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>
テスト済みのアプリケーション
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.
HSV と A2DP の設定の切り替え
以下のコマンドを実行することで簡単に切り替えられます (2 は適切なデバイス番号に置き換えて下さい):
pacmd set-card-profile 2 a2dp_sink
PulseAudio で A2DP が動作しない
bluez 4.1+ と PulseAudio 3.0+ を使っていて、PulseAudio でプロファイルを A2DP に切り替えられない場合、/etc/bluetooth/audio.conf を編集して Enable=Socket という行を削除して Disable=Socket という行を追加することで Socket インターフェイスを無効化できます。
テスト済みのヘッドセット
| 機種 | バージョン | コメント | 対応状況 |
|---|---|---|---|
| Philips SHB9150 | bluez5, pulseaudio 5 | 停止・再生が動作せず。mpv や Banshee では停止ボタンを押すと音声出力は停止するがプレイヤーは停止せず。 | Limited |
| Philips SHB9100 | 停止・再生がおかしい。音質を改善する一時的な方法は [1] を参照。 | Limited | |
| Philips SHB7000 | 停止・再生がおかしい。 | Limited | |
| Philips SHB5500BK/00 | bluez 5.28, PulseAudio 6.0 | 停止・再生が機能せず。 | Limited |
| Parrot Zik | ファームウェア 1.04。マイクは検出されるが、動作せず。ときどき遅延が発生 (スタッタはなし)。基本的に、ゲームを遊んだりするのでなければ問題なし。ゲームを遊ぶときは有線に切り替えることを推奨。 | Limited | |
| Sony DR-BT50 | bluez{4,5} | a2dp で動作。[2] を参照。アダプタ: D-Link DBT-120 USB ドングル。 | Yes |
| Sony SBH50 | bluez5 | a2dp で動作。アダプタ: Broadcom Bluetooth 2.1 Device (Vendor=0a5c ProdID=219b Rev=03.43)。btusb モジュールが必要。
|
Yes |
| Sony MDR-XB950BT | pulseaudio | a2dp でテスト済み。アダプタ: Grand-X BT40G。自動で接続されない場合、手動で接続する必要があります。他の機能は問題なく動作。 | Limited |
| Sony MUC-M1BT1 | bluez5, pulseaudio-gitAUR | A2DP & HSP/HFP どちらも問題なく動作。 | Yes |
| SoundBot SB220 | bluez5, pulseaudio-gitAUR | Yes | |
| Auna Air 300 | bluez5, pulseaudio-git | 何らかの理由で、再起動が必要ですが、それで問題なく起動します。 | 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 ボタンは何も設定しなくても動作しますが、Play/Pause ボタンは動作しません。 | Yes |
| Audionic BlueBeats (B-777) | bluez5, pulseaudio 4.0-6 | Yes | |
| Logitech Wireless Headset | bluez 5.14, pulseaudio-git | 製造番号 PN 981-000381。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 で動作、HDP は問題あり。 | Yes |
| Philips AEA2000/12 | bluez5 | Yes | |
| Nokia BH-104 | bluez4 | Yes | |
| Creative AirwaveHD | bluez 5.23 | Bluetooth アダプタ 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 | アダプタ: CSL - USB nano Bluetooth-Adapter V4.0。a2dp プロファイルでテスト。マイクは未テスト。(ペアリングしても) 自動接続は行われないため、手動で接続する必要あり。再生/停止ボタンを押すとヘッドフォンがミュート/アンミュートになるが、再生には影響なし。次に進む/前に戻るボタンは動作せず (xev で変化なし)。 | 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 | A2DP プロファイルで何も設定しなくても動作。 | Yes |
| Beats Studio Wireless | bluez 5.28, pulseaudio 6.0 | 何も設定しなくても動作。マルチメディアボタンは未テスト。 | Yes |
| AKG Y45BT | bluez 5.30, pulseaudio 6.0 | 停止・再生が動作せず。/etc/bluetooth/audio.conf に Enable=Socket を、/etc/pulse/default.pa に load-module module-bluetooth-discover を設定する必要あり。
|
Yes |
| Bluedio Turbine | bluez5, pulseaudio 6.0 | HSP/HFP で動作、A2DP は未テスト。 | Yes |
| Sony SBH20 | bluez 5.30, pulseaudio 6.0 | A2DP プロファイルで問題なく動作。 | Yes |
| Nokia BH-111 | bluez 5.30, pulseaudio 6.0 | HSP/HFP と A2DP どちらでも動作。ボタンは特定のアプリで動作。 | Yes |
| Sony MDR-ZX330BT | bluez 5.31, pulseaudio 6.0 | 何も設定しなくても動作 (HSP/HFP と A2DP)。ボタンは特定のアプリで動作。 | Yes |
参照
Using the same device on Windows and Linux without pairing the device over and over again