Software release 2.30.26

inkognito

@Walter-Samuel I believe that all metrics with new algorithms need to establish new baselines etc. Therefore, I would really give them a week or somethig before rating sleep quality and resources accuracy.

wmichi

@far-blue I don’t have 25 year of experience in software development, but my 18 years are also more than enough to know, that you are absolutely right. Endusers simply don’t see how complicated all of this can be. They only see the result and they can only judge the result. And if the result is buggy, it’s buggy.
Ordinary users just want a product to work as advertised, they don’t care about code refactorings, migrations, unit tests, reimplementations of existing code or whatever. Why should they? If you ship buggy software, people will complain about those problems until they are fixed. We just have to deal with this.

GiPFELKiND

@Dimitrios-Kanellopoulos said in Software release 2.30.26:

Tss etc values are off by one day. Known issue.

Does this clear the discussion?

Yes but when this Problem will be changed?! Why this was not seen by the beta testers before bring a new watch out

jjpaz

@wmichi said in Software release 2.30.26:

Ordinary users just want a product to work as advertised, they don’t care about code refactorings, migrations, unit tests, reimplementations of existing code or whatever. Why should they? If you ship buggy software, people will complain about those problems until they are fixed. We just have to deal with this.

That’s the point. Users want a product to work as advertised (and expected) because the’ve paid for that product. This isn’t an Open Source software like Intervals.org or something like that so users/customers are going to demand the correct behavior.

far-blue

@wmichi If I wanted to summarise my post, it wouldn’t be “Bugs happen, deal with it”, it would be “The developers will have been pressured (completely understandably) to release by the marketing department but the slow updates, lack of communication and lack of features over the last 2 years should be a thing of the past and bugs should get squashed within weeks so be hopeful, don’t despair :)”

Of course, this is entirely my guess and I have no internal knowledge so I might be completely wrong.

wmichi

@jjpaz I am one of those people. And I submit bug reports, because I really like Suunto watches and the app. If I wouldn’t care I would use another brand. While Polar seems to be at the end (not an expert, it seems to me this way), Suunto will make a big comeback, I am sure. All of those recent developments are awesome. Just a little bit buggy

@far-blue That’s also what I was thinking, good summary. Of course it’s always the management/marketing/the money/market pressure. That’s no sarcasm, in my experience this is simply how the business works. No dev has an interest to ship buggy software. That’s something we should not forget: everyone is doing his/her best: devs, testers, support,…

far-blue

@jjpaz There has been a cross-industry shift over the last few years due to the implementation of automatic over-the-air updates in products. The benefit is new features on existing hardware and, often, new features arriving more frequently. The flip-side is that there’s also often more bugs. It all boils down to market competitiveness - it’s more commercially successful to release features with minor bugs if the cost of fixing those bugs is low. If you hold off on a feature release when your competitors have strong offerings then you miss out on sales. Before OTA updates, the cost of fixing bugs was much higher - initially because you needed to replace the hardware and then, more recently, the support helpdesk resource costs of explaining to users how to do a firmware update via their computer. This meant slower release cycles and more testing. You can see the exact same pattern across TVs, home security products, even xmas tree lights! I’m not saying it’s a good thing, just that it’s a thing And Garmin have had their fair share of dodgy updates over the last few years - hence why they have a beta community testing program.

BastMaSVSRS9PP

@Majkel-Paszeko yeah that makes sense. Thanks for explaining !

jjpaz

@far-blue Yes, I know the “new” industry process. In my company we are “fighting” every day with our own developments (and bugs) and the third-party partners software and bugs.
Also our customers demand us to correct the issues as soon as possible.
Some issues are solved as soon as possible, some bugs are acknowledged and delayed due to “script requirements” (or more commonly, priorities).
It’s not easy to find the balance…

What we do is allow downgrading to a stable software version (or previous one) in case of a serious failure. I think Garmin also allows that.

DrSilverthorn

@Maryn I would disagree. The problem with more features is more bugs. And Garmin is the feature king. I’ve got an Enduro - it was a great watch until Garmin pushed an update that broke the course guidance display. Five months later, and it’s still broken.

I think it’s important to pay attention that core features work. Of course everyone will disagree on what those are.

Dimitrios Kanellopoulos

Let me add that not all development is the same. You cannot compare web development to embedded development nor android etc.

So while everyone speaks with experience it doesn’t mean we have to argue all the time.

A button takes 2 seconds to style on html, 2 minutes on Android and perhaps 1 day on embedded.

Luís Pinto

@Dimitrios-Kanellopoulos well said!

duffman19

Am I the only one whose training numbers in the watch match SA? They have since day one of the update.

Maybe it’s a multiple watch issue? The Vertical is my first Suunto in a while, so there was no transition or swapping for me. Although I did import most of my activity history into SA and had to tweak some TSS numbers, but everything lines up for me now.

Antoine

@Dimitrios-Kanellopoulos i agree. This discussion should be uses to provide factual informations rather than personnal opinions to help suunto team to have usefull feedback and to correct/improve them in a next release…

Majkel Paszeko

@duffman19 Maybe it is a case. Since vertical is yor first Suunto watch, SA calculates CTL etc. basing on same short term metrics as your watch.
But as I mentioned in my earlier post SA metrics should be always source of truth for all linked watches to pull when they sync.

stromdiddily

@duffman19 said in Software release 2.30.26:

Am I the only one whose training numbers in the watch match SA? They have since day one of the update.

Maybe it’s a multiple watch issue? The Vertical is my first Suunto in a while, so there was no transition or swapping for me. Although I did import most of my activity history into SA and had to tweak some TSS numbers, but everything lines up for me now.

hahaha thank you for saying this! Mine also match

dzembronja

@Dimitrios-Kanellopoulos Good evening, I think the map without squares will be solved once and for all, but I would like the names of cities and objects on the map, I like the clock itself after 9 baro

dzembronja

@Dimitrios-Kanellopoulos I was just hoping to see a map without black squares in this update, it’s not a lack of clock right? So it’s a software problem right?

Stefan Kersting

Anybody else that has this bug: when zooming out I can zoom max to 1,8 km and not 2,0 km

stromdiddily

@Stefan-Kersting said in Software release 2.30.26:

Anybody else that has this bug: when zooming out I can zoom max to 1,8 km and not 2,0 km

It’s a mile for me…not sure in KMs

I have also noticed now that when you hold the middle button to switch the “action” menu for the map, it is defaulting to the left/right actions (second option) vs the zoom in/out actions (first option).

This is a bit annoying for me. Never do I use the buttons to move the map around.