Posts by chewitt

Please test again with a Milhouse Leia build. Krypton has been dead code for a while and Leia has many changes so there's not much point investigating unless you're working with current code.

advancedsettings.xml - Official Kodi Wiki

Kodi default smb client timeout is 30 seconds

Different device, different antenna, different results. The best I can suggest is experimenting with different channels on the router to see if one works best, because ultimately it's a radio problem.

which part of "for LibreELEC 8.2 for RPi2/3" is not clear?

If the USB drive is only used on LE then EXT4 is best, but this is not readable from Windows or macOS. NTFS and exFAT are the two cross-platform "portable" filesystems. Both are supported and should be trouble free.

there are no changes in 8.2.4 that would benefit iMX6 so just ignore that it exists

I've no idea what the solution could be, but Chromium runs completely outside Kodi so there is no interaction with Kodi fonts.

If you connect the SD card directly to another computer config.txt is in the root folder of the first partition. The /flash folder only exists when you access via SSH.

It's the responsibility of the community developer whose image you are using to provide addons. LE has never shipped an S805 image so we have no add-on repo for S805 devices.

Kodi v18 for iMX6 is in technical limbo. The older iMX6 interface in Kodi was broken for some time (more than six months) due to large surrounding changes in Kodi and nobody stepping forwards to maintain the code, which has been an issue for a couple of years. The irony is that iMX6 is maybe the most comprehensively documented SoC that exists for Linux, but anyone who has access to that documentation is under an NDA that prevents them from contributing their knowledge (gained from closed sources) to an open-source project. So right now we have a working OS image for iMX6 on a mainline kernel but the etnaviv DRM driver only supports a single output plane, which is not an impossible issue but affects performance (as drivers normally support four which allows GUI and video to be processed separately and combined before output which is more efficient). The DRM driver also doesn't handle mode switching properly so Kodi cannot change from 1080p60 to 1080p23.976 etc. and playback is not as smooth (and again, not as efficient) as it could be. There is allegedly some work going on upstream towards solving those, but we're a passenger in the process and right now there is nothing we can combine into something we can put our name to. I have a suspicion that iMX6 will skip a Kodi release, but might stage a comeback once upstream efforts on iMX8 have a trickle-down effect and improve things.

OMXPlayer is a Raspberry Pi thing. It is not supported on any other platform, and it is probably being deprecated from Kodi (in favour of MMAL which is another Pi only thing) after v18 ships.

It's sounds like that rip you made from CD/SACD didn't go right. I'd also rip to WAV or ISO as those are better supported file formats.

It's possible to pop a simple toaster with simple one-line messages but anything more requires skin support for the Window format, which won't exist unless you tweak/hack the skin. However, the goal of a working systems is a) it just works, b) you watch movies not console output. If you fail on those criteria the configuration or something more serious requires code debugging and fixing, which requires proper tools, which means using SSH to see things, which means this is not required.

usb_modeswitch can be install via the system-tools add-on in our repo, but some devices (that present themselves as a CDROM) also switch if you eject the disc with a simple "eject /dev/sr0" so that's something to also investigate.

Not that I'm aware of.

You can experiment with the "snapcast" client/server add-ons in our repo.

Also look at dmesg and check the driver is correctly detecting/setting the correct wireless regulatory domain for the network. In some cases the driver doesn't (not always the drivers fault) and this results in missing radio frequencies which restricts or prevents 5GHz from working.

For non-x86 devices it depends on uboot configuration. If the device uses the manufacturer provided uboot (which is the case in 99.99% of Amlogic boxes) it will not be possible as the console config is not required for Android so is missing from the uboot config. For SBC devices where we provide uboot (and in the future when running a mainline kernel where we can force CMDLINE options) it's possible to have a console same as Generic.