SOFTWARE UPDATE 2.35.34 Q2

[EzioAuditore]

@Ars-Vitae this is user’s forum and Suunto (although represented by some exceptional people that work for them in it) is not aware of what we write here. Testers have informed about the problem and hinted here and there that new FW is coming so maybe the delay is just because of the bat drain and to try and pinpoint the culprit: there seems to be not apparent pattern that causes it. I feel you (and others pain) though: I have it on the SV too but not on the Race for some reason.

[Łukasz Szmigiel]

@EzioAuditore said in SOFTWARE UPDATE 2.35.34 Q2:

is not aware of what we write here

While I’m aware of this - I still wonder why? This is a gold mine of (mostly) good quality feedback.

[EzioAuditore]

@Łukasz-Szmigiel don’t know It would be great to have something like YouTrack open to the public (those of us with Suunto account) where we can search and report BUGs. They will be flooded maybe but then there can be a secondary level of testers that prunes the real bugs to the feature requests. I mean look what is happening here: the title says something and then there are some people that polute all the posts with the same comment. On YouTrack they could be banned (here too but this is forum afterall you can write ‘whatever’ you want )

[isazi]

@Ars-Vitae it is already a priority, and being investigated. If there are news on the issue being identified and fixed I will share them. As I said previously, it does not affect all watches, it is unpredictable, and it does not show in the logs, so special battery logging functions have been enabled in the test version of the next firmware to try and find the root cause.

[isazi]

@Łukasz-Szmigiel said in SOFTWARE UPDATE 2.35.34 Q2:

While I’m aware of this - I still wonder why? This is a gold mine of (mostly) good quality feedback.

My guess: not enough resources. The head count at Suunto Finland was 300 humans, and one third of them was fired in July. So if people are wondering why the update is taking this long, maybe this is another reason for the delays.

[Ars Vitae]

@EzioAuditore I am aware that this is a user forum, but as you write yourself, information about problems regularly reaches Suunto through testers or people in close contact with them. Among other things, that’s why I appreciate this forum.

[Ars Vitae]

I didn’t pay attention before so I dont know if it’s caused by new update but did someone noticed that in the monthly dotted line summary data of some activities don’t match? An exemple is given below:

[isazi]

@Ars-Vitae this seems app related, not watch related

[Ars Vitae]

@isazi If so, I apologise. I try not to multiply threads, but there’s so much of it on this forum that it’s hard to find something really relevant. In addition, you have named this post a ‘software update’. Isn’t it more about ‘firmware update’? I’ll admit that I didn’t fully follow the content, I was suggesting the title.

[Ars Vitae]

@isazi You can delate my post if you want, I will put it elsewhere.

[The_77]

Did this route the other day and ran into a fun bug with the sections.

As you can see, no major downhills registered on the profile. Despite that, the downhill section from the peak to the end was registered as a 13km long downhill segment with 139m of downhill to go. Despite that apparent to go descent, what instead happened is that the to go descent slowly ticked down, but no actual descent was registered on the running total field.

I didn’t take any pictures as the firmware update soon is fixing things (hopefully), but it was bizarre.

[Lionel B]

@The_77 i think this graph is messed up
Looks related to the bug i posted recently https://forum.suunto.com/topic/11351/itinerary-details-elevation-mismatch-between-global-values-and-ascent-details?_=1724350840713

[The_77]

@Lionel-B I mean the underlying elevation data for that area isn’t great, but it did tally to within 10% or so of what the watch measured so it isn’t awful. Might be more of a parsing issue between the graph and what it actually spits out, idk.

[The_77]

I know there’s a FW update soon, but another graphic mismatch between SA and watch. Watch profile can’t match what is given by the app for elevation data. Underlying map data looked good on SA.

[ajjvbeek]

@moein-rezaei said in SOFTWARE UPDATE 2.35.34 Q2:

Hello
After the new update 2.35.34 my suunto vertical solar watch is weak in gps and also it can find the satellite with delay at the beginning of the exercise
battery mode performance
@isazi and @Brad_Olwin

I have the same issue. When I start an activity I always wait for a gps fix. Be the first 5 minutes or so the location is way off, at least 50 meters. After it is fine.

This started after the update.

[Tieutieu]

Official news/teasing from the app !

[EzioAuditore]

@Tieutieu will this be the Q3 release or the hotfix ( if it can be called that after 2 months ) Or both combined.

[Tieutieu]

@EzioAuditore With the leaks 2 weeks ago and this announcement now, I guess release of this feature is close !

[Antoine]

@Tieutieu i hope the “drain issue” will be corrected also

[Egika]

@EzioAuditore a bit of both