onPartialUpdate and Low Power Mode

Here's a whole thread about 1hz, with a number of tips. (and a simple sample watch face that shows much of what I'll say here)
https://forums.garmin.com/forum/developers/connect-iq/158133-?376929=
The Analog sample in the SDK is an analog WF that does 1hz.

Ok, a couple things.

In the sim, when you uncheck Low Power mode, onUpdate gets called every second instead of every minute. And onPartialUpdate doesn't get called.
This is what happens with a gesture, OnUpdate gets called every second for 10 seconds, then falls back to low power mode and onUpdate gets called every minute. onEnterSleep()/onExitSleep() is how a WF can tell if it's in low power mode or not

When in low power mode, onPartialUpdate gets called every second (if onUpdate hasn't been called that second). and this is where the power budget comes into play. If you exceed an avg of 30ms per call, onPartialUpdate is no longer called. You can see if the budget has been exceeded with a delegate in the WF.

For 1hz HR, you want to use Activity.Info.currentHeartRate, as getHeartRateHistory only updates every couple minutes. You may want to get get seconds working before you try to add hr.

Take a look at the thread and sample and ask if you have questions.

Thank you very much. I will spend some time digesting all of this and post back when I've resolved it or if I continue to have problems connecting the dots.

Jim,

Just wanted to thank you again and give you a quick update on my progress so you'd know that your assistance didn't fall on deaf ears. When I originally posted my question, I didn't realize I was exceeding the power budget. However, after I implemented your delegate code I could see that I was, in fact, exceeding it. So, the first thing I started doing to decrease usage was to start using setClip(). That helped. However, after trying every trick I could think of (including skipping a few seconds), I was still not able to stay within the budget. The fonts I was using to display the time of day and the seconds were custom fonts. I ended up compromising on the custom fonts for seconds. It appears that they take too long to load up from file. I ended up having to use Gfx.FONT_LARGE for the seconds. That keeps me below the budget.

My code is a mess after all of the experimenting. So, I have a lot of clean up and abstracting to do. But, at least it's usable and turned out close to exactly like what I wanted. I originally planned to include icons. But, I think everything is obvious without them and it's cleaner and allows for bigger fonts. The whole purpose of me doing this was because I couldn't find a watchface with large enough numbers and included all of the fields I wanted to see at a glance. I need reading glasses but, I don't wear them all of the time. There were a lot of watchfaces that were close, but not exactly like I wanted. I still think other people might benefit from it. So, I'll probably try to polish it up and get it on ConnectIQ.

I've attached a screenshot of the simulator.
community.garmin.com/.../1412951.jpg

Oh, one thing about onPartialUpdate. You should load things like custom fonts once (I do it in onLayout() or initialize()) to keep onPartialUpdate as minimal as possible. In your picture you should have a clip for just the seconds and another for just the HR, but the "cost" will be the rows from the top of the seconds to bottom of HR. You'd save a bit if you swapped the date and HR. Also, before you set the clip region for the HR, see if you need to update it. If it's not changed since it was last displayed, only do the seconds.

Oh wait. I don't think you're doing HR! I was thinking of another thread. But here's a couple of mine where I do 1hz and custom fonts for time Simple Big and Four Fields. In Four Fields, I use 1hz for HR too. The picture is a bit old as I user a custom font for icons there now. (a heart for HR that needs to be redrawn when the HR changes as it can be 2 or 3 digits)