Manjaro bluetooth

Manjaro bluetooth DEFAULT

Bluetooth stopped working

Hi and I hope I am at the right place here:
I checked out all forum posts and the wiki already and I somehow cannot find a solution therefore I had to create an account. Sorry if this is something simple I just overlooked or so…

I set up the AutoEnable feature a few weeks ago and after the recent manjaro update I was pretty happy about my bt keyboard finally working as intended.

Today, it all stopped working and I do not know why.

I followed the wiki regarding the grub settings (bluetoothctl:_No_default_controller_available) because I somehow managed to start the service at some point but I had no controller set up, still nothing though.

bluez and bluez-utils are installed.

Also tried the following as suggested in another topic…

Also I cannot connect any Gamepads via USB anymore. Feels like something f*ed up my mainboard controller or so. I dunno…

I hope somebody can help me.

btusb module does not load on startup.
Loading the module and starting the service gives me the following status:

But no controller is available:


Bluetooth not working

im having similar issues if you can help.

sudo systemctl status bluetooth -l
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendo
Active: active (running) since Wed 2017-05-17 20:16:00 BST; 1h 24min ago
Docs: man:bluetoothd(8)
Main PID: 603 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 4915)
CGroup: /system.slice/bluetooth.service
└─603 /usr/lib/bluetooth/bluetoothd

