Related
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

[17.26] Reboot after notification arrives

Attila_Molnar
over 1 year ago

I have realized that the watch reboots accidentally when notification arrives. Not every time, but randomly mainly few times per week. Very annoying.

  • 0 over 1 year ago in reply to Garmin-Sierra

    I am also facing this problem. I usually sync my watch right after a workout. After a few seconds of completed sync and a few notifications, my watch rebooted. Fortunately, the workout data is intact, but there's a gap of blank data from the last time I synced until the point of my latest sync.

    1. Yes
    2. Yes
    3. Malaysia
  • 0 over 1 year ago

    Also have his issue. Been happening ever since the update. Seems to only cause crash when the notification is shown on "full screen" and has never caused a crash when showing a "minimised" notification during an activity but I'm always terrified to expand a notification during an activity as would be a bit of a gamble on whether it will crash and restart. 

    My device has never successfully shown any image in notification. Normally just missing or represented by an "X".

    1 Yes

    2 Yes

    3 UK (England)

  • 0 over 1 year ago in reply to Garmin-Sierra

    I'm having the same issue. Reboots randomly after 17.26 update. I think the reboot coincides with a notification, but I don't see any pattern to which notification (if any) is triggering it.  When the reboot happens, there end up being gaps in the stress, heartbeat, body battery data in the Connect app.  Usually the gap is a few hours long. Probably the length of time since the watch tried to sync with Connect.

    1. Yes
    2. Yes.
    3. USA

  • 0 over 1 year ago

    Hi, I have the same issue

    1. Yes

    2. Yes

    3. US

  • 0 over 1 year ago in reply to Garmin-Sierra

    any resolution yet?

  • 0 over 1 year ago in reply to Mus

    Not yet, it is still under escalated investigation. It looks like we are making progress though, and I apologize for any frustration caused by this disruption.

  • +1 over 1 year ago

    All, 

    Thank you very much for your patience as we investigated the reboots. We now have a fix that should be included in our next software release. I will post again when it's released, or if there is a beta that includes the fix as well. 

  • 0 over 1 year ago in reply to Garmin-Sierra

    Wonderful news! Thank you for keeping us updated during all this! Is there an estimate on when the next software release will happen?

  • 0 over 1 year ago in reply to andrew.mccaffrey

    You're welcome! I don't have a timeline for the release at the moment, but I will update this thread once it's available!

  • +1 over 1 year ago

    All, 

    We have released a fix for this disruption in the 18.15 beta software release which is currently in a 20% phased rollout. This will only work for Wi-Fi compatible devices that have a Wi-Fi network currently set up on the watch (the non-music FR 255 and FR 255s are not supported).

    If you do not wish to enroll in beta, feel free to wait until the live software version is released. I do not have a timeline for that release date at the moment.

    If you are still experiencing freezing after 18.15, please start a new thread on the main FR 255 channel.

    Thank you very much for your patience as we investigated.