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.24][17.26] Lags, Freezes and missing data

3788518
over 1 year ago

Since the update to 17.24/17.26 my Forerunner 255 shows several bugs:

  • Starting the morning report today lead to extremely laggy behaviour. Every interaction/loading of a new page took minutes(!), with even getting stuck in the transition between the morning report pages (showing half of the previous page and have of the following page for a minute).
    After i got to restart it, it was working again, but i noticed the watch drained 28% of battery within less than 24h, with only a 20min activity tracked.
  • Some days before the watch froze completely upon starting the morning report and restarted itself.
  • Twice in the last days it lost data from the past night: heartrate, body battery and stress data is missing in Garmin Connect from exactly midnight until the first wake phase. HRV however is there.

Am I the only one encountering those issues?

  • 0 over 1 year ago in reply to 5559358

    Do you also have forerunner 255 music?

    -went for run

    -left phone at home 

    -Came back turned on bluetooth

    -To sync data. Data unable to sync

    -Watch restarts on its own on connecting with Bluetooth.

    -Steps miscalculations as it's not logging in or syncing steps after a walk or run with phone left home rewriting data overlapping missing data and giving false data

    -Data miscalculations

    This all happening to me

  • 0 over 1 year ago in reply to 8362088

    How about syncing with Wifi instead, to find out if this is a bluetooth issue?
    I don't use bluetooth, and my watch seems to have no issues at all.

  • 0 over 1 year ago in reply to ovekvam

    yea i did with wifi working with wifi but not bluetooth. Also i tried physically connecting watch to laptop in order to sync it failed to sync missing data. bluetooth and sync issue.

  • 0 over 1 year ago

    It’s a couple of days that problems seem recovered doing nothing from my side…

  • 0 over 1 year ago in reply to 6367814

    I took my watch to the Garmin centre they diagnosed the same issues that were being mentioned in this thread loss of data restart and drain of battery

  • 0 over 1 year ago

    Same for me, it freezes once a day or so and I have to restart it manually. Also seems to drain battery faster can a couple of days ago it went from ~40% to dead in a day.

  • 0 over 1 year ago

    Does the support center actually do anything to fix this since it seems like it's software related? I'm experiencing the same issues since the update and I don't want to waste my time for them to give me the solutions people are already doing in here since it's a workaround, not actually fixing the problem. I switched from fitbit to this and it really just regretting it because I had just battery drain, not the entire watch failing to operate. 

  • 0 over 1 year ago in reply to 2794843

    Nope mine would require a replacement it seems.

    They diagnosed hardware and software issues that are being discussed in this forum. 

    I am also thinking about a Fitbit now lol

  • 0 over 1 year ago in reply to 8362088

    Sounds like software to me, hardware is nonsense. sounds like a typical excuse for a software problem they can’t figure out. Had the same with faceid on my ipad a year ago after a software update. Sat at genius bar for an hour, they concluded the sensor was broken (which apparently happens easily, I concluded it must have broke one time when i dropped it). A year later i got an ios update and suddenly it worked again. "Hardware" problem was total bs, it was software all along.

  • 0 over 1 year ago in reply to 2148361

    Since it suddenly happens to a lot of people here, it is unlikely to be a hardware issue. It is not necessarily a bug in the new software, but it could be the rollout of the software that got some watches into an unfortunate state. It seems to be related to bluetooth communication. I don't use bluetooth, and I didn't have any symptoms yet. It could also be related to some IQ store addon that is not compatible. Maybe a watchface, app og data field.