I am asking on the off chance, is there a way to install that dependancy without rolling back to an older version or breaking things horribly?
No chance. However all VPN add-ons are just some form of wrapper around the openvpn binary so you can always create a start/stop script and systemd .service file to start/stop the service.
There is some debate in the team on whether to spin an LE 10.2 release with Kodi 19 and bumped kernels; as as stop-gap until Kodi 20 moves closer towards release. On one hand there's no dispute something with newer kernels is needed. On the other it's a lot of work, and getting people to focus away from the LE 11 codebase won't get a full audience which always raises quality concerns. Kodi DevCon will be in ~3 weeks time so assuming Kodi 20 schedule gets discussed then (it's on the agenda) we'll make a decision after.
That thread reads pretty much as expected. There's a world of difference between "it compiled" and "it works reliably" and drivers for these random no-name chips are normally garbage.
The LE 9.2.8 img will not boot on the newest revisions of RPi4 boards as the boot firmware in the image is too old. We have no plans to release any updated LE 9.2 versions so the best thing to do is use LE 10.0.2 which should boot fine on all RPi4 hardware.
2GB is the minimum for normal LE use. The 4GB or 8GB boards are only really needed if you want to start fiddling with docker containers and other things that consume RAM in the background. You shouldn't need to fiddle with GPU memory defaults; they are set correctly by default.
Please run the test again using a current RPi4 nightly image. Also provide dmesg/journal logs so we can see what hardware it is (and which driver) and any system messages. Pastebin the log with "dmesg | paste" and share the URL.
I haven't pushed any changes that would/should improve or regress anything for Amlogic devices for a couple of weeks, so current nightly testing probably has more placebo than technical effect 
As long as you backup the eMMC using "dd" first it shouldn't be too hard to restore it again if things go wrong. GXL devices boot the same from eMMC and SD card so once you've erased eMMC it's simple to test u-boot(s) from SD and when you've proven it works, you can write the boot stuff to eMMC. In the event you do screw up and need to erase eMMC the worst-case scenario is shorting pins on the eMMC chip to stop it being checked during boot, and then the SOC finds u-boot on SD or USB again.
IIRC there are some capabilities that OSMC runs from the secure world (BL32) to prevent them being copied (Dolby Vision?) so any mainline u-boot will lose those (not that upstream supports DV anyway). I can ask Sam for the boot FIPs (minus the BL32 bits I'd expect) and then it's a straightforward process to create a complete image. It's not something I'd have interest in adding to LE as the "box" approach with vendor u-boot works fine, but the ability to TFTP boot can be useful for testing.
RPi4 has no real to-do items remaining unless you care about 3D support - it's my daily driver and very reliable. The only negative might be the lack of native VP9 support for 4K YouTube .. but 1080p streams run fine for me with software decode so it's not an issue for me. N2+ is less supported by LE images at the current time; Amlogic upstream code is a bit experimental in places and 10-bit VP9/HEVC cause issues. CE will be a better choice for an N2 than LE right now.
Support for V4L2 deinterlace methods needs to be proven over a wider range of SoC hardware before we send things upstream. The other patches already have PR's open on the Kodi git repo, but as everything involving colourspace has an unholy level of complication it will take time to get them merged.
I would have low interest in adding this to LE images as the driver is not in-kernel, but it appears to be supporting Android 11 so the driver can probably be compile on a modern kernel. Let us know if it works?
At this point in the Kodi 19 lifecycle the only add-ons that we see "many add-ons not working" reports around are pirate shitware. Feel free to educate us otherwise with a Kodi debug log for help to continue.
I am surprised that this requires optimization, since the LE9 code seems to be working great.
You appear to be missing the point that LE11 uses the upstream Linux kernel and an entirely new/different codebase. There is probably less than 1% code in common with the legacy kernel used in older LE images.
The HK forums have a lot of similar reports; though to play devils-advocate the inherent nature of support forums is you attract users with problems (we see the same here) so that's to be expected.
I have access to a German TVH installation for testing so if this is the original broadcast format it's probably not needed, but can you create a much larger sample; ~2 seconds is too short. NB: The "fix" will need someone to pick up a keyboard and do rework and optimisation on the HEVC codec. Right now it's in a state where I was able to dust off Maxime's known-unfinished code and get it compiled, but that's all. Sadly that's the limits of my coding abilities.
I have enable ssh and can connect with box but i cant find correct remote config files
Run "kodi-remote" to navigate in the GUI via SSH, and read https://wiki.libreelec.tv/configuration/…figuration-hard to create a remote config (despite the title it's not that hard).
You can have a look at the LE 9.2 images dtech is releasing or experiment with LE11 nightly images.
Ilvy99 the HEVC codec is not very optimised at the current time. It might help to enable adjust-refresh and set the whitelist to use 1080p @ 24/50/60Hz with 'doubled' modes working. The TV doesn't appear to have 23.976 or fractional rates like 29.97 or 59.94 but that shouldn't be an issue with PAL media; 25Hz should use 50Hz is doubling is on.
