Failed to start discovery org bluez error inprogress

I have the same problem.

2022-08-16 18:17:16.169 DEBUG (MainThread) [homeassistant.components.bluetooth] Stopping bluetooth discovery
2022-08-16 18:17:16.172 ERROR (MainThread) [homeassistant.components.bluetooth] Error stopping scanner: [org.bluez.Error.InProgress] Operation already in progress
2022-08-16 18:17:16.173 DEBUG (MainThread) [homeassistant.components.bluetooth] Initializing bluetooth scanner with {‘scanning_mode’: ‘active’}
2022-08-16 18:17:16.173 DEBUG (MainThread) [homeassistant.components.bluetooth] Starting bluetooth scanner
2022-08-16 18:22:16.177 INFO (MainThread) [homeassistant.components.bluetooth] Bluetooth scanner has gone quiet for 0:05:00, restarting
2022-08-16 18:22:16.178 DEBUG (MainThread) [homeassistant.components.bluetooth] Stopping bluetooth discovery
2022-08-16 18:22:16.180 ERROR (MainThread) [homeassistant.components.bluetooth] Error stopping scanner: [org.bluez.Error.InProgress] Operation already in progress
2022-08-16 18:22:16.181 DEBUG (MainThread) [homeassistant.components.bluetooth] Initializing bluetooth scanner with {‘scanning_mode’: ‘active’}
2022-08-16 18:22:16.181 DEBUG (MainThread) [homeassistant.components.bluetooth] Starting bluetooth scanner

Logger: homeassistant.components.bluetooth
Source: components/bluetooth/init.py:422
Integration: Bluetooth (documentation, issues)
First occurred: 16:27:15 (32 occurrences)
Last logged: 19:02:16

Bus 002 Device 004: ID 0b05:190e ASUSTek Computer, Inc. ASUS USB-BT500
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub

systemctl restart bluetooth:

● bluetooth.service — Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2022-08-16 19:09:24 CEST; 2s ago
Docs: man:bluetoothd(8)
Main PID: 635646 (bluetoothd)
Status: «Running»
Tasks: 1 (limit: 9298)
Memory: 984.0K
CGroup: /system.slice/bluetooth.service
└─635646 /usr/libexec/bluetooth/bluetoothd

aug 16 19:09:24 homeassistant systemd[1]: Starting Bluetooth service…
aug 16 19:09:24 homeassistant bluetoothd[635646]: Bluetooth daemon 5.55
aug 16 19:09:24 homeassistant systemd[1]: Started Bluetooth service.
aug 16 19:09:24 homeassistant bluetoothd[635646]: Starting SDP server
aug 16 19:09:24 homeassistant bluetoothd[635646]: Bluetooth management interface 1.18 initialized
aug 16 19:09:24 homeassistant bluetoothd[635646]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
aug 16 19:09:24 homeassistant bluetoothd[635646]: sap-server: Operation not permitted (1)
aug 16 19:09:24 homeassistant bluetoothd[635646]: Endpoint registered: sender=:1.64 path=/MediaEndpoint/A2DPSink/sbc
aug 16 19:09:24 homeassistant bluetoothd[635646]: Endpoint registered: sender=:1.64 path=/MediaEndpoint/A2DPSource/sbc
aug 16 19:09:26 homeassistant bluetoothd[635646]: Loading LTKs timed out for hci0

Only a full Bluetooth reset can temporarily solve the problem:

hciconfig hci0 down
rmmod btusb
modprobe btusb
hciconfig hci0 up

I am having problems getting bluetooth to work.

# uname -a
Linux alpine 4.19.98-0-vanilla #1-Alpine SMP Thu Jan 23 10:17:11 UTC 2020 x86_64 Linux

As you can see, hciconfig shows that the adapter is up:

# hciconfig hci0
hci0:   Type: Primary  Bus: USB
    BD Address: 5C:F3:70:62:65:B6  ACL MTU: 1021:8  SCO MTU: 64:1
    UP RUNNING 
    RX bytes:2144 acl:0 sco:0 events:91 errors:0
    TX bytes:1111 acl:0 sco:0 commands:75 errors:0

bluetoothctl shows all seems ok:

[bluetooth]# show
Controller 5C:F3:70:62:65:B6 (public)
    Name: BlueZ 5.54
    Alias: BlueZ 5.54
    Class: 0x00000000
    Powered: yes
    Discoverable: no
    DiscoverableTimeout: 0x000000b4
    Pairable: yes
    UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
    UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
    UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
    UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
    UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
    Modalias: usb:v1D6Bp0246d0536
    Discovering: no
Advertising Features:
    ActiveInstances: 0x00
    SupportedInstances: 0x05
    SupportedIncludes: tx-power
    SupportedIncludes: appearance
    SupportedIncludes: local-name

But whenever I attempt to enable scan I get the same error:

[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress

dmesg shows a timeout with the tx command:

# dmesg | grep Bluetooth
[    2.709741] Bluetooth: Core ver 2.22
[    2.709758] Bluetooth: HCI device and connection manager initialized
[    2.709769] Bluetooth: HCI socket layer initialized
[    2.709771] Bluetooth: L2CAP socket layer initialized
[    2.709775] Bluetooth: SCO socket layer initialized
[    2.843398] Bluetooth: hci0: BCM: chip id 63
[    2.847554] Bluetooth: hci0: BCM: features 0x07
[    2.901177] Bluetooth: hci0: BlueZ 5.54
[    2.905321] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[    2.922080] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0a5c-21e8.hcd not found
[    9.240210] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    9.240211] Bluetooth: BNEP filters: protocol multicast
[    9.240214] Bluetooth: BNEP socket layer initialized
[  172.932277] Bluetooth: hci0: command 0x200b tx timeout
[ 1150.828537] Bluetooth: hci0: command 0x2005 tx timeout

Everything seems to be alive and kicking, but it just refuses to enable scan, no matter how many reboots, or restarting bluetooth service, or power off and power on the adapter.

Any suggestions ?

[РЕШЕНО]Не видится ни одно устройство bluetooth

