MIP questions

With both AMOLED and MIP, when in low power bode, in both cases, onUpdate is only called once a minute, but a big difference is how much can be displayed during that time (to save battery on AMOLED devices).

In the early days, when a MIP device was in low power, it was typical that seconds weren't displayed, as they didn't update every second, but other than that, the watchface looked the same.

With onPlartialUpdate, that was called every second where you could update a small section of the screen every second - such as seconds, but has other restrictions, - onPartialUpdate could only run an avg of 30ms each time over a minute.

But other than that, the watch face could look exactly the same in low or high power.

Here's a simple example of using onPartialUpdate on an MIP device from when it was first introduced:

https://forums.garmin.com/developer/connect-iq/f/discussion/5156/1hz-watch-faces---q-a

Here's a example of a watch face for both NIP and AMOLED devices, where you can see how things differ with the two different displays

https://forums.garmin.com/developer/connect-iq/f/discussion/349473/simple-example-wf-that-shows-a-bunch-of-things

For me, I might have some common functions between onUpdate and onPartialUpdate, but wouldn't just use onUpdate when onPartialUpdate is called. In onPartialUpdate, it could be that something like seconds changes, but the rest of the screen doesn't need to be touched.

thanks for your reply. I have some measurements displayed on the hour and minute hand as well on the clock numbers, so if they are on screen I guess they need to be updated on change, all other stuff comes from a cached bitmap. I'll study the examples and work from there. Thanks again. 

Also. I have other MIP users not complaining, so maybe they do like the screen to go to the current low power mode. Is there any way to add a setting for MIP users on the Connect IQ settings thing? I am starting to wish settings could only be done on the device itself :D .

The second link sample has both on device and phone based app settings.

With onPartialUpdate, the 30ms limit could be a pain for analog watchfaces, with the highest time wii be at 12 and 6.  Watchface diagnosis will help you when looking into this.

Changes I make only seem to effect execution and graphics time. I guess the total time is counted as onPartialUpdate is shut down after a minute if I just make a blind call onUpdate from there. I'd like to know what Display Time stands for.

beva said:

I'd like to know what Display Time stands for.

I believe this is the time taken to actually update the display.

forums.garmin.com/.../analog-watchface-too-much-display-time-in-watchface-diagnostics

jim_m_58 said:

The display updates by row, so the more rows, the longer it takes.  clip regions get combined if you have more than one, so it's min row and max row for the combined.

Here's one of mine in the sim for the fr955 in low power mode:

Here, 10191 indicates about 10ms for the onPartialUpdate.

Ah oke, that's why it stays the same and 6 and 12 are hardest to get. At best/worst I could get it down by 50% and it needs to get down more, so I need to start to think this over :D .

Are you using clip regions in onPartialUpdate?  Looks like you're updating the whole screen