Posts by chewitt

Historically most of the important media drivers that LE depends upon for RPi were 32-bit only. Over time that situation has improved, but there are still missing bits. RPi4 brings more drivers. It is overall more 64-bit capable in software than previous generations but there are still gaps (mostly bits that are common with older Pi kit) and the development focus is on must-have functional items more than nice-to-have capabilities like ensuring everything can run in 64-bit (but where new code is written it should support both). For LE there is also an additional consideration for libwidevine support (needed for Netflix etc.) so even in the future when a 64-bit kernel is hopefully available we'll still be using 32-bit userspace in the same 64/32 arrangement we use on other Aarch64 devices.

The Server and Client functions technically have nothing to do with each other, although in most current generation networks everything will be using SMB2/3 to avoid SMB1 so the settings will happen to be the same. The Kodi settings need a reboot (or restart of Kodi) to effect changes.

The current connman feature is working as designed. It just wasn't designed to do much (2.4GHz) because that's fast enough for data sharing between a phone and a laptop. Enhancement to add support for 5GHz and more config is not impossible, but it's not a simple task and we don't have people on-staff with the skillsets to do it. So your choices are: a) find someone with the skills and willingness to code it, or b) get a proper access point.

The hotspot (not access point, hotspot) feature comes from software called "connman" that manages connections in the OS. It was originally written for a mobile phone OS to provide a tethered hotspot, e.g. laptop connects to mobile and shares the mobile connection. As a result it is deliberately simple and the only configuration options are on, off, and the ability to change SSID and passphrase. If you want an access point with access point features and config options, you need to get an access point.

The file /storage/.cache/services/samba.conf (server) is edited via the LE settings add-on. The contents of guisettings.xml (client) are edited via Kodi Services settings. If Kodi is accessing media from something older or misconfigured that only speaks SMB1 then Kodi settings are correct. If the media host is newer and can handle SMB2/3 then it's better to use them (as SMB1 has large security holes) and Kodi settings are wrong. If media is stored on the LE device there is no need to access anything over SMB so it's irrelevant if the settings are mismatched.

Venom is an Exodus fork. No further support.

So you have a garbage realtek driver then. Deja-Vu.

Depends on what the command is, i.e. what you're trying to achieve. Kodi has a fairly comprehensive XML-RPC api that covers many things.

The UK version oif "House of Cards" came first (based on largely the same story-line) and it's a valid response to a query. You either need to provide and nfo file to avoid this, or use the refresh option in the Kodi GUI to select from other available options and then pick the US series.

"Band of Brother" or "Band of Brothers" ?

echo "sleep 10" > /storage/.config/autostart.sh && chmod +x /storage/.config/autostart.sh

^ run that and see what happens. The script is run at the very start of userspace boot and will stall everything for 10 seconds. Kernel side loading should continue though, and I'm wondering if it's just a case of slow loading kernel drivers.

LMGTFY

Yes "works fine for me" .. but I'm using a wireless device with a well written drivers (ath9k_htc). If you're using something with a garbage Realtek USB wireless driver .. YMMV.

Make sure you're using the HDMI connector nearest the power port.

LibreELEC.tv/openssl-config at master · LibreELEC/LibreELEC.tv · GitHub

^ put the certs that you need in /storage/.config/cacert.pem and they will be appended to the embedded certs at boot time.

I think we reached the point where we need to start mirroring add-ons for download instead of self-host

No Linux devices truly support HDR at this time and Kodi has only partial siupport (still work in progress). RPi4 and Intel NUCs (Gemini Lake and newer) are most likely to be best/first supported due to the higher overall levels of development in their ecosystem.

Team Kodi made the decision to bring forward the release for Kodi Matrix (v19) to forcibly kick-start the migration to Python3; because most of the add-on developers are sitting on their arses not-migrating their code. I'd previously expect things to play out over the next ~6 months and that would align with the original v19 not-an-agreed-schedule, but now that v19 comes early it will push HDR to v20. That said, v20 is probably a shorter development sprint than normal to compensate. Not that the word "sprint" should ever be closely associated with Kodi schedules

crazycat is/was planning to bump things once 5.4 is released, not before. I'm also waiting on LE master branch to stabilise after the Py3 changes before spending time on 5.4 things (not much spare time at the moment).