# 4 года, 7 месяцев назад (отредактировано 4 года, 7 месяцев назад) Ноут не обнаруживает устройства bluetooth (аппаратно модуль работает, пользовался на opensuse). Рядом лежат колонки и смарт, друг друга отлично видят. Обнаружение естественно включено.
Искал через blueman и bluetoothctl
В настройках blueman видимость выбрана — всегда.

bluez и bluez-utils установлены. Сервис запущен

Устройство не заблочено

Пользователь в группу добавлен

dmesg | grep Bluetooth

ls -l /lib/modules/$(uname -r)/kernel/drivers/bluetooth

lsusb | grep Bluetooth

wifi на BCM43хх работает отлично

Если мне не изменяет память, то для данного девайса BCM43142A0 требуется firmware конкретно для 105b:e065
Смотри вывод — dmesg | egrep -i ‘blue|firm’ — если это так, то в выводе будет ругань.
# 4 года, 7 месяцев назад (отредактировано 4 года, 7 месяцев назад)

dima81
[ 4.348882] Bluetooth: hci0: BCM: chip id 70
[ 4.349874] Bluetooth: hci0: BCM: features 0x06
[ 4.365893] Bluetooth: hci0: arch
[ 4.365897] Bluetooth: hci0: BCM (001.001.011) build 0000
[ 4.366177] Bluetooth: hci0: BCM: Patch brcm/BCM.hcd not found
[ 6.453379] Bluetooth: hci0: command 0x1003 tx timeout

# 4 года, 7 месяцев назад (отредактировано 4 года, 7 месяцев назад)

indeviral
Она и есть, только отразиться ли это на работе?
Самой главной ошибки нету failed load firmware) Да и bluetoothctl матерился бы не в себя…

Источник

Bluetooth headset

Both A2DP and the less popular HFP/HSP are supported by the kernel as well as different sound servers. Although Bluetooth is infamous for being unreliable[1], many implementations have seen massive improvements, making it a somewhat less excruciating experience on well-established hardware like Intel Bluetooth chips.

Headset via PipeWire

PipeWire acts as a drop-in replacement for PulseAudio and offers an easy way to set up Bluetooth headsets. It includes out-of-the-box support for A2DP sink profiles using SBC/SBC-XQ, AptX, LDAC or AAC codecs, and HFP/HSP.

The daemon will be started automatically as a user service. Use pavucontrol or your desktop environment’s settings for configuration. For more information, see PipeWire#Bluetooth devices.

Headset via Bluez5/PulseAudio

This article or section is a candidate for merging with Bluetooth.

Install the pulseaudio-alsa , pulseaudio-bluetooth and bluez-utils packages, the last of which provides the bluetoothctl utility.

Configuration via CLI

Now we can use the bluetoothctl command line utility to pair and connect. For troubleshooting and more detailed explanations of bluetoothctl see the Bluetooth article. Run

to be greeted by its internal command prompt. Then enter:

Now make sure that your headset is in pairing mode. It should be discovered shortly. For example,

shows a device that calls itself «Lasmex LBT10» and has MAC address «00:1D:43:6D:03:26». We will now use that MAC address to initiate the pairing:

After pairing, you also need to explicitly connect the device (if this does not work, try the trust command below before attempting to connect):

If you are getting a connection error org.bluez.Error.Failed retry by killing existing PulseAudio daemon first:

Finally, if you want to automatically connect to this device in the future:

If everything works correctly, you now have a separate output device in PulseAudio.

You can now redirect any audio through that device using the «Playback» and «Recording» tabs of pavucontrol .

You can now disable scanning again and exit the program:

Setting up auto connection

To make your headset auto connect you need to enable PulseAudio’s switch-on-connect module. Do this by adding the following lines to /etc/pulse/default.pa :

Configuration via GNOME Bluetooth

You can use GNOME Bluetooth graphical front-end to easily configure your bluetooth headset.

First, you need to be sure that bluetooth.service systemd unit is running.

Open GNOME Bluetooth and activate the bluetooth. After scanning for devices, you can connect to your headset selecting it on the device list. You can directly access to sound configuration panel from the device menu. On the sound panel, a new sink should appear when your device is connected.

LDAC/aptX

LDAC/aptX codecs are supported as of PulseAudio 15.0. You can verify the codec you are using for connection as follows:

Troubleshooting

Bad sound / Static noise / «Muddy» sound

If you experience bad sound quality with your headset, it could in all likelihood be because your headset is not set to the correct profile. See #Switch between HSP/HFP and A2DP setting to solve the problem.

Selected audio profile, but headset inactive and audio cannot be redirected

Deceptively, this menu is available before the device has been connected; annoyingly it will have no effect. The menu seems to be created as soon as the receiver recognizes the device.

Make sure to run bluetoothctl as root and connect the device manually. There may be configuration options to remove the need to do this each time, but neither pairing nor trusting induce automatic connecting for me.

Pairing fails with AuthenticationFailed

If pairing fails, you can try enabling or disabling SSPMode with:

You may need to turn off BlueTooth while you run this command.

Pairing works, but connecting does not

You might see the following error in bluetoothctl:

To further investigate, check the unit status of bluetooth.service or have a look at the log as follows:

You might see a message like this:

This may be due to the pulseaudio-bluetooth package not being installed. Install it if it missing, then restart pulseaudio.

It can also be due to permission, especially if starting pulseaudio as root allows you to connect. Add your user to the lp group, then restart pulseaudio. See /etc/dbus-1/system.d/bluetooth.conf for reference.

If the issue is not due to the missing package, the problem in this case is that PulseAudio is not catching up. A common solution to this problem is to restart PulseAudio. Note that it is perfectly fine to run bluetoothctl as root while PulseAudio runs as user. After restarting PulseAudio, retry to connect. It is not necessary to repeat the pairing.

If restarting PulseAudio does not work, you need to load module-bluetooth-discover.

The same load-module command can be added to /etc/pulse/default.pa .

If that still does not work, or you are using PulseAudio’s system-wide mode, also load the following PulseAudio modules (again these can be loaded via your default.pa or system.pa ):

