I’ve got a Framework desktop recently and am trying to connect it to my Bluetooth headphones. It’s already connected successfully to my bluetooth soundbar. But when I connect it to my headphones (Anker Soundcore Life Q20), it just disconnects immediately. I’ve searched this forum and even online and haven’t found any good solutions. I’ve found this reported on the kernel mailing list too: https://bugzilla.kernel.org/show_bug.cgi?id=80791
I go into pairing mode directly from headphone by pressing down the power button till the power light blinks blue, indicating that its in the pairing mode.
Then i open my bluetooth utility from the taskbar and click on add new device button.
I find the correct device name and click on pair and it does pair
After I click on connect device in bluetooth utility, it connects for a few seconds and then disconnects automatically
I’m wondering if you should do it manually with bluetoothctl. Its been a while since I have had to do it this way but I remember a while back I had a similar issue and that was the only way I could pair it with out it immediately disconnecting. Of course I could have had another issue so its a crap shoot.
[CHG] Device 98:47:44:E7:27:2F ServicesResolved: no
[SIGNAL] BREDR.Disconnected - org.bluez.Reason.Local, Connection terminated by local host
[SIGNAL] Disconnected - org.bluez.Reason.Local, Connection terminated by local host
[CHG] Device 98:47:44:E7:27:2F Connected: no
I’m basically running on (warped) memory It seems like the issue I had was When pairing rfkill wouldn’t allow it. I honestly don’t remember what I had to do back then but I do remember I had to do a manual pair in order to get things to work.
if rfkill is installed you can rfkill list should show a list of available devices
Then it maybe it is an issue between the kernel and the device. From what I read in the original link several still seem to have this issue as well. Sorry It wasn’t something I was able to assist with. Good Luck. I’m out of idea’s on this one.
Is power saving enabled? I seem to remember (from a long time ago in a distro far far away) having a similar problem due to that. Unfortunately, I can’t remember how I resolved it other than I turned power saving off.