Type this commands in SSH console to update the addon. To see if there is any difference.
wget -O driver.dvb.sundtek-mediatv-10.80.0.105.zip http://vpeter.libreelec.tv/tmp/driver.dvb.sundtek-mediatv-10.80.0.105.zip
killall -9 mediasrv
unzip driver.dvb.sundtek-mediatv-10.80.0.105.zip -d /storage/.kodi/addons -o
rm driver.dvb.sundtek-mediatv-10.80.0.105.zip
rebootYes, addon is broken for Kodi Matrix. I will update it in next few days.
Can you show some pictures?
What about if you post this problematic subtitle file and someone can replicate the issue?
offending code is within kodi
What about if you would show this code to make analysis easier? And if the code is in Kodi open issue there?
racko, this adapter has one chip on it - can you read what is it?
this patch are for another kernel of linux I think.
Sure, but the idea was to support both versions at the same time - yours supports only b.
You could use this patch to support A and B variant at the same time: Bluetooth: btrtl: Add RTL8761B Bluetooth device · CoreELEC/linux-amlogic@957a18a · GitHub
I dont know how
Add it to your command?
This argument is probably needed
--rsync-path=/storage/.kodi/addons/virtual.network-tools/bin/rsyncAh, touch device restart is not something I think off.
You can took parts from here too if you want: Kernel NFS server by vpeter4 · Pull Request #250 · CoreELEC/CoreELEC · GitHub
What exactly is hardcoded? Because It should set correct device based on it's name with using evtest program.
There is an option in addon to update the driver itself from Sundtek.
So basically all the big words for last 2 years were way to much optimistic.
I wonder what "improvements" have been hacked into the latest Khadas bootloader.
Maybe related to this: init/Kconfig: increase INIT_ENV_ARG_LIMIT as otherwise maybe the limi… · CoreELEC/linux-amlogic@1689530 · GitHub
Why haven't you PR'd your changes yet?
Because you refused the changes I proposed on Slack. And I don't bother doing same thing twice.
Want a cookie?
Yes please. Can I send you an address? 
Because I was bored today I looked this issue just for fun. Like Gentoo Wiki link I posted.
After examining how U-Boot works with extlinux.conf I noticed that there is a tag named FDTDIR which specifies the directory where FDT files are located. The actual filename is set by U-Boot and allows booting similar devices from same image. The requirement is that all dtb files must be in some folder pointed by FDTDIR tag.
So there is no need to use 2 (or more) images and follows LE way of using modern extlinux.conf 
Seems I'm still the most knowledgeable man with i.MX6Q U-Boot
LABEL LibreELEC
LINUX /KERNEL
FDTDIR /
APPEND boot=UUID=2812-4128 disk=UUID=0ed065e2-54e6-47ca-95e5-47a652053a43 quiet console=ttymxc0,115200 console=tty0U-Boot SPL 2020.10 (Dec 28 2020 - 09:41:54 +0100)
WDT: Not found!
Trying to boot from MMC1
U-Boot 2020.10 (Dec 28 2020 - 09:41:54 +0100)
CPU: Freescale i.MX6Q rev1.2 1200 MHz (running at 792 MHz)
CPU: Extended Commercial temperature grade (-20C to 105C) at 25C
Reset cause: POR
Board: MX6 Cubox-i
DRAM: 2 GiB
MMC: FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... *** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Card did not respond to voltage select!
Net: Could not get PHY for FEC0: addr 0
No ethernet found.
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
161 bytes read in 21 ms (6.8 KiB/s)
1: LibreELEC
Retrieving file: /KERNEL
11815896 bytes read in 568 ms (19.8 MiB/s)
append: boot=UUID=2812-4128 disk=UUID=0ed065e2-54e6-47ca-95e5-47a652053a43 quiet console=ttymxc0,115200 console=tty0
Retrieving file: /imx6q-cubox-i.dtb
37891 bytes read in 19 ms (1.9 MiB/s)
## Flattened Device Tree blob at 18000000
Booting using the fdt blob at 0x18000000
Loading Device Tree to 1fff3000, end 1ffff402 ... OK
Starting kernel ...