Do AMOLED screen devices call onHide when screen turns off?

I have a timer that I start and stop with onShow and onHide respectively (main view).

This works fine in my fenix6 that never turns off the screen, but in my wife's Venu, when the screen turns off the timer stops running. I suspect the onHide is called when the screen turns off (default device behaviour due to Amoled).

Does anyone know if this is the case?

0 jim_m_58 over 5 years ago

onExitSleep()/onEnterSleep() are really the place to start/top your timer.

onShow()/onHide() may work, but why risk it?

0 André Zunido over 5 years ago in reply to jim_m_58

Hi jim_m_58,

I had no idea that those were even in the app view class
https://developer.garmin.com/connect-iq/api-docs/Toybox/WatchUi/View.html

I use the onHide because the user can navigate to another view and back again and if I only stop the timer when entering sleep I would assume that after a bit of back and forth the timer limit would throw an exception.

The timer should keep running while the view is not "exited". This application is of the "watch app" variety.

0 jim_m_58 over 5 years ago in reply to André Zunido

They are only for watch faces. You didn't mention an app type.

0 André Zunido over 5 years ago in reply to jim_m_58

jim_m_58, you're right I should've been more clear.

So it seems its not known if the screen turning off calls onHide, I tried to find any reference in the API and docs, but no luck.
When I get the chance I'll add some prints in a test build and see if its indeed being called when the screen turns off.

If this is the case I'll have to rethink my approach.

0 acrossthekyle over 4 years ago in reply to André Zunido

Hello! Did you ever find an answer to this? Thanks!

0 André Zunido over 4 years ago in reply to acrossthekyle

Hi, unfortunately no.

Somehow the onHide() event is not triggered when amoled screen turns off. I did empirical testing in a venu with logging.

0 _psx_ over 4 years ago in reply to André Zunido

in watch face I've never seen onHide call so simple remove it from code