Have you lost your VO2Max in a watch crash?
-
@BrunoH don’t worry. My VO2Max used to be above 50. I cannot run due to some health issues and my VO2Max was 41 when I got the vertical in May. It dropped from 41 to 38,6 in July after some time in Italian Alps. Since then it has not changed a bit. No idea how this is calculated. Now after a hike 2 days ago it dropped again and I don’t care anymore.
Anyways, when you finished the activities, did they display an estimated VO2Max in the summary in the watch?
-
@BrunoH btw… I just checked the SA and I don’t see any VO2Max estimate on activities AFTER the upgrade. Same on the watch - it’s not there.
Maybe the new software calculates it only for running activities… not sure.
-
I would recommend factory resetting the watch. While preparing my Vertical for update by charging it I had a looping 1403 crash apparently related to wifi network and map downloads that’s been discussed in another thread. The watch factory resetted itself after a while and lost everything but after the update I decided to initiate another one myself just to be safe. Now everything runs smoothly and seems better than during old SW, though it could just be the reset clearing some corrupt stuff in the watch. My VO2max and race estimates came up after just one run (45 mins around 6:00/km).
-
@tomasbartko said in Have you lost your VO2Max in a watch crash?:
Anyways, when you finished the activities, did they display an estimated VO2Max in the summary in the watch?
No, not in the summary, not in the logbook and not in SA.
-
@BrunoH Yeah just noticed I don’t have it as well. After the update it’s not showing anywhere.
-
@tomasbartko I did a factory settings reset this morning. For the last couple of hours I’ve been watching “This is taking longer than expected. Thank you for being patient” screen and animation. Let’s see…
-
@BrunoH said in Have you lost your VO2Max in a watch crash?:
@tomasbartko I did a factory settings reset this morning. For the last couple of hours I’ve been watching “This is taking longer than expected. Thank you for being patient” screen and animation. Let’s see…
I had this yesterday too. This message did NOT disappear by itself for 7 hours. I pressed upper button for 12 seconds and then the Vertical came back with a message that en error was fixed (1609?) and on the old firmware. I had to install the new firmware again. A very strange thing …
-
@BrunoH I don’t really want to do a factory reset because of custom sport activities. But let’s see how it works out for you, fingers crossed.
-
@BrunoH So I did a 25m test run (my back will thank me) and VO2Max was again visible. Apparently it’s not calculated for walking/hiking, but only for running (?). It also says Running VO2Max in the watch, so it would make sense. Any luck with your watch?
-
@tomasbartko I received today detailed requirements from the support.
- Walk and run modes are supported
- GPS and HR tracking must be uninterrupted and perfect quality
- HR must remain at least 8 minutes in zone 3 or higher.
- GPS quality requirement is especially important if there are no prior measurements (this applies to my case now that I did the hard reset)
Good work support! I’d like to see all these explained in the user manual or FAQ. In depth explanations would make support’s life easier.
-
@BrunoH oh nice, good to know, thanks! So I guess in my case it’s because I was not in zone 3, at all. I’ve had no idea about that.
-
@tomasbartko my problem is quite the opposite. My wreck of a body goes to z5 in under five minutes and it is hard to keep going for 8 mins being that exhausted.
And I have had bad GPS fix sometimes in the beginning of the exercise. I’d better let it settle first.
-
I have been getting vo2 max readings under “walking” activity and i do not get my hr in zone 3 so I’m no sure what support is taking about.
-
@gone-troppo They are talking about getting the first VO2max estimate after full factory reset. Back in the old sw (and with my old S9B as well) I saw VO2max value after every run or walk no matter how bad quality the data was. The watch was probably showing the previous measurement.
-
@gone-troppo weird, because I did not. Only for running.