JMCC

Probably the unique network interface names "feature" has misconfigured your network. I don't use OMV, but in regular Armbian I would use armbian-config to reconfigure network.

As I said just above, look in the first post

Hello! In the first post, you have links to all the sources, most of them from my GitHub repos. The procedure might be outdated, though, I haven't touched it since 2019. For Kodi, you can try the rockchip branch for legacy kernel, or the mainline branch for current. Compilation instructions are included in the repo. Good luck!

It would need a complete rework and recompile

Well, I don't even own a RPi, but here are some suggestions: You mention several OS'es, but not Armbian. Have you tried Armbian? If not, that would be the first thing to do, specially since you asked here :) In your video, you show RISC OS, and apparently it is running a armv7 version. Could it be that 32-bit ARM OS's are working, but 64-bit are not? If this is the issue, then maybe you can try to build 32-bit Armbian image and see if it works. It could also be a device tree issue. Maybe you can extract the DTB from some of the OS's that are working, and try to use it with an Armbian image.

Do you have emmc or only SD card? Renegade legacy images don't get along well with SD cards (it was a problem with regulator voltages, and didn't affect all units). For example, mine worked only with certain older legacy images on SD card, but it broke somewhere around early 2019. So do you have emmc? If so, the easiest is boot the board from a current image, and then flash legacy from it into emmc. I can teach you how to do that If you don't have emmc, please try this image: https://armbian.tnahosting.net/archive/renegade/archive/Armbian_5.75_Renegade_Ubuntu_bionic_default_4.4.174.7z , and use the old multimedia script instead (DO NOT upgrade the kernel, use "apt-mark hold"):

The version shipped with Buster works just fine with this integration

This one

Look at the first post of the thread, there you have all info about the sources

Get a Buster legacy desktop image from here: https://armbian.systemonachip.net/archive

Sorry, I don't have that board and have not tested the framework on it. Maybe you can build an image and try.

First of all, for this multimedia integration to work, you need to be running the legacy kernel (4.4.x). You don't specify which kernel you are running. Second, AFAIK the only option to make HW encoding to work is gstreamer. This solution will install the required gstreamer plugin (see first post). But Jellyfin uses ffmpeg, so it is difficult that you can make it work with gstreamer, without editing the code and recompiling. Maybe another option is using a wrapper script that uses a ffmpeg pipe, and pointing the custom ffmpeg version from Jellyfin menu, but I have never tried something like that. Third, and most important, if you want to post any question, please follow the forum guidelines and provide all the necessary information.

