Problem in walking activities

I'll try it, but I don't think anything has changed. There's no mention of this in the changelog and the sensor driver version hasn't changed either.

The miracle happened. I walked a 4km test lap with beta 21.05, 2km (until 21:45) with my hand moving, and the 2km back with it in my pocket. It measured the distance perfectly. I tried to walk at a steady pace, which is also visible on the diagram, which is also perfect. I checked the "FIT" file with my little code, it is also perfect. I am attaching it here as an excel file, as well as the pace diagram.
Since the sensor drive version has not changed, I think the algorithm took the accelerometer data into account too much or completely incorrectly in a certain pace range (since it was good at running pace until now). Thank God it was finally fixed.

v21.05 4km , perfect measurement.xls

Thanks for the quick test, mate 

I already did my 8-mile loop today (when this version was released), watch in pocket. I loaded this 21.05 version on my watch, will try it tomorrow and report my results. I hope this version will not introduce other anomalies (I will read the forums for reports). 

I think I was a little happy yesterday. Today my wife and I walked our usual route, which should be 5.21-5.22 km. Hers was 5.22 km, mine was only 5.16 km. I analyzed it with my little code (I'm attaching it), and the errors are visible. Yesterday my average speed was 5.5 km/h, where everything was perfectly fine. Today our average was 4.8 km/h, here unfortunately I lost 60m. It seems that in the lower speed range the calculation still depends too much on the accelerometer. Why??? The GPS was perfect !!!!
By the way, there are no big waves in the speed diagram like before, but we walked at about 4.8 km/h the whole time, our highest speed was still 9 km/h. How?????
The calculation is much better than it was, but still not good!!!!

By the way, according to the Haversine formula, it's 5.22 km too!!

v21.05 5,16km (should be 5,22km).xls

Today I completed my 8-mile loop with the 21.05 version. Watch was on my wrist, I was using the HR-Pro strap. The distance calculation today was correct. That includes the seven intermediate 1-mile points. I didn't analyze logs, but for my use case the distance and pace calculations were satisfactory.

This almost 2-month Garmin fiasco was an extremely negative experience. The Tech Support was polite but beyond useless. My appeals to be able to reach management in the software development department were blocked, nobody wanted to listen. Once this "fix" is incorporated in a "stable" release (and it is confirmed that it still works and that something else was not destroyed in the process), I will set my watch to NEVER download another update. Lesson learned.

Garmin does not seem to be interested in customer feedback. They do not seem to be interested even in the feedback given by the beta testers who take time (for everyone's benefit, including Garmin Corporation's) to report issues. Garmin is squandering an extremely valuable resource. This arrogance will be costly as people move on to other sports watch brands. Perhaps somebody in Garmin management will read this (I encourage others to contact Garmin management, their email addresses are easily obtainable online) and they will make some changes.

Hello davidgtc. I don't know if you read my posts about the problem, but I would like to ask you something. It would be a great help if you or your wife would walk the same route (about 5km) with Fenix ​​8, once with smart data recording set, once with per second data recording and share the measured distance with me. If you could also attach the activity files, that would be great.
Of course, you don't have to, but it would help me a lot to understand whether the Garmin algorithm is fundamentally flawed, or just in Epix.

thanks for the time! appreciated