SW update 2.37.34 Q3

Stefano M64

@Stefano-M64 said in SW update 2.37.34 Q3:

After the last update the Blood Oxygen measurements on my Race seems to me to have started to give correct (or at least reasonable) readings, while before I always got values below 90%, however that “fix” isn’t listed in the Q3 release info. I also changed the strap (a nylon velcro band) but don’t believe that could have affected the readings in that way.

none replayed to me, but I really started to have correct measurement most of the time, even if sometimes I still get wrong values. I noted that this usually happens when the measurement takes too long to be completed. When it is fast, that is taking few seconds, then the value is usually in line with a pulse oximeter.

Iggge

@RaDeck For me the Vertical Did show to many steps before, but now it’s ridiculous low.
When running or doing a exercise my Vertical works fine. But when it comes to the daily tasks it’s so far off. Can show 5.000-8.000 steps less sometimes.

I have compared to Garmin 245 Music, Samsung watch 7 and obviously my phone, S23 Ultra.

ODo67

Hello everyone.
In February I was very happy with my Race. Then, after the various updates, problems appeared, in particular :

laborious and often incomplete synchronisation
excessive battery consumption
…
I’m very pleased with this latest update, which seems to have solved these problems on my watch. And that changes everything - it’s pleasant and headache-free again!
I know we tend to come here to report problems, but for once… just once thank you!
Have a nice day

SvenSchroeter

@ODo67 Praise to the DEV TEAM

Ecki D.

Stuck on saving again!
This only happened to me since this SW Update. Anything I can send to Support for debugging:
image0.jpeg

Stoke80

@Ecki-D

Had the same issue last Tuesday. I got over the savings screen only after a very long time (1 hour or even 90 minutes).

Ecki D.

@Stoke80 had this 2 times now and waited quite long 1hour to 5 hours, gave up and restarted the watch. Track was saved anyway.

Stoke80

@Ecki-D

Good to know that the track was saved, even when the watch is restarted.

I was not brave enough to try, but luckily it was “solved” by the watch itself.

isazi

@Ecki-D always bad when this happens. If it happens again, let’s hope not, can you send logs after the watch reboots and you sync with the app?

KSGravelJunkie

Question, if it can be shared is Suunto working on the ability to switch between complications by tapping the complication on the screen (like how it was before the Q2 update)? I miss having the ability to switch between complications on the watch face, it was much more convenient to tap the complications than to scroll down to see steps, sunset time, etc. I realize there was a trade off of having custom complications or generic watch faces but I can’t help but think there would be a way to make a watch face that could do both (I.e. customize which X number of complications to cycle through a complication spot on the watch face). At this point I would rather have the original uncustomizable Suunto Race watch face than the one that just shows three complications.

Likarnik

Weird bug today, I pressed lap button but It went to pause menu like on previous firmware (no play/stop buttons on screen) - first oprion was to end activity with a yellow banner on top saying ‘undefined’ - is this js? I tried twice and then left with no lap… it was custom cycling mode, S+ Suunto ZoneSense and TrainingPeaks - Ride with route navigation. Unfortunately I didn’t send logs as I forgot, I was quite dead after the ride. I’ll try next time with same settings if it helps.

minimark069

Just discovered the ability to long press a complication to access the widget. Love it!! Suunto, making my watch better with every update!!

Antoine

@minimark069 said in SW update 2.37.34 Q3:

Just discovered the ability to long press a complication to access the widget. Love it!! Suunto, making my watch better with every update!!

Thanks !

BrunoH

“Improved capability to determine VO2Max. Should be easier to get the estimate now.” -> Did it get any easier for anyone? It’s still a no-show for me on Vertical even after 15 months. For comparison, S9B back then was a piece of cake. Down below you can see my latest running attempt.

Is there an updated list of certified requirements? I know I am fat and in bad shape, but I think I did fulfill all the requirements Suunto support listed me back a year ago. 15 minutes in or above Z3 with flawless GPS and HR. Well I can’t be sure about the flawlessness, but they both look good to me in Suunto App.

Does my run have to be above certain constant speed?
Can I even get the estimate with over 120 kg weight?
Am I supposed to hit the start button after I reach the red zone?
How long does it have to be? Time, km?

The downward spikes are there because I just had to slow down a few times… Yeah yeah, I know it is just an estimate anyway and I should forget this stupid measure. But I have such fond memories: it used to correlate with my jogging feeling back then with S9B and I found it highly motivating to get the estimate up one decimal at a time. I hate it when either I am too stupid to use Vertical, or Vertical doesn’t want to co-operate as marketed.

Screenshot_2024-09-24-12-42-12-49_b14a9358fd6881e7ef1642d19c4cec95.jpg

timecode

@BrunoH Not sure, but all I can say is that for me my Vo2max went down on my first run after the upgrade. I get however readings after every run.

Mff73

@BrunoH not sure neither, but if the criteria is like “15 min in or above…”, this activity is quite at the fringe of the criteria.

larrybbaker

@BrunoH I have had no issues since having the watch on release day - through all the updates it all just keeps working

BrunoH

@Mff73 you are right, but not all of my runs are this pathetic. It is funny though, I got a set of instructions from the support long time ago but tje field testers in this forum were publising different rules! (I’ve been following VO2max discussions closely.)

Which brings me to my next point: documentation is way too vague. Too often the user manual sounds more like marketing material. More thorough explanations would take pressure off from the support engineers. Just sayin’

VoiGAS

@BrunoH said in SW update 2.37.34 Q3:

“Improved capability to determine VO2Max. Should be easier to get the estimate now.” -> Did it get any easier for anyone? It’s still a no-show for me on Vertical even after 15 months. For comparison, S9B back then was a piece of cake. Down below you can see my latest running attempt.

Is there an updated list of certified requirements? I know I am fat and in bad shape, but I think I did fulfill all the requirements Suunto support listed me back a year ago. 15 minutes in or above Z3 with flawless GPS and HR. Well I can’t be sure about the flawlessness, but they both look good to me in Suunto App.

Does my run have to be above certain constant speed?
Can I even get the estimate with over 120 kg weight?
Am I supposed to hit the start button after I reach the red zone?
How long does it have to be? Time, km?

The downward spikes are there because I just had to slow down a few times… Yeah yeah, I know it is just an estimate anyway and I should forget this stupid measure. But I have such fond memories: it used to correlate with my jogging feeling back then with S9B and I found it highly motivating to get the estimate up one decimal at a time. I hate it when either I am too stupid to use Vertical, or Vertical doesn’t want to co-operate as marketed.

Got my VO2MAX on a new Race S after about 1 week. So it should not be aproblem from App or OS

kriskus

@BrunoH Overall however, your zones seem to be somehow strange - last zone which should be really for maximum effort is much broader than any of the three previous zones.