Arch Linux

ArMor007

Member

Registered: 2020-11-15

Posts: 11

[SOLVED] Bluetooth can't connect after reboot

I have recently bought a pair of Galaxy Buds2 Pro, It can pair and connect all fine but after rebooting the system it won't connect, the only way to fix it seems to be removing the device and pairing it again.
I have been struggling with Bluetooth connectivity and I have to pair the device again and again to be able to use on Arch.

More info:
When the device fails to connect here is what I get:

$ sudo systemctl restart bluetooth.service
$ bluetoothctl 
Agent registered
[bluetooth]# power off
hci0 class of device changed: 0x000000
hci0 new_settings: bondable ssp br/edr le secure-conn 
Changing power off succeeded
[CHG] Controller 98:2C:BC:07:8C:89 Powered: no
[CHG] Controller 98:2C:BC:07:8C:89 Discovering: no
[CHG] Controller 98:2C:BC:07:8C:89 Class: 0x00000000 (0)
[bluetooth]# power on
hci0 class of device changed: 0x7c010c
[CHG] Controller 98:2C:BC:07:8C:89 Class: 0x007c010c (8126732)
hci0 new_settings: powered bondable ssp br/edr le secure-conn 
Changing power on succeeded
[CHG] Controller 98:2C:BC:07:8C:89 Powered: yes
[bluetooth]# agent on
Agent is already registered
[bluetooth]# default-agent 
Default agent request successful
[bluetooth]# connect F8:5B:6E:CD:17:22 
Attempting to connect to F8:5B:6E:CD:17:22
Failed to connect: org.bluez.Error.Failed le-connection-abort-by-local
[bluetooth]# 

Last edited by ArMor007 (2023-11-03 13:31:42)

ArMor007

Member

Registered: 2020-11-15

Posts: 11

Re: [SOLVED] Bluetooth can't connect after reboot

I found a workaround using blueman:
1- Open blueman-manager
2- Right click on the device, select Serial Port
3- The device will connect rfcomm0
4- Disconnect
5- Connect normally

It is possible to do the same through terminal commands, note that you need to install bluez-utils-compat to be able to use serial bluetooth.

$ rfcomm connect rfcomm0 MAC_address_of_Bluetooth_device
$ bluetoothctl connect MAC_address_of_Bluetooth_device

By running the above RFCOMM will fail to initiate a connection, but normal bluetooth connection will work for some reason.

At this point the issue is solved, the remaining question is that if this happens due to a bug in bluez or something is wrong with Samsung's bluetooth implementation?

Last edited by ArMor007 (2023-11-03 13:31:21)

c00ter

Member

From: Alaskan in Washington State

Registered: 2014-08-28

Posts: 421

Re: [SOLVED] Bluetooth can't connect after reboot

My question is if you dual-boot with Windows? Windows has a habit of "capturing" peripherals like bluetooth devices. It has to do with Windows fastboot and some BIOS hardware detection settings.

---

UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn

ArMor007

Member

Registered: 2020-11-15

Posts: 11

Re: [SOLVED] Bluetooth can't connect after reboot

My question is if you dual-boot with Windows? Windows has a habit of "capturing" peripherals like bluetooth devices. It has to do with Windows fastboot and some BIOS hardware detection settings.

No, I don't dual-boot.

dlakatos847

Member

Registered: 2024-06-19

Posts: 1

Re: [SOLVED] Bluetooth can't connect after reboot

My solution was this on KDE:

System Settings > Bluetooth > Configure > On login: Restore previous status --> Enable Bluetooth