This is a pretty serious and easily replicated bug. This happens to be on the Edge 1030 with the lastest firmware. The bug has been around for a couple of years at least.
Start an activity. Then hit STOP. Everything is still working fine. Elapsed Time is incrementing as it should, Moving Time is not incrementing. Great. At this point, Exhibit A (while STOPPED), I'm 25 seconds into the Activity, watching the native fields (bottom row). And my own CIQ metrics. SysE is the CIQ elapsed time. And CalcE is my own elapsed time, which is simply current time minus start time. SysE and CalcE should match, but no biggie.
Here is the BUG. While stopped, hit the lap button. This is not an unusual practice. Say auto-pause is off but you don't want to count a longer stop. You hit stop. Then before starting again, you hit LAP. then hit START and off you go.
Anyway, if you hit LAP while STOPPED - guess what.... the SYSTEM Elapsed Time goes all wonky. In this case, it started back almost at ZERO. What it seems to do is revert back to the time when you hit STOP. Which of course is wrong. Elapsed Time is a non-stop running clock since the start of the Activity. And if you didn't happen to hit LAP, Elapsed Time would have done the right thing and counted the STOPPED time.
So, for now, I resort to my own internal Elapsed Time function. But then there is the issue of crossing Time Zones and Standard/Daylight time shifts.
Anyway - not sure anyone here has contacts with Garmin - since the built-in native elapsed time also reflects this bug - it isn't really a CIQ issue. But does impact all of us writing CIQ apps.
