I can test this tonight. But can I roll back to 12.0.2 using the same commands ?
Yes/No. Kodi upgrades DB files and add-ons when you update, and does not support downgrades, so make a backup first (see the basic file copy below) and then rolling back is a simple case of stopping Kodi, moving the folders around again, then repeating the "update" using an older image.
systemctl stop kodi
cp -R /storage/.kodi /storage/.kodi-backupI will get around to investigating temp things at some point, but to be clear, it's entirely cosmetic as the OS self-manages anything to do with temps, and a long way down the list. There is no need to further report the problem unless you are reporting a complete fix.
Settings > Media > Videos > Library > Flatten TV show seasons > Always .. and disabling "Show All Items" will reduce the number of navigation levels, and you need to set the viewtype to what you prefer at each navigation level. TV Shows has more potential levels due to the concepts of Seasons/Series and Specials, etc.
In LibreELEC once Kodi runs it opens/owns the alsa sink preventing anything else from using it, so audio MUST go through Kodi to reach the audio hardware; ergo Kodi is the only place to implement something. General purpose desktop distros will be different because they typically implement some other layer, e.g. PulseAudio or PipeWire, and Kodi runs audio through them, so Sendspin integrates there to reach the hardware. LE can also use them, but PulseAudio has rather limited support for pass-through audio (a popular feature with users) and PipeWire either has similar limitations and/or isn't so well supported once you move away from the x86_64 hardware (me is forgetting which) so there's always a compromise and hence we don't use them by default.
I've bumped the test images in my share to 12.95.1 and they contain Linux 7.1.1 kernel and K22-Beta1. In the last couple of days I dug out an Odroid C2 with HiFi-Shield2 DAC and finally wired it and a WeTek Play2 box up to the digital inputs on my AVR for some long-overdue S/PDIF testing. This flagged FIFO buffer underrun issues (aka, machine gun noise) in the AIU audio driver when you switch between HDMI and S/PDIF inputs and when S/PDIF playback stops, which Claude fixed. and some minor changes to the HiFi-Shield device-trees. The HiFi-Shield2 board is now confirmed (by me) as working fine and I plan to send this upstream. It would be great to also get confirmation on the older HiFi-Shield+ board (which I don't have) so it can also go upstream.
Put Kodi in debug mode, demonstrate the problem, then run “pastekodi” share the log URL generated so we can see what it does/doesn’t do.
I saw a mention about autostart.sh in /storage/.config and put my alias there, but it didn't work (no error, but no alias command either)
It did work, but only in the context/lifetime of the autostart.sh shell session. Once the script exited, the config died too.
The diagram shows you are using CE. Problems should be posted in the CE forum; because we have nothing to do with their images and have no knowledge of how audio routing has been wrangled/mangled for the Amlogic BSP codebase.
Everything is in our main GitHub repo.
I don't see how this is relevant to this particular case.
It's relevant because explicit configuration of things is a general design objective for the buildsystem. Whether that was/wasn't an option in the past is irrelevant because what's possible today takes prescedence.
I plan to leave the PR open for a while for people to show up with comments on the state of MPEG2 decoding.
Please consider updating service.bluetooth-audio so that it stores and applies the full Kodi PulseAudio device identifier:
If you've investigated the problem and already figured out the fix/solution, perhaps send us a pull request?
Our general preference with packages is to always be explicit in what we enable. That way package featuresets never magically change because some upstream maintainer changed the scope of "all" without us noticing.
Looks like it should changed to -Dvideo-codecs=all to enable all codecs rather than list them individually.
Our preference has always been to be explicit about what we build and support rather than use catch-all configs.
ConnMan owns resolv.conf and it exists in /run which is not persistent over reboots. You can configure things using the settings add-on which has a dbus-agent that speaks to connmanctl, or by using connmanctl from the CLI, or by cloning /etc/connman/main.conf to /storage/.config/connman_main.conf and editing defaults there (reboot to effect changes).
It might be better to enable the capability in code and allow people to disable through Kodi VAAPI settings if there are issues rather than the current block in code?
Is there a reason why it's disabled/missing in the Mesa package.mk?
There's no reason that I'm aware of, although for context I haven't paid much attention to x86_64 matters for about a decade. You are welcome to send a pull request. We'll leave it open for a bit and see what comments it attracts.
Clear SPI and boot LE from SD card. Establish that you can see the NVME drive, i.e. the kernel modules and device-tree stuff is there to support that function. Format the NVME drive with a single EXT4 partition 100% sized with a unique disklabel. (re)Mount /flash as writeable and reconfigure /flash/extlinux/extlinux.conf so disk=label=STORAGE points to the NVME disklabel instead. It will boot from SD card, but Kodi effectively runs form NVME so you see the benefit of faster I/O access.
2026-06-17 06:29:45.745 T:807 info <general>: Running on LibreELEC (community): nightly-20260612-5c96e68 13.0, kernel: Linux x86 64-bit version 7.0.8Please bump to a current nightly as the RTL8157 changes I can see were merged for Linux 7.1 and are not present in Linux 7.0