build VS termux-adb-fastboot

https://github.com/armbian/build

There isn't any hypervisor running on that and still no SVE

The number of boards supported by these two distros is astonishing:

https://www.armbian.com/download/

https://dietpi.com/#download

The NanoPC-T6 is already supported by Armbian build system:

https://github.com/armbian/build/tree/main/config/boards

It's my understanding that https://www.armbian.com/ has quite broad hardware support, and there are boards from Orange Pi and Pine64 that boast actual mainline kernel support, so this is more a case of a fragmented ecosystem than there being zero competitors that can meet or exceed pis.

The normal Raspberry Pi OS Lite is pretty okay.

https://www.armbian.com/ is also pretty awesome and also supports bunch of other RaspberryPi clones for cheaper price.

git clone https://github.com/armbian/build cd build ./compile.sh BOARD=orangepi5-plus RELEASE=jammy BUILD_MINIMAL=yes KERNEL_GIT=full BUILD_DESKTOP=no BUILD_ONLY="u-boot,kernel,armbian-config,armbian-zsh,bootstrap" KERNEL_CONFIGURE=no

If the SBC is supported by Armbian then the software support is usually pretty good.

https://www.armbian.com/

I use an old Android media player, repurposed with Ubuntu OS instead of Android (https://www.armbian.com/). Works fine, cost me nothing ($40 originally AFAIK, but it was being retired anyway). It has low power consumption, good reliability, more-than-adequate performance for HA and Plex media server. Equipped with multiple USB ports, ethernet, WiFi, HDMI.

Using only the device itself (you will need to be connected to wifi for this to work, these instructions are hot garbage): Install Termux from F-Droid. In termux install platform-tools adb/fastboot. Then Enable Wireless ADB, Settings-> System -> Developer Options -> Wireless Debugging, turn the slider to on, then get the port number from the Wireless Debugging sub menu get the port number. (Remember to turn off Wireless Debugging when done!). In Termux run adb connect localhost:PORT then check adb devices you should see an authorization prompt for a debug connection, you'll need the connection challenge code from settings (this authorization only needs to happen once). Then adb shell and run one of the commands below.

Termux for the help install in termux this: https://github.com/rendiix/termux-adb-fastboot pair your localhost:port with termux's adb connect to it and run adb shell wm size [Xres]x[Yres] -d [display number]

Just a heads up for anyone reading that tries this and finds it doesn't work: in the comments /u/-korni- linked to an alternative version of adb and I found that fixed the problem for me and the task works again.

There is a known bug with Samsung devices and the version of android-tools included in the repo. You have to use a different version of ADB to getaround the issue with the server not running right, I personally use https://github.com/rendiix/termux-adb-fastboot on my A32 5G. Not sure if others like termux-ADB work.

This one works; https://github.com/rendiix/termux-adb-fastboot

newest binary