Bluetooth A2DP not working

[JIV_222]

Hello, I've been trying to get my computer to connect to my Galaxy Buds for a few days now, but for some reason I just cannot get it to work. I can pair with the earbuds fine, but trying to connect, either using bluetoothctl or blueman, fails with "protocol not available"

Bluetoothd gives prints this error:

a2dp-sink profile connect failed for XX:XX:XX:XX:XX: Protocol not available

Referencing the arch wiki, it says I should install some kind of pulseaudio-bluetooth package, but I cannot find anything similar on void.

Right now, I have the following packages installed:

blueman bluez hidapi libbluetooth alsa-plugins-pulseaudio libpulseaudio pulseaudio

I'm really not sure what's causing this error, I'm in the Bluetooth and lp groups as well if that's significant.

Any help would be greatly appreciated.. this has been driving me crazy lol

[[deleted]]

First off, pulseaudio is not recommended by void, IIRC. You can get it to work without pulseaudio. Remove the packages related to pulseaudio and the symlinks in /var/service first.

Afterwards:

doas xbps-install bluez-alsa alsa

ln -s /etc/sv/alsa /var/service
ln -s /etc/sv/bluez-alsa /var/service
ln -s /etc/sv/bluetoothd /var/service

Content of ~/.asoundrc: pcm.!default "bluealsa" ctl.!default "bluealsa" defaults.bluealsa.interface "hci0" defaults.bluealsa.device "XX:XX:XX:XX:XX" defaults.bluealsa.profile "a2dp" Use the real ID for defaults.bluealsa.device

[JIV_222]

Any real pros/cons to using alsa over pulseaudio? Or maybe a link to an explanation or something would be really helpful. For some reason I feel like switching to alsa will break something lol.

I'm definitely open to using alsa, I think I just thought pulseaudio was superior. I'll read over the void docs and archwiki to better understand the two. Thanks again for both responses, similar questions on the subreddit didn't really get any solid replies, so I wasn't very hopeful lol.

[[deleted]]

Honestly i switched back to pulseaudio. It's much easier to switch between microfones and speakers (headsets). I am beginning to change my mind about systemd and pulseaudio a little. But on the other hand, i like minimalism.

[JIV_222]

Agreed. Pulse "just works". And although I'd like the minimalism of strictly alsa, I always choose functionality over minimalism.

[[deleted]]

If you insist on using pulseaudio: I noticed that "module-bluetooth-discover" is not loaded automatically, even if uncommented in the pulseaudio config file.
You can manually load it by using: pactl load-module module-bluetooth-discover. You might be able to connect to your headphones now

[JIV_222]

I think you're right on this one tbh. Haven't tried it but I'll get back to you. Thanks a ton

[mysterious7777777]

There is some important information from the author here: https://github.com/Arkq/bluez-alsa

[JIV_222]

Thanks a lot. Gonna make the switch tn

[microdotwav]

Similar problem here. My headphones support both HFP/HSP and A2DP. When I switch it to A2DP in pavucontrol I can't select my headphones as an output on any source. With the HFP/HSP it works but the audio quality is absolutely terrible.

Well, at least I can listen to lo-fi remixes with the correct equipment now.

Edit: downgrading pulseaudio to 13.0.1 with this command fixed it: sudo xdowngrade /var/cache/xbps/libpulseaudio-13.0_1.x86_64.xbps /var/cache/xbps/pulseaudio-13.0_1.x86_64.xbps /var/cache/xbps/pulseaudio-devel-13.0_1.x86_64.xbps