Suunto Vertical: Bug Collection

Although I am not a user of the watch, I think that with the growing number of bugs (related to more features! Not criticizing) it would be nice to change the forum to have a system like we have for the features. Where number of likes/comments would demonstrate the number of people who has that bug. And when it is solved it would be marked solved. Garmin also has similar system in their beta forum.
I think it allows more capitalization .

@André-Faria True. I mean, the Garmin beta forum had major problems in the beginning, but it’s getting there.

I am not sure if it’s a bug or if it has been reported, but it happened a few times already.

When I scroll through the widgets (mostly when swiping left) the screen gets stuck on a pure black screen, something like in between widgets. Then I have to swipe again to get out of it. Not a big deal, just FYI.

Dimitrios Kanellopoulos

@André-Faria no we won’t facilitate that. We have an extrernal group of fieltesters to manage that in an internal way.

Dimitrios Kanellopoulos

@Dimitrios-Kanellopoulos last known location might not be in this update. Fyi. (recent news)

renton82

@Dimitrios-Kanellopoulos said in Suunto Vertical: Bug Collection:

@Dimitrios-Kanellopoulos last known location might not be in this update. Fyi. (recent news)

What do you mean?

isazi

@renton82 there was a new feature tested, somewhat requested in this forum, to have the last known position used to show the map even if you don’t have GPS. But it has been decided to remove this from the hotfix, and focus only on bug fixing.

renton82

@isazi Ah ok! But why don’t take current position from smartphone when watch GPS is unavailable? Or simply from weather widget…

isazi

@renton82 because that is not the issue, there were other issues. And this is why Suunto does not announce new features, because people then expect them without knowing the complex implementation details

renton82

@isazi Ok, understood!

wmichi

@surfboomerang I have no idea. I use it the exact same way as the S9PP (not a single reboot since release). The only exception is maps.

wmichi

@Tieutieu If the watch restarts itself, it‘s a bug. I can imagine something like a race condition. If the user needs to do a soft reset to make the watch work again as expected/advertised (if it freezes or whatever ), I would also say some bug is involved. Every software is full of bugs, because humans create it. That‘s the way it is. As long as a company acknowledges this and works on fixing them, no problem. Suunto does a very good job in this regard (especially communication with users in this forum), much better than Garmin.

Tieutieu

@wmichi i didn’t had any erratic restart. I just had some parts of maps that were not visible. Stopping the watch and restarting it solved.

freeheeler

@André-Faria
if you look at the recent kosovo map topic: I think this is one of several points what Suunto differentiates from Garmin

Frederick Rochette

@isazi so no new features in the next update?

@Ilya-Sul said in Suunto Vertical: Bug Collection:

@renton82 That’s why we need an “official” list of reported bugs.

I can’t disable PulseOx during sleep btw. It just keeps on tracking, no matter the setting.

Had the same issue on S9PP, only after a soft reset the PulseOx stopped with tracking.

@twekkel Thanks for letting me know!

isazi

@Frederick-Rochette it’s not an update, it’s a hotfix release.

Frederick Rochette

Regarding the measurement of power at the wrist, the data seems consistent on the flat but absolutely not on hills and downhills, which don’t seem to be taken into account (or else there’s a reliability problem).
Has SUUNTO taken this into account and will we soon have a reliable version? If not, this data is useless (as it is unreliable).
I used to use STRYD, which is what allows me to compare.
This is also the case for the NGP of the S+ Hill reps app.
Last question, when will it be possible to have an NGP field (reliable) in a sports profile?

runomatic

Today my Vertical crashed at my trailrun after 1,7 km while navigating on a route created with Komoot.
I hope the coming update will fix this kind of issue.