Screensaver not working after resuming from Standby


#1

It seems the screensaver is not working after resuming from Standby.

Here is how I tested:

  • power up the Vero 4K+
  • check screensaver status via json, which returns ‘false’ as expected
  • wait until the screensaver starts
  • check screensaver status via json, which returns ‘true’ as expected
  • press a button on the remote so the screensaver stops
  • check screensaver status via json, which returns ‘false’ as expected
  • using the Power menu set the Vero to Suspend
  • check screensaver status via json, which returns ‘true’ as expected
  • wake-up/resume OSMC by pressing a button on the remote
  • check screensaver status via json, which returns ‘true’ which is NOT expected
  • wait longer than the screensaver timeout
  • the screensaver does NOT start
  • check screensaver status via json, which returns ‘true’ which is NOT expected

After I use the Preview screensaver function in the Settings menu, the screensaver starts working as expected again.

Is anybody experiencing the same?

Thx.


Screensaver not kicking in
#2

Thanks. I’ll look in to this.


#3

Hi Sam,
Thx.
FYI: I cannot say when this problem got introduced as I only used started using the Suspend option on a daily basis about 5 days ago.
Regards, Carlos.


#4

Just to let you know I’m experiencing the same issue with my Vero 4K+.

Also screen dimming when playback is paused is not working either after resuming from suspend.

Thanks for checking this!


#5

This will be fixed in the next update (for v17).


#6

Hi,

Gave this a thorough test today and it should be resolved in today’s update.
@Carlosmc1: thanks for the JSON tip; I found that made it much easier to find out when things were (and weren’t) working correctly.

Cheers

Sam


#7

Hi Sam,

I installed the update and tested the Standby function, and can confirm this no longer breaks the screensaver.

Many thx!

Regards, Carlo.


#8

Thanks for confirming.


#9

I installed the update and tested the Standby function, and can confirm this no longer breaks the screensaver.

I can confirm. Screensaver working as expected now.

Thank!