Once you install an addon (ID) from a third-party repo it will only update from that repo even if other repos have the same addon ID and a newer version available. I forget the logic for manual installs from zip but I suspect Kodi will not auto-update the ID from an online repo if you install from zip. Kodi has some very specific logic around repo updates due to general problems seen with piracy oriented third party add-on repos that have the habit of publishing addons and modified dependencies that reuse the same ID(s) with the version articifically bumped to 'force' the modified version to be used instead of the correctly numbered versions available in the official Kodi repo.
Posts by chewitt
-
-
Different issue that we fixed: https://github.com/LibreELEC/LibreELEC.tv/issues/9884 and different zoom issue still being resolved on RPi4/5: https://github.com/raspberrypi/linux/pull/6741
Re-reading the issue report (not on a phone) and I'd guess either the there's no function to do what you want for Zoom? - I don't see anything similar on https://kodi.wiki/view/List_of_built-in_functions or it's not working and needs to be reported upstream to Kodi developers via https://github.com/xbmc/xbmc/issues
-
I've done some further build experiments with patches. In short, the second patch smp flagged does not apply to Linux 6.12.y as the function being patched doesn't exist, and the more I look into surrounding code for the change that adds it, the more I see that r8169 has seen a large amount of change in Linux 6.13.y and 6.14.y and I don't think it's worthwhile trying to add ever-more patches to see if the NIC works.
As LE13 currently plans to use Linux 6.12.y this means the release version of LE13 will not support the chip so you will either need to keep using the development build I previously shared until LE14 ships sometime in 2026 or you will need to learn how to self-build an LE image with a newer kernel. The development image will continue to work, but once LE13 ships we'll bump the LE add-on repo version to match the release version and from that point there will be no updated to the repo, and a some point we'll cleanup/delete the old development repos.
-
The zoom issue was reported a week or so ago and should be resolved in the latest LE13 nightlies.
-
Intel continuously breeds new something-lake chipsets and most folks lost track of what's supported or not some time ago. If it appears not to work with LE12 which uses Linux 6.6.x, test the latest LE13 nightly as that's using Linux 6.12.x. If it's so darn new that even Linux 6.12.x doesn't support it, then you'll need to self-build an image with Linux 6.14.x and cross fingers.
-
We don't allow "warnings" from a random forum user to dictate release strategy. If you have an issue; report it to Kodi devs and then work with them to get it resolved. Then the issue is not an issue, and the fix can go into some future LE update. That's how it works. If you don't report it, there is no issue, or the only person with the issue is you..
-
Just install from the repo over the top of the existing add-on and then future updates from the repo will auto-update things.
The LE13 addon is now merged. Let's see if all is okay and then we'll merge to LE12 too.
-
Run "dmesg | paste" and share the URL so we can see the full log. Always share a full log; every time you share log snippets you are leaving out useful info/context on the device.
-
but UI is crap and I want to get Kodi on there instead
So why not install Kodi on Android?
-
Please update with: https://chewitt.libreelec.tv/testing/LibreE…_64-12.80.0.tar - the image now uses Linux 6.14.0 which contains a load more r8169 changes. If that works i'll revert back to 6.12.x and the extra patch that smp flagged. I'd already built the 6.14 image so you might as well test that first.
-
-
The 2GB is enough for normal LE use. If you want to run additional services in the background (docker, tvheadend, etc.) the 4GB or 8GB variants would be more suitable. The eeprom option POWER_OFF_ON_HALT=1 is not configured in LE by default, but you can change that yourself if desired.
-
-
LibreELEC supports custom alsa routing configuration via /storage/.config/asound.conf so on an OS level there is nothing to prevent you from configuring the audio hardware to route audio from the S/PDIF input to the speakers. However it cannot be done from the Kodi UI as there is simply no concept of audio input (only output) within Kodi.
The next challenge is that alsa configuration and routing is one of the Linux "dark arts" and the configuration you seek is specific to that exact hardware so there is rarely some kind of 'generic' solution or example to follow, and nobody here is an alsa expert, and Google searching for alsa configuration normally returns a million irrelevant results; it's a particularly dense and troublesome topic to search and find useful information on.
As we are unlikely to be helpful and you have nothing to lose; Give ChatGPT or GitHub Copilot examples of amixer controls and amixer contents output and some prompt/direction and ask them to suggest an asound.conf. I have low expectations of anything they create actually working, but it might give you hints for further research.
-
If the subtitle add-on is available from the Kodi repo then it's fine to mention here. Are there any others?
-
I linked the .tar file because you said WiFi worked so you have a working internet connection. I assume this was used to share the previous "dmesg | paste" dump. An .img.gz version of the tweaked image is in the same webserver folder but reinstalling only results in the same state as an update (which is quicker/easier).
Please share a URL from "dmesg | paste" again, so we can see if the chip is now correctly detected and is there any attempt to load firmware? Note that r8169.ko.xz is an xz compressed kernel module (.ko) file not firmware (usually .bin or .fw) so adding that to the image via a firmware overlay will not do anything useful.
-
I'm not sure why it's not working in LE12, but it isn't, and we're unlikely to release more LE12 maintenance updates, so:
Kodi 22 (Piers) removes support for setting the timezone from within Kodi (as this is an OS function) so LE13 nightly images now set timezone from the LE settings add-on, and this definitely works. So the workaround is to update to an LE13 nightly.
-
Pinging this thread to raise awareness of new WireGuard capabilities that need testing:
ThreadWireGuard - Experimental support for connecting via FQDN not IP
Regular ConnMan contributor and SailfishOS maintainer Jussi Laakonen has been working on improvements to WireGuard support in ConnMan. Specifically, the ability to define 'Host' (the remote WireGuard server) as a hostname/FQDN instead of an IP address. This eases long-term WireGuard use with servers self-hosted from dynamic IP address ranges, and commercial WireGuard services where each node has multiple IP addresses in DNS that are rotated reguarly to avoid IP blocking. The changes should also…chewittMarch 25, 2025 at 12:59 PM