Hi Guys.. Was mentioned there was a sky go addon someone had working? Is this a UK version as assume the german one is only for those with German sky? If so where do I find it.
SkyGo is for German users only. There is currently no equivalent for UK users.
There are balbes150 test images available in this forum if you want to have a play with 5.0 kernel images. For 1080p/8-bit/2.0 video things are super stable but 4k/10-bit and multi-channel audio development is still work in progress.
To manually install LE .. create two EXT4 partitions on a disk; 1GB for "BOOT" and remaining space for "STORAGE" then install any bootloader that works on that hardware and configure it for boot=LABEL=BOOT and disk=LABEL=STORAGE .. and ensure KERNEL/SYSTEM live in the boot partition (and mark it active). That's all our installer does. We use syslinux but GRUB and others are fine. We don't touch boot ever after install.
NB: Team Kodi gave up on maintaining an entire distro (Kodibuntu) but the stable/unstable PPA's are still maintained for use with current Ubuntu.
LE requires two partitions and (once you create the installer USB using our USB/SD Creator app) the install process is designed for single-use HTPC devices and it does not support dual/multi boot arrangements. In other words, if you keep pressing "okay" to get past the multiple "this will erase the contents of your disk" warning messages; it will nuke your Windows install. We have no desire to support dual-boot or single partition installs.
Current version in the LE 9.0 repo is 2.3.15.0 and we maintain a single repo (it's not mirrored like the Kodi repo) so there's no other source.
I'm unable to reproduce on Fusion 11.0.2, the 9.0.1 ova just works as normal/expected.
rm /storage/.kodi/userdata/profiles.xml && systemctl restart kodi^ that should work. I've seen the same issue but it's unclear what causes it.
Panfrost is making serious progress. It now passes almost 100% of GLES 2.0 tests and Rob Herring + Tomeu Viscuso are making good headway on a proper kernel driver (Rob brings the kernel DRM/DRI knowledge lacking among the core panfrost developers). If the current pace of change continues I'm expecting to switch from the ARM kbase driver to a native one in the next month.
If you have fixes for anything please upstream them to the kernel, or at least as far as @Kwiboo's repo where things can be validated and aggregated with other changes we accumulate and prove over time.
Kodi forums would be the best place to ask for skin development advice; it's where all the skin designers hang out.
As long as the wireless chips use the standard (correct) device ID's it shouldn't be an issue as the mainline kernel has reasonably intelligent sourcing of the firmware and nvram files (detecting the ID's and using a lookup table). Current VIM1 does not use the correct ID so once we start condensing images we'll need to hack a solution together (and it being hacky, it probably won't be upstreamable) .. but I have some ideas.
I'm not aware of any skins supporting custom_ prefixes, but then I don't follow skin development so it might be possible. However, you need to clone and then rename the skin, e.g. create mimic-mod, else any updates to mimic will overwrite your changes. Since you now have a custom skin, it would be easier to edit the normal .xml file. You will need to reload the skin (via kodi-send commands) or restart Kodi to see any changes.
Anything involving Ace streams is piracy and falls on the wrong side of forum rules.
I'm also out of town .. the longer log (via the settings addon so it also contains systemd journal) after 10 mins would be useful. I don't see these issues with my 918+ so there's no known issue with Synology kit.
If should be possible to create an LE 9.0 image but in addition to changing the legacy driver to the last 304.xx version you'll also need to change to an older Xorg and maybe mesa packge else the driver doesn't support the minimum ABI version required. IMHO it would be easier to start from 9.0 and revert a small number of things to support the older driver, than start from 8.2 and figure out the larger number of things needed to sustain newer Kodi.
I'm not sure where "script.libreelec.devupdater" came from, but it's not our code, so not our responsibility to fix. Please nag the creator 
If you image a working SD card you are creating a file that matches the 16GB? of the card, even if the card only has 1GB of actual data on it. It would be faster to create a backup (in LE settings) that you restore after installing the default LE image, as this will only be the actual data. The difference in time is simply the difference in how long it takes to write 1GB vs 16GB (or whatever capacity the SD card is).