You are not logged in.
yes, wired usb devices are working normally
Sorry, I meant "access to a BT keyboard/mouse"…
Do you mean that the phone might have connected to the headphones
No, I meant the phone might have registered as speakers.
Added it to kernel parameters, didn't help
Do they show up in "cat /proc/cmdline"?
I still don't get it. What exactly does the problem seem to be?
Either the chip powers down and silently fails to resume and wireplumber/BT-audio is victim to this or spa.bluez5.native itself causes this (possibly triggered by the HPs) and trashes everything else.
Though going back to your OP
After a few days, earphones automatically disconnect.
Attempting to reconnect results in the device not being found or failing to pair/connect.
This issue persists for several days, after which the Bluetooth device may reconnect on its own without any configuration changes.
and "several days" probably includes reboots(?) I'd rather bet on the HPs being the origin here, notably if you connect them to multiple devices - can you wipe their connections and does that + a reboot immediately allow you to reconnect them?
You could also try to delete the connection on the arch system, use is along other BT devices (input woulud be good, but also your phone or the other HPs, notably if they're not connected to any other host, incl. your phone) and see whether you've still bluetooth failures.
(Ie. we need to figure which side of the connection is the troublemaker here)
Offline
Sorry, I meant "access to a BT keyboard/mouse"…
No, I don't think I have one.
No, I meant the phone might have registered as speakers.
No that did not happen, it registered as a data transfer device when bluetooth was working, so it must remain the same in the non working state.
Do they show up in "cat /proc/cmdline"?
Yes, I checked that immediately after adding them.
Either the chip powers down and silently fails to resume and wireplumber/BT-audio is victim to this or spa.bluez5.native itself causes this (possibly triggered by the HPs) and trashes everything else.
Oh.
and "several days" probably includes reboots(?) I'd rather bet on the HPs being the origin here, notably if you connect them to multiple devices - can you wipe their connections and does that + a reboot immediately allow you to reconnect them?
Okay, I'll try resetting the earphones and rebooting the system.
edit : Tried it, did not change anything.
You could also try to delete the connection on the arch system, use is along other BT devices (input woulud be good, but also your phone or the other HPs, notably if they're not connected to any other host, incl. your phone) and see whether you've still bluetooth failures.
(Ie. we need to figure which side of the connection is the troublemaker here)
So basically once bluetooth starts working again, I should try using the laptop with devices other than earphones and check if bluetooth stops working again. Is that right?
I'll also try setting up a windows install on my laptop to find out whether this is a hardware issue or a linux issue.
Last edited by aperiogon3141 (2025-01-04 06:04:48)
Offline
So basically once bluetooth starts working again, I should try using the laptop with devices other than earphones and check if bluetooth stops working again. Is that right?
Yes. So BT currently isn't working *at all* (incl. after reboots)?
Did you already try to completely power down the system (incl. removing the battery for a couple of minutes) and/or resetting the CMOS to get out of this?
Offline
So BT currently isn't working *at all* (incl. after reboots)?
No, not at all. It will probably start working again in a few days.
Did you already try to completely power down the system (incl. removing the battery for a couple of minutes) and/or resetting the CMOS to get out of this?
Will do that now.
Offline
Hello seth,
It has been 11 days, and bluetooth hasn't started working yet. I will update you once it does.
Offline
update : It began working shortly after a system update and a period of remaining shut down for 10-15 minutes.
The next time it stops working, I will try completely powering the laptop off for some time after.
Last edited by aperiogon3141 (2025-01-22 15:26:28)
Offline