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

Firmware 5.20 and current pace

Former Member
Former Member over 8 years ago
Hi,
Yesterday my watch has been updated to ver. 5.20 and today I made a small training.
And I noticed that the stability of the current pace value became definitely worst than before. Now it is rapidly changing +/- 30 sec/km or even more while I'm running in a constant pace. I was running in a good weather conditions and on the open area.
The current pace value was never perfect, but now it is completely unreliable. Fortunately the average pace is still OK and the accuracy of the track is also quite good.
Do you have the same?
  • 0 over 8 years ago
    Well even if not every single individual user uses this field, surely you'd agree that if you're Garmin pushing out this firmware update, "Current Pace" is something important enough to be worthy of basic testing. My point is that this is one of the most commonly used features on the watch, and this malfunction would be readily apparent after any basic testing. It's not a bug buried deep in the features or menus.


    Right. I would think everyone who uses a running watch for running would want to know pace as a primary field, whether it is current pace or average pace.

    Regardless, somebody at Garmin would have surely noticed it, I'm sure not all 630/235/230 customers who test this stuff ONLY use average pace. Personally I use both average AND current pace, which makes the current pace bug look even more broken, as I tend to be a very consistent runner when I settle into a pace.
  • 0 over 8 years ago
    ETA on fix?

    We appreciate the discussion, and have escalated this issue to the device teams for further investigation and resolution.

    We do apologize for any inconvenience that this has caused in the meantime.


    Is there an ETA on a fix for this (newly introduced) bug? Are we talking hours, days, weeks, months? Years? Decades? Centuries?

    As there is a work-around (revert back to older FW version), but it's time-consuming (no way to revert without losing all settings), it would help if we knew what sort of time-frame we are talking about... If a fix is coming tomorrow, I'll wait; if you're talking weeks, I'll revert. Of course, a smart and fast action would be to release the previous version as a 'new release', allowing your customers to revert back without losing data/settings; but at the same time I can't see this as being a complex fix either, you have a functional version (5.07) and a buggy version (5.20), and one visible parameter affected, it can't be so complicated...
  • Former Member
    0 Former Member over 8 years ago
    We have received word from the software teams that they have identified the root cause of the erratic pace issue, and have indicated that they are working on getting the fix released to production. Unfortunately, I do not have an exact time frame, but the team has indicated that they plan to release the fix as soon as possible.

    Just wanted to give everyone an updated on the information that has been provided to us.

    Thank you again for the discussion, and we do apologize for the inconvenience.
  • Former Member
    0 Former Member over 8 years ago
    A software update has been released to address the issue of erratic pace. Information and a link to the change log can be found in this sticky:

    https://forums.garmin.com/showthread.php?359080-Software-Update-5-40-Now-Available!
  • 0 over 8 years ago
    It might be the weekend before I get to try it out for myself, but I'm impressed at how responsive Garmin is to problems like this. It only took a week to get it sorted. Other companies might not be so quick.

    Thankyou Garmin.
  • 0 over 8 years ago
    Although I am a loud critic I too can say that this fast response was impressive. Bravo!
  • 0 over 8 years ago
    The good, the bad and the ugly

    The good:
    - Fast and timely communications on the issue - messages to acknowledge , indicate root cause found, and fix released, on 230, 235 and 630 boards;
    - Relatively fast fix release

    The bad:
    - Introducing such a bug at this point in the product lifecycle, on (as far as I can tell) the 3 core running products (230, 235, 630) on a core running metric...

    The ugly:
    - Letting anyone play in what should be "sacred code" - the path between the MediaTek GPS chip and the user - without thorough regression testing, and/or;
    - A regression testing process that does not sufficiently cover real-life situations to catch a bug that is readily apparent to most users.
  • 0 over 8 years ago
    Thank you for the fast resolution of issue and keeping us informed.

    I do hope that it is part of your job responsibilities (because otherwise it gives more credit to you personally, but really bad for Garmin).
    Thanks!
  • 0 over 8 years ago
    I tested it this morning. And with my FR235 everything is OK regarding this issue.

    My pleasure is back in the FR235. I used the instaneous speed to trigger alarms for to slow and fast and was getting mad of the many wrong alarms in the last week.
  • 0 over 8 years ago
    Problem still exists!!!!

    IMHO the problem still exists.
    I'm begginer, so set my training to 20 min in Z1. All the time watch was showing pace between 7:30 to 8:10, so imagine my surprise after the run, when the graph showed me that i was running from 6:47 to 9:26. Avarage pace was 8:22!!! How is this possible?