Posts by chewitt

The community build is from escalade; best to post in his support thread to see if there's a driver bump available.

mount -o remount,rw /flash
touch /flash/oemsplash.png
mount -o remount,ro /flash
reboot

I'm not entirely sure whether a zero bytes png causes any graphical issues at boot, but I suspect it just results on no LE boot logo. Worst case you can create a proper all-black png image and deploy that. It will still be squashed up, but you won't see it.

systemctl stop kodi.service
rm /storage/.kodi/userdata/guisettings.xml
systemctl start kodi.service

SSH in and run the above commands. It will drop Kodi back to defaults (skin, language, etc.) and that normally clears things back to a point where Kodi will start, download a load of updated add-ons, which normally resolves the issue with something being out of date and causing Kodi to crash.

There are no tutorials that I know of for dual-boot with Lakka, but create 2x 1GB partitions for boot, and then split the remaining space roughly 50/50 for the two OS to share. Install GRUB and then configure it with appropriate boot= and disk= configurations. Then copy over the respective KERNEL and SYSTEM files and you should be in business.

Sure, create 4x partitions on the drive (boot/storage for 2x OS) and install GRUB as the bootloader (easier for dual-boot than syslinux).

The "cputemp" and "gputemp" scripts present the values shown in the GUI so just run those commands from the console.

All you have to do is enable the "tethered hotspot" feature in LE settings add-on. No need for hostapd to be present. The native feature requires wireless drivers that support AP modes (most, but not all, do) and it is very simple, not a substitute for spending on a proper router.

@Monica (and other shill accounts for Khadas VIM). If you wanted to build a positive reputation for your products and brand with our project all you had to do was participate openly and honestly with our community of users. Instead you see us as a marketing opportunity and have registered multiple forum accounts to post URL links that promote your product and boost Google page rank scores. This is not welcome, and as you have ignored previous warnings your account is now banned from the forum.

@Monica We have no problem with commercial parties providing assistance and support to their users who posting queries/issues in our forum. We have a big problem if you persist in posting "advertorial" content full of links to reviews of your products etc. to boost your Google page ranking. We are not a marketing opportunity and I have binned other threads with unacceptable content - and posts above are edited. Final warning. Thanks.

Quote from douglas

Has anyone tried these builds yet with the Xiaomi Mi Box yet? It looks to me like the perfect S905X box, available in the US, well supported, 4k and HDR... etc.

AFAIK nobody on staff has one (or at best maybe one person has) and I doubt Xiaomi can spell Linux. You might want to adjust your definition of well supported.

Retest using MMAL only pls.

Are you using OMXplayer or MMAL on the RPi?

No logs .. no problem.

MikeBuzz, how?

Same URL .. change Slice3 to Slice.

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.

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.