Had a run with Beta 16.16 and Sensor Hub 28.11 - Impressions on HR

I had a 10k run yesterday with the latest beta that has a new Sensor Hub SW Ver 28.11. Rumours were that some of the OHR bugs would be fixed in this version.

I don't know if it was a fluke, but the OHR reading was all over the place. I've never experienced this type of cutouts or such a low HR reading for over 1km (see from km ~8 to ~9)

Previous betas were more consistent in OHR readings. Run conditions were the same as always.

Top Replies

socorsu over 1 year ago in reply to Vizi +4

Exactly, i used a F6Pro until October 23 and never saw these drops (and long one) or spikes with this watch.

Running with F7Xss 14.xx System software i never experience it, but since release 15.xx, 16…
Vizi over 1 year ago in reply to Fozzee1970 +3

Fozzee1970 said:
What OHR inaccuracies?

Inaccuracies reported in all those topics related to bad HR tracking in in Fenix 7 and Epix forums, which were closed without being actually resolved - those inaccuracies…
socorsu over 1 year ago +2

Hi, i created a Bug Report for spikes, you can do it for "long" drop.

This one should correspond to your issue, https://forums.garmin.com/beta-program/fenix-7-series/public-beta-reports/i/public…

All Replies

0 Dr Phil over 1 year ago

Beta problems for the beta forum

0 Adrian s over 1 year ago in reply to Dr Phil

By this logic we shouldn't even discuss the long standing OHR inaccuracies if that punctual discussion revolves around a beta version that was supposed to fix the said inaccuracies?

0 socorsu over 1 year ago

Hi, i created a Bug Report for spikes, you can do it for "long" drop.

This one should correspond to your issue, https://forums.garmin.com/beta-program/fenix-7-series/public-beta-reports/i/public-beta-16-xx/heart-sensor-failure-fenix-7-fenix-7-pro-during-activity

--- My Bug Report

https://forums.garmin.com/beta-program/fenix-7-series/public-beta-reports/i/public-beta-16-xx/whr---sudden-spikes-during-constant-effort-activity-run-in-my-case

--- Open discussion here with something interesting

https://forums.garmin.com/beta-program/fenix-7-series/f/community-discussion/357529/whr---sudden-spikes-during-constant-effort-activity-run-in-my-case

===> Interesting fact, FRxx5 or F7/E2 shared the Elevate 4 WHR , software for this sub-component is also the same WHR/BMX 15.5.0/15.05.00, i don't know if Sensor Hub is concerned but same situation with version 28.11.

---

https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-965/354823/heart-rate-bug---part-2/1719316#1719316

This bug has been escalated to the highest level. We have a fix in an upcoming software update, but I do not have a timeline for when it will be released unfortunately. I will update this thread once it's available. I'm very sorry for the frustration in the meantime.

---
https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-255-series/324326/erratic-wrist-based-heart-rate-bug-root-cause/1719498#1719498

All,

We have a fix for this bug but are still conducting tests. I'm very sorry for the frustration, but appreciate your patience as we get closer to releasing the fix.

0 Adrian s over 1 year ago in reply to socorsu

Thank you socorsu, I went ahead and updated the thread that applies to my issue!

0 Fozzee1970 over 1 year ago in reply to Adrian s

What OHR inaccuracies?

0 Dr Phil over 1 year ago in reply to Adrian s

Adrian s said:
By this logic we shouldn't even discuss the long standing OHR inaccuracies

The logic is that issues with publicly released software are best addressed here. Problems with beta software should be addressed specifically in the beta forum established to address problems with beta software..

Issues with WHR are longstanding and have been problematic for some people on every watch with OHR ever since OHR was introduced on a watch.

0 3959478 over 1 year ago in reply to Dr Phil

We believe we should not generalize this issue. The OHR on Garmin Watches is just too bad.

0 Dr Phil over 1 year ago in reply to 3959478

3959478 said:
The OHR on Garmin Watches is just too bad.

...for some. It works fine for others.

That's not denying the absence of a problem; it's not generalising the issue.

0 Vizi over 1 year ago in reply to Fozzee1970

Fozzee1970 said:
What OHR inaccuracies?

Inaccuracies reported in all those topics related to bad HR tracking in in Fenix 7 and Epix forums, which were closed without being actually resolved - those inaccuracies. Also, all those users reports of same nature in beta forums until now.

It seems that the idea is to ignore the issue but keep it look like it is not important issue by diverting users to beta forums where those reports are ignored, while in forum for stable software those topics are constantly being closed without actual resolution of the problem. Whenever someone reports a problem he is treated as if he should not have done so at all or have not done so at that place or whatever. All without actual reply on questions raised.

Dr Phil said:
Issues with WHR are longstanding and have been problematic for some people on every watch with OHR ever since OHR was introduced on a watch.

That is generalization, which conveniently disregards 2 important points:

1. some issues started appearing after software updates, which means HR algorithm was changed for the worse

2. users have been reporting significant inaccuracies in concrete workouts. These should not be constantly put aside and treated as general user issues but considered objectively and handled/fixed appropriately.

0 socorsu over 1 year ago in reply to Vizi

Exactly, i used a F6Pro until October 23 and never saw these drops (and long one) or spikes with this watch.

Running with F7Xss 14.xx System software i never experience it, but since release 15.xx, 16.xx(beta) system branch i have these issue.

I do not expect perfect WHR measures "perfection", even compared to chest strap, but consistency and avoid errors like those mentioned for a new generation watch