So what you guys are doing regarding GPS/ Pace?

Hi,

After almost 5 weeks with the Fenix5 and seeing constant comments regarding GPS accuracy and pace I was wondering what you all doing about it? For me, the pace is the issue, as the overall GPS distance is good or comparable to what i got on the 735XT, however the pace is not usable at all, too jumpy, too inaccurate!

So what you guys are doing:
* using footpod - i tried once, but saw some funky avg. pace behavior, not really consistent with the pace i was receiving from the pod.
* replacing the Fenix 5 with another one? - Has somebody seen an improvement with a replacement unit?
* CIQ data field for smoothing pace? if works, can i get some suggestions?
* wait for any firmware improvement?
* other? please share...

Welcome all suggestions, as I'm nearing my return window and the pace is really an issue for me? Thanks

0 MalcolmLavery over 8 years ago

Im just pacing races and just hoping for the best :)

0 scotthunter2 over 8 years ago

I have also experienced issues with pace inaccuracy with the Fenix 5. I would like to return the product to the store where I brought it as it's no use for running. I can't exchange it for any other watch as the store only stocks Fenix watches.

If I had brought it online it would be easy as the Distance Selling Rules apply.

I would like to know what my consumer rights are. I brought it from a shop in the UK but I know the shop will be reluctant to accept my return as it's been used and I will have difficult proving that it's defective.

Does the Sale of Goods Act apply in this instance and how do I go about doing this? If they refuse, can I complain to the Retail Ombudsman?

Would appreciate some advice.

0 meste7 over 8 years ago

I use DozenRun or any other data field that can average the pace for anything between 3-30sec in this case. And it works very well to se if I need to go faster or slower.

0 Former Member over 8 years ago

I use lap pace and it works very well. Consistently steady and no jumps in pace.

0 F3b Software (Brian) over 8 years ago

I use lap pace and it works very well. Consistently steady and no jumps in pace.

I have the F3 and i use three: DozenRun (6 sec), a 3 Minute auto alert set to Pace and i have auto lap set for every 0.5 miles. This way i'm getting feedback, with or without looking at my watch.

0 FryeX over 8 years ago

Whenever I care about the pace I have used foot pod. Since Polar RS800cx through all the units up until current 5X from Garmin. Never issues with pacing.

0 Crispin_Ellisdon over 8 years ago

For those lucky enough to just be able to throw money at a problem to make it go away, it seems the Stryde foot pod is the best solution to getting reliable instant pace, closely followed by a normal foot pod. Meanwhile I'm actually not using the foot pod on either my Fenix 5 or Fenix 3 as I gather data as solid evidence that there's something that needs tweaking on the Fenix 5 to get the native instant pace working at least on par with the Fenix 3. But if I'm doing a race then the foot pod goes straight back on.

0 Former Member over 8 years ago

I have returned my first F5 after 2 weeks. I did 5 runs with it, every run had erratic pace recordings. It also did reboots during the runs :/

I have notified the Garmin Support about my issues, they suggested to send the watch in. But what could they have done with it to get it to work?
A member in the forum suggested to return the watch and not to wait for patches. So I returned it.

Today my new F5 arrived. I did a run. The pace in the data field was steady during the run. The pace graph in GC isn't erratic anymore.
Seems like I really had a watch with faulty hardware.

0 Former Member over 8 years ago

@grobo

Could you post public links to the activity? I'd like to see an example of the old watch's pace vs the new watch, preferably on the same course, if possible.

0 Former Member over 8 years ago

@grobo

Could you post public links to the activity? I'd like to see an example of the old watch's pace vs the new watch, preferably on the same course, if possible.

Sorry DJ,

I haven't run the same track yet.

But here are two examples:

Run with first watch:
- the pace data field on the watch was jumping every second from low pace to high pace, for example from 6:00 min/km to 24:00 min/km.
- the watch rebooted during the run.
- the navigation pushed pop-ups to the screen that I was off-course, then back on-course, then off-course again - every dozen seconds. really annoying.
- a 16 km run was shown as 14 km in GC
--> all these errors are the result of a faulty gps I assume
https://connect.garmin.com/modern/activity/1693686549

Run with the new watch:
- the pace data field isn't "jumpy" anymore. for example it moves from 6:00 min/km to 6:05 min/km and back 6:00 min/km after a few seconds. the drops in the pace graph are real - I was too tired today ^^
- the navigation is on point
- had my Suunto Ambit 3 with me. both watches recorded the same pace and distance - for me that's proof enough :)
https://connect.garmin.com/modern/activity/1706771070