GPS + GLONASS Drops Out Mid-Run (Watch 10 days old)

I was mid-run and GPS + GLONASS dropped out for about 1/2 mile.

See https://connect.garmin.com/modern/activity/1723342270

I did have the metronome turned on as I was working to increase my cadence.

I will monitor this and report back if it recurs. I never had this problem on this route before in over a year running it with a Fenix 3HR.

Best,

Tim

Strange thing is that it seems to keep tracking your pace meaning it does seem to have some actual gps-lock...

No - it had no lock. It was assuming pace by cadence (I had a HRM-TRI on). If you look at the map, it goes off road at Talmadge Drive at Prince when I kept going on Prince Avenue all the way to Sunset drive and took a left. This tells me the GPS lock was lost at Talmadge (it's in front of a hospital) and then reacquired when I was 2/3 the way down Sunset drive. I was running a 9:30 pace the entire time and during the loss of GPS the watch had me at 10:45 - 11:00 pace.

This is a known issue that supposedly will be fixed in the next firmware update.

"Fixed an issue, where the watch would incorrectly report that GPS signal was lost, while using UltraTrac."

See http://www8.garmin.com/support/download_details.jsp?id=11665

If you turn your watch off of UltraTrac and use one second recording Garmin says you should not experience the problem.

Same problem....?!?
https://connect.garmin.com/modern/activity/1727681306

Mine did same thing when using the Run Dynamics Pod. Since then I stopped using it and no drop outs. Some bug in Watch when it's recording Run Dynamics I believe.

No - it had no lock. It was assuming pace by cadence (I had a HRM-TRI on). If you look at the map, it goes off road at Talmadge Drive at Prince when I kept going on Prince Avenue all the way to Sunset drive and took a left. This tells me the GPS lock was lost at Talmadge (it's in front of a hospital) and then reacquired when I was 2/3 the way down Sunset drive. I was running a 9:30 pace the entire time and during the loss of GPS the watch had me at 10:45 - 11:00 pace.

This is a known issue that supposedly will be fixed in the next firmware update.

"Fixed an issue, where the watch would incorrectly report that GPS signal was lost, while using UltraTrac."

See http://www8.garmin.com/support/download_details.jsp?id=11665

If you turn your watch off of UltraTrac and use one second recording Garmin says you should not experience the problem.

Its not just an UltraTrac issue. This was GPS with smart recording https://connect.garmin.com/modern/activity/1730906621

+1

I have experienced a very long GPS drop today on 3.30 production with 1-second recording and GPS+Glonass: https://connect.garmin.com/modern/activity/1736144953
As ANT+ sensors I had HRM (with running dynamics), Tempe and Stryd connected.

I've not seen anything like this in earlier firmware versions so I suspect it's a regression of 3.x

I truly hope this issue gets identified and fixed soon because it is a _major_ issue for a GPS watch!

Thanks

I just encountered this issue on my post-run bike ride. :mad:

GPS + Glonass
F5X FW v3.30
Speed and Cadence sensors (forgot the HRM-Tri after the run)

https://connect.garmin.com/modern/activity/1739778528#

I never saw such issues with F3HR. I have Strava segments on and it started trying to navigate me to the segments so it looks like it took me off the paths and trails stuck me on to the road (when I wasn't flying over the neighbourhoods).

The actual track should have been: https://goo.gl/GcuYKZ

It happened to me again this morning.

GPS 1s + GLONASS
No Ant + devices

https://connect.garmin.com/modern/activity/1740450205