Software update 2.16.26 June 10th 2021
-
@dimitrios-kanellopoulos to me, current GPS firmware is great and I very rarely have any issues. Most of times it’s spot on. Challenging conditions are challenging and I don’t mind really. If Suunto / Sony were to decide it’s final, I’d be ok with that. The only thing that I’d like to see improved is battery life with Galileo / GLO. If it’s possible to make it equal to GPS only - that would be super awesome.
OHR is another story though - I don’t mind “spikes” but OHR locking on ~160 for 5 - 15 minutes while walking is a bummer. I think there’s room for improvement there as the problem is less so with accuracy but with “stubbornness” of OHR module. If it locks too high or too low (rarely), it likes to stay there for long. I use belt for running but it’s nice to have a nice backup option for hiking and some less intense sports where I don’t need the belt. But honestly - can Suunto really do much about OHR in S5/S9 without input from 3rd parties (like with GPS and Sony)?
-
@isazi i understand but i didn’t thougt Suunto saw the gosth runner like it
-
@łukasz-szmigiel S3 has the same OHR. It works for some folks. The Valencell OHR is problematic for me on any watch. If I wear the watch substantially up my wrist from where I normally do, the Valencell actually works well. The LifeQ OHR on the S7/S9Peak is far better, it works almost always and will work for intervals for me wearing the watch close to my wrist bone. I do not think there is much more that can be done. Suunto has worked hard to improve the OHR on S3/S5/S9 models.
-
So I would like to start my post with 2 kudos. One kudo to Fenix6x that I used last year to train. It’s pace/distance proved to be so inaccurate that I was always pushing to the limits to reach the suggested pace. I almost felt bad for myself when I saw that I am barely improving.
And the second kudos go to Suunto for this FW and the jewel of a watch that is my S9 ambassador.
Not to go into much details but I ran half marathon (known route and checked with maps both SA, google and Garmin explore. Suunto 9 showed 21.12km (20m more I guess when I paused to cross a car street) and f6x showed 20.01km!!! That’s 1.1km difference. I was running with pace 5m per km but fenix decided it is 7 at some points (I walk faster than 7). I had both S9 and f6 to the best gps recording and both gps+glonass.
Nevertheless, kudos to Suunto and the great team behind it. No I do not need ‘walk your dog 800eu tracker’, thank you very much. -
@brad_olwin can’t say for LifeQ but for Valencell - this is also my experience. Except sometimes wearing it high isn’t enough. As I said before - I don’t mind it going bad from time to time but locking on ~ 160 for 15 minutes is an overkill. But I get it there’s not much that can be done about that.
PS. Shaving wrist seems to help somewhat. I had some success prior to using the belt but since I wear the watch on different heights (as I tend to get blisters from left side of Valencell housing when having watch on the same spot for 12+ hours) this is somewhat pointless, especially in the summer season
-
@isazi yeah, but if you f up in the first km, then your ghost is running with wrong pace. In most races you start to fast because of hype/environment, and not setting ghost pace before start is not so useful. I remember on old Garmin 405 I had virtual partner, you set for example 4:30min/km for run an you follow it. For first km you can be 30s ahead and then you can get into the rhythm. At least this is my use case, maybe others will benefit from this ghost runer
-
@likarnik while not optimal , pressing the lap button twice with 5s in between will set your current pace as the ghost
-
Btw does the use of TbT together with s+ still cause possible crash of the watch?
-
@дима-мельниченко no that should have been solved. Please report if it happens again.
-
@дима-мельниченко solved and tested
-
@likarnik don’t believe you are not heard. Suunto is aware of this, and while the current S+ is already useful (e.g. with the lap trick Dimi mentioned), many of the testers asked for what you mention. Hopefully this is only version 1 of this app.
-
@isazi and Dcrainmaker XD
-
Can someone with S9 non-baro with 2.16.26 please confirm that zooming on route isn’t bugged and works as usual that is hold middle and use top / bottom to zoom in / out?
-
@łukasz-szmigiel i have opposite problem with WHR. It sometimes drop to half of my heart rate. And than it sticks to this and don’t want come back up. Usually on bike when there is more vibration from terrain. It drops from 120-140 to 60-70 and i must stop for few minutes for watch to catch back my heart rate. But on asphalt there is usually good accuracy now when weather is hot. In spring it had much worst performance even on asphalt. For me it was usually 10-20% of activity when it is inaccurate but in hot weather is accuracy good. And maybe i am more careful to keep watch higher on my wrist.
-
@łukasz-szmigiel can indeed confirm
-
@дима-мельниченко
I’ve also experienced this, would not say due to shaking, but my HR was also 60. When I finished my session 3,5h . there had been 2 smaller sections where my HR was around 60. -
The backlight illuminates even when it is not needed, resulting in increased battery consumption - interval timer and automatic lap in running and cycling modes.
Training on the bike more than 100 km, every kilometer the backlight lights up. I need the cut-off every km, but do not need the backlight in the daytime. The same situation with intervals in running. -
The update is out for S5/S3 as well
-
S5 updated. Few minutes I go out to try snap to route and ghost
-
@dimitrios-kanellopoulos thanks for info. I am very excited to try snap to route. And at same time very disapointed that backlight toggle mode is away. Now on every button press there is backlight enabled even when enough ambient light. In average light conditions, visibility of screen with backlight on is even worst because it subjectively decrease screen contrast.