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

Bug in Benchmark Run / interval pace calculation

flocsy🤠
over 2 years ago

Both in the 1st and 2nd run the Average Pace of the run (the 1st line of the lighter gray blocks) is totally incorrect. When you look at the 2 lines below you see that the total Average is about half of what it should be: 1st km: 4:58, 2nd "km"**** 4:35. Now I think the bug in GCM android is that instead of calculating the total average pace of the 1st run by dividing the total time (5:00) by the total distance (correct value: 1.01km as it is written) it divides by 3km. So the 2nd "lap" which was just 10m is calculated to be 1km. The exact same can be seen on the 2nd run.

BTW: the same is correctly displayed on the web, so this is definitely a bug in how GCM android displays it

  • 0 over 2 years ago

    Garmin!??!?!?!? Why? Why???? Why you employ such untalented customer support agents????? Why?

    It's blowing my mind again and again! Im trying to help, I'm taking a screenshot when I see an obvious bug, I'm explaining it, it seems like an easy thing to fix, and then I go to the Customer Support website to report it, ad the (sorry, but I have no other words) stupid agent doesn't even read what I am reporting, just asks what is my device's serial number. At the moment I sent him he didn't say a word, and within 3 seconds he "transferred me to the Fenix team, because I reached the Forerunner team".

    So 1st of all let me add another bug: when I report "Garmin Connect Mobile" related bug in the Customer Support website, why am I connected to Forerunner team? Ah you don't have an Android or CGM team? Yeah, unfortunately we, the users can feel that...

    And why can't I contact you by email when I chose "Garmin Connect App"? This alone would force me to find a "workaround" and report it as Fenix6 bug by email, and of course the stuff that responds to the chat just makes it more obvious that next time I'll go straight to the fenix page and report it by email not to encounter this nonsense chat...

  • 0 over 2 years ago

    Hello, I'm sorry for the misleading queue that you were sent to, but it is often normal to be transferred to whichever department your device is associated with. We like to get you to the correct department right away, just in case you have any other bugs that are device-specific. Regardless, I am happy to help you with this report. May I have permission to reach out to you via email so I can create a case, so you can then be personally notified when there is a resolution?

  • 0 over 2 years ago

    I do have the same bug for weeks.

  • 0 over 2 years ago

    I confirm the bug. The same behaviour I see already several weeks in many differnt forms of running training.

    With 0.25 Min / km I would be outrunning my car on the highway.

  • 0 over 2 years ago

    I have same issue on moblie Connect app, web Connect don't have the issue.  I'm using forerunner 255.

  • 0 over 2 years ago

    All,

    We have been able to reproduce this internally and are currently looking into a resolution for this disruption. Once we have any updates, I will be updating this thread.  At this time, no further information is necessary. Thank you for your patience while we work on this disruption.

  • 0 over 2 years ago in reply to 2391421

    Try landscape mode 

  • 0 over 2 years ago in reply to Yury

    Interesting. In Portrait the mobile app shows 0:19, and in Landscape the correct 4:09