Bluetooth doesn't connect to any device

Hi, I’m new to the community, my Bluetooth doesn’t connect to any device, what data do I need to provide?

What desktop you’re using, and some kind of indication what hardware you’re trying to use would be a good start.

@sfalken
I entered the command dmesg | grep -i blue :

[    5.375345] usb 1-2: Product: Bluetooth Radio
[   10.153895] Bluetooth: Core ver 2.22
[   10.153907] NET: Registered PF_BLUETOOTH protocol family
[   10.153908] Bluetooth: HCI device and connection manager initialized
[   10.153911] Bluetooth: HCI socket layer initialized
[   10.153913] Bluetooth: L2CAP socket layer initialized
[   10.153915] Bluetooth: SCO socket layer initialized
[   10.192918] Bluetooth: hci0: RTL: examining hci_ver=0b hci_rev=000b lmp_ver=0b lmp_subver=8852
[   10.195909] Bluetooth: hci0: RTL: rom_version status=0 version=1
[   10.195911] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_fw.bin
[   10.198459] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_config.bin
[   10.198693] Bluetooth: hci0: RTL: cfg_sz 6, total sz 58003
[   10.982752] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   10.982754] Bluetooth: BNEP filters: protocol multicast
[   10.982756] Bluetooth: BNEP socket layer initialized
[   11.647071] Bluetooth: hci0: RTL: fw version 0xdbc6b20f
[   11.828901] Bluetooth: hci0: AOSP extensions version v1.00
[   11.828903] Bluetooth: hci0: AOSP quality report is supported
[   11.828975] Bluetooth: MGMT ver 1.22
[   33.773117] Bluetooth: RFCOMM TTY layer initialized
[   33.773124] Bluetooth: RFCOMM socket layer initialized
[   33.773126] Bluetooth: RFCOMM ver 1.11
[ 6241.962433] Bluetooth: hci0: RTL: examining hci_ver=0b hci_rev=000b lmp_ver=0b lmp_subver=8852
[ 6241.965438] Bluetooth: hci0: RTL: rom_version status=0 version=1
[ 6241.965441] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_fw.bin
[ 6241.965502] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_config.bin
[ 6241.965520] Bluetooth: hci0: RTL: cfg_sz 6, total sz 58003
[ 6243.410550] Bluetooth: hci0: RTL: fw version 0xdbc6b20f
[ 6243.588412] Bluetooth: hci0: AOSP extensions version v1.00
[ 6243.588417] Bluetooth: hci0: AOSP quality report is supported
[ 6243.588548] Bluetooth: MGMT ver 1.22
[13498.350993] Bluetooth: hci0: RTL: examining hci_ver=0b hci_rev=000b lmp_ver=0b lmp_subver=8852
[13498.353997] Bluetooth: hci0: RTL: rom_version status=0 version=1
[13498.354000] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_fw.bin
[13498.356357] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_config.bin
[13498.356633] Bluetooth: hci0: RTL: cfg_sz 6, total sz 58003
[13499.800975] Bluetooth: hci0: RTL: fw version 0xdbc6b20f
[13499.978967] Bluetooth: hci0: AOSP extensions version v1.00
[13499.978972] Bluetooth: hci0: AOSP quality report is supported
[13499.979066] Bluetooth: MGMT ver 1.22
[14857.616040] Bluetooth: hci0: RTL: examining hci_ver=0b hci_rev=000b lmp_ver=0b lmp_subver=8852
[14857.619036] Bluetooth: hci0: RTL: rom_version status=0 version=1
[14857.619040] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_fw.bin
[14857.619104] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_config.bin
[14857.619117] Bluetooth: hci0: RTL: cfg_sz 6, total sz 58003
[14859.064032] Bluetooth: hci0: RTL: fw version 0xdbc6b20f
[14859.242017] Bluetooth: hci0: AOSP extensions version v1.00
[14859.242020] Bluetooth: hci0: AOSP quality report is supported
[14859.242145] Bluetooth: MGMT ver 1.22
[16669.945479] Bluetooth: hci0: RTL: examining hci_ver=0b hci_rev=000b lmp_ver=0b lmp_subver=8852
[16669.948458] Bluetooth: hci0: RTL: rom_version status=0 version=1
[16669.948461] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_fw.bin
[16669.950907] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_config.bin
[16669.951211] Bluetooth: hci0: RTL: cfg_sz 6, total sz 58003
[16671.395484] Bluetooth: hci0: RTL: fw version 0xdbc6b20f
[16671.573467] Bluetooth: hci0: AOSP extensions version v1.00
[16671.573472] Bluetooth: hci0: AOSP quality report is supported
[16671.573597] Bluetooth: MGMT ver 1.22
[18791.176589] Bluetooth: hci0: RTL: examining hci_ver=0b hci_rev=000b lmp_ver=0b lmp_subver=8852
[18791.179575] Bluetooth: hci0: RTL: rom_version status=0 version=1
[18791.179578] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_fw.bin
[18791.179640] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_config.bin
[18791.179651] Bluetooth: hci0: RTL: cfg_sz 6, total sz 58003
[18792.624595] Bluetooth: hci0: RTL: fw version 0xdbc6b20f
[18792.802579] Bluetooth: hci0: AOSP extensions version v1.00
[18792.802582] Bluetooth: hci0: AOSP quality report is supported
[18792.802711] Bluetooth: MGMT ver 1.22
[26209.452470] Bluetooth: hci0: RTL: examining hci_ver=0b hci_rev=000b lmp_ver=0b lmp_subver=8852
[26209.455461] Bluetooth: hci0: RTL: rom_version status=0 version=1
[26209.455464] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_fw.bin
[26209.458365] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_config.bin
[26209.458715] Bluetooth: hci0: RTL: cfg_sz 6, total sz 58003
[26210.901532] Bluetooth: hci0: RTL: fw version 0xdbc6b20f
[26211.079455] Bluetooth: hci0: AOSP extensions version v1.00
[26211.079458] Bluetooth: hci0: AOSP quality report is supported
[26211.079588] Bluetooth: MGMT ver 1.22
[31410.570222] Bluetooth: hci0: RTL: examining hci_ver=0b hci_rev=000b lmp_ver=0b lmp_subver=8852
[31410.573195] Bluetooth: hci0: RTL: rom_version status=0 version=1
[31410.573199] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_fw.bin
[31410.573263] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_config.bin
[31410.573274] Bluetooth: hci0: RTL: cfg_sz 6, total sz 58003
[31412.018189] Bluetooth: hci0: RTL: fw version 0xdbc6b20f
[31412.196261] Bluetooth: hci0: AOSP extensions version v1.00
[31412.196264] Bluetooth: hci0: AOSP quality report is supported
[31412.196453] Bluetooth: MGMT ver 1.22
[36477.550280] Bluetooth: hci0: AOSP extensions version v1.00
[36477.550284] Bluetooth: hci0: AOSP quality report is supported

