It will be in LE11 (Kodi 20) .. it's technically possible to backport onto K19 but it's a large patch so we'd avoid doing that.
Posts by chewitt
-
-
What did I miss?
You miss the fact that RPi4 does not support HDR > SDR tonemapping. There is no IP block on the chip to handle this translation in hardware and since 99.9999% of HDR media is 4K it's never going to be practical to handle this in software. Perhaps you have other devices which do have this capability?
-
I suggest you push the changes to a GitHub repo in addition to sharing pre-built files. It's the best way of attracting interest in things.
-
OK I know W7 is out of date but is there a reason why SD creator will no longer even open, no error message or anything in W7?
Win7 is no longer supported. Given the quantity of security issues in it now we'd strongly advise you update it to Win10 (which is free IIRC).
-
Last time I used Kodi on Windows was maybe 9-years ago so I'll avoid commenting. And LE is designed to test-boot from a USB key so the best way to find out whether anything makes sense or works is creating a USB and having a go yourself.
-
Nothing known or done on our side. Must be general internet wobbles in the ether.
-
Amlogic technical direction with their latest chips (S4, T7, etc.) is not friendly towards open source and basically forces distros to use vendor u-boot and vendor kernel sources. That's the opposite of LE technical direction so even when it's technically possible to boot things I'm not sure we'll invest time/effort in supporting them. TL/DR; don't hold breath and ask me again this time next year to see if anything changed.
-
Correct, it has initial support under Windows. K20 will add some improvements under Windows and hopefully initial support under Linux.
-
Install. Finish the setup wizard. Go to LE settings and update the RPi firmware(s). Avoid restoring backups from LE 9.x as these will restore Python2 add-ons that often cause issues (hence all the "clean install" advice for LE10). If you really need/want to restore things do a manual unpack of the .tar backup file and then manually restore only the bits you really need.
-
LE has no support for S905W2 chips at the current time, and since this is an all-new SoC type any future LE support will depend on Amlogic upstreaming lots of new drivers. I have low expectations we will support these chips anytime soon. NB: These boxes are built to run Android. Kodi runs on Android too; so I suggest you use it that way.
-
Kodi 19 does not support HDR, hence LE10 does not either. You need to use a Kodi 20 (LE11) development build.
-
-
Connect a UART cable to the board and share the early boot output.
-
Those commands only work on the LE11 image.
-
La langue de notre forum est Anglais, desolé.
-
1. First option sets global default NTP servers, and second sets connection specific servers that override the defaults when the connection is the active one. 2. Forces a startup delay in the LE boot process for X seconds; the second (in Kodi settings, not LE) has something to do with power and likely doesn't have any effect on LE since most HTPC devices (RPi4 is a good example) lack power management hardware.
-
Code
WP2:~ # echo 0 > /sys/devices/platform/leds/leds/blue:power/brightness WP2:~ # echo 1 > /sys/devices/platform/leds/leds/blue:power/brightness^ the first command (0) turns the BLUE power LED off, but the underlying firmware (which we have no control over) switches the LED to RED. It can be reversed with (1). It's a good example for why it's hard to have a consistent feature in the settings GUI. Put some black electrical tape over the LED and it can be silenced.
For boot, I never understood why users are so obsessed with running from eMMC. I run an WP2 from a decent SD card (with mainline u-boot, as I wiped the emmc clean) and this works nicely. An RPi4 will be better overall, but for it's age the WP2 is still surprisingly useable.
Note that LE11 is functionally behind old vendor kernel images (no DVB tuners, no deinterlace etc.) .. there are few developers working on media drivers so progress is a bit slow.
-
Code
systemctl stop kodi mv /storage/.kodi /storage/.kodi-old touch /storage/.update/.nocompat reboot^ after downloading the update file to /storage/.update .. this just moves the old Kodi install out of the way so that add-on issues don't cause issues as part of the update. Kodi will start in the new version with a clean environment, and then you can stop-kodi/move/restart-kodi to put back the essential bits you really need.
