Suunto 2.50.28 hot-fix Q4
-
@Dimitrios-Kanellopoulos
This introduces a new bug…If I have a scheduled Guide that I want to use on a different run later, using my customised sports profile I select X as usual, but now scrolling down I see the Guide is showing active and the X has been ignored. -
Pace reading nightmare is still present since 2.50.26 on my Race S.
Before this update it was a nice smooth curve relatively mirroring my speed curve. Now it’s a complete erratic mess, therefore impacting my VO2max score. I’ve lost almost 1 whole point from just 3 runs…
HR is also consistently higher during exercise than before the update.
Any fix coming soon?
-
@Nigel-Taylor-0 The same thing happened to me with Suunto Run; when there is a guided training mode, the free training mode disappears.
-
@Bastienhere check your pace zones. It can be that cause of the update your Personal pace zones are deleted. Check it
-
Press the blue (i) button at your pace in the App in both training and you see if you have Others zones there, if yes your custom pace zones are deleted and you have to save your “older” zones new
If it doesn't challenge you, it doesn't change you. #lifewithasthma #runwithasthma #nevergiveup #pushinglimits #adventurestartshere Suunto Ambit 3 Peak , D9, 9 Baro, 9 Peak, Vertical Ti, Race , RaceS Courtney, Race 2, Vertical 2, SA (Beta) Android🏃🏼🧗🚵
-
one more thing I noticed after this update - sleep summary is working again
-
@Bastienhere said in Suunto 2.50.28 hot-fix Q4:
Before this update it was a nice smooth curve relatively mirroring my speed curve
But… That’s just the Suunto App presentation, not FW related. And the ‘smooth’ Pace curve in relation to Speed is due to a silly left side Pace graph going from 04:36/km to 46:17/km! You can hardly see the real variations there. The top image example you give has discernable pace variations between the 05:32/km and 07:00 extremes. Using 20.0 and 0.0 km/h for the right side Speed graph is not how I would present it, but still, all that is an App issue.
Suunto Race S
-
@duffman19 Unfortunately you are right, the bug is still there.
-
@Inge-Nallsson you’re making some fair points although the places where my pace dipped from 04:36/km to 46:17/km (and the others in the graph) was when I was stopping for traffic lights.
It’s just very inconsistent in the way it represents pace now, almost like I’m running like a drunk man lol. And to be fair I strongly think this is what is affecting my VO2Max readings.
-
@GiPFELKiND hmm I checked my latest run and another back in December and the pace zones are the same
