And for future reference: this fixes #912

Can this be merged?

Need this functionality as well. Any update on this?

I had done a pull request, don’t think it is merged yet
…
On Tue, Feb 12, 2019 at 3:32 PM RHerasymenko @.***> wrote: Need this functionality as well. Any update on this? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#919 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AGPPbsJ2-MNAxTJe9Qb1HtMuQ8vxy8gEks5vMyTvgaJpZM4YfCB_ .

I know, it's more a question to maintainers ...

@fornwall any chance we can move on this?

@brubakerjeff Sorry for the delay here.

The main argument against merging this PR was that the current behaviour (to avoid drawing the background if not necessary) is actually intended, to avoid overdraw (https://www.youtube.com/watch?v=T52v50r-JfE) for performance and battery efficiency.

So AFAIK this change would be a workaround for broken graphics behaviour/driver for android on raspberry pi. Or do we believe the current code to be wrong?

With that said, I haven't actually measured if the overdraw avoidance actually improves efficiency in any meaningful way, I just looked at the android developer option and visually determined that overdraw was avoided.

@brubakerjeff Can you re-check with the latest available Android version/build for the device and see if the system behaviour has improved (is this still necessary)?

Thank you. I will add it to my list to try to with the new version. No worries for backlog, glad there was follow through. I wish we could get a google android things developer (does anyone know any) on here to be more authoritative for the "workaround" statement. Understandably if this is perceived as a workaround a fix at the root is perceived as more advantageous.

Ping, still needed?

Ping 2, is this still needed?