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 4040642

    Sounds like your watch is stuck in some loop. My watch does not have the symptoms, and probably not the watches they use for testing at Garmin either. I would suggest to try to compare your settings, to see if you have some setting or use pattern in common. That can pinpoint where the bug is, to make it easier for Garmin to fix it.

    Have you tried to switch off bluetooth during the night, to see if the bug goes away?

  • 0 over 1 year ago

    I have similar issues since 17.26 a few days ago. Now every morning I click the light to see the time and the whole watch freezes. I have to restart it to use it. it does seem to be vaguely functioning behind the frozen UI thread because I connected with connect app and the heart rate changed even though clock face was frozen.

    I have also noticed a big increase in battery drain and frequently more lag than prior to this update. Battery is now reducing 10% per day with little activity recorded - it used to last a month, looks like tis now barely a week

    I am pretty sure I have lost data too - I can see the morning report values on the app and they are the very outer limit of plausible.

    I have a forerunner 255 Music

  • 0 over 1 year ago in reply to 7909073

    To add some more data from my side: 

    • I have a forerunner 255S music
    • I see no gaps in the heart rate data on Sunday and Monday. The freezing of the UI during the morning report, and the massive drop in battery from 96% to 34% in one day, was seen on Monday morning
    • It does not happen every morning. This morning my battery was at 24% and the watch face UI was reponsive and normal during the morning report
    • This has happened at least two other times in the last week, although I did not document exactly which days nor did I document if there were big battery drops correlated with the UI freezes. 

    I will continue to document my symptoms by posting in this thread. I will not make any changes like turning off bluetooth until I have a clear baseline of how often this happens and if I can find any correlations with other things I do with the watch. 

    I will also make a video next time it happens and post it on youtube so that people can see clearly the symptoms with their own eyes (my experience with humans is that sometimes you need to see it to believe it...)

  • 0 over 1 year ago

    My wife has the same issue with her 255s

  • 0 over 1 year ago

    What kind of phone do you have the watch connected to?  I wonder if there's anything common there with the folks having problems.

    My FR255 doesn't seem to have any problem with data collection or syncing, but I normally have the bluetooth disabled on the watch (and phone) except when I intend to sync every week or so.  My watch was last charged 6 days ago and is at 61% battery, with about 5 hours of GPS activities since charging.

  • 0 over 1 year ago

    I haven’t had the battery issues, but I have had gaps in heart rate, body battery, and steps, but not on any pattern. On the first update, probably 17.24, the watch froze and rebooted itself, I lost a bunch of steps and for most of the remainder of the day the steps on the watch and the app were out of sync. It eventually synced up, no idea how. 

    this morning, I have a couple of hours of gap in data, which is annoying. 

  • 0 over 1 year ago

    Battery seems worse than usual, which kinda sucks but that's really no big deal, but no other problems you mentioned here on my 255M, morning report is nice and smooth, and all data is intact.

  • 0 over 1 year ago in reply to jerrymk

    Update from today on my symptoms on my 255S Music:

    The UI was repsonsive this morning (it did stuff when I pushed the buttons) but woke up to a battery warning. Battery was at 22% last night at midnight, and at 7 am this morning battery was down to 2%. 

    (It sounds to me like there is a process in the software on the watch that occassionally gets stuck into an infinite loop, sucking battery and causing UI to become unreponsive. That would be my guess, in case any garmin software developers are listening.)

  • 0 over 1 year ago in reply to 2148361

    20% in half a day? That'll only last 2.5 days, that's unacceptable

    Mine is now at 52% after I charged it to full last Saturday, and had about 2 to 3 hours of workout with multiband GPS. Not perfect, and that just won't last 14 days as advertised, but it's... fine. Not sure what else under the hood has been changed for the version 14 update. The actual new feature, nap detection, doesn't seem all that useful. I do set nap timers, and that starts a nap perfectly, but I can't extend the nap time if I decide to keep sleeping. Body battery doesn't seem to reflect the benefits of the naps. (Usually +0 or +2).

  • 0 over 1 year ago in reply to jerrymk

    Remember that +0 is also a benefit, since the body is usually decreasing during the day if you aren't resting.
    My watch does not seem to have increased battery consumption after the last few firmware updates. If yours does, it is probably getting stuck in some unintended loop of some sort. Maybe it desperately tries to connect to something that is unavailable, or some software from IQ-store is no longer compatible.