![]() ![]() You can downgrade just the Bluetooth firmware by downloading the previous version from this link. My usual BT keyboards are working as expected, but I have a K380 on order for testing purposes. Thanks for clearing up my dribble dribble This seems to me to be a particular problem with Bluetooth, probably due to the lack of official documentation. Be very careful with outdated information found on the internet. You do need to be paired and trusted with the speaker.Ĥ. There is no need to connect with a Bluetooth speaker in bluetoothctl. In particular, be very careful with postings that are more than a year or two old.Ģ. ![]() You should actually read it if contemplating the use of raspi-update.Ĥ. Raspi-update should not be used unless you know what you are doing. Sudo is never needed with bluetoothctl on a properly configured system.ģ. You do need to be paired and trusted with the speaker. BlueALSA is not useful for any Bluetooth use cases apart from audio streaming.Ģ. You may need to manually install it on the Lite version. BlueALSA has replaced the functionality of PA, and is pre-installed in the Raspberry Pi OS full install. PulseAudio is not required for Bluetooth audio streaming (or anything else involving Bluetooth.) It can cause conflicts, and should be avoided. I thought I should clear up some misinformation from previous posts.ġ. In order to ease the path for future readers. Now I have a working BT stack, so finally onward to my project. I do know that Pulseaudio installs with Bluez on the pi4, since I purged all the BT stuff and reinstalled it with apt. I would think not, since BT did not work with the original package, using the 'Using Bluetooth within the Terminal' on this website And the things I list above resolved the problem. No idea if BlueALSA is included in the Buster LITE package, or not. As noted previously, I'm running headless. ![]()
0 Comments
Leave a Reply. |