Posts by chewitt

    We compiled it, and for playback everything works very nice after recent changes, but if you scroll about in a Library view (as users do) it eventually goes OOM and a power pull is needed to restart the box. Rinse/repeat until something corrupts and you need to reinstall. That's not acceptable in our definition of beta so we chose not to release it.

    If you want to self-build just clone or checkout the libreelec-8.0 branch and crack on.

    The add-on you've installed from it (ITV) is harmless, but you can get/install the add-on from one of their mirrors without installing the repo.

    Fiddling with cache settings is almost always bad and unnecessary. Unless your network or NAS/server are rubbish (in which case; fix the media source before blaming the playback device) there is no need to change something.

    If you want to cheat installation and the SD card is a decent size you can just stop kodi and rename .kodi to .kodi-old and restart. I'm mostly interested in a clean system because a known state eliminates variables, and because anything we showcase upstream to Kodi or PVR add-on developers will only start with them asking for the same thing.

    Code
    03:07:05.177 T:1962473392   DEBUG: ADDON: cpluff: 'Plug-in $uperrepo.kodi.isengard.all has been installed.'

    I had a brief look at the logs but won't look further because your install looks very messy. There are remnants of an older OE install present. There are some unusual (and I suspect detrimental) changes to advancedsettings.xml. There is also a pirate add-on repo installed ^^ which breaches this forum's conditions for providing support.

    Take a backup so you can selectively restore anything of particular importance (DB files etc.) at a later date, then do a clean installation using 7.95.1, and then if there is still a problem with DVBLink, post some clean debug log files.

    If you follow instructions on the Raspberry Pi Foundation website to mount the CM3's eMMC device to Windows our USB-SD creator app can be used to write the "Slice (CM3)" image directly to the eMMC volume. I've no idea how eMMC mounting is done via Mac or Linux, but assuming there is a process the native USB-SD creator apps for Mac/Linux should work fine too. Then just boot the Slice and it will format/prep things as required - it's exactly the same installer routine as an RPi3 for those that have done it. From chat with Gordon some other funky things like booting Slice (CM3) directly from the internal HDD should be possible, as it's connected via USB so Slice (CM3) has the same "can boot from USB" capabilities as RPi3, but until I have some time to fiddle around and experiment there are no written instructions with pretty screenshots.


    Wtf?! Those two repositories have normal legal addons,
    I am not talking about warez stuff or something like that.
    I would understand that.

    I guess all the studio's and TV networks give all their content away $FREE to anyone with a "fully loaded" Kodi box just because they are nice lovely people .. goodness of their own hearts etc. ~ or perhaps there is another explanation behind all the pirate streaming crapware in those repo's. Yes there are few legitimate things, but they are few, and you can always install the zip for a legitmate add-on without adding the entire banned repo and all its security risks to your LE install.

    It's a long-standing position in our and Kodi forums, and there are no exceptions granted.

    WeTek have been seeing an increase in support work caused by users who don't install the NAND image correctly, or who install 3rd party images for similar spec Amlogic devices that are not appropriate. It is not impossible though quite hard to truly brick a device, but it is relatively simple to create something that an average user can't resolve themselves; requiring extensive handholding or even RMA.

    Facts are: WeTek supports LE when installed to a micro-SD card using the dual-boot capability in their firmware and they do not officially support the NAND install. As this is becoming a greater issue we are currently discussing with them how to message and address this with users.

    Basically.. no idea. Once 7.95.1 beta is available I'm interested in results using that build because a) there are numerous network package bumps present that could potentially change things, and b) we stopped developing on 7.0 some time ago.