Is this GPS difference within the norm?

Completed a run today and also recorded it using the Strava app on my Android phone. Never really been too bothered about pace/GPS but today the pace was usually down at by 1-2min/mile and the F5 recorded 3.2 mile, when my phone recorded 3.4 mile. Resulting average pace on the F5 8.33/m, but 8.13 on the Android.

Is this within the threshold of acceptable for a wearable compared to a watch which sports a larger antennae?


Thanks,
  • me too is giving a lot of GPS problems, like track and step! Until a few weeks ago there were no such problems, so I just hope it's a software problem ... :mad:
  • To me 6% drift is 'good enough', but that might vary for each person.
    Keep in mind that the mobile might not be entirely correct either and that the actual distance might be 3.3.
    The only way to find out is to compare the tracks side by side.

    I get spikes in GPS pace only when I run around large buildings or under bridges where the watch loses GPS signal.
  • response from Garmin regarding the metal casing being a potential cause..


    "I believe I have seen similar comments on forums, stating the bezel is affecting the accuracy, however this is unlikely, as the bezel itself, serves a purpose of enhanced antenna, so the result should be quite the opposite.

    Once you have made another run, please provide the one from the Vivoactive to compare with.

    Thank you for your feedback.

    Kind regards,"

    I would really need to do some more runs with both 1 second and smart recording, using Strava on my phone as well. Not fully convinced there's an issue yet. Appears that on the F5, it's the start of the run that gets affected the most, so maybe (even though the gps goes green quickly), it needs a little more time to get ready.
  • A good way is to compare tracks from phone Strava and watch garmin connect on http://www.mygpsfiles.com/app/
    Download the tracks on computer and drag & drop to the left upper frame and you can compare several tracks with map / satellite overlay.
  • maybe (even though the gps goes green quickly), it needs a little more time to get ready.

    I usually wait until my pace data field shows --:--.
    It's just few more seconds but it does miracles on the chart.
  • tried again after a factory reset and setting to 1 second recording. Pace was blank to begin with. Results much better in general. Pace was off again at the beginning (slower by 2 min/mile) but after around 1/4 mile it was much more consistent. In fact the overall average between android and F5 was exactly the same