What do you expect from the next update?
-
I’m mostly happy with the Vertical, I would like to see:
HRV data and their replacement algorithms in place of FirstBeats for Resources (training load, recovery), Sleep
Nice to have:
Suggested workouts
Routable trails on map data
Support for multi-sensor pairing when of the same type.
Bigger Fonts / Text when following a structured workout describing the next targets/goals/stage of the workout.
Better notification handling (no more zombie, unable to clear notifications) -
One feature I would really like to see would be the ability to restore the watch as you had it last set. When it hard resets, it requires you to set up each structured workout over again which is tedious. It would be very useful to “push your last settings” to the watch instead of manually entering everything over again. I use 3 panel global views for each of the workouts with the top, center and bottom the same for each. Having to go into 7 different workouts and set this up every time is not fun.
I have had to do this about 6 times now that the watch crashed.
-
@Todd-Danielczyk oh boy how many times it was requested… Especially when “do a hard reset” is often times recommended as a last resort prior to sending back the watch to servicing.
-
@seanvk said in What do you expect from the next update?:
Support for multi-sensor pairing when of the same type
I second that!
-
@Frederick-Rochette better cycling support. ClimbPro is one thing, but it is really irritating that you cannot pair with watch two dedicated sensors for speed and cadency. BTW it was possible in ambit2 watches. In current models including vertical you can either connect speed or cadency unless you are not use two in one sensor. Other thing is that it will be good to have few slots for each of this sensor types so I can pair sensor for few bikes, without a need to pairing each time I am choosing different bike.
-
Now the “what do I think the update will contain” became a “what would I like to get”
-
I would expect a better separation of VO2Max for non-running. It’s amazing how a week of hiking in the Canadian Rockies tanked Suunto’s VO2Max.
Suunto Race Titanium
Suunto Vertical Titanium
Suunto 9 Peak Pro Forest Green
Suunto 9 Peak Moss Gray -
Not sure if I have seen correctly on internet. There seems to be a smaller version of the vertical with a different name. Probably on test mode now. Perhaps all the new updates will be launched together with this new watch which I believe will replace the 9 peak series ?
-
@seanvk I just got my Vertical recently and did a couple of runs. The first one was done using the default Running Basic profile which recorded my VO2Max, while the second using a custom Running profile as I want to tweak the data screens, but that time it didn’t record a value. I read in another thread that VO2Max is only supported with the default profiles—I wonder if you could try creating a custom profile to do those hikes so it doesn’t affect the Fitness Level?
Current: Ocean, Vertical Titanium Solar
Past: 9 Baro, Spartan Ultra, Ambit3 Peak Sapphire -
@Jonathan-Chu Thanks. Yes, I will probably have to create a custom outdoor activity and name it Hiking to avoid this issue.
-
@seanvk why it behaves like this is beyond me. VO2Max separation and integration with specific sports NOT profiles has to be on the wishlist of updates.
Current: Ocean, Vertical Titanium Solar
Past: 9 Baro, Spartan Ultra, Ambit3 Peak Sapphire -
@Jonathan-C said in What do you expect from the next update?:
@seanvk I just got my Vertical recently and did a couple of runs. The first one was done using the default Running Basic profile which recorded my VO2Max, while the second using a custom Running profile as I want to tweak the data screens, but that time it didn’t record a value. I read in another thread that VO2Max is only supported with the default profiles—I wonder if you could try creating a custom profile to do those hikes so it doesn’t affect the Fitness Level?
I only use custom modes for trail running and running. Vo2 calculation works
To avoid vo2 calculation for hiking, so far you only have two options :- disable HR/OHR when using a walk/hike mode
- using another sport mode where there is no vo2 calculation and change the type of sport after recording, in SA
-
@Jonathan-C because, as we’ve recently learned, Suunto has no resources to focus on such subtleties when it’s busy racing its competitors
-
Łukasz-Szmigiel said in What do you expect from the next update?:
Jonathan-C because, as we’ve recently learned, Suunto has no resources to focus on such subtleties when it’s busy racing its competitors
Racing! Must be with 16’40/km
-
@Jonathan-C I never use default running profiles and my Suunto Vertical shows Vo2 values after every training, isn’t that correct?
-
@jjpaz it is becoming a little off topic here.
Maybe open a separate thread for VO2max…
In short: it can be calculated in default and custom modes. Just the VO2max calculation requires some minimum data quality.
So if GPS or HR data is not of sufficient quality, VO2max is not calculated for an individual activity. -
@Tieutieu thanks—and my mistake. Just gave custom Running profile another try on what should be my cross training day (too impatient
) and this time VO2Max is calculated! It’s possible that I have to make sure the battery mode is Performance (somehow it defaults to Custom when creating a new profile) for this to happen… but glad it is working as intended.Promise this will be my last comment on this subject here.
-
@Frederick-Rochette honestly, what I’m expecting from suunto is a better communication. There is clearly a serious issue with this watch and the “black screen of death” but they did not provide any information or confirmation about that. I opened a case at their support, asking for clarifications and the only answer I received is “if you have a problem with your watch, please contact your local dealer for support”.
Yes, it’s a complicated piece of hardware with a lot of dev and code running in there but when a serious bug is clearly identified, it would be more than welcome to inform customers and confirm the issue.
Honestly, the lack of communication from suunto is quite ridiculous.
-
@darxmurf said in What do you expect from the next update?:
@Frederick-Rochette honestly, what I’m expecting from suunto is a better communication. There is clearly a serious issue with this watch and the “black screen of death” but they did not provide any information or confirmation about that. I opened a case at their support, asking for clarifications and the only answer I received is “if you have a problem with your watch, please contact your local dealer for support”.
Yes, it’s a complicated piece of hardware with a lot of dev and code running in there but when a serious bug is clearly identified, it would be more than welcome to inform customers and confirm the issue.
Honestly, the lack of communication from suunto is quite ridiculous.
In which way would it help you if Suunto shared their service stats with you?
Like 0.02% watches back with button malfunction
1% watches experienced restart during activity
0.1% of watches have sealing issue at the glass connection
10% have barometric sensor failureThis is company internals and no comapny in the world shares those numbers.
They use it to improve product quality.
What you as an individual customer should expect a prompt handling of a possible service case.t6, S6, Elementum Terra, Ambit 3 Sapphire, Spartan Ultra Copper, Traverse Alpha, S7 Graphite LE, S9B Ambassador, S9P Granite Blue Titanium, S9PP Titanium Sand, Vertical All Black, Race Titanium Charcoal,
Race S All Black - TI Canary - Titanium Courtney -
@Egika I would like to support @darxmurf . Back when I had serious crashing problems with my S7 I did what they suggested and contacted my local dealer. My watch was sent to be serviced, but it came back with factory settings and unsurprisingly continued crashing. At this point I would expect the support to take responsibility of the problem escalation. Their communication was minimal at best and I had to take extra effort and literally demand support and service.
It was never about sharing statistics, but instead coming up with a solution for the customer with a bad device. If there is a SW bug causing problems, then they should come clean and say that it is a known problem and will be addressed in the next bugfix release in a few months. Playing dead won’t get the problem go away. Some info about a brighter future would be better than no info at all.
