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

Software Version 8.00

4 hours ago is available new software, but via cable i can't download still not visible for me via Garmin express webupdate , mobile app.
My watch is no APAC so should be visible. How long should I wait?
  • msgl,

    In order, I'd suggest trying:

    * removing any custom watch faces
    * checking your backlight settings
    * powering down, then back up (this can clean up any looping code that can be left after an update).
  • Former Member
    0 Former Member over 7 years ago
    Until the update, the resting HR seemed to be calculated by getting the lowest average HR over any given 60 second or so period.

    Now, it appears to have changed to take an average over a very long period (assuming an hour or more).

    So mine has jumped from an average of 41 for the month, to 58 today. I'm sat at my desk, occasionally walking around, doing my job and talking but all of this activity seems to be counting towards my 'rest' HR calculation.

    Presumably even strength exercises (planks for example?) will be included since there is no perceived movement.

    This seems completely wrong to me. But again, I'm assuming others are getting the same... if you aren't, do let me know!


    I have the same issue, and I think your analysis of the change could be correct. Very annoying and not in line with their documentation. (Which is here: https://support.garmin.com/faqSearch...Jd5PG0DR9ICV3A)

    Edit:

    Hmm, perhaps I was too soon with my conclusions. The RHR of both yesterday (looked at the all-day heart rate graph again) and today have been updated to more reasonable values after all. I did nothing to resolve this (no changes to HR zones, no resets, no power cycles, etc.)
  • Maarten_s,

    Thanks for confirming. I created a thread on this on the Fenix 5X forum if you are interested and want to chip in.

    Seems to be affecting only those who don't wear their watch to bed (daytime averages).


  • After 6 days I can say for me works ok after cleaning like already mention before . Only wait for first LTHR detection .
  • Former Member
    0 Former Member over 7 years ago
    Until the update, the resting HR seemed to be calculated by getting the lowest average HR over any given 60 second or so period.

    Now, it appears to have changed to take an average over a very long period (assuming an hour or more).

    So mine has jumped from an average of 41 for the month, to 58 today. I'm sat at my desk, occasionally walking around, doing my job and talking but all of this activity seems to be counting towards my 'rest' HR calculation.

    Presumably even strength exercises (planks for example?) will be included since there is no perceived movement.

    This seems completely wrong to me. But again, I'm assuming others are getting the same... if you aren't, do let me know!


    mine did not change too much, just +- 1 or 2. The difference is, before updating to 8.0, it usually have a new number for a day not too long after 12:00 am, and it will change during the night. Now I can't see a new number until 7:00 am. I think it depends on when you get up. I usually get up around 7 am.
  • Former Member
    0 Former Member over 7 years ago
    After each firmware update I remove and then pair again my F5 and Stages in the hope Garmin has given me back some connectivity. They connected when I first got my F5, and I gained a FTP and w/kg score but after an update last year I haven't been able to maintain a connection unless they were virtually touching.
    Well tonight I followed my usual procedure after updating to FW 8.0 and I'm a little bit excited, not only did they pair and remain connected even when I stood up but I managed to walk a couple of steps away from the bike and my F5 said it was still connected.
    Tomorrow morning will be the true test when I cycle to work. Maybe FW 8.0 is lucky for me.
  • Former Member
    0 Former Member over 7 years ago
    msgl,

    In order, I'd suggest trying:

    * removing any custom watch faces
    * checking your backlight settings
    * powering down, then back up (this can clean up any looping code that can be left after an update).


    Yeah..nah, no luck with that, don't have any custom watch faces and powering down/up is not a problem since the watch runs out of battery every 8hrs, backlight is working as normal, thanks for the suggestions anyhow. I guess next step is to try a factory reset but it's so annoying to have to change all the settings again.
  • My point with the backlight is not whether it is working "normally", it is how powerful it is. Each 10% of backlight burns 1.5-2% of battery per hour. If you are running the backlight at 100% rather than the default 20%, and regularly activating it via gesture or key press, then it will suck the battery, even if the backlight is working exactly as you have it set up.

    Of course, the problem could still lie elsewhere. If a factory reset doesn't solve it (last resort giving having to change the settings), then it is time to contact Garmin Support.

    Edit: Perhaps also try removing/re-pairing the watch with your phone, and resetting the wifi (if Sapphire).
  • Former Member
    0 Former Member over 7 years ago
    Maarten_s,

    Thanks for confirming. I created a thread on this on the Fenix 5X forum if you are interested and want to chip in.

    Seems to be affecting only those who don't wear their watch to bed (daytime averages).


    Saw the thread there as well indeed. However, after 3 days (updated on Sunday) and looking back at the graphs I think the 'error' is not as big as a previously thought. [TABLE="align: left, border: 1, cellpadding: 5"]
    [TR]
    [TD]Day[/TD]
    [TD]RHR[/TD]
    [TD]Lowest on All-Day HR graph*[/TD]
    [TD]Delta[/TD]
    [/TR]
    [TR]
    [TD]Thursday (v7.60)[/TD]
    [TD]36[/TD]
    [TD]39[/TD]
    [TD]-3[/TD]
    [/TR]
    [TR]
    [TD]Friday (v7.60)[/TD]
    [TD]33[/TD]
    [TD]37[/TD]
    [TD]-4[/TD]
    [/TR]
    [TR]
    [TD]Saturday (v7.60)[/TD]
    [TD]38[/TD]
    [TD]39[/TD]
    [TD]-1[/TD]
    [/TR]
    [TR]
    [TD]Sunday (v8.00)[/TD]
    [TD]50[/TD]
    [TD]43 (this caused my concern)[/TD]
    [TD]+7[/TD]
    [/TR]
    [TR]
    [TD]Monday[/TD]
    [TD]44[/TD]
    [TD]42[/TD]
    [TD]+2[/TD]
    [/TR]
    [TR]
    [TD]Tuesday[/TD]
    [TD]42[/TD]
    [TD]40[/TD]
    [TD]+2[/TD]
    [/TR]
    [TR]
    [TD]Wednesday[/TD]
    [TD]54[/TD]
    [TD]49[/TD]
    [TD]+5[/TD]
    [/TR]
    [TR]
    [TD]Thursday[/TD]
    [TD]47[/TD]
    [TD]46[/TD]
    [TD]+1[/TD]
    [/TR]
    [TR]
    [TD]Friday[/TD]
    [TD]52[/TD]
    [TD]35 (43) lowest could be error[/TD]
    [TD]+17 (+9)[/TD]
    [/TR]
    [TR]
    [TD]Saturday[/TD]
    [TD]54[/TD]
    [TD]47[/TD]
    [TD]+7[/TD]
    [/TR]
    [TR]
    [TD]Sunday[/TD]
    [TD]47[/TD]
    [TD]46[/TD]
    [TD]+1[/TD]
    [/TR]
    [TR]
    [TD]Monday[/TD]
    [TD]51[/TD]
    [TD]36 (48) lowest could be error[/TD]
    [TD]+15 (+3)[/TD]
    [/TR]
    [/TABLE]



























    Note that the All-Day HR Graph in both Garmin Connect Mobile and Web show a 2-minute interval - this can be the cause of a delta in the RHR (1-min interval) and what we can see/determine from the graph.

    I'll keep monitoring this to see how it develops. But from what I see now, it appears that the algorithm may have been too kind before (v7.60), and is now a little bit too strict (v8.00).
  • I am seeing the following (since 8.00): [TABLE="border: 0, cellpadding: 0, cellspacing: 0, width: 279"]
    [TR]
    [TD="width: 75"]Date[/TD]
    [TD="width: 128"]Lowest Recorded[/TD]
    [TD="width: 105"]RHR (Garmin)[/TD]
    [TD="class: xl64, width: 64"]Delta[/TD]
    [/TR]
    [TR]
    [TD="class: xl63, align: right"]20/02/2018[/TD]
    [TD="align: right"]44[/TD]
    [TD="align: right"]54[/TD]
    [TD="class: xl64"]+10[/TD]
    [/TR]
    [TR]
    [TD="class: xl63, align: right"]19/02/2018[/TD]
    [TD="align: right"]46[/TD]
    [TD="align: right"]52[/TD]
    [TD="class: xl64"]+6[/TD]
    [/TR]
    [TR]
    [TD="class: xl63, align: right"]18/02/2018[/TD]
    [TD="align: right"]43[/TD]
    [TD="align: right"]50[/TD]
    [TD="class: xl64"]+7[/TD]
    [/TR]
    [TR]
    [TD="class: xl63, align: right"]17/02/2018[/TD]
    [TD="align: right"]46[/TD]
    [TD="align: right"]50[/TD]
    [TD="class: xl64"]+4[/TD]
    [/TR]
    [TR]
    [TD="class: xl63, align: right"]18/02/2018[/TD]
    [TD="align: right"]45[/TD]
    [TD="align: right"]58[/TD]
    [TD="class: xl64"]+13[/TD]
    [/TR]
    [/TABLE]