Enable Bluetooth Radio and Try Again

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.

Installation

Install the bluez package, providing the Bluetooth protocol stack.
Install the bluez-utils package, providing the bluetoothctl utility. Alternatively install bluez-utils-compat ^AUR to additionally have the deprecated BlueZ tools.
The generic Bluetooth driver is the btusb kernel module. Check whether that module is loaded. If it is not, then load the module.
Get-go/enable bluetooth.service.

Note:

Past default the Bluetooth daemon will only give out bnep0 devices to users that are a member of the lp group. Make certain to add together your user to that grouping if you intend to connect to a Bluetooth tether. You can change the grouping that is required in the file /usr/share/dbus-1/system.d/bluetooth.conf.
Some Bluetooth adapters are bundled with a Wi-Fi bill of fare (due east.k. Intel Centrino). These require that the Wi-Fi card is firstly enabled (typically a keyboard shortcut on a laptop) in guild to brand the Bluetooth adapter visible to the kernel.
Some Bluetooth cards (eastward.g. Broadcom) conflict with the network adapter. Thus, you demand to make sure that your Bluetooth device gets connected earlier the network service kicking.
Some tools such every bit hcitool and hciconfig take been deprecated upstream, and are no longer included in bluez-utils. Since these tools will no longer be updated, it is recommended that scripts be updated to avoid using them. If you still desire to use them, install bluez-utils-compat ^AUR. See FS#53110 and the Bluez mailing list for more information.

Front-ends

Console

bluetoothctl — Pairing a device from the shell is one of the simplest and most reliable options.

http://www.bluez.org/ || bluez-utils

Tip: To automate bluetoothctl commands, use echo -east "command1\northwardcommand2\north" | bluetoothctl or bluetoothctl -- command .

Graphical

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

GNOME Bluetooth — GNOME'due south Bluetooth tool.
- gnome-bluetooth provides the back-finish
- gnome-shell provides the status monitor applet
- gnome-command-center provides the configuration forepart-end GUI that can be accessed by typing Bluetooth on the Activities overview, or with the gnome-control-center bluetooth command.
- You tin can also launch the bluetooth-sendto command directly to transport files to a remote device.
- nautilus-bluetooth ^AUR adds a "Ship via Bluetooth" entry to Nautilus' correct-click card
- To receive files, open the Bluetooth settings panel; you lot tin can only receive whilst the Bluetooth panel is open.
- To add a Bluetooth entry to the Transport To bill of fare in Thunar's file properties menu, come across instructions hither. (The command that needs to exist configured is bluetooth-sendto %F).

https://wiki.gnome.org/Projects/GnomeBluetooth ||

Bluedevil — KDE's Bluetooth tool. If in that location is no Bluetooth icon visible in Dolphin and in the system tray, enable it in the system tray options or add a widget. You can configure Bluedevil and detect Bluetooth devices by clicking the icon. An interface is also available from the KDE System Settings.

https://invent.kde.org/plasma/bluedevil || bluedevil

Huckleberry — Linux Mint'south spin-off of GNOME Bluetooth, which works in all desktop environments. Huckleberry does not support receiving files through Obex Object Button.

https://github.com/linuxmint/huckleberry || blueberry

Blueman — A full featured Bluetooth director.

https://github.com/blueman-project/blueman || blueman

ObexFTP — A tool for transferring files to/from any OBEX enabled device.

http://dev.zuckschwerdt.org/openobex/wiki/ObexFtp || obexftp ^AUR

Pairing

Note: Before using the Bluetooth device, brand sure that it is not blocked by rfkill.

This department describes direct configuring bluez5 via the bluetoothctl CLI, which might not be necessary if you are using an alternative front-end tool (such every bit GNOME Bluetooth).

The exact procedure depends on the devices involved and their input functionality. What follows is a general outline of pairing a device using bluetoothctl.

Offset the bluetoothctl interactive command. Input help to get a listing of available commands.

(optional) Select a default controller with select MAC_address .
Enter power on to plough the ability to the controller on. It is off by default and will plow off once more each reboot, run into #Auto power-on later boot/resume.
Enter devices to become the MAC address of the device with which to pair.
Enter device discovery mode with scan on control if device is not still on the list.
Plough the amanuensis on with agent on or cull a specific agent: if you press tab twice after agent you should see a list of available agents. A bluetooth amanuensis is what manages the Bluetooth 'pairing code'. It can either respond to a 'pairing lawmaking' coming in, or can send i out. The default-agent should be appropriate in most cases.[1]
Enter pair MAC_address to practice the pairing (tab completion works).
If using a device without a Pin, one may need to manually trust the device before information technology can reconnect successfully. Enter trust MAC_address to do so.
Enter connect MAC_address to establish a connexion.

An case session may wait this way:

# bluetoothctl

[NEW] Controller 00:x:20:30:twoscore:fifty pi [default]

[bluetooth]# agent KeyboardOnly

Agent registered

[bluetooth]# default-agent

Default amanuensis asking successful

[bluetooth]# power on

Changing power on succeeded [CHG] Controller 00:10:20:30:40:50 Powered: yes

[bluetooth]# scan on

Discovery started [CHG] Controller 00:10:20:30:40:50 Discovering: yes [NEW] Device 00:12:34:56:78:xc myLino [CHG] Device 00:12:34:56:78:90 LegacyPairing: yes

[bluetooth]# pair 00:12:34:56:78:xc

Attempting to pair with 00:12:34:56:78:ninety [CHG] Device 00:12:34:56:78:xc Connected: yeah [CHG] Device 00:12:34:56:78:90 Connected: no [CHG] Device 00:12:34:56:78:xc 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

[bluetooth]# connect 00:12:34:56:78:90

Attempting to connect to 00:12:34:56:78:90 [CHG] Device 00:12:34:56:78:90 Continued: yes Connectedness successful

Dual boot pairing

To pair devices on dual boot setups you demand to change the pairing keys manually on your Linux install, so that they match in both systems.

Setup

To practise this, first pair your device on your Curvation Linux install. Then reboot into the other Os and pair the device. At present you lot demand to extract the pairing keys, but first switch off the Bluetooth devices to foreclose any connexion attempts.

For Windows

The factual accurateness of this article or section is disputed.

Reason: The key structure for a BT5.ane mouse may exist different than described here. (Discuss in Talk:Bluetooth)

The registry primal containing the link keys may only exist accessed by the SYSTEM account, which cannot be logged into. Therefore, you will need Microsoft's PsExec tool from the official Windows Sysinternals site in guild to run regedit.exe equally Arrangement.

Download PsTools, and excerpt PsExe64.exe.

In an administrator case of a command shell, from the location of the extracted EXE, launch the registry editor:

.\PsExec64.exe -s -i regedit.exe

In the registry editor, navigate to the following registry key:

HKEY_LOCAL_MACHINE\Arrangement\CurrentControlSet\Services\BTHPORT\Parameters\Keys

Within this key is a key for each Bluetooth adapter, by MAC address. If there are multiple keys, and you are unsure of which to utilise, follow this guide to find the MAC address for the desired Bluetooth adapter.

Within the desired device adapter key, there is a binary value for each paired device, by MAC address in the aforementioned fashion.

For each paired device that you wish to share between the installations, right click on the whole key and export it as a .reg file.

If there are LTK, ERand, and EDIV values present, this is a Bluetooth five.1 device, and these likewise must be saved.

Note: If your Windows sectionalisation is encrypted with Bitlocker, you will non exist able to access it from Linux using chntpw.

Reboot into Arch. Install chntpw. Mount your windows system drive.

$ cd          /path/to/windows/system/Windows/System32/config $ chntpw -e SYSTEM

Note: Instead of CurrentControlSet you may come across ControlSet00X, where X is any number. Bank check using the ls command.

Inside the chntpw environment, run

> cd CurrentControlSet\Services\BTHPORT\Parameters\Keys

> cd ControlSet00X\Services\BTHPORT\Parameters\Keys

Then get your Bluetooth adapter'south MAC accost and enter its folder

> ls > cd          your-device'southward-mac-accost

Practice the same for your paired devices:

> ls

Node has 0 subkeys and one values size  blazon        value proper noun    [value if type DWORD] 16    REG_BINARY <123456789876>

Now get your device's key through hex:

> hex 123456789876

:00000 Xx XX XX XX Xx Twenty 20 Xx 20 Xx XX 20 Xx XX XX XX (some other chars)

The "20"s are the pairing key. Brand notation of which keys map to which MAC addresses.

In a BT5.1 Mouse, you might see this output:

Node has 0 subkeys and 8 values   size     type              value name             [value if type DWORD]     xvi  three REG_BINARY         <LTK>      4  4 REG_DWORD          <KeyLength>               xvi [0x10]      8  b REG_QWORD          <ERand>      four  4 REG_DWORD          <EDIV>                 37520 [0x9290]     16  3 REG_BINARY         <IRK>      eight  b REG_QWORD          <Address>      4  iv REG_DWORD          <AddressType>              1 [0x1]      4  iv REG_DWORD          <AuthReq>                 45 [0x2d]

Of these values, you must salve LTK, ERand, and EDIV.

Preparing Bluetooth 5.1 Keys

If at that place were LTK, ERand, and EDIV values in the registry for the desired device, they must be converted for employ with Linux. LTK corrsponds to LongTermKey.Key, ERand to Rand, EDIV to EDiv. The ERand value shound be reversed and converted to decimal. For instance:

An LTK of 48 4D AF CD 0F 92 22 88 0A 52 9A F4 76 DA 8B 94 makes for a LongTermKey.Primal of 484DAFCD0F9222880A529AF476DA8B94.
An ERand of 63 02 84 B8 5D 40 44 DF makes for a Rand of 16088054540146049635.
An EDIV of 37520 makes for an EDiv of 37520.

Note: Yous tin use this Python code to practice the ERand conversion:

>>> ERand=' 63 02 84 B8 5D 40 44 DF   ' >>> ERand=list(reversed(ERand.strip().carve up())) >>> int("".join(ERand), 16) 16088054540146049635

For macOS

Boot into macOS, so open a terminal.

If yous are on Sierra or older, run

# defaults read /private/var/root/Library/Preferences/blued.plist LinkKeys > ~/bt_keys.txt

If yous are on High Sierra or newer, run

# defaults read /private/var/root/Library/Preferences/com.apple.bluetoothd.plist LinkKeys > ~/bt_keys.txt

For older versions of macOS (High Sierra and older) you will have to reverse the keys. For instance, 98 54 2f aa bb cc dd ee ff gg hh two jj kk ll mm becomes MM LL KK JJ GG FF EE DD CC BB AA 2F 54 98.

Copy the bt_keys.txt file to a bulldoze that tin can exist read from Arch Linux. Reboot into Arch Linux.

Finishing up

Now that you have the keys alter user to root, so go on with:

# cd /var/lib/bluetooth/BT-Adapter-MAC-accost

Here you lot will notice folders for each paired Bluetooth device. For each device y'all want to pair with Arch and your dual kick, do the post-obit:

# cd          device-MAC-address

Edit the info file and alter the key under [LinkKey]. E.g.:

info

[LinkKey] Key=XXXXXXXXXXXXXXX

Annotation: You will have to make sure that all the letters are in majuscule case. Remove any spaces.

Then restart bluetooth.service and pulseaudio (with pulseaudio -yard && pulseaudio --kickoff).

Yous should be able to connect to your device now.

Note: Depending on your Bluetooth managing director, yous may need to perform a total reboot in social club to reconnect to the device.

Configuration

Car power-on subsequently boot/resume

