Excelent! That works. I didn't, notice that pinctrl-rk805 was externalized and can't be loaded automatically. For now I've just add pinctrl-rk805 to /etc/initramfs-tools/modules and update-initramfs. Werner: device tree has no changes for a long time. Thanks!

Which DTB did you use? I extracted the Android files and found a resource file named ENTRrk-kernel.dtb. The file began with "Rockchip RK3399 Excavator Board edp (Android)". Could it be possible that the device is compatible with this board?

Hi Brent; YES! I did figure it out, finally. The issue is that almost all information on the web is for the older pipewire and wireplumber which works completely differently than the new versions. Bookworm used the "old way" and Trixie uses these new versions for which there isn't much info. Compounding the issue is that most information is regarding desktop versions of Linux, not headless like I run. So, when you use bluetooth on linux, wireplumber auto-creates profiles and pw nodes. Or at least it's supposed to. It wasn't creating these profiles because I was missing a conf file which is only needed when your NOT running on desktop, AFAICT. Add this file: /etc/wireplumber/wireplumber.conf.d/50-bluez-no-seat.conf wireplumber.profiles = { main = { monitor.bluez.seat-monitoring = disabled } } If you do that, all of sudden, bluetooth "just works". Took forever to find that stupid little piece of information.

@sicxnull I ran into the same issue when flashing "Armbian-unofficial_26.02.0-trunk_Mxqpro_bookworm_current_6.12.65_minimal" (worked only in SD Card). The issue was gone when I switched to "Armbian-unofficial_25.05.0-trunk_X96q-lpddr3-v1-3_bookworm_edge_6.12.11_server" built by @Nick A

Could you send me just the (short) list of packages you installed atop the base Armbian distro rather than a dump of every installed package? The goal is to provide me a simply procedure I can use to replicate the freeze you observe. You might also try running repeating the "free" command to monitor memory usage just after you start your tests. I expect you will see the swap usage steadily increasing. If you disable swap, the system will likely start killing processes.