Transport not available during connection phase, but amixer shows device about bluez-alsa

Solution: Yes, pulseaudio and bluealsa cannot both try to access the bluetooth device at the same time (whatever that means in lower level, probably registering handlers to it on bluez). I removed the pulseaudio bluetooth connection (in my case on arch linux pulseaudio-bluetooth, restarted, and now it works.

[arkq]

Hi,

This issue is definitely related to #5, but you've provided full logs, which is really helpful. It seems, that the A2DP profile is not connected (at least bluealsa think it is not connected). The crucial log (from my explanation in #5) is this:

Endpoint method call: org.bluez.MediaEndpoint1.SelectConfiguration()

And it seems, that you are right, it might be the conflict with PulseAudio (or any other application, which has registered A2DP profile). To be honest, I never though about that. I will try to figure something out (if it is possible).

Many thanks for reporting it!

EDIT:
And for the HSP thing - in the current master snapshot there is only a stub for HSP/HFP. Currently I'm trying to make this work, however to accomplish that I have to make HUGE refactoring :) I will push lots of changes in a few next days.

[george-ai]

Hi

Quick question. Is HSP included now?

[arkq]

Yes, it is in the master branch. However, I've tested HSP audio-gateway only.