Missing temporal events after a disconnect

[osa1]

When phone and watch go out of range, after connecting again, it seems like the next temporal event is not getting fired, and the app also doesn't schedule new temporal events.

As a result, we see "next event time" shown as negative number (i.e. we should've done a request but didn't) and we never update the bg levels again.

The workaround is to switch to a widget and then back to the watch face, which schedules a temporal event again.

We should find out which callbacks are called after a re-connection and schedule a temporal event there.

[osa1]

I think this problem only occurs when a temporal event is missed because the watch was disconnected.

If the temporal even is not missed during a disconnect, then it's fired as expected after reconnecting, and the next temporal event is scheduled.

[osa1]

With acd1f33 I've added temporal event scheduling to per-minute and per-second updates, so we should always have a temporal event scheduled now.

However it will mess up the schedule for the next bg data (i.e. when we skip the next update to catch up with regular 5-min updates again). We should share and resuse this logic:

Dextrack/source/DextrackApp.mc

Lines 137 to 147 in 040a990

	if (diffSecs < 15) {
	// Give Dexcom some time to upload the next reading before
	// requesting again
	nextEventTime = now.add(FIVE_MINUTES).add(new Time.Duration(15 - diffSecs));
	} else if (diffSecs >= 120) {
	// Data more than a minute old. Wait 5-N minutes plus a few
	// seconds to catch recent readings again.
	nextEventTime = now.add(FIVE_MINUTES).add(new Time.Duration(300 - diffSecs + 15));
	} else {
	nextEventTime = now.add(FIVE_MINUTES);
	}