Segment navigation woes

Having a consistent issue with Garmin and Strava segments that trigger along a bike trail in the city, and so near roads. The segment triggers as expected, then immediately tries to get me to move to roads or freeways NEAR the segment, rather than following the segment itself. This leads to GPX tracks that show assumptions about me being on these roads, then teleporting to other roads on my way to the finish line. When the finish line is passed, the navigation desperately wants me to turn around to get back to it, alerting near every subsequent nearby street crossing.

I am using the default mapset. This condition has persisted through 2.9, the betas and now 3.3. Lock to roads is off. I also attempted telling the Bike activity specifically to have its own settings with lock to road off. 'Routing' in the Activity profile is set to cycling. I've attempted switching from Strava to Garmin, with the same behavior. This afternoon (post-ride) I wiped the contents of the segment and segment list folders. I have also gotten much faster at stopping navigation while riding. If I cancel it in time, the GPS continues to track and strava or Garmin recognize that I rode on the segment in question.

I searched for this topic with no luck and apologize if this has already been covered. But I am also losing my humor about this. What else should I be trying?
  • I think your issue could be the 'lock on road' setting, to turn this off I had to stop the bike app using system settings and then turn this feature off in the app settings.

    Hope that helps!
  • I am having the same issue with running segments and have reported it several times in the Beta threads and via mail to the development team. One thing that might be a workaround is deactivating all maps for the activity because the Fenix 5 doesn't seem to produce this bug.
  • I think your issue could be the 'lock on road' setting, to turn this off I had to stop the bike app using system settings and then turn this feature off in the app settings.


    That setting is off, though I agree that is how it is behaving. It's almost as if there is another 'Lock to Road' setting within Segments overriding everything.

    I am having the same issue with running segments and have reported it several times in the Beta threads and via mail to the development team. One thing that might be a workaround is deactivating all maps for the activity because the Fenix 5 doesn't seem to produce this bug.


    Good to know that I'm not alone seeing this. This may be the next troubleshooting step if the navigation behavior stops with an empty segment folder.
  • In case anyone comes across this as they troubleshoot a similar issue, the following troubleshooting has NOT yet fixed this for cycling:

    • v3.41, GPS 4.3, Display 2.2, BLE/etc 3.20
    • Lock on road disabled in main watch settings
    • Lock on road disabled in Bike activity
    • Segment & segment list folders cleared, segments redownloaded
    • Garmin cycle map disabled in Bike activity
    • Cycle map & base map disabled in Bike activity


    The original, more irritating behavior of trying to shift segments to the nearest major road has gone. But so has Live Segments overall. Neither Garmin nor Strava segments currently work.

    Hope that helps someone narrow down their own efforts.
  • I tried a Strava Live Segment while mountainbiking yesterday and it worked fine.

    Still have to test running segments.
  • Glad it's running for you. The segments I'm watching it struggle with (or ignore, really) are urban greenway paths running along or near major roads. Behavior did not change in latest beta. I'm probably going to wipe the watch next but weather will keep me from further testing for some time.