For activities like cyclists, my Fenix only shows the right pulse when I start an activity on the watch. If I don't do this, the pulse will remain 40-50 beats below the actual pulse.
Why is that so, someone can enlighten me.
For activities like cyclists, my Fenix only shows the right pulse when I start an activity on the watch. If I don't do this, the pulse will remain 40-50 beats below the actual pulse.
Why is that so, someone can enlighten me.
Ok thanks, that's interesting. This means that if I am very active due to my job, i will never be shown the correct heart rate. Then the Fenix 6 as a fitness tracker is completely pointless, then all…
Last week I had a treadmill walk/run of 1 hour. 6X OHR tracked very well with a chest strap paired to my 5X+
Following that activity I stopped recording, but started another run/walk with the 6X on the…
writing this is plain useless. the sampling rate may be less frequent outside of an activity, but if the WHR delivers totally wrong and way to low results it is simply not working, e. g. useless.
if the…
Yes, the error also occurs with 7.78 beta
Are Garmin developers reading these forums at all or should we all just send bug report to them?
I've also been discussiing with Garmin support but they are just playing dum and not seeing or admitting the issue.
I think the best way is to send a bug report.
And normally we should have to return the clocks.
Are Garmin developers reading these forums at all or should we all just send bug report to them?
Many people have already sent bug reports, but it doesn't hurt to send your own so that they have more data available to help resolve it.
What doesn't help is posting thread after thread (after thread after thread after thread after thread after thread after thread after thread after thread after thread after thread after thread after thread after thread after thread after thread after thread after thread after thread after thread after thread after thread after thread after thread after thread after thread after thread after thread after thread after thread) about this problem, which only serves to annoy all the other Fenix 6 owners who are trying to use the forum for giving and receiving advice and tips.
I realize the person who started this thread is probably only here for the first time and didn't know about the countless other threads and posts about this, but a quick browse through the first page or two, or using the search bar, would have saved him a lot of typing, and saved the forum from getting further crudded up by something that's already been discussed relentlessly.
Why is it so?
The OHR samples more frequently (and therefore is likely to have better accuracy) in Activity mode than it does in 24/7 mode. Peek under your watch as you open an activity and see for yourself as the OHR changes from strobing to pretty much solid. Of course, this more frequent sampling does use more battery.
You don't actually need to start an activity, just opening it is enough. If you don't need GPS, you could copy and rename an Indoor activity.
writing this is plain useless. the sampling rate may be less frequent outside of an activity, but if the WHR delivers totally wrong and way to low results it is simply not working, e. g. useless.
if the sampling rate is that low, they should simply disable the WHR outside of activities and remove the measurement of stress, body battery, sleep, activity minutes and more.
even if the heart rate is not read as often, it would have to adjust until it finally shows the correct value. But it sinks again.
Even with a long load, it does not achieve the right value.
In the attached video on the left hand Fenix6X on the right Fenix5X
and in the middle Edge using HRM-Run.
The OHR samples more frequently (and therefore is likely to have better accuracy) in Activity mode than it does in 24/7 mode. Peek under your watch as you open an activity and see for yourself as the OHR changes from strobing to pretty much solid.
by the way, the 5x did not behave differently. In contrast to the 6x, the 5x was able to track the heart rate well even outside of an activity. You can see that in the video above.
further f6x test here:
I'm sorry that you feel that trying to educate and understand the root cause of problems, or even actually answering the OP's explicit question is useless.
I know I am old school like that, and completely behind the times.
I should get with the fact that maximum outrage is the only acceptable response,.
Probably you already answered it somewhere - but again te question: did you informed / open a bug / ticket officialy by Garmin or you just post it here?
Asking cuz I'm on the way to open a ticket for the same issue and would like to mention the issue number if they already exists.
To the others - for the most user is such a behaviour (wrong WHR outside an activity on high(er) load) not a deal breaker due it is a simple workaround to solve it, but it's feeling "wrong" that Garmin added a "battery saver feature" (if that was really the intetion) and changes the basic behaviour of the Fenix line.
My "problem" is that the HR drops "rapidly" after an activity - eg. running, end with 160+, stop the activity and proceed with a "cool down walk", the HR drops quite immediately to 70-80 and start slowly to raise to 100-110 in 10 minutes, when I start an activity it jumps immediatley to the correct level (over 100).
Last week I had a treadmill walk/run of 1 hour. 6X OHR tracked very well with a chest strap paired to my 5X+
Following that activity I stopped recording, but started another run/walk with the 6X on the watch face. For the first five minutes the 6X was nowhere near the correct figures, but then it closed the gap quite well for several minutes before I returned to walking to cool down. Once walking the numbers from the 6X became more and more absurd, reaching a low point of 50 BPM while I was still walking and had a true heart rate above 110. I can't present a graph, as there is no recording fit file, but here is a photo showing the ridiculous value on the 6X vs reality. This was towards the end of 27 minutes of continuous run followed by walking.
I reported the problem to Garmin in December. It is my video linked earlier in the thread. Garmin does not dispute the problem, but also has no solution to offer.
The watch is simply wrong. It needs a fix and it needs people to report it to Garmin to gain the traction it deserves.