Glad you got it fixed. You can try now to apply the overclock back, though I'd recommend you give it a try without it and see how the system performs. The Pi4 should be powerful enough for most systems.
@ramco That's weird, I never saw a TV/Remote who shuts down Kodi or the Raspberry, the power button is never assigned to o CEC button, it should only turn off the TV.
Probably it is your TV brand, never heard about that one. Each TV brand as it's own CEC implementation and name, yours might be one of the weakest.
You said you are running Kodi 18.2, Kodi is currently in version 18.8, update it and check, although I doubt it will fix your problem.
@Marco-G gpu_mem=320 is pretty much essential if you want to play high bitrate 4k hevc. You don't need as much if you don't play this kind of media.
About hdmi_ignore_cec_init=1, what it does is to not switch (the TV) to the Raspberry Pi/Retropie source when it is started or rebooted. It has no effect in anything else.
Emulstation and kodi should not be services enabled/start by default at boot but rather autostart.sh start the first service by something like:
systmctl --user start kodi.service
if kodi is configured to be the first one.
To go further we can also think about replacing the autostart script by a retropie service which is enabled at boot time. At start, it launches the first configured service. At stop it ensures that emulstation and kodi are stoped.
If the service is run as pi user (which is more secure), the pi user must be lingered to enable autostart of the service at boot even if the user is not logged in.
loginctl enable-linger pi
systemctl --user enable retropie
All the services could be controlled, inspected, logged through the systemd tools
Not need for automatic login
It could be easily extended to any number of services not just 2.
@jbsapp Unfortunately, no. I stopped searching for a solution after awhile, since it doesn't bother me that much. Actually, I came to appreciate that the beautiful Comic Book Theme is shown from time to time this way.
A friend of mine who is an electrician suggested to short-circuit the port in question by sticking a piece of wire in both sockets. I never got around to do this unbelievably complicated operation, though. 😇
@Rascas the issue is max_framebuffers=2 on retropie. It should be max_framebuffers=1 when using a single display. This resolved my issue.
Tried all different cables, monitor inputs, monitor outputs, rebuilding libcec. only solution was max_framebuffers=1.
Could this issue be fixed by making customisations to the /etc/emulationstation/es_systems.cfg directly rather than creating a copy or would that put the customisations at risk of being overwritten & lost?
The system file (in /etc) is maintained by the RetroPie-Setup script, so it might get changed by an update, so it shouldn't be used for custom systems.