Which Garmin does not have the sony GPS chip issue accuracy impacting some Garmin?
Thanks !
Regards,
Alex
Which Garmin does not have the sony GPS chip issue accuracy impacting some Garmin?
Thanks !
Regards,
Alex
That was a specific issue that happened at the start of 2021. Garmin didn't just post that in reply to you, don't blatantly lie.
I use my Fenix 6 for running all the time, hundreds of runs recorded on it and never had any significant GPS issues even once. Distance is always consistent (within +/- 0.5% most days, or maybe 1% on the…
Nonsense. I’ve got a Fenix 6 Sapphire that’s a couple of weeks old now and it’s spot on. Why are you posting utter nonsense?
Yes it is !
So, Just tell me why Forerunner 245 has better result then ? Why Forerunner 220 has better result ? Why Strava has better result ?!
Yes it is
I use only the GPS even O have tried GPS + Glonass and GPS + Galileo. No change
And here comes the fun part: the Fenix, Garmin Connect and Strava all use the same source set of recorded GPS coordinates along your route.
It seems that the calculation of the distance is implemented differently across the systems. (Yeah, fun part, because if this is what you are complaining about, then it has nothing to do with GPS quality)
> settings/system/data recording
Was set to "Intelligent" on my watch, changed it to "every second". Maybe it is even better now ;) Thx
Do understand me wrong !! You’re not stupid at all ! Tell me wich one is the worst one
Forerunner 220 :
semi-marathon 21,36 km
marathon : 42,60 km
my usual run : 11,20 - 11,10 or 11,00 depending but most of the time 11,00 +-
usuel Run : 11 km
Forerunner 220 : see above
Forerunner 245 : 11,01 km
Strava : 11,11 km
Fenix : 10,49 km !! So what the worst you thing ??
Coachsportif_BE: Actually you seem to be pretty mad about your Fenix. So why don't you return it? I mean: If it is so bad, there is no reason to keep it. For others, it seems to work ok so don't expect *everybody* to return the watch. I guess nobody here can answer your questions...
So as bw said above it's not the GPS chip or tracking that's the problem it's actually the algorithm used to calculate the distance along those points. Here's a random thought, maybe the Fenix is correct and all the others over compensate? Or as UliHe42 has just posted, if it's so bad send it back heck you can send it to me if you want and i'll use it!
I checked my runs: The one with the pictures above had a length of 16.4 km according to JGPSTrackEdit. Within GarminConnect, it says 16.23 km. So GarminConnect uses a different algorithm. Markw50 is probably right