This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Position arrow getting stuck - while route still is at correct/current position.

While hiking from times to times - the position arrow gets stuck when following a route/course. I think once it even happened without active route/activity/course.

While navigating then the navigation will continue but route back to the stuck position. Especially if you are in an area with bad map quality, this is super annoying and I got lost a couple of times due to not noticing that the map was stuck.

Only solution to correct - pause activity, reboot, resume activity. Sometimes pausing/resuming activity alone solved it too. This happened with the screen lock on or off.

0 vmojzisek over 2 years ago

seems to be the bug described in this thread https://forums.garmin.com/sports-fitness/cycling/f/edge-1040-series/306808/lock-on-road---not-working-in-mtb-profil/1488852#1488852

There is also workaround solution described there.

0 extremecarver2 over 2 years ago in reply to vmojzisek

Nope it's really different. And it happens very rarely, like every 12-30 hours or so once. I don't know if it happens while cycling too or only at low speed and while cycling I I usually have the data fields active and rarely look at the map page.

I think it only happens while the map page is active.

0 Martin868 over 2 years ago

Could be you device is in auto-pause. Walking can be so slow that the Edge think you stopped. To test this turn off auto-pause. When paused the track is not updated but some background functions are still happening, go knows what. Personally I turn off auto-pause for mountain biking for a similar reason, we ride so slow that auto-pause keeps triggering when it should not.

0 extremecarver2 over 2 years ago in reply to Martin868

No I didn't activate auto-pause - it was on manual pause only.

It was really just the position arrow being stuck (and of course the map window not moved accordingly) - the track itself and the route continued to be calculated (just that it wanted to route me back to the stuck arrow before continuing to the next destination)