Use on watch now...

Horizontal_2

Hi! Just found out this is resolved! You can use ‘use on watch now…’ multiple times during an activity. That was impossible for a long time. After using it one time, it was greyed out.

Just wondering since when. I feel like I wanted to use it more this summer, but I thought it wasn’t possible.

One of the best functionalities of Suunto

elbee

@Horizontal_2

My race s still has this bug, so it must be fixed in the 2026 q2 update for the race 2/vertical 2.

Too bad most manufacturers, including suunto, couldn’t bother to make proper release notes, including all the bugs that are fixed. Or somehow they think secrecy makes them look less incapable, while I think openness shows they care and they want to make a product better.

Egika

@elbee there are dozens of bug fixes in each build, and there is an internal build every 1-2 weeks.
Listing everything between the quarterly updates would be a huge list with mostly cryptic ticket numbers and names. This would raise more questions than provide answers I guess…

elbee

@Egika

Synology nas does this, for instance. And so do I in my profession work.

It should be no work at all if suunto would keep a proper issue management system. Just one button press and the list for a release is generated. But to be honest, that is a big if, in my experience with suunto support.

Egika

@elbee this is what Suunto is using of course.
As mentioned there are full and long release notes with each build.
Just again: this is not useful at all to the average user.
Firstly you would need to map your issue (in this case “use on watch now”) to the internal bug.
If this is fixed, it may happen by doing something different and the internal code base details don’t help.
So you would need to keep multiple lists and translate and map between them.
Again: I doubt that it can be beneficial for the average user. And for the few freaks here in the forum, it is not worth the effort.

elbee

@Egika

Then provide a short and extensive version of the release notes. And you don’t need to map. Bugs should have clear titles. Internal code changes are never in release notes.

Now the opposite happens: a user thinks a bug still exists but happens to be fix.

Egika

@elbee I can only see that it is not as simple as it seems…

Steven Hambleton

@Egika Do you not use version control commit messages? Those that are making their way to production are the actual fixes and can be compiled. Surely these would be the thing to show and they compile themselves unless your commit looks like this -

Done
Done
Done

Egika

@Steven-Hambleton my point is that there are so many bugs fixed, noone has ever encoutered here, and some are so cryptic dev speak, that you would need to ask them for explanation.
I stand with my point that getting all this together and explained would be a full time job.

sky-runner

@elbee said:

Now the opposite happens: a user thinks a bug still exists but happens to be fix.

Exactly! From time to time I do discover that some old issues have been fixed. There is rarely if ever information about that in the release notes or in the forum. I always discover that on my own.

What would be really good is to somehow tag community reported issues to let users know that the issues are tracked by the dev team. And then when the issues are resolved to also tag them as resolved in the forum. But I guess this would be a lot of work for the forum moderators unless this is somehow automated.

Stefano M64

@Egika said:

@Steven-Hambleton my point is that there are so many bugs fixed, noone has ever encoutered here, and some are so cryptic dev speak, that you would need to ask them for explanation.
I stand with my point that getting all this together and explained would be a full time job.

nowadays, releasing a new software version without a changelog is absurd to me, unless there are only “under the hood” technical changes that do not affect the users experience

also the SA is always released without any changelog …

Egika

@Stefano-M64 If I view the changelog of app updates on my iphone, they mostly state “stability and functional improvements”…

There is a change log for watch updates, like for example here:
https://www.suunto.com/Support/Software-updates/Release-notes/suunto-vertical-2-software-updates/
This is highly aggregated though and not every small bug is listed here.

Steven Hambleton

@Egika I had no idea about these pages! I would subscribe to a newsletter with changelog updates.

2b2bff

@Steven-Hambleton this is actually the same as you get in the app within watch settings, update and “older versions” or so.

Stefano M64

@Egika yes, firmware updates are usually well documented, I mostly referred to the Suunto App, which never has a changelog

Egika

@Stefano-M64 agree!

snow*

@Stefano-M64 said:
I mostly referred to the Suunto App, which never has a changelog

Strangely enough, if I’m not mistaken, I’ve seen them on iOS

elbee

@snow If I look at the version history in the app store:

a 3.x.0 version has a description of the one biggest change.
a 3.x.y version has Fixed known issues and improved system stability.