Posts by chewitt

The act of asking for public help usually allows people to instantly spot the obvious mistake made or it provides a sudden burst of inspiration to solve something

Thanks for sharing the solution.

GitHub has the advantage of allowing others to compare your fork against our main branch (or others) but any public repo is fine and we're not out to dictate anyone's workflow.

sertem только английски язык пожалуйста

Kodi needed to reduce the size of their install binary due to Android store limits so between v15 and v16 they shed bloat by moving lots of tertiary functions into installable addon modules; LCD support is one of them. This means in addition to installing LCD support to the OS (via our addon) you also need to install LCD support to Kodi (via their addon). I'll admit it's not the most obvious thing..

You can only set a single map in dts but look at the multimap config that's done in the v4l-utils package.mk

Android has native voice search API's that allow third-party apps like Kodi to hook into the underlying OS support. There's no equivalent for Linux so voice search will not work in LibreELEC (or any other distro).

Lakka devs already have a bootable XU3 image that should be more or less copy/pasteable into our buildsystem to provide core board support. However Retroplayer != Kodi. If the device has DRM (direct rendering manager) support in the kernel (ideally mainline, worse some odroid specific kernel) it should be fairly simple to get the Kodi (Leia) GUI running as the DRM framework in Kodi is now quite mature and has been tested on a wide range of devices. However GUI != awesome performance and hardware decode will require an Exynos V4L2 driver. If that also exists things become theoretically possible but you'll hit some challenges with V4L2 support being on the bleeding edge of current kernel and Kodi development and some of the 'standards' are still in development and a little fluid right now. The main API that things need to coagulate around is targeted for the 4.19 kernel which is late summer, although things are now close enough to end spec that developers have something to pursue that won't need major rework when things are finalised.

While that's generally positive, the normal challenge with older boards (even great ones) is that by the time all the standards settle down a new one appears (with different chips) and then the number of technically capable people interested on adding support for the old model drops off because they all have new shiny playthings to poke.

LE has installed syslinux bootloader and created two ext4 partitions in a GPT scheme; first is 512MB and the second fills the remaining available space on the drive. The good news is that LE is small and so regardless of where the new partition boundaries have been drawn on the drive we've only overwritten ~235MB of the first (boot) partition space and no more than 20MB on the second (storage) space if it's just a clean LE/Kodi install. The overwritten data is probably only Windows OS files so someone who knows how to perform data recovery should be able to find and retrieve a large amount.

** If you don't fully know what you're doing and the data is valuable, stop immediately and seek professional help **

tomtomclub You have banned (piracy) add-ons installed so there will be no further support in this forum until we see debug logs from a clean device.

Please provide a Kodi debug log.

Yes (and no). The hardware is capable but Intel Linux driver support for HDR is still on the learner slopes of the support curve.

If you're using the TV remote and it "just worked" you're using CEC to control the pi. Reconnect the Pi directly to the TV (remove the HDMI switch) and test again. If it all works, your HDMI switch disrupts CEC and we have a starting point to investigate from.

You could create /storage/.config/autostart.sh and add something like:

(

sleep 10

systemctl restart <name of service>

)&

The trick will be figuring out what service needs to be restarted.

I'm sure that's the wrong solution though. What IR hardware is being used?

is this on RPi hardware (or something else with no RTC chip) ?

Try doing this: Custom EDID [LibreELEC.wiki]

It sounds like a bug in either the Android app or the Kodi XML-RPC api that mobile apps use to control Kodi. The only thing you can do it update to newer releases - all development on LE7/Kodi16 stopped ~2 years ago.

I've used 'dar' for mail server backups in the past as it has a useful combination of tar and rsync features, but it can be complex and it's probably easier to work with rsync which is already included in the OS.

NB: It would be nice to have a decent wiki page with some sample scripts that hook into cron for scheduling to describe this stuff. The step beyond that is expanding features in the settings add-on, although we're more likely to rewrite the add-on (to make it easier to maintain and expand) before that happens.

Just a hunch .. change the partition labels on the SD card so they are not LIBREELEC/STORAGE.