Unreliable bluetooth on fresh install

General system Newbie
1

I installed EndeavourOS on my Lenevo ThinkBook 15 G5 and I tried to connect my SONY WH-CH720 headset using bluetooth. At first I faced the same issues which I am about to describe, but after removing, trusting, pairing and connecting for about 10 to 20 times, it connected. And after reboot the same problem appears

The problem as follows,

  1. I open bluetoothctl
  2. Turn on my headset to pairing mode
  3. I scan → trust → pair → connect
[bluetooth]# power on
[bluetooth]# Changing power on succeeded
[bluetooth]# agent on
Agent is already registered
[bluetooth]# default-agent
[bluetooth]# Default agent request successful
[bluetooth]# scan on
[bluetooth]# SetDiscoveryFilter success
[bluetooth]# Discovery started
[bluetooth]# [CHG] Controller 4C:82:A9:24:23:58 Discovering: yes
[bluetooth]# [NEW] Device 84:D3:52:9D:EF:38 WH-CH720N
[bluetooth]# [NEW] Device AC:B6:87:8F:B9:C9 AC-B6-87-8F-B9-C9
[bluetooth]# [CHG] Device 84:D3:52:9D:EF:38 RSSI: 0xffffffc3 (-61)
[bluetooth]# trust 84:D3:52:9D:EF:38
[bluetooth]# [CHG] Device 84:D3:52:9D:EF:38 Trusted: yes
[bluetooth]# Changing 84:D3:52:9D:EF:38 trust succeeded
[bluetooth]# pair
84:D3:52:9D:EF:38  AC:B6:87:8F:B9:C9
[bluetooth]# pair 84:D3:52:9D:EF:38
Attempting to pair with 84:D3:52:9D:EF:38
[CHG] Device 84:D3:52:9D:EF:38 Connected: yes
[WH-CH720N]# [CHG] Device 84:D3:52:9D:EF:38 Bonded: yes
[CHG] Device AC:B6:87:8F:B9:C9 RSSI: 0xffffffb0 (-80)
[CHG] Device 84:D3:52:9D:EF:38 Connected: no
[bluetooth]# [CHG] Device 84:D3:52:9D:EF:38 Paired: yes
[bluetooth]# Pairing successful
[bluetooth]# connect 84:D3:52:9D:EF:38
Attempting to connect to 84:D3:52:9D:EF:38
[CHG] Device 84:D3:52:9D:EF:38 Connected: yes
[WH-CH720N]#

Note: Right after I type pair <MAC> I get a notifcation that my headset is connected, and when the “Pairing successful” message shows up, I get a notification that my headset is disconnected.
When I then try to connect, it says connected: yes. but my headset doesn’t give off the connected chime which it usually gives when its connected to a device.

Around 2 minutes later after “connecting”, it disconnects (my headset doesnt sound the disconnected chime as well) and I get a notification that my headset got disconnected.

This is the output of systemctl -u bluetooth.service
Context: Time is May 24 16:41 at the time of command execution

May 24 16:30:05 eva systemd[1]: Stopped Bluetooth service.
May 24 16:30:05 eva systemd[1]: Starting Bluetooth service...
May 24 16:30:05 eva bluetoothd[32267]: Bluetooth daemon 5.76
May 24 16:30:05 eva systemd[1]: Started Bluetooth service.
May 24 16:30:05 eva bluetoothd[32267]: Starting SDP server
May 24 16:30:05 eva bluetoothd[32267]: src/plugin.c:init_plugin() System does not support bap plugin
May 24 16:30:05 eva bluetoothd[32267]: src/plugin.c:init_plugin() System does not support bass plugin
May 24 16:30:05 eva bluetoothd[32267]: src/plugin.c:init_plugin() System does not support mcp plugin
May 24 16:30:05 eva bluetoothd[32267]: src/plugin.c:init_plugin() System does not support vcp plugin
May 24 16:30:05 eva bluetoothd[32267]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
May 24 16:30:05 eva bluetoothd[32267]: src/plugin.c:init_plugin() System does not support micp plugin
May 24 16:30:05 eva bluetoothd[32267]: src/plugin.c:init_plugin() System does not support ccp plugin
May 24 16:30:05 eva bluetoothd[32267]: src/plugin.c:init_plugin() System does not support csip plugin
May 24 16:30:05 eva bluetoothd[32267]: Bluetooth management interface 1.22 initialized
May 24 16:30:05 eva bluetoothd[32267]: Battery Provider Manager created
May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/ldac
May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSink/aptx_hd
May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/aptx_hd
May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSink/aptx
May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/aptx
May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSink/aac
May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/aac
May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSink/sbc
May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/sbc
May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSink/sbc_xq
May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/sbc_xq
May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/aptx_ll_1
May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/aptx_ll_0
May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/faststream
May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/faststream_duplex
May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSink/opus_05
May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/opus_05
May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSink/opus_05_duplex
May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/opus_05_duplex
May 24 16:34:48 eva bluetoothd[32267]: src/device.c:search_cb() 84:D3:52:9D:EF:38: error updating services: Input/output error (5)
May 24 16:36:04 eva bluetoothd[32267]: src/device.c:search_cb() 84:D3:52:9D:EF:38: error updating services: Input/output error (5)