@hudsilva:

Please take a look at “rfkill” – you’ll need to ensure that, the “util-linux” package is installed.

 # LANG=C rfkill --help

Usage:
 rfkill [options] command [identifier ...]

Tool for enabling and disabling wireless devices.

Options:
 -J, --json             use JSON output format
 -n, --noheadings       don't print headings
 -o, --output <list>    define which output columns to use
     --output-all       output all columns
 -r, --raw              use the raw output format

 -h, --help             display this help
 -V, --version          display version

Available output columns:
 DEVICE      kernel device name
 ID          device identifier value
 TYPE        device type name that can be used as identifier
 TYPE-DESC   device type description
 SOFT        status of software block
 HARD        status of hardware block

Commands:
 help
 event
 list   [identifier]
 block   identifier
 unblock identifier
 toggle  identifier

For more details see rfkill(8).
 #

@dcurtisfra
I’m using KDE Desktop.
rfkill:

hudson@Hud-Desktop:~> sudo rfkill
[sudo] senha para root: 
ID TYPE      DEVICE         SOFT         HARD
 0 bluetooth hci0   desbloqueado desbloqueado
 1 wlan      phy0   desbloqueado desbloqueado

I’m using in portuguese, not block. Util-linux installed.

Your output looks normal.
What does exactly mean “my Bluetooth doesn’t connect to any device”?
1- devices are not visible at all?
2- your computer bt is not visible by peripheral devices?
3- you cannot transfer files to-from peripheral devices (e.g. from-to a phone)?

