borine
borine
@Muppet1856 Is this issue still happening? I have been unable to find any similar reports, and am unable to replicate it on my own system. To be able to help,...
Two more possible issues with your setup, even after you have the `bluealsa` daemon running: First: ``` pcm.!default { type plug slave { pcm "pulse" } } pcm.pulse { type...
``` sudo journalctl -xeu bluealsa.service ``` will print out the error messages from the bluealsa daemon
OK, so the wiki systemd guide is out-of-date; with the latest bluealsa sources it is necessary to specify at least one profile on the command line. See the manual page...
omit the `-B C9:F0:F4:F3:FD:E5` option - it has nothing to do with bluetooth addresses, and is not needed except in special cases (see the EXAMPLE section of the manual page...
That error is because your user does not have permission in D-Bus to acquire the name "org.bluealsa". Run it as root: ``` sudo bluealsa -p a2dp-sink ```
OK, looks like your installation is broken - you appear to be missing at least one critical file (`/etc/dbus-1/system.d/bluealsa.conf`). I am out of time on this for today, will look...
> Nothing changes if I run it as root. Please can you post the output from `sudo bluealsa -p a2dp-sink`
That's good !! bluealsa is running - in another terminal type ``` ps -ef | grep bluealsa ``` you should see it running
Well, now we go back to a previous question - does your bluetooth device act as a A2DP source (ie A2DP microphone)? Right now that is the only profile that...