Как найти bluetooth в linux

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

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

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

• bluetuith — Provides a bluetooth manager via a Terminal User Interface for easier pairing and device/adapter management, with OBEX File Transfer and mouse support.

https://www.github.com/darkhz/bluetuith || bluetuith^AUR

Tip: To automate bluetoothctl commands, use echo -e "command1ncommand2n" | bluetoothctl or bluetoothctl -- command.

Graphical

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

• GNOME Bluetooth — GNOME’s Bluetooth tool.
  • gnome-bluetooth-3.0 provides the back-end (gnome-bluetooth is now legacy)
  • gnome-shell provides the status monitor applet
  • 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.
  • You can also launch the bluetooth-sendto command directly to send files to a remote device.
  • nautilus-bluetooth^AUR adds a “Send via Bluetooth” entry to Nautilus’ right-click menu
  • To receive files, open the Bluetooth settings panel; you can only receive whilst the Bluetooth panel is open.
  • To add a Bluetooth entry to the Send To menu in Thunar’s file properties menu, see instructions here. (The command that needs to be configured is bluetooth-sendto %F).

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

• Bluedevil — KDE’s Bluetooth tool. If there 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

• Blueberry — Linux Mint’s spin-off of GNOME Bluetooth, which works in all desktop environments. Blueberry does not support receiving files through Obex Object Push.

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

• Blueman — A full featured Bluetooth manager.

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, make sure that it is not blocked by rfkill.

