CEC issues since xmas update


#22

Just want to swing by with same issue since the december update.
Setup Vero4K --> AVR --> TV.

Since december update the TV turns on randomly. As of now i deactivated CEC under peripheral since the suggested option to deactivate active source does not help.

The issue is definitely introduced since the update, proof is my second VERO4 runnning on October release. When i hook up the machine and replace the Vero4K everything is back to normal

cheers
Boris


#23

Hi

We haven’t changed anything related to CEC in this update; with the exception of waking the display from standby

Sam


#24

That’s whats happening to me and looks like everyone else, aka the device is being woken from standby, only its happening randomly.


#25

Hi Sam,

but this “waking” seems to trigger a standby TV to turn on. This is what i observed now for couple of times. The TV is in stand by and the vero wakes the screen and thus turns on the TV. When the TV is on the vero seems to run in kind of hibernation mode with a dimed UI.

Will try to create some logs for you to check!

Any questions are welcome to my attention,
cheers
Boris


#26

The Vero is indeed meant to wake your TV when you resume it from standby, as per the December update.


#27

Sure, but this behavior is happening spontaneously, and even when it’s set not to do this


#28

Then I would need to see a log when this occurs, as this is the only CEC change that has been made for several months


#29

log below. everything woke up around 21:00

http://paste.osmc.tv/ipateliwif

Edit: looks like it spontanously wakes up at 20:59:51.391


#30

Are the logs provided above sufficient?


#37

I can confirm I am seeing the same thing, no changes made other than the update.

HDMI CEC is obviously enabled, Vero 4K => Yamaha AVR RX-A770 => Sony 930e

No standby enabled or power savings enabled on the Vero, it just runs all the time, or should be. I use a Harmony remote, and the TV turns off and turns of the AVR as part of its CEC control.


#38

If you don’t use the suspend option at all, it would be very useful to see a log when this happens for you


#39

I will try to find when it happens… My wife is the one whos reported it to me when I’ve been out… I will try to track down a time when it happens. It’s completely random. I had no idea it could have been the Vero until I came here and saw the post talking about the same scenario.


#40

@chamelious + @clegg:

It would be helpful to collect more data on the Vero side by activating logs and additionally activate the libCEC component logging which should write the events of the CEC protocol as well.

You can learn more about how to submit a useful support request here.

Depending on the used skin you have to set the settings-level to standard or higher, in summary:

  • enable debug logging at settings->system->logging

  • enable component-specific logging ONLY for the libCEC component

  • enable event logging and notification event logging

  • reboot the OSMC device

  • reproduce the issue (exactly describe what happend and what is the difference to your exception)

  • upload the log set either using the Log Uploader method within the My OSMC menu in the GUI or the ssh method invoking command grab-logs -A

  • publish the provided URL from the log set upload, here

Perhaps, this will shed some more light to this.

OSMC skin screenshots:


#41

Hi there, i have the same issue since the update and i think i know what the cause is in my case.

setup: vero 4k+ - av receiver - tv.

vero wakes the TV in the middle of the night, so the TV is on when i come out of bed…

i think the cause is the library update request from Sonarr which was triggerd after download. The Vero comes out of ‘standby’ and triggers the TV to turn on. This behaviour was different before the december update.

In Sonarr logs i can see that at 02.50 a serie download was started. In the Vero log i can see activity also at 02.54 and at 03.10 the vero goes INTO standy en seconds later is detects the TV (so it is turned on).

