Sorry for this question but did I get this right that the release of LE10 will first be for Generic devices and will be released for other platforms successively after that?
Nope. It will be released simultaneously for Generic, RPi4, and the current roster of Allwinner and Rockchip devices. Everything else is either still in a developmental state or discontinued.
Can someone elaborate on why support for raspberry pi 1 is discontinued.
RPi0/1 devices need to use the older OMX decoder to run well with recent Kodi versions, and support for OMX (and MMAL) no longer exists in K19. Support was removed as part of the long-term cleanup/removal of vendor-proprietary decoding methods in Kodi. The newer GBM/V4L2 video pipeline needs more than 512MB to run well, so we have discontinued support. You can continue using LE 9.2.
4K60 modes are not supported in the LE10 nightly images. Some optimisation is required to achieve it, and it is being actively worked on.
You've purchased a CM3+ "lite" module. The U7 blank on the right side of the second image is where the RAM chip is (not) soldered.
Common mistake #1 is setting the Kodi smbclient "min" to SMBv1 and "max" to SMBv3 because "that covers all options!" but this means Kodi will connect with SMBv2 which is now the smbclient default (as SMBv1 is considered insecure) which is incompatible with the router which only speaks SMBv1. The only way to force Kodi to use SMBv1 is to set both min and max to SMBv1.
Common mistake #2 is configuring the LE samba (server) share options in the LE settings add-on, which have nothing to do with the Kodi smbclient (client) settings which are in Kodi settings > services > smb client.
ConnMan (the connection manager) will prefer the strongest signal for the SSID that you're connected to, so the solution is not installing drivers (which you cannot do on LE) but ensuring the 5GHz network has a better signal than 2.4GHz. The workaround is forcing the router to use a different SSID for 2.4GHz and 5GHz channels, allowing you to only connect to the 5GHz SSID. There is no way to force it to use 5GHz.
NB: Their instruction is for installing a .deb package which I guess contains drivers, but this will not work on LE because most of the filesystem you look at is expanded at boot-time from two compressed and read-only files, and you cannot install things inside them.
The "community" sections were originally created so there was an area for community builders creating unofficial images (for new unsupported H/W) to encourage their efforts and we organised the forum by SoC type to contain things. Over time some of those unofficial efforts became official but the threads didn't relocate and the categories are now sort-of wrong. At some point we need to clean things up a bit 
"take note that CODA driver (imx6) is missing the read-back of parsed SPS (I think Philipp never reversed that) and as a side effect, it cannot implement the SOURCE_CHANGE event used to sync after a seek. You'll notice that seeking works reliably on CODA with GStreamer, but that's only made possible as we do hold some workaround implemented by Pengutronix folks (used on Zodiac in-flight systems)"
^ This is from one of the Collabora engineers who maintains GStreamer. So lack of seeking is known but needs some non-trivial changes in the drivers to enable it. Half the fun with iMX6 is all the documentation and BSP code is under an oppressive NDA, so despite being one of the best-documented SoCs available you have to reverse-engineer everything under clean-room conditions.
Best to report the issue to the creator of the add-on that provides access to FRx channels (not LE or OSMC). Most add-ons have a support thread in the Kodi forums.
iw was moved to the image when we added the wireless regdomain feature, so between 9.0 and 9.2
SMBv2 or SMBv3 work "out of the box" and SMBv1 requires you to reconfigure the Kodi smclient to use min/max SMBv1 (and perhaps legacy security) if that's all the ancient samba version in the router will support.
There are three: YouTube, YouTube Channels, Tubed (Matrix only). You're probably referring to the first one.
Kodi overscan settings only change the output of Kodi itself so when you run this add-on Kodi is stopped and the add-on runs from the framebuffer which has no knowledge of them (or mechanism to recreate them) then when you exit Kodi restarts and the overscan settings are reapplied. The solution to overscan is to set the TV to "just scan" or similar so you don't need overscan, it's a hack. You might need to change HDMI outputs as some TVs don't support it on all.
OK. Bad news for le but thanks for your reply!
The number of active nVidia users continues to dwindle with time and stats show the vast majority have older cards (using the older of the two drivers we ship) so even if we implemented support for NVDEC and EGL streams in Kodi (could be done, but nobody in Team Kodi is interested in implementing another proprietary nVidia method) this will only benefit the tiny number of installs with the latest cards. In the end, GBM/V4L2 is a big move forwards for Kodi and not having to maintain the 40+ packages needed for X11 support is good news for LE.
Just test stuff .. and report things that don't work or cause problems. If things work, we don't need to know. Debug kodi.log and sometimes dmesg if it shows errors are useful .. you can "cat /path/to/log | paste" to send to a paste site and get a URL to share. Most staff auto-ignore text file attachments (as too much effort to download/open) and logs pasted into posts (as usually ends up incomprehensible to read).
Hello all! I have a nvidia and as I underdtand, after libreelec 10, it won’t be supported anymore or did I get it wrong ?
At some point, after LE10, probably LE11 (K20) we will transition LE to GBM/V4L2 and you will either need to transition to another distro that runs X11 with the nVidia vendor drivers, or change GPU to Intel/AMD. No dates, but it will happen.
LE is not derived from any other distro, it's assembled from sources using Welcome to Linux From Scratch! principles.
