bluez-alsa VS alpine-raspberry-pi

One thing I found from a quick search is that you no longer need to use hciattach if you're using a recent enough firmware. See here.

Maybe your Rant might have made sense a decade ago not anymore, you're just forgetting you you choice one can still survive with Alsa+Jack (even the firefox supports alsa when you complied with flags) if you question about bluez has pulse dependency bluez-alsa has been running flawlessly for me years now.

The current headset status in Linux for traditional bluetooth looks like this: The better quality mSBC (16kHz mono) codec for HFP is available with. pipewire/pipewire-pulse 0.3.20: https://gitlab.freedesktop.org/pipewire/pipewire/-/blob/master/NEWS Work is in progress for pulseaudio: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/254 bluez-alsa seems to have something as well, I am not sure about the completeness. https://github.com/Arkq/bluez-alsa

archlinux-arm/alpine (https://github.com/knoopx/alpine-raspberry-pi)

I personally like Alpine 64 bit for Docker: it is hard to beat Alpine’s speed on the pi. You can build from tarball as mentioned on their website or use a premade image like here.

You can try a premade image here. I know it has armv7 support, not sure if it supports armv6.

You can do it with Alpine. Here is an example.

Alpine runs great on the pi! Check out this script. You can add docker as an additional package, change between armhf and arm64 (with the applicable edits to config.txt in the bootstrap folder,) add docker to the list of startup services, and even configure things like wifi and user accounts. You then build a custom image and flash a preconfigured Alpine OS.