Blockquote
02:54:49.038 T:3442295552 NOTICE: VideoInfoScanner: Starting scan …
02:55:04.132 T:3442295552 NOTICE: VideoInfoScanner: Finished scan. Scanning for video info took 00:15
02:56:59.542 T:4076855888 NOTICE: Samba is idle. Closing the remaining connections
03:10:04.145 T:4076855888 NOTICE: Activating standby mode
03:10:04.274 T:4076855888 NOTICE: CApplication::ToggleStandby – checking for existence of /home/osmc/.kodi/userdata/wake.py
03:10:16.646 T:4076855888 ERROR: GetString: error reading /home/osmc/.kodi/userdata/disp_cap
03:10:16.647 T:4076855888 NOTICE: Desktop setting is 00192001080060.00000pstd
03:10:16.647 T:4076855888 NOTICE: Found resolution 1280 x 720 for display 0 with 1280 x 720 @ 60.000000 Hz
03:10:16.647 T:4076855888 NOTICE: Fallback resolution at 16 + 0
03:10:16.647 T:4076855888 NOTICE: Found resolution 1280 x 720 for display 0 with 1280 x 720 @ 59.940060 Hz
03:10:16.647 T:4076855888 NOTICE: Found resolution 1920 x 1080 for display 0 with 1920 x 1080i @ 60.000000 Hz
03:10:16.647 T:4076855888 NOTICE: Fallback resolution at 16 + 2
03:10:16.647 T:4076855888 NOTICE: Found resolution 1920 x 1080 for display 0 with 1920 x 1080i @ 59.940060 Hz
03:10:16.647 T:4076855888 NOTICE: Found resolution 1920 x 1080 for display 0 with 1920 x 1080 @ 60.000000 Hz
03:10:16.647 T:4076855888 NOTICE: Desktop resolution found at 16 + 4
03:10:16.647 T:4076855888 NOTICE: Found resolution 1920 x 1080 for display 0 with 1920 x 1080 @ 59.940060 Hz
03:10:16.647 T:4076855888 NOTICE: Found resolution 1280 x 720 for display 0 with 1280 x 720 @ 50.000000 Hz
03:10:16.647 T:4076855888 NOTICE: Found resolution 1920 x 1080 for display 0 with 1920 x 1080i @ 50.000000 Hz
03:10:16.647 T:4076855888 NOTICE: Found resolution 1920 x 1080 for display 0 with 1920 x 1080 @ 30.000000 Hz
03:10:16.647 T:4076855888 NOTICE: Found resolution 1920 x 1080 for display 0 with 1920 x 1080 @ 29.970030 Hz
03:10:16.647 T:4076855888 NOTICE: Found resolution 1920 x 1080 for display 0 with 1920 x 1080 @ 50.000000 Hz
03:10:16.648 T:4076855888 NOTICE: Found resolution 1920 x 1080 for display 0 with 1920 x 1080 @ 24.000000 Hz
03:10:16.648 T:4076855888 NOTICE: Found resolution 1920 x 1080 for display 0 with 1920 x 1080 @ 23.976025 Hz
03:10:16.648 T:4076855888 NOTICE: Found (1920x1080@60.000000) at 20, setting to RES_DESKTOP at 16
03:10:16.650 T:4076855888 NOTICE: Updated resolutions and set desktop

full logs: http://paste.osmc.tv/vafevanoto


#42

Hi @sam_nazarko,

my TV keeps waking up even if i disable CET completely under system.
What setting is necessary to completely disable this? Setup the Vero not to hibernate?

Boris


#43

For now – do not suspend the system.
I will add a configurable option in the next update so this can be toggled on or off.


#44

Rather than doing this, can we not revert to however CEC used to work pre december update? it used to work perfectly, and now theres a thread full of users with the same issue. I would just revert to the old firmware but the video changes made in Dec are desirable to keep.


#45

Yes – you can install an older version via osmc.tv/download.

There were a number of requests to send a CEC wake-up signal when Vero is resumed from standby; so that’s what we do.

It looks like a couple of users are experiencing sporadic wake-ups; but it could be a third party add-on or library update (as seen above) causing this.


#46

Hi Sam,

ok. I am running vanilla OSMC without any additional 3rd party lib or program and i am suffering from sporadic wake-ups as well, just to let you know.

Boris


#47

It’s hard to speculate without a debug log.
Some of the reports here aren’t actually indicative of a problem; just reflective of the changed behaviour

Sam