Searching for the error in last 2 lines doesnt give me much useful links, these are the ones I could find

  1. https://askubuntu.com/questions/1421177/bluetooth-headphones-keep-disconnecting
  2. https://github.com/blueman-project/blueman/issues/1836

The solutions for these are for pulseaudio, I am using pipewire and wireplumber

This is the output of info 

Device 84:D3:52:9D:EF:38 (public)
	Name: WH-CH720N
	Alias: WH-CH720N
	Class: 0x00240404 (2360324)
	Icon: audio-headset
	Paired: yes
	Bonded: yes
	Trusted: yes
	Blocked: no
	Connected: no
	LegacyPairing: no
	UUID: Vendor specific           (fa349b5f-8050-0030-0010-00001bbb231d)
	UUID: Vendor specific           (00000000-deca-fade-deca-deafdecacaff)
	RSSI: 0xffffffc3 (-61)

What have I tried?

  1. I tried restarting bluetooth.service and performed the same steps as shown above
  2. Tried to remove the headset and pair it again as specified in https://discovery.endeavouros.com/audio/bluetooth/2021/03/

Output of systemctl status bluetooth

[bharath@eva ~]$ systemctl status bluetooth
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
     Active: active (running) since Fri 2024-05-24 16:30:05 IST; 17min ago
       Docs: man:bluetoothd(8)
   Main PID: 32267 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 16569)
     Memory: 1.0M (peak: 1.3M)
        CPU: 77ms
     CGroup: /system.slice/bluetooth.service
             └─32267 /usr/lib/bluetooth/bluetoothd

May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/faststream
May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/faststream_duplex
May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSink/opus_05
May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/opus_05
May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSink/opus_05_duplex
May 24 16:30:05 eva bluetoothd[32267]: Endpoint registered: sender=:1.38 path=/MediaEndpoint/A2DPSource/opus_05_duplex
May 24 16:34:48 eva bluetoothd[32267]: src/device.c:search_cb() 84:D3:52:9D:EF:38: error updating services: Input/output error (5)
May 24 16:36:04 eva bluetoothd[32267]: src/device.c:search_cb() 84:D3:52:9D:EF:38: error updating services: Input/output error (5)

I have checked my headset and it is working properly, so the issue is not with the headset.
What might be causing this issue? and how can I fix it? any help will be greatly appreciated :slight_smile:

2

Try lts kernel ? Someone on the forum reported similar issues that doesn’t happen with lts kernel, sudo pacman -S linux-lts linux-lts-headers if running nvidia, also run sudo pacman -S nvidia-dkms after the first command.

1 Like
3

I am facing this issue in a LTS kernel only, 6.6.31-2-lts to be exact.
For odd reason, my headset got connected without me doing anything and it started working… and after around 15 minutes, the audio started to crack and now my headset is again not working.

4

I’m having the same issue if anyone is able to help. Running KDE plasma desktop. Any luck on this Bharath?

5

No luck, I am using my headset wired for now. I would like to solve it as well : (

6

Any luck since June @Bharath? I’m also using Sony WH-CH720 and it was mostly fine for a long time, but for the last few days I had problems with connecting the headset to the PC, and now after unpairing it - I can’t pair it again. All I can see in journalctl is:

paź 15 00:40:45 kimek-pc bluedevil-wizard[3912]: kf.bluezqt: PendingCall Error: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."

I’ve also tried pairing my Sony WF-1000XM5 headphones, the result was the same :frowning:

7

Ok, with some help from a friend - I think I now have a somewhat working solution.

  1. Set ReverseServiceDiscovery in /etc/bluetooth/main.conf to false
  2. Restart bluetooth: systemctl restart bluetooth
  3. Forget the device in the bluetooth UI if it was added
  4. Turn on pairing mode in your headset
  5. Open bluetoothctl
  6. scan on
  7. connect <yourDeviceMac>
  8. Your headset should now be playing sound from your PC
  9. Turn off the headset
  10. Turn on the headset
  11. A popup should appear in the corner, click Trust and authorize

Both the WH-CH720N and WF-1000XM5 now play sound and are paired with my PC!

2 Likes
8

I created an account to thank you for this. I was despairing that these new headphones were bricked because of this error, but that one setting that no one else in my googling has suggested was the trick.

Thank you!

1 Like
9

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.