Posts by Flachzange

    What screensaver are you using? Using Aerial, I can't get the screensaver to come on if I have a movie paused, but I can if I use the black screensaver, which for whatever reason flickers between a light and a dark black, but that one doesn't turn off the TV at all if I'm in a movie. If I'm not in a movie, the black screensaver does turn off the TV. A single press of the remote does turn on the TV now.

    For screensaver issues look into this thread: Paused video shows scrensaver, but does not turn off via CEC.

    I don't have Aerial as a screensaver, only black and dim, but what you describe is basically confirmed in the other thread as well. My issues are not with the screensaver, but the idle functionality for the display.

    Maybe it's relevant, but in Settings/System/Input/Periperals, I have two CEC items

    I don't have an RPi, but I only have one entry. Are you using an external CEC adapter with the RPi?

    and 4 minutes later, Kodi killed the display signal but didn't power off the TV. Back to the "no signal" message on the TV.

    Which is the same behaviour here, only that I cannot resurrect the TV easily afterwards (~1 min later)

    1. If I have a video paused, the visual screen saver kicks in but the TV never turns off. I do have the CEC setting to turn off the TV enabled. If no video is paused, the TV does turn off as expected. My workaround is to use the turnoff screensaver for now, but I was wondering why a paused video would break CEC's ability to turn off the tv.

    I can confirm this now. The CEC shutdown/suspend is not initiated while a playback is paused although the screensaver was activated

    After numerous trial and error attempts, I have some more information

    • A couple of seconds after sending the display to sleep, it can be resurrected via any button of the remote
    • if the display was sent to sleep (disconnected HMDI) and no button seems to work, the remote is actually operating Kodi in the background and you can blindly operate Kodi. Once you play a movie, or start TV, the display is signalled again
    • A connected USB keyboard behaves exactly the same. Also, the keyboard is not able to resurrect the connection

    => Conclusion: It seems not an issue of CEC, the TV, or the AVR, but rather by Kodi not resurrecting the display if any button is pressed received from the remote or an attached keyboard

    Especially the part with the keyboard makes me think that others should have the same issue, if it actually is a broader issue.

    I recently migrated to LibreELEC after using Kodi Standalone on Linux for 15 years now. The setup and migration was super smooth and LibreELEC is working very well.

    I have only one minor issue left with the display idle functionality.

    Short Story:

    The sleep functionality in "System->Power Saving -> Put display to sleep when idle" results in a disconnected HDMI signal and I am not able to resurrect the connection via the remote control. The TV shows "searching for input"

    Restarting the Kodi service via SSH works and also start playing something via the app remote control brings back the display.

    Long Story:

    System Setup:

    • AVR: Denon X2800H
    • TV: LG OLED
    • LE box: x86-based hardware with Pulse Eight CEC adapter

    The dedicated screensaver functionality on the other hand works as expected in combination with the CEC config. Once the screensaver kicks in, TV and AVR are switched off and switched on again once a button on the remote control is pressed. Because it is configured to behave like that at the moment. I would rather like to use the screenscaver as an actual screensaver and use the idle functionality which is not working for me at the moment.

    In my old Kodi 20 setup, the idle functionality also disconnected the HDMI signal and the TV was looking for a source, but I could easily bring it back by pressing a button on the remote.

    I have not changed any of the CEC config in KODI, the AVR, or the TV compared to my previous setup.

    Logs: https://paste.libreelec.tv/smiling-mongoose.log

    Is this a known thing with the current LE / kodi build or maybe someone has any ideas what the issue can be?


    Cheers

    Chris