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

Updating + crash + clock time

Approx once a week the following happens

- FR235 gets stuck saying 'Updating' (not sure what is updating to be honest, I don't request anything, it just does it itself)
- I try hitting all different button combos, disconnecting from iPhone. Nothing helps
- I hold all the buttons for a while
- FR235 resets
- FR235 says the wrong clock time until I go outside and start a GPS activity

So a few of questions

- Why the crash? why so often?
- Anyway to get out of a crash without the painful GPS/clock reset issue?

I still kind of feel this watch is in beta, not the most robust thing I've ever owned

Thanks community
  • Former Member
    0 Former Member over 8 years ago
    Approx once a week the following happens

    - FR235 gets stuck saying 'Updating' (not sure what is updating to be honest, I don't request anything, it just does it itself)
    - I try hitting all different button combos, disconnecting from iPhone. Nothing helps
    - I hold all the buttons for a while
    - FR235 resets
    - FR235 says the wrong clock time until I go outside and start a GPS activity



    This happens exactly as you describe with my FR630 too (with Android phone). I have now woken up two mornings straight to a watch that is stuck to Updating. I can't reason why this happens, but it is really annoying.

    BTW are you using a third party watch face? Just checking...
  • This happens exactly as you describe with my FR630 too (with Android phone). I have now woken up two mornings straight to a watch that is stuck to Updating. I can't reason why this happens, but it is really annoying.

    BTW are you using a third party watch face? Just checking...


    Interesting... yes, am using Actiface watch face. You thinking that may be related?

    Does anyone know what the 'Updating' means? could that be a watch face or this that updating notifications or something else?

    Is there any way to debug these issues? maybe a log file somewhere.
  • 'Updating' crash now twice in a day. So annoying. Makes the watch useless as a watch as the clock time always resets.

    I find it quite amusing that I have to go and stand outside yet again to reset the clock. Its great that to get outside and all that but just not at the random moment that the watch dies on me.

    If anyone from Garmin out there wants to use my watch data to help debug this let me know. Alternatively it would be nice to hear if this is a common issue that is shortly to be fixed.
  • Instead of trying to debug it (which is neither your responsibility nor your concern, but Garmin's if it is anyone's), have you tried to resolve it by resetting the watch to factory defaults, and see if the problem persists or goes away?
  • Former Member
    0 Former Member over 8 years ago
    Approx once a week the following happens

    - FR235 gets stuck saying 'Updating' (not sure what is updating to be honest, I don't request anything, it just does it itself)
    - I try hitting all different button combos, disconnecting from iPhone. Nothing helps
    - I hold all the buttons for a while
    - FR235 resets
    - FR235 says the wrong clock time until I go outside and start a GPS activity



    I experienced the exact same scenario this morning, for the first time. And I am also using Actiface.
  • Sounds to me like Actiface is the common factor in your problems. Perhaps you should uninstall it and see if that fixes your problems.
  • Sounds to me like Actiface is the common factor in your problems. Perhaps you should uninstall it and see if that fixes your problems.


    Actually, I kind of doubt that Actiface causes the problem. It's more likely that it exposes the problem. As far as CIQ watchfaces go, it's a fairly large and complex one, and also a very common one. CIQ watchfaces are very restricted on what they can do and what they can access, so the watch face itself likely doesn't cause the problem.

    There have been cases in the past where something in the native firmware incorrectly uses part of the CIQ memory (the "fireworks" for step goal in the 2.80 FW for the original vivoactive is a good example), as the FW itself can do anything it wants, and the fireworks did just that - walked over parts of Connect IQ. In this case, the "updating" circle, could be "walking over" bits of Actiface, resulting in a crash, and with Actiface being a large watch face memory wise, there is more of a chance of something getting "stepped on" by the FW.

    What I suspect is that any of the larger/more complex watch faces could expose the problem with the lockup/crash, and the problem isn't any of the watchfaces, it's how the FW does the "updating" thing... (as was the case with the "fireworks" on the va)
  • Former Member
    0 Former Member over 8 years ago
    solution for me

    Hello,
    I had the same worries as you.
    After doing a "little reset" : let press the power button 15 seconds
    I have a "big reset": press power at the same time as the key at the bottom right
    Then putting you on the start position of activity wait 15 minutes that the watch finds a GPS and it resynchronizes your clock and calendar.