OMG. I finally fixed my bluetooth audio issues I had on linux.
I wasn't able to connect my bluetooth headset via a2dp.
What was required was for me to edit my bluetooth/main.conf to include these 2 lines:
MultiProfile = multiple
Disable = Socket
Pretty sure this problem took me around 10 hours to solve in total. Spent many evenings tinkering around with it. :/
@Anachron
I have an old ThinkPad T43, which has a really old BT adapter and I can't make it paid with a Bluetooth speaker every other device is able to use. I was going to give up: it's indeed old after all, but I have to try this first! Thanks!
Good luck! Maybe not a big chance, but better than giving up I guess!
@Anachron
Yeah, worth a try. It used to work long ago when Bluetooth LE didn't even exist and the whole stack was way simpler, maybe bluez attempts to do with this adapter things it doesn't support and fails. I can pair it with phones and other computers, BT input devices even, but audio seems to pose an issue for some reason 🤷
@dcc
It's a good idea actually, but these GUI things usually bring in TONS of dependencies, besides, I don't think think it would don anything I didn't try. I've literally tried everything in the book — even the legacy hcitool route to no avail. I have an interactive agent running I get to the point of entering the PIN, I know it is correct as when I enter the wrong one it fails, but with the correct one the pairing stalls and times out in about a minute.
@m0xee @dcc@annihilation.social
Also it would maybe worth a try to go with bluetoothctl info and pactl list into an IRC channel and use a pastebin service to ask for help.
Good luck!
@dcc
I'm using the same setup everywhere, including computers with BT2.1+EDR — it works, only on this one it doesn't.
It's like the speaker doesn't detect a2dp-source and audio gateway service on the computer, but they are there — bluealsa provides them, I can see them listed.
I think that "MultiProfile" setting *might* have something to do with it, so I'll give it a try tomorrow.
@Anachron