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.
Posts by chewitt
-
-
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:
-
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.
