Posts by chewitt

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?

Have you installed the IMDB scraper add-on and configured Kodi to exclusively use that scraper?

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:

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

Quote from thosti

Wow, is available now. Well don job to OE Team!

Freudian slip? .. I suppose "former OE Team" sort-of applies to most of us, but we prefer LE

To change the Intel driver you only need to change the githash in packages/x11/driver/xf86-video-intel/package.mk and it will download/use the driver at the appropriate commit; although Intel's development repo is further upstream than the freedesktop.org one we use. You should be able to change the repo URL used to point it at another one. The same general process can be applied to most other packages. The build system is fairly simple (e.g. logical) once you figure out the general build workflow.

NB: Some of the devs (and/or people with solid building experience) hang out in the #libreelec IRC channel on freenode. It'd be easier to chat there than give major instruction via forum posts.

Our daily increase in active-install figures prove the Generic image is good and it makes no difference whether the USB is created on macOS or Windows as you're writing the same image to the USB stick. However, older NUCs can be finicky with USB booting (avoid using USB 3.0 ports) so you may need to fiddle with boot options in the BIOS and/or maybe update the BIOS to resolve Intel firmware bugs first. People definitely do use NUC's; they're a popular platform among our users.

Aeon Nox is available from the official Kodi repo, so there's no need for custom repo locations unless you want to be on the bleeding edge of untested Kodi development (in which case black screens and bugs are self-inflcited and not our concern). Go add it from the official source.

Our website needs updating to remove references to gaming in Krypton as development has been slow and the feature(s) needed didn't make the cut for Kodi v17 .. they will carry forwards and hopefully/maybe arrive in v18. That said, there are some community created builds that bundle retroplayer or retroarch components in to make setup of things easier - have a look for @escalade's "enhanced" builds and read his release thread for instructions on where to obtain other bits. NB: If you're using RPi3 you could also swap SD cards and use Lakka directly. LE v8.0 is a way off yet

Ubuntu will be more flexible for installing random apps, but flexibility also brings complexity for you to manage. LibreELEC is less flexible (a limited range of apps available from our add-on repo) but hard to break (most of the filesystem is read-only) and easier to update. If you don't have much experience with Linux, LibreELEC should be easier for you. Kodi should be functionally the same in either distro.

NB: You can install LE to a USB key (boot from the installer USB, install to a second USB) for testing.

This is normal. If you migrate from OE your existing config.txt is not touched to ensure any customisations you made (e.g. overlays) are retained. If you clean install LE the config.txt file will only have references to LE.

I didn't look at the logs, but Kodi folks have been playing about with inputstream API things (or forgetting them) and that's probably the cause. Now that Kodi moved to beta the PVR/DVB front-end apps should start to stabilise. Please check again with v7.90.005 when it's released (it's work in progress) as most Kodi sourced add-ons will be bumped to match at the same time.

Skins are installed from the Kodi repo, so the Studio Icons aspect is not a LibreELEC specific issue. The profiles issue should be tested on a current alpha build and if the same issue exists in Krypton it can be reported to Kodi devs via the Kodi forums. You can report it for Jarvis too, but since all Kodi activity moved to Krypton months ago nothing will happen.

There is no official LE 7.1 build for the C2 so you'd need to ask that question to whoever is taking liberties with our version numbers and creating that community build.

tester100: Let us know when you finish reverse engineering the pre-compiled Android binary code and have something to share that we can compile to use in LE. Thx

There's a couple of extended-staff with WP boxes who have tried (and failed) to replicate the issue; they are able to install things okay .. so honestly I have no idea what the problem is