Splash loading is implemented simple, see here. Look for the file and use ply-image to display it.
So why not to use my (currently) broken LE for testing purposes?
You can add debugging break=load_splash to the APPEND line of syslinux.cfg to start a debug shell after loading the splash. Be warned, this stops the boot process by opening a shell and requires an attached keyboard.
I believe they won't as it is clearly said only 32bit will do.
They do (usually) work.
Where are they located on the HDD after LE is installed?
They are included into the internal initramfs of the kernel and not accessible after system is booted.
No, I don't. Black screen with LibreELEC (official): 11.0.1 at the top left corner.
Then splash is not visible on your system.
With this discussion in mind I noticed that splash is not visible when booting LE11 or LE12 in VMWare Player (just a development setup). LE9.2 or LE10 do show the splash.
A debug shell session show the splash is extracted successfully but not visible until redraw due to scrolling.
Maybe something with framebuffer device changes but it is working on my real HW.
They are included in the LE images and shown by default.
Do you see a splash screen without custom oemsplash .png?
Default splash files are at https://github.com/LibreELEC/Libr…ibreELEC/splash
Which HW do you use?
The colors have to be opaque (alpha channel 100%)
a) New settings are only applied after reboot.
b) /storage partition full?
c) A pastekodi after reboot may show more.
a) The VNSI Addon is using the VDR channel notation like 1_0_1_28AD_431_A401_FFFF0000_0_0_0.png, not the channel name.
b) You have to enable Debug Logging and PVR Component Logging to see the messages.
c) In addition it is (or was - did not test this recently) possible to use Channel Name Logos via the Kodi Core Settings.
a) As you already know the script mentioned in OP can only work on Generic-legacy (X11), not on Generic (GBM). I'm not aware of a GBM tool to be capable switching resolution.
b) Even on Generic-legacy the device name ("HDMI1") may have changed . Type xrandr to check this.
c) /storage/.config/sleep.d has to be used.
You can override guisettings.xml settings from advancedsettings.xml.
Can confirm the issue. Until fixed add systemctl restart samba-config to autostart.sh.
The device names are auto-generated from the chip set by the driver and device card0-HDMI-A-2 (or HDMI2 in X11) is connected.
Configuration is stored in /storage/.cache/services/samba.conf and processed with /usr/lib/samba/samba-config
Remove any EDID configuration, reboot and create complete logs with:
pastekodi
paste /var/log/Xorg.0.logMaybe something is visible.
What does it mean anyway? What can't he do?
The error message is irrelevant and printed on not-ARM systems. This is fixed in recent kernels.
releases_v2.json is WIP for update process changes of (maybe) LE12.
I've no idea how releases.json was generated after 11.0.1 release. This "Generic"/"Generic" may be intentionally but then a copy with "Generic-legacy.x86_64" can be added. Maybe someone else does know more.
Regarding the USB keyboard you need to get more information what is causing the problem.
Best start with wired keyboard and test in any available USB port.
Repeat with the wireless keyboard. Please keep in mind that for best transmission the keyboard should "see" the USB dongle.
