Serious Navigation Bug: Fenix Ends Route After Signal Loss

Hello,

For several months now, I’ve noticed a frustrating bug with my Fenix. Whenever the watch loses satellite signal during active navigation, it suddenly assumes I’ve already reached my destination.

In an urban environment this happens often: walking through a pedestrian tunnel, stepping into a shop to buy a bottle of water, etc. Each time, navigation simply stops.

This is tedious, because when I glance at the watch, the pink guiding path has disappeared. In practice, losing satellite signal means losing navigation altogether — immediately.



  • 2 months to investigate? Yeah ,ok.

  • Yes, I am working as a software engineer and  today’s software is very complex. I know of bugs where people have spent 6 months of investing the bug before find root cause in some tricky cases. 

    Once found the bug then you have to think how to fix it, then do the fix, then write tests, then make sure all test pass and not broke anything else, then plan for which release which could take 1 to 3 more months. 

    And unfortunately in some cases the bug has to be rejected without fix since not able to reproduce it after thorough investigation.

    Another thing is that sometimes there are more severe bugs that has priority and with limited resources (engineers) then some bugs with lower prio has to put on hold. Not saying that this is a low priority bug

  • Understood,but when this sort of bug could have serious consequences you would expect a quicker resolution.

  • This point is valid until you realize how poorly they seem to test their software. It feels like their workflow is: create new features so we can release new products, and then let end users test those features. If polishing your software takes that long, why not pause for a moment, deliver a solid version, and then add new features in a safer way?

  • FYI as Beta testers, we had requested Garmin for 1 or 2 beta phase by year fo fix only, but nothing ...

    If you take a look to the beta changelog, they are adding more and more features for each new beta minor revision. Lessons are not learned !

  • I would like to confirm that I notice this issue as well. More interestingly (for example), if GPS is manually turned off during after attempting to use the "Navigate" feature to navigate to a destination, I observe similar behaviour. The purple line with chevrons disappears. I could not replicate this problem on a Fenix 7 Pro Solar Sapphire (47mm). The watch has great hardware features, unfortunate that the software is not up to par. Hopefully this issue gets fixed soon.

  • Yesterday, I paused my activity while buying something to eat. The activity went properly on hold, the watch face returned, and the little pause icon showed at 12 o’clock.

    But after barely three minutes inside the fast-food place, my Fenix notified me that I had “reached my destination.”
    So even with the activity paused, the watch essentially decided that navigation no longer mattered… which is frustrating.

  • This point is valid until you realize how poorly they seem to test their software

    I definitely agree with you here. I think Garmin could do much better on their SW quality. The quality of fenix 8 at the time when released was in such bad state that it was not ready for release. Only after a year the worst bugs were fixed and still bugs left to fix. I really hope they will get better in future. SW quality should be highest priority since useless with new features if you can’t rely on those already existing 

    My point in previous post was just an attempt to explain why it could take some time to fix bugs but as said, having a good test procedure is something that we should expect from Garmin with the price we pay for their devices.

  • I have moved to Apple Watch. 
    Sorry Garmin but years of bugs have convinced me to go away.

    I'm out!