Posts by chewitt

Quote from ApexDE

Is there a time-schedule for the 10.0.1 Release? (with new Kodi and playback fix for corrupted recordings - RE: LE 10 Nightly unstable / Kodi crashing on RPi 4B)

No specific schedule, but soon-ish. There are some bugs we'd like to resolve first.

LE Settings = Samba Server, Kodi Settings = SMB Client. You need to set Kodi SMB client to min/max SMBv1 and if the SMB implementation is really ancient and rubbish you may also need the legacy security option setting.

Quote from blackride

Can we hope to improve the LE 10 for the odroid C2?

It should be quite usable for H264 things now (1080p, not 4K) and with the 41KHz/48KHz issue resolved I've re-enabled HDMI in the alsa-conf and passthrough works fine. I'm still trying to figure out why audio channels are mixed up with non-passthrough media, and the static noise bug is there as a nasty suprise when it happens. There's been some discussion on the linux-amlogic mailing list to "ask the audience" on that problem, but so far no eureka moment. No change to video - still neglected

Quote from kennywoo

Can some one guide me to detailed install instructions on how to get this to boot on my Minix U1. Ive tried Belana Etcher, Rufus placing the correct dtb image on card. Toothpick method and nothing. Can someone guide me to a solution. Thanks

Create an SD card from https://chewitt.libreelec.tv/testing/LibreE….0.1-box.img.gz then set the minix u1 dtb name to use in uEnv.ini (the filename is in the dtb folder). NB: You do not rename anything to dtb.img or move files to the root folder (unless you want to break boot). I'm not sure what state the U1 dtb is in right now - I did work before but it wasn't widely tested. Also note there are a few audio glitches to resolve still (in addition to all the video things).

Minor progress on a couple of things: One of the issues with the audio driver used with GXBB (S905) boards was figured out so there is no longer any need to force output rates to 41KHz to output 48KHz media. See: https://patchwork.kernel.org/project/linux-…googlemail.com/. This also leads to a major simplification for alsa configuration which we will send upstream. Sadly we still didn't figure out *that* static noise problem for GXBB/GXL/GXM devices yet, and this is what I regard as the minimum fix before some nightly images can resume. In the background I also have the full vendor sources and schematics for Minix Neo U1 (S905) and U9-H (S912) devices. I plan to extract and post the boot fips so that mainline u-boot support is possible. I can also validate the device-trees which have previously been created with user support (U9-H is upstream, U1 still wip).

Tethering changes default routes. It's hard to know whether that's an issue though .. I've never used Rasplex (which is a dead project these days) and the OE codebase it was forked from is also rather ancient now. Show logs of anything/everything and we might be able to figure out what the problem is.

Two things come to mind. First, LE has a local firewall that can be enabled. Second, the ports aren't mapped in the container configuration.

Google limits the number of searches per API key so the default key in the add-on is exhausted quickly. The workaround for this is creating your own 'app' as a Google developer and then configuring/using your own API key (with your own limits). This is probably what the YouTube video is instructing you on.

The buffering issues are something separate: Google has started throttling unofficial clients. Workarounds for this are still being figured out.

cp /etc/connman/main.conf /storage/.config/connman_main.conf
sed -i 's/PreferredTechnologies = ethernet,wifi,cellular/PreferredTechnologies = ethernet/g' /storage/.config/connman_main.conf
reboot

^ Removing wifi from PreferredTechnologies should ensure eth0 always has the default route (maybe .. not tested). You can then create a systemd service file to set defaults routes after the network is up and before Kodi starts.

I don;t know what IP is used for NPU in RK chips but in general NPU drivers are often a challenge to upstream due to NDAs and restrictions on the SDKs from the IP owners.

Just disable update checking in the browser.

It makes no functional difference whether you update from .tar or .img.gz files, but .tar is a little faster. I did make a mistake in the commands though, I did not recreate /storage/.update though I hope you spotted that as the next command was to cd into that dir before downloading the .tar tile. Please check the udpate file is in /storage/.update (note the . it is important) before rebooting to update.

The Kodi Plex add-on is a client with a sole purpose of playing media stored in a Plex server. If you want the media to be visible in the Plex client you need to add it to the media library in the Plex server. If you run a Plex server on the same HTPC host as Kodi (and the Plex client in Kodi) you can map media from local drives. If you run the Plex server somewhere else; you'll need to remotely mount the drives so that the remote Plex server host can see the media on them to add into the Plex server library. Kodi doesn't follow a rigid client/server model in the same sense; the GUI just provides access to media wherever you store it, and in your install that media is local which is easy.

It is not possible to change the behaviour of the Plex add-on without writing code to change the behaviour. As the current add-on is created by Plex staff the behaviour is intentional and I doubt changes to access local media would be welcome.

Linux 4.19 is less-worse than 4.4 but the underlying issue is the same; userspace apps like Kodi and FFMpeg (and g-streamer, not that LE uses it) are evolved around V4L2 kernel APIs and code that simply does not support the vendor kernels. The good thing is - Rockchip has numerous corporate backers funding upstreaming development for chipsets like RK3568 so support is being actively worked on and is starting to land in mailing lists .. and as long as that work follows standards (which it is/does/will-continue-to-do) creating an LE image in the future should be fairly simple.

The precise ordering that's possible with systemd *is* the leanest way. Anything else requires guessing (the timing) and hoping (that you guessed correctly). Note that startup scripts will often need "/path/to/pactl" not "pactl" in them.

Perhaps just create a systemd service to run that command after pulse is running and before Kodi starts; systemd will allow that.

2021-10-12 17:32:01.107 T:3908014960   ERROR: CCurlFile::FillBuffer - Failed: SSL peer certificate or SSH remote key was not OK(60)

It's not the NTP/time issue that invalidates the cert (which produces different error messages). It's also not clear what the issue is, but I'd hazard a guess that something fundamental with the TLS cert is bad, e.g. ciphers supported or perhaps broken chain of authority (signed by someone that the embedded certs in your 9.0.2 image cannot trust).

If you attempt to download https://mirrors.kodi.tv/addons/leia/sc…ktail-1.1.0.zip direct from the console you might get more info?

NB: There are some community releases for S905 devices that are newer than 9.0.2 which might be worth investigating on a spare SD card. Sadly the LE10 codebase is not ready for prime-time use (board support is good, media capabilities are not).