Yeah whatever Garmin is saying about platform commonality the Stryd issue only occurs with the fenix 5, not the 5x or the 935. Makes you wonder what else could be different I guess ;)
Can I just say in defence of the F5 and Stryd that having upgraded the watch to FW2.90, forgetting and then re-pairing the device as a footpod everything has been perfect. I don't use the Stryd app as the data field does the job. All my metrics are being pulled into Garmin Connect, I get perfect pace and have had no dropouts. I agree that the gps accuracy and subsequent pace on the watch is terrible but the Stryd footpod has made a massive positive difference. Expensive fix but with no option to return the unit, probably cheaper than moving the unit on and buying a 935
You have no dropouts from Stryd on a fenix 5, not a 5x? If so would you mind posting a link to a GC activity showing that as you are the only one, including Stryd employees to have that experience.
I tried removing and repairing Stryd and the issue remained for me.
Very interested to see your data if it is on a fenix 5.
Sure. This is a sample activity where I can't see any dropouts? I did have to stop momentarily to cross a road but other than that all looks good to me - unless of course I'm missing something?
I had a run this morning with the Fenix 5 on one arm and 2 x Tomtom watches on the other (yes, 2 x Tomtom watches)..
The Garmin device got GPS lock within seconds. The Tomtom devices took a bit longer, which possibly gave the Garmin device a bit more time to "soak" before I started the run. The GPS plot is the best I have seen from a Garmin device. It had a slight wiggle, but it actually tracked my run very well. It was at least as good as the Tomtom units. It was 50 mtrs out over 5.5 km, when compared to the Tomtom units. Which brand was correct? No idea, but it is close enough that I don't really care. It has consistently returned accurate distance, despite some interesting looking GPS tracks.
I am not certain why it was so much better today. It may have been the latest firmware, a slightly longer soak before the run, or a number of other reasons. Regardless, I was very happy with the result. GPS is tough on this route, as there are a number of trees hanging over the path, lots of inclines etc. The Fenix 5 nailed it. For me, the GPS issue is a non-event. I understand it is still an issue for others, but for me this is a very acceptable result.
Sure. This is a sample activity where I can't see any dropouts? I did have to stop momentarily to cross a road but other than that all looks good to me - unless of course I'm missing something?
Yeah that is clean with no dropouts. Wonder what is different in your fenix 5 compared to others? When and where did you get it, if you don't mind me asking? Now I am wondering if this is hardware related and not software. Also when did you get your Stryd (maybe something changed on their side too)?
Phew! That's a relief, thought I was heading for another Fenix 3 nightmare again only solved with the purchase of a 735!
Okay, I got the silver Fenix 5 with the granite strap from Amazon, released after the black models. Anything in that possibly? Also I bought my Stryd off eBay as an ex demonstration model so unsure how old it is. The first time I used these in combo I did suffer from dropouts galore and ended up with a short marathon (gutted as it was a big PB too but won't show up on my watch). It's only since I went from the beta 2.72 to 2.9, reinstalled and re-paired things that it all works. Thanks for the confirmation that all is well with my watch
No worries, glad it is working. Might be something to do with the watch hardware, but tough to tell.
In the case of lost data from the race, you may know this already, but you can download the power data and metrics from the Stryd directly in to Stryd Power Center so all the Stryd data should be available and will not have any dropouts.
i tried to compare my new Fenix5 to my old V800. Fenix set to smart recording GPS only, V800 set to high acurracy. In flow polar distance is 14,59km and i GC distance is 14,52 km which doesn't seems to be bad result, what made me a bit sad was current pace (I expected this) some times way off. Today will try 30 minutes regeneration, so I'll try 1 sec recording if there are some difference
Overall distance not too bad indeed but the variance in the lap times is consistent with what I've seen and horrible if you're trying to pace yourself. A runner's watch this is NOT ;-)