It is also possible there are no write permissions for the owner of /var/lib/bluetooth/ . If this is the case, you may get the device to work by removing and re-pairing it, but the issue will return after rebooting. Restoring write permissions fixes this issue:

Connecting works, but there are sound glitches all the time

This is very likely to occur when the Bluetooth and the WiFi share the same chip as they share the same physical antenna and possibly band range (2.4GHz). Although this works seamlessly on Windows, this is not the case on Linux.

A possible solution is to move your WiFi network to 5GHz so that there will be no interference. If your card/router does not support this, you can upgrade your WiFi drivers/firmware. This approach works on Realtek 8723BE and latest rtl drivers for this chip from AUR.

If nothing of the previous is possible, a less effective mitigation is to tweak the fragment size and the latency on PulseAudio output port, trying to compensate interference. Reasonable values must be chosen, because these settings can make the audio out of sync (e.g. when playing videos). To change the latency of the bluetooth headset’s port (e.g. to 125000 microseconds in the following example):

where the identifier of the card can be found with

The fragment size can be set in /etc/pulse/daemon.conf and takes effect after a restart of PulseAudio (for more details please see PulseAudio/Troubleshooting#Setting the default fragment number and buffer size in PulseAudio).

Perhaps it will help to add options ath9k btcoex_enable=1 to the /etc/modprobe.d/ath9k.conf (with the appropriate bluetooth adapter):

Connecting works, but I cannot play sound

Make sure that you see the following messages in your system log:

If you see a message similar to this, you can go on and investigate your PulseAudio configuration. Otherwise, go back and ensure the connection is successful.

This article or section is a candidate for merging with PulseAudio/Troubleshooting.

When using GDM, another instance of PulseAudio is started, which «captures» your bluetooth device connection. This can be prevented by masking the pulseaudio socket for the GDM user by doing the following:

On next reboot the second instance of PulseAudio will not be started.

It may happen that bluez wrongly considers an headset as not a2dp capable. In this case, search the index of the bluetooth device with

Among the output there should be a section related to the bluetooth headset, containing something similar to

To manually set the profile, run

where 2 is the index of the device retrieved through pacmd ls .

Connecting works, but the device does not show up in PulseAudio sinks

If the headphones connect successfully (which can be confirmed via bluetoothctl ) but do not show up as an output/input sink in pavucontrol , you can try adding the following policy to your Bluetooth configuration file /etc/bluetooth/main.conf :

Some users report that this has solved their problem.

Connecting works, sound plays fine until headphones become idle, then stutters

If the headphones play sound correctly until they become idle and then stutter on resume (e.g. because the sound is paused, or because no sound is played for a while), try disabling PulseAudio’s automatic sink/source suspension on idle.

Some user reports huge delays or even no sound when the Bluetooth connection does not send any data. This is due to the module-suspend-on-idle module, which automatically suspends sinks/sources on idle. As this can cause problems with headset, the responsible module can be deactivated.

To disable loading of the module-suspend-on-idle module, comment out the following line in the configuration file in use (

/.config/pulse/default.pa or /etc/pulse/default.pa ):

Finally restart PulseAudio to apply the changes.

UUIDs has unsupported type

During pairing you might see this output in bluetoothctl:

This message is a very common one and can be ignored.

PC shows device as paired, but is not recognized by device

This might be due to the device not supporting bluetooth LE for pairing.

Try setting ControllerMode = bredr in /etc/bluetooth/main.conf . See [3].

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:

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 adapter). You can fix this by re-pairing the device. Start by removing the device:

Then restart bluetooth.service , turn on your bluetooth adapter, make your device discoverable, re-scan for devices, and re-pair your device. Depending on your bluetooth manager, you may need to perform a full reboot in order to re-discover the device.

Apple AirPods have low volume

Create a drop-in file for bluetooth.service with the following contents:

Then, restart bluetooth.service , reload its configuration, and reconnect your headset.

Additionally, for AirPods Pro, disable the spatial audio and enable Mono in the settings of your iPhone.

This can also solve issues with some devices that are unable to be controlled through AVRCP.

Apple AirPods Pro working with PulseAudio as A2DP Sink but not with HSP/HFP

If you find that AirPods Pro are working with PulseAudio, but are incapable of using the HSP/HFP configurations (in pavucontrol‘s Configurations tab, usually listed as unavailable), try switching to pipewire-pulse .

Note that switching to pipewire-pulse (and restarting your computer or the appropriate user-level systemd services) should enable HSP/HFP, but may also disable A2DP. (When selecting A2DP Sink in the Configurations tab, the option is instantly deselected and becomes Off.) If you encounter this issue, try removing/renaming the /var/lib/bluetooth folder like so:

Re-pair your AirPods Pro (and other devices) afterwards. This should make all configurations (HSP/HFP and A2DP) available again and easily accessible from pavucontrol and pacmd.

HSP problem: the bluetooth sink and source are created, but no audio is being transmitted

You may be missing firmware or the SCO (audio protocol of HSP and HFP) routing might be wrong. See [4] — the firmware for BCM20702 can be installed via bcm20702a1-firmware AUR or bcm20702b0-firmware AUR .

Error: Failed to start discovery org.bluez.Error.InProgress

If your headset is discovered, but fails to connect with the error «Failed to start discovery org.bluez.Error.InProgress», install bluez-hciconfig AUR and run

where X is the identifier of your computer’s bluetooth device (typically 0).

You should then be able to connect following the steps in #Configuration via CLI.

High audio volume due to synchronization between headphones and PulseAudio

As of PulseAudio 15, «Absolute Volume» interlocks the audio volume of your headphones with PulseAudio, making it impossible to change one without the other. On some headphones, e.g. on the the Hoco W25, this may result in irritating loudness. To disable «Absolute Volume», edit /etc/pulse/default.pa and change the line

Switch between HSP/HFP and A2DP setting

This can easily be achieved by the following command where the card_number can be obtained by running pacmd list-cards .

