After update to 5.0 WHR is Trash!

EDIT: 5.74 beta fixed my problem. Now my Fenix 6X Pro is great again. Thanks.


Guess what... After 5.0 firmware update my Fenix 6X Pro WHR is trash. It was working fine. Now, I not only have Allalin72 problem, but HR overall is a "random number generator" as someone wrote on this forum.

Video showing that problem

https://youtu.be/itScQILQYlo

The data:

FM: 5.00 /// GPS: 2.60 /// Wi-Fi: 2.60 /// WHR: 20.04.50 /// ANT: 4.30 /// Sensor Hub: 3.10

The data is compared to Apple Watch 4 paired with Garmin HRM Dual or with builtin AW WHR.

About 24/7 WHR widget:

It's inaccurate like hell! Not going above ~110 BPM. But that is not the worst thing... I've noticed that that during the day my HR is quite different on F6 and on AW. F6 is showing 90, AW 60. Quick check on my neck... Yeah... It's ~60. And this is repeating all day. 

So today im wearing ALL DAY my HRM Dual paired with AW. When you pair a HR strap to AW, the WHR is off all day. Its taking all the data from HRM Dual and display it constantly (1 sec) on my watch face. What I'm seeing is little bit sad. 90% of the time it's different at least 10 BPM. Funny thing is for example - I see 90 BPM on F6, 74 AW - run downstairs and back - F6 60 BPM. AW 110 BPM :D.

So to sum up - not only it's not going above 110 BPM, it's inaccurate like hell. It's only good when I sleep.

EDIT: Half day - F6 and AW+HRM Dual. Not even close... :(

About Activity WHR:

It was great for me. Now I have differences of 60 BPM! Take a look at that nice example of 1k walk with a stop in a store. AW+HRM Dual is spot on (orange). Im mad like hell!


EDIT: changed it to view by duration, not km

Firmware flashed again, watch wiped 3 times... nothing works. This is the case with Walk, Run, Bike, Cardio...

Couple days ago I was showing Allalin72 how not all devices have hisbug. One update was enough to make my F6 worse than my mothers in law Mi Band 4.

BUT NOT ALWAYS

Today my Fenix was performing excellent on a walk with my little daughter.

There was a lag, but that's how all WHR work, so no problem here. F6 had two "hang times", but in recovered quite quick.

This is a walk in the city, so my pace is not consistent. Couple of times I intentionaly slowed down, to seatle my HR and speeded up. Beside that two times F6 WHR was great. At the end I've ran. F6 picked that right away.

So yeah... I'm certain if I would run with a stedy pace that HR graph would be nice and clean. Average pace from F6 and chest strap is the same - 130 bpm. So for me, thats EXELENT for na WHR.

Beside that (it was very cloudy):
GPS: EXELENT (AW was wrong)
Instant pace: EXELENT
Distance: EXELENT 
Elevation: VERY GOOD

  • If there was a tolerance specified for the OHR sensor, let's say within +-10-20%, users could choose their watch based on this and the expectations would adjust to these values.

    This is impossible because of the several variables already mentioned.  No company can or would be willing to make such a statement because of all the variables.  What may be within + or -20% for me may be + or - 40% for you.

  • Glad I could bring a few joyful tears to someone.  Trying keep it real here.   Seriously though.  I know @Allalin72 and many others are experiencing frustrating issue.  I really really hope they get fixed soon.  It stinks to pay out $800 or more for a watch that has issues.  

    If you've had prior Fenix watches though, you'll know this is sadly how it goes.  Get the watch to market quickly.  Then spend 6 months in frequent firmware updates to stabilize it.   Then 15 months into the product cycle the development staff shifts to the next watch iteration and updates greatly reduce.


  • One update was enough to make my F6 worse than my mothers in law Mi Band 4.

    I don't have MiBand 4 but I managed to find my old MiBand 2.

    So let's compare.

    Left to right: Garmin Fenix 6X Pro, MiBand 2, Amazfit Stratos (connected to Polar H10 chest strap).

    Results:

    After starting activity on Garmin:

  • This is one example of my OHR testing with Fenix 6x Pro Solar.

    I started the workout with OHR, then switched to HR strap and at the end switched back to OHR.

    Initially OHR was 20-30 beats too high.

    In the middle the HR strap is correct.

    At the end, after disconnecting HR strap the OHR shows 20 beats too low and then after a small stop it went 20 beats too high.

    This is the same run recorded with FR945 using HR strap.

    I reported this to [email protected] as suggested.

  • Former Member
    0 Former Member over 5 years ago in reply to jetguat

    Yes. Experienced this with my F3HR. 

    then they said I can‘t get no new features because of a new garmin OS. And raised the Price for the F5 laughable high. 

  • Former Member
    0 Former Member over 5 years ago

    Hi,

    Today I was at my indoor cycling training and I have my Fenix 6 pro on hand with WHR and Suunto HR Strap on screen in my fitness club. My watch band was fasten really tide.

    I'm very dissapointed how bad is F6 WHR :( 

    Looks at screens below, it's the same ride from today, on fenix it looks totally different, most of time Fenix was around 40-50 bpm lower than HR Strap! During whole workout HR on Fenix jumps suddenly from 70 bpm to 120 bpm a then down to 80 bpm. It's ridiculous!

    Avrage HR: Fenix6 91bpm, HR strap 146bpm

    Max HR: Fenix6 130 bpm, HR strap 167 bpm

    Before I had Fenix5 and WHR was really good, now I paid additional 300Euro for this SH*T!

    Shame on you GARMIN! FIX IT!

    GarminSuuntoGarmin

  • Hi,

    I personaly have the "WHR way to low outside an activity profil" problem. But when i start an activity, here an indor bike activity, everything perfect.
    I have just noticed that there is two activities that show me wrong WHR indication : Hiking and Backcountry skiing. On those two, it seems that the WHR works just like the Wiget.


  • Former Member
    0 Former Member over 5 years ago in reply to kekelamalice

    I have observation that in run activity HR works better.

    Today i will go running with F6 and vivoactive3 na wrist. I will compare it and share here.

  • Please test what the optical sensor shows if you have not started an activity profile.