Elapsed Time Weirdness - SYSTEM BUG

DAMN - this isn't a CIQ thing, but could impact you. After a couple hours of attempting to debug a weird error in my data field, I finally found this is a Garmin system error related to Elapsed Time.

If you START an activity with autopause on. Elapsed Time does the right thing and counts the time since START.

If you come to a stop sign and auto-pause engages at, say, 5:32 into the activity, ELAPSED TIME continues to count as it should.

You sit there, stopped, for, say, 2 minutes... the ELAPSED time will say 7:32, as it should.

But then if you hit LAP, the ELAPSED TIME will revert back to 5:32 and then begin counting up from there again.

So weird. I don't recall that happening last week. I have not reported this - not sure how to do that other than call customer support tomorrow.

I've tested this on my Garmin Edge 520 and 820.

Former Member over 7 years ago

I have reported this issue to the Edge team. Reporting it here is a more direct line for this type of issue, so you shouldn't need to talk to support.

DaveBrillhart over 7 years ago

Thank you Brian! Let me report another system bug that, well, really bugs me.

Using an EDGE 820, there is a BATTERY SAVE mode. It blanks the screen with a 3 second count down.

When following a ROUTE, this count down is delayed, such that each second on the on-screen 3 second count down takes like 6-8 seconds.

This is the easy way to replicate the bug. But this also impacts CIQ data fields.... in that compute() which is supposed to run every second, only runs every 6 to 8 seconds. Again, this occurs when following a turn-by-turn route.

Thanks!!

Former Member over 7 years ago

I forwarded this to the device team. They wanted to know what software version your Edge 820 was running when you saw this.

DaveBrillhart over 7 years ago

I forwarded this to the device team. They wanted to know what software version your Edge 820 was running when you saw this.

I'm running 8.40 - I always keep it up to date. I just tried to replicate the bug and it seems like it is resolved, possibly in the last firmware update or two. I have a ride Saturday with a course, so I'll know Saturday for sure. Thanks!

DaveBrillhart over 7 years ago

I confirmed the bug is still present in v8.40. On today's ride. I rode with a guy with a Garmin Edge 1000. Same error! I will test on my 520 tomorrow.

So it isn't my device, or even my model (820). the common factor in these bugs is that the route is generated from a RideWithGPS TCX file, that I drop into the Garmin's NewFile directory. Upon restart, the Garmin turns this into a course. I select Training, Race an Activity, Saved Activities, and then pick the course. I can see the map and it displays where I am, but quickly gets into a weird state where is doesn't track me or show the turns.

The real bummer is that the compute() method is only called about every 14 seconds!! And it isn't just CIQ... For example, the Battery Save mode that counts down 3 seconds with an on screen 3...2....1. Takes about 30 seconds or more to count down before the screen is blank.

I can send my TCX file to you or your contact in Garmin engineering. Or even FedEx my Garmin 820 for a few days, if they can't reproduce it. But I bet they can since others are seeing this too.

Thanks!