Posts by chewitt

Kodi expects the audio hardware configuration to remain static so it will not dynamically switch between two different configs although you could probably detect an HDMI event to run a python script to make changes over the XML API. Also, on most laptop/generic audio chipsets the alsa configuration will just output sound on all devices; and to change that you'd need to dig into the configuration for that specific chipset and come up with a custom audio routing configuration. It's all technically possible but alsa expertise is one of the Linux "dark arts" and you're unlikely to find willing volunteers and a nicely typed-up howto.

Kodi on Windows probably handles this scenario better.

The mobile phone tethered hotspot feature in connman (which is what you're using) is not a replacement for a proper router, and a quick glance on eBay shows things available for £10. Using the right tool for the job is often easier.

Tvheadend runs under Kodi which also runs as root. It's possible to screw up permissions in LE and do lots of other wrong things, but wrong user is never the problem.

Normally ehe onboard WLAN device will be wlan0 and the USB device wlan1, and the connections screen in LE settings identifies the network name and the device which scanned it. So connect to the right network with the right device and the job's done.

You'll need to build the entire distro image as the binaries are in a read-only filesystem. I'm not au-fait with the patches in Milhouse's release but if it has the current work on whitelisting which replaces "adjust refresh" you'll need to whitelist the modes it will switch to, so check that.

Krobar submit a pull request on github with a reasonable explanation for why the config change is needed and it will be considered. As a general rule enabling a couple of minor drivers isn't a big deal and shouldn't be an problem.

If you remove /storage/.kodi you end up with a clean Kodi configuration but not a clean LE install; some config resides outside /storage/.kodi

The first thing to do is test a current Milhouse Leia build because nothing is going to be fixed in Krypton now. If the issue still exists in Leia then it needs to be reported to Kodi devs via their forums.

The version of Krypton hasn't changed since but there will be other changes. It's usually hard to tell with community releases due to all the hacks that get recycled and the dubious version numbering. It's not Leia though, which is the main thing, so apart from the different ARCH (aarch64 vs arm) which requires you to remove/reinstall any binary add-ons the Kodi settings will be compatible.

That location is temporary so don't get too attached to finding things there.

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.