fenix 7X Sapphire Solar - firmware 20.22 - Activity distance wrong

Hi, I'm back again to report this issue. It hasn't been resolved. Discrepancies between firmware versions continue to exist.

As such, the most accurate firmware version is 17.28. Its route is almost identical to the Google Map measurements. All tests are the same route.

Firmware Version: 17.28
Distance: 4.99 km
Steps: 5800
connect.garmin.com/.../18464288362
Additionals: None
Satellite setting is: Use default (Automatic Selection)

Firmware Version: 20.16
Distance: 4.54 km
Difference: 450 m
Steps: 5964
connect.garmin.com/.../18473859866
Additionals: None
Satellite setting is: Select Automatically (Dynamically selects the best one) mode)

Firmware Version: 20.22
Distance: 4.59km
Difference: 400m
Steps: 6038
connect.garmin.com/.../18512100007
Additional: Running Dynamics Pod
Satellite is: Use default (Automatic Selection)

Some observations:

  • The pace metrics fluctuate too much between 17.28 vs 20.22 and 20.16
  • Running Dynamics Pod shows no improvement
  • I set the stride length to 0.90m, multiplied by the steps, it should give me 5.3km to 5.4km, so it doesn't respect this parameter either.
  • I contacted , they asked for the activity log, but I didn't know how to activate it, and I haven't heard back.

I'm a little tired of being a beta tester.

  • Update April 28, 2025:

    Our engineers have released a potential fix for this in beta software version 21.10. If you would like to get beta software updates, sign up for our public beta program: Enrolling in and Learning About Garmin Beta Software Program

    Notes about the beta update, can be found here: https://forums.garmin.com/beta-program/fenix-7-series/f/announcements/408411/beta-version-21-05---check-for-updates-only 

    If you get the beta update, please let us know if it resolves the problem for you. 

  • I'm not so convinced that using beta versions will solve the problem, especially at the risk of further bugs.

  • I tried it, 21.10 measures the distance correctly again.

  • after so many months, instead of releasing a quickfix, you suggest customers to try the beta with all their new bugs ... :-(

    If your are confident with this Beta branch, then release it to Public to simplify the process for your customers ?

  • Yes, I have tested it on 21.06 and it works (it may have a loss of 30m), the problem is that they recommend that we be beta testers for a solution to a problem that has been around for months.

  • Dear Fellow Garminers and Product Support

    I had received the 20.16 update on Feb 13 and right away noticed the problem. I reported this within days. After few days of going back and forth on trying a few different things, finally I was able to convince Garmin Product Support that it is a bug in their software on Feb 26. However, it was not until mid to late March that this bug was being tracked formally. In that time, I received 20.22. I remember being super excited thinking this is the update that will fix the problem. But 2 months on the bug is still alive and well. It has been more than 3 months now and my expensive premium device that I wear with pride every day has been broken.

    It is also a very fundamental issue.

    To their credit Product Support had set very strict expectations on their support:
    1. They will reach out if they have an update. I can reach out but no solid response should be expected.
    2. The fix can take as much time as it can - days, weeks, months. This has stayed true to the expectations and I just hope it doesn't get into years of wait.
    3. They would not tell me if there is a device in the Garmin family that doesn't have this problem. My intention was to switch my gear, because this bug really impacts my usage.
    4. One "effective" work around is to Edit the distance of my walks, runs and hikes in the Connect app after the fact. However, I have told them 1. It doesn't change pace 2. I would not always have the actual distance, because I could be on a hike I did not do before.
    5. Finally, I have been following up with Product Support patiently and respectfully about once every week. However, recent responses have been showing annoyance and "sandbagging".

    I love Garmin watch and have been a user for several years and upgraded it twice. As such I am a loyal customer of Garmin. I am being asked to try Beta software update. I am super afraid of doing so given the lack of quality control with 20.16 and 20.22. Why am I being forced to use a Beta software for a bug fix they introduced and repeated it in multiple released versions?

    I am very sad that an expensive watch has been rendered nearly useless for more than 3 months now and there is no accountability.

    I am holding on to the hope that the bug fix will come out soon and it will not introduce any new bugs or side effects.

    F22Maverick


  • Welcome to Garmin's poor or non-existent support. I'm sorry you noticed the company is getting worse every day.

    As such, if the distance problem is fixed in a beta version (I hate being a beta tester anyway), it is the only way to get a solution, although at the risk of other problems.

    To be honest, you will solve the problem of the huge difference in distance, but it will never be exact, since the device does not measure, it calculates and as you say, any change in your movement can be counted as incorrect and discarded (I have a very long post explaining the details, but it seems that it did not have the impact I expected).

    Buying another watch will not give you a solution. I tried the Fenix ​​8 and it had the same behavior (small but noticeable losses (100m per 10km)). Going with the competition would be the best option, but giving up several options (in my case it was Suunto).

  • Thanks Mark! 

    Despite the lack of empathy from Garmin Product Support, I am still holding on to Garmin - hope against hope.

    It is so sad that Garmin has such low bar for customer service and low regard for their customers.

    They are testing my loyalty every single day at this point. There must be a way to highlight the poor quality of software and customer service.

  • What is the update on beta testing? It is more than 3 weeks since this update came out and more than 3 months the serious bug was reported.

    Is there a path to general release?

  • It seems that the fw has not come out very well, since the problem was reported they have released 4 versions, that's where I stopped, I sold the device