If using deinterlaced media make sure the 1080p@25/29.97/30 modes are NOT enabled in the whitelist so that Kodi will default to 50/59.94/60; as Kodi only outputs progressive and needs to render each interlaced half-frame as a full frame, requiring double the frame rate. Also set "Adjust refresh" to start/stop not always.
The one upgrade you can do that would make a difference is to replace the ATA drive with an SSD, as the stock drive is 5400rpm (and likely around a decade old - the fact it hasn't failed is a miracle) and although RAM is an unresolvable issue, swapping on an SSD is greatly improved. I've used SATA SSDs via an adapter in the past, but Amazon/eBay show mSATA to IDE/ATA drive converters now which would be easier to fit inside the case.
Which LE release?
Do you have "WireGuard.PersistentKeepalive" in your config?
I don't see issues with the connection dropping from LE, but I sometimes see issues from macOS to the same WG server.
The OE 6.0.1 image is the best-performing release for the AppleTV that I created as it has hacks like nVidia shader caching and a startup sequence in Kodi designed to force things into swap to create free RAM headroom that helps subsequent playback. However it's all a fudge/compromse and both OE and OSMC have the same fundamental issue: the CHD drivers are not perfect and 256MB RAM is not enough for good Kodi operation.
NB: An RPi Zero (€15 new, prob. cheaper used) with 512MB RAM would be a huge improvement over a mk1 AppleTV.
Setttings > System > Display > Whitelist .. add the specific resolution/refresh rates that you want Kodi to use, e.g. [email protected]/24/50/59.95/60 (skip 25/29.97 if you have interlaced media) and in Settings > Player enable "Adjust display refresh rate to" start/stop.
The Android box market moved onto newer/shinier things so S912 is long-forgotten as the top device in Amlogic's line-up, but there is still commercial interest in S912 from industrial users. LibreComputer is about to release a new board (tartiflette) and because GXM is only a minor evolution from GXL it's a solid/stable platform, which is key for that audience. I've been passed some S912 devices recently and even without an Android dtb or schematics it's been fairly trivial to get all the core hardware working.
However, the tricky bit is always the boot firmware. You either need to self-compile a recent mainline u-boot and experiment with fip sources. The only public ones are for VIM2 and Tartiflette so that shouldn't be a lengthy exercise. Or you extract something from an Android image. Until you solve that piece of the puzzle building higher-level distro's (meta-meson, LE, Armbian, etc.) isn't going to be fruitful.
Setting the wireless regulatory domain may also help to ensure the correct spread of radio channels is available. This becomes a GUI setting in LE 9.2.3 .. before then it has to be done manually from a conf file.
The only way to force a connection to 5GHz only networks is to set the router so it has a dedicated SSID for 5GHz and then only authentticate the LE device to that SSID. Otherwise the WiFi card is doing what it's supposed to do .. find the best connection and use it. The problem with all WiFi networks is that connectivity and performance are variables that are largely outside your control.
RPi4 does not support any decoder licenses as the CPU is capable of software decoding the formats that historically required them.
You have banned repo's installed. No futher support. Official:Forum rules/Banned add-ons - Official Kodi Wiki
It is banned pirate crapware. End of conversation.
If you're using the .img.gz files that I linked, it's the first and only Amlogic device I've encountered which is not looking for boot firmware in the normal and known locations, and there isn't much I can do to help. The last dice-roll is writing them to a USB stick instead of an SD card.
I think the minimum supported version will be around 10.9 but you can always use "dd" to write things under macOS.
Those logs show no sign of u-boot at all, so I think the SD card image is not written correctly. Even if the boot firmware has the wrong SM1 fip sources or bad RAM timings you'll still see BL2 loading and some form of output on the console.
The C4/VIM3L images have a single dtb in them for the respective device. The "box" image has all the dtb's including the SEI610 dtb. You can copy the SEI610 dtb from that image to an SD card created from the C4 or VIM3L images and then edit extlinux.conf to change the dtb name.
I've had more success using the VIM2 dts with random boxes than the Q200/Q201 ones. That's also true of boot firmware - the 'vim2' suffix image on our test server is for emmc installs and has mainline u-boot in the imaage, but to test that you'll need to erase emmc first else the box will always find BL2 in emmc and use it.
