I've been using this 255 for a couple of years now and never had any issues. However, after the 20.32 update a few days ago, it's been having issues with GPS. Normally, it'd find signal within 30 seconds of being turned on in front of my house. Now it's taking minutes. It's exactly the same spot, same environment, nothing changed other than the firmware update.
Also, on a bike ride a couple of days ago, it'd lose GPS signal all the time and couldn't calculate the speed. After I got home, I also noticed that the mileage was not accurate and a big chunk of the track was a straight-line. Here's the activity:
https://connect.garmin.com/modern/activity/17270389229
If you zoom in, you'll see the northwest section of the track, west of Lake Washington, is a straight-line and par of it is in the water. I certainly didn't bike on water :). And this is a stretch I've biked and run literally hundreds of times and it's a super busy stretch if you look at Strava's global heat map, one of the busiest trails in Seattle. It's not covered by dense trees. The lake side has clear views of the sky.
The same happened to a run yesterday. It's my routine route. I know every pothole of the route and I know the distance to the second decimal place. The mileage was off by ~0.2 miles out of 6.28. I have never seen it off by this much. The variance has been plus minus. 0.02 miles, usually.
Has anyone else been experiencing the same problem after this beta update? My "Satellite" setting was set to "auto select". I'm going to change it to "all systems" today and see if it makes a difference.
