Related
Options
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

Heart rate low for first ~10 minutes of activity then jump

dosjlock
over 1 year ago

It seems others have a similar issues, but I'm posting here to give it further visibility and to show to very clear examples.

I've never had an issue with the heart rate sensor before, and in fact I've always been very impressed with its response.

But after the most recent update heart rate tracking is very unreliable during the first 10 minutes of an activity. Below are two examples: the first was a daylight trail run, and the second was a dark road run. I wore the watch in the exact same way as normal both occasions.

There is a big 40bpm jump in heart rate after about 8 minutes or so. The runs were steady - so this is just tracking error. The higher heart rate is correct, and what is usually recorded.

Just to emphasise, this has only occured since the most recent update so I am very inclined to believe it is software related. A fix would be most welcome - it is currently rendering many of the Garmin statistics useless.

  • 0 10 months ago

    Finally! I experienced it too during a very early run this morning...

  • 0 8 months ago

    I have the same problem. Please fix. First 10 mins or so heart rate is too low then jumps to correct level. 

  • 0 8 months ago in reply to 5827727

    Write to Garmin support requesting a fix, but do not hold your breath. They did not pay attention to numerous user reports about this issue for past 8 months. 

  • 0 8 months ago in reply to 5827727
    Vizi said:
    Write to Garmin support

    The only useful words.

  • 0 8 months ago in reply to Dr Phil

    Sharing relevant information to other users is useful to help them get the whole picture about issue at hand. But I understand that you have another agenda. 

  • 0 8 months ago in reply to Vizi

    Seriously???

  • 0 8 months ago in reply to gaijin

    Yes, I believe in providing all relevant information to users. 

    You and philipshambrook act as if it is isolated case whenever this particular HR issue is mentioned, despite knowing very well that it’s a common problem across various Garmin watches (epix, fenix 7, forerunners) and heavily reported by users in last 8 months after software updates in that period.

    Instead of feigning surprise and hiding relevant information (such as that this was not the problem before software updates), let’s focus on giving users honest and complete information about the issue. Only Garmin can fix this, so let’s stop playing around and be straightforward with those affected.