rm -rf /storage/.kodi/addons/inputstream.*
rm -rf /storage/.kodi/addons/packages/inputstream.*
rm -rf /storage/.kodi/cdmM-Reimer Those commands ^ should remove all traces of inputstream and related widevine files. You should be able to reinstall inputstream add-ons from the LE repo and then let the widevine files be downloaded/unpacked again.
Also note that we have a virtual image (OVA) that runs in vmware Workstation/Fusion or Oracle VirtualBox; which can make running LE on something fast(er) and more local/portable easier than using a real board/box device.
There must be a better way.
Clone the skin files to /storage/.kodi/addons/skin.myskin and edit the addon.xml to define a new/different skin name so there is no name clash. Restart Kodi for it to see the 'new' skin as something installed but disabled. Enable the skin. You can now edit the files in-situ using nano. You can reload the skin using a keyboard command (if one is attached) or use a kodi-send command to reload if editing 'remotely' over SSH (can't remember the command, Google will find it for you).
systemctl stop/disable/mask the pulseaudio service
On what LE version? - Logs? - Sample file?
It seems like that the Host i.e Host = 185.210.30.121 in the example tutoral, cannot be a DDNS name. How come?
You're configurating a network interface not an application. NICs route traffic based on IP data and you're basically defining a static IP route to the other end of the tunnel. If you want to handle DDNS hostnames you need something at application level to resolve the hostname to an IP and update the WireGuard config. ConnMan watches the config files; I'm not sure if it can adjust the tunnel routing while the connection is active or it needs to stop/restart the connection first (should be simple to test though).
Fliesystems going read-only is normally an indication of the SD card going bad. Please share the full boot log.
VNC works well on LibreElec
I'll disagree with the statement. There is no current VNC support (or support coming) for devices that use GBM graphics; which is basically everything these days except for the Generic Legacy (X11) image or very old (LE9.x) images.
If swapping newer KERNEL/SYSTEM to older SD card works the issue is related to u-boot which is installed to the SD card, and the card has an old version; a newly created card has a newer (non-working) version.
jernej ?
karotrape Can you please test https://chewitt.libreelec.tv/testing/LibreE…droid-c2.img.gz to see if the DAC works now? - I've partially reverted a change related to USB init on the C2 that might responsible.
How about bwm-ng?
Also in the same tools package.
I'd be surprised if it was a power issue as USB DACs don't normally draw much current and it worked on older LE releases. If you see the LE splash on-screen with cold boot the issue is something in the kernel (as we booted that far). If you're not seeing the LE splash on screen during cold boot (or nothing on screen, HDMI should work) the problem involves u-boot and that's going to need UART output to see what's happening.
For the sake of asking, what DAC are you using?
krisrok also update to the LE12 beta: newer everything might fix the issue, and if not, then you're on the release that will can receive fixes as there will be no more LE11 releases.
it uses Realtek 8812au chipset and LibreELEC doesn't support drivers for this
Explain this then: https://github.com/LibreELEC/Libr…12AU/package.mk
Run "pastekodi" then "lsusb -tv | paste" with the T4U attachd and share the URL's generated. If the driver isn't probing/loading the USB device ID's are probably missing or there's some other explanation.
Sep 12 19:04:40 LibreELEC systemd[1]: Configuration file /storage/.config/system.d/storage-timecapsule.mount is marked executable. Please remove executable permission bits. Proceeding anyway.^ "chmod -x /storage/.config/system.d/storage-timecapsule.mount" .. but that's not the issue stopping mount.
At this point I'm unsure what the issue is 
What happens if Tvheadend is restarted after the third tuner is connected?
Share Tvheadend logs!
https://wiki.libreelec.tv/development/build-basics
^ Start with creating a current LE12 (master) image that boots the device. Once you have a working image, adding a patch to change kernel behaviour and rebuilding to include the change is simple. NB: figuring out what to change will be the challenge. I can't offer any advise on that, but maybe others can.
That's correct.