I already installed OpenVFD from CoreELEC repo, and put the correct vfd.conf on ./config folder. No change on the clock...
What am I doing wrong?
If you want to run CE code from CE repos, run CE, and then you post "it doesn't work" messages in the CE forum where someone that cares about CE code issues might reply to your message.
can i install LE in USB and boot from Amlogic? if can, please give a tip? thank!
If the (unknown) device has a working device-tree in the upstream kernel, it should be able to boot the AMLGX "box" image from USB.
Stuff is a bit broken right now due to not caring too much about old infra that broke itself (again) and people being super-busy with day jobs which is limiting time spent on the new infra which still needs some experimenting. Remember we're all just a bunch of volunteers doing this in our spare time for fun (allegedly) 
It hasn’t progressed since the last snapshot above (20220504), but since you are the third to find me with WP2, now I’m really trying to get one from somewhere (at a reasonable price).
dtech I have another WP2 box lying unused at my parents in the UK, so if you don't find one via eBay I can always post that one to you when I visit them in mid-July.
WP2 is usable with the LE11 codebase based on upstream Linux (currently 5.18.0); albeit with no support for the DVB tuners inside (as there is no support for them upstream) and HEVC decoding being a little unpolished. H264 is good, other codecs are mostly software decoded but that isn't a big deal. NB: That specific image contains upstream u-boot and to use it you must completely erase Android from the internal emmc storage while the "box" image can boot using the vendor u-boot that comes with Android on the emmc storage. Neither WP2 or box image can update an existing image/SD card, a new/clean one is required.
It's not clear/decided whether Amlogic support is formally resurrected for LE11 as newer hardware has some major issues to solve, but there are no plans to stop nightlies.
Once the changes go through there will be no hotdog folder and no need for lots of per-folder releases.json files (only one).
I didn't submit these changes. Do you want to use for your device?
I'm interested to see what's required for RK3568. Target device would be Odroid-M1.
balbes150 do you have RK356x change in a GitHub repo/branch? - I looked but didn't see them in your account.
I worked in IT for 25+ years. I would make zero assumptions that any developer expected their code to run in a container on a cheap ARM board device and considered how that might affect transactional integrity in backups. That said, the rate of change in MariaDB from Kodi use is probably low enough that you will get away with our backup process. The best thing to do with backups is a) take them regularly, b) store them off the device that can go wrong, c) prove you can restore them too (not all the time, but occasionally).
So does LIbreElec work now with the zero 2 w?
LE11 nightly images will boot/run on the board, but will probably deliver a weak Kodi experience for two reasons. First, 512MB RAM just isn't really enough for Kodi 20 and a good overall experience and we see the same on other 512MB systems which is why the project has chosen to drop official support for all hardware with under 1GB RAM. Second, the newer RPi codebase no longer supports all the "clever but hacky" optimising done to OMX/MMAL in the past (these no longer exist in Kodi) so HEVC will be a problem. The simple reason there are deliberately no official LE 9.2.x images for the Zero2 is: we didin't want to add support for something in LE9.2 that we already dropped support for in the next release (LE10). TL/DR: You can boot LE11 but don't expect it to be great and when it isn't, don't expect support.
Zero2W is an awkward one for people. As it's 512MB it really needs the older LE codebase which is lighter on lower spec hardware, but at the same time it launched after we've stopped all work/effort on that codebase. It's not particularly hard to add support for it (although users in that forum thread seem to have done things the hard way) but we deliberately chose not to spin an official image with support; because we already decided to drop support for <1GB devices in LE10+ .. so we don't want add support and encourage people to purchase Zero2W boards when we effectively already discontinued support for them. It's not a bad board, but people have high expectations and it's still low-spec so we have to be sensible about the amount of work we create for ourselves.
Kodi add-ons are stored under /storage/.kodi so core TVH add-on/settings should be backed up.
RPi Zero W is supported in LE 9.2.8 but no longer supported in LE10+ due to the <1GB RAM rule.
Cloning requries you to duplicate the entire filesystem, and filesystems have all kinds of checks and such to detect corruption; hence when the size of source and target aren't the same it all goes wrong. Instead make a backup and then restore it to the target; this way you are working only with the content of the filesystem and not the entire disk. The content of the filesystem is a lot smaller, more manageable and thus the process is also quicker.
TL/DR; learn how to use tar .. make a backup, then restore the backup. LE settings has this capability built-in, although it only grabs specific folders (/storage/.kodi, /storage/.cache, /storage/.config) not all folders.
It seems you love unsupported low-spec hardware. Note that LE 9.2.6 (or 9.2.8) will not run on a Zero2W because it was launched some time after we released the last LE 9.2.x image so the image doesn't include the required firmware and other boot bits. In theory it can run LE11 images (nightlies) but it will probably run rather 'meh' due to low RAM on that model; we decided to officially not support anything with less than 1GB starting with LE10 to avoid those kinds of support issues (sound familiar?). That guidance is documented in release notes for LE10 and such (that we write and nobody reads). There is also a thread around here with some people flailing around the process of trying to backport Zero2W support to the older codebase, but I stopped reading that thread after a while as it made my head hurt.
The decision about what to support (or not) belongs to individual maintainers, not me, although there is general agreement among the team to avoid boards with less than 1GB RAM for LE10 and above to avoid a certain category of support issues.
Kodi does not support fade in/out itself, but you could pre-process the video content to include those steps to effect nice transitions between videos in a playlist. I'd assume content used for advertising or kiosk type use-cases? will be pre-processed to ensure everything is correctly encoded for nice output anyway, so I'd build that book-ending step into my encoding pipeline. See https://donaldfeury.xyz/add-fade-in-an…ts-with-ffmpeg/ for one approach.
Kodi supports play/pause/stop and management of what's playing (or playlists) through APIs. It also has controls for speed, but you probably don't want to mess with speed for good output (again, if you do, do it during encoding). There are no controls for Hue and Brightness in Kodi (or at OS level in LE) - in our opinion (and what's been coded for) those belong to the TV not the player software.
LE/Kodi support basic kiosk/advertising type use-cases, but to do something more professional you probably want to develop a custom Skin that avoids OSD pop-ups during transitions and might need to make code changes to add features, and all the code is open-source to help with that kind of thing. NB: LE does not take on 'paid' projects, we're not resourced for that kind of thing. Kodi is much the same although some of their team are independent developers in their day-jobs and might consider paid work; but there is no formal channel to ask for a quote so you'd need to post in their forum and hope someone 'bites' on the opportunity (it's never guraranteed).
Can you build in some kind of feature, to use 24Hz in case of a 23.976 fps file?
Atm it switches to 60Hz, which is uncomfortable.I also looked if I can force 10bit output (s905x) - sadly I found nothing.
Is it a feature missing in kodi or lima?
Kodi supports refresh rate bounding/override via advancedsettings.xml; you can define min/max boundaries and what refresh should be picked so you could define 23-24 and force 24Hz instead of using 3:2 pulldown and/or 60Hz.
GXL (S905X) hardware supports 10-bit decoding so you can play 10-bit media, but the SoC internally downmixes to 8-bit HDMI output so it's a hardware restriction and the AVR/TV will always show 8-bit output. GXM (S912) was the first Amlogic SoC to support 10-bit output.
