Ticket Created
over 5 years ago

WERETECH-8570

WERETECH-8569

in connectiq-sdk-win-3.1.7-2020-01-23-a3869d977 watchface diagnostics doesn't work

Hi

In new SDK watch face diagnostic no more works. All is good in previous version

Parents
  • That works with the first run in the sim, but not for subsequent runs.  After the first run, toggling lowPower on/off make no difference, and onPartialUpdate never gets called (only onUpdate(), but it's called every second even when it's set for lowPower) and therefore, no stats in watch face diagnostics..

Comment
  • That works with the first run in the sim, but not for subsequent runs.  After the first run, toggling lowPower on/off make no difference, and onPartialUpdate never gets called (only onUpdate(), but it's called every second even when it's set for lowPower) and therefore, no stats in watch face diagnostics..

Children
  • Agree!  for the 2nd+ runs, you have to turn off low power then turn it back on, and I see that works.  The menu isn't showing the proper state if you were in low power and did another run.

  • I see what you're talking about now, however I do get onPartialUpdate calls back if I toggle  Low Power Mode 2 times.

    Low Power Mode: LPM   High Power Mode: HPM

    Per your instructions:
    1. With the simulator closed, run the WF (it starts in HPM).
    2. toggle to LPM (now LPM).
    3. then run in the sim again without closing.

    Those steps result in a strange state.

    In the "strange" state, the Settings menu will show that LPM is enabled, however, the wf is actually in HPM. The Setting is incorrectly showing that LPM is enabled. In this state, If you un-check LPM, the wf tries to switch to HPM, but it is already in HPM so the wf power mode doesn't change. You have to toggle it LPM back on again to start getting onPartialUpdates again.

    So I think the actual bug is that the Settings toggle doesn't properly report the current power state when you re-run the WF when the sim is open and in LPM.

    That is the issue that I'm going to report.

    I don't think the fact that it is returning 0 when the sim starts in HPM is an issue.