Track recording currupts... again (16.17)

Which GPS setting did you have set? All Satellites + Multiband or something else?

Have you tried using any other GPS device?

The loss of lock on the recording at the 1.5km point on 30 October can only be GPS jamming. It's a wide open space with nothing obstructing the sky.

gpsjam.org/

I agree. The GPS FW 5.0.0 is being used on multiple devices and there are not many complaints - So the problem is not related to the FW itself. As your tracking has been just fine on previous runs.. It must be something else. And in this case it could definately be gpsjamming for some reason.

Having said that.. Before you complain further you should really bring more information to the table. 

What GPS settings? One-Second recording or smart recording?

UltraKapitan said:

If you can't make a normal firmware, then give the option to rollback to a working firmware. Stop joking of users!

Personally I have never seen that, with no firmware, including 16.17. I live and train in Germany.

I don‘t think, the firmware is to blame.

nowster said:

gpsjam.org/

That is much more likely the reason for track corruption.

Seems that in fear of Ukrainian drone attacks, the GPS in some Russian places, including Moscow is jammed.

Garmin will not be able to solve this.

The gps settings don't matter. tried everything.
yes, other devices work fine.
It's not jamming. look closely at the track - it's recorded perfectly in the opposite direction.

There really are jammers in town. But you probably don't know how they work. If the jammer is on, the watch does not even get gps. Watch the run again. At the first kilometer, it crushed. On the way back, it's fine.
Here's an example in a completely different place outside the city.
connect.garmin.com/.../12500139001.

By the way, no such problem with walking.

The older versions of the firmware were probably released before the jamming became as active as it is now.

And the jamming is possibly not continuous. It's probably tested regularly for a few minutes. It's also probably ground-based and directional, meaning that it only affects the watch when that side of your body faces the transmitter.

Yeah! And they are waiting for me every time)) it works in other way. I'm working near zone with jammers. There is no chance to catch gps. And this is how it works. And it was before, year ago, jammers were active and still now, but not everywhere. 

look at this - https://connect.garmin.com/modern/activity/12042681509

there were jammers)

The standard answers to this problem are just a reason not to look into it. I'll say it again - this problem occurred and was somehow solved simply by releasing a new firmware. And the funny thing is that nobody knows how it works. And why don't my friends have gps problems on the route mentioned in the description? They have other models of Garmin or Suunto or Polar.  And they're fine.

@UltraKapitan is right. This problem has happened before. The versions he mentioned had the same problem. After 16.17 I had the same situation. Attached is the route I ran with my wife today. In normal gps comparison the distance is correct but 955 overestimated the distance by 1KM.
the correct distance is 5.1km.