Posts by chewitt

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

Quote from Soringo

After trying Tranmissions (it works funny sometimes, changing the download directories and has few settings), rtorrent+rutorrent (some rutorrent addon destroyed all my seeding torrents, plus rutorrent is not working in LibreELEC so it seems it has no maintenance); I tried Deluge and I loved it.

Can it be installed on LibreELEC as it can be, for example, on Raspbian?

It's not possible to install it directly (as above) and we have no plans to add torrent client apps to our add-on repo (we're a media distro and these apps are used to steal media) but if you're using Generic/RPi/imx6 we support docker and someone has probably created a docker container for the app.

The better way to do it is a systemd .mount file in /storage/.config/system.d (look at the sample) but the same autostart.sh method will continue to work without issues.

run "dmesg | paste" and share the URL

master according to the build dirs (wrong kernel for 7.0) but make sure it's a full clean build and clear ccache

Are you turning on the TV before the HTPC?

Kodi has no Linux support for Rockchip so LE is not available. There was an OE fork with tentative support at some point but it was a one-man effort that died when Kodi refused the patches for code quality reasons.

I'd ask you report the problem to OpenELEC's developer then; his codebase is no longer our problem

Amlogic support in Kodi is/was massively impacted by the VideoPlayer changes in Krypton and it's not far off a ground-up rewrite. It is improving but still quite a bit of effort to be made. It is likely that Generic/Pi devices enter LE beta and maybe even release while Amlogic things continue in Alpha for a while longer and follow their own sub-schedule. The good thing is we have a bunch of people starting to collaborate on Amlogic support instead of the historic situation where WeTek devs do 95% of the effort and others do the remaining 3-4% in isolation from each other. It's all a bit entangled and progress is slow, but we're making progress

LE team are familiar with Lakka and it's main developer is part of our extended collaboration team. Lakka is originally derived from OpenELEC but has emphasis on support for older hardware (e.g. 32-bit x86). The GPU/graphics needs for retroplayer are much lower than Kodi which allows Lakka to run on a wider range of low-cost maker-board devices.

Could be crap firmware in the USB>SATA bridge used by the drive. Could be unclean mounting from Windows. Have a look at "dmesg" output for error messages. If nothing obvious run "dmesg | paste" and share the URL generated.

I had to close and clean up the PR's (one is enough, no need for three) but support has been merged and will be in v7.90.005

Have a look at the example service file in /storage/.config/system.d/ for a persistent and reliable method of locally mounting remote volumes so they are accessible from the filesystem. If you need written instructions look at Mounting network shares - OpenELEC