V18 - Suspend not working

#1

On v18, my Vero 4K+ is refusing to go into Suspend mode (or at least refusing to stay in Suspend mode; I think possibly it suspends for <1 second).

Sometimes it works correctly one time after I reboot; other times not even once.

Logs:

https://paste.osmc.tv/cebokoraxa

1 Like

After Easter Update, Suspend Does Not Work
#2
2019-04-15 11:38:45.347 T:4057985760   DEBUG: LIRC: - NEW 66 0 KEY_HOME_UP linux-input-layer (KEY_HOME_UP)
2019-04-15 11:38:45.348 T:4068044800   DEBUG: ------ Window Deinit (Custom_Overlay_Debug.xml) ------
2019-04-15 11:38:45.348 T:4068041440   DEBUG: CAnnouncementManager - Announcement: OnScreensaverActivated from xbmc
2019-04-15 11:38:45.349 T:4068041440   DEBUG: GOT ANNOUNCEMENT, type: 4, from xbmc, message OnScreensaverActivated

Might be a Input Layer Problem we had seen before.

@sam_nazarko you remember the topic?

0 Likes

#3

I’ll test this later today.

0 Likes

#4

I’m having the same issue with the daily builds. trying up to a dozen times will normally work somewhere in that range.

0 Likes

#5

Nightly builds are also based on v18 – so that makes sense.

Sam

0 Likes

#6

I can’t reproduce this reliably on the 18.2 release candidate. Works at least 9 times out of 10.

0 Likes

#7

It does seem to come and go. After a reboot it was working fine today, but after watching a film and then using the Netflix plug-in for a bit, it had gone wonky again.

0 Likes

#8

I have the same issue. Triggering suspend makes the screen go blank for a fraction of a second (and I can see on my AVRs display that apparently HDMI is switched off(?)) but after a second everything comes back to life and I’m back at my Kodi home screen.
I haven’t looked at the logs yet and I also didn’t run any test series to see how many times out of 10 it might actually work.
Just wanted to let you know that this seems to be a common issue.

Sebastian

1 Like

#9

Please upload debug logs after you rebooted and tried to suspend. And also list down all the input devices (Remotes) you have connected

0 Likes

#10

I run the Vero 4K as stock with no add-ons, just configured for video & audio settings to match my Home Theatre setup. I was on the December 2018 firmware. The suspend function worked. I updated to the April update through the Vero 4K built-in My OSMC Updater.

I found that the Suspend did not work. When chosen, the blue LED flashed red momentarily, then turns blue. The screen goes black for about four seconds and then shows the default screen.

Before updating, I had experienced some erratic behaviour in that sometimes (increasingly more often than not) 4K movies would not load. I would either get a twirling icon, a black screen or the screen would still show the movie name (no picture or sound) with a time stamp at top right showing that the movie was actually playing. I sometimes could back out but most times it froze, resulting in switching the power off at the wall. When the movies played OK and I tried to jump forward using the up arrow, I would get the word “buffering” at the top right and the Vero 4K would freeze.

This errant behaviour continued after updating to the April update.

I decided to reinstall the 2018-12-01 update from a USB stick. Did so. Suspend works again. No problems playing any movie. The previous problems were gone. Perhaps it had got a bit buggy like Windows does over time. I then again updated to the April update. No problems playing any movies.

The suspend does not work.

Enabled debugging, rebooted and here is the log: https://paste.osmc.tv/ifadecujus
I only use the supplied remote to control the Vero 4K.

1 Like

#11

@theoldfarter just when you posted the older thread (the one I forgot about) popped up. So I moved your post here.

1 Like

#12

Unfortunately the Logs are empty.
Could you please reboot, try to suspend and then upload logs again aither via MyOSMC or easier SSH grab-logs -A

0 Likes

#13

Perhaps I have not enabled some/all logs. Should I enable all logs? I find it easier to use MyOSMC

0 Likes

#14

Well seems you didn’t enable any :slight_smile:
For this case the Kodi.log would be the crucial one. so choose at least that one

0 Likes

#15

Here goes nothing :slight_smile:
https://paste.osmc.tv/ifabewirub

0 Likes

#16

Thanks, as expected the infamous “KEY_OK_UP” event (or better to say not working repeat filter) wakes the Vero. We have seen this before but we are not able to reliable reproduce it which makes troubleshooting tough.

