Problem in walking activities

I've also noticed the problem is whenever you walk, regardless of the activity/app you are using (fenix 7x pro sapphire solar).  The GPS/FIT file itself will show the correct distance.  But when viewed in the Garmin Connect app or web, the distance is always off (significantly short in my case).

The last straw for me was running a 10k on a USATF certified course.  The watch distance (and garmin connect) were off, affecting pacing, etc.  The FIT file shows the correct distance.  However that wasn't helpful during the run.

I rolled back to 19.41 and the problem cleared up immediately.  I have automatic updates turned off on my watch now and won't be updating until there is a confirmed fix for this issue and the battery drain on 20.xx.

I upgraded to firmware 20.22 yesterday and today I tried a test walk of ~2 km with my Epix 2 Pro 51mm, 6X Pro Solar, 5X+, 3HR and Polar V800.

All four Garmins returned a distance of 2.13 km in the app, on the web and when exported and examined in DCRainmaker's Analyzer. The V800 ended with 2.12 km. I don't think there is a "Walking distance" problem, at least with my watch. However, it looks like sensor connectivity could be flaky.

HR data differs a little because the Epix did not auto-connect to my HRM Pro and my 3HR had the HRM disabled. The V800 was not even paired to the strap I noticed this and corrected the Garmins about half way through the walk. Even so, the Epix did a good job of sticking close to the chest strap and only the 3HR showed some wobbles. To be fair I was wearing two watches per wrist, with the Polar V800 over the back of my hand.

That's the beauty of bugs: they don't neccessarily affect everyone... me neither. Epix Pro 20.22.

Same problem with me - significant discrepancy (7.27 vs 6.0 km) betweem my Epix and my wife's FR965 during the same walk session. GPS is set on "Auto select" on both devices. Both devices updated with latest fw.

Probably a sensor driver software bug. See my posts in another discussion.

forums.garmin.com/.../distance-measurement-inaccurate

I read your posts in the other thread. The info in the other thread is great, but this thread needs to continue for as long as the "Problem in walking activities" persists. So I am posting here. As others have notices, the incorrect distance calculations are seen in other activities as well (I have personally tried running activity and biking activity, with wrong distance calculations). I have been struggling with this issue for over one month. I read all the forums, I contacted Tech Support (Tech Support was polite but utterly useless, I may even say "clueless"), I escalated to some form of manager (polite but just as useless). I provided logs. The discussion in the other thread indicates that the accelerometer destroys the distance calculations, walking with your hand in the pocket or the watch in the pocket may fix the incorrect distance calculations. My regular (almost daily) walking path is an 8 mile loop. For 2 years this distance and the intermediate 1-mile points were calculated by my Epix Gen 2 perfectly, every time, within a few steps. After the 20.xx updates, for over 1 month now, I have been getting random distances between 7.5 and 7.8 miles. Of course, all pace and other calculations are severely off as well. Today I did the same loop with my watch in the pocket and wearing the HRM-Pro. I can confirm that with the watch in the pocket the distance calculation was extremely accurate. The steps were calculated correctly as well as calories used. What in the world is the accelerometer contributing, other than destroying the distance and pace calculations, I do not know. The inconvenience wearing the watch in the pocket is that I cannot glance at the watch to see current HR. What a screwed up way of making use of a $1,000 watch! The attitude of the Garmin company regarding this issue (and not fixing it for over 1 month) is very sad. I do not like "conspiracy theories", but it looks to me like Garmin is bricking their older watches so we will buy newer models. If that is the case, shame on you, Garmin (this practice is illegal and other companies have gotten into big problems doing just that). Shame on you, Garmin, for destroying my $1,000 watch by releasing terrible software that was not tested properly prior to release. Finally, shame on you, Garmin, for providing clueless Tech Support.

6909374 said:

What in the world is the accelerometer contributing, other than destroying the distance and pace calculations, I do not know.

From what I know and understand, the accelerometer was used to calculate the route when there were problems with GPS/GNSS, e.g. you were entering a tunnel. Then, based on your hand movements, the watch tried to guess in which direction you were going and how fast (of course, it works sometimes better, sometimes worse).

I guess they changed something in the algorithm and now the watch relies too much on data from the accelerometer even when the GPS/GNSS signal strength is good.

6909374 said:

The attitude of the Garmin company regarding this issue (and not fixing it for over 1 month) is very sad. I do not like "conspiracy theories", but it looks to me like Garmin is bricking their older watches so we will buy newer models. If that is the case, shame on you, Garmin (this practice is illegal and other companies have gotten into big problems doing just that). Shame on you, Garmin, for destroying my $1,000 watch by releasing terrible software that was not tested properly prior to release.

Since the Fenix ​​8 came out, Garmin's support and interest in Fenix ​​7 users has been practically zero. Bug fixes are released with a 1-2 month delay (if they even bother to fix the problem). On top of that, the software quality is a joke. Now the "stable" versions work so badly that we should call them "public betas". Fixes are not tested, user feedback is ignored, more and more bugs appear with none new functionalities.

On Sunday, Support said they expect a response from Garmin-Lauriue on Monday-Tuesday. It's Friday and nothing .......

Maybe try writing to support again with the information that there is no contact from their side?