jeanrhum

First test with ugoos ut3s with default dtb (firefly-reload): http://ix.io/2o7o
For information, I have jock uboot and an old Q8 image installed on emmc.
Wifi works, but ethernet seems buggy like on recent arm64 images (kernel 5.X pb with current dtbs ?). I didn't test it, but the connection was activated whereas no cable... System halts instead of reboot.
Bluetooth seems not working well (xfce applet disappear when I try to use it to activate)
With Q8 dtb the experience seems similar from a user perspective: http://ix.io/2o7q
With popmetal and tinker dtb, the system does not boot: waiting root file system... running /scripts/local-block
With miqi dtb, it boots, but without wifi and I was not able to connect a cable to test the wired network, but eth0 still shows as connected.
 
Edit: As I noticed on Jock images, the Q8 dtb is not able to detect emmc on contrary to firefly-reload.

And there are a number of important differences between ArmbianTV and the official versions. For example, there are two sections. The first boot partition is necessarily made available for any PC (Windows Linux MAC etc), in particular it uses FAT. This is crucial. This allows any user, on any device, to easily configure system startup for their device. In case of problems with startup, it can connect the media to any PC and easily edit startup parameters, enable new options, change settings, add/delete files, etc. With official versions, this is not possible on a Windows PC, which greatly narrows the circle of users who want to start using Linux (Armbian). The official versions also use oters technologies. Installation in eMMC using direct bitwise copying of the source system (via DD).  use of the UUID, etc.
Please note that I do not impose anything on anyone or criticize the official version. I'm just stating the differences. Developers of the official version decide what to do and what to use.

Images with two kernel versions are available for testing.
Legacy.
Uses the 5.4 core built using source code and patches (with minor fixes) that are used to build the rockchip.
 
DEV.
The core 5.7-rc7 is used (the sources are shared with the version I use to build aarhc64 images).
 
There are no patches in this version yet. The legacy version has almost all the working hardware on UM3. On the DEV version, not everything works, but there is access to eMMC. how it is used (the setting for running is the same as the aarch64 version of images). To configure dtb, use the file (uEnv.txt). At this stage, I used settings and patches from MIQI to build the u-boot. I tried the u-boot version from Q8, it works the same way, but I haven't decided which version is better to use yet (I haven't fully figured out what the pros and cons of these u-boot versions are).
 
The link to the images and the launch order will be placed in the first message.

I opened this theme to support running ArmbianTV on 32-bit ARM models. To date, there are first results on launching ArmbianTV on the Rockchip rk3288 and AML s8xx platform (in the future, by analogy with aarch64, I plan to switch to a common image for all 32-bit models of TV boxes).
 
 
 
The link to the images
https://yadi.sk/d/85ZvBuXyyenf_A
 
 
MEGA (name -rk3288)
https://mega.nz/#F!j9QSDQSQ!6WpasOlbZYIInfw6yo4phQ
 
Now you can download the latest versions of images and DEB packages from the official Armbian resource via the link. 
https://users.armbian.com/balbes150/
 
 
Recommended startup procedure on UM3.
 
1. Install the Linux firmware version in eMMC (either a dual boot or a single Linux).
2. follow these instructions to download and run the Linux version from linuxium
 
https://forum.freaktab.com/forum/tv-player-support/rk3288-devices/21091-use-windows-to-create-an-sd-card-so-you-can-run-linux-on-a-rk3288-device
 
(do not forget to immediately expand the system partition to the entire media after writing the image). After launch, make a full backup eMMC with the DD command (or copy the ddbr utility to the system and use it).
3. Erase the first 4Mb on eMMC (using a simple DD command).
4. Download, unpack and burn the ArmbianTV image to your SD card.
5. Connect to the TV box and turn on the power. The system will start automatically.
 
For those who are not afraid to lose their regular firmware and be able to easily restore it later, you can use the "accelerated" launch option (erase eMMC use the tools for Rockchip TV boxes). 
 

One suggestion is to forget about this WiFi chip and use a USB chip.
 
 

The new version 20.05.5 (20200522).
All images are build entirely on the ARM platform (rk3399 + NVMe). After fixing bugs, the process of building the first image (including downloading sources, building all packages, building the kernel, u-boot, and so on) took less than 50 minutes. 

