Performance metrics with Stryd footpod - bugs?

Anyone else noticed that vo2max calculation on fenix 5x is handled differently / or buggy when using stryd as source for distance and pace?

My threshold runs are in 4:10 - 4:05 min/km range with HR 168-172bpm. F5X was showing these values most of the time before I got Stryd. My vo2max level ranged from 56 (most of the time) to 58 after breaking PRs in 10k and half-marathon earlier this year.

Since I started using Stryd Fenix 5X stopped respecting it and begun to lower my performance.

No matter how long I run my LT sessions (4:10@172) garmin keeps saying my LT pace is 4:40@176bpm (makes no sense at all). Also since Stryd vo2max calculation dropped to 53-54 range without any visible signs in performace deterioration from my side. My workouts are now classified as unproductiove or recovery.

I'd say that there is something wrong with me, but I still run LT sessions at the same speed and HR levels as a month ago (before stryd).

Anyone else noticed something similar?

My setup:
F5x @ 3.30 production software
1sec recording, GLONASS OFF,
BT connectivity OFF (can't pair with my android device since day 1)

Stryd2.0 with datafield
FP autocalibration OFF
Distance: ALWAYS; Pace: ALWAYS (fp as source for both)
  • Former Member
    0 Former Member over 8 years ago
    The same happened already with Fenix 3 + Garmin Footpod (Pace: always, Distance: indoors): https://forums.garmin.com/showthread.php?353306-VO2-Max-and-Footpod11
  • Hi TH3ORETIKER,
    with F3 I've been using a regular footpod (garmin and a decatholon branded equivalent) and I don't recall to have problems with vo2max lowering without any visible cause (my injury for example).
  • Former Member
    0 Former Member over 8 years ago
    4200 for sale

    Hi,

    My input on the matter @
    https://forums.garmin.com/showthread.php?376533-F%C4%93nix-5X-%96-3-41-Beta-Release&p=987242#post987242

    Yes, same here...
    Thanks

    Anyone else noticed that vo2max calculation on fenix 5x is handled differently / or buggy when using stryd as source for distance and pace?

    My threshold runs are in 4:10 - 4:05 min/km range with HR 168-172bpm. F5X was showing these values most of the time before I got Stryd. My vo2max level ranged from 56 (most of the time) to 58 after breaking PRs in 10k and half-marathon earlier this year.

    Since I started using Stryd Fenix 5X stopped respecting it and begun to lower my performance.

    No matter how long I run my LT sessions (4:10@172) garmin keeps saying my LT pace is 4:40@176bpm (makes no sense at all). Also since Stryd vo2max calculation dropped to 53-54 range without any visible signs in performace deterioration from my side. My workouts are now classified as unproductiove or recovery.

    I'd say that there is something wrong with me, but I still run LT sessions at the same speed and HR levels as a month ago (before stryd).

    Anyone else noticed something similar?

    My setup:
    F5x @ 3.30 production software
    1sec recording, GLONASS OFF,
    BT connectivity OFF (can't pair with my android device since day 1)

    Stryd2.0 with datafield
    FP autocalibration OFF
    Distance: ALWAYS; Pace: ALWAYS (fp as source for both)
  • Today, during a track interval session of 15x 400m followed by 200m rest - vo2max calculation went up from 51 to 53.
    That's still a lot less than before stryd (56) but it's also 1st time I'm seeing an improvement, that could be related to the new beta (3.41) I installed yesterday. Anyone noticed similar behaviour?

    (I know changelog didn't mention any fixes here, but I assume there is some chance that they won't broadcast all fixes...)
  • Since nobody confirmed / denied I'd like to note, that again (on 3.41) my vo2max values got back to 56 during last week and look stable. First time I noticed them getting higher was after 3.41 beta that I still use.
    Anyone notices anything similar?
  • Hah. I found it at last. I have the same problem and contacted "heartbeat" I ran a half-marathon with 4:15 pace and 153 heart rate with my 80kg. VO2max should be over 52 and the threshold faster than 4:15. But the watch gave me 4:58 at 150 heartbeat for threshold and VO2max of 47. So I ran 12 minutes faster than the prediction.
  • To be honest, I think this issue was resolved a couple of firmware iterations ago - at least with regards to vo2max computation.
    On my end vo2max is now pretty stable and reflects the way I feel about my progress.

    LT pace and HR is a different story, as I fail to understand how this number is computed - a recent example: after a session of 6x1km followed by a 3min rest where intervals where ran at 3:30 - 3:40 min/km pace, with peak HR at 180 and my maxHR set to 195, LT pace came out at 4:18min/km and LT HR at 172.
    Maybe there is some logic, maybe there's not. There are days I can run at 4:10min/km keeping 172HR, and there are days where I struggle to force myself to keep 4:25.
  • Former Member
    0 Former Member over 7 years ago
    Reviving old thread. I do a lot of trail running under thick trees and at this time of year GPS+GLONASS on Fenix 5 is at best within 6% of distance and playing havoc with my PB’s so splashed out on a Stryd.

    Ran 2 x 10ks so far. Pace and Distance brilliant, distance within 1% of map measure.

    However first 10k F5 did not report Performance until about 20 mins into run and transpires even the GC post run graph does not start until 1/3rd way into run? Post run reported VO2 Max down a point 51 to 50 and unproductive (it was an unintentional PB and had more to give?!)

    Second run today and Performance kicked in where I expected just after 1Km at -9, yes minus 9. I’ve never seen less than -1 on any run at the start - and I was tempo running so at good start pace for me?! Post run ‘unproductive’ and VO2 Max down a further point to 49... Guess what - it was another 10k PB.. (consistent with training plan) and 3rd party apps accurately capture it as one of my highest performances to date...?

    Anyone any clue what’s happening (F5 APAC ver 8.0) I thought performance was pace and HR based - so in theory should be more accurate now??

    oh and my LT has updated and seemingly wiped all previous months LT data at same time...

    what a complete shambles...