-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transport not available during connection phase, but amixer shows device #6
Comments
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 |
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:
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: |
Hi Quick question. Is HSP included now? |
Yes, it is in the master branch. However, I've tested HSP audio-gateway only. |
Hi,
I seem to have some trouble getting my bluetooth headset fully connected. It shows an error "Transport not available" when I want to play a media file and also shows this error during the initial connection to the device. However, unlike issue #5 I am able to get the device shown in the output of `amixer -D bluealsa:
Beforehand I already got an error in the connection phase in the output of
bluetooth
(Transport not available).I execute commands in this order:
bluealsa
as rootbluetoothctl
as root:power on
andconnect E4:22:A5:08:7B:FF
(headset then tells me, it connected to PC)When the command
connect E4:22:A5:08:7B:FF
executes, I get the errorTransport not available: /org/bluez/hci0/dev_E4_22_A5_08_7B_FF/fd9
in the output ofbluealsa
(where the fd9 is a number increasing with each trial).That's also the error I then get, when I want to play a media file either by passing the device information via command line or using it from the
asound.conf
(likeamixer
does):I am executing all commands as root, to make sure it's not permission issues.
I also tried executing both
aplay ...
commands from above with a user who is part of groupaudio
, but this leads to the same error.I might also have to say that I have a PulseAudio running, but for a new project I needed bluetooth device input in ALSA. Might the PulseAudio "steal" the device from bluealsa? Don't know if bluez can only handle one handler at a time or so.
pactl
also lists the device:How can we further investigate this? Am I missing some libraries for HSP?
Transport not available
sounds like it could be such an issue.The text was updated successfully, but these errors were encountered: