Bluetooth

This article Article description::describes the configuration and usage of Bluetooth controllers and devices.

Prerequisites
This article assumes that udev and USB have been previously configured.

Kernel
In most cases enabling RFCOMM ( CONFIG_RFCOMM ), HIDP ( CONFIG_BT_HIDP ), HCI USB ( CONFIG_BT_HCIBTUSB ) and/or HCI UART ( CONFIG_BT_HCIUART ) should be sufficient. The User-space I/O driver for HID input devices ( CONFIG_UHID ) should be enabled for Bluetooth keyboards and mice.

Firmware
Most Bluetooth controllers need firmware to function. If the controller is supported by Linux, will usually indicate if firmware is needed. The package should provide the needed firmware, although some devices may need firmware that is only available from the manufacturer.

USE flags
BlueZ is an implementation of the Bluetooth protocol stack for Linux, and it is provided by the package.

Bluetooth support can be enabled system-wide by setting the USE variable to :

Emerge
The system needs to be updated if the USE variable was set to :

Install BlueZ:

Permissions
Permissions for Bluetooth devices will be handled automatically if the USE variable is set to, and ConsoleKit or systemd is being used.

Alternatively, adding a user to the group will allow that user to access Bluetooth devices:

OpenRC
Start bluetooth:

Start bluetooth at boot:

systemd
Start bluetooth:

Start bluetooth at boot:

Controller setup
Display controller information:

Where  is the name of the controller, and   (3rd line) indicates that the controller is enabled.

Enable the controller if indicates (with  ) (3rd line) that the controller is disabled:

In this case, query the state of the Bluetooth radio transmitter with :

can be installed with the package, or the >=-2.31 package.

Unblock the controller if indicates (with  ) that the controller is blocked:

If indicates (with  ) that the controller is blocked, unblock the controller by physical switch or keyboard function key.

Bluetooth controllers can be enabled automatically by setting  in :

In some instances Bluetooth controllers may have been soft-blocked by power management tools in udev. Make sure state is set to  in the corresponding rule file, or remove the following line entirely:

Device pairing
Bluetooth devices need to be paired with a Bluetooth controller before they can be used. This is done by entering a PIN (or other code) on both devices via an interaction agent. Certain devices such as headsets do not allow entering an arbitrary PIN. These devices use a static PIN, which is usually 0000, 1111, 1234 or 9999. There are also devices (e.g. Sony BD Remote Control) that do not require PIN entry, and attempting to enter a PIN when prompted will result in failure. Paring can be skipped with such devices.

This article only covers device pairing with, which is a command-line interaction agent provided by the package. If a graphical desktop environment is being used, device paring can be done with a graphical interaction agent. For KDE use, for GNOME use , and for GTK use or.

Start :

List the available controllers:

Display information about a controller:

Set the default controller:

Power on the controller:

Enable the agent and set it as default:

Set the controller as discoverable (temporarily for 3 minutes) and pairable:

Scan for devices:

Put the device into pairing mode. This generally involves pressing a button or a combinations of buttons, usually for several seconds.

Discover the device MAC address:

Pair with the device:

Enter the if prompted:

Allow the service authorization if requested:

Trust the device:

Connect to the device:

Display information about the device:

The device is now paired: