Nick A

That odd are you sure you didn't mix up the images? I think Tanix, tx6 image can boot on Vontar.

@Felps you need to install it on emmc using armbian-config.

Try this Armbian image https://github.com/NickAlilovic/build/releases/download/20250306/Armbian-unofficial_25.05.0-trunk_X96q-lpddr3-v1-3_bookworm_edge_6.12.11_xfce_desktop.img.xz

@Felps which image are you using exactly?

Hi @Marcelo38 Why did you select Bananapi? There should be Transpeed in the list? In the choose board menu, you need to select "show CSC/WIP/EOS/TVB". You'll find it in the list.

Hi @Jose Ramirez I'm updating the aic8800 driver. Not sure if it will fix your issues. But it seems to be more stable. https://github.com/warpme/minimyth2/commit/bcb3cf537d5c6ebbd5144901cc556e0e28fbdca5 I'll also update the kernel headers using your x98h build. You can build the image yourself it's already updated or you'll have to wait. (if the build stops with an error about 'base-files'. Restart the build It will continue where you left off) git clone https://github.com/NickAlilovic/build.git --branch v20250306

Hi @ketzercat I have 4 different images.. Try them see if they work for you. https://github.com/NickAlilovic/build/releases/tag/20250306

We should change this line in the config. Armbian uses ondemand. CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y # CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set I noticed my box runs pretty hot.

Can you check your kernel config. I think warpme sets the governor to performance. ./compile then select show kernel configuration menu... When it's done downloading the kernel the kernel configuration menu will popup. . Cpu Power Management ->Cpu Frequency scaling->Default CPUFreq governor (????).. what's ???? set too.. It should be ondemand. Don't change it in the menu or save any changes. For some reason it doesn't save all the settings. Better to change it in the build system file. /build/config/kernel/linux-sunxi64-edge.config

@firepower Vontar has a different kernel dts name. U-boot: sun50i-h616-vontar-h618.dts Kernel: sun50i-h618-vontar-h618.dts So in your board config add this at the bottom. function post_family_config_branch_edge__different_dtb_for_edge() { declare -g BOOT_FDT_FILE="allwinner/sun50i-h618-vontar-h618.dtb" display_alert "$BOARD" "Using ${BOOT_FDT_FILE} for ${BRANCH}" "info" }

Warpme's patches has 4 usb nodes enabled. I had to do the same on one of my boards. https://github.com/NickAlilovic/build/blob/v20250329/config/boards/transpeed-8k618-t.csc Instead of making patches you could create a Armbian board config for your Tanix TX6s. All you have to do is change the BOARD_NAME="Tanix TX6s AXP313", BOOTCONFIG="tanix_tx6s_axp313_defconfig" and file name. This will allow you compile warpme patches below. You can do the same for Vontar. https://github.com/NickAlilovic/build/blob/v20250329/patch/u-boot/u-boot-h616/153-add-tanix_tx6s_axp313_defconfig.patch https://github.com/NickAlilovic/build/blob/v20250329/patch/kernel/archive/warpme-6.12/0646-arm64-dts-allwinner-h616-add-Tanix-TX6s-axp313-TVbox.patch +&ehci0 { + status = "okay"; +}; + +&ehci1 { + status = "okay"; +}; + +&ehci2 { + status = "okay"; +}; + +&ehci3 { + status = "okay"; +}; + +&ohci0 { + status = "okay"; +}; + +&ohci1 { + status = "okay"; +}; + +&ohci2 { + status = "okay"; +}; + +&ohci3 { + status = "okay"; +}; https://github.com/NickAlilovic/build/blob/v20250329/patch/u-boot/u-boot-h616/160-add-vontar-h618-defconfig.patch https://github.com/NickAlilovic/build/blob/v20250329/patch/kernel/archive/warpme-6.12/0649-arm64-dts-allwinner-h618-add-vontar-h618-TVbox.patch

I'm missing a few patches for bluetooth: https://github.com/NickAlilovic/build/blob/v20241125/patch/kernel/archive/sunxi-6.10/patches.armbian/Code-to-enable-Internal-OSC-Clock-Auto-Calibration.patch https://github.com/NickAlilovic/build/blob/v20241125/patch/kernel/archive/sunxi-6.10/patches.armbian/Add-Bluetooth-transeed8k.patch Not sure about IR.. the device node is in the transpeed.dts &ir { status = "okay"; }; Maybe I need to enable IR in the kernel config? I see this option enabled. CONFIG_IR_SUNXI=m and this CONFIG_LIRC=y 6.12 https://github.com/NickAlilovic/build/blob/v20250329/config/kernel/linux-sunxi64-edge.config 6.10 https://github.com/NickAlilovic/build/blob/v20241125/config/kernel/linux-sunxi64-edge.config

Jock updated his repository. If you are running XFCE turn off the compositor for smooth playback. killall xfwm4 && xfwm4 --compositor=off &

Sorry but I can't help any further without this device installed.. we are working blind right now. If it still boots Android then the box should be okay. There's always a risk when modifying a tv box. I haven't broken one yet.

This device is used to see the debug messages...

it could be.. the only way to find out is to install one of these... https://www.amazon.ca/IZOKEE-CP2102-Converter-Adapter-Downloader/dp/B07D6LLX19/ref=sr_1_5?crid=AMXIJBW4D3ME&dib=eyJ2IjoiMSJ9.Co3Uo8H4Xww9Sh693R4fJMfx-ODJ6Y_QaEWUP4zIOtoNKGIlFEYRqP4C0KzSPBy8jVLpNByeON_vsk0APSGxvWfseX_G4ItSw4nYPFOw7JRUep64_8ajaRvPhlZcW2TtfcdGMgVoenpBc1oX9hNSzCRAGTOxxVvJGpdVcD1CARcRLg_kgv4aFLwG7eyCtWw0ONVKSXczzt3p10BL2002l1FxX9Ohu9XHD8R22zlKXJu4hincHMKrWIlhaaKPeSYlGVQ7-kIZVtLLiJEyAkrqX_8Z0X4vq1ymDhGfVa4AqsWhnR9HHUTJr1CImmApwUmGCCka59lDC2ENNOSp1aXal0_0bRN6roLH0scZIsYGS8-Jh-R458uQiirWrrawf_pteu8lV_QoPK6xc7NK_5iLBGsydnPyYU9CR92LtK-yP3rlLNhpfexFcgbU73riWwlE.hhyW78XT4oycGfmgiIAbSTrykfO7MEMG9CF1UjqKJ-k&dib_tag=se&keywords=usb+to+ttl+adapter&qid=1743443020&sprefix=usb+to+ttl%2Caps%2C101&sr=8-5

Sorry I never played with openwrt on these boxes. I found this.. not sure how it works. But I see x96q-lpddr3. https://github.com/armarchindo/ULO-Builder

@Felps Try this image. If it boots I'll make you a Armbian image. https://github.com/warpme/miniarch/releases/download/gdde1069c/MiniArch-20240715-6.14.0-board-h616.tanix_tx6s_axp313-SD-Image.img.xz

Try this image

Can you extract your dts from your original android. You directory structure might be different.

Which wifi chip do you have? Can you upload your dmesg logs here?

I use BalenaEcher.. never tried Raspberry Pi imager.

I can't tell you which u-boot image to use until I get more information. u-boot is in the images you write to your sdcard. If you want try all these images. https://github.com/NickAlilovic/build/releases/tag/20250306 The best way to know if it's booting is to install a usb serial ttl device to your uart. Then use a terminal software to view u-boot/kernel messages. sudo gtkterm -p /dev/ttyUSB0 -s 115200