SW update 2.37.34 Q3
-
@Jordi-C found it! Water in the barometer sensor.
Water on the sensor will cause wild pressure swings (like water in the ear after swimming).I’m confident this is where the wild altitude numbers are coming from. She can use pool swimming while in the pool, then shake the watch and give it a light breath of air in the sensor if she plans on doing any further exercising outside of the water and wants to measure altitude.
-
But, why combined training doesn’t show also this strange ascent behavior?
She started swiming with this mode on after the gymnastics issue. -
@Jordi-C if she swims, she should use the swimming mode and not the gymnastics mode, because gymnastics does not filter ascent off.
Watch: Suunto Vertical Ti
Blog: isazi's home
-
@isazi Got it!, Thanks a lot folks
And now just waiting for the coming update to solve the high battery drain issue in her watch. -
@Jordi-C An addition. I had very very abnormal elevation gains last summer in trekking by the mere fact of sitting with water up to my chest in a mountain river with little current. It seems that water has a strong effect on the sensor. @Brad_Olwin and others pointed out this effect in my post.
J
-
I forgot to comment that my wife’s watch problem with the pause/resume was related to her, walking too slowly to trigger the motion threshold warning.
I tested it today walking at over 6 km/h and it worked as expected.
-
@Jordi-C said in SW update 2.37.34 Q3:
I tested it today walking at over 6 km/h and it worked as expected.
I my opinion, that threshold is rather high at least for walking activities (walking, hiking, trekking…) 5 or even 4 km/h would be more reliable, it’s not that easy to reach 6 km/h on a mountain path, especially when walking uphill. Would be better to differentiate the threshold depending on the sport mode.
-
@Stefano-M64 said in SW update 2.37.34 Q3:
@Jordi-C said in SW update 2.37.34 Q3:
I tested it today walking at over 6 km/h and it worked as expected.
I my opinion, that threshold is rather high at least for walking activities (walking, hiking, trekking…) 5 or even 4 km/h would be more reliable, it’s not that easy to reach 6 km/h on a mountain path, especially when walking uphill. Would be better to differentiate the threshold depending on the sport mode.
The threshold is really 5.4km/h over 5 sec, but still rater high in my opinion. Lower threshold or a lower threshold combined with GPS position changes could work better.
-
@Ecki-D agree with this! I used to get 7 - 8k steps when just being at work the whole day. Now it’s more like 2-3k for a similar day. It used to count me steps when riding my scooter and moving my wrist
-
@PatPinel I solved this. The faces are included in the total number of apps you can install. Open the apps tab and delete some of those (I had scoreboards etc all sorts of stuff I’ve never used). Once you delete enough of those, you’ll be able to add all your preferred watch faces!
-
@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.
-
@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.
-
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
-
@ODo67 Praise to the DEV TEAM
-
Stuck on saving again!
This only happened to me since this SW Update. Anything I can send to Support for debugging:
image0.jpeg -
@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).
-
@Stoke80 had this 2 times now and waited quite long 1hour to 5 hours, gave up and restarted the watch. Track was saved anyway.
-
@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.
-
@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?
-
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.
