With the landing of https://code.launchpad.net/~raof/mir/1hz-rendering-always/+merge/217377 we now have the return of the bug which a "stale" frame of application render is seen on top of greeter
with the 1Hz policy, upon screen blank, lifecycle kicks in at around 3s so there's only around 3 frames drawn.
also volume key is laggy. b/c the toolkit interrupt service slows down to the same rate as well.
potential solution is to set the render rate to be as close to the "slowest connected display"
With the landing of https:/ /code.launchpad .net/~raof/ mir/1hz- rendering- always/ +merge/ 217377
we now have the return of the bug which a "stale" frame of application render is seen on top of greeter
with the 1Hz policy, upon screen blank, lifecycle kicks in at around 3s
so there's only around 3 frames drawn.
also volume key is laggy. b/c the toolkit interrupt service slows down to the same rate as well.
potential solution is to set the render rate to be as close to the "slowest connected display"