So I went for my usual 10 mile run yesterday with the new F5.
Here is the route:
https://www.strava.com/activities/955234611
https://connect.garmin.com/modern/activity/1694808792
In short, I was really disappointed with the Fenix 5. I was hoping to use it as a replacement for my old Forerunner 630 and HRM-Run strap, but after yesterday, I don't think I will be using the Fenix again for running.
Pace was all over the place - I'm not talking about real time pace, either, but average lap pace. Even mid way though a mile, the lap pace was very erratic - one minute I'd be doing a 7:30 min/miles, the next minute I'd be doing 8:30 min/miles, even though I was keeping a steady pace.
It was a route I have done many times. With my old Forerunner 630, I knew exactly where I would be - next to my house - when the 10th mile registered. With the Fenix, I had to run about 200m down the road past my house to register the 10th mile. The Fenix had told me that my average pace for the run was 8:30 min/mile, but to my surprise, after I had uploaded the run to Strava, I was told I had averaged 8:13 min/mile. Then I looked at the GPS track and noticed that the last 2 miles were all over the place. I live in a small city and there are a few relatively tall buildings near where I live, but it's not exactly NYC. I've never had issues before when running though the city centre, unless I had started a run without getting a GPS lock.
Also, the heart rate data from the optical sensor is completely meaningless, saying I averaged 177bpm and maxing on 200bpm, even though it was a recovery run! Earlier that day, during a cross country duathlon race, my average HR had been 133bpm.
I want to return the Fenix 5 now as it's useless for running. I expected better from Garmin since it's supposed to be their flagship money-no-object multi-sport watch.
I'm now seriously thinking about going down the Sale of Goods Act route to get a refund as the watch is not fit for purpose in consideration of the price of the watch and its stated claims. I think the issues with the watch are inherent and down to hardware design - something that isn't going to be fixed with a firmware update.
I think my experience is similar to others from reading the other posts on this board?