For enabling automatic profile switching from A2DP to HSP when a recording stream appears without any role set, you can append auto_switch=2 to load-module module-bluetooth-policy in /etc/pulse/default.pa .

For more information about PulseAudio profiles, see PulseAudio Documentation.

A2DP not working with PulseAudio

Socket interface problem

If PulseAudio fails when changing the profile to A2DP with bluez 4.1+ and PulseAudio 3.0+, you can try disabling the Socket interface from /etc/bluetooth/main.conf by removing the line Enable=Socket and adding line Disable=Socket .

A2DP sink profile is unavailable

When the A2DP sink profile is unavailable it will not be possible to switch to the A2DP sink (output) with a PulseAudio front-end and the A2DP sink will not even be listed. This can be confirmed with pactl .

Trying to manually set the card profile with pacmd will fail.

This is known to happen from version 10.0 of PulseAudio when connecting to Bluetooth headphones via Bluedevil or another BlueZ front-end. See related bug report.

This issue also appears after initial pairing of Headphones with some Bluetooth controllers (e.g. 0a12:0001, Cambridge Silicon Radio ) which might default to the Handsfree or Headset — HS service and will not allow switching to the A2DP PulseAudio sink that requires the AudioSink service.

• For some headsets, using the headset’s volume or play/pause controls while connected can trigger the A2DP profile to become available.
• It is possible that connecting to a headset via bluetoothctl from bluez-utils will make the A2DP sink profile available. There is an automation for this every time a bluetooth device is connected: fix-bt-a2dpAUR (detailed usage)

• Manually switching to Bluetooth’s AudioSink service which would make the A2DP profile and its A2DP PulseAudio sink available. This can be done with blueman-manager which included in blueman or by registering the UUID of the AudioSink service with bluetoothctl .

• Disable the headset profile

• Enable MultiProfile support. This may help with headsets that support A2DP as well as Headset audio.

• Sometimes, none of the steps above will work. You may have tried rebooting and powering bluetooth off and on to no avail. In this case, try restarting the bluetooth.service .
• For some headphone models with audio control panel, the A2DP profile must be enabled by pressing the Play/Pause button on the panel.

Gnome with GDM

This article or section is a candidate for merging with #Connecting works, but I cannot play sound.

The instructions below were tested on Gnome 3.24.2 and PulseAudio 10.0 however they may still be applicable and useful for other versions.

If PulseAudio fails when changing the profile to A2DP while using GNOME with GDM, you need to prevent GDM from starting its own instance of PulseAudio:

• Prevent PulseAudio clients from automatically starting a server if one is not running by adding the following:

• Prevent systemd from starting PulseAudio anyway with socket activation:

• Restart, and check that there is no PulseAudio process for the gdm user using:

Further discussion about this problem and alternative fixes can be found at [5] and [6]. Alternatively, one may try and install fix-bt-a2dp AUR .

HFP not working with PulseAudio

HFP-only bluetooth headsets may not be usable in the standard configuration of PulseAudio. The respective profiles occur, but they are not available:

To solve the respective issue, update PulseAudio and BlueZ to latest versions. Then install ofono AUR and phonesim AUR then create / activate a fake modem as described here [8]:

• Create /etc/ofono/phonesim.conf with:

• Start as user:

• Enable/start the ofono.service .
• Power modem:

• Activate modem:

• To check the results, use the test commands from ofonoAUR installed in /usr/lib/ofono/test/ . To power, activate, and test the modem you can use:

The output of the respective modem section should read like this:

• Finally, restart PulseAudio and reconnect headset. Now, HFP should be available:

Disable PulseAudio auto switching headset to HSP/HFP

When using a bluetooth headset that supports multiple profiles, some applications switch to HSP/HFP profile automatically. If this behaviour is undesired you can disable this by appending the auto_switch=false parameter to the bluetooth-policy module:

Disable PipeWire HSP/HFP profile

Unlike PulseAudio, PipeWire does not automatically switch between A2DP and HSP/HFP in response to input events. However, rather than to enable automatically switching to the (lower audio quality) HSP/HFP profile if A2DP fails, you may prefer to disable the former altogether. To do so, make a copy of /usr/share/wireplumber/bluetooth.lua.d/50-bluez-config.lua [9] as shown below.

Tips and tricks

The following applies to both PipeWire and PulseAudio.

Battery level reporting

To get the current battery level of your headset reported to upower , you must enable bluez’ D-Bus experimental features as described in Bluetooth#Enabling experimental features.

Media controls

To use the media controls they may be forwarded to MPRIS, where they can be picked up by media players that support MPRIS for external control. See MPRIS#Bluetooth for details.

Источник

Both A2DP and the less popular HFP/HSP are supported by the kernel as well as different sound servers. Although Bluetooth is infamous for being unreliable[1], many implementations have seen massive improvements, making it a somewhat less excruciating experience on well-established hardware like Intel Bluetooth chips.

Headset via PipeWire

PipeWire acts as a drop-in replacement for PulseAudio and offers an easy way to set up Bluetooth headsets. It includes out-of-the-box support for A2DP sink profiles using SBC/SBC-XQ, AptX, LDAC or AAC codecs, and HFP/HSP.

Install pipewire-pulse (which replaces pulseaudio and pulseaudio-bluetooth).

The daemon will be started automatically as a user service. Use pavucontrol or your desktop environment’s settings for configuration. For more information, see PipeWire#Bluetooth devices.

Headset via Bluez5/PulseAudio

Install the pulseaudio-alsa, pulseaudio-bluetooth and bluez-utils packages, the last of which provides the bluetoothctl utility.

Note: Before continuing, ensure that the bluetooth device is not blocked by rfkill.

Configuration via CLI

Start bluetooth.service.

Now we can use the bluetoothctl command line utility to pair and connect. For troubleshooting and more detailed explanations of bluetoothctl see the Bluetooth article. Run

$ bluetoothctl

to be greeted by its internal command prompt. Then enter:

[bluetooth]# power on
[bluetooth]# agent on
[bluetooth]# default-agent
[bluetooth]# scan on

Now make sure that your headset is in pairing mode. It should be discovered shortly. For example,

[NEW] Device 00:1D:43:6D:03:26 Lasmex LBT10

shows a device that calls itself «Lasmex LBT10» and has MAC address «00:1D:43:6D:03:26». We will now use that MAC address to initiate the pairing:

[bluetooth]# pair 00:1D:43:6D:03:26

After pairing, you also need to explicitly connect the device (if this does not work, try the trust command below before attempting to connect):

[bluetooth]# connect 00:1D:43:6D:03:26

If you are getting a connection error org.bluez.Error.Failed retry by killing existing PulseAudio daemon first:

$ pulseaudio -k
[bluetooth]# connect 00:1D:43:6D:03:26

Finally, if you want to automatically connect to this device in the future:

[bluetooth]# trust 00:1D:43:6D:03:26

If everything works correctly, you now have a separate output device in PulseAudio.

Note: The device may be off by default. Select its audio profile (OFF, A2DP, HFP) in the «Configuration» tab of pavucontrol.

You can now redirect any audio through that device using the «Playback» and «Recording» tabs of pavucontrol.

You can now disable scanning again and exit the program:

[bluetooth]# scan off
[bluetooth]# exit

Setting up auto connection

To make your headset auto connect you need to enable PulseAudio’s switch-on-connect module. Do this by adding the following lines to /etc/pulse/default.pa:

/etc/pulse/default.pa

### Automatically switch to newly-connected devices
load-module module-switch-on-connect

Note: Make sure that your bluetooth audio device is trusted, otherwise repeated pairing will fail. See Bluetooth#Pairing for details.

Configuration via GNOME Bluetooth

Note: The A2DP profile will not activate using this method with pulseaudio 9/10 due to an ongoing bug, leading to possible low quality mono sound. See #A2DP not working with PulseAudio for a possible solution.

You can use GNOME Bluetooth graphical front-end to easily configure your bluetooth headset.

First, you need to be sure that bluetooth.service systemd unit is running.

Open GNOME Bluetooth and activate the bluetooth. After scanning for devices, you can connect to your headset selecting it on the device list. You can directly access to sound configuration panel from the device menu. On the sound panel, a new sink should appear when your device is connected.

LDAC/aptX

LDAC/aptX codecs are supported as of PulseAudio 15.0. You can verify the codec you are using for connection as follows:

$ pactl list | grep a2dp_codec

Troubleshooting

Note: Many users report frustration with getting A2DP/Bluetooth Headsets to work. see #Switch between HSP/HFP and A2DP setting for additional information.

Bad sound / Static noise / «Muddy» sound

If you experience bad sound quality with your headset, it could in all likelihood be because your headset is not set to the correct profile.
See #Switch between HSP/HFP and A2DP setting to solve the problem.

Selected audio profile, but headset inactive and audio cannot be redirected

Deceptively, this menu is available before the device has been connected; annoyingly it will have no effect. The menu seems to be created as soon as the receiver recognizes the device.

Make sure to run bluetoothctl as root and connect the device manually. There may be configuration options to remove the need to do this each time, but neither pairing nor trusting induce automatic connecting for me.

Pairing fails with AuthenticationFailed

If pairing fails, you can try enabling or disabling SSPMode with:

# btmgmt ssp off

or

# btmgmt ssp on

You may need to turn off BlueTooth while you run this command.

Pairing works, but connecting does not

You might see the following error in bluetoothctl:

[bluetooth]# connect 00:1D:43:6D:03:26
Attempting to connect to 00:1D:43:6D:03:26
Failed to connect: org.bluez.Error.Failed

To further investigate, check the unit status of bluetooth.service or have a look at the log as follows:

# journalctl -n 20

You might see a message like this:

bluetoothd[5556]: a2dp-sink profile connect failed for 00:1D:43:6D:03:26: Protocol not available

This may be due to the pulseaudio-bluetooth package not being installed. Install it if it missing, then restart pulseaudio.

It can also be due to permission, especially if starting pulseaudio as root allows you to connect. Add your user to the lp group, then restart pulseaudio.
See /etc/dbus-1/system.d/bluetooth.conf for reference.

If the issue is not due to the missing package, the problem in this case is that PulseAudio is not catching up. A common solution to this problem is to restart PulseAudio. Note that it is perfectly fine to run bluetoothctl as root while PulseAudio runs as user. After restarting PulseAudio, retry to connect. It is not necessary to repeat the pairing.

If restarting PulseAudio does not work, you need to load module-bluetooth-discover.

# pactl load-module module-bluetooth-discover

The same load-module command can be added to /etc/pulse/default.pa.

If that still does not work, or you are using PulseAudio’s system-wide mode, also load the following PulseAudio modules (again these can be loaded via your default.pa or system.pa):

module-bluetooth-policy
module-bluez5-device
module-bluez5-discover

It is also possible there are no write permissions for the owner of /var/lib/bluetooth/. If this is the case, you may get the device to work by removing and re-pairing it, but the issue will return after rebooting. Restoring write permissions fixes this issue:

# chmod -R u+w /var/lib/bluetooth

Connecting works, but there are sound glitches all the time

This is very likely to occur when the Bluetooth and the WiFi share the same chip as they share the same physical antenna and possibly band range (2.4GHz). Although this works seamlessly on Windows, this is not the case on Linux.

A possible solution is to move your WiFi network to 5GHz so that there will be no interference. If your card/router does not support this, you can upgrade your WiFi drivers/firmware. This approach works on Realtek 8723BE and latest rtl drivers for this chip from AUR.

If nothing of the previous is possible, a less effective mitigation is to tweak the fragment size and the latency on PulseAudio output port, trying to compensate interference. Reasonable values must be chosen, because these settings can make the audio out of sync (e.g. when playing videos). To change the latency of the bluetooth headset’s port (e.g. to 125000 microseconds in the following example):

$ pactl set-port-latency-offset <bluez_card> headset-output 125000

where the identifier of the card can be found with

$ pacmd list-sinks | grep -Eo 'bluez_card[^>]*'

The fragment size can be set in /etc/pulse/daemon.conf and takes effect after a restart of PulseAudio (for more details please see PulseAudio/Troubleshooting#Setting the default fragment number and buffer size in PulseAudio).

Perhaps it will help to add options ath9k btcoex_enable=1 to the /etc/modprobe.d/ath9k.conf (with the appropriate bluetooth adapter):

/etc/modprobe.d/ath9k.conf

# possibly fix for sound glitches
options ath9k btcoex_enable=1

Then restart.

Connecting works, but I cannot play sound

Make sure that you see the following messages in your system log:

bluetoothd[5556]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSource
bluetoothd[5556]: Endpoint registered: sender=:1.83 path=/MediaEndpoint/A2DPSink

If you see a message similar to this, you can go on and investigate your PulseAudio configuration. Otherwise, go back and ensure the connection is successful.

When using GDM, another instance of PulseAudio is started, which «captures» your bluetooth device connection. This can be prevented by masking the pulseaudio socket for the GDM user by doing the following:

# mkdir -p  /var/lib/gdm/.config/systemd/user
# ln -s /dev/null  /var/lib/gdm/.config/systemd/user/pulseaudio.socket

On next reboot the second instance of PulseAudio will not be started.

It may happen that bluez wrongly considers an headset as not a2dp capable. In this case, search the index of the bluetooth device with

$ pacmd ls

Among the output there should be a section related to the bluetooth headset, containing something similar to

$ pacmd ls

index: 2
        name: <bluez_card.XX_XX_XX_XX_XX_XX>
        driver: <module-bluez5-device.c>
        owner module: 27
        properties:
                device.description = "SONY MDR-100ABN"
                device.string = "XX:XX:XX:XX:XX:XX"
                device.api = "bluez"
                device.class = "sound"
                ...

To manually set the profile, run

$ pacmd set-card-profile 2 a2dp_sink

where 2 is the index of the device retrieved through pacmd ls.

Connecting works, but the device does not show up in PulseAudio sinks

If the headphones connect successfully (which can be confirmed via bluetoothctl) but do not show up as an output/input sink in pavucontrol, you can try adding the following policy to your Bluetooth configuration file /etc/bluetooth/main.conf:

/etc/bluetooth/main.conf

[General]
Enable=Control,Gateway,Headset,Media,Sink,Socket,Source

Some users report that this has solved their problem.

Connecting works, sound plays fine until headphones become idle, then stutters

If the headphones play sound correctly until they become idle and then stutter on resume (e.g. because the sound is paused, or because no sound is played for a while), try disabling PulseAudio’s automatic sink/source suspension on idle.

Some user reports huge delays or even no sound when the Bluetooth connection does not send any data. This is due to the module-suspend-on-idle module, which automatically suspends sinks/sources on idle. As this can cause problems with headset, the responsible module can be deactivated.

To disable loading of the module-suspend-on-idle module, comment out the following line in the configuration file in use (~/.config/pulse/default.pa or /etc/pulse/default.pa):

~/.config/pulse/default.pa

### Automatically suspend sinks/sources that become idle for too long
#load-module module-suspend-on-idle

Finally restart PulseAudio to apply the changes.

UUIDs has unsupported type

During pairing you might see this output in bluetoothctl:

[CHG] Device 00:1D:43:6D:03:26 UUIDs has unsupported type

This message is a very common one and can be ignored.

PC shows device as paired, but is not recognized by device

This might be due to the device not supporting bluetooth LE for pairing.

Try setting ControllerMode = bredr in /etc/bluetooth/main.conf. See [3].

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 adapter). You can fix this by re-pairing the device. Start by removing the device:

$ bluetoothctl
[bluetooth]# devices
Device XX:XX:XX:XX:XX:XX My Device
[bluetooth]# remove XX:XX:XX:XX:XX:XX

Then restart bluetooth.service, turn on your bluetooth adapter, make your device discoverable, re-scan for devices, and re-pair your device. Depending on your bluetooth manager, you may need to perform a full reboot in order to re-discover the device.

Apple AirPods have low volume

Create a drop-in file for bluetooth.service with the following contents:

/etc/systemd/system/bluetooth.service.d/noplugin-avrc.conf

[Service]
ExecStart=
ExecStart=/usr/lib/bluetooth/bluetoothd --noplugin=avrcp

Then, restart bluetooth.service, reload its configuration, and reconnect your headset.

Additionally, for AirPods Pro, disable the spatial audio and enable Mono in the settings of your iPhone.

This can also solve issues with some devices that are unable to be controlled through AVRCP.

Apple AirPods Pro working with PulseAudio as A2DP Sink but not with HSP/HFP

If you find that AirPods Pro are working with PulseAudio, but are incapable of using the HSP/HFP configurations (in pavucontrol‘s Configurations tab, usually listed as unavailable), try switching to pipewire-pulse.

Note that switching to pipewire-pulse (and restarting your computer or the appropriate user-level systemd services) should enable HSP/HFP, but may also disable A2DP. (When selecting A2DP Sink in the Configurations tab, the option is instantly deselected and becomes Off.) If you encounter this issue, try removing/renaming the /var/lib/bluetooth folder like so:

# mv /var/lib/bluetooth /var/lib/bluetooth.bak

Re-pair your AirPods Pro (and other devices) afterwards. This should make all configurations (HSP/HFP and A2DP) available again and easily accessible from pavucontrol and pacmd.

HSP problem: the bluetooth sink and source are created, but no audio is being transmitted

You may be missing firmware or the SCO (audio protocol of HSP and HFP) routing might be wrong. See [4] — the firmware for BCM20702 can be installed via bcm20702a1-firmware^AUR or bcm20702b0-firmware^AUR.

Error: Failed to start discovery org.bluez.Error.InProgress

If your headset is discovered, but fails to connect with the error «Failed to start discovery org.bluez.Error.InProgress», install bluez-hciconfig^AUR and run

$ hciconfig hciX up
$ hciconfig hciX reset

where X is the identifier of your computer’s bluetooth device (typically 0).

You should then be able to connect following the steps in #Configuration via CLI.

High audio volume due to synchronization between headphones and PulseAudio

As of PulseAudio 15, «Absolute Volume» interlocks the audio volume of your headphones with PulseAudio, making it impossible to change one without the other. On some headphones, e.g. on the the Hoco W25, this may result in irritating loudness. To disable «Absolute Volume», edit /etc/pulse/default.pa and change the line

 load-module module-bluetooth-discover

to

 load-module module-bluetooth-discover avrcp_absolute_volume=false

Switch between HSP/HFP and A2DP setting

This can easily be achieved by the following command where the card_number can be obtained by running pacmd list-cards.

$ pacmd set-card-profile card_number a2dp_sink

For enabling automatic profile switching from A2DP to HSP when a recording stream appears without any role set, you can append auto_switch=2 to load-module module-bluetooth-policy in /etc/pulse/default.pa.

For more information about PulseAudio profiles, see PulseAudio Documentation.

A2DP not working with PulseAudio

Socket interface problem

If PulseAudio fails when changing the profile to A2DP with bluez 4.1+ and PulseAudio 3.0+, you can try disabling the Socket interface from /etc/bluetooth/main.conf by removing the line Enable=Socket and adding line Disable=Socket.

A2DP sink profile is unavailable

When the A2DP sink profile is unavailable it will not be possible to switch to the A2DP sink (output) with a PulseAudio front-end and the A2DP sink will not even be listed. This can be confirmed with pactl.

$ pactl list | grep -C2 A2DP
     Profiles:
             headset_head_unit: Headset Head Unit (HSP/HFP) (sinks: 1, sources: 1, priority: 30, available: yes)
             a2dp_sink: High Fidelity Playback (A2DP Sink) (sinks: 1, sources: 0, priority: 40, available: no)
             off: Off (sinks: 0, sources: 0, priority: 0, available: yes)
        Active Profile: headset_head_unit

Trying to manually set the card profile with pacmd will fail.

$ pacmd set-card-profile bluez_card.C4_45_67_09_12_00 a2dp_sink
Failed to set card profile to 'a2dp_sink'.

This is known to happen from version 10.0 of PulseAudio when connecting to Bluetooth headphones via Bluedevil or another BlueZ front-end. See related bug report.

This issue also appears after initial pairing of Headphones with some Bluetooth controllers (e.g. 0a12:0001, Cambridge Silicon Radio) which might default to the Handsfree or Headset - HS service and will not allow switching to the A2DP PulseAudio sink that requires the AudioSink service.

Possible solutions:

• For some headsets, using the headset’s volume or play/pause controls while connected can trigger the A2DP profile to become available.
• It is possible that connecting to a headset via bluetoothctl from bluez-utils will make the A2DP sink profile available. There is an automation for this every time a bluetooth device is connected: fix-bt-a2dp^AUR (detailed usage)

[bluetooth]# connect headset_MAC_address

• Manually switching to Bluetooth’s AudioSink service which would make the A2DP profile and its A2DP PulseAudio sink available. This can be done with blueman-manager which included in blueman or by registering the UUID of the AudioSink service with bluetoothctl.

$ bluetoothctl
[bluetooth]# menu gatt
[bluetooth]# register-service 0000110b-0000-1000-8000-00805f9b34fb
[bluetooth]# quit

• Disable the headset profile

/etc/bluetooth/main.conf

[General]
Disable=Headset

• Enable MultiProfile support. This may help with headsets that support A2DP as well as Headset audio.

/etc/bluetooth/main.conf

[General]
MultiProfile=multiple

• Sometimes, none of the steps above will work. You may have tried rebooting and powering bluetooth off and on to no avail. In this case, try restarting the bluetooth.service.
• For some headphone models with audio control panel, the A2DP profile must be enabled by pressing the Play/Pause button on the panel.

Gnome with GDM

The instructions below were tested on Gnome 3.24.2 and PulseAudio 10.0 however they may still be applicable and useful for other versions.

If PulseAudio fails when changing the profile to A2DP while using GNOME with GDM, you need to prevent GDM from starting its own instance of PulseAudio:

• Prevent PulseAudio clients from automatically starting a server if one is not running by adding the following:

/var/lib/gdm/.config/pulse/client.conf

autospawn = no
daemon-binary = /bin/true

• Prevent systemd from starting PulseAudio anyway with socket activation:

$ sudo -ugdm mkdir -p /var/lib/gdm/.config/systemd/user
$ sudo -ugdm ln -s /dev/null /var/lib/gdm/.config/systemd/user/pulseaudio.socket

• Restart, and check that there is no PulseAudio process for the gdm user using:

$ pgrep -u gdm pulseaudio

Further discussion about this problem and alternative fixes can be found at [5] and [6]. Alternatively, one may try and install fix-bt-a2dp^AUR.

HFP not working with PulseAudio

Note: Some users have reported success in enabling HFP support by replacing PulseAudio with PipeWire for Bluetooth support. [7] See #Headset via PipeWire for installation instructions.

HFP-only bluetooth headsets may not be usable in the standard configuration of PulseAudio. The respective profiles occur, but they are not available:

bluetoothctl info

UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)

pactl list

...
Profiles:
      ...
      headset_head_unit: Headset Head Unit (HSP/HFP) (sinks: 1, sources: 1, priority: 30, available: no)

To solve the respective issue, update PulseAudio and BlueZ to latest versions. Then install ofono^AUR and phonesim^AUR then create / activate a fake modem as described here [8]:

Note: The steps following the creation of phonesim.conf should be done every time you want to connect the headset.

• Create /etc/ofono/phonesim.conf with:

[phonesim]
Address=127.0.0.1
Driver=phonesim
Port=12345

• Start as user:

$ phonesim -p 12345 /usr/share/phonesim/default.xml &

• Enable/start the ofono.service.
• Power modem:

$ dbus-send --print-reply --system --dest=org.ofono /phonesim org.ofono.Modem.SetProperty string:"Powered" variant:boolean:true

• Activate modem:

$ dbus-send --print-reply --system --dest=org.ofono /phonesim org.ofono.Modem.SetProperty string:"Online" variant:boolean:true

• To check the results, use the test commands from ofono^AUR installed in /usr/lib/ofono/test/. To power, activate, and test the modem you can use:

$ /usr/lib/ofono/test/enable-modem /phonesim
$ /usr/lib/ofono/test/online-modem /phonesim
$ /usr/lib/ofono/test/list-modems

The output of the respective modem section should read like this:

...
[ /phonesim ]
  Online = 1
  Powered = 1
  Lockdown = 0
  Emergency = 0
  Manufacturer = MeeGo
  ...

• Finally, restart PulseAudio and reconnect headset. Now, HFP should be available:

headset_head_unit: Headset Head Unit (HSP/HFP) (sinks: 1, sources: 1, priority: 30, available: yes)

Note: HFP support is not stable and may cause glitches with switching to A2DP; try reconnecting, if the needed mode is not available.

Disable PulseAudio auto switching headset to HSP/HFP

When using a bluetooth headset that supports multiple profiles, some applications switch to HSP/HFP profile automatically. If this behaviour is undesired you can disable this by appending the auto_switch=false parameter to the bluetooth-policy module:

/etc/pulse/default.pa

load-module module-bluetooth-policy auto_switch=false

Disable PipeWire HSP/HFP profile

Unlike PulseAudio, PipeWire does not automatically switch between A2DP and HSP/HFP in response to input events. However, rather than to enable automatically switching to the (lower audio quality) HSP/HFP profile if A2DP fails, you may prefer to disable the former altogether. To do so, make a copy of /usr/share/wireplumber/bluetooth.lua.d/50-bluez-config.lua [9] as shown below.

Note: HSP mode is required for built-in microphones to work [10].

/etc/wireplumber/bluetooth.lua.d/50-bluez-config.lua (or ~/.config/wireplumber/bluetooth.lua.d/50-bluez-config.lua)

...
bluez_monitor.properties = {
  ...
  ["bluez5.headset-roles"] = "[ ]",
  ...
  ["bluez5.hfphsp-backend"] = "none",
}
...
bluez_monitor.rules = {
  {
    ...
    apply_properties = {
      ...
      ["bluez5.auto-connect"] = "[ a2dp_sink ]",
      ...
       ["bluez5.hw-volume"] = "[ a2dp_sink ]",
    },
    ...
  },
}

Tips and tricks

The following applies to both PipeWire and PulseAudio.

Battery level reporting

Note: This is an experimental feature. Enabling it may prevent some Bluetooth mice from connecting automatically (see GitHub issue).

To get the current battery level of your headset reported to upower, you must enable bluez’ D-Bus experimental features as described in Bluetooth#Enabling experimental features.

Media controls

To use the media controls they may be forwarded to MPRIS, where they can be picked up by media players that support MPRIS for external control. See MPRIS#Bluetooth for details.

Hello
I am trying to make my adapter discoverable but it displays me this:- after bluetoothctl

[bluetooth]# scan on
[bluetooth]# discoverable on
Changing discoverable on succeeded
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress
[bluetooth]# 

Output of command :- lspci -knn | grep Net -A3; lsusb

02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290]
    Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055]
    Kernel driver in use: rt2800pci
    Kernel modules: rt2800pci
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. 
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
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Output of command :-dmesg | grep -i bluetooth

   [   12.851854] Bluetooth: Core ver 2.22
    [   12.851883] Bluetooth: HCI device and connection manager initialized
    [   12.851888] Bluetooth: HCI socket layer initialized
    [   12.851889] Bluetooth: L2CAP socket layer initialized
    [   12.851893] Bluetooth: SCO socket layer initialized
    [   67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create"
    [   67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
    [   67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create"
    [   67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
    [   68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create"
    [   68.194710] audit: type=1400 audit(1611909043.887:66): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1102 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
    [   81.668783] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    [   81.668785] Bluetooth: BNEP filters: protocol multicast
    [   81.668791] Bluetooth: BNEP socket layer initialized
    [ 1965.556683] Bluetooth: RTBT_Tb: vendor=0x1814, device=0x3298
    [ 1965.556685] Bluetooth: RTBT_Tb: vendor=0x0, device=0x0
    [ 1965.556687] Bluetooth: DynamicAlloc pci_device_id table at 0x00000000ad8b89c2 with size 64
    [ 1965.556688] Bluetooth: RTBT_Tb: vendor=0x1814, device=0x3298
    [ 1965.556689] Bluetooth: Convert: vendor=0x1814, device=0x3298
    [ 1965.556690] Bluetooth: RTBT_Tb: vendor=0x0, device=0x0
    [ 1965.556691] Bluetooth: pci_device_id: vendor=0x1814, device=0x3298
    [ 1965.556922] Bluetooth: rtbt_pci_probe(): PCI Dev(0000:02:00.1) get resource at 0xf7d00000,VA 0xffffa64041d80000,IRQ 17.
    [ 1965.556935] Bluetooth: call dev_ops->dev_ctrl_init!
    [ 1965.556951] Bluetooth: call dev_ops->dev_resource_init!
    [ 1965.582792] Bluetooth: RtmpOSIRQRequest(): request_irq (IRQ=17)done, isr_handler=0xffffffffc1274640!
    [ 1968.792846] Bluetooth: hci0: command 0x0c52 tx timeout
    [ 1968.832504] Bluetooth: rtbt_hci_dev_flush(dev=0xffff8ea3907f4000)
    [ 1968.900515] Bluetooth: RFCOMM TTY layer initialized
    [ 1968.900525] Bluetooth: RFCOMM socket layer initialized
    [ 1968.900534] Bluetooth: RFCOMM ver 1.11
    [ 1971.898810] Bluetooth: RtmpOSIRQRequest(): request_irq (IRQ=17)done, isr_handler=0xffffffffc1274640!
    [ 1975.160848] Bluetooth: hci0: command 0x0c1a tx timeout