By default, the Bluetooth adapter does not ability on after a reboot or resuming from suspend. If you would like the adapter to be powered on after reboot or resume, set AutoEnable=true in /etc/bluetooth/main.conf in the [Policy] department:

/etc/bluetooth/main.conf

[Policy] AutoEnable=true

Discoverable on startup

If the device should always exist visible and directly connectable:

/etc/bluetooth/main.conf

[General] DiscoverableTimeout = 0

Wake from suspend

To permit bluetooth keyboards, mice, etc. to wake the organisation from suspend. First, check the bios settings and brand certain that wake from USB is not disabled. In many cases, bluetooth from the motherboard is a USB device.

Detect the vendor code and device ID for the bluetooth adapter

$ lsusb | grep bluetooth -i Bus 001 Device 002: ID 8087:0039 Intel Corp. AX200 Bluetooth

Add a new udev rule for the vendor code and device ID to enable wake from suspend

/etc/udev/rules.d/91-keyboardmousewakeup.rules

SUBSYSTEM=="usb", ATTRS{idVendor}=="8087", ATTRS{idProduct}=="0039" RUN+="/bin/sh -c 'echo enabled > /sys$env{DEVPATH}/../power/wakeup;'"

Audio

Y'all volition typically need to take an additional step to integrate the audio server with Bluetooth. This is detailed in the below sections.

See the Bluetooth headset folio for more than information almost Bluetooth sound and Bluetooth headsets.

PulseAudio

In society to be able to use audio equipment similar Bluetooth headphones or speakers, you need to install the additional pulseaudio-bluetooth package. Make sure to restart pulseaudio to make the installation take result: pulseaudio -chiliad. With a default PulseAudio installation you lot should immediately be able to stream audio from a Bluetooth device to your speakers.

If you accept a system-wide PulseAudio setup make sure the user running the daemon (usually pulse) is in the lp group and yous load the Bluetooth modules in your PulseAudio config:

/etc/pulse/system.pa

... load-module module-bluetooth-policy load-module module-bluetooth-discover ...

PipeWire

PipeWire every bit of v0.3.nineteen enables its Bluetooth back up by default.

ALSA

Note: Bluez5 has dropped directly integration for ALSA and supports PulseAudio only. Follow the instructions below if you cannot or exercise not want to use PulseAudio.

First, ensure that your Bluetooth audio device is correctly paired and continued to the system.

Then, install bluez-alsa-git ^AUR, start (and enable) the bluealsa service, and add your user to the audio group.

Run the following command to check if everything is working every bit intended (replace XX:Xx:XX:XX:XX:20 and FILE.wav beneath):

$ aplay -D bluealsa:SRV=org.bluealsa,DEV=Twenty:Twenty:XX:Xx:XX:Xx,Contour=a2dp          FILE.wav

Finally, add the following lines to your ~/.asoundrc:

~/.asoundrc

defaults.bluealsa {     service "org.bluealsa"     device "Twenty:Twenty:Twenty:Xx:Xx:Xx"     contour "a2dp" }

You tin now use the bluealsa device to reach your Bluetooth sound device. Volume management is conducted normally via alsamixer with the pick -D bluealsa.

Bluetooth series

To go Bluetooth serial communication working on Bluetooth-to-Serial modules (HC-05, HC-06) practice the post-obit steps:

Pair your Bluetooth device using bluetoothctl equally described above.

Install bluez-rfcomm ^AUR and bluez-utils-compat ^AUR, as they provide certain functionality which is missing from newer tools.

Bind paired device MAC address to tty final:

# rfcomm bind rfcomm0          MAC_address_of_Bluetooth_device

At present you can open /dev/rfcomm0 for serial advice:

picocom /dev/rfcomm0 -b 115200

Troubleshooting

This commodity or section is out of date.

Reason: Replace hciconfig with newer commands. (Discuss in Talk:Bluetooth)

Debugging

In order to debug, get-go terminate bluetooth.service.

And so starting time it with the -d parameter:

# /usr/lib/bluetooth/bluetoothd -northward -d

