Active threads

Okay here's a huge update and a win for me: While i stopped playing with the kernel, i focused on improving openauto by replacing GStreamer with ffmpeg and utilizing the same RTAudio to Alsa Patch which achieved the following things: 720p 60 1080p 60 FPS Stream (cma set to 265) RTAudio to Alsa (Video and Audio are synced) Low Latency Touch or Mouse Response Now while there is still some bugs like when i disconnect my phone by pulling the usb cord results into a segment fault i'd say that's just a minor bug that can be fixed along the way. Huge thanks to the experimental ffmpeg patches and the guide @jock PS: hopefully someone can help me improve the code even more, i know this board is capable of being an android auto head unit for those who like to build it on their own: Github: Openauto-rk3229-armbian (requires you to compile aasdk)

@Werner, @Igor: Is the Raspberry Pi 500 supported by Armbian? It’s the successor to the RPi 400, for which support is mentioned. Internally, it looks similar to the RPi 5, except that it seems to lack wifi.

Hi! This is my first message here, congrats to the community for building this I would also like to corroborate that the current Balena Etcher, in Windows at least, is not writing the image correctly to the SD card. The Armbian imager did it well for me. I just booted an unused A95X (S905X) "Mini Kitty" with Armbian, but I don't think I will spend too much time with it, I already got a lot of mini PCs for servers and it's too slow for a terminal 😅 What do you recommend me to do with this little box? Thanks!

It is a AP-mode problem of the Realtek 8822CE chipset. Replaced the M2 card with Intel AX200 card and since then solid as a rock

Armbian 25.11.2 Noble XFCE (BSP Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + Box64 arm64 v0.4.1 72807b6b9 (https://ryanfortner.github.io/box64-debs/) + proton-10.0-3-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/download/proton-10.0-3/wine-proton-10.0-3-amd64-wow64.tar.xz) + dgVoodoo2 (https://github.com/dege-diosg/dgVoodoo2/releases) + DXVK-stripped v1.7.1 50~60fps@1080p (no AA) box64 environment variables: FlatOut 2 Enhanced

@Nick A I flashed your latest build in Dec.2025 which is named to use for Transpeed, and in addition, manually added brcmfmac4334 firmware. Wifi is working now but bluetooth. Other malfunction in previous rom version April.2025 also disappear. Thank for your time to advise me

I downloaded image today using Armbian Imager, and it asked me to run something like armbian-update. I installed the system afterward, but it didn’t work.

Ordered 2 more X96Qs off aliexpress. will see what versions i get. Will build images for them if they're different.

@SuzSinclair Start by reading the first post of this thread, which has all the information you should need to get started.

There is no way. You need a dedicated image for your hardware. https://docs.armbian.com/User-Guide_FAQ/

@Torte continued to help on his github site. The boot.img of the OEM firmware appears to set up a serial framebuffer screen and some shenanigans with the camera. I'm pausing the thread for now - need to figure out a path to reverse engineer the boot.img. Otherwise, alternative boards will need to be adapted.

Coming late to the party, but I have observed a similar thing with moderm kernels on PCduino 3 nano. To know what is happeneing, have you tried connecting to UART? That gives you more info about what is going on. Now I have trouble with the OTG port. I am unable to configure it for mass storage.

Mine is M1, no plus, so no WiFi. I used the following 2 years ago when I got the SBC: https://fi.mirror.armbian.de/oldarchive/bananapi/archive/Armbian_23.11.1_Bananapi_bookworm_current_6.1.63.img.txt

OK so how can I help to fix this issue?

Userspace has nothing to do with hardware features. I don't know what is the case for A20, but for many others, OTG functionality is driven with overlays. If there are no overlays, you need to edit device tree and change its role. If that doesn't help, it is more complex problem. More complex, perhaps days / weeks to debug and fix. Most of (Armbian) kernel developers are long gone from this 10+ years old platform and users can't help. Also look into previous builds. Finding out when this broke is half of the solution https://fi.mirror.armbian.de/oldarchive/ or by finding a kernel that works https://docs.armbian.com/User-Guide_Armbian-Config/System/#alternative-kernels With any userspace (trixie/noble/jammy ...) Probably all A10 and A20 boards share this problem.

@shexplorer Control +c should have worked after: U-Boot SPL board init U-Boot SPL 2017.09_armbian-2017.09-S93fe-Pe5fd-Hbdb5-Va5b2-Bbf55-R448a (Nov 06 2025 - 16:35:49) SPL Hotkey: ctrl+c Make sure that USB TX is well connected to RX and try to spam it. Or use another terminal emulator, like putty instead of screen on a bash terminal. Maybe control is being intercepted.

I think it depends on what you want. If you want to have some fun, then building this one is interesting actually, and there is more extensibility, and since radxa zero GPIO pin is compatible with Raspberry pi's, you can also get a DAC Mini Hat raspberry pi module, so there is more you can play or customize. But, if you just want to solve the problem and don't want to have these hassle, buying an existing product is a better option, so you have the warranty, customer support, and everything should work out of the box. I don't have Fosi Audio DS1 or Fiio Ka13, so every information I get is from the google search and cannot guarantee the correctness. From what I saw, Fiio Ka13 seems to be unable to work with PS5, and Fosi Audio DS1 can. This project only handles digital audio data, so I do not need to pay attention to the audio electronic properties when outputting (because that's the job of that USB speaker), and I do not know the sound quality of Fosi Audio DS1. One last word, if your original plan is to use this converter to connect to Hiby R3II, then to your headphone, that should work, but that is kind of redundant; there is more latency introduced, and the robustness could be wore because you have a longer output chain (from the engineering perspective). It would be easier to just get a high quality UAC 1.0 Amp.

Tried this?

What exact image are you running? Or better yet providing full logs with armbianmonitor -u

I installed Waydroid on an Amlogic Meson GXM (S912) TV box. The SOC has a Mali-T820 GPU, and the box has 2 GB of RAM and 16 GB of eMMC. This was easy to do and Waydroid worked, but it was very slow, even before it heated the SOC to 80°C, which is probably its throttling limit. I removed Waydroid because it was too slow. I wasn't trying anything demanding. Even navigating Android Settings was ridiculously slow. This is a bit surprising because the hardware was designed for running Android. I was not running much else, just Wayfire and one or two Alacritty consoles. I don't think I was running out of memory. Is it possible to get decent Waydroid performance on other arm64 hardware?

Ubuntu Noble variant already supports ZFS on 6.18.y while Trixie was added today: https://github.com/armbian/os/pull/425 Testing: Once automation completes, it will be provided via normal apt update.

Hello. BTT says what BTT Pi and CB1 is same, but realy not. Dunno why i brought what board. But now I owner of this "piece of ****" So. New board, clean install v25.11.2 for BigTreeTech CB1 running Armbian Linux 6.12.58-current-sunxi64 Packages: Debian stable (trixie) armbianEnv: overlays=gpu tft35_spi extraargs=fbcon=rotate:2 fbcon=rotate:2 for screen rotation, because armbian not from btt and didn`t have feature like param_tft35_spi_rotate Next, help me to determine how to enable UARTs and I2C From BIGTREETECH_Pi_V1.2.1 Hardware Pdf UART0: CPUX-UTX CPUX-RX UART2 (May work as i2c0; uart2-pi-pins; i2c0-pins ) Pi5 Pi6 UART3 (May work as i2c2; uart3-pi-pins; i2c2-pi-pins ) Pi9 Pi10 I2C (i2c4-ph-pins; spi1-pins): PH6 PH7 (must work, i`ll think i2c4-ph overlay present) All pins present in sun50i-h616-bigtreetech-cb1-sd, but didnt have overlays for it... I wish to stay uart0 for u-boot console first uart setup for klipper connections to mcu. any help? If I understand right PH6 is 7*32+6=230 gpioinfo output line 230: unnamed input consumer=kernel line 231: unnamed input consumer=kernel cat /sys/kernel/debug/gpio gpiochip0: GPIOs 0-287, parent: platform/300b000.pinctrl, 300b000.pinctrl: gpio-71 ( |spi0 CS1 ) out hi ACTIVE LOW gpio-74 ( |i2c-gpio ) out hi gpio-75 ( |spi0 CS0 ) out hi ACTIVE LOW gpio-76 ( |i2c-gpio ) out hi gpio-77 ( |spi0 CS2 ) out lo gpio-78 ( |dc ) out hi gpio-166 ( |:wifi_power ) out hi gpio-207 ( |:wifi_wake ) out hi gpio-210 ( |reset ) out hi ACTIVE LOW gpio-229 ( |led-0 ) out lo ACTIVE LOW

Does this mean you have a working DTS that fixes the issue with smc starting the the other 3 CPUs successfully?

hallo @WanJiXianSheng, responding to this image, for the SUB position where the SD card is installed, there are 3 cables, what is their function? Please share here the guide for flashing to Armbian thx..