Posts by chewitt

Quote from Paul Webster

I know that this thread is ancient ... but ... is there still a way to preconfigure WiFi?

There never has been a way to preconfigure it (LE has never packaged os_config.json). I'd suggest you force the SSH daemon to start by adding "ssh" to boot params in cmdline.txt and then connecting an Ethernet cable. As you have not configured an IP on the RPi it will auto-configure itself with a 169.254.x.x/16 address. In the absence of DHCP the device you need to connect from should also self-configure itself in the same range (which is a large range) and you can run arp -a or perhaps ping the broadcast address (the .255 address of the local subnet) to discover the other device's IP address; and then connect over SSH. Once connected over SSH you can run connmanctl > agent on > scan wifi > connect <name-of-service> to configure the network connection, and use kodi-remote to navigate around the screen. If you struggle with the remote IP discovery another approach is to have your computer connect to WiFi and then share its connection via Ethernet to the RPi, which results in the RPi using a known IP subnet that requires less guesswork.

Quote from Flat

I've forbidden automatic upgrades, waiting for stable LE13 to come up

FYI, development/nightly images never auto-update.

All forms of "spinning rust" media have a lifespan; typically 5-7 years but nothing is ever guaranteed. Boot LE with the drive attached and run "pastekodi" and share the URL so we can see the kernel/system log. I'm expecting to see a bunch of errors that suggest the USB drive has problems; the errors can/might hint whether the issue is related to a messed up filesystem (might be recoverable) or something more hardware oriented.

See https://github.com/LibreELEC/LibreELEC.tv/pull/11533

Official:Forum rules/Banned add-ons - Official Kodi Wiki

You have banned add-ons installed; no support

IMHO the three main causes of hardware lockups are power and thermal issues, and then software issues. For hardware like an Intel N100 device the software side is used at a large enough scale that hard lockup bugs in software are quite rare.

Quote from Flat

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-backup

I 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.

Quote from alexxx

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.

Quote from smp

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.

Quote from alex.caserini

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.