Instinct 2X. Navigate by activity= total freezing.

Hi, if I choose navigation by activity from the history in the watch, after about 1 hour the system begins to chop, lag until completely freezing. If I cancel the navigation, the watch works normally again. If they freeze, only the factory settings helped me, with losing all data and not saving the activity. FW: 12.26

photos.app.goo.gl/3fuDZTUMqH3zb9ht8

  • The same happened to me, while navigating by activity from the history. Instinct 2 solar, FW: 14.12.

    The only way to reset the watch was by method with pressing 3 buttons during watch start.

    I had to find the 3 button method for reseting the watch (I though it was completely bricked) on internet.

    Then I had to set up the watch again.

    Very frustrating experience, I would not like to experience this on multi day hike without internet coverage.

  • got the same errors.

    this was suggested by garmin support:

    "This does not seem to be the result of either an issue with the course or an incompatibility with the watch.

    I recommend performing a reset as follows:

    If needed, you can perform a backup of your device."

    training for a marathon ATM, so I don't risk navigating with the instinct

  • Same happened to me today on Instinct 2 standard edition (software 15.08). Standard master reset combination (ctrl + set) would open the reset menu but the watch would immediately freeze and I couldn't select any option, had to use secondary 4 key combination.

  • Same here running 15.08 update on instinct 2x.  Hiking using courses to navigate and screen either freezes completely with all buttons unresponsive - had to google on phone to work out how to reset as never had this issue before - or watch goes into cycle of just showing Garmin logo (no response to key presses) then switching to paused hike mode which when you select resume then goes back to the Garmin logo and so on about 5 times.  Eventually it says gps ready and resume works (no issues with gps reception as friends basic Garmin (no navigation option) continued to work perfectly throughout. Really frustrating.  Watch didn’t measure distance travelled while this was going on.  Happened multiple times last week. Have never seen this prior to 15.08 update.

  • Hi, I've had this problem recently (with the current firmware) and some time before (with the previous firmware). The watch can handle one hour tops, then it freezes. Is using Navigate by activity or Race in an activity no go for the watch? Is there anyone using these two functions successfully? I've tried to use this function twice and got the watch to freeze both times. I'm gonna have to use navigate by course in an upcoming race so I'm hoping it will not cause the same problem too.

  • I had similar situation last month. I was running 52 km trail. There was chest belt (Garmin) on me and I selected "Navigate by Course" on my Instinct 2 watch. After 31-32 km it freezed, only garmin logo and beep on pressing any button. Resetting didn't help. Only full reset with 3 buttons helped, so I've lost my 32 km running and recorded only 20 km.

  • So it isn't just the Crossover that is affected by this then. Interesting. And yes, this still occurs on the latest firmware (16.11).

    I'm not surprised this issue has been around as long as it has. For those experiencing it - while the display is frozen, the watch itself is not. Open Garmin Explore and cancel the navigation from there. The watch may take its sweet time to respond, but will eventually unfreeze - this can take up to half an hour in my testing.

    DO NOT power the watch off while frozen. Doing so bricks it and you will need to perform a factory reset in order to use the watch again.

    I reported this to Garmin customer support directly a few days back. I was initially told that this is intended behaviour when loading large courses or GPX tracks. I wish I was joking.

    After some back and forth, the rep eventually decided to file a bug report with the engineers, after warning me that it will likely be dismissed and not fixed.

    To be clear here. We are talking about an adventure watch - a device people will use for wilderness navigation in places where there is no cell service.

    If this watch freezes and ends up bricked while multiple days into a bushwhack, you're screwed. You might be able to find your way back out. You might also get lost and die.

    I cannot stress enough the severity of this bug. If I cannot rely on my $500 wilderness navigation tool to do what it says on the box, the product is defective. And the answer given by customer service - that the engineers will likely not attempt to fix this - is UNACCEPTABLE.

    Apologies for the caps lock here and there. But yes, I am somewhat angry about this - this is a software bug that has the potential to kill adventurers without a backup navigation device, and Garmin seems to be hand-waving it away. Not to mention I'm now stuck with an almost $700 CAD device that can't be trusted to do what it says on the box.

    I do love the Instinct Crossover. There's not much else like it, and I'd much rather see this get fixed than request a refund and give up the watch (which I'm seriously considering at this point). But until this bug is fixed I can't recommend it - or Garmin in general - to anyone.

  • Thanks for reporting it to Garmin. I'm sure they won't do anything with it and once they release the Instinct 3, it will also have the same bug.

    Anyway, great observation. I always powered it down eventually and lost everything. I didn't know there is a way to turn off navigation in the app.

  • Hi, any new information about this error?
    Has anyone tried beta FW if she solved the problem?
    When will the new FW come out?
    I think I will complain about the watch.

  • I haven't seen this happen since updating to beta 17.01 firmware.

    However, it's also worth noting that I haven't recorded any long activities since then - the watch hasn't really had a chance to freeze. Cycling season is over since winter has hit hard in Edmonton, and the mountains are covered in even more snow so hiking is off the table. I won't be able to say for sure whether this bug is gone until I have a few months of cycling and hiking done this year.