@Armin
if you need just something such small, you may find nanopi or orange pi boards. Some small models are pretty cheap (<10$) and well supported by armbian. Tv boxes have no exposed GPIOs, which can instead be very useful for domotic applications.
For example, I have an old Orange PI One (Allwinner H3) which has ethernet, 1 USB port, 512mb of ram and some exposed GPIO. I paid less than 10$ some year ago. I guess now you can get something similar with wifi too at the same price.

No SPI - is very bad. Use an SD card (speed 50) or eMMC (speed 125) , if you have USB 3 (speed 340), to work - you need to be an idiot. At the same time, u-boot placement is possible only on SD\eMMC\SPI and therefore for the system to work with USB, you will have to have either an SD card (all SD cards are complete crap in speed and reliability and I generally consider them only as temporary media , such as CD\DVD on a PC), or buy an expensive branded EMMC module (almost 15$ for 8Gb), just for the sake of starting the system from USB. HK needs to be added before mass release SPI (only 4Mb is enough) and make it the main carrier for u-boot placement.

The version of the image 20200323.
Resolved then issue of pulseadio conflict with the G12 audio device . Now you don 't need to delete PULSEAUDIO. To enable audio on g12, you only need to run the script (g12_sound.sh) or for GX\GXM models, run the script (gx_sound.sh).

These are debian and ubuntu release names. Prefer buster if you want debian or bionic for ubuntu.

Hi,
I tested several sbcs:
- buster image for pine64: http://ix.io/2bMQ
- buster image for OPi+2E: http://ix.io/2bMU
- buster image for pineh64-b (wlan0 visible, but not able to connect to my wifi network): http://ix.io/2bN0

Currently amlogic s922x or A311D are the most powerful socs (4xA73). The first one can be found some tvbox like beelink gt king or ugoos am6 and the second one in khadas vim3.
I think that most rk3399 boards have better supported than amlogic ones.
 
For your second question, it mainly depend on your use case.

Hi, writting from my box. I use the latest image from balbes150. base don kernel 5.5.1 with meson-sm1-sei610.dtb. Trying to use the color trick for g12 board doesn't work for me, the board does not boot at all. Without considering the color problem, the desktop experience is smooth and the soc stay cool even if I have remove the heat sink (<50°C without heavy loads and go up for 60°C when watching test videos on mpv or chromium).
 
eth0 is visible but not able to send/receive data. wlan0 not visible, I use an usb dongle. Bluetooth seems active but not able to detect a bluetooth audio speaker.
 
Stop here since the blue color is not comfortable, but a more detailed report can be found here: http://ix.io/2bEh
 

Currently amlogic s922x or A311D are the most powerful socs (4xA73). The first one can be found some tvbox like beelink gt king or ugoos am6 and the second one in khadas vim3.
I think that most rk3399 boards have better supported than amlogic ones.
 
For your second question, it mainly depend on your use case.

ver 20.02.0-rc1 20200129
 
The sound works on all models S9xxx, rk3399 , rk3328 , aw h6.
Please note that to enable audio on g12 chips s922x s905x2 (models Ugoos AM6, Ugoos x2, Odroid N2 etc), you must follow the instructions specified in the first message.

this is just a quick note that in my experience the amount of tv boxes with fake specs has grown quite a bit in the last months and that this is something to always have in mind when getting a box for a surprisingly cheap (i.e. quite a bit cheaper than usual or most of the other offerings) price - you might be lucky and it will be a bargain or you might hit one with fake specs. some examples i saw recently: a qplus 4g ram / 32g emmc ended up to be 2g ram and 16g nand, a h6 box sold as 4g ram / 32g emmc ended up as 2g ram / 16g emmc, a x96mini 2g ram / 16g emmc ended up at only 1g ram / 16g emmc, a r39 2g ram / 16g emmc with rockchip rk3229 ends up as 1g ram / 16g emmc and an allwinner h3 cpu and so on. the fake specs are not that easy to spot: in android they even fake the storage size shown in the storage settings and with a terminal installed even the "free" command tells you most of the time that the memory amount is proper. what usualy works for storage is "cat /proc/partitions" and watching for the device itself (for instance mmcblk0) - this also quickly shows you if its emmc (=mmcblk) or nand (=nand) and for memory "dmesg | grep -i mem" (do this immediately after booting android, otherwise the memory lines from the bootup might run out of the log buffer) - both of course called in a terminal app. booting one of balbes150's armbian images usually quickly shows you the real specs of the box too.
 