To transfer files you need to install bluez-obexd which is not part of a default install I think.
Check with:

bruno@LT-B:~> zypper --no-refresh se bluez
Loading repository data...
Reading installed packages...

S  | Name                      | Summary                                                        | Type
---+---------------------------+----------------------------------------------------------------+--------
i+ | bluez                     | Bluetooth Stack for Linux                                      | package
i  | bluez-auto-enable-devices | Configuration that automatically enables all bluetooth devices | package
i  | bluez-cups                | CUPS Driver for Bluetooth Printers                             | package
   | bluez-deprecated          | Bluez tools that upstream considers obsolete                   | package
   | bluez-devel               | Files needed for BlueZ development                             | package
   | bluez-devel-32bit         | Files needed for BlueZ development                             | package
 l | bluez-firmware            | Bluetooth(TM) Firmware                                         | package
i+ | bluez-obexd               | Object Exchange daemon for sharing content                     | package
   | bluez-qt-devel            | Async Bluez wrapper library - development files                | package
   | bluez-qt-imports          | Async Bluez wrapper library                                    | package
   | bluez-qt-udev             | bluez-qt integration with udev                                 | package
   | bluez-test                | Tools for testing of various Bluetooth-functions               | package
   | bluez-zsh-completion      | Zsh completion for bluez                                       | package
   | libKF5BluezQt6            | Async Bluez wrapper library - development files                | package
   | python39-pybluez          | A Python Bluetooth wrapper                                     | package
   | python310-pybluez         | A Python Bluetooth wrapper                                     | package
   | python311-pybluez         | A Python Bluetooth wrapper                                     | package
bruno@LT-B:~

Did you notice the following in my post?

 # LANG=C rfkill . . .

If you have a non-English system then, prefix your CLI commands with “LANG=C” and then, the output will be English …

Sorry, rfill:

ID TYPE      DEVICE      SOFT      HARD
 1 wlan      phy0   unblocked unblocked
 2 bluetooth hci0   unblocked unblocked

Hi,

  1. Devices visible at all
  2. My computer is visible
  3. Devices visible but show error in connection.

Bluez

Hud-Desktop:~ # zypper --no-refresh se bluez
Loading repository data...
Reading installed packages...

S  | Name                      | Summary                                                        | Type
---+---------------------------+----------------------------------------------------------------+--------
i  | bluez                     | Bluetooth Stack for Linux                                      | package
i+ | bluez-auto-enable-devices | Configuration that automatically enables all bluetooth devices | package
i  | bluez-cups                | CUPS Driver for Bluetooth Printers                             | package
   | bluez-deprecated          | Bluez tools that upstream considers obsolete                   | package
   | bluez-devel               | Files needed for BlueZ development                             | package
   | bluez-devel-32bit         | Files needed for BlueZ development                             | package
i+ | bluez-firmware            | Bluetooth(TM) Firmware                                         | package
   | bluez-obexd               | Object Exchange daemon for sharing content                     | package
   | bluez-qt-devel            | Async Bluez wrapper library - development files                | package
i  | bluez-qt-imports          | Async Bluez wrapper library                                    | package
i  | bluez-qt-udev             | bluez-qt integration with udev                                 | package
   | bluez-test                | Tools for testing of various Bluetooth-functions               | package
   | bluez-zsh-completion      | Zsh completion for bluez                                       | package
i  | libKF5BluezQt6            | Async Bluez wrapper library - development files                | package
   | python39-pybluez          | A Python Bluetooth wrapper                                     | package
   | python310-pybluez         | A Python Bluetooth wrapper                                     | package
   | python311-pybluez         | A Python Bluetooth wrapper                                     | package

What errors?

