The main Kodi DVB maintainer asks that you update to a Leia build and retest before filing trac tickets against Krypton for two reasons:
a) Krypton is a dead codebase so nothing will ever be fixed there
b) There are lots of DVB issue fixes in Leia so there's a good chance it's already been addressed
We used the latest patchset from the Pi Foundation folks at the time the release was assembled. It's unlikely there will be further 8.2 releases so the next round of Slice updates will come with Leia. I'm not aware of anything specific for 10-bit support, but then I'm not the person on staff who deals with most of the Pi related things.
Clone skin files from /usr/share/kodi/addons to /storage/.kodi/addons/ then change the name of the skin (folder and in addons.xml) then restart and select your newly named skin. The files are now editable.
No idea how you add another menu item .. the default ones are generated from core code.
The LE column looks about right. I can't speak for anything else. You should also consider the underlying OS software. Is the box running on a current or recent kernel or some hacked up turd that's 5+ years old. When you factor that criteria in .. they all fail (and they should fail).
Publishing via Zeroconf is a Kodi thing that depends on the OS level Avahi service running which is enabled/disabled from LE settings. Check that it has not been disabled there first. Plan B .. backup and clean install then selectively restore things from the backup. If you do a normal restore you will just restore whatever cruft/issue is causing the problem too.
Drivers must be baked into the LE image for things to work - no addons are required. We support most (but not all) of the common USB wireless crap out there. As most cheap devices do not make it clear what chipset is inside, it's a bit of a dice roll when purchasing.
No, and this will not change for some time as the V4L2 graphics driver it will use (and support for that driver in ffmpeg/Kodi) is still being coded.
It might test your patience and sanity with bugs, but it will not "damage" the box. IMHO things are not ready for broad public testing yet.
mount -t cifs //192.168.31.1/Data /storage/networktest/ -o vers=1.0,guestIn LE 8.2 the default connection will be SMB2 and most routers appear to be crap and only supporting SMB1, so try adding vers=1.0 to the options. If that still doesn't work also add sec=ntlm so it's not trying to use NTLMv2.
File is updated again - this time with the three files you shared. The two txt files appear to be the same file at different versions (similar but not the same content. Both appear to have references to hardcoded MAC addresses so there is no way we'd embed them as-is into our normal image. It looks like something that should be supported properly within the kernel and not done via copy/pasting.
Use the backup function in the LE settings add-on, it exists for a several good reasons:
a) backup up the contents of the /storage partition is always faster than making an image of the entire partition
b) restoring the contents is always faster too
c) no partition size shenanigans to deal with
There is a time/place in the LE ecosystem for cloning tools. Backup is never it.
It's not about us adding support for something. It's about Intel writing reliable drivers. Once they fix their crap (don't hold your breath) our distro will magically work "out of the box" without users needing to hack stuff. We stopped adding the hacks ourselves because what works for one flavour of NUC (which supports 4k when connected to a 4k screen) creates false modes in Kodi for someone who doesn't have 4k hardware.
Either change the partition labels so the two (or four, or any other multiple of two) sets of partitions are labelled distinctly, or switch to using UUID. It will not work in an OOB config as it is using labels and you have duplicate labels (something will boot, but, roll dice to guess what).
There will probably be an update file by the time LE 9.0 exists. Anything you find in the forums today claiming to be 9.0 is a little premature.
I've never actually done it, but reading instructions from the Pi Foundation site something like this should work:
Use our USB/SD creator app to create a bootable SD card with the RPi2 image, then append "program_usb_boot_mode=1" to config.txt and boot the Pi to configure USB boot. SSH in and run "vcgencmd otp_dump | grep 17:" and you should see "17:3020000a" afterwards. If you don't, the Pi will not USB boot. Now use the USB/SD creator app to create a USB using the same RPi2 image. You will need to edit boot=/dev/sda1 and disk=/dev/sda2 in cmdline.txt on the USB stick as the default image is hard-coded for /dev/mmcblk0 devices (SD card) and will fail to boot.
In future LE 9.0 we dropped the hard-coded reference to SD cards (we use boot=UUID= and disk=UUID= format) which will make this easier.
People that develop Tvheadend have advised that they do not support migration. I trust they know what they are talking about.
You have to create autostart.sh, it does not exist by default.