Another choice is via the btmon tool.

Deprecated BlueZ tools

Eight BlueZ tools were deprecated and removed from bluez-utils, although not all of them were superseded by newer tools. The bluez-utils-compat ^AUR package provides an alternative version of bluez-utils with the deprecated tools.

Deprecated tool	About likely replacement
gatttool	btgatt-client, D-Bus Gatt API
hciattach	btattach
hciconfig	btmgmt (and bluetoothctl?)
hcidump	btmon (and btsnoop)
hcitool	missing, D-Bus Device API bachelor
rfcomm	missing, implement with D-Bus Profile1 API?
ciptool	missing, implement with D-Bus Profile1 API?
sdptool	missing, functionality seems to be scattered over different D-Coach objects: Profile, Advertising, and the UUIDs arrays in device and adapter.

gnome-bluetooth

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

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

And so make sure that the XDG user directories be.

Bluetooth USB Dongle

If you are using a USB dongle, yous should check that your Bluetooth dongle is recognized. You can practice that past running journalctl -f as root when you lot have plugged in the USB dongle (or inspecting /var/log/letters.log). It should expect something similar the following (await out for hci):

Feb xx 15:00:24 hostname kernel: [ 2661.349823] usb 4-i: new full-speed USB device number 3 using uhci_hcd February twenty 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 fifteen:00:25 hostname bluetoothd[4568]: Adapter /org/bluez/4568/hci0 has been enabled

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

# btmgmt

[mgmt]# info

Index list with 1 item hci0:	Principal controller 	addr 00:1A:7D:DA:71:10 version 6 manufacturer 10 class 0x000000 	supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr hs le advertising secure-conn debug-keys privacy static-addr          current settings:          connectable discoverable bondable ssp br/edr le secure-conn  	name Mozart 	short name

[mgmt]# select hci0

Selected index 0

[hci0]# power upwards

hci0 Set up Powered complete, settings:          powered          connectable discoverable bondable ssp br/edr le secure-conn

[hci0]# info

hci0:	Primary controller 	addr 00:1A:7D:DA:71:10 version six manufacturer 10 class 0x1c0104 	supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr hs le advertising secure-conn debug-keys privacy static-addr          current settings: powered          connectable discoverable bondable ssp br/edr le secure-conn

# bluetoothctl

[bluetooth]# bear witness

Controller 00:1A:7D:DA:71:10 (public) 	Proper noun: Mozart 	Allonym: Mozart 	Grade: 0x0000095c          Powered: no          Discoverable: yes 	Pairable: yep

[bluetooth]# power on

[CHG] Controller 00:1A:7D:DA:71:ten Class: 0x001c0104 Changing power on succeeded [CHG] Controller 00:1A:7D:DA:71:10          Powered: yes

[bluetooth]# show

Controller 00:1A:7D:DA:71:10 (public) 	Name: Mozart 	Alias: Mozart 	Course: 0x001c0104          Powered: yes          Discoverable: aye 	Pairable: yeah

To verify that the device was detected you can utilise btmgmt which is part of the bluez-utils. You can become a listing of available devices and their identifiers and their MAC accost by issuing:

$ btmgmt info

Alphabetize list with 1 particular hci0:	Primary controller 	addr 00:1A:7D:DA:71:x          version half dozen          manufacturer ten course 0x1c0104 	supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr hs le ad secure-conn debug-keys privacy static-addr  	current settings: powered connectable discoverable bondable ssp br/edr le secure-conn

It is possible to check the Bluetooth version as mapped to the HCI version according to the table in the official specification. For case, in the previous output, HCI version half-dozen is Bluetooth version 4.0.

More than detailed data about the device tin be retrieved past using the deprecated hciconfig. (bluez-utils-compat ^AUR)

$ hciconfig -a hci0

hci0:   Type: USB         BD Address: 00:1B:DC:0F:DB:xl ACL MTU: 310:10 SCO MTU: 64:8         Upward RUNNING PSCAN ISCAN         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 Take          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 (x)

