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

freezes with notifications, requires hard power cycle, loses current time

Former Member
Former Member
After the most recent batch of firmware updates, there have been a couple times when I got a flurry of notifications, after which the watch completely froze with a notification on-screen. The first time it happened, I left it on-screen a solid 10 minutes before holding down the power button 'til it shut down. On restart, the watch had lost its current time setting -- it was something like 13.5 hours off. I left it alone for a couple hours (with "set time automatically" toggled on), but it never updated to current localtime, even persisting through multiple sync cycles with my phone. I set the time manually so I didn't miss my wake-up alarm, went to bed, plugged it in to charge while I was in the shower, and when I got out of the shower, the *manual* time I'd set was wrong. So I toggled "set time automatically" back on and it flipped to current localtime immediately. :confused:

The notification-flurry-freeze thing just happened again a little while ago, so I powered off the watch, powered it back on, and connected it to my PC/Garmin Express, thinking that might trigger a time sync. Nope. So I reset the thing to defaults, thinking there might be a bug caused by my watch face (Actiface) or one of the widgets I use. Nope again: When it reset, it still had the wrong time, even after re-pairing with my phone and syncing with Garmin Express.

As I sit here, it's 3:16pm, but the watch says 5:48 am.

Ain't nobody got time for this, right?

Any ideas for how I can get a stable watch again?
  • You need to get a GPS lock to GE the correct time

    HTH

    CW
  • Not sure why the notification froze the watch, but when you hard reset as you did, the time will always be wrong when you reboot. The time/date is set by GPS ... go outside under sky and start a GPS enabled activity (Run), wait for GPS Ready, and when you go back to the watch face, the time/date should be correct.

    Max
  • Former Member
    0 Former Member over 8 years ago
    You need to get a GPS lock to GE the correct time

    HTH

    CW


    Not sure why the notification froze the watch, but when you hard reset as you did, the time will always be wrong when you reboot. The time/date is set by GPS ... go outside under sky and start a GPS enabled activity (Run), wait for GPS Ready, and when you go back to the watch face, the time/date should be correct.

    Max


    Okay, I assumed it was syncing from the phone, but that worked. That's a step closer. Now I just need to sort out whether I'm going to have to turn off notifications. :-/
  • Former Member
    0 Former Member over 8 years ago
    I have the same problem after the latest firmware update.
    After the most recent batch of firmware updates, there have been a couple times when I got a flurry of notifications, after which the watch completely froze with a notification on-screen. The first time it happened, I left it on-screen a solid 10 minutes before holding down the power button 'til it shut down. On restart, the watch had lost its current time setting -- it was something like 13.5 hours off. I left it alone for a couple hours (with "set time automatically" toggled on), but it never updated to current localtime, even persisting through multiple sync cycles with my phone. I set the time manually so I didn't miss my wake-up alarm, went to bed, plugged it in to charge while I was in the shower, and when I got out of the shower, the *manual* time I'd set was wrong. So I toggled "set time automatically" back on and it flipped to current localtime immediately. :confused:

    The notification-flurry-freeze thing just happened again a little while ago, so I powered off the watch, powered it back on, and connected it to my PC/Garmin Express, thinking that might trigger a time sync. Nope. So I reset the thing to defaults, thinking there might be a bug caused by my watch face (Actiface) or one of the widgets I use. Nope again: When it reset, it still had the wrong time, even after re-pairing with my phone and syncing with Garmin Express.

    As I sit here, it's 3:16pm, but the watch says 5:48 am.

    Ain't nobody got time for this, right?

    Any ideas for how I can get a stable watch again?
  • Same problem here. Lockup on Notification screen has happened twice in two days. I am new the the FR235. It upgraded to 5.40 the first time I connected so I can't identify if this was a problem prior to 5.40.
  • I have had the same issue in the past fewweeks - probably 6 times or so.

    I started a service ticket with Garmin - hasn't went anywhere...

    But ironically I haven't had a lockup since.... :-) (week or more)

    I couldn't pin point it to an update of firmware, possibly an update to Garmin connect app (droid) and/or a little bit after a droid update to Marshmallow.
  • Former Member
    0 Former Member over 8 years ago
    I have had the same issue in the past fewweeks - probably 6 times or so.

    I started a service ticket with Garmin - hasn't went anywhere...

    But ironically I haven't had a lockup since.... :-) (week or more)

    I couldn't pin point it to an update of firmware, possibly an update to Garmin connect app (droid) and/or a little bit after a droid update to Marshmallow.


    Well, since I'm on iOS, I'm going to say it wasn't an Android update. No way of knowing how similar the codebase is for their Android/iOS apps, but I'm still putting my money on firmware.
  • Same problem here. Lockup on Notification screen has happened twice in two days. I am new the the FR235. It upgraded to 5.40 the first time I connected so I can't identify if this was a problem prior to 5.40.


    Since I posted this today, I have had two more lockups. When it happens, my Garmin is displaying an email notification; but I don't know how long it was displayed. I have been able to properly dismiss notifications when I catch them quickly after they are displayed. Maybe the problem is related to the length of time the notification is displayed before it is dismissed.
  • Lockups Continue

    Same problem here. Lockup on Notification screen has happened twice in two days. I am new the the FR235. It upgraded to 5.40 the first time I connected so I can't identify if this was a problem prior to 5.40.


    Lockup happened two more times for me today. I looked at the watch, saw the email notification message and the watch was locked up. I have had notifications since that and I have been able to dismiss them without lockup. The significant difference may be that I did not immediately respond to the notifications that resulted in a lockup...they may have been there for a long period of time before I looked at my watch and noticed them. The notifications that I have dismissed immediately have successfully disappeared without locking up the watch.
  • Have you tried a hard reset?

    CW