I've been using my Forerunner 245 Music for a couple of years without any issue, but in the last week or 2 it has started to take a long time - several minutes - to acquire a GPS signal when starting a run starting from my home. This has happened about 3 times.
Today I ran 3km to my local parkrun and it did not acquire GPS at all in 15 minutes.
I started a new activity on the watch for the 5km parkrun itself and looking at the tcx/gpx file it had GPS data from the very start. However I noticed while running at the start the speed seemed accurate but then decreased to an implausible jogging pace while I was running hard. This is the activity - https://connect.garmin.com/modern/activity/10487308033#
The elapsed time is correct - 21:15.
The distance is completely wrong - 3.62km not 5.0km.
The location is off - the map shows it West of where it should be. The run was in the park but the map shows it starting the other side of the road outside the park. There is some tree cover on that side of the park but this has never been an issue in the past.
One thing that might be relevant is I did a treadmill run this week and the watch asked me to calibrate the distance, which I did. Previously its indoor running pace estimate was too high by about 30s/km. Calibrating the accelerometer-based pace I don't think explains the incorrect distance.
Is the difficulty acquiring GPS that the watch now seems to have related to the GPS position inaccuracy and the incorrect pace and distance? This is the first the distance has been completely incorrect. The other 2 recent runs when it took a long time to acquire GPS, the distance was correct.
Software is up to date — Version 11.60
Thanks
Alex
