You are not logged in.
bluez version: 5.84-1
bluez-utils version: 5.84-1
Kernel: Linux 6.17.5-arch1-1
I am trying to connect to my earbuds with two endpoints (/org/bluez/hci0/dev_XX_XX_XX_XX_XX_XX/sep1 and /org/bluez/hci0/dev_XX_XX_XX_XX_XX_XX/sep2) and a transport point (/org/bluez/hci0/dev_XX_XX_XX_XX_XX_XX/sep2/fd1). The first connection upon pairing was as expected. In order to auto-connect by putting the earbuds on, I also trusted the device with
trust XX:XX:XX:XX:XX:XXThe unexpected behavior began after that. Putting on the earbuds causes them to automatically connect to my controller, wireplumber recognizes them as audio device, playback works, even the buttons on the earbuds work (wev output for XF86Audio- keys are as expected) but bluetoothctl or the bluetooth module for Waybar, which probably uses a bluez API doesn't list them as connected devices.
Here's the output for
bluetoothctl info XX:XX:XX:XX:XX:XXDevice XX:XX:XX:XX:XX:XX (public)
Name: root-ap
Alias: root-ap
Class: 0x00240404 (2360324)
Icon: audio-headset
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
CablePairing: no
UUID: Audio Sink (0000110b-0000-1000-8000-XXXXXXXXXXXX)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-XXXXXXXXXXXX)
UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-XXXXXXXXXXXX)
UUID: A/V Remote Control (0000110e-0000-1000-8000-XXXXXXXXXXXX)
UUID: Handsfree (0000111e-0000-1000-8000-XXXXXXXXXXXX)
UUID: PnP Information (00001200-0000-1000-8000-XXXXXXXXXXXX)
UUID: Vendor specific (74ec2172-0bad-4d01-8f77-XXXXXXXXXXXX)
Modalias: bluetooth:v004Cp200XXXXXX
Battery Percentage: 0x64 (100)I tried to reproduce this with two other bluetooth audio devices but it seems to be related to the connection with this particular device only.
A similar issue was posted on manjaro forum as well: https://forum.manjaro.org/t/bluetooth-d … /159676/12
Although that didn't really help.
Part of me wants to just forget about it and change my earbuds since I'm due for an upgrade anyway, but I'm curious to why this won't work. I haven't had the same problem with an earlier Arch installation 1-2 years ago.
Offline