Sound devices start to skip at short distance from dongle

If other devices share the same USB host, they can interrupt communication with sound devices. Make sure information technology is the only device attached to its bus. For example:

$ lsusb

Charabanc 002 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Motorcoach 001 Device 004: ID 048d:1345 Integrated Technology Express, Inc. Multi Cardreader Motorbus 001 Device 003: ID 0424:a700 Standard Microsystems Corp. ii Port Hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Charge per unit Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation ii.0 root hub

CSR Dongle 0a12:0001

The device ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) has a regression bug, and currently only works in the kernel version ≤ 3.ix.11. There is a patch available for newer versions. For more than information, see Kernel Problems 60824.

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 and so it seems to your PC that you are using a normal USB mouse/keyoard.

If you lot hold the lilliputian cherry Push button on the USB BT mini-receiver it will enable the other mode. Hold the red button on the BT dongle and plug information technology into the computer, and after 3-5 seconds of holding the button, the Bluetooth icon volition appear in the system tray. Word

Alternatively, yous can install the bluez-hid2hci package. When you connect your Logitech dongle it will automatically switch.

hcitool scan: Device not found

On some laptops (e.thousand. Dell Studio 15, Lenovo Thinkpad X1) you have to switch the Bluetooth mode from HID to HCI. Install the bluez-hid2hci parcel, so udev should do this automatically. Alternatively, you lot tin can run this command to switch to HCI manually:

# /usr/lib/udev/hid2hci

If the device volition non show upward and you lot take a Windows operating organisation on your machine, endeavor booting it and enable the Bluetooth adapter from windows.

Sometimes also this simple command helps:

# bluetoothctl power on

bluetoothctl: No default controller available

This error may happen if the device is blocked past rfkill.

Information technology might besides happen with some intel cards (such as the 8260) to not be picked up correctly by the Bluetooth service. In some cases, using the deprecated bluez-utils-compat ^AUR in lieu of bluez-utils have reportedly fixed the upshot.

This might as well be acquired by power saving measures, in which case adding the kernel parameter btusb.enable_autosuspend=n is a potential solution. See also Red Hat Bugzilla – Issues 1573562.

Sometimes unloading and loading btusb without options helps to get the controller dorsum:

# modprobe -r btusb # modprobe btusb

systemd: Condition check resulted in Bluetooth service being skipped

bluetooth.service only requires the directory /sys/course/bluetooth to be, which should be created by kernel module bluetooth, which is simply autoloaded by systemd-udev if it actually finds a working Bluetooth hardware device.

If your /sys/class/bluetooth does not exist, check if your kernel Bluetooth module is loaded by lsmod. If not, and you lot believe you take a Bluetooth device, you can effort manually starting them by loading the Bluetooth module and restarting bluetooth.service.

You lot should also load your corresponding kernel Bluetooth driver when loading the bluetooth module, almost likely btusb, just can too exist btrtl,btintel,btbcm,bnep,btusb etc.

Bank check bluetooth.service'south unit status to see whether it started.

See also Debian Problems report logs - #853207.

If bluetooth.service started successfully, but at that place is adventure that you however cannot use Bluetooth normally (e.g. bluetoothctl says something similar org.Bluez.Error.NotReady when you lot scan on). If this happens, attempt rebooting your estimator, and double-cheque: whether directory /sys/form/bluetooth exists; whether lsmod includes correct Bluetooth modules; log messages in the journal; etc. systemd-udev should pickup your Bluetooth hardware automatically without manual changes again.

rfkill unblock: Practise non unblock

If your device even so soft blocked and yous run ConnMan, try this:

$ connmanctl enable bluetooth

Computer is non visible

Enable discoverable mode if your computer cannot be discovered from your phone:

# bluetoothctl discoverable on

Verify that discoverable mode is on:

# bluetoothctl prove

          Powered: yes 	Discoverable: yep 	Pairable: yes