Sure, you can PM them to me, please. On a side note, I finally got to re-flash some image to my TV box, using a usb-c to usb-a cable on my laptop. This one seems to make the box run a bit hotter and maybe faster, I will try to investigate whether memory is clocked at 666MHz or not. [EDIT: No, all dmc opp's 400MHz and above are disabled. But the CPU opp at 1104MHz is runnig at a voltage of 1275/1275/1350, hence the heat. This is crazy...]

No prob, I was counting on the possibility of bricking it, but it was just a 20€ crappy device laying around. And it is not bricked after all, yet it works faster than factory with Armbian, and even have WiFi, which I didn't expect 😆 I'm on vacation and I don't have any USB-OTG cable here, so I cannot use the RK flashing tool. There is an option to create an "upgrade SD card", but it only supports cards up to 16GB, not bigger (WTH?), and also requires a reset button which seems not to be present on the device. This also motivates me to spend some time finishing the media integration for Mainline, so I can at least use Kodi on this 😄

Sorry, anybody has a stock-android flash backup for X88 Pro 10, made with jock's Multitool? I have been trying to use the official Rockchip tool to flash the firmware, but no luck, these devices are so crappy... (More info: I made a backup, but it is corrupted due to the 4Gb bug)

@jock Thanks for the info. On a side note, I found a small bug: when making the emmc backup, if the resulting file is bigger than 4Gb it will just stop there (because of the FAT size limit) and you will get a broken backup. Probably could be solved by splitting the backup, for example along these lines: # Split backup in 2Gb parts, with two-character suffixes dd if=/dev/mmcblk1 | gzip -c | split -b 2000m - tvbox-backup.img.gz. # Restore the backup cat tvbox-backup.img.gz.* | gzip -dc | dd of=/dev/mmcblk1

@jock I got some X88 pro 10 laying around, and tried your solution. It works great, I was able to boot from the multitool, and flash Armbian to the emmc. However, I am wondering if there is any possibility to keep the original Android on the emmc, and boot Armbian when plugged on a SD card/USB. After all, if it can boot the multitool with the original firmware on emmc, there must be some way to boot the full Armbian image, right? Maybe an issue with Mainline U-Boot, and you are using BSP u-boot for the multitool?

IT'S FINALLY HERE... THE OFFICIAL ROCKCHIP-LEGACY MULTIMEDIA INTEGRATION After two years of using a separate script to enable the multimedia features in RK3399 Legacy Kernel, the whole framework has been incorporated to the official Armbian packaging system. The choice distro for this integration is Debian Buster (see FAQ at the end of this post about the reasons). I. Installation Download a Armbian Buster Legacy Desktop image for your board, and install it with the standard Armbian method. Install the complete multimedia solution with sudo apt update && sudo apt upgrade sudo apt install media-buster-legacy-rk3399 --install-recommends The switch "--install-recommends" will add the whole Kodi binary addons collection (retro-gaming cores, music visualizations, screensavers, additional media decoders/encoders, vfs, etc.), plus the GLES-to-OpenGL wrapper "gl4es". II. Features Accelerated GLES/EGL X desktop: No action needed. Accelerated Chromium, with WebGL and video display acceleration: No action needed Desktop video player capable of smooth 4K HEVC-HDR: Use the "Rockchip Gst Player" from the Multimedia menu, or choose it with right-click on the media file. Command-line 4K playing is also possible with "gst-play-1.0 --videosink=kmssink". RKMPP-accelerated MPV: Use normally for standard operation (windowed with mouse-operated GUI). For fullscreen, keyboard-operated mode, use the command line switch "--gpu-context=drm" (this will allow you to play smooth 4K). - See instructions below, in the next post, for playing YouTube videos up to 4K with this MPV. ISP Camera with real-time h.264/1080p HW encoding: Using the Gstreamer Plugin. Check this wiki for instructions on how to use it. Most of it applies to Armbian, except for the selection of ov5647/imx219 camera, which must be done using DT overlays. OpenCL 1.2 support: It will be fully functional, no further action needed. You can download some tests and examples from this link. Kodi 18.9 Leia with full RKMPP+GBM acceleration, 4K-HDR capable: You can start it from LightDM menu as your user account: Alternatively, you can also run it as a system service with these command lines: sudo systemctl disable lightdm sudo systemctl enable kodi-gbm sudo reboot Full collection of Kodi binary add-ons: Includes retrogaming cores, media encoders and decoders, PVR, screensavers, vfs and audio visualizations. They are all installed with the package "kodi-addons-full", but are disabled by default. They need to be enabled individually within the Kodi GUI. OpenGL 2.1 support through the gl4es wrapper: It is installed with the package "gl4es", with no further action needed. III. Sources This is the list of the sources used for the packages: IV. FAQ ¿Why did you use Debian Buster as a base for this implementation? It was the most appropriate for several reasons. Upstream Rockchip-Linux developers use Debian buster, so the software could be ported with less modifications than if we chose a different distro. Besides, it is a completely stable distro, unlike Bullseye, which is a moving target as of today. It also has Chromium as a package, unlike Focal that uses snap instead. For last, it has a good backports repo, with several libs that would otherwise need to be compiled and maintained if we chose, for example, Focal. ¿Why Legacy instead of Mainline? This is an implementation based on the vendor's BSP kernel. It has been tested and is reliable, which many people will prefer rather than having a bleeding-edge, less stable implementation. In addition to that, Mainline upstream multimedia support is still a WIP, and lacks many features that are only present on Legacy kernels. ¿Will you add new features to this implementation? No, this implementation will only receive bug fixes if necessary. From now on, all multimedia work will be focused on Mainline and recent distros (like Focal or Bullseye). All new features will go there.