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

Enduro Rebooting During Activity

Is anyone else having issues with the enduro rebooting in the middle of an activity? (This is the first version as I haven't received the second yet.) I've had this happen several times over the past few weeks. I don't seem to lose any data, it just reboots to the save/resume page. I'm running the 20.42 but it has happened on other version as well. 

  • My Enduro had a number of file system issues (corrupted files), among which the track which I was running when the latest reboot happened. I'm not sure if the state of the file system was the cause or the result of the reboots, but after a factory reset, my issues disappeared. No reboot since then. You might want to try this.

    If you're IT-savvy enough, you might want to check your file system before doing the factory reset. I would not recommend to do a repair, as you're working on a running system with open files.

  • I just had it happen again last Saturday. 2 hour 42 minute run. Happened about 1 hour and 14 minutes in right after a text message came in. I don't know if that is related or if it was coincidental as I had been receiving them pretty consistently all run. I think the watch dropped about 2 minutes or so and that is it. Didn't do it again the rest of the run. Still not very confidence inspiring.

  • My Enduro is rebooting during Ultra length activity too. It's also not recording in history

  • At first, I thought that it was a problem with navigation.  I did a 30mi run that took 8hrs.  At the beginning of the run it would only restart if I stopped the timer to take pictures or something.  Then it would happen randomly after 6 hours or so.

    This time I was running UTMB and it crapped out at about 29 hours.  It would just reboot and reboot.  Eventually it gave up on the activity and I gave up on it.  I hope that the 23.0 firmware I just uploaded to my watch fixes it.

  • My Enduro restarts 50%+ of the time when I try to read a message, usually from my crew during a race. Really thought it would be fixed in v23.00 but nope, very much still there. For clarification, this happens when I go to read the message, messages come in fine, but if you go to read them, you are rolling the dice.

  • I just ran my first 100km. The Enduro even with the new update did it again leaving me in a lurch with absolutely no data to help with the race. I'm going to call in tomorrow. It's really upsetting as this was the biggest running race for me so far and important. The watch isn't cheap either. 

  • It is very important to go by what I have noted above if you haven't already:

    "If you continue to experience your Enduro restarting during an activity, if you are willing to provide examples of the issue, please highlight my name and send me a Private Message. Thank you!"

    There are specific items that can be provided from your Enduro that are critical to engineering who continues to look into the issue further for those still experiencing a restart.

  • Yep, I have been in contact with Garmin anytime it happens. 

  • Former Member
    0 Former Member over 2 years ago

    I bought this today and shortly after set up it rebooted.

    I was sat down and started a "run" activity after selecting my "Favourites" during the activity selection phase.

    After it rebooted from the triangle screen it went back to the run activity but had in the meantime loaded "Todays Suggested Workout".

    It is blatantly obvious that the clock speed of the processor has been downgraded from Fenix 6X to Enduro to get the battery savings.

    That much is evident with the lag that used to occur when scrolling through widgets and is undoubtedly the rationale behind the map's omission - the chip simply could not cope with the amount of processing required.

    Looking over the examples here, it seems that often the reboot occurs when an extra boost of processing power is required (ie a notification, a deviation from the course that requires an alert etc).

    I think the watch simply struggles to cope due to this chip down grade.

    I also believe that the Enduro was a tester to determine whether the market would pay even more for a longer battery on a Fenix platform. It was financially viable to test because all they had to do was alter the chip speed of an existing product and voila.

    Nothing inherently wrong with that of course but it would explain the challenges with the watch.

    Of course, all this is supposition and perhaps it is simply a bug that will be ironed out.

    However I have decided to return and stick with the 6x Pro - last thing I want to do is have it fail at my ultra next weekend after 7 hours

  • I'm going to call in tomorrow and see what they can offer. It clearly can't hold up for what it was built for.