Pace During Workout is Incorrect

Shiva we do have an investigation ongoing but the more information we have, the better.  If you can check your email, I requested some additional information from you on November 10th but have yet to receive a reply.  Sending this requested information may help us to find the root cause a bit faster.

5495831, 6949985, runner42, and Pierangelo75 it looks like I am waiting on email replies from each of you as well please.

Just waned to follow up with the best workarounds I know ...

First, people have reported mixed success in using foot pods (either Garmin or Stryd) to get better instantaneous pace.  It depends on calibration being correct and isn't terribly accurate.  But some (myself included) have found it better than what we're currently getting from GPS.  If you want to try this, make sure you do a few runs with auto-calibrate turned on.  And ensure you activate your footpod to provide speed data in all settings (by default, it will only provide speed data indoors .. when GPS is off).

You can also use lap pace, including in structured workout context.  After you start your workout, scroll to a screen that has lap pace.  You can't see both the lap pace and the structured workout screen at the same time, but the workout will continue.  If you use headphones, you can get prompts at the start of each workout interval.

Both of the above are far from ideal, and I still expect Garmin to fix the bug introduced in the latest release.  However, it's worth a try if you are struggling with structured workouts.

Would it be enough to send you the activities? The problem is very easy to reproduce and I am not so eager to perform all 8 points of the report.

Are you using some kind of issue tracker like Jira? That would have a lot of advantages. 

Do you know when the next release will come?

Garmin-Kevin

runner42

Just the activities is not enough.  We are seeing some differences in the disruptions reported, so we want to be sure to treat them as like/different issue according to the details provided.  Grouping separate issues together as one single issue can significantly delay finding a root cause and developing a fix.

Yes, we have tracking software that we use internally.  This is where I get the questions that I email to users when they report a disruption.  These questions/requests come straight from the Engineering and Developer teams.

At this time, I do not have any information on when the next sw update will be released.  We hope to have something soon though.  This is why I am trying to get as much data from you all as soon as possible in hopes that we can investigate this thoroughly before the next release or at least the one following the next release.

I have just bought the 255s I am sick of this pace bug it's making workouts annoying and messing up the training and recovery metrics. 

I will miss the maps, hotkey for Garmin Pay and longer battery but the most important thing on a running watch is GPS it's the core feature so I am looking forward to more accurate data and reliable instant pace. 

9386496 said:

I have just bought the 255s I am sick of this pace bug it's making workouts annoying and messing up the training and recovery metrics. 

I hate to police anyone else's spending habits but I think this is the worst possible way to incentivize Garmin to fix problems. But I see it so often: "My current Garmin has a show stopper bug. Welp, time to buy a different Garmin!"

Same as when people have connectivity issues with their earbuds (whether it's Garmin's fault or the earbuds' fault), I see people saying "oh well, time to buy more expensive earbuds".

That may be a (somewhat) practical solution to a problem, but seems like it will only lead to more problems in the future. I wish there was a way for consumers to collectively put our feet down. (Yes, I know the market isn't granular enough, etc.)

EDIT: I'm no better as I continue to buy Garmin products as well...

Have your testing/QA teams reproduced the issue? Or are you relying on only user reports? I assumed it was happening to everyone on this firmware. It is for me, and it's the most active thread since 7.11 was rolled out.

Greg we have some reports from users, but the symptoms are so different that many of these need to be submitted separately, as different issues.  For instance, "Pace is too slow during sprint intervals" and "Pace jumps up and down at the beginning of an activity then stabilizes" are different issues and cannot both be submitted under a report stating "Inaccurate GPS during activities".

This is precisely why I am trying to get more information from users like 5495831, 6949985, runner42, and Pierangelo75.  If you can answer my questions in the Top Replies section, I would be happy to gather this information from you as well.

To answer your question, we have been able to reproduce an issue where the average pace displayed for each lap during a run activity is being displayed as faster than the best pace for that same lap in the activity.  We have not been able to reproduce any other symptoms related to GPS at this point.  If the users reporting disruptions can submit the requested information to us, I am happy to continue working on these concerns.

I will add that, for fastest and most detailed assistance on concerns with features like GPS and Heart Rate, because the symptoms can be so broad, we encourage you to reach out to your local Garmin Product Support team directly.

Garmin Product Support