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

Bluealsa not working after update - error: a2dp-source profile connect failed for protocol not available #137

Closed
henry-shadowjet opened this Issue Aug 24, 2018 · 8 comments

Comments

Projects
None yet
4 participants
@henry-shadowjet
Copy link

henry-shadowjet commented Aug 24, 2018

Hi fellow BlueALSA users,

I've been extremely happy since using Raspbian Stretch on my Raspberry Pi 3 Model B+ with the Bluealsa A2DP instead of using the buggy and slow Pulseaudio.

I've had my setup working for my Pi to play audio from my phone using the A2DP and playback through bluealsa-play.

However since the large update I did yesterday (23-08-2018), which from memory includes a kernel update and a bunch of other programs, my bluetooth stopped working properly as described above.

First I noticed that I just stopped being able to connect to the Pi. And when I try to connect using bluetoothctl from the Pi side I get "org.bluez.error.Failed". That is typically when I didn't have pulseaudio activated in the old days. I stopped getting this error since bluealsa, but now it's back!

I then tried to unpair and re-pair the bluetooth from phone to the Pi. Went thru the pairing process smoothly, except now the services available doesn't include media playback anymore (as seen by the phone).

I looked at bluetooth.service and it threw the error as follows:
a2dp-source profile connect failed for protocol not available

I tried to reinstall bluealsa and bluetooth through apt-get, still doesn't work.

I'd appreciate any help. Thanks in advance

Henry

@Arkq

This comment has been minimized.

Copy link
Owner

Arkq commented Aug 25, 2018

@henry-shadowjet

This comment has been minimized.

Copy link
Author

henry-shadowjet commented Aug 25, 2018

Hi Arkq,

Thanks for your quick response.

The funny thing is bluealsa is running. Pidof bluealsa or pgrep bluealsa both return a PID, and so does systemctl status bluealsa.service. I stopped the service and run it manually as well, it runs, but nothing changes.

I tried to also start from fresh install. The bluealsa worked, as it usually would. As soon as I updated through apt, same problem.
Now I installed a fresh copy again and just refrain from updating, but it's just not ideal :(

Thanks for your help though ;)

@jbrowne200

This comment has been minimized.

Copy link

jbrowne200 commented Aug 27, 2018

Also experiencing this issue, my two Raspberry Pi's were working flawlessly as bluetooth receiver's using Bluealsa, and since updating both the other day neither are working. My devices can connect to the Pi, but the connection is cancelled only seconds later and no audio streaming is possible.

Hoping this issue is resolved soon as was really enjoying the feature.

@XECDesign

This comment has been minimized.

Copy link

XECDesign commented Aug 28, 2018

If it helps, these are the changes in the last update:
XECDesign/bluealsa@d926746...XECDesign:master

There was also a change to the bluetooth firmware nvram files:
RPi-Distro/firmware-nonfree@b518de4

@Arkq

This comment has been minimized.

Copy link
Owner

Arkq commented Aug 28, 2018

I think that the problem is cause by recent bluealsa changes (according to this comment). By default not all BT profiles are enabled. In order to enable A2DP Sink, one has to specify this profile on the command line. So, it seems that the startup script has to be changed from bluealsa to bluealsa -p a2dp-source -p a2dp-sink. See bluealsa --help for details.

@henry-shadowjet

This comment has been minimized.

Copy link
Author

henry-shadowjet commented Aug 28, 2018

Hi, thanks for helping out XECDesign, Arkq.

@XECDesign: wow, thanks but coding and the implications are out of my scope at the moment. I'll take it on notice. Thanks :)

@Arkq: Thanks for the suggestion. Pardon me I didn't mention earlier but latee on I tried exactly what you mentioned. I stopped the bluealsa.service thru systemctl (which automatically starts) and started it manually with a2dp-sink and a2dp-source. It didn't change anything. The process started, but nothing changed in terms of being able to connect. I didn't restart bluetooth.service and in hindsight maybe I should have. At the moment, I'm not willing to install the update and gamble it not working as this feature is quite essential for how I use my Pi. Please let me know if anyone has any success.

Thank you :)

@henry-shadowjet

This comment has been minimized.

Copy link
Author

henry-shadowjet commented Sep 3, 2018

I tried your suggestion, Arkq and it worked! Finally dared to update bluealsa again after having some time in the weekend. The -p flags really fixed it! Thanks!

@Arkq

This comment has been minimized.

Copy link
Owner

Arkq commented Oct 11, 2018

Issue seems to be resolved, I'm closing it then.

@Arkq Arkq closed this Oct 11, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment