Posts by chewitt

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?

You need to create two partitions ~ 512MB and 8GB are good sizes if media is stored somewhere else. Format both as ext4 and put the boot files (KERNEL and SYSTEM from an installer USB) in the first partition. Then configure your bootloader along the lines of the syslinux.conf file you'll find on the bootable USB. Do not install from the USB as this will nuke the contents of whatever device you point it to ~ it assumes LE is the only OS and it does not support installation to a blank partition like some general purpose distros do.

mount -o remount,rw /flash
cp /storage/yoursplash.png /flash/oemsplash.png
mount -o remount,ro /flash

I forget how to do the Kodi one, but ^ that does the LE boot splash.

I've updated the thread name so people are more likely to find it.

You need two partitions, one for the boot files and a second for the persistent /storage area.

distributions/LibreELEC/splash

Make a backup from the LE settings add-on inside Kodi then copy it off box for safe keeping ~ in most cases the backup file will be smaller (and thus quicker to create) than imaging the entire SD card. It also doesn't require any extra software and a future restore will be quicker too.

You'd need to go patching Kodi to add it into one of the on-screen displays. Adding GPU/CPU temp should be relatively simple as code exists for them in the system info screen that's part of Kodi settings, but HDD temp is not so you'd have to add more code for that. If you're competent at C++ go have a crack at it. If not, a cron job that exports values to a text file in /storage once per minute will be considerably easier.

The PR should be sent here: GitHub - raspberrypi/linux: Kernel source tree for Raspberry Pi Foundation-provided kernel builds. Issues unrelated to the linux kernel should be posted on the community forum at https://www.raspberrypi.org/forum then it benefits all RPi users, not just LE, and becomes something we pick up in the RPi backports patch we rebase as part of minor kernel bumps. The folks who maintain that repo will also evaluate and judge whether it's something that should go further upstream to the mainline kernel.

It's completely unclear what you're trying to do and which end (server, client, etc.) you're talking about.

If whatever change you're thinking up is worthwhile it should be submitted to the linux kernel. Then we'll pick up the change in a future kernel release. Patches and hacks are out of fashion around here