Kodi's screensaver switches input (CEC) back to Vero V

Help and Support
1

HDMI1 - ATV
HDMI2 - AVR (eARC)
HDMI3 - Vero V

  1. Stop watching on Kodi
  2. Press ‘home’ on ATV remote → TV switches to HDMI1
  3. After 2m (Kodi screensaver setting) → TV switches to HDMI3 + screensaver starts

Ideally, the screensaver would not kick in if there is no active display… I don’t think such an option exists.

I looked at the CEC adapter settings from Kodi, but there is nothing I see related to my scenario.
Am I overlooking an option?

P.S. - I don’t remember having this issue on Vero 4K or Vero 4K+.

2

Turn everything off for five minutes (TV, all attached devices).
This sometimes happens if you swap HDMI ports or devices unexpectedly.

3

Same sort of thing happens to me on Raspberry Pi.
I had not associated it with screensaver / dimmer kicking in but it might well be.

Note - RPi is plugged into AVR along with some other stuff on same AVR. If I switch sources on the AVR then this problem does not happen.
However, I have Amazon FireStick on a different HDMI port on the TV. If I switch to that from AVR which was showing OSMC/Kodi then it switches back to Kodi after a few tens of seconds.
If I switch source on AVR (to Freeview STB) and then switch HDMI on TV to FireStick then everything continues to work with no automatic switch back.

4

Did you try power cycle everything? I can reproduce this behaviour but only if I shuffle HDMI cables around which confuses the TV a bit

5

The issue is gone now. I did turn off all devices (AVR/TV standby + OSCM power off) the other day.
Strange :slight_smile:

Thank you both for the suggestions!

6

@sam_nazarko I was too early declaring success. The automatic switching back to HDMI3 (Vero) when the screensaver kicks in is no longer occurring when switching to HDMI1, but now when I power off the TV while HDMI3 is active showing the screensaver, AVR and TV are powered off and immediately woken up again to HDMI3…

Is there no way to stop the screensaver when the monitor goes into suspend (or some other signal telling the system that there is no active output)? It might save power too.

7

Save yourself the grief and just switch to the dim screensaver. I keep mine set just bright enough that it is noticeable and I don’t think the TV is off when it is not. If your using a TV that varies its backlight, or an OLED, this should reduce power and also likely minimize the impact of it being on (burn-in and the like).

1 Like
8

Could be that the ATV or Fire TV are asserting the same logical address…
Can be manually overridden via Peripheral settings, but first I’d work out which device is causing the conflict.

9

I’m afraid to ruin my new LG OLED after my last one suffered from severe burn-in.
To give you some context, LG have removed their screensaver to work on external inputs for any duration below 30m (unless you enable ads to show): https://www.reddit.com/r/LGOLED/comments/1f9fol1/screensaver_gone_after_update_on_c3/

In the meanwhile, I’ll go with Dim and test it out.

@sam_nazarko

CEC bus information
===================
device #0: TV
address:       0.0.0.0
active source: no
vendor:        LG
osd string:    TV
CEC version:   1.3a
power status:  on
language:      eng


device #1: Recorder 1
address:       3.0.0.0
active source: no
vendor:        LG
osd string:    CECTester
CEC version:   1.3a
power status:  on
language:      eng


device #5: Audio
address:       2.0.0.0
active source: no
vendor:        Denon
osd string:    Audio
CEC version:   unknown
power status:  on
language:      ???


device #8: Playback 2
address:       1.0.0.0
active source: yes
vendor:        Apple
osd string:    Woonkamer
CEC version:   2.0
power status:  on
language:      ???
10

It’s now working across the board with and without a real screensaver!

  • Force AVR to wake up when Kodi is activated: OFF
  • Send “Inactive source” command on shutdown: ON
  • Devices to power off during shutdown: TV
  • When the TV is switched off: Suspend
2 Likes