Posts by chewitt

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.

Have you been reading the SD card in other machines? .. apart from a complete networking failure the only reason the SSH daemon will fail to start is a change to permissions on the server private key. I've occasionally seen people mounting the /storage partition in another OS to copy media to the card faster and an inadvertent perms change on /storage/.cache breaks stuff.

As I wrote in post #2 .. changes in Win10 mean Kodi needs to use an authenticated SMB connection to the Win10 shares. This means you need to set a user/pass (credential) on the Win10 share (as guest access no longer works after the update) and you need to (re)configure Kodi to access the 'source' (the Win10 share) using the same credential.

The last four major versions of Windows all require different solutions. Then throw macOS and occasionally Linux into the frame. Then sprinkle the three major evolutions of Samba that could be involved. Then mix it up whether LE is the server or the client. So there's 100+ possible combinations of problem and no simple way to provide an answer. Reporting users typically don't provide enough information while responding users chip in with the answer to their problem which may not be the same as the reported problem. Few staff deeply understand how the whole shizzle hangs together and they're not always on-point, and not always perfect either. Any threads started on this topic become definitively confusing rather quickly. Sorry that's not the answer you'd like, but that's the current reality. Hopefully in a couple of years MS stops reconfiguring Windows in each update and there's a more consistent position!

Learn how to use passwords on shares .. in Win10, LE, and Kodi.

Quote from AlexCalderon02

LibreELEC build's aren't official for the Rock, and the development ones are laggy, buggy, and unstable.

At the point where the lead developers for RK hardware think it's ready we'll release something. Until then you're running a known-to-be unfinished work. We expect the codebase to have bugs. You should expect them too.

Win10 has probably applied updates during the reboot that change it's SMB configuration. It now requires an authenticated connection to shares so you need to edit sources (in Kodi and on Win10) and set credentials. Win10 will also expect an authenticated connection when it connects to the LE samba server; if you have enabled the user/pass function the default is libreelec/libreelec.