The cause I found out about the Problem is because my Device is a Laptop. If it reboots it while the TV is powered off, the HDMI not work and the Internal Display is activated. So I have to do a reboot again to get the TV output on HDMI0
LE13-20260906-Generic - Crash in the middle of the night
-
Mayoru -
September 13, 2026 at 9:18 AM -
Thread is Unresolved
-
-
Run getedid create from the console with HDMI connected and the kernel will always see the TV as connected:
https://wiki.libreelec.tv/configuration/edid
You can also hard-disable the internal screen:
Laptops | LibreELEC.wikiHow to disable the internal screen and force external HDMI/DP/VGA outputwiki.libreelec.tvIf the issue is something deeper in how the laptop hardware or firmware works, there is nothing we can do. We don't fix laptop firmware

-
OK, thanks. I do not assume the cause in the Firmware. This Laptop worked great before reinstalled as Mediacenter.
- getedid create does nor work. More than a single device connected. Probably enable "Disable all other monitors" at Kodi settings. Aborting! This setting is already set.
- Does the crashlogs help? Any idea why my device reboot at night?
-
Disable the internal screen first then so there's a single device, then it will run.
-
OK, but that is not the goal. I like it to have a way to plug it out and use the laptop as TV. We plan to use it for vaccation.
I think that there is a problem with the auto switcht feature. If I set a screen as prefered, It should be used the moment the screen is available.
I would say this is a bug.
-
I think that there is a problem with the auto switcht feature. If I set a screen as prefered, It should be used the moment the screen is available. I would say this is a bug.
This was merged in Kodi https://github.com/xbmc/xbmc/pull/28633 .. and you will spot me clearly calling out that this feature is not working as it needs to, but it was merged anyway. Technically this is not a bug because the [bad] code is working as [badly] designed; and that incomplete design will be extended in K23. I predict the fix to be invasive; lots of things need to be touched, so it's unlikely we can backport anything to K22.
Our current plan is to hide the setting in the GUI to stop people using it and then complaining it doesn't work as they expected it to work and how it needs to work.