It's possible, but basically requires you to run a full desktop OS like Ubuntu in a docker container. There is no "native" way to run things on RPi because we run Kodi on the framebuffer not an Xorg environment.
The situation might change in the future if GBM support evolves in Chrome (for ChromeOS) as the next generation of Linux graphics pipeline in Kodi also uses DRM/GBM to support V4L2.
LE is intentionally a dumb client OS with no package manager and our approach to these kind of changes is to have people create and release community images with a unique builder ID via these forums first. Then if we can see a feature is popular (the builder ID allows us to count active installs) we will consider absorbing the changes into official releases. To avoid "the death of a thousand cuts" we have always avoided making speculative changes.
Most Kodi binary addons in out 9.0 repo are currently out of date. It's known. Some build failures are being resolved and then we'll push updates and do a built run to get everything updated. NB: As we're still sat on the fence regarding technical direction for Amlogic images in 9.0 those might not updated with the same priority as other build targets. It's not that we don't care about Amlogic.
If you want an easy life the ls.io repo is the way to go ..
Sounds like you've hidden the "add sources" option via Skin settings.
<advancedsettings>
<!-- enable debug logging -->
<loglevel hide="false">1</loglevel>
</advancedsettings>Kwiboo ^ Kodi debug without the GUI overlay and without needing to fiddle with boot config which enables debug for the entire OS.
Frits1980 it would help your cause if you provided a Kodi debug log that shows it attempting (and presumably failing) to connect to the DB. It would be good to see what error message is captured?
Last time I looked it was already in our addon repo.
If the driver can be added by setting CONFIG options in the kernel we'll happily add support as it's a trivial change. If the screen requires an out of tree driver that isn't under active maintenance (and it looks like it) we aren't interested. Sorry.
I may have found an audio bug.
Multi-channel audio support is incomplete. At the current time the only audio we expect to work is 2-channel stereo.
would like to know how I can add other skin or addons with and then compile
There is "prior art" in the build-system, but it's not something we encourage or discuss in the forums because we want to avoid people releasing "builds" full of piracy add-ons. Sorry.
Any tips on why it won’t connect?
Win10 now mandates an authenticated connection. Go into the LE settings addon and enable password protected shares. Now you can connect with user/pass and it should be happy?
LibreELEC.tv/package.mk at master · LibreELEC/LibreELEC.tv · GitHub
^ PKG_VERSION controls the Kodi version used; we use the githash for the Kodi commit (version) you want to use.
There's no need for autostart.sh and a 10 second delay in wait for network is normally fine so if it's not working after 30+ seconds either your NAS is broken or you have another problem. Are you connecting on the right ports? .. correct credentials?
If the work-around is simple can you please tell me what it is for the sake of summarizing this topic?
Enabled the "wait for network" timer for ~10 seconds and delay Kodi startup until the network is ready. If you're one of those people who sleeps their NAS and disks that 20 seconds to spin up before the DB is accessible; set a longer time.
Kodi has no ability to "wait a bit" when connecting to the DB so it bails out to sqlite DB files (which are empty). It's more of a lacking in feature than a true bug .. and it's messy code which is why Kodi developers have studiously avoided trying to "fix" the missing feature for a long time. The fun part about software like Kodi which is developed in everyone's spare time pro-bono is you can't task and make any of the devs do things they are not personally interested in. This 'problem' doesn't show up on Windows, macOS and Android because those are slow booting and the network is always up long before you find the icon to click-on and launch Kodi. The biggest issue is that the workaround is simple, so the developers with the skills to fix the problem use the workaround. If it was fiendishly complicated to workaround someone would solve it 
We do not provide any torrent apps for LibreELEC and they are not a use-case that we care about. If it runs, keep it to yourself. If it doesn't run (or runs badly) .. not our problem.
It's not a great surprise that crypto functions run better as 64-bit code on a 64-bit processor but you may hit two challenges running aarch64 LE images. The first is there are no aarch64 binary addons in our repo; because there are no official LE 9.0 aarch64 images. The second is addons requiring libwidevine (e.g. Netflix/Amazon) will not work as there are no 64-bit 'arm' versions of the lib in circulation to use. Being able to access DRM protected services is a hallmark feature/capability for Kodi 18 so this is the primary reason LE moved from aarch64 in LE 8.x releases to a split 64-bit kernel and 32-bit userspace arrangement (the same as Android) for LE 9.0.
Questions on RK crypto things might find an audience in the #linux-rockchip channel on IRC, or perhaps their GitHub issue tracker:
