As it seems, it still has the same issue with wifi that le 11 had, because iwd and connman could not work well together
If this is about your ageing Amlogic box? the primary issue is the unmaintained Realtek vendor drivers it requires that are not fully conformant to modern kernel wireless frameworks, so no point/need to start threads on them. If you're lucky I might be able to persuade the person working on upstream support for RTL8192DU to look at RTL8189ES/FS in the mid-term future.
LibreComputer's owner said "Green, not tint, is usually HDCP or HPD issues with the TV. What make and model?"
Unfortunately, the range of devices supported by the Skip 1s is a big lack luster.
You know it's a programmable universal remote, right? 
should I change the docker volume setup
Yes.
Does this mean the "whole system" is loaded to, and runs from RAM after boot?
If the device has 1GB+ RAM, yes.
OpenVPN is present in the OS and a new VPN connection can be created by calling it (at the right time in the boot sequence) with a command that specifies the relevant .conf file to use; and assuming that conf file correctly references the certs that are required (either external files or more likely they are embedded in the conf itself). The /storage/.config/system.d/wireguard.conf.sample shows how to run a wireguard connect command at the right time in the boot sequence. All you need to do is rename and mod the file slightly to run an OpenVPN command instead. NB: The sooner you learn a little about how OpenVPN connections are started and stopped, the sooner you stop needing GUI add-ons that are rarely available/updated and only complicate a simple process.
what does SDC, Balena, Rufus, etc. have that dd lacks?
a GUI for command-line-phobic users, which is probably 80%+ of our userbase
Better to ask in the Kodi forums where people who support Kodi on Android hang out.
I guess it would help to understand what version of RasPlex is being used?
Kwiboo ^
Current images support HDMI output. If anything else works it's a bonus. It is what it is..
It automounts to "ugly" name folders i can live with that but would prefere to be able to change it.
Create disk labels and /var/media/MYLABEL will be used instead of /var/media/0023-554320 or whatever UUID is used.
Not really sure what the second Q is about. You should be able to create sources named however you like against locally mounted (nicely labeled) drive mount points.
In short, there is no "restricted/secure" GUI mode in Kodi suited for Kiosk use. If I needed to do this for myself I would probably look into tweaking the skin so accessing problem navigation/settings options requires the skin to be in expert mode; then ship the skin in basic mode and have a systemd service that runs on startup (before Kodi.target) to sed the guisettings.xml file to forcibly reset the skin mode back to basic (or if there are multiple settings to reset, a bash script that handles them all). Then in theory "turning it off and on again" will restore the system to a known state. Taking that contept to a more extreme level you could have systemd run a script that erases /storage/.kodi and restores a pre-configured environment from a .tar flie on each boot. I'd invest more time and effort in ensuring the system powers up in a known state than in trying to prevent fiddling in the first place.
For clarity: there is no browser in LE for RPi hardware, only x86_64 devices. If that's important to you, better to use RPiOS.
Not something I've seen/heard of before. Put Kodi in debug mode, reboot, repeat the issue then run "pastekodi" and share the URL.
Use Etcher or Win32DiskImager then. Anything that writes a file to a USB stick will work.
I can see the first is H264/10-bit which isn't a real-world broadcast standard and thus is often under-supported in software.
Share samples of the files and we can ask Pi devs to comment.
I tried to boot the 11.95.1 test image (which isn't public yet) on an old Xtreamer Ultra2 board; this is ION (Atom + GT520M) and the first obvious problem was that it failed to boot into Kodi as the card IDs are selecting the latest nVidia driver instead of the ancients and no longer supported 340.108 one needed for the GT520.
An educated hunch confirmed that at an update last September where the python script we run to extract new card IDs from the latest driver also appended a load of legacy card IDs causing the wrong driver to be selected at runtime. The workaround for this is creating /storage/.config/udev.rules.d/96-nvidia.rules with the following to override the embedded one:
ACTION!="add|change", GOTO="end_video"
SUBSYSTEM=="pci", ATTR{class}=="0x030000", ATTR{vendor}=="0x10de", GOTO="subsystem_pci"
GOTO="end_video"
LABEL="subsystem_pci"
GOTO="configure_nvidia-legacy"
LABEL="configure_nvidia-legacy"
ENV{xorg_driver}="nvidia", TAG+="systemd", ENV{SYSTEMD_WANTS}+="[email protected]"
GOTO="end_video"Xorg (and thus Kodi) now started and after adding a NAS source and selecting the HDMI card output, I was able to play 1080p media with 2.0 audio output (2.0 is the max possible on the 10" test LCD that I used).
I've flagged the issue with card ID's to colleagues so it can be investigated and fixed, but I wasn't able to replicate no-audio. It does however prove that audio issues people might have are either device or perhaps card specific and not a general "ION audio is broken" problem which is how the current posts read.