Posts by chewitt

Submit an enhancement request to the add-on maintainer(s) via the Kodi forum support thread for the add-on.

Quote from coreflake

Any ideas on what I could try ?

Sharing debug log-files, else all we see is another user expecting us to divine the problem using magic and we'll go find someone else to help.

Quote from mylarguten

can someone make the generic to a img file? impossible to get 11.0.1 online to use the tar file

Did you think of looking in the same folder to see what other files are there?

As per release notes; the AMLGX image is not perfect and will not be for all users. I'm not too interested in bug reports because I know the hardware decoders have bugs, there is nothing I can do about that, and comparisons with CE are meaningless since the codebase has 0% kernel and driver code in common.

HDR format: Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, HDR10 compatible / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile A compatible

Dolby Vision = No

HDR10+ = No

HDR10 = Yes

HDR = Yes

TL/DR; ^ the static formats are supported, the dynamic and proprietary ones are not. I'll also caveat that right now LE/Kodi (on Linux) have reached the "HDR support v1.0" milestone, and maybe v1.5 on RPi4 which has more plumbing for colourspace and bit-depth wired up. HDR support still needs more things in the Linux kernel to be agreed upon, and should hopefully improve with related planned changes for Kodi Omega (v21).

video=Composite-1:720x480@60ie  <= NTSC
video=Composite-1:720x576@50ie  <= PAL

^ add one of those those to boot params in cmdline.txt; notice that PAL gives higher resolution than NTSC so if the TV supports it, use PAL.

LE11 will have better compatibility with add-ons. LE 9 is starting to show age now.

I've enabled auto-update earlier so you should be prompted now too..

Go into the LE settings add-on, change to manual update, select 11.0.1, then later (after download/reboot) switch back to auto again. No need to reinstall between minor version bumps.

Here are two test images for RPi4 and Generic (GBM) that contain connman/iwd with latest patches/changes (HEAD):

https://chewitt.libreelec.tv/testing/LibreELEC-RPi4.arm-11.0.1.tar

https://chewitt.libreelec.tv/testing/LibreELEC-Generic.x86_64-11.0.1.tar

If others can confirm things are resolved we'll get the changes submitted and merged.

Quote from gozothegreat

Could it be possible to create a Generic-legacy image for Virtual machines also?

No. The current image is created solely to facilitate internal dev/test work in vmware workstation/fusion and is not formally supported (and not on other hypervisors) so we have no desire to create more versions. If it happens to run anywhere else it's a coincidence, and if it breaks (and it does, because staff are not using it often) then we have no promise of fixing things.

At the moment there are still some add-ons and Kodi Omega plumbing bits that are not aarch64 compatible so we are deliberately omitting the config needed to permit successful crossgrade from arm to aarch64 images; and based on how future testing goes we might decide to not allow that anyway. As such the update from arm to aarch64 is being correctly rejected. If you make a clean install, the aarch64 images should run fine; albeit Kodi Omega is a pre-Alpha codebase right now.

In LE11 the keymaps need to be in toml format which is similar and human-readable but not the same as the older text file format. Have a look at existing toml files in the system and crib the format (the wiki article needs to be updated to show this).

It may help to have 1080p 60/59.94/50/24/23.976 modes whitelisted and adjust refresh start/stop enabled as it will eliminate or greatly reduce the amount of correction Kodi needs to attempt; as the decoder doesn't handle correction too well (same issue as seeking). There is no known list of problem media configs/types so nothing to avoid .. it either works or doesn't.

I'd be interested in a sample of the file for long-term testing with problem media, but currently there isn't anything I can do about fixing the decoder so my advice would be to transcode the file to H264.

frakkin64 the two patches I picked off the list are here: https://github.com/chewitt/connman/commits/invalid-key

An image for RPi4 with two additional patches from the connman list for someone to test. I have low expectations that either patch will resolve anything, but for the sake of a 30-second rebuild: https://chewitt.libreelec.tv/testing/LibreE….arm-11.0.1.tar

[Unit]
Description=ngroc service
After=network-online.target nss-lookup.target time-sync.target
Wants=network-online.target nss-lookup.target time-sync.target

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/path/to/ngrok tcp 22

[Install]
WantedBy=multi-user.target

^ something like that in /storage/.config/system.d/ngrok.service

Then "systemctl enable /storage/.config/system.d/ngrok.service" and "systemctl start ngrok.service" .. it should then be persistent over restarts and even upgrades (as long as ngrok itself continues to run).

Run "getedid create" with the system on/working and the EDID data from the HDMI connection is captured and cached so the HTPC will always see the AVR/TV as being connected. Much easier than scripts.

Over time the software packages we use evolve; normally adding support for new hardware and features, and occasionally doing spring cleaning to drop support for old hardware. The version of mesa we use in LE11 (mesa is responsible for 2D graphics like the Kodi GUI) has done spring cleaning since the version used in LE10 and the GMA950 card appears to be one of the casualties.

Options are:

a) Custom image that uses an older (pre spring-clean) mesa version

b) Disable onboard video (if possible?) and use a newer supported card

c) Stick with LE10

A is not guaranteed to be possible, but also not hard to try if you have some self-building skills. If tempted with B, pick a newer Intel or AMD card, not nVidia (else you are forced to use the Generic legacy version of LE). C is the easy option.