So, I began preparing for my first half marathon. It was a delight running with a watch. I was surprised by the accuracy of the Ambit 3. It recorded my runs very accurate. I could rely on the navigation. The stats were always complete after a run and identical to the stats I recorded with some apps on the smartphone.
When I heard about the F5, I was hyped. The price scared me, but all the functions and the look of this watch allured me. Garmin wasn't new to me. I hike a lot with my etrex. That thing never let me down - NEVER!! And I was in places, I would have never come out of alive without that little helper. So two weeks ago, I decided to join the Fenix Club.
Let's get to the ugly part:
I have done 5 runs with the F5 now. I started with FW Version 2.90. The 2.95 beta hasn't done any improvement regarding my issues with the watch.
In all of my 5 runs the behaviour of the watch made me disappointed. The disappointment turned into anger fast, which made me run faster, but that is not the point.
Here we go:
- The pace was jumping from 5:00 min/km to 30:00 min/km every second. Every app showed different behaviour in pace. The result is an erratic pace chart in Garmin Connect.
- When navigating, the watch tells me every 20 seconds, that I'm off-course, but I never left the course. 5 seconds later it tells me, that I'm on-course again. It's permanently pushing this notification to the display. Makes navigation painful.
- Today, it rebooted twice during a 16km run. At least I was able to resume the run where the watch had stopped recording. So i got that going for me, which is nice.
- Garmin Connect showed the 16km run as a 14km run. Because of that, the pace was very slow. But after the sync to Strava, Strava showed the correct distance and pace.
Please don't tell me to get a foot pod or a stopwatch. How come, that watches at the half/third of the price of the F5 do everything they are supposed to do. If the F5 isn't able to show me my current pace, what it is good for then? Look fancy?
Please don't tell me, that you guys were living with these bugs for the last couple of years (F3/F2) and made the best with a bad bargain.
Do I have to wait for Garmin to fix these bugs with FW Updates?
I know I'm not the only one with these kind of problems, so I don't think, that I have a faulty hardware.
Just tell me, that it will get better.
Thanks for reading.