Posts by chewitt

There's nothing in the log to indicate a specific problem. Does it show up when it's the only device connected?

It is technically possible, but would require you (not us, you) to rewrite the skin to add the pick/choose function.

You'll find all of the former OE forum staff and regulars here. There's really only one person missing, but he was the reason the entire team left and forked LE in the first place, so he's unlikely to show up anytime soon.

The 8.1.102 add-on was built for LE 8.0 which has compile differences to LE 8.2 and the 8.2.x series of add-ons. You need to remove and reinstall it or update it to the 8.2.x version. This *should* happen automatically unless the add-on auto-update feature in Kodi is disabled.

I'm unaware of an issue with manual update being ignored so I'd suspect a person vs. fast internet timing issue. The default is auto-update and the OS update image for iMX6 is small so if you have a fast connection the settings add-on has probably polled for updates and downloaded the update to /storage/.update by the time the first-run wizard has completed and you go into LE settings to disable updates.

We are aware of an issue with black screens on official iMX6 releases that use a 4.4 kernel. It's never been pinned down but affects a small minority of users. It's possible to use LibreELEC-imx6.arm-8.2.1-3.14-sr.img.gz from vpeter which uses an older 3.14 kernel (which has other issues, but the black screen is not one of them.

If you install 8.2.2 directly it will not update as there a no more 8.2 releases planned. I suspect you will still see a black screen on reboot though. It is not possible to disable 'kernel' updates as the OS is packaged as single unit of kernel and system.

No, OSMC is running on debian environment that can use Xorg. LibreELEC does not use X11/Xorg for it's Amlogic releases.

RetroPlayer will be a Kodi v18 feature, so part of our 9.0 release.

READ THIS THREAD BEFORE POSTING !!

Install Raspbian on an SD card, then install the debian binary, then copy the binary to an LE install and see if it works. The kernels etc. are quite similar so binaries from Raspbian or Ubuntu sometimes work. If it doesn't work, you'd need to create a custom LE image with a new package that compiles the binary from source and bakes it into the image.

Quote from smp

I tested on RPi3 and I can confirm that reverting commit 4cd13c21b207e80ddb1144c576500098f2d5f882 completely fixed the issue.

^ to be pedantic, it works around the issue, it does not fix the issue. Adding patches is only a short term solution and we don't want to add patches all the time as it impacts long-term sustaining of the distro. At least we now understand where the issue lies.

There has been contact between developers on the AMD side of things and their work on VAAPI should (no guarantees, but should) fall into line with the future Kodi linux graphics architecture we're driving. No timescales though.

Unless you've seen a particularly cheap AMD card to acquire I'd stick with the nVidia card for a while until the way forwards is more visible.

There is not much interest in developing for the 8726-MX chipset in those boxes when something 10x better can be acquired for $30 these days. It can probably be done, but there is probably not nicely written guide or pre-pacakged release.

You can keep asking, but no friendly guide for hardware porting exists, and there are no plans to create one. There is an extensive library of "prior art" in our GitHub repo. If you have the skills for the task, or the aptitude to learn them, everything you need is there.

Intel drivers in the Linux kernel do not currently support HDR, but development is ongoing. Kodi Krypton also has no formal support for HDR, but this is expected to become part of the Leia release. If HDR is a big requirement you will have to suffer Windows for a while longer.

Old routers may require SMB1 and the legacy security option to be forced. It's a simple change in Kodi SMB client settings.

In future please ask for a thread to be moved instead of posting the same thing twice. The previous thread has been deleted.

Last I heard Xtreamer went bust, hence the lack of website. One less GPL violator in the world

There are a couple of community efforts for S812, but it uses the older 3.10 kernel which doesn't see much activity or focus. Look for S812 threads.

It's not an add-on, it's a compilation dependency for the Chromium add-on, hence in the addon-depends subtree