Each Kodi version bump necessitates some rework from add-on authors, which creates an opportunity to fiddle and change things, and K18 > K19 included the Python2 > Python3 change which almost certainly mandated some rework. So where, say, the Krypton and the Leia versions of the add-on are probably quite similar, the Leia and Matrix versions are very likely to have bigger changes. The author is key..
Posts by chewitt
-
-
Sony STR-DN1050 has HDMI ports. Use them!
-
I suggest you flag the issue to the add-on author via the Kodi forum thread.
-
-
The problem is the clock is not being (re)set via NTP at startup, so the system clock falls back to a default value (glibc version release date) which is before the validity start-time of the TLS certificates used on the add-on repo servers (the S in HTTPS). As a result your system sees the webserver certs as invalid and the connection fails.
The connection manager in LE defaults to pool.ntp.org servers, so either access to these is being blocked (some ISPs do this) or there is something odd in your network (perhaps DHCP from the router sets the NTP server with a null value). Either way.. this is the problem you need to solve. As long as the ISP is not blocking port 123 (NTP) you should be able to find/set other NTP servers in the LE settings addon; then reboot to effect the change. If the ISP is blocking the port, they probably provide their own NTP server, or you will need to have a local in-network time source (NAS box, Active Directory server, etc.) or invest in an RTC chip/hat for the RPi4 so that you can manually set the clock and persist the time value over reboots.
NB: Kodi regional settings are irrelevant to this problem. It's the system clock value that matters.
-
est ce que cette version, peut -être téléchargée et installée en mode mise à jour, ou bien faut-il repartir de zéro.
Repartir de zéro est préféré si vous ne comprenez le process de migration. Dans l'avenir postez aussi en Anglais SVP (la langue de notre forum).
Restarting from a clean install is preferred unless you understand the manual upgrade process. In future please post in English as well (it's an English language forum).
-
Matrix is just different, there is nothing changeable.
-
The system boot fine but it can't detect the wifi chip inside the box.
The p212 dtb is expecting a Broadcom SDIO module and the one pic I can see of the board shows one (see below). So what wireless chip is in the box? - share logs from LE10 and the older LE8.x image.
-
Sorry, it's not clear. Did setting the locale work? .. or you made some other changed that worked? Or it is still not working?
-
The official RPi3 PSU (presumably with a USB-C adaptor) is under-spec for an RPi4.
-
Did you install and then set the system locale to DE and reboot .. or just install the add-on?
-
Please use "pastekodi" and make sure it's a debug log file. I'm lazy for not looking, but you won't believe how annoying it is to be asked to download and unzip log files when it's the 10,000th time.
-
The "lsusb" output isn't helpful, we know the kernel driver probes/loads and is running and it just (conf)uses space in the post. I think you're going wrong at the lirc level. I have low personal knowledge of this stuff, but I know you need to create the conf and options conf and reboot to effect the changes, not simply restart Kodi. Maybe HiassofT has suggestions when he returns from vacation.
-
Are there any recommendation which settings in the whitelist should be configured?
As per previous post (#2): enable adjust-refresh with start/stop, then allow double-rates, and whitelist 1080p @ 23.976/24/50/59.94/60.
-
Please post the problem with Kodi debug logs in the Kodi forum support thread for the Aeon Nox skin. It's unlikely to be an LE problem, so best to start there.
-
It's not a debug log .. so impossible to see some important configuration and media details.
-
This image is current LE10 with connman bumped to latest commit, which includes the connman WPA3 change. Please test and report back:
-
Amlogic uses a prioprietary partition scheme that Amlogic u-boot and kernel can understand, but no conventional userspace apps (fdisk, parted, etc.) can work with (see: "Partition Table: unknown"). As a result installing to emmc can only overwrite the contents of specific known partitions (/system and /data) instead of generally reformatting emmc to be used with LE. Android has a pile of other partitions defined which still exist on disk and consume space, but have been hidden from LE to keeep things simple. So you won't ever see the full 8GB.
