orangepi zero3 and 3w have, besides the confusing name, nothing in common. There is no support for any Allwinner A733 device in the framework yet. Best chance is to get in touch with Nick A since he tries to bring up support for raxda a7a, a7z, a7whateever devices which also use this SoC.

@Nick A Thanks for releasing the wonderful Armbian image for the Allwinner H618 and for supporting the community with your valuable suggestions. I recently purchased a TV box with 4GB of RAM and 64GB of storage running Android 12. I downloaded Armbian-unofficial_25.05.0-trunk_Transpeed-8k618-t_bookworm_edge_6.12.11_server.img.xz from here and flashed it to an SD card using BalenaEtcher. The box boots successfully, and I can configure it via the CLI. However, this motherboard is different from the ones previously posted here. The silkscreen on the board reads "X3Plus_H618_4bit_V3.0". Based on the naming convention and the appearance of the device, it seems to be the model available here. This board uses an FD6551 chip for the front VFD display. I have managed to extract .img file from the stock android. Are there any modifications I need to make to get the Wi-Fi, USB ports, and front VFD working? Could you please suggest? Things that are working: HDMI Display LAN Controller 1 out of the 2 USB ports. The port near to SD Card slot more precisely Things that are not working: WiFi - The chip got a metal shield. On top of the shield it is written with W804S1, inside the shield I could find AIC8800D40 chip. 1 x USB Port - Near the top left hand corner Front VFD display.

I recently got an Orange Pi Zero 3W, and I noticed that the official Ubuntu image is still based on the sunxi BSP stack, using the sun60iw2-6.6.98 kernel, while the bootloader is also using an older version of U-Boot. Right now, I’m wondering whether it would be feasible to use AI agents to help compile an Armbian image for the Orange Pi Zero 3W with a mainline kernel, while still keeping the old vendor U-Boot for compatibility. Has anyone here experimented with a similar approach or have any good suggestions or ideas? I also really hope the official team can eventually provide a proper Armbian image for the Orange Pi Zero 3W, because I’ve run into quite a few issues with the stock official image.

Oh I just downloaded Yamagi from Snap but OpenGLES was glitchy so I switched the settings to OpenGL 1.4 and it works great so I don't especially want to risk what might happen if I switch it to OpenGL 3.4 lol I also gave eduke32 a try and the flatpak version would launch Duke3D, Ion Fury, BloodCM, etc but have sound & no video despite what resolution I set it to or if it was on OpenGL vs Software. So I compiled the eduke32 mobile version which will launch my Duke Nukem 3D Plutonium Edition's duke3D.grp but give a CON file compilation error when I try those other build engine games.

NanoPi M5 test report for 26.5.1 vendor images Board: NanoPi M5 Boot media: SD card Kernel branch tested: vendor 6.1.115 Test scope: quick first-boot / first-login / desktop smoke test only. I mainly tested the vendor kernel images because my intended use case requires vendor kernel support, especially for NPU-related use later. 1. Image: `Armbian_26.5.1_Nanopi-m5_resolute_vendor_6.1.115_gnome_desktop.img.xz` Result: OK What worked: * Booted from SD card successfully. * Armbian initial configuration completed successfully. * After initial configuration, the GNOME desktop started normally. * I was able to enter the desktop and open a few basic applications. Notes: * I did not do a full hardware validation in this round. * I did not collect serial logs because the image reached the desktop successfully. 2. Image: `Armbian_26.5.1_Nanopi-m5_resolute_vendor_6.1.115_kde-plasma_desktop.img.xz` Result: FAILED What worked: * Booted from SD card successfully. * Armbian initial configuration started normally. What did not work: * The system got stuck at the Armbian first-login / initialization screen when it was supposed to start the desktop. * It did not proceed to a usable KDE Plasma desktop. Notes: * I only did a basic desktop startup test. * I have not collected serial logs yet, but I can retest and provide logs if needed. 3. Image: `Armbian_26.5.1_Nanopi-m5_trixie_vendor_6.1.115_minimal.img.xz` Result: CLI OK, XFCE installation failed What worked: * Booted from SD card successfully. * Armbian initial configuration completed successfully. * Login to the terminal worked normally. * Basic CLI usage appeared normal. What did not work: * I tried installing XFCE through `armbian-config`, using the XFCE mid option. * The desktop package dependencies appeared to download successfully. * After that, the screen switched to a black screen with a blinking terminal cursor in the top-left corner. * I waited for about 10 minutes, but it stayed stuck there and did not continue to a usable desktop. Notes: * The base minimal image itself seemed to work correctly from the terminal. * The issue happened during or after the XFCE installation/startup process via `armbian-config`. * I have not collected detailed logs yet, but I can retest and provide logs if needed. Summary: * `resolute_vendor_6.1.115_gnome_desktop`: boots from SD card and reaches GNOME desktop successfully. * `resolute_vendor_6.1.115_kde-plasma_desktop`: boots from SD card, but gets stuck at the Armbian first-login / initialization screen and does not reach KDE Plasma. * `trixie_vendor_6.1.115_minimal`: boots from SD card and CLI works, but installing XFCE mid through `armbian-config` gets stuck on a black screen with a blinking cursor.