good luck at not ending up with fake boxes and best wishes - hexdump
 
p.s.: one thing to keep in mind is that allwinner h6 boxes always only can use 3g ram, even if they have 4g installed - this is a limitataion of the soc ...

In the new year, I plan to focus on improving and developing Armbian-TV  (Armbian-TV is a version that is based on the official Armbian, aimed at improved support for media capabilities and ease of use by ordinary users) support for the platforms Rockchip and Allwinner  (perhaps a few more platforms will be added that are not yet in use). To do this, I have already ordered several popular models based on rk3399 (NanoPC T4, RockPi 4, Renegade-Elite), in a complete set with obligatory Support of nvme carriers (I consider this support essentially important, for transition of TV boxes and SBS to the category of mini-PC, as highly effective and improved replacement of the usual PC). I'm plan to buy several more models on Allwinner (I'm still evaluating the capabilities of the selected models). 
I had plans to buy some more models based on rk3399 from other manufacturers, but there were problems with delivery and / or payment for my country.
 
If anyone has any suggestions for models that I should consider, I'm willing to listen to reasonable descriptions of the models.

For the same price, I prefer to buy an ugoos am6 pro (what I have done). The sdcard with coreelec is not so interesting compared to what you can get for balbes150 excellent work.

Armbian (5.98_20191018) and Libreelec KODI-19 (kernel 4) 20191018 images update for rk3399 platform with USB startup support. Important change. When testing these images on Magicsee N6 Max (rk3399) and MVR (rk3328) I found an interesting nuance. If you install one of the versions of Armbian or Libreelec in eMMC of these models with support for launching from USB, you can write to a USB flash drive any version of the image for rk3399 or rk3328 and use it on both platforms (on TV boxes with rk3399 and rk3328 at the same time). I. e. the image from rk3399 can be run on rk3328 and Vice versa (you only need to correctly specify the desired DTB in the settings).
 
 
p.s. On Magicsee N6 Max running from USB works on both USB 2.0 ports (on the left side of the TV box).

I'm not going to waste my time on all the shit that manufacturers shove in their crafts (just to write on them - WiFi available). Want to have WiFi, you have several options.
1. Use normal equipment where there is guaranteed WiFi support.
2. Use external USB WiFi with good support.
3. Themselves add the necessary support for your WiFi.
4. You seek from the seller\manufacturer of your equipment the necessary support.

Hi,
You'd may look at this topic:
With jock image, I'was able to boot my ut3s. I didn't take time to customize a dts to have a better support, but it was useable for a light desktop.

Small progress update -
 fresh photo.
 
 

Added nightly minimal images (root ≈ 500 Mb in size) for La Frite.
https://dl.armbian.com/lafrite/

Added a wip target to the build system, it is dev kernel only, and builds just fine, however booting is another issue I've not spent a lot of time with yet:
 
Found U-Boot script /boot/boot.scr 3048 bytes read in 11 ms (270.5 KiB/s) ## Executing script at 08000000 154 bytes read in 5 ms (29.3 KiB/s) ## Error: Can't overwrite "ethaddr" himport_r: can't insert "ethaddr=00:50:43:84:fb:2f" into hash table 8101414 bytes read in 217 ms (35.6 MiB/s) 16093192 bytes read in 416 ms (36.9 MiB/s) libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! 232 bytes read in 26 ms (7.8 KiB/s) Applying kernel provided DT fixup script (meson-fixup.scr) ## Executing script at 34000000 ## Loading init Ramdisk from Legacy Image at 13000000 ... Image Name: uInitrd Created: 2019-08-12 5:04:59 UTC Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 8101350 Bytes = 7.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree The device tree is there in the /boot/fdt/amlogic folder, and the script is the same for Le Potato/ Khadas Vim/Nanopi K2 and works.
 
[some minutes elapse]
 
I think I found it, the printenv (had to figure out the UART, not an easy task) shows me
 
fdtfile=libre-computer/aml-s805x-ac/platform.dtb
 
...which is completely wrong in a normal context, where it should match the linux device tree:  meson-gxl-s805x-libretech-ac.dtb
 
I'll try to figure that out later.
 
 

I was under ubuntu using gtkterm.
 
It's nice to see your experiments even if it has been better that realtek and manufacturers published documentations.