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.
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
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).
Is anyone experiencing this with the OSMC remote; or are you all suspending using a universal remote?
Also happens with OSMC remote only
same for me, using both the supplied remote or the iphone kodi app.
Same here with Vero 4K+ and OSMC RF remote control. I will post debug logs when I get home after work today.
With both remotes the OSMC stock device as well as with an MSE remote.
When using the keyboard suspending works.
Yes, and I only use the supplied Vero 4K remote.
As promised: https://paste.osmc.tv/anopetiyit
Clean reboot, a few unsuccessful attempts at suspending, then a successful suspend. Hope that helps!
This should now be fixed.
I’d appreciate it if you could test this and provide feedback before we potentially release this as an update to other users. To test this update:
- Login via the command line
- Edit the file
- Add the following line:
deb http://apt.osmc.tv stretch-devel main
- Run the following commands to update:
sudo apt-get update && sudo apt-get dist-upgrade && reboot
- Your system should have have received the update.
Please see if the issue is resolved.
I also recommend you edit
/etc/apt/sources.list again and remove the line that you added after updating. This will return you to the normal update channel.
I installed the update and suspend mode is now working as expected.
Thank you, Sam!
Update installed, suspend now working properly, and as before.
Thanks very much Sam!
Great. Thanks for the feedback.
Sorry, I missed the updates to this thread…
I can confirm that it works for me now too.
Thanks a lot!
Glad to see how quickly this issue was addressed!!
Will there be an easier way to update, which does not involve the ssh and edit/adding of files? Perhaps the grandfather approved download via My OSMC
Yes this will be included in the next stable update
With Kodi 18 my Vero 4K+ wasn´t able to suspend anymore so I followed post #32 and updated my Vero.
Now after the update I´m finally able to suspend the device and the red LED turns on but after couple of minutes the LED turns off. If I turn the TV on I immediately see the Kodi home screen.
I´m using the default OSMC skin without any special addons.
I have only the standard remote and during my tests didn´t run the iOS Kodi Remote.
HDMI CEC isn´t active.
I created the log files:
after the restart I suspended the Vero. After powerup I created the logs (I deleted lines with information about my movies/series)