Posts by chewitt

I've updated the 4K/HDR page in the wiki with some more specific comments on 4K60 (based on noggin posts)

https://wiki.libreelec.tv/configuration/4k-hdr#id-4k-60hz

It sounds like a bug of some kind .. but it's not a LibreELEC bug, so best to post it in Kodi forums for their devs to triage.

Do what it says then..

Yes, but read the latest LE11 release notes to understand the current state of Amlogic support.

Connect a USB keyboard?

The wireguard.service example has:

[Service]
Type=oneshot

So once it fails, that's it.

The openvpn.service example has:

[Service]
Type=forking
Restart=always
RestartSec=15

Do some reading on systemd and experiement..

Enable the analogue audio overlay:

dtoverlay=pisound
dtparam=audio=on

Read: https://wiki.libreelec.tv/configuration/…ration-advanced

I can't speak for that service, but WireGuard generally delivers much better performance than OpenVPN does.

<advancedsettings>
  <video>
    <playcountminimumpercent>101</playcountminimumpercent>
    <ignorepercentatend>101</ignorepercentatend>
  </video>
</advancedsettings>

Create /storage/.kodi/userdata/advancedsettings.xml with ^ that content and it should work.

Not that I'm aware of, but it would be possible to periodicatlly edit content in the database to reset status of all media to unwatched.

IIRC the default behaviour can be changed in RPi5 firmware but it's best to search for info on the Raspberry Pi website/docs.

Read: https://wiki.libreelec.tv/support/log-files

Note that "profiles" support in Kodi is often a little broken, and trying to copy things between different OS often fails due to different install locations and \\path\to\files in Windows is not the same as /path/to/files in Linux. Lots of scope for incompatibilty and that's before you roll dice with custom skins.

Trying to run the LE repo will create as many problems as it solves. I wouldn't go there

Just install MariaDB on the RPi4 running RaspiOS and follow the HOWTO in the Kodi wiki for setting up a new DB. Most of the well known SQL tools are php based (adminer/phpmysqladmin) and thus require you to have a webserver somewhere to use them, but there are other tools like SquirrelSQL (which is Java based IIRC) that should run anywhere and give you a GUI to help with dumping the existing DB content and importing it to a new DB instance.

NB: In addition to moving the SQL DB content; if you change the paths to the sources (e.g. change SMB server name) you will also need to update paths in the DB else clients will be able to see everything in the DB but nothing will play (as the /path/to/files will be wrong). If things will change and that all sounds too complicated; just setup new sources, new DB, and rescrape. As long as the media is well structured/named everything will rescrape easily and fairly quickly (current python scrapers are much faster than older xml ones from a few years ago) so it's not the worst suggestion.

To use SSH key authentication you need to add your public key to /storage/.ssh/authorized_keys before disabling password access in the LE settings add-on. Note that disabling SSH password auth does not stop the SSH daemon from prompting for passwords; but it does guarantee that no password will be accepted.

If the device has booted CE it will be looking for CE boot files which are different to LE boot files. You need to trigger recovery boot again so the device searches for LE bootscripts and loads them. This will stop CE from working.. until you repeat the process and make the stick search for CE bootscripts. NB: LE bootscripts use the dtb name configured in uEnv.ini, we do not use the "rename dtb file to dtb.img" process that CE uses, so if you are doing that, it's why nothing works.

There are no browsers for Kodi on ARM SoC devices, only for x86_64 harware using the legacy Xorg image (not for GBM).

Best supported device = RPi5. If you need DAC outputs add a HAT that provides the right connectors.

Kodi .nfo files are used to provide info to a scraper, e.g. telling a scraper to collect information from a specific online media database resource, or providing info to the local file scaper (which does not check online resources). In both scenarios Kodi scrapes info from the media files (with matching .nfo files) for the defined source, into the library database.

So local .nfo files may be needed, or may-not be needed, depending on what the media files are, whether Kodi has access to the internet (easiest) or not (needs a lot more preparation and effort) and what you're trying to achieve with them.

If you're trying to acheive an "offline" Kodi setup, it's probably easiest to start "online" and scrape all media, then export the DB content to local files, and switch sources from the default online scrapers to the local file scraper. Then if something triggers the source(s) to be scraped it will find the local data from local .nfo/image files and be happy.. (in theory). It's not something I've ever personally attempted though and Kodi is designed-for/biased for online use, so YMMV.