I am maintaining the open-source Infocal watchface, and i am not able to get onPartialUpdate to work properly.
Even without any screen writes; GraphicsTime is showing 1,770,000 uS (1.7 seconds)!
Has anyone seen this before? What even is GraphicsTime when you are not doing any screen drawing 
This happens in Simulator, and on-Device (so at least they are consistent 
You can find my Watchface code here if you want to play around:
https://github.com/blueacorn/Infocal
Thanks in advance,
Jay :)
"Power budget is exceeded" only after a full minute, starting at 0 seconds. The average over a minute can't exceed 30ms
For displaying digital seconds, you define a clip region, which should…
You are making expensive calls to Application.Properties.getValue() in onPartialUpdate().
If you remove those calls, you will find that the watchface diags make more sense.
Instead of reading properties…
One thing of note, is that these Properties are defined as Settings - and they are at least available in-memory for getValue()
<setting propertyKey="@Properties.use_analog" title="@Strings.use_analog">
<setting propertyKey="@Properties.always_on_second" title="@Strings.always_on_second">
<settingConfig type="boolean" />
</setting>
<setting propertyKey="@Properties.always_on_heart" title="@Strings.always_on_heart">
<settingConfig type="boolean" />
</setting>
Am i reading settings wrong?
> If you mean the new code with Application.Properties, how were the partial updates running if the power budget was exceeded?
On the new (this) code. onPowerBudgetExceeded() takes 2-3 minutes to trigger, so you get to observe it working for a few minutes
Posted https://forums.garmin.com/developer/connect-iq/i/bug-reports/bug-watchface-onpartialupdate-reports-graphicstime-1-700-000---with-no-screen-updates - maybe a developer will chime in on Tuesday and tell me why all my assumptions are wrong
