MichaIng

Is it named `linux-image-*`? Then it should stay after `dietpi-installer`, but if it has a different name, it would be purged, indeed.

This explains it. So the script needs to be edited to preserve these packages. However, I suggest to follow the Linux package naming convention (like `linux-image-rockchip64`), since I'm not keen...

But Armbian kernel packages do follow this conversion, so nothing to patch on their end.

Ah sorry, yes they'd need to add your patches for proper R4SE support inkl. eMMC boot, but at least the kernel package has the common naming that is preserved by...

@TROFER First of all are the Bluetooth devices detected correctly? `bluetoothctl` Do you mean bluez-alsa? https://github.com/Arkq/bluez-alsa A I see now it is called bluealsa indeed nowadays. And can you paste...

@TROFER Okay indeed ALSA only detects the onboard sound card. I am not familiar with bluealsa, is it probably required to run a command to create a certain audio device...

@TROFER Exactly. Please try the following: ``` cat /etc/asound.conf defaults.bluealsa.service "org.bluealsa" defaults.bluealsa.device "XX:XX:XX:XX:XX:XX" defaults.bluealsa.profile "a2dp" defaults.bluealsa.delay 10000 _EOF_ ``` Replace XX:XX:XX:XX:XX:XX with the MAC address of the connected Bluetooth audio...

@TROFER Great. It should be btw possible to configure it as default audio device: https://github.com/Arkq/bluez-alsa/issues/251 The following additional `/etc/asound.conf` entry could be tried: ``` pcm.!default bluealsa ctl.!default bluealsa ``` So...

Ah there is actually a bluealsa package available on the RPi repo: ``` # apt show bluealsa Package: bluealsa Version: 0.13 Priority: optional Section: sound Maintainer: Simon Long Installed-Size: 244...

I reopen this issue and make a feature request out of it as most info around it is accumulated here.