Related
Options

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

Mark_Antony_8
2 months ago

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.

  • 0 3 days ago in reply to Garmin-Laurie

    When is public software update? It has been 3 months. Beta is not a solution and you must not sell it as one. It appears beta version after beta version are not doing well in any case.

  • 0 2 days ago in reply to Garmin-Laurie

    Just wanted to share my thoughts. Beta software idea it's ok in my opinion. But we, as beta testers, need to receive more feedback from Garmin. You need to enhance communication with your beta testers. They are doing a job for free! If someone just listen and reply sometimes on the biggest bug threads on the beta software forum...

    I think communication from Garmin is insufficient right now, at least in fenix 7 beta forum

  • 0 1 day ago

    I got the public update for 21.19. I can't wait to test it later today. Fingers crossed. It has been long 3+ months.

  • 0 1 day ago in reply to F22Maverick

    Since 21.10, walking activity works well, no matter if you run, walk, or walk with your hands in your pockets, it measures the distance well. But. If you choose a running activity (run, trail run or ultra run) and walk, it measures the distance just as badly (if you run, it measures it perfectly). I wrote a private message to Garmin_Jake about this 3 weeks ago, I also sent data about it. Version 21.19 came out, walking activity is completely fine, but running activities, if you walk instead of running, do not work properly, they have not been fixed. After that, I wrote to Garmin_Jake again, I got the answer that they opened a ticket about this and it will be fixed with a future software update. More months again??

  • 0 1 day ago in reply to aribacsi

    Why you walk for running activity ? :) You need to use multisport  for that :) came on it's Garmin :)

  • 0 1 day ago in reply to aribacsi

    It measures less distance? Or higher distance?

    I use trail run profile a lot, and I use to run with poles. I think it will affect my metrics, I am afraid to update my watch again. I will stay on 17.28 software for more months I guess...

    I was really hoping this update was the good one...

  • 0 22 hours ago in reply to 5811112

    It measures less distance. The answer to Extreme's question is: there is plenty of walking on a 100km trail run with 3000m of elevation gain. The problem affects all running activities: Run, Trail Run, Ultra Run

  • 0 11 hours ago

    I've already reported that problem with walking while running.

    And yes, it does the same thing as walking, just in reverse.

    The combination of both routines is necessary, especially when you're doing intervals or just need a breath of fresh air to keep running.

  • 0 10 hours ago in reply to aribacsi

    It is a problem that Garmin is not doing regression testing enough to catch these issues before pushing the updates out. It took 3+ months to fix what is a basic issue - losing ~20% of your walking distance.

  • 0 9 hours ago in reply to F22Maverick

    It's more than possible that they ARE testing but just not catching errors that only happen to some folks equipment. I regularly run (and walk) wearing my Fenix 7 S Pro with other folk, all using a variety of devices, and there's never more than a few metres between our recorded distances.