Posts by chewitt

It's the same add-on in the same unmaintained state. Chromium seems to revise itself every-other release and thus needs a high level of effort to keep working. Ideally the community would step up to assist with the process of maintaining, but despite the existence of other versions we don't see submissions to GitHub. If that doesn't change we may choose to drop it from the 9.0 repo.

Nothing stands out apart from file read errors which is normally about a lack of bandwidth between pi and the source (smb share). If you connect an Ethernet cable does everything work? (if yes, wireless is the issue).

codesnake ^

Kodi (on Linux) doesn't see new DVD hardware if connected after startup. Reboot with the drive connected and it will be seen.

If you run "touch /storage/.update/.nocompat" before updating (as advised on-screen) the update script will bypass the CPU architecture compat check, but I wouldn't advise doing that. Kodi is not designed for downgrades (only upgrades) so things like guisettings.xml from a newer version will be partially invalid on an older release and any binary add-ons installed will fail to run as they're compiled for arm not aarch64.

It will be better to take a backup, move it off box, clean install to the older release and then selectively restore specific things like add-on settings and thumbnails from the backup to speed up the rebuild time.

Save /storage/.kodi/userdata/keymaps/Keymap.xml to somewhere off-box and the restore to the same location after a clean install.

Linux is not Android (thankfully) and the answer given in post #2 is still the correct answer.

It's the pop-up that appears when you insert an external storage device and it's mounted. You can create a udev rule that prevents devices with specific names from being mounted. You cannot disable the pop-up.

days not weeks

Python2, with a fixed configuration to suit Kodi (no PIP). Have a look for the EPG tools from edit4ever as they may bundle what you need.

Kodi requires Python v2 (v3 in the future with v19) so it's not user selectable, and the OS is read-only (appliance like) so does not support Python PIP unless you start creating your own add-ons with modules you require included in them. AFAIK everything else apart from socat is available though. You may be able to find add-on code for that if you don't mind self-building.

Contrast and brightness are adjusted on the TV using the remote control, not on the Raspberry Pi.

If you want to run banned repo's you're asking for help in the wrong forum. The door is that way ---->

Create /storage/.config/asound.conf and it will be used.

The autostart.sh script runs at the start of userspace boot before anything Kodi related is run. You can use it to script movement of files and folders to create a clean (or cleaner) runtime environment, e.g. moving /storage/.kodi to /storage/.kodi-old will give you a clean Kodi instance.

If the SoC chipset in your box is mentioned on this page Rockchip open source Document there is an active effort by Rockchip and the Linux community (of which LE is a part) to create mainline Linux kernel support for it and there is a possibility to run LE/Kodi images. Vendor and community efforts are focussed on current shipping and future Rockchip SoC's not the legacy stuff that shipped a few years ago, so if a SoC is not listed (and yours is not) we are not working on support and post #2 is the final answer.

The main problem with unreleased software is that it's not finished. We didn't even make an Alpha1 release yet.

disable lirc in LE settings?