I'd step back a level. Why are you self-compiling? .. i.e. what changes are you looking to make to an image?
Posts by chewitt
-
-
Are you using the Kodi backup addon (which is nothing to do with us, and you need to ask questions to its creator via the Kodi forums) or the backup function in the LE settings addon (in which case we'd like to see a Kodi debug log please)?
-
What are you compiling on?
-
Not unless you figure out how to edit files inside a read-only filesystem. There's a method for using a custom connman_main.conf and you can configure the existing (compiled) featureset using connmanctl, but anything more that that requires a custom OS image.
-
LibreELEC.tv/package.mk at master · LibreELEC/LibreELEC.tv · GitHub
^ those are our current build options. The only reason we build without DNS proxy is the Kodi system info screen then shows 127.0.0.1 and we got bored of dealing with users who think their DNS is broken and claim this is the root cause of whatever other issue they're experiencing.
-
Odd. Can you pastebin a Kodi debug log.
-
LibreELEC (community): 8.2.3.1-C2 (S905.arm)
^ You have an 'arm' build. We run a split 64/32 arrangement where kernel is aarch64 but userspace is aarch32 (arm)
-
The Kodi log is complaining about being unable to open an alsa device. This normally means the audio configuration is wrong (i.e. wrong output device) or something similar.
-
-
No, because Kodi aims to run on multiple distributions and Linux has no standard method so it's up to individual distributions how support is packaged. Once you look at the complexity of handling things over multiple OS platforms (and distros) the idea of using a cloud service that works the same way everywhere, it's actually more simple.
-
Check your audio device configuration.
-
I don't remember that, but then I don't remember lots of things. I keep the arm repo up to date so no harm in using it. If you want to keep building aarch64 it's best to create another repo though. I can setup some webspace if you need it - ping me in Slack.
-
It has made it on the to-do list of the developer who's been poking at some settings addon refinements and changes. It has not (as of right-now) actually been implemented though, but "Rome wasn't built in a day"
-
Sounds about right
-
EXT4 is an efficient in-kernel driver. exFAT runs in userspace via translation layer (FUSE) so is less efficient. If the media file is large enough that could cause a bottleneck. Solution is to play from the EXT4 drive.
-
Could it be possible that the latest User Agent from the Libreelec Version ist not known by the addon repository?
It's because balbes150 persists in creating "aarch64" images and the image is probably still configured to point at the "amlgx" repo that I maintain which only contains "arm" addons. No bug, and I have no intention of building aarch64 stuff
-
On update the old version may be flagged as incompatible, but the first time the LE repo is contacted it will (or should) detect and update to a newer version which should be compatible. It's definitely in our repo at latest version.
Any further investigation requires a Kodi debug log to be shared.
-
Have a look at the "Pi Tools" addon; it most likely has all the extra Python libs/bits required for GPIO work etc, and if it doesn't we'd be happy to accept changes to add them.
