VO2 Max

Like I said earlier, I don't use a treadmill, but according to Garmin it should work.

https://support.garmin.com/en-US/?faq=lWqSVlq3w76z5WoihLy5f8&productID=571520&searchQuery=Vo2%20max

Using the Treadmill app will certainly not generate a VO2max value (or performance condition, or LT value or any other physio metric for that sake).
The F5+ doesn't calculate VO2max for other activity types than Run and Cycling and I guess there's still one combination I haven't tried, which is the native Run app with GPS disabled and Stryd enabled. I'll try that tonight.

Also, I haven't tried running outside with GPS disabled (I like to get the trace on map recorded even if I use Stryd for pace/distance).

Also, I haven't tried running outside with GPS disabled (I like to get the trace on map recorded even if I use Stryd for pace/distance).

I also use GPS for the map tracing while Stryd reports pace and distance. I've had my Stryd for 6 weeks and I don't recall getting any VO2 Max updates during this time. Are you getting updates using it this way?

Native run app with disabled GPS while using Stryd does not generate VO2 max. I tested it on treadmill with FR 645 and Stryd.

TMK17:
I use Stryd as pace and distance source, while GPS is enabled for map. VO2 max is updated whenever VO2 max changes significantly. (VO2 max is a number with decimal places, but shows as integer number in Garmin)

I also use GPS for the map tracing while Stryd reports pace and distance. Are you getting updates using it this way?

Yes I do, however I suspect that it's GPS pace that goes into the algorithms regardless of foot pod settings. This was "confirmed" by running on treadmill with GPS enabled, which did not give any Firstbeat metrics.

Native run app with disabled GPS while using Stryd does not generate VO2 max. I tested it on treadmill with FR 645 and Stryd.

I tested this on the treadmill tonight and found the same as you. This will also mean that running outside without GPS will also not trigger any FirstBeat calculations.

VO2 max is updated whenever VO2 max changes significantly. (VO2 max is a number with decimal places, but shows as integer number in Garmin)

VO2max doesn't need to change significantly to get an update. I get updates regardless of change in (whole number) value, and this can be seen if you look at the VO2max graph in Connect. (There's a dot on the graph on the dates with detection, even if value doesn't change)


So, to sum up: I think we can conclude that Garmin doesn't allow updates of FirstBeat metrics unless GPS pace is available, which makes all the fancy features useless for many people 30-40% of the year.

Well isn't that just brilliant? Can we get an applause for Garmin please?

So, to sum up: I think we can conclude that Garmin doesn't allow updates of FirstBeat metrics unless GPS pace is available, which makes all the fancy features useless for many people 30-40% of the year.

More like a 100% of the year for people like me. I find my Stryd is much more accurate with pace and distance then GPS that I'll never go back. I'm only using the GPS for tracking. I guess I'll have to do a VO2 Max test with GPS pace every 4-6 weeks along with my critical power test. I wonder when Garmin ever decides to catch up with their competition and makes running power native in their watches if it will still be necessary to use GPS pacing for VO2 Max?

VO2max doesn't need to change significantly to get an update. I get updates regardless of change in (whole number) value, and this can be seen if you look at the VO2max graph in Connect. (There's a dot on the graph on the dates with detection, even if value doesn't change)

You are right. I just didn't consider same value as update.

More like a 100% of the year for people like me. I find my Stryd is much more accurate with pace and distance then GPS that I'll never go back.

Actually, when I come to think about it, that’s true for me as well since indoor running gives no data, while outdoor data gives wrong data.
Inaccurate GPS pace was the only reason why I bought a Stryd as well. Quite frustrating to find out that it doens’t improve the analytics after all.

Either Garmin is getting outdated, or they are clinging to GPS as the holy grail due to their heritage as a GPS company.

Something is wrong here. Or something has changed. I recall from older threads that several users have had the experience that they got a lower VO2Max when running with a Garmin Foot Pod for pace and GPS for path logging, compared to running with GPS only.

This would indicate that pod pace is (or was) used for VO2Max calculation.

Then I believe something has changed, and that the article linked by TMK17 earlier in this tread is outdated, or not very well explained at best.

When running outside using Run app with Stryd and GPS enabled I always get Performance Condition popping up after 6 minutes. (which indicates to me that the FirstBeat algorithms are live and kicking). This is regardless if I do long easy runs, medium treshold runs or fast intervalls, FB never fails to detect PC etc.

If I use the same setup, Run app with Stryd and GPS enabled on the treadmill (GPS speed = 0) I never get PC or any recording of the other FB metrics.

If I use Run app with Stryd and GPS disabled I don't get PC or any of the other FB metrics. I've only tested this scenario once, but I see Markus has done the same and did the same finding.
I haven't tested this outdoors, but indoor/outdoor shouldn't make any difference as long as GPS is disabled.

For all of the scenarios described above I've used the HRM-Run for high quality HR/HRV data, and Stryd for high quality pace/distance data.