This section describes directly configuring bluez5 via the bluetoothctl CLI, which might not be necessary if you are using an alternative front-end tool (such as 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.

Start the bluetoothctl interactive command. Input help to get a list of available commands.

1. (optional) Select a default controller with select MAC_address.
2. (optional) Enter power on to turn the power to the controller on if the device is set to off. It is on by default; see #Default adapter power state.
3. Enter devices to get the MAC address of the device with which to pair.
4. Enter device discovery mode with scan on command if device is not yet on the list.
5. Turn the agent on with agent on or choose a specific agent: if you press tab twice after agent you should see a list of available agents. A bluetooth agent is what manages the Bluetooth ‘pairing code’. It can either respond to a ‘pairing code’ coming in, or can send one out. The default-agent should be appropriate in most cases.[1]
6. Enter pair MAC_address to do the pairing (tab completion works).
7. 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.
8. Enter connect MAC_address to establish a connection.

An example session may look this way:

$ bluetoothctl

[NEW] Controller 00:10:20:30:40:50 hostname [default]
[bluetooth]# agent KeyboardOnly
Agent registered

[bluetooth]# default-agent
Default agent request 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:90 device name
[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

[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 Connected: yes
Connection successful

Dual boot pairing

To pair devices on dual boot setups you need to change the pairing keys on your Linux install so that they are consistent with what Windows or macOS is using.

This page only describes the manual method of doing so. To automate the process, see the bt-dualboot project and the related repositories.

Setup

To do this, first pair your device on your Arch Linux install. Then reboot into the other OS and pair the device. Now you need to extract the pairing keys, but first switch off the Bluetooth devices to prevent any connection attempts.

Note: Some Logitech devices, such as the Logitech MX Master and Logitech 604 Lightspeed, increment the MAC address by one every time that the device is paired with a new system. You should determine whether this is the case, so that it can be accounted for at the end of the process.

For Windows

First, boot into Windows.

The registry key containing the link keys may only be 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 order to run regedit.exe as SYSTEM.

Download PsTools, and extract PsExec64.exe.

In an administrator instance 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_MACHINESYSTEMCurrentControlSetServicesBTHPORTParametersKeys

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 use, follow this guide^{[dead link 2023-05-06 ⓘ]} to find the MAC address for the desired Bluetooth adapter.

Within the desired device adapter key, there is a key for each paired device, also organized by MAC address.

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. This is a text file that you can copy the keys from.

Within this file, if there is a single binary key, then this is not a Bluetooth 5.1 device, and that pairing key is all that is needed.

Otherwise, if there are several keys for the paired device such as LTK or IRK, then this is a BT5.1 device. Refer to #Preparing Bluetooth 5.1 Keys to see how to use them.

Finally, to import the key(s) into your Linux installation, reboot into Linux and proceed to #Finishing up.

Note: If your Windows partition is encrypted with Bitlocker, you will not be 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 see ControlSet00X, where X is any number. Check using the ls command.

Inside the chntpw environment, run

> cd CurrentControlSetServicesBTHPORTParametersKeys

or

> cd ControlSet00XServicesBTHPORTParametersKeys

Then get your Bluetooth adapter’s MAC address and enter its folder

> ls
> cd your-device's-mac-address

Do the same for your paired devices. If this is not a Bluetooth 5.1 device, you will only see the pairing key:

> ls

Node has 0 subkeys and 1 values
size  type        value name    [value if type DWORD]
16    REG_BINARY <123456789876>

If so, get your device’s key through hex:

> hex 123456789876

:00000 XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX (some other chars)

The “XX”s are the pairing key. Make note of which keys map to which MAC addresses.

If this is a Bluetooth 5.1 device, then you will see several keys corresponding to the one device.

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

Refer to #Preparing Bluetooth 5.1 Keys to see how to use these, using hex value_name to obtain the requested values.

Finally, to import the key(s) into your Linux installation, proceed to #Finishing up.

For macOS

Boot into macOS:

• For macOS Monterey or newer:
  1. Open Keychain Access and search for Bluetooth.
  2. Sort by date.
  3. If you’ve recently removed and reconnected the device then you can simply sort the keys by date modified and pick the latest. It is probably called MobileBluetooth (for older Bluetooth devices) or is just an UUID (for Bluetooth 5.1+).
  4. Double click on the entry. Check that the MAC address in the Account field matches the MAC address of your device.
  5. Click the “Show password” checkbox. You will now need to enter your password, twice.
  6. Copy the text in the password field, it’s actually an XML file (⌘+a ⌘+c)
  7. Paste the text in bt_keys.txt in your home directory.
• For High Sierra or newer, run the following in a terminal:

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

• For Sierra or older, run the following in a terminal:

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

The ~/.bt_keys.txt file now contains the established Bluetooth keys. For older versions of macOS (High Sierra and older) you will have to reverse the keys before proceeding. For example, 98 54 2f aa bb cc dd ee ff gg hh ii jj kk ll mm becomes MM LL KK JJ GG FF EE DD CC BB AA 2F 54 98.

>>> key = "98 54 2f aa bb cc dd ee ff gg hh ii jj kk ll mm"
>>> " ".join(reversed(key.strip().split()))

If this is a Bluetooth 5.1 device, then there will be more than one key corresponding to one device. Refer to #Preparing Bluetooth 5.1 Keys to see how to use these.

Finally, to import the key(s) into your Linux installation, reboot into Linux and proceed to #Finishing up.

Preparing Bluetooth 5.1 Keys

If you observed the presence of Bluetooth 5.1 keys while following #For Windows or #For macOS, you must apply certain transformations to their values before importing them into Linux. Create the requested files with their appropriate contents, for installation in #Finishing up. This process will depend on the device, and some of the values have to be manipulated; code utilities for doing so are provided below.

>>> "key_value".replace(" ", "")

>>> ERand=" 63 02 84 B8 5D 40 44 DF   "
>>> ERand=list(reversed(ERand.strip().split()))

>>> int("".join(ERand), 16)
16088054540146049635

binascii.hexlify(base64.decodebytes(b'...')).upper()

struct.unpack('<H', base64.decodebytes(b'...'))

struct.unpack('<Q', base64.decodebytes(b'...'))

For an example of the general case:

• An LTK of 48 4D AF CD 0F 92 22 88 0A 52 9A F4 76 DA 8B 94 makes for a LongTermKey.Key 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.

Finishing up

Now that you have the keys change user to root, then continue with:

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

Here you will find folders for each paired Bluetooth device. For each device you want to pair with Arch and your dual boot, do the following:

# cd device-MAC-address

Note: At this point, if you are using a device which increments its MAC address on pairing, you must move the MAC address directory to the incremented path. Either copy the MAC address from Windows, or increment it yourself while minding the fact that each octet is a two-digit hexadecimal number.

If you have a pairing key (i.e. this is not a Bluetooth 5.1 device), then edit the info file and change the key under [LinkKey]. E.g.:

info

[LinkKey]
Key=XXXXXXXXXXXXXXX

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

If you have Bluetooth 5.1 keys, then you must instead copy the key files to the MAC address directory.

Then restart bluetooth.service and pulseaudio (with pulseaudio -k && pulseaudio --start).

You should be able to connect to your device now.

Note: Depending on your Bluetooth manager, you may need to perform a full reboot in order to reconnect to the device.

Configuration

Default adapter power state

As of bluez 5.65, BlueZ’ default behavior is to power on all Bluetooth adapters when starting the service or resuming from suspend. [2]

If you would like the adapter to not be automatically enabled (e.g. on a portable device where you wish to save battery), set AutoEnable=false in /etc/bluetooth/main.conf in the [Policy] section:

/etc/bluetooth/main.conf

[Policy]
AutoEnable=false

The adapter can still be turned on manually by running power on as described in #Pairing.

Discoverable on startup

If the device should always be visible and directly connectable:

/etc/bluetooth/main.conf

[General]
DiscoverableTimeout = 0

Wake from suspend

To allow Bluetooth keyboards, mice, etc. to wake the system from suspend. First, check the bios settings and make sure that wake from USB is not disabled. In many cases, Bluetooth from the motherboard is a USB device.

Find 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-keyboard-mouse-wakeup.rules

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

To automatically re-configure your Bluetooth keyboard after wakeups to e.g. have a different keymap or key press repeat rate (for details, see Xorg/Keyboard configuration#Adjusting typematic delay and rate and xmodmap), create an executable script.

configure_keyboard.sh

#!/bin/sh
export DISPLAY=:0
xset r rate 220 30
xmodmap /your/path/to/.Xmodmap

Then create an additional udev rule like above.

/etc/udev/rules.d/92-keyboard-reconfiguration-wakeup.rules

SUBSYSTEM=="usb", ATTRS{idVendor}=="8087", ATTRS{idProduct}=="0039" RUN+="/your/path/to/configure_keyboard.sh"

Enabling experimental features

The Bluez stack keeps new, potentially buggy features behind the D-Bus experimental and kernel experimental options. The functionality included under these varies over time, as experimental features are determined to be stable and no longer require the option (as an example: enabling D-Bus experimental interfaces currently allows to report battery level for old headsets). To enable these, uncomment the corresponding line in the configuration:

/etc/bluetooth/main.conf

...

# Enables D-Bus experimental interfaces
# Possible values: true or false
#Experimental = true

# Enables kernel experimental features, alternatively a list of UUIDs
# can be given.
# Possible values: true,false,<UUID List>
# Possible UUIDS:
...
# Defaults to false.
#KernelExperimental = true

Alternatively, you can edit the bluetooth.service to add the --experimental or --kernel flag, like this drop-in file:

/etc/systemd/system/bluetooth.service.d/override.conf

[Service]
ExecStart=
ExecStart=/usr/lib/bluetooth/bluetoothd --experimental

Either way, you must then restart the bluetooth.service.

Audio

You will 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 page for more information about Bluetooth audio and Bluetooth headsets.

PulseAudio

In order to be able to use audio equipment like Bluetooth headphones or speakers, you need to install the additional pulseaudio-bluetooth package. Make sure to restart pulseaudio to make the installation take effect: pulseaudio -k. With a default PulseAudio installation (specifically, using a user instance with the packaged default.pa) you should immediately be able to stream audio from a Bluetooth device to your speakers. [3]

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

/etc/pulse/system.pa

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

Optionally, add load-module module-switch-on-connect if you want to auto-switch all audio to the Bluetooth device.

PipeWire

PipeWire as of v0.3.19 enables its Bluetooth support by default.

ALSA

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

First, ensure that your Bluetooth audio device is correctly paired and connected 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 as intended (replace XX:XX:XX:XX:XX:XX and FILE.wav below):

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

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

~/.asoundrc

defaults.bluealsa {
    service "org.bluealsa"
    device "XX:XX:XX:XX:XX:XX"
    profile "a2dp"
}

You can now use the bluealsa device to reach your Bluetooth audio device. Volume management is conducted normally via alsamixer with the option -D bluealsa.

Bluetooth serial

To get Bluetooth serial communication working on Bluetooth-to-Serial modules (HC-05, HC-06) do the following steps:

Pair your Bluetooth device using bluetoothctl as described above.

Install bluez-utils-compat^AUR, as it provides certain functionality which is missing from newer tools.

Bind paired device MAC address to tty terminal:

# rfcomm bind rfcomm0 MAC_address_of_Bluetooth_device

Now you can open /dev/rfcomm0 for serial communication:

$ picocom /dev/rfcomm0 -b 115200

Troubleshooting

Debugging

In order to debug, first stop bluetooth.service.

And then start it with the -d parameter:

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

Another option 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.

gnome-bluetooth

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 make sure that the XDG user directories exist.

Bluetooth USB dongle

If you are using a USB dongle, you should check that your Bluetooth dongle is recognized. You can do that by running journalctl -f as root when you have plugged in the USB dongle (or inspecting /var/log/messages.log). 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

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

# btmgmt

[mgmt]# info
Index list with 1 item
hci0:	Primary 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 up
hci0 Set 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 6 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

Or

# bluetoothctl

[bluetooth]# show
Controller 00:1A:7D:DA:71:10 (public)
	Name: Mozart
	Alias: Mozart
	Class: 0x0000095c
	Powered: no
	Discoverable: yes
	Pairable: yes

[bluetooth]# power on
[CHG] Controller 00:1A:7D:DA:71:10 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
	Class: 0x001c0104
	Powered: yes
	Discoverable: yes
	Pairable: yes

To verify that the device was detected you can use btmgmt which is part of the bluez-utils. You can get a list of available devices and their identifiers and their MAC address by issuing:

$ btmgmt info

Index list with 1 item
hci0:	Primary controller
	addr 00:1A:7D:DA:71:10 version 6 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

It is possible to check the Bluetooth version as mapped to the HCI version according to the table in the official specification. For example, in the previous output, HCI version 6 is Bluetooth version 4.0.

More detailed information about the device can be retrieved by using the deprecated hciconfig. (bluez-utils-compat^AUR)

$ hciconfig -a hci0

hci0:   Type: USB
        BD Address: 00:1B:DC:0F:DB:40 ACL MTU: 310:10 SCO MTU: 64:8
        UP 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 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)

Audio devices start to skip at short distance from dongle

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

$ lsusb

Bus 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
Bus 001 Device 004: ID 048d:1345 Integrated Technology Express, Inc. Multi Cardreader
Bus 001 Device 003: ID 0424:a700 Standard Microsystems Corp. 2 Port Hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.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 5.17 and < 6.0. For more information, see Kernel Bug 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 so it seems to your PC that you are 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

Alternatively, you 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.g. Dell Studio 15, Lenovo Thinkpad X1) you have to switch the Bluetooth mode from HID to HCI. Install the bluez-hid2hci package, then udev should do this automatically. Alternatively, you can run this command to switch to HCI manually:

# /usr/lib/udev/hid2hci

• 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:

# bluetoothctl power on

bluetoothctl: No default controller available

There is a bug with some motherboard bluetooth controllers. To see if this might be the issue, run journalctl | grep hci. If there are entries like “command tx timeout” or “Reading Intel version command failed”, then power off your pc and physically unplug the power cable for a few seconds. This forces the controller to reload the firmware (while a standard reboot will not). See bug report here.

Make sure the device is not being blocked by rfkill.

It might also 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 issue.

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

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

# modprobe -r btusb
# modprobe btusb

It may occur also when the dongle is a CSR clone

systemd: Condition check resulted in Bluetooth service being skipped

bluetooth.service only requires the directory /sys/class/bluetooth to exist, which should be created by kernel module bluetooth, which is only 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 believe you have a Bluetooth device, you can try manually starting them by loading the Bluetooth module and restarting bluetooth.service.

You should also load your corresponding kernel Bluetooth driver when loading the bluetooth module, most likely btusb, but can also be btrtl,btintel,btbcm,bnep,btusb etc.

Check bluetooth.service‘s unit status to see whether it started.

See also Debian Bug report logs – #853207.

If bluetooth.service started successfully, but there is chance that you still cannot use Bluetooth normally (e.g. bluetoothctl says something like org.Bluez.Error.NotReady when you scan on). If this happens, try rebooting your computer, and double-check: whether directory /sys/class/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: Do not unblock

If your device still soft blocked and you run ConnMan, try this:

$ connmanctl enable bluetooth

Computer is not visible

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

# bluetoothctl discoverable on

Verify that discoverable mode is on:

# bluetoothctl show

	Powered: yes
	Discoverable: yes
	Pairable: yes

Note: Check DiscoverableTimeout and PairableTimeout in /etc/bluetooth/main.conf.

If the computer still does not show up, try changing the device class in /etc/bluetooth/main.conf as follows:

# Default device class. Only the major and minor device class bits are
# considered.
#Class = 0x000100 # Computer Type (from default config)
Class = 0x100100 # (Object-Transfer Service & Computer Type)

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

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

See 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 require the firmware to be flashed into the device at boot.

Some firmware is available when searching for broadcom on the AUR, a notable package being broadcom-bt-firmware^AUR, which provides the files for multiple cards.

Alternatively, the firmware can 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, try searching the device vendor:product code obtained with lsusb, for example:

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

or

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

Alternatively, boot into Windows (a virtual machine installation will suffice) and get the firmware name from the Device Manager utility. If you want to know the model of your device but cannot see it in lsusb, you might see it in lsusb -v as iProduct.

The .hex file can be extracted from the downloaded Windows driver without having to run Windows for it. Download the right driver, for example Bluetooth Widcomm. Depending on the format, extracting the files might need unrar or cabextract. 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 should see the file name of the right .hex file.

Once you have the .hcd file, copy it into /lib/firmware/brcm/BCM.hcd – this filename is suggested by dmesg and it may change in your case so check your dmesg output in order to verify. Then reload the btusb module:

# rmmod btusb
# modprobe btusb

The device should now be available. See BBS#162688 for information on making these changes persistent.

Intel combined WiFi and Bluetooth cards

See Wireless network configuration#Bluetooth coexistence.

Device connects, then disconnects after a few moments

If you see messages like the following in the journal, and your device fails to connect or disconnects shortly 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 you have already paired the device with another operating system using the same Bluetooth adapter (e.g., dual-booting). Some devices cannot handle multiple pairings associated with the same MAC address (i.e., Bluetooth adapters). Follow instructions on #Dual boot pairing for solving this issue.

Device does not show up in scan

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

# bluetoothctl

[NEW] Controller (MAC) myhostname [default]

[bluetooth]# power on
[CHG] Controller (MAC) Class: 0x0c010c
Changing power on succeeded
[CHG] Controller (MAC) Powered: yes

[bluetooth]# scan on
Discovery started
[CHG] Controller (MAC) Discovering: yes

In another terminal:

# hcitool lescan

Wait until your device shows up, then Ctrl+c hcitool. bluetoothctl should now see 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 journal:

Jun 18 11:18: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 by default will not accept it. The behavior 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

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

Interference between Headphones and Mouse

If you experience audio stuttering while using a Bluetooth mouse and keyboard simultaneously, you can try the following as referenced in #23 https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/424215

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

Bluetooth mouse laggy movements

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

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

You can see your local adapter MAC address by running the command hcitool dev. You can see the MAC addresses of currently connected remote devices by running the command hcitool con.

Adapter disappears after suspend/resume

First, find vendor and product ID of the adapter. For example:

$ lsusb -tv

/:  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, Driver=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 case, the vendor ID is 8087 and the product ID is 0025.

Then, use usb_modeswitch to reset the adapter:

# usb_modeswitch -R -v vendor_ID -p product_ID

Problems with all BLE devices on kernel 5.9+

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

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

[IdentityResolvingKey]
Key=...

See the relevant discussion on the Arch forum.

Bluetooth immediately waking up suspend-to-idle devices

On systems capable of suspend-to-idle/S2idle/S0ix/Modern Standby, Bluetooth controllers will stay enabled during sleep. This will usually cause the system to wake up immediately after going to sleep if any Bluetooth device is connected.

To prevent this, you can disable Bluetooth completely before going to sleep – install bluez-utils and create this file:

/etc/systemd/system/bluetooth-disable-before-sleep.service

[Unit]
Description=Disable Bluetooth before going to sleep
Before=sleep.target
Before=suspend.target
Before=hybrid-sleep.target
Before=suspend-then-hibernate.target
StopWhenUnneeded=yes

[Service]
Type=oneshot
RemainAfterExit=yes

ExecStart=/usr/bin/bluetoothctl power off
ExecStop=/usr/bin/bluetoothctl power on

[Install]
WantedBy=sleep.target
WantedBy=suspend.target
WantedBy=hybrid-sleep.target
WantedBy=suspend-then-hibernate.target

Enable this service and check if Bluetooth devices disconnect when going to sleep, and whenever Bluetooth goes back up after waking up the system.

If this workaround is in use, waking up the system with a Bluetooth mouse/keyboard will not work.

Continually connect/disconnect with TP-LINK UB400 and Xbox controller

Use the settings below:

/etc/bluetooth/main.conf

...
[General]
JustWorksRepairing = always
FastConnectable = true
Class = 0x000100
...
[GATT]
ReconnectIntervals=1,1,2,3,5,8,13,21,34,55
AutoEnable=true
...

Then restart the bluetooth.service.

You can see relevant discussion on xpadneo but the xpadneo driver is not needed.

Mediatek MT7921 or MT7961 on dual boot with windows

On dual boot systems, if Bluetooth firmware versions are different for Windows and Linux, the Bluetooth adapter is not working after rebooting to Windows.

The best way to prevent this is updating the Bluetooth drivers (especially firmware) with latest version for each OS.

If you cannot find the latest version driver (or firmware) for Windows, you can copy the latest firmware file /usr/lib/firmware/mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin.xz from Arch Linux and extract to Windows (e.g. C:WINDOWSsystem32DRIVERS, you can find the firmware file path in the device manager on Windows).

Cannot reconnect after sleep

You may notice that you cannot automatically reconnect to a device after it goes to sleep, or after the computer wakes from suspend.

You would for example notice the following errors in your logs:

bluetoothd[487]: Authentication attempt without agent
bluetoothd[487]: Access denied: org.bluez.Error.Rejected

This could be because the device is not marked as trusted. See #Pairing.

Bluetooth turns off after logout on a headless/server system

This can have various causes:

• Both Pulseaudio and PipeWire run as user services by default, which are terminated once the last session ends. Enable lingering for the user to fix this.
• Additionally, when running WirePlumber with PipeWire (which is usually the case), WirePlumber runs a “logind-monitor” which enables Bluetooth on login and disables it on logout. See WirePlumber#Keep Bluetooth running after logout / Headless Bluetooth for a fix.

See also

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

В отличие от многих аспектов Linux, поддержка Bluetooth не выполняется ядром Linux автоматически. Это во многом связано со стеком Bluetooth и тем, как он взаимодействует с системой Linux в целом. Чтобы компенсировать это, удобные для пользователя дистрибутивы, такие как Ubuntu, Elementary и т. Д., Очень стараются настроить Bluetooth для пользователей. Однако не все Linux делают это. Необходимо установить различные службы и клиенты Bluetooth. Кроме того, все радиомодули Bluetooth отличаются (а некоторые из них не имеют драйверов с открытым исходным кодом), что означает, что их нужно устанавливать постфактум. Вот как подключить и использовать устройства Bluetooth в Linux.

ОПОВЕЩЕНИЕ СПОЙЛЕРА: прокрутите вниз и посмотрите видеоурок в конце этой статьи.

Примечание: используете Ubuntu? Если это так, возможно, ваш компьютер уже имеет превосходную поддержку Bluetooth, и нет необходимости настраивать его с помощью этой статьи.

Arch Linux

sudo pacman -S bluez bluez-utils

Fedora

sudo dnf install bluez bluez-tools

OpenSUSE

Получение инструментов и служб Bluetooth в SUSE осуществляется с помощью OBS. Перейти на эту страницуи нажмите кнопку быстрой установки. Отсюда YaST все установит.

Debian

sudo apt-get install bluez*

Другие Linux

Стек bluetooth bluez совместим со всеми дистрибутивами Linux, даже с Chrome OS! По этой причине у пользователей менее известных альтернативных дистрибутивов Linux не будет проблем с работой этих инструментов. Чтобы установить их, откройте диспетчер пакетов и найдите «bluez». Установите все, что содержит слово «bluez», на всякий случай.

В качестве альтернативы, перейти на сайт загрузки, возьмите исходный код и соберите его вручную.

Получение клиента Blueman

Установка Bluez позволяет вашей среде рабочего стола Linux напрямую использовать Bluetooth. Это означает, что если вы используете KDE Plasma, он будет работать напрямую с клиентом KDE Bluetooth. То же самое и со встроенным клиентом Gnome Shell. Итак, устанавливать Blueman не нужно.

Если вы используете среду рабочего стола Linux или оконный менеджер, в котором нет встроенного диспетчера Bluetooth, подумайте об установке Blueman. Это легкий инструмент для подключения, который значительно упрощает взаимодействие с устройствами.

Arch Linux

sudo pacman -S blueman

Fedora

sudo dnf install blueman

OpenSUSE

sudo zypper install blueman

Debian

sudo apt-get install blueman

Другие Linux

Инструмент подключения Blueman широко используется в Linux. Чтобы найти его в альтернативных дистрибутивах Linux, откройте диспетчер пакетов (или программный браузер), найдите «blueman» и установите его. Не можете найти его в источниках программного обеспечения? Вместо этого загрузите его с sourceforge!

Конфигурация

Недостаточно скачать стек Bluez Bluetooth и установить его в Linux. Службы должны быть активными, иначе устройства не будут подключаться. Сначала откройте терминал и получите корневую оболочку, используя: sudo -s

С помощью корневой оболочки вручную загрузите универсальный драйвер Bluetooth USB, если вы используете ключ BT.

modprobe btusb

При использовании портативного компьютера со встроенным радиомодулем Bluetooth драйвер (если поддерживается Linux) должен автоматически загружать драйвер, поэтому нет необходимости загружать его вручную.

Примечание: некоторые ключи Bluetooth не поддерживают этот драйвер в Linux. Если это произойдет с вами, прочтите руководство для вашего устройства и узнайте, какие драйверы ему требуются для работы в Linux.

Arch Linux, Fedora, SUSE и другие системные Linux

Во-первых, включите службу BT, чтобы она всегда запускалась при загрузке Linux. Это делается с помощью:

sudo systemctl enable bluetooth.service

Затем сразу же запустите службу:

sudo systemctl start bluetooth.service

Если в какой-то момент systemctl отказывается запускать или включать эти службы, рассмотрите возможность использования параметра force:

sudo systemctl enable bluetooth.service -f

и

sudo systemctl start bluetooth.service -f

Старая версия Debian

Используете версию Debian без systemd? Если да, то после установки Bluez и всех других инструментов Bluetooth перезагрузите компьютер. Службы запуска будут активны после повторного входа в систему.

Подключение к Bluetooth в Gnome

Если служба Bluetooth работает правильно, при подключении адаптера Bluetooth (или) использовании встроенного радиомодуля Bluetooth на вашем ПК вы должны увидеть значок Bluetooth на панели Gnome.

Щелкните значок, и откроется меню. В меню выберите «Настройки Bluetooth», чтобы открыть инструмент просмотра устройств.

В инструменте просмотра нажмите на устройство, к которому хотите подключиться.

Следуйте инструкциям на экране, которые дает Gnome для подключения.

Подключение к Bluetooth в KDE

Чтобы подключить устройства Bluetooth к рабочему столу KDE Plasma Desktop, убедитесь, что ваш USB-ключ (или) встроенный радиомодуль Bluetooth работает.

Отсюда щелкните значок BT на панели Plasma, затем выберите устройство для подключения. Следуйте инструкциям на инструменте для сопряжения!

Подключение к Bluetooth в Blueman

Чтобы устройство Bluetooth работало с Blueman, сначала щелкните значок Bluetooth на панели задач. Затем нажмите кнопку «Поиск», чтобы найти устройство. Когда появится устройство, выберите его мышью, затем нажмите «Настройка».

Инструмент Blueman проведет вас через процесс сопряжения. Следуйте инструкциям на экране, и вскоре ваше устройство будет сопряжено.

Вывод

Bluetooth всегда был ненадежным в Linux, и многие дистрибутивы Linux не настраивают его сразу. Надеюсь, что, следуя этому руководству, ваши проблемы с Bluetooth в Linux останутся в прошлом.

Технология Bluetooth сейчас получила широкое распространение. В основном, ее используют для подключения к смартфону каких-либо гаджетов – например, наушников или смарт-часов. Но в Linux есть и дополнительные возможности, которые реализовываются с ее помощью. Пользователь может подключить тот же смартфон к компьютеру, передавать и принимать файлы, производить подключение к сети Интернет. А вот о том, как все это настроить в репозитории Ubuntu 19.04, я сегодня и расскажу. 

• Первичная настройка
• Сканирование устройств Bluetooth
• Сопряжение устройств
• Отправка и прием файлов
• Подключение к Интернету по Bluetooth

Первичная настройка

В первую очередь надо позаботиться о наличии специального адаптера Bluetooth – в большинстве современных ноутбуков он встроен, а вот для стационарных ПК придется приобретать отдельный USB модуль. Еще требуется наличие специальных прошивок и утилит в системе Linux. Вообще, если зайти в раздел «Настройки» Ubuntu 19.04, можно увидеть соответствующий раздел Bluetooth.

Как можно видеть на скрине, пока я не подключу адаптер, включить данную функцию мне не удастся. 

Если в настройках системы такого пункта нет, необходимо установить специальную утилиту. Для этого я открываю командную строку «Терминал» и даю следующий запрос на установку утилиты Blueman:

sudo apt-get install blueman

Если не сработает (а она сработает), можно дать вот такую команду на установку соответствующего программного обеспечения:

sudo apt-get install bluetooth bluez bluez-tools

После завершения процесса установки следует перезагрузить операционную систему. Если адаптер был подключен, при загрузке в области уведомлений должен отобразиться значок менеджера Bluetooth. 

Перед тем как начать сканирование, нужно проверить, правильно ли подключен адаптер и не блокируется ли он с помощью утилиты rfkill. Чтобы активировать ее, я ввожу в командной строке «Терминал» следующий запрос:

sudo rfkill list 

Если в отчете будет отображено, что адаптер не работает из-за аппаратной или программной блокировки, можно будет провести разблокировку, введя вот такую команду:

sudo rfkill unblock bluetooth

После этого обязательно включаю адаптер вот таким запросом:

sudo hciconfig hci0 up

И как только данная процедура будет завершена, можно приступать к сканированию. Перед этим проверю, включен ли Bluetooth модуль на другом устройстве и не находится ли он в скрытом режиме. 

sudo hcitool scan

После завершения сканирования отобразится имя устройства и его MAC адрес. А чтобы узнать более подробную информацию о нем, использую утилиту sdptool:

sdptool browse [тутдолженбытьMACадрес]

А вот с помощью утилиты ping можно проверить доступность удаленного устройства. Выглядеть команда при этом будет примерно вот так:

sudo l2ping [тутдолженбытьMACадрес]

Если действовать через настройки, тут все будет намного проще. Нужно просто запустить поиск, и в результате отобразится список доступных устройств. 

Сопряжение устройств

На старых версиях операционной системы Ubuntu сопряжение с устройствами по Bluetooth производилось с помощью специальной утилиты RFCOMM. В моем случае она не была обнаружена, поэтому просто привожу пример, так как у некоторых пользователей она может сработать. Синтаксис команды в данном случае будет выглядеть вот так:

sudo rfcomm connect [устройствоадаптера] [MACадрес] [канал] 

После этого на устройстве, с которым производится подключение, высветится окно с запросом на соединение. На обоих устройствах в этот момент необходимо ввести одинаковый код. 

В случае с настройками все куда проще – надо просто найти нужное устройство по имени, подключиться в нему и ввести тот же код. Практически, все то же самое, но в графическом виде. 

Отправка и прием файлов

Отправить файл на удаленное подключенное устройство можно с помощью протокола OBEX и использования опции -p. При этом запрос в командной строке в подобном случае будет выглядеть следующим образом:

sudo bt-obex -p [MACадресустройства] /путькфайлу/файл.формат

После нажатия на кнопку Enter выбранный файл с компьютера будет отправлен. А вот чтобы получить файл, нужно применить уже другую опцию -s.

bt-obex -s /путьдлясохраненияфайла/раздел/папка

Чтобы посмотреть файлы, которые есть в памяти подключенного устройства, нужно использовать следующий синтаксис:

sudo bt-obex -f [MACадрес]

Подключение к Интернету по Bluetooth

Да, по беспроводной сети Bluetooth можно подключиться к сети Интернет, и соединение такого типа называется Dial-up. Ранее данная технология была очень распространена, но сейчас ее редко кто использует из-за наличия Wi-Fi. Чтобы подключиться к сети мобильного устройства, можно использовать два протокола – старый DUN и современный BNEP, схожий по принципу действия с локальной сетью. 

Сначала еще надо определить, поддерживает ли устройство работу по этим протоколам. Проверяю первый – для этого использую утилиту rfcomm и канал 15. 

sudo rfcomm bind [MACадрес] 15

Если все же поддерживается, на экране появится устройство rfcomm0. Дальше для соединения можно использовать NetworkManager. 

Все процессы обрабатываются через bluez и тот самый менеджер подключений. Просто добавляю новый тип соединения в программе, выбираю соответствующую сеть, просматриваю информацию о ней и начинаю использование. 

Заключение

В Ubuntu подключение к стороннему устройству по Bluetooth можно настроить как с помощью командной строки «Терминал», так и через раздел «Настройки». Если это ноутбук, то приобретать дополнительный адаптер не придется – достаточно будет просто активировать функцию, найти нужное устройство и подсоединиться к нему. В ином случае нужно будет приобретать отдельный USB адаптер, но даже в таком случае проблем в программном плане возникнуть не должно.

Post Views: 32 244

Introduction

Bluetooth is a widely supported local area communications technology for communications with cellphones, headsets, keyboards, mice, PDAs, and storage devices. See also BluetoothRemoteControl and BluetoothAudio on Ubuntu.

Requirements

For a desktop or laptop without Bluetooth support use a Bluetooth dongle that connects through USB. While adapters can be found all over the web some do not work well with free software systems. The free software foundation recommends users purchase hardware with free drivers. Most cards are not clearly marked. ThinkPenguin.com is an exception and explicitly provide support for Ubuntu and other distributions. Alternatively users can investigate free software compatible bluetooth chipsets and try to locate a card based on this information.

For Dell laptops install the latest drivers from Dell’s website in Windows in order for the bluetooth module to work in Linux. (Required for D430 with Gutsy / Hardy and D830 and D630) (http://ubuntuforums.org/showthread.php?t=572335 https://wiki.ubuntu.com/LaptopTestingTeam/DellLatitudeD430#bluetooth)

For Dell laptops with a Dell Wireless 355 Bluetooth card where the card is turned off, reenable the card before installation. Go to a utility in Windows to turn it on before you can reinstall the driver. If you turn the card off in Windows reenable the card so Ubuntu can recognize it.

Installation and Configuration

Ubuntu 10.04 Install via the command line

sudo apt-get install bluez python-gobject python-dbus

python-gobject and python-dbus are needed for the python scripts in /usr/share/doc/bluez/examples/ to work.

cd  /usr/share/doc/bluez/examples/

Here are the scripts located. Discover the hciX location of the dongle with:

hcitool dev

Devices:
        hci0    00:11:95:00:1A:CF

Your Bluetooth device will have a different id.

sudo ./simple-agent hci0 XX:XX:XX:XX:XX:XX

XX:XX:XX:XX:XX:XX is the MAC or BT ADD or BlueTooth Address of the bt device. Press the reset or pair button on your keyboard, simple-agent will ask to specify a pin like 1111, then type that pin on the bt keyboard and your bt keyboard is paired.

sudo ./test-device trusted XX:XX:XX:XX:XX:XX yes

To set the device as trusted

#sudo /etc/init.d/bluetooth restart

To restart the bluetooth daemon.

Check if the device is added:

dmesg|tail

The last lines will list your device.

Ubuntu 11.04 Install via the command line

sudo apt-get install bluez python-gobject python-dbus

python-gobject and python-dbus are needed for the python scripts bluez-simple-agent and bluez-test-device to work.

Discover the hciX location of the dongle with:

hcitool dev

Devices:
        hci0    00:11:95:00:1A:CF

Your Bluetooth device will have a different id.

sudo bluez-simple-agent hci0 XX:XX:XX:XX:XX:XX

XX:XX:XX:XX:XX:XX is the MAC or BT ADD or BlueTooth Address of the bt device. Press the reset or pair button on your keyboard, simple-agent will ask to specify a pin like 1111, then type that pin on the bt keyboard and your bt keyboard is paired.

sudo bluez-test-device trusted XX:XX:XX:XX:XX:XX yes

To set the device as trusted

sudo /etc/init.d/bluetooth restart

To restart the bluetooth daemon.

Check if the device is added:

dmesg|tail

The last lines will list your device.

Found the method for 10.04 and 11.04 here: http://www.spinics.net/lists/linux-bluetooth/msg13445.html

Additionally, according to this thread (http://www.raspberrypi.org/phpBB3/viewtopic.php?f=27&t=6838), it may be necessary, after authenticating your keyboard, to run

sudo bluez-test-input connect XX:XX:XX:XX:XX:XX

to actually get the Bluetooth device to connect to the computer (I had to do this when using a Logitech Dinovo Edge with a generic Bluetooth adapter). After this, set the device to be trusted as above, and the connection should persist upon reboot.

Older documentation:

Before you begin open up the terminal and type the following:

sudo apt-get install bluez && sudo apt-get install bluez-utils

Restart the bluetooth server to ensure your pc can communicate with a bluetooth device

sudo /etc/init.d/bluetooth restart

By default the BlueTooth notification icon appears, although the service may not. If the service is not running try the service command, otherwise you can now connect.

For jaunty (9:04) and above verify you have a supported adapter connected. When the icon appears, right click and configure your preferences. Devices should auto connect to your PC where you configure your security options.

To configure mail for your phone, install the gnome-bluetooth package so the system finds it in the accessories menu. Send a file by right clicking the file and selecting Send-to. To automate, select System –> Preferences –> Sessions. Add a Startup program. For example you can name it, “Bluetooth File Transfer” and in the Command box, enter “gnome-obex-server”. Click OK.

Manual Discovery

Open a terminal window and install the required packages with their dependencies:

sudo apt-get install bluez-utils

Connect your Bluetooth device and restart the Bluetooth services:

sudo /etc/init.d/bluez-utils restart

Verify your Bluetooth device is detected along with the appropriate modules. View the lsusb (in case of usb device) output: lsusb output:

Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

Review the output of hcitool dev for all your system’s Bluetooth devices.

• hcitool dev output:

    Devices:
          hci0    00:11:95:00:1A:CF

Your Bluetooth device will have a different id.

• If the id is all zeros, restart the bluez-utils service and retry.

Setup Devices

Find Device Addresses

Locate the device address, make the device discoverable (a “Connect” button for keyboards and mice or check the manual) and search for the device by the following:

sudo hidd --search

(If that command doesn't work, try the following:)
  hcitool scan

Each device’s address has the aa:bb:cc:dd:ee:ff format. Hint: If no devices are shown for Edgy Eft (6.10), try the following:

  sudo hciconfig hci0 inqmode 0

See bug #70718. If this helps, you may add the hciconfig command (without “sudo”) to your /etc/rc.local file for a permanent workaround.

Connect Devices for Current Session Only

For a temporary connection, use the address of the device ‘aa:bb:cc:dd:ee:ff’

sudo hidd --connect aa:bb:cc:dd:ee:ff

You can now connect.

For a “Can’t create HID control channel: Connection refused” error, the discovery period timed out. Try again but enter the command more quickly.

Connect Devices at Startup

To connect automatically, edit the configuration file:

sudo cp /etc/default/bluetooth /etc/default/bluetooth_backup
sudo nano /etc/default/bluetooth

Locate line:

HIDD_ENABLED=0

Change it to:

HIDD_ENABLED=1

Look in the same file for a line close to:

HIDD_OPTIONS="--master --server"

Leave the “–master” command or remove it, it depends on the device. If you have problems with “–master”, remove it or vice versa.

Add additional “–connect” arguments for the device you want to connect to at startup:

HIDD_OPTIONS="--connect aa:bb:cc:dd:ee:ff --connect aa:bb:cc:dd:ee:ff --connect aa:bb:cc:dd:ee:ff --server"

Save and add HIDP to /etc/modules:

echo hidp | sudo tee -a /etc/modules

Your Bluetooth devices should now connect at startup.

Using Devices as Modems

Refer to page BluetoothDialup

Using audio devices

• Refer to page BluetoothAudio

• For Bluetooth Headsets specifically refer to BluetoothHeadset

Troubleshooting

“obex://[xx:xx:xx:xx:xx:xx]” is not a valid location.

If you receive this error in Gutsy enter the following:

sudo apt-get install gnome-vfs-obexftp

Although this gives “Couldn’t display “obex://[xx:xx:xx:xx:xx:xx]”.” for some. In this case try:

sudo hciconfig hci0 auth

See this forum thread for information.

Reset the adapter:

sudo hciconfig hci0 reset

The hcitool options can now connect and if often required despite an automatic connection setup.

bluez-gnome

Reboot after you install bluez packages even if your dongle is recognized after installation. 2/8/2009 bluez-gnome bug:

• https://bugs.launchpad.net/ubuntu/+source/bluez-gnome/+bug/285007

Forum page: http://ubuntuforums.org/showthread.php?p=6438656#post6438656

CategoryBluetooth CategoryNetworking

With the increasing prevalence of Bluetooth peripherals such as mice, keyboards, and headsets, it can be difficult to imagine using the wired versions of these devices sometimes. On some Linux distributions, Bluetooth is set up perfectly for you straight out of the box. Distributions like Ubuntu and Elementary make it easy for you to get Bluetooth set up and working on your machine. However, other distributions like Fedora and Arch Linux require you to do some setup before you’re able to fully enjoy the benefits of Bluetooth on your machine. Here is how you can set up Bluetooth in Linux.

How to Set Up Bluetooth on Your Linux Machine

The steps will vary a little across distributions, but the basic steps are the same. If your distribution doesn’t already have Bluetooth set up for you, you will first need to install Bluez, which contains the driver stack for Bluetooth adapters as well as utilities for the CLI administration of Bluetooth.

After installing Bluez, you may need to install a Bluetooth manager. Some desktop environments have built-in Bluetooth managers. For example, KDE Plasma has the KDE Bluetooth client. Gnome also has a built-in client. If you are using a desktop environment that doesn’t have a built-in client, you can install the Blueman client.

How to Install Bluez

Below are instructions on how to install Bluez on a few different distributions.

Debian and Ubuntu

OpenSUSE

With OpenSUSE, you have to install bluez with the Open Build Service.

Fedora

sudo dnf install bluez bluez-tools

Arch Linux

sudo pacman -S bluez bluez-utils

Other Package Managers

Bluez works with all Linux distributions. If you have a different package manager than the distributions above, have no fear. You will just need to search for bluez in your package manager, then install everything that includes the term bluez.

How to Install Blueman

Find out how to install Blueman on various Linux distributions below.

Debian and Ubuntu

OpenSUSE

sudo zypper install blueman

Fedora

Arch Linux

Other Distributions

To install Blueman on your Linux distributions, you should search the package manager in the distribution being used for Blueman, then install all of the relevant packages.

Enable Bluetooth

After installation, you will need to activate and start the Bluetooth service. If you are using a Bluetooth dongle, you will first have to run the following command:

To enable the Bluetooth service, run the following command:

sudo systemctl enable bluetooth.service

To start the Bluetooth service, use this command:

sudo systemctl start bluetooth.service

After doing this, you’ll be able to start using Bluetooth on your system.

Connect to Devices Using Blueman

The connection process will vary depending on the desktop manager you’re using. However, we show how it’s done using Blueman since it’s fairly representative of the process across the board.

To connect to a device, open “Bluetooth Manager” in your applications and hit search. Make sure that the device you want to connect to is discoverable. When you see it in the device list, right-click on it and hit “Connect.” You may have to enter a passcode, but this information will be in the user’s manual of your device.

Set up Bluetooth Devices in GNOME Linux

Gnome comes with Bluetooth support from the start, and you can easily set up Bluetooth devices without installing any other tools.

1. Click on the status icons on the top-right corner of your screen. Doing this will bring up a small menu where you can choose how your machine connects to the network.

1. Click on the “Bluetooth” entry to bring up a drop-down menu where you can choose to toggle Bluetooth or access the appropriate settings for it. Choose to access the Settings.

1. The Bluetooth Settings window will display all the devices that you can connect to. In this example, I can select my phone to pair it with my machine.

1. GNOME will display a window showing a six-digit PIN that you need to match with your device to ensure that you are pairing the right devices together.

One important thing to note, however, is that the six-digit PIN will only show up on non-peripheral devices, as GNOME will automatically pair with any Bluetooth keyboard and headphones.

Connect to Bluetooth Devices in KDE Plasma

It is also possible to set up Bluetooth out of the box through the Plasma desktop in Linux.

1. Click the Bluetooth icon in the lower-left corner of your screen to bring up a small menu where you can configure how Bluetooth works in your machine.

1. Click the “+ Add New Device…” button in the middle of the window.

1. Plasma will start its Bluetooth discovery program and search for every active nearby device and will list all found devices in a small window.

1. Select your device and press “Next” to start the Bluetooth pairing process. Plasma will display a small window with a six-digit PIN that you need to match with your device.

Set Up the Bluetooth CLI Utility in Linux

It is also possible to connect a device through a dedicated Bluetooth CLI utility, a program that comes with Bluez that allows you to pair and control devices straight from your command line. It can be especially useful for devices that do not have a display, such as Raspberry Pi.

1. Run the bluetoothctl program to load the Bluez CLI utility. This will change your prompt to [bluetooth]#.

1. Start the internal Bluetooth transmitter by powering it on:

1. Tell the transmitter to scan for any active Bluetooth device in the area by running these two commands:

1. Look for the device you want to pair with your computer by telling the transmitter to list all the devices that it detected during the scan:

1. Use the MAC address of your device to pair it with your computer by running these two commands:

pair [MAC address]
connect [MAC address]

One important thing to note, however, is that unlike the methods described above you need to type the PIN displayed on the device.

Frequently Asked Questions

Image credit: Unsplash, altered by Ramces Red. All screenshots by Ramces Red