Annotation: Check DiscoverableTimeout and PairableTimeout in /etc/bluetooth/master.conf.

If the reckoner notwithstanding does not show up, try changing the device form in /etc/bluetooth/primary.conf equally follows:

# Default device grade. Only the major and modest device form bits are # considered. #Class = 0x000100 # Figurer Type (from default config) Class = 0x100100 # (Object-Transfer Service & Estimator Type)

Note: In some cases, Class in main.conf gets overridden later device initialization, so fix the class directly with hciconfig hci0 class 100100.

A user reported that this was the only solution to make their figurer visible for their telephone. LG TVs (and some others) are discoverable from their audio devices, so using 000414 (the soundbar course) volition make such devices appear.

Come across https://bluetooth-pentest.narod.ru/software/bluetooth_class_of_device-service_generator.html to generate Bluetooth device/service classes.

Foxconn / Hon Hai / Lite-On Broadcom device

Some of these devices crave the firmware to exist flashed into the device at boot. The firmware is not provided just tin converted from a Microsoft Windows .hex file into a .hcd using hex2hcd (which is installed with bluez-utils).

In order to get the right .hex file, effort searching the device vendor:product code obtained with lsusb, for example:

... Omnibus 002 Device 004: ID          04ca:2006          Lite-On Technology Corp. Broadcom BCM43142A0 Bluetooth Device ...

Bus 004 Device 004: Id          0489:e031          Foxconn / Hon Hai

Alternatively, boot into Windows (a virtual machine installation will suffice) and go the firmware proper noun from the Device Director utility. If y'all want to know the model of your device only cannot encounter it in lsusb, you might see information technology in lsusb -five as iProduct.

The .hex file can be extracted from the downloaded Windows driver without having to run Windows for information technology. Download the right driver, for example Bluetooth Widcomm (listed among the drivers for Lifebook P771), which contains the drivers for many Broadcomm devices. In case of Bluetooth Widcomm, the driver is a self-extracting RAR archive, then it can exist extracted using unrar 10. To find out which of the many .hex files is the right one for you, look in the file Win32/bcbtums-win7x86-brcm.inf and search for [RAMUSBE031.CopyList], where E031 should be replaced with the product code (the second hex number in lsusb) of your device in upper-case. Underneath you lot should see the file proper noun of the right .hex file.

Once you have the .hcd file, re-create information technology into /lib/firmware/brcm/BCM.hcd - this filename is suggested past dmesg and it may alter in your case so check your dmesg output in order to verify. So reload the btusb module:

# rmmod btusb # modprobe btusb

The device should at present exist available. See BBS#162688 for data on making these changes persistent.

Intel combined WiFi and Bluetooth cards

See Wireless network configuration#Bluetooth coexistence.

Device connects, so disconnects after a few moments

If yous encounter messages like the following in the journal, and your device fails to connect or disconnects before long after connecting:

bluetoothd: Unable to get connect data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107) bluetoothd: connect error: Connection refused (111)

This may be because y'all have already paired the device with another operating organisation using the aforementioned Bluetooth adapter (e.g., dual-booting). Some devices cannot handle multiple pairings associated with the aforementioned MAC address (i.e., Bluetooth adapters). Follow instructions on #Dual boot pairing for solving this event.

Device does non testify upwards in browse

Some devices using Bluetooth low energy do not appear when scanning with bluetoothctl, for example the Logitech MX Master. The simplest way I have establish to connect them is past installing bluez-utils-compat ^AUR, then commencement bluetooth.service and practise:

# bluetoothctl

[NEW] Controller (MAC) myhostname [default]

[bluetooth]# power on

[CHG] Controller (MAC) Grade: 0x0c010c Changing ability on succeeded [CHG] Controller (MAC) Powered: yes

[bluetooth]# scan on

Discovery started [CHG] Controller (MAC) Discovering: yeah

In some other concluding:

# hcitool lescan

Look until your device shows up, and then Ctrl+c hcitool. bluetoothctl should now encounter your device and pair normally.

