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

Navigation finishes before a single meter is ridden.

I often select a course to navigate before I actually jump the bike.

If the course is loaded completely (100%) it can happen -- mostly (always?) if there is overlap between start and end of the ride in opposite directions -- that the naviagation finishes before I ride a single meter: "Congratulations ride finished" and I have to start the process from scratch again.

That sucks as bit, especially since loading the course takes a few minutes .. 

Why does the device not check the time (A 100km course should not finish after a few seconds.. or even minutes) ?

Any ideas? Also how can I file a bug to Garmin? Email to support does not work any more / does not appear to be the correct way anyway..

Thanks, also please leave a 'me too' comment if you have experienced similar problems == more evidence of a common bug ...

  • Former Member
    +1 Former Member

    forget it. this feature was around since 2010 and the edge 705. garmin didnt add the "Why does the device not check the time (A 100km course should not finish after a few seconds.. or even minutes) ?" function for 10 years.

    just make start and end point different, mine is in front of the house and on the back.

  • Why does the device not check the time (A 100km course should not finish after a few seconds.. or even minutes) ?

    The behavior is a consequence of being able to join a course in the middle (which is an important feature).

    Two ways to deal with this:

    • If you are designing the route, then make the route a bit shorter. The idea is to be closer to the start point than the end point when you start the route.
    • Start the route a bit later along the route (start it after the start point).
  • Thanks to both of you.
    Working around the issue is a fair option.

  • do not navigate to route, when device is asking this in beginning