May 17 21:29:09 anthony-pc bluetoothd[603]: Failed to set mode: Failed (0x03
May 17 21:35:54 anthony-pc bluetoothd[603]: Endpoint registered: sender=:1.3
May 17 21:35:54 anthony-pc bluetoothd[603]: Endpoint registered: sender=:1.3
May 17 21:36:14 anthony-pc bluetoothd[603]: Failed to set mode: Failed (0x03
May 17 21:36:27 anthony-pc bluetoothd[603]: Failed to set mode: Failed (0x03
May 17 21:36:37 anthony-pc bluetoothd[603]: Failed to set mode: Failed (0x03
May 17 21:36:49 anthony-pc bluetoothd[603]: Endpoint unregistered: sender=:1
May 17 21:36:50 anthony-pc bluetoothd[603]: Endpoint unregistered: sender=:1
May 17 21:37:02 anthony-pc bluetoothd[603]: Failed to set mode: Failed (0x03
May 17 21:37:12 anthony-pc bluetoothd[603]: Failed to set mode: Failed (0x03
lines 1-20/20 (END)

rfkill list
0: ideapad_wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
1: ideapad_bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

  1. Songfacts app
  2. Fortigate import certificate
  3. Log2 2 3
  4. Eso scp

Using bluetooth on the Manjaro XFCE

Hey guys.

I’m not able to use bluetooth on the Manjaro XFCE.

When i start the system, blueman-applet, blueman-mechanism and blueman-tray start up. According to the task manager.

Then I try to open the Bluetooth Manager - blueman-manager - and the output is:

After some research I read about putting acer_wmi on the blacklist because of the model of my card - Qualcomm Atheros AR9485 Wireless Network Adapter - and the issue of coexistence between Wifi and bluetooth on the same card.

So following the tips I created the files in /etc/modprobe.d/



And run the commands

sudo modprobe -r acer_wmi
sudo modprobe btusb
sudo systemctl start bluetooth.service
sudo systemctl enable bluetooth.service

And finally the status according to the command systemctl status bluetooth was this:

Apparently works but when I run the blueman-manager command the output is

I already tried to restart.
I’ve tried liveusb with Manjaro KDE, Gnome, and other distros.
I’ve tried restarting with systemctl restart bluetooth.service
And it always gives the same result. Did not work.

In the research I did and the help I got from the community, I saw that several people managed to solve it by following these steps.

can you help me? Did you try anything else? Am I forgetting something?

Some information about the system



lsmod | grep btusb


inxi -Fazy

Manjaro RTL8821CE WI-FI/Bluetooth adapter fix


Related articles

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.


  1. Install the bluez package, providing the Bluetooth protocol stack.
  2. Install the bluez-utils package, providing the utility. Alternatively install bluez-utils-compatAUR to additionally have the deprecated BlueZ tools.
  3. The generic Bluetooth driver is the kernel module. Check whether that module is loaded. If it's not, then load the module.
  4. Start/enable.
  • By default the Bluetooth daemon will only give out bnep0 devices to users that are a member of the group. Make sure to add your user to that group if you intend to connect to a Bluetooth tether. You can change the group that is required in the file .
  • Some Bluetooth adapters are bundled with a Wi-Fi card (e.g. Intel Centrino). These require that the Wi-Fi card is firstly enabled (typically a keyboard shortcut on a laptop) in order to make the Bluetooth adapter visible to the kernel.
  • Some Bluetooth cards (e.g. Broadcom) conflict with the network adapter. Thus, you need to make sure that your Bluetooth device gets connected before the network service boot.
  • Some tools such as hcitool and hciconfig have 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-compatAUR. See FS#53110 and the Bluez mailing list for more information.



  • bluetoothctl — Pairing a device from the shell is one of the simplest and most reliable options. || bluez-utils

Tip: To automate bluetoothctl commands, use or .


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

  • GNOME Bluetooth — GNOME's Bluetooth tool.
    • gnome-bluetooth provides the back-end
    • 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 command.
    • You can also launch the command directly to send files to a remote device.
    • nautilus-bluetoothAUR 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 ). ||
  • 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. || 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. || blueberry
  • Blueman — A full featured Bluetooth manager. || blueman
  • ObexFTP — A tool for transferring files to/from any OBEX enabled device. || obexftpAUR


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 .

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

  1. (optional) Select a default controller with .
  2. Enter to turn the power to the controller on. It is off by default and will turn off again each reboot, see #Auto power-on after boot.
  3. Enter to get the MAC Address of the device with which to pair.
  4. Enter device discovery mode with command if device is not yet on the list.
  5. Turn the agent on with or choose a specific agent: if you press tab twice after 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 should be appropriate in most cases.[1]
  6. Enter 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 to do so.
  8. Enter to establish a connection.

An example session may look this way:

# bluetoothctl[NEW] Controller 00:10:20:30:40:50 pi [default] [bluetooth]# agent KeyboardOnlyAgent registered [bluetooth]# default-agentDefault agent request successful [bluetooth]# power onChanging power on succeeded [CHG] Controller 00:10:20:30:40:50 Powered: yes [bluetooth]# scan onDiscovery started [CHG] Controller 00:10:20:30:40:50 Discovering: yes [NEW] Device 00:12:34:56:78:90 myLino [CHG] Device 00:12:34:56:78:90 LegacyPairing: yes [bluetooth]# pair 00:12:34:56:78:90Attempting 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:90Attempting 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 manually on your Linux install, so that they match in both systems.


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.

For Windows

Tango-inaccurate.pngThe factual accuracy of this article or section is disputed.Tango-inaccurate.png

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

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

Download PsTools, and extract .

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:


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 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 same way.

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. Alternatively, you may double click on a binary value, and copy the device key in hex.

If there are , , and values present, this is a Bluetooth 5.1 device, and these too must be saved.

Note: If your Windows partition is encrypted with Bitlocker, you won't 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

Inside the environment, run

> cd CurrentControlSet\Services\BTHPORT\Parameters\Keys

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:

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

Now get your device's key through :

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

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] 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]

Of these values, you must save , , and .

Preparing Bluetooth 5.1 Keys

If there were , , and values in the registry for the desired device, they must be converted for use with Linux. corrsponds to , to , to . The value shound be reversed and converted to decimal. For example:

  • An of makes for a of .
  • An of makes for a of .
  • An of makes for an of .
Note:You can use this Pythoncode to do the conversion: >>> ERand=' 63 02 84 B8 5D 40 44 DF ' >>> ERand=list(reversed(ERand.strip().split())) >>> int("".join(ERand), 16) 16088054540146049635

For macOS

Boot into macOS, then open a terminal.

  • If you are on Sierra or older, run
$ sudo defaults read /private/var/root/Library/Preferences/blued.plist LinkKeys > ~/bt_keys.txt
  • If you are on High Sierra or newer, run
$ sudo defaults read /private/var/root/Library/Preferences/ LinkKeys > ~/bt_keys.txt

For older versions of macOS (High Sierra and older) you will have to reverse the keys. For example, becomes .

Copy the file to a drive that can be read from Arch Linux. Reboot into Arch Linux.

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

Edit the file and change the key under . E.g.:


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

Then restart and (with ).

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.


Auto power-on after boot

By default, the Bluetooth adapter does not power on after a reboot, you need to add the line in the configuration file at the bottom in the section:

/etc/bluetooth/main.conf[Policy] AutoEnable=true

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-keyboardmousewakeup.rulesSUBSYSTEM=="usb", ATTRS{idVendor}=="8087", ATTRS{idProduct}=="0039" RUN+="/bin/sh -c 'echo enabled > /sys$env{DEVPATH}/../power/wakeup;'"


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.


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: . With a default PulseAudio installation you should immediately be able to stream audio from a Bluetooth device to your speakers.

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

/etc/pulse/ load-module module-bluetooth-policy load-module module-bluetooth-discover ...


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


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-gitAUR, start (and enable) the service, and add your user to the group.

Run the following command to check if everything is working as intended (replace and 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 :

~/.asoundrcdefaults.bluealsa { service "org.bluealsa" device "XX:XX:XX:XX:XX:XX" profile "a2dp" }

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

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 as described above.

Install bluez-rfcommAUR and bluez-utils-compatAUR, as they provide 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 for serial communication:

picocom /dev/rfcomm0 -b 115200


Tango-view-refresh-red.pngThis article or section is out of date.Tango-view-refresh-red.png

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


In order to debug, first stop.

And then start it with the parameter:

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

Another option is via the 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-compatAUR package provides an alternative version of bluez-utils with the deprecated tools.


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 as root when you have plugged in the USB dongle (or inspecting ). 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]# infoIndex 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 hci0Selected index 0 [hci0]# power uphci0 Set Powered complete, settings: powered connectable discoverable bondable ssp br/edr le secure-conn [hci0]# infohci0: 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


# bluetoothctl [bluetooth]# showController 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]# showController 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 which is part of the . You can get a list of available devices and their identifiers and their MAC address by issuing:

$ btmgmt infoIndex 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 . (bluez-utils-compatAUR)

$ hciconfig -a hci0hci0: 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:

$ lsusbBus 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 has a regression bug, and currently only works in the kernel version ≤ 3.9.11. There is a patch available for newer versions. 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

This error may happen if the device is 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-compatAUR 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 is a potential solution. See also Red Hat Bugzilla – Bug 1573562.

systemd: Condition check resulted in Bluetooth service being skipped

only requires the directory to exist, which should be created by kernel module , which is only autoloaded by if it actually finds a working Bluetooth hardware device.

If your does not exist, check if your kernel Bluetooth module is loaded by . If not, and you believe you have a Bluetooth device, you can try manually starting them by loading the Bluetooth module and restarting.

You should also load your corresponding kernel Bluetooth driver when loading the module, most likely , but can also be etc.

Check 's unit status to see whether it started.

See also Debian Bug report logs - #853207.

If started successfully, but there is chance that you still cannot use Bluetooth normally (e.g. says something like when you ). If this happens, try rebooting your computer, and double-check: whether directory exists; whether includes correct Bluetooth modules; log messages in the journal; etc. 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 and in .

If the computer still does not show up, try changing the device class in 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, in gets overridden after device initialization, so set the class directly with .

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 (the soundbar class) will make such devices appear.

See 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. The firmware is not provided but 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 ...


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 .

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 (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, so it can be extracted using unrar x. To find out which of the many .hex files is the right one for you, look in the file and search for , where 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 - 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 connect with an error in journal

If you see a message like the following in the journal while trying to connect to a device:

a2dp-source profile connect failed for 9C:64:40:22:E1:3F: Protocol not available

try installing pulseaudio-bluetooth and restarting PulseAudio. This error can manifest even while using only file transfer.

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-compatAUR, then start 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 onDiscovery started [CHG] Controller (MAC) Discovering: yes

In another terminal:

# hcitool lescan

Wait until your device shows up, then 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 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 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

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

Bluetooth mouse laggy movements

Try edit the file ( - your Bluetooth adapter MAC-address, - your mouse MAC-address) and add those lines:

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

You can see your local adapter MAC address by running command , your can see MAC addresses of currently connected remote devices by running command

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 [2] this issue, open , remove the following lines, and restart :

[IdentityResolvingKey] Key=...

See the relevant discussion on the Arch forum.

Problems with some Bluetooth drivers in kernel 5.10

Tango-edit-cut.pngThis section is being considered for removal.Tango-edit-cut.png

Reason: The issue is supposedly fixed. (Discuss in Talk:Bluetooth)

Starting with v5.10, some Qualcomm Atheros Bluetooth chipset drivers have stopped working with the following error:

# journalctl --grep=hci0Feb 22 18:40:24 user kernel: Bluetooth: hci0: do not support firmware rome 0x31010000

See the relevant bug report on the Bugzilla.

You can either rebuild the modules with the applied patches (btusb-210681-fix), or use an old (5.9.x) kernel. This bug was fixed in linux 5.11.arch2-1.

See also


Bluetooth manjaro

Bluetooth implementation in Manjaro Linux can occur via two different sets of packages. First is Bluez, which offers Bluetooth stack implementation in all Linux distributions. Bluez provides drivers and various command-line utilities to administer Bluetooth. Whereas the second method is via desktop tools or GUI packages to manage these devices. Similarly, to use audio equipment, users need to install an additional pulseaudio-bluetoothpackage.

In other words, Bluetooth functionality in Manjaro or any Linux distributions results due to various interacting modules that include hardware drivers, client applications, kernel, bluez, and pulseaudio. Hence, troubleshooting Bluetooth problems in Manjaro is a daunting task.

In this article, we discuss some of the most common Bluetooth connection problems and present effective solutions.

Getting Started

Before beginning to troubleshoot Bluetooth device connection problems, confirm Bluetooth connection and adapter settings.

Verify that the Bluetooth adapter/device is not blocked via the following command:

[[email protected]:~]$ sudo rfkill list
: ideapad_bluetooth: Bluetooth
       Soft blocked: no
       Hard blocked: no

The above output illustrates that the adapter is unblocked. On the contrary, scenario, use the following command to unblock the adapter.

[[email protected]:~]$ sudo rfkill unblock bluetooth

Lastly, verify if the Bluetooth service is enabled and active.

[[email protected]:~]$ sudo systemctl status bluetooth

Bluetooth not available after Sleep/Startup

Bluetooth gets disable after the restart, sleep or hibernate. This process causes the user to re-enable every time from the taskbar or CLI. As soon as the system resumes (before manually enabling Bluetooth), use the above-mentioned command rfkill to verify adapter settings. If the command output is similar to the above, it confirms that the issue is not with the driver.

One of the root causes can be a bug in the old versions of bluez 4.49, 4.50, etc. It also causes unusual behavior during Bluetooth connection, disconnection, and pairing processes.

Use the following command in the terminal to check the current version details of bluez:

[[email protected]:~]$ sudo pacman -Qi bluez| grep "^Version:"

Update the Manjaro repository and update the bluez to its latest version.

[[email protected]:~]$ sudo pacman -Sy bluez

The version update resolves the Bluetooth access problem after suspension. It also improves system behavior during Bluetooth pairing, connection, and other settings.

Bluetooth Headset Playing HSP/HFP Not A2DF

Another common Bluetooth problem is that the headsets only play low-quality audio for phone calls instead of high-quality audio playback (music). To troubleshoot this problem, make sure the system identifies the right Bluetooth device in the configuration file.

Before that, verify all the required dependencies are available in the system.

[[email protected]:~]$ sudo pacman -Sy pulseaudio pulseaudio-utils pavucontrol pulseaudio-module-bluetooth

After verification, edit or create the audio configuration file in the /etc/bluetooth directory, to include the following lines:

[[email protected]:~]$ sudo vim /etc/bluetooth/main.conf
 #This section contains general options

Save the above file and restart the Bluetooth service.

[[email protected]:~]$ sudo service bluetooth restart

A2DP not compatible with PulseAudio

Sometimes PulseAudio fails to switch from low-quality audio to A2DP. That occurs due to the socket interface problem. The problem happens with the PulseAudio and bluez versions that are above 3.0 and 4.1.

To troubleshoot, disable the Socket option in the main.conf file in the /etc/bluetooth directory.

#This section contains general options

Bluetooth Device Connects and Disconnect

Another problem that Manjaro Bluetooth users face is that the device fails to connect or disconnect after a few moments of connection. Use the journalctl command to check the error logs:

The above error occurs in dual boot systems, not in standalone Manjaro installation. That means the device has already paired with another operating system via a Bluetooth adapter.

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

Whenever the Bluetooth device pairs, the service generates pairing keys. The system stores the device MAC address and the keys. Similarly, the device also stores the system’s MAC address and the matching key.

However, the MAC addresses for both OSs in the system are the same. When the Bluetooth device re-pairs, it overwrites the previous key with the new one. Hence, some devices can not handle pairing twice with the same MAC address or adapter.

Use the following step-by-step instructions to troubleshoot this problem:

Boot into the Windows OS and pair all the devices

Now reboot into the Manjaro Linux and pair all the devices.

Now extract to the Windows pairing keys, switch off the Bluetooth devices to avoid connection attempts.

Go to the command-line terminal to install the chntpw utility

[[email protected]:~]$ sudo pacman -Sy chntpw

Use the following command to mount Windows system drive

[[email protected]:~]$ cd /[path_to_windows_system]/Windows/System32/config

Now chntpw -e SYSTEM to get inside the chntpw environment to run

> cd ControlSet001\Services\BTHPORT\Parameters\Keys

Now ls to get Bluetooth adapter MAC address

Node has 1 subkeys and 0 values
  key name

Now cd into the [bluetooth-adapter-mac-address] folder to list existing MAC address devices.

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

Use hex to get the device keys.

> hex xxxxxxxxxxxx

The XX’s in the above output is the pairing keys. Now note which device maps to with which key.

Add the pairing key to the Manjaro configuration entries:

Change user to root: su

cd into the Bluetooth configuration folder /var/lib/bluetooth/[bluetooth_MAC_Add], such that each paired device has a separate configuration file. To pair each device with both OSs, add Windows Manjaro and Windows, open the configuration file for each device, and add the Windows pairing key under the [LinkKey] option.


Save the files and restart the services:

[[email protected]:~]$ sudo systemctl restart bluetooth.service
[[email protected]:~]$ pulseaudio -k


In this tutorial, we demonstrate troubleshooting various Bluetooth connection problems in Manjaro Linux. The issues discussed are the most commonly faced problems by new Manjaro users. The article also resolves the most commonly occurring Bluetooth connection problem in a dual boot system.

How to Use Bluetooth on Arch Linux

He felt that the magic fog in his head was thickening, and at the same time the inevitability of the coming moment. Another moment, and a powerful impulse pierced his testicles. The young seed rushed into the mouth of the eagerly accepting, at the same time orgasmic woman in a stormy stream. Natalya Vladimirovna, in a sweet mist, felt how the boy's penis began to pump thick sperm into her mouth, and lustfully.

You will also like:

In my pocket. She was no longer a virgin. But she didn't give it to the ass, and then she added booze, saw enough of her ex's flirting and dragged me back to.

451 452 453 454 455