Bluez bug makes my headphones crash

Hi guys, a newbie linux user here. So, I think this is a bluez bug but what happens is this…

A lot of times, when i connect my bluetooth headphones(Sony-WH-CH710N) with my fedora KDE (5.25.5), mostly after a pause or so, the headphones stop working… and after sometimes, the headphones just crash(I hear a “tik” and then the light starts to blink and no buttons work so i have to switch it off and turn it back on)… in the system logs, i feel this is the chronology:

Transport Acquire() failed for transport /org/bluez/hci0/dev_30_53_C1_67_B1_8C/sep2/fd10 (Input/output error)
fedora pipewire[1429]: pw.node: (bluez_output.30_53_C1_67_B1_8C.1-79) idle -> error (Received error event)
fedora wireplumber[1431]: (bluez_output.30_53_C1_67_B1_8C.1-20) suspended -> error (Start error: Operation not permitted) 

I have really no idea what else information do you guys need but feel free to ask…

Probably this problem can be caused by the Linux kernel which suspend the Bluetooth adapter (it can be connected as a USB device) because it considers the device inactive. Can you show the output of the lsusb command?


Bus 001 Device 002: ID 8087:8001 Intel Corp. Integrated Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 002 Device 004: ID 04ca:704d Lite-On Technology Corp. HP HD Webcam
Bus 002 Device 006: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader
Bus 002 Device 002: ID 0bda:b001 Realtek Semiconductor Corp. Bluetooth Radio 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Your Bluetooth adapter is listed here as a USB device. It’s possible to prevent the Linux kernel from suspending this device by adding the following udev rule to /etc/udev/rules.d/50-bluetooth.rules:

ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="0bda", ATTR{idProduct}=="b001", ATTR{power/autosuspend}="-1"

ohkkk. Did that and restarted ;D…
Imma observe it for around an hour or two and follow back…
This bug has been frustrating me since i got these headphones and i’ve even switched os but this didn’t change.

this works flawlessfly thanksssssss