2019-04-23 21:32:30.264 T:4045402848   DEBUG: LIRC: - NEW 160 0 KEY_OK linux-input-layer (KEY_OK)
2019-04-23 21:32:30.304 T:4065357824   DEBUG: HandleKey: 11 (0x0b, obc244) pressed, action is Select
2019-04-23 21:32:30.309 T:4065357824  NOTICE: Activating standby mode
2019-04-23 21:32:30.309 T:4065357824    INFO: Activating Vero standby mode
2019-04-23 21:32:30.309 T:4065357824    INFO: Toggle standby state is sleeping
2019-04-23 21:32:30.310 T:4065357824    INFO: CApplication::ToggleStandby -- Toggle TMDS clock to 0
2019-04-23 21:32:30.310 T:4065357824    INFO: CApplication::ToggleStandby -- Toggle LED brightness to 0
2019-04-23 21:32:30.310 T:4065357824    INFO: CApplication::ToggleStandby -- governor will now be powersave
2019-04-23 21:32:30.317 T:4065357824    INFO: CApplication::ToggleStandby -- HPD locking will now be hpd_lock1
2019-04-23 21:32:30.319 T:4065357824  NOTICE: CApplication::ToggleStandby -- checking for existence of /home/osmc/.kodi/userdata/standby.py
2019-04-23 21:32:30.320 T:4065357824   DEBUG: ------ Window Deinit (Custom_Overlay_Debug.xml) ------
2019-04-23 21:32:30.320 T:4065354464   DEBUG: CAnnouncementManager - Announcement: OnScreensaverActivated from xbmc
2019-04-23 21:32:30.321 T:4065354464   DEBUG: GOT ANNOUNCEMENT, type: 4, from xbmc, message OnScreensaverActivated
2019-04-23 21:32:30.322 T:4065357824   DEBUG: ------ Window Deinit () ------
2019-04-23 21:32:30.322 T:4065357824   DEBUG: ------ Window Deinit (DialogButtonMenu.xml) ------
2019-04-23 21:32:30.352 T:4065357824   DEBUG: ------ Window Init (Custom_Overlay_Debug.xml) ------
2019-04-23 21:32:30.361 T:4045402848   DEBUG: LIRC: - NEW 160 0 KEY_OK_UP linux-input-layer (KEY_OK_UP)
2019-04-23 21:32:30.375 T:4065357824   DEBUG: ------ Window Init () ------
2019-04-23 21:32:30.396 T:4065357824    INFO: Toggle standby state is waking
2019-04-23 21:32:30.397 T:4065357824    INFO: CApplication::ToggleStandby -- Toggle TMDS clock to 1
2019-04-23 21:32:30.514 T:4065357824    INFO: CApplication::ToggleStandby -- Toggle LED brightness to 1
2019-04-23 21:32:30.515 T:4065357824    INFO: CApplication::ToggleStandby -- governor will now be ondemand
2019-04-23 21:32:30.520 T:4065357824    INFO: CApplication::ToggleStandby -- HPD locking will now be hpd_lock0
2019-04-23 21:32:30.520 T:4065357824  NOTICE: CApplication::ToggleStandby -- checking for existence of /home/osmc/.kodi/userdata/wake.py
2019-04-23 21:32:30.521 T:4065357824   DEBUG: HandleKey: 0 (0x00, obc255) pressed, action is
0 Likes

#17

Thanks for the info. I will just keep an eye out for the fix, if one is found.

1 Like

#18

Yeah, think that is best. Alternatively I use the CEC event “TV off” to then put the Vero to Suspend. That works as there is no key pressed.

0 Likes

#19

I stay as far away as possible from using anything CEC as it can do unwanted changes to some of my components and get my Harmony Ultimate One remote out of sync and when that happens, that gets my wife “out of sync”, which is not good for me. lol

2 Likes

#20

It seems to be the same “key up” issue:

2019-04-23 20:05:54.254 T:4045402848   DEBUG: LIRC: - NEW 74 0 KEY_POWER linux-input-layer (KEY_POWER)
2019-04-23 20:05:54.269 T:4066140160   DEBUG: HandleKey: rewind (0xc4) pressed, action is suspend
2019-04-23 20:05:54.286 T:4066140160  NOTICE: Activating standby mode
2019-04-23 20:05:54.286 T:4066140160    INFO: Activating Vero standby mode
2019-04-23 20:05:54.286 T:4066140160    INFO: Toggle standby state is sleeping
2019-04-23 20:05:54.286 T:4066140160    INFO: CApplication::ToggleStandby -- Toggle TMDS clock to 0
2019-04-23 20:05:54.286 T:4066140160    INFO: CApplication::ToggleStandby -- Toggle LED brightness to 0
2019-04-23 20:05:54.286 T:4066140160    INFO: CApplication::ToggleStandby -- governor will now be powersave
2019-04-23 20:05:54.291 T:4066140160    INFO: CApplication::ToggleStandby -- HPD locking will now be hpd_lock1
2019-04-23 20:05:54.293 T:4066140160  NOTICE: CApplication::ToggleStandby -- checking for existence of /home/osmc/.kodi/userdata/standby.py
2019-04-23 20:05:54.294 T:4066140160   DEBUG: ------ Window Deinit () ------
2019-04-23 20:05:54.295 T:4066136800   DEBUG: CAnnouncementManager - Announcement: OnScreensaverActivated from xbmc
2019-04-23 20:05:54.295 T:4066140160   DEBUG: ------ Window Deinit (DialogNotification.xml) ------
2019-04-23 20:05:54.296 T:4066136800   DEBUG: GOT ANNOUNCEMENT, type: 4, from xbmc, message OnScreensaverActivated
2019-04-23 20:05:54.330 T:4066140160   DEBUG: ------ Window Init () ------
2019-04-23 20:05:54.515 T:4045402848   DEBUG: LIRC: - NEW 74 0 KEY_POWER_UP linux-input-layer (KEY_POWER_UP)
2019-04-23 20:05:54.544 T:4066140160    INFO: Toggle standby state is waking
2019-04-23 20:05:54.545 T:4066140160    INFO: CApplication::ToggleStandby -- Toggle TMDS clock to 1
2019-04-23 20:05:54.648 T:3608138464   DEBUG: Thread Timer 3608138464 terminating
2019-04-23 20:05:54.659 T:4066140160    INFO: CApplication::ToggleStandby -- Toggle LED brightness to 1
2019-04-23 20:05:54.660 T:4066140160    INFO: CApplication::ToggleStandby -- governor will now be ondemand
2019-04-23 20:05:54.665 T:4066140160    INFO: CApplication::ToggleStandby -- HPD locking will now be hpd_lock1
2019-04-23 20:05:54.665 T:4066140160  NOTICE: CApplication::ToggleStandby -- checking for existence of /home/osmc/.kodi/userdata/wake.py
2019-04-23 20:05:54.665 T:4066140160  NOTICE: CApplication::ToggleStandby -- script /home/osmc/.kodi/userdata/wake.py found

I’m using an IR remote only (programmable; based on the OSMC IR remote, with a few additional buttons like KEY_POWER).

Sebastian

0 Likes