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

V7.2

While the v7.1 is still rolling out at 25%, surprisingly my watch got the v7.2 update today. Do anyone has the change log?

  • Did my first running activity with 7.2 all seemed fine except the same as the 7.1 update it threw away the records on the watch so I once again gained my fastest k etc on an easy run. Not a big deal obviously.

  • I am part of the 25% who received 7.1 with which I had no problem, this morning I updated to 7.2 and in the first race today everything was OK. The upgrade from 7.1 to 7.2 was very fast as if only something was added instead of all the SW

  • I fount it's perfectly fair that those who got a "problematic" firmware are the one to get the "good" one first. And it's very good to not see any bad report about 7.2 !

  • They just put out more of the update - I just got it!  Go go go!   :-D

  • So it seems.. Now I don't have the beta anymore which worked great :) and did the usual 15s light button press to avoid possible problems after FW update.

  • First trail run and first night's sleep went well.  The only oddities:

    No sleep metrics appeared until I added the sleep widget to my watch.  

    My vo2max took a crap after getting done with the trail run; it started me out at a -4 performance condition, and didn't get any better from there.  What was surprising is it impacted my OVERALL vo2max, and didn't break out trail/regular runs on my watch or in-app.   Is the point a weighted average between trail and road runs, or was there supposed to be separate v02maxes?  Anyone know?

  • Running is running. In my trail runs I think the VO2max has been pretty much the same, at least I don't remember noticing anything out of the ordinary and I've had it since 6.85 beta.

    If you continue have so much difference I think the recommend thing is then disable the VO2max from Trail run settings.

  • My vo2max took a crap after getting done with the trail run; it started me out at a -4 performance condition, and didn't get any better from there.  What was surprising is it impacted my OVERALL vo2max, and didn't break out trail/regular runs on my watch or in-app.   Is the point a weighted average between trail and road runs, or was there supposed to be separate v02maxes?  Anyone know?

    This is the feature I have been looking forward to most with this release, and I finally just got it today so will be testing tomorrow.  80% of my running is trail running, so my Vo2max previously only updated about once a week (which actually is fine as conditions are pretty similar each of those runs).  I'm really curious what's going to happen with mine once all of my trail running gets factored in.

    As for your situation, what kind of trail running are you doing?  Lots of elevation change?  Unusual conditions (highly technical trails or mud)?  Just trying to ballpark things that might throw the algorithm a curveball it can't handle.

  • From what I'm noticing about sleep and body battery, this is the best SW version ever

  • Do we have to have the sleep widget added to receive a sleep score?