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

FR255: Name all current bugs you are encountering - Garmin, please fix!

rentagreement
over 1 year ago

Hi, 

I am quite frustrated about the massive amount of bugs the FR255 has even in the latest firmware. since so many bugs are listed in this forum in countless threads, lets list them here so that Garmin maybe starts working on them.

- Control Music on the Phone: Pausing the music stops the phone playing, but the music screen on the watch moves on, even jumping to next songs despite the music being stopped and not playing on the phone

- Workout App: Choosing a run daily workout suggestion opens the Strength App and not the Run app. I cant start the running workout and have to go via the Run App. This makes the workout App quite useless

- Workout Animations: After about 20sec the workout animation video gets stuck, and the screen backlight stays on for unlimited time. Only pushing a button reanimates the video until 20sec later it gets stuck again

- Breadcrumb Map: The planned route and the actual course you accomplished are overlapping in an unfortunate way, which makes the map rather unusable

- Wrist HRM: Is regularly way too low, up to 20bpm lower than a *** belt measures. Makes Training Status and other data unusable.

- Intensity Minutes: For no reason the watch adds up to 200 IM per day without me doing any considerable workout or even having nowhere close this high heartrate

...

  • 0 over 1 year ago in reply to ovekvam

    About that stress level.   How does it different from one watch to another ? Forerunner says I'm stressed a lot and yet my vivoactive says I manage stress quite well . Body battery drains a lot faster with forerunner since last update and yet vivoactive drains at normal pace .. 

  • 0 over 1 year ago

    Something very odd going on with mine, its either the HR reading itself or its using some strange conversion factor for loading.

    Base runs are being logged as tempo *despite* the auto description showing "base" on the name of activity.

    Figures all show zone 2 the entire time, 90%+ performance score.  BUT the pace is much faster than normal.

    So either the HR readings displayed are too low but internally its using a more real, higher figure to calculate loading or there's some other bug.

    Either way its pretty unusable for me now as i cant get any low aerobic logged at all, my steady runs are threshold and so on.  Makes all the training and condition features absolutely, utterly useless.

  • 0 over 1 year ago in reply to RDW

    I have something similar going on - in that I also have been unable to get any low aerobic logged, even when doing "Base" runs. In my case, though, the runs definitely *feel* like they're low Zone 2 difficulty, and should be logged as "base" and not "tempo".... and yet they're persistently logged as "Tempo", contribute zero low aerobic and are classed as being firmly in Zone 3, which they don't feel like *at all*.

    I'm not sure precisely where things are going wrong, but it's good to know it's not just me.

  • 0 over 1 year ago in reply to aoanla

    I did another test yesterday.

    Did a run at my known base pace.  This time the execution score was only about 10% and the HR displayed 10-15bpm lower than it should be.

    So its a zone 1 run on the display.

    Watched logged it as a good score base run as if all of it was in zone 2.

    Contrast to my previous runs maintaining base HR instead where (i) its faster than base for sure and (ii) it all shows as tempo.

    Since 16.19 something is very wrong with the wrist HRM here.  Its displaying and logging a HR lower than it should be during exercise but seemingly using a different, more accurate figure to calculate training load.

    Obviously the effect of this is all calculations on load, training focus, VO2 Max, race predictions, Fitness age and so on are going to be utterly inaccurate and unusable.

    This is a 16.19 firmware issue for me - it started with that update and persists with it.  Even after resets.