wooden bay
I'm using a sennheiser momentum 4 headset with my motherboard its onboard BT.
Everything works perfectly fine, but each time I restart my PC I have to resync my headset.
"Failed to connect" upon trying to connect after a restart.
It's not a HUGE problem but it gets quite annoying after doing it so many times, any ideas how I could fix this?
cosmic garnet
That sounds frustrating asf. I've got something to forward in a bit, do tell me if it works for you.
wooden bay
"Failed to connect: org.bluez.Error.Failed br-connection-unknown"
Is what I get when trying that
Always have to hold the sync button on my headset in order for it to connect again
wooden bay
So I've tried reinstalling Blueman and bluez but still no dice. Any other tips?
outer whale
I'm using a sennheiser momentum 4 headset with my motherboard its onboard BT.
Ev...
hay that hapens to me too! lmk if u can fix it
outer whale
Always have to hold the sync button on my headset in order for it to connect aga...
Exactly the same thing that happens to me
pliant mirage
Is it paired in Windows also?
vagrant perch
"Failed to connect: org.bluez.Error.Failed br-connection-unknown"
This indicates an issue with the bluetoothd daemon. Steps are as follows. by default the daemon that handles bluetooth connections on Linux Mint is bluetoothd. Bluetoothd handles org.bluez which is the interface for bluetooth management. An outdated version of bluetoothd could cause this issue.
1.) Check the status, in terminal systemctl status bluetooth
If it is running you will see something like:
Status: Running
(I dont expect it to not be running but this will check the status)
2.) retry connection, if the issue persists attempt to reload the dbus system sudo systemctl restart dbus
3.) Reattempt, if it persists try checking your bluetoothd version
bluetoothd --version
4.) If the version is outdated ie: > 6.0 you should update the daemon.
sudo apt update
sudo apt install --only-upgrade bluez
5.) Check the version again bluetoothd --version
6.) if it is updated restart it sudo systemctl restart bluetooth
7.) this hopefully will resolve the issue so go ahead and try again
crude glacier
This indicates an issue with the bluetoothd daemon. Steps are as follows. by def...
Please avoid putting generated answers here, people can get that themselves, they come here for more specific help from others.
vagrant perch
Please avoid putting generated answers here, people can get that themselves, the...
This is not AI generated
Im just anal about how I format things
vagrant perch
Please avoid putting generated answers here, people can get that themselves, the...
I dont blame you tho youre not the first person to say that, its something about the way I type
crude glacier
OH no problem then, 
vagrant perch
lol im a bit flattered
crude glacier
If the version is outdated ie: > 6.0 you should update the daemon.
for a small correction, should be "... < 6.0 ...", maybe?
vagrant perch
> If the version is outdated ie: > 6.0 you should update the daemon.
for a smal...
Yeah, youre right should have just said less than 6.0
crude glacier
No worries, and thank you for the help!
vagrant perch
No worries, and thank you for the help!
o7
outer whale
This indicates an issue with the bluetoothd daemon. Steps are as follows. by def...
sudo apt install --only-upgrade bluez
Did this its still 5.72
hey @crude glacier
bluetoothd --version
4.) If the version is outdated ie: > 6.0 you should update the daemon.
sudo apt update
sudo apt install --only-upgrade bluez
how do i follow these steps?
should i update kernel for this?
pliant mirage
See if https://github.com/x2es/bt-dualboot helps. Bluetooth can get confused with a Linux/Windows dual boot because the Bluetooth device on the computer only has one MAC address
vagrant perch
See if https://github.com/x2es/bt-dualboot helps. Bluetooth can get confused wi...
Oh, that makes a lot of sense actually I assumed it was an issue with bluetoothd
