No change at all.
I go for a 4-5km walk twice a day, mainly on stony country tracks, so heart rate is not constant for long periods of time, but no VO2 reading at all for a year or so, no matter what I do.
It used to be recorded on the same outings when I first got my S3 last year, but not for a year now, not on the S3 nor on the S6.
Thanks, and what a bummer. I do wonder if it's an issue with the heart data though. I walk way less than you, but I used to get recordings when I walked my dog, even for short 20-30 minute walks. The first half is always less intense as it's downhill, then on the way back my heart rate goes up.
With watchOS 5 (the default version that came with Series 4) VO2 Max was spotty, then watchOS 6 was incredibly consistent as far as recording it went. It may not change much, but it was recorded virtually every single time I went out. Same watch, same routes, same everything... given the track record — pun intended — of the watchOS 7 update, I wonder if they just messed something up *also* with VO2 Max.
I even tried resetting my calibration data and going for a 20 minute walk in a flat area (pretty much drove there just for that!) but it didn't do absolutely nothing for me. I then went for dog-less walks uphill just to make sure it was "vigorous", and still nothing.
I just wish we could see that kind of data on the watch, to at least figure out if the issue is with recording it in the first place, or "just" transferring it to the phone. When the GPS bug hit me, the Watch was fine but the phone got broken data, so it was clear where the issue lay.
I don't personally care that much about it as I'm not an athlete, but it sort of bothers me that they showcase it as a metric on the Fitness app, and then the data there just dies off on September 15.