Posts by chewitt

What's the resolution of the display?

TVHeadend etc. can only save recordings to the local machine, so you need to mount a remove share from the NAS to a local folder. LibreELEC can auto-mount the share at startup using a systemd .mount file. SSH into the box and copy the example file in /storage/.config/systemd and edit (and then rename) to suit your share names etc. ~ it's not so hard.

Look in /storage/.config/systemd and there's an example .mount file to crib things from. Compared to setting-up TVHeaded it's not hard

You cannot install it, it would need to be compiled from source and packaged as an add-on. I'm sure that's possible as Oolite already runs on a broad range of Linux distros but it's a task that would need to be done by the community. It won't be on the roadmap for official development.

That trick no longer works (out of the box) for LibreELEC because we added a compatibility check to the update process that detects you are trying to update with an incompatible image and aborts the update. The check was added because we (used to) get a percentage of Generic (x86) users who cannot see the large Raspberry Pi logo on the default download page trying to update with the Pi (arm) image.

The trick can still be done, but you need to disable the compatibility check with "touch /storage/.update/.nocompat" first.

Using "make image" will result in .img.gz and .tar files in the target folder. All versions of LibreELEC support updating from either file.

You might see crashes building Python with only 4GB. I'd allocate 8GB of RAM for compiling.

I've published some instructions to the Download page: FiveNinja’s Slice – LibreELEC ~ I frequently forget to update those links when a new release is published too, but at least it looks more organised than a blank directory listing on my webspace.

It will say 8.0.2 so the only way to tell is update and either the LED's work or they don't. If they still don't work, wait another couple of hours before trying again. I've also removed the slice folder from my server because i'm fed up of being asked about the files there ~ not you specifically but just in general. For some reason Slice users appear to be thick at understanding THEY'RE THE SAME FILES AS THE MAIN RELEASES SERVER and I get a bit pissed off with being repeatedly asked about them in PM messages.

I've pushed updated files with the drivers included to the releases server so if people do a manual update in the GUI (or once the mirrors have synced the updated files, it will take a few hours) they should get the updated .tar file.

I can see the issue (audio and led drivers are not in the kernel) and I will build and push an updated 8.0.2 image sometime later today to fix it. I'll also see if I can beg a Slice-light kit from the folks at Pimoroni to replace the dead hardware I have.

Win10 doesn't support client connections to NT1/SMB1 servers since a security update in late 2016 and the version of Samba used in LE doesn't support SMB2/3 - hence it cannot browse/connect to our Samba server. This will/should be resolved in a future release that bumps the version of Samba to something that supports newer protocol versions.

NB: LE does not support (and never has supported) insecure FTP connections. You can use SFTP (FTP over SSH).

If the add-on is not working on multiple platforms it should be reported to the developer via the add-on support thread in Kodi forums. We take a major interest in things like TVHeadend as it's so widely used, but for clients like NextPVR we just build whatever Kodi provide. If what they provide doesn't work it needs upstream attention.

If using WLAN the issue is slow loading network drivers and the network not being up when Kodi starts and the initial check for updated add-ons is made. It will fix itself given enough time. Or you can context-click on the repo and "check for udpates" to force a refresh. If you add a small boot delay using the "wait for network" function in LE settings that should prevent it from happening in the future.

The installer (blue background, grey boxes, etc.) runs on the framebuffer driver. Kodi itself runs in Xorg which needs proper GPU drivers. It's entirely possible to see the installer and not see Kodi. In theory there is no difference between Kodi in Xorg in Live mode and normal mode.

It's an S905X device so "probably" is the answer. I moved the thread to the Amlogic section of the forum.

Database files should migrate up okay. Add-ons are normally the source of problems. Take a back-up and move it off box, then do a clean install of LE 8.0.2 then selectively copy back the databases, thumbnail files and sources.xml and any customised remote xml files. Then add current versions of any add-ons. It looks like it takes longer but in reality it's quicker to do it that way than "just upgrade" and having to find/fix broken things.

Clean install also avoids small boot partition size issues which might be a problem if it's a really old OE install. If it's an XBMC > KODI migration you also need to be aware that XBMC stored userdata in /storage/.xbmc and KODI expects things to be in /storage/.kodi

YOUR CAPS LOCK KEY IS STUCK

Wizard status is saved in /storage/.kodi/userdata/addon_data/service.libreelec.settings/oe_settings.xml .. but add-ons run within Kodi, so to delete everything (assuming just the Kodi data) you need to stop Kodi first before deleting everything except that file and restart Kodi. However, stopping Kodi will also kill the script/process of the add-on too so the process fails. TL/DR; it cannot be done from an add-on. It needs a companion script in the embedded part of the OS to detect a marker file that performs the actions at startup (before Kodi starts). For the sake of eliminating 4-5 remote button clicks it's not worth the effort. Why do you even need to reset Kodi in the first place?