worst accuracy ever

  • Its reported that GLONASS make GPS signal worse than GPS alone. Try using only GPS on next activity and see if it improves.
  • Former Member
    0 Former Member over 8 years ago
    1) Experiment with GPS only, GLONASS only, then GPS + GLONASS. All locations are not equal, in my experience, sometimes having both turned gives less accurate results.

    2) Check whether your 'lock on roads' is set to on or off.

    3) Check your recording settings. Smart, Ultratrac, 1 sec intervals. Again, all are not equal.
  • https://connect.garmin.com/modern/activity/1743296537?share_unique_id=29


    It's weird that from 3:52 to 13:30 it was recording data but it just had you in one location. I had that happen once on my old 620. I wonder if your device is defective or if somehow the .fit file is corrupted, given that it was recording everything else. Other than that your track looks good.
  • Here's a side by side comparison of the same run

    My Girlfriends 5s on my left wrist:
    https://connect.garmin.com/modern/activity/1744085726

    My 5x on my right wrist:
    https://connect.garmin.com/modern/activity/1744086082

    Nearly two miles missing from the 5x map recording and 30+ seconds difference in recorded pace
  • Here's a side by side comparison of the same run

    My Girlfriends 5s on my left wrist:
    https://connect.garmin.com/modern/activity/1744085726

    My 5x on my right wrist:
    https://connect.garmin.com/modern/activity/1744086082

    Nearly two miles missing from the 5x map recording and 30+ seconds difference in recorded pace


    that's a weird one. my garmin connect (german user) lists the 5x track as 17.75 km and the 5s track as 17.95km - nothing seems to be missing in the summary, the pace does look comparable here while the comparison doesn't sound too good to me such a difference may certainly happen occassionally when using two gps watches.

    but taking a closer look: on the map the east of lake calhoun there is indeed a piece of the track missing. screenshots:

    fenix 5x:
    https://abload.de/img/fenix5xzmu8e.png
    fenix 5s:
    https://abload.de/img/fenix5stsu99.png

    i downloaded the .tcx files and dragged them into mygpsfiles for direct comparison: the 5x tracks does miss 2 km + around 12 minutes there.
    there is another thing which is notable: the fenix 5x recorded 3777 points vs 994 recorded points from the 5s.

    were both watches recording the data every second?
    if yes, it looks like the 5x doesnt smooth data at all and the graphs will look noisy


    -----------
    i am too a fenix5x owner since last week and right now i am too not happy with the gps accuracy. I did a slow run today with someone wearing a fenix 3hr: same track, mine was measured 6.66km against 6.94 km on the fenix 3hr.
    An observation probably connected to the gps problem but way more annoying then to look at the recorded track accuracy after an activity: the instant pace is disastrous and not usable at all right now.
    my first guess is that they missed to implement some kind of smoothing algorithm to get rid of the noise coming from the gps.
    but of course, i have to do more testing.

    however, the accuracy problem on the fenix 5 series is kind of annoying since garmin seems to make the same mistakes over and over again.
    one would think that garmin learned their lessons and improved their products/software over the many forerunner and fenix releases, which, at least at the beginning of the product cycle, often (mostly?!) had similar issues with gps.
    btw. anyone knows if the gps problems got finally fixed on the fenix 3? as a former epix owner i didn't follow the discussion there entirely as we were left alone with our own problems...
  • Just finished another slow and short run. i did the same track as yesterday. yesterday: 6.66 km today: 7.03 km. data is recorded at every second.

    [irony]feels good coming home with a couple of new records in a rather slow run: 1 km in 2:58.90 min/km, 1 mile 6:07.99, fastest 5 km 30:44.8 [/irony]
    - all records are impossible timings for me right now.

    instant pace during the run is way off from the summary data shown at garmin connect again. best pace there was 5:10 minutes/km (way above 3 min/km from the record!) which could be possible. the pace graph show some gaps - which are probably related to the gps.
    it is not only the jittering of the instant pace which is annoying but the instant pace seems to be strongly biased above. my watch is set to the english language but all measures are changed manually to a metric system - the biased values i saw during the run let me wonder if the internal calculation of the instant pace is done per miles instead of per km.

    on the positive site: at least the gps-accuracy is well within its proclaimed specification of <1000 m (or was it 10 m?! can't be possible!) - see the attached picture. the pink dotted street was the street i was running on. i have never encountered such a bad precision from any garmin devices until now.

    as the watch is still new for me, I still have to investigate more, but it doesnt look too good.

    i wonder why there is only a topic in the fenix 5/5s forum (and in the forerunner 935 forum, telling us how good their gps is) and not here to collect experiences with this issue. it is way more important than some latent screen flickering.
  • i wonder why there is only a topic in the fenix 5/5s forum (and in the forerunner 935 forum, telling us how good their gps is) and not here to collect experiences with this issue. it is way more important than some latent screen flickering.


    That image you posted is pretty awful when it comes to mapping your location on the trail! Was it thick tree cover?

    The reason why there is only a topic on the fenix 5/5S forum is because shortly after the release of the fenix 5 series, people on the forums consolidated the discussions into a single thread because people were having the same experiences of poor quality GPS tracking on all three of the watches. There are plenty of posts about the 5X in that thread!
  • There is a big problem under trees and between walls.
    https://www.strava.com/activities/1003300388/segments/24595086322
    Look at the beginning of the segment. It's a straight stair 3meters wide. The walls are about 2,5m tall.
    The other day I ran in a less wide road with higher walls, and the signal was completely lost for a lot of minutes.
    This was never happened with Fenix 3 and vivoactive-hr
  • Former Member
    0 Former Member over 8 years ago
    There is a big problem under trees and between walls.


    Can confirm this. On my runs done on open ground, my gps accuracy is pretty good. However, on a 32k mountain hike involving some tree-cover and cliff-faces, the accuracy was less than desireable to say the least. My 5 year old Polar RX delivered better results.