Cannot receive transferred files due to symlink

If incoming file transfers fail on an an otherwise functional Bluetooth connection, the problem may be due to symlinks in your file transfer path. Logs like this would appear in the periodical:

Jun 18 11:eighteen:13 ember obexd[3338969]: open(/home/me/.cache/obexd/MOC740): Operation not permitted (1)

If the path shown in the error message contains a symlink, then obexd past default will not take it. The beliefs can be overridden on initialization using a drop-in file for the obex.service user service:

~/.config/systemd/user/obex.service.d/10-symlink.conf

[Service] ExecStart= ExecStart=/usr/lib/bluetooth/obexd --symlinks

And then reload the systemd manager configuration of the calling user and restart the obex.service user unit.

Interference between Headphones and Mouse

If y'all experience audio stuttering while using a Bluetooth mouse and keyboard simultaneously, you tin can try the post-obit equally referenced in #23 https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/424215

# hciconfig hci0 lm Take,MASTER # hciconfig hci0 lp HOLD,SNIFF,PARK

Bluetooth mouse laggy movements

Try to edit the file /var/lib/bluetooth/XX:Xx:XX:XX:20:20/YY:YY:YY:YY:YY:YY/info (20:XX:XX:Xx:Xx:Xx - your Bluetooth adapter MAC address, YY:YY:YY:YY:YY:YY - your mouse MAC address) and add together these lines:

[ConnectionParameters] MinInterval=6 MaxInterval=ix Latency=44 Timeout=216

Y'all tin can meet your local adapter MAC address past running the control hcitool dev. You can see the MAC addresses of currently connected remote devices by running the command hcitool con.

Adapter disappears after suspend/resume

Starting time, find vendor and production ID of the adapter. For example:

$ lsusb -tv set

/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M     ID 1d6b:0002 Linux Foundation 2.0 root hub     ...     |__ Port 3: Dev 3, If 0, Class=Wireless, Commuter=btusb, 12M         ID 8087:0025 Intel Corp.      |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M         ID 8087:0025 Intel Corp.      ...

In this example, the vendor ID is 8087 and the product ID is 0025.

Then, utilise usb_modeswitch to reset the adapter:

# usb_modeswitch -R -v          vendor_ID          -p          product_ID

Problems with all BLE devices on kernel 5.ix+

Starting with v5.9, the kernel Bluetooth stack tries to use link-layer privacy on BLE connections. If the device works after pairing merely does not survive a reboot or append, it is probably considering of this.

To workaround [two] this issue, open /var/lib/bluetooth/adapter_mac/device_mac/info, remove the following lines, and restart bluetooth.service:

[IdentityResolvingKey] Key=...

Run into the relevant word on the Arch forum.

Continually connect/disconnect with tp-link UB400 and xbox controller

Edit /etc/bluetooth/chief.conf and set below settings (uncomment/change value):

[General JustWorksRepairing = always FastConnectable = truthful Class = 0x000100

[GATT] ReconnectIntervals=1,1,two,3,five,viii,13,21,34,55 AutoEnable=true

So restart the bluetooth.service.

You can see relevant give-and-take on xpadneo merely the xpadneo commuter is not needed.

Enabling experimental feature

The factual accuracy of this article or section is disputed.

Reason: Does the Arch Linux package have this compiled in? If not, how tin can one get a build with experimental features (preferably an AUR package)? (Discuss in Talk:Bluetooth)

The Bluez stack keeps new, potentially buggy features backside the Experimental choice. The functionality included nether this by this vary over fourth dimension, as experimental features are determined to be stable and no longer crave the choice. To enable this, uncomment the relevant line in the configuration:

/etc/bluetooth/main.conf

# Enables experimental features and interfaces. # Defaults to false. Experimental = true

See likewise

Keeping Bluetooth devices paired between Linux and Windows
Bluetooth link keys on dual-boot systems

bobbittthereastelf.blogspot.com

Source: https://wiki.archlinux.org/title/Bluetooth