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

7.0 bug - course stays at beginning

Since 7.0 when I load a course and select to not navigate to the beginning of the course, the device doesn’t show turn by turn navigation, gives instructions at the top as if I’m at beginning of course, and doesn’t count down mileage to destination. 

  • I encountered this also once when starting navigation while I was at 75% of the ride. Purple Route was shown + east on <first street>

  • Have you tried selecting yes for navigating to the start of the course? This shouldn't be required, I'm just curious if there's something specific triggering this issue. 

    I would also recommend performing a hard reset on the Edge (holding power button in up to 15 seconds) as well as removing and re-adding this course. 

  • Ok Former MemberI hit this bug again today - and I have a better understanding of the nuances. This was a new route that I uploaded. Route is here. If I start the course at its beginning, all functions normally. Once I pass through somewhere between mile 1.4 and 2.5, a few things break:

    1. Distance to destination just stays at the full distance of the course

    2. Turn by turn is lost for the rest of the course

    3. Initially on the map page, at the top, it says "continue to end point" and at some later point in the ride it states "ride northeast on Webster St", which is the initial instruction for the course at the starting point

    4. It does know if you're on the route or off the route for the full duration, even after the turn by turn and distance break. If you go off course, it'll alarm and draw a suggested route back.

    Of note, this course and the previous one I reported above both followed this same initial routing that happen here between 1.4 and 2.5 miles in.

    I suspect something about this route is causing the bug. This area is a bike trail, with a series of bridges, that have recently been rebuilt. It's possible the Garmin doesn't understand that there are paths / bridges, but the Strava routing / reality does, and that's causing the bug? 

    I did complete the course and I could upload the ride file if it'd be helpful.