Posts by chewitt

    Current "normal" versions of Ubuntu/Fedora/CentOS are used by various team members so the workaround is to use a proper Linux distro and not the frankenversion that's running under Win10. You're probably the first person who's attempted this, and I doubt any of the devs are interested to spend time adding support when easy alternatives that require zero/little effort exist.

    Yes, and No :)

    We are working on overall support for Amlogic devices. There are at least 4-5 different kernels in use among different community builders and a dogs breakfast of Kodi patches that are poorly attributed and frequently hacked in device specific (not always reusable) ways. To make progress we need to get people working around a common kernel and patch set. It would be nice to have a Generic S905 build, and we are planning to move @kszaq's work to our main repo alongside the WeTek Hub (S905-H rev.c) and Odroid C2 (S905) to encourage community contribution, but the hardware reality of the general S905 (and now S905X + S912) landscape is not simple and little differences that are not significant to individual S905 devices are collectively very complex to handle in a single codebase. It may be the case that we act as a central focal point for development, but leave releases to community builders who work as part of our extended team and support the specific devices they have a personal interest in. So, there are plans, but not crystal clear plans, and with Kodi team starting to wrap-up Krypton development there is still a lot of do on the Amlogic side of the house; to the point where it's possible LE v8.0 might release with full support for Generic x86 and Raspberry Pi hardware, and "beta" support for Amlogic things.

    Pi devices are amazing for what they are, but they are also a $30 hobby board with limited CPU. Some visualisations are OpenGL and will be handled nicely through GPU decoding. Others require CPU and will be challenging on low-spec hardware. Most Kodi devs use mid-range x86 hardware with a lot more CPU power for development so it's not too surprising that some Kodi eye-candy puts a Pi board beyond its limits - it was never the design target. The easy option for a small speed bump is moving from RPi2 to RPi3 but that may not be enough and the real step-up requries to you move beyond Pi to something more capable. You don't always need to look at the latest/greatest (most expensive) kit; it depends on your media playback needs. I'm still using an older Atom/nVidia box as my main player device. It's nearing 5-years old and is up for replacement as it can't handle newer HEVC/1080p/4k content that I need to test with now, but it still has 3.5x the CPU grunt of an RPi3 and plays H.264 content perfectly.

    Which specific visualisations are you trying to use?

    My guess is the .nfo files contain URLs for a site that you don't have a scraper installed for so nothing is retrieved for that site, and sites with no .nfo file use the default multi-scraper which finds something (working as normal). So check the .nfo URL's in files, then check you installed the scaper for that site from the Kodi repo and configured the source to use it - the default source/scraper config in Krypton is slightly different than older Kodi versions.

    a) The OP used our USB-SD Creator app which creatse a USB directly from the img.gz file - so there's absolutely no need for unzipping to get images and using Win32DiskImager or other tools.

    b) You only wipe the HDD if you select the HDD as the install target. If you insert a formatted USB it can be selected and you preserve existing HDD content - which is what the OP was attempting.

    OE can be updated by dropping LibreELEC-Generic.x86_64-7.0.2.tar into the /storage/.update folder, see:

    External Content www.youtube.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

    Good luck remaining with OE .. you'll need it.