03-06-2019, 01:05 AM
Hi Tim, thanks.
I had a look at the bluealsaaplay.conf and it was wrong. Despite sharing being activated in the gui, it was set to "plughw:0,0". After I changed it manually, speaker sharing started to work as expected. Thus, there is probably a bug in how the gui settings are processed.
With the scanning option, connecting a bluetooth device eventually works. However, it is a bit clunky that one can't just connect any new device without having to scan, pair and reconnect in various orders until it eventually works.
Basically, there would have to be something like in this solution here: https://stackoverflow.com/questions/3023...-in-bluez5 (including the set_trusted() call mentioned in a comment). But I don't know which program handles the pairing in moode so I don't know whether that's easy to fix.
Using the scan function, it is the line
inside the bt.sh script that makes bluez trust any device it scanned for.
I had a look at the bluealsaaplay.conf and it was wrong. Despite sharing being activated in the gui, it was set to "plughw:0,0". After I changed it manually, speaker sharing started to work as expected. Thus, there is probably a bug in how the gui settings are processed.
With the scanning option, connecting a bluetooth device eventually works. However, it is a bit clunky that one can't just connect any new device without having to scan, pair and reconnect in various orders until it eventually works.
Basically, there would have to be something like in this solution here: https://stackoverflow.com/questions/3023...-in-bluez5 (including the set_trusted() call mentioned in a comment). But I don't know which program handles the pairing in moode so I don't know whether that's easy to fix.
Using the scan function, it is the line
Code:
echo -e "trust $y\nquit" | bluetoothctl >/dev/null