Hi there,
Since a week or more I'm trying to get a macro working that starts the screensaver after 2 minutes when being on the launchers home screen. Sounds easy but in reality it's a miracle.
MD is running on one of this China Android TV boxes with Android 8.1. I'm using the ATV launcher. The system build in screensaver function doesnt work for some reason that's why I hoped MD can help.
This is what I setup. You can see I tried several constraint combination.
What I want:
# starts screensaver after 2 minutes when being on the launchers home screen
# not start screensaver when following apps are running in foreground: YouTube, Kodi, Netflix and so on
Momentary behavior:
# being in the home screen once and launching those mentioned apps after that, triggers the screensaver even when a movie or video is running. After 1 or 2 times hitting the back button when the screen saver is active I can then watch the movie without interruption
My guess is that the OS delays or fails to give the foreground/background state to MD.
MD is running in SuperUser mode.
Maybe one of you have some ideas what I can try.
Since a week or more I'm trying to get a macro working that starts the screensaver after 2 minutes when being on the launchers home screen. Sounds easy but in reality it's a miracle.
MD is running on one of this China Android TV boxes with Android 8.1. I'm using the ATV launcher. The system build in screensaver function doesnt work for some reason that's why I hoped MD can help.
This is what I setup. You can see I tried several constraint combination.
What I want:
# starts screensaver after 2 minutes when being on the launchers home screen
# not start screensaver when following apps are running in foreground: YouTube, Kodi, Netflix and so on
Momentary behavior:
# being in the home screen once and launching those mentioned apps after that, triggers the screensaver even when a movie or video is running. After 1 or 2 times hitting the back button when the screen saver is active I can then watch the movie without interruption
My guess is that the OS delays or fails to give the foreground/background state to MD.
MD is running in SuperUser mode.
Maybe one of you have some ideas what I can try.