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 
Posts by chewitt
-
-
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:
-
Also run some ping tests to see whether 1.1.1.1 is faster than than 8.8.8.8 from Google. In some parts of the world it is, but in mine the CF servers are consistently slower than Google so I left things as-is.
-
Try setting SSHD_DISABLE_PW_AUTH="true" in /storage/.cache/services/sshd.conf and run "systemctl restart sshd.service" to bounce the daemon and reload the new config.
-
Retest with a current milhouse build (assuming this is a 'Generic' install if it has USB3) which runs newer everything.
-
IIRC library auto-update can be run nightly or on startup, but there are kodi-send commands that could be used with systemd .power services to run a command on wake. Subtitle options changed between Jarvis and Krypton so you will need to adjust them.
-
This forum has nothing to do with Android.
-
I apologize in advance if this is a silly question, but are there plans to eventually merge them into LibreELEC down the road?
Apology accepted. Yes.
-
There are no publicly released images for LE on the shield so that can be eliminated. Have a look at MrChromebox.tech for instructions on how to install LE to the Chromebox.
-
I got if from my original Android firmware
Android device tree files work on Android not Linux. On an LE 3.14 kernel they will be similar, but they are not interchangeable.
-
The reasoning still stands. On most devices time to wake from hibernate will be slower than a clean boot. Also consider that 85%+ of our installed base has hardware that lacks the power management functions to hibernate. You're welcome to self-build and experiment for your own needs but it's not even remotely on our roadmap to resurrect hibernation.
-
SSH in and "rm -rf /storage/.kodi/addons/blah" where blah is the name of the addon
-
CGarces I've not been tracking the status/state of RT drivers for some time. If adding the missing ID works please send a PR
-
Intel and RaspPi are the only two manufacturers who will get reliable Kodi support in the future.
I look forward to making you eat your hat in the future. Seriously
-
I wouldn't expect a mainline release for K18 (LE9.0) at this time.
-
I'm already running an LE image with K18 and a Linux 4.17.3 kernel on S905+ devices but the codebase needs to hit some milestones before we invite public testing and feedback. The core OS is solid but audio/video are still in a proof-of-concept state. LE is orchestrating the current activity on Amlogic mainline audio/video things and one of our extended team also contributes to Armbian; so once things are useable Armbian will see some updates too.
-
You can install Kodi add-ons that contain binary apps (as network-tools does) but there is no apt-get or equivalent in the OS. So you either add things to extend an existing add-on package (and then submit changes to our git repo.. or not) or you create new ones (and submit them to our git repo.. or not). I think the questions you're asking show you're not familiar with how LE is build/packaged, so before you run away with ideas of reconfiguring LE to be OpenWRT go find the "self-build" instructions in the wiki and compile an image. There are no instructions on how to add more packages to the OS, but there is a ton of "prior art" in our git repo. From past experience; if people have the skills and knowledge to succeed in that kind of task .. that's all they need to get started.