Please show what you did (commands) and what the results (errors shown) were.

As @OrsoBruno already explained in #5: To transfer files via bluetooth you need to install the package bluez-obexd (and you should check that the obex service is enabled for your user).

I’m able to connect using the terminal, before remove using bluetoothctl remove and after bluetoothctl connect.

Remove:

hudson@Hud-Desktop:~> bluetoothctl remove FC:58:FA:25:0A:F4
[DEL] Device FC:58:FA:25:0A:F4 MI BT 18I
Device has been removed

Connect:

hudson@Hud-Desktop:~> bluetoothctl connect FC:58:FA:25:0A:F4
Attempting to connect to FC:58:FA:25:0A:F4
[CHG] Device 5C:C1:D7:B1:AE:73 RSSI: 0xffffffac (-84)
[CHG] Device 5C:C1:D7:B1:AE:73 ManufacturerData.Key: 0x0075 (117)
[CHG] Device 5C:C1:D7:B1:AE:73 ManufacturerData.Value:
  42 04 01 01 67 5c c1 d7 b1 ae 73 5e c1 d7 b1 ae  B...g\....s^....
  72 06 00 00 00 00 00 00                          r.......        
[CHG] Device 5C:C1:D7:B1:AE:73 ManufacturerData.Key: 0xff19 (65305)
[CHG] Device 5C:C1:D7:B1:AE:73 ManufacturerData.Value:
  00 75 00 09 01 00 00 00 06 01 00 00 00 00 00 00  .u..............
  00 00 00 00 00 00 00 00                          ........        
[CHG] Device 98:06:3C:9F:0F:15 ManufacturerData.Key: 0x0075 (117)
[CHG] Device 98:06:3C:9F:0F:15 ManufacturerData.Value:
  42 04 01 20 67 20 0f 00 02 01 4b 01 01 00 01 00  B.. g ....K.....
  00 00 00 00 00 00 00 00                          ........        
[CHG] Device 98:06:3C:9F:0F:15 ManufacturerData.Key: 0xff19 (65305)
[CHG] Device 98:06:3C:9F:0F:15 ManufacturerData.Value:
  00 75 00 09 01 00 00 00 06 01 00 00 00 00 00 00  .u..............
  00 00 00 00 00 00 00 00                          ........        
[CHG] Device A4:30:7A:3B:91:FF ManufacturerData.Key: 0x0075 (117)
[CHG] Device A4:30:7A:3B:91:FF ManufacturerData.Value:
  42 04 01 01 67 a4 30 7a 3b 91 ff a6 30 7a 3b 91  B...g.0z;...0z;.
  fe 01 00 00 00 00 00 00                          ........        
[CHG] Device D0:D0:03:94:A5:73 ManufacturerData.Key: 0x0075 (117)
[CHG] Device D0:D0:03:94:A5:73 ManufacturerData.Value:
  42 04 01 01 67 d0 d0 03 94 a5 73 d2 d0 03 94 a5  B...g.....s.....
  72 0a 00 00 00 00 00 00                          r.......        
[CHG] Device A4:30:7A:3B:91:FF ManufacturerData.Key: 0x0075 (117)
[CHG] Device A4:30:7A:3B:91:FF ManufacturerData.Value:
  42 04 01 20 67 19 0f 00 00 01 32 00 00 00 00 00  B.. g.....2.....
  00 00 00 00 00 00 00 00                          ........        
[NEW] Device 62:5E:25:3F:51:7A 62-5E-25-3F-51-7A
[CHG] Device FC:58:FA:25:0A:F4 Connected: yes
[CHG] Device FC:58:FA:25:0A:F4 ServicesResolved: yes
[CHG] Device FC:58:FA:25:0A:F4 Bonded: yes
[CHG] Device FC:58:FA:25:0A:F4 Paired: yes
[NEW] Endpoint /org/bluez/hci0/dev_FC_58_FA_25_0A_F4/sep1 
[NEW] Transport /org/bluez/hci0/dev_FC_58_FA_25_0A_F4/sep1/fd0 
Connection successful

Thanks.