SOFTWARE UPDATE 2.35.34 Q2
-
@Tieutieu said in SOFTWARE UPDATE 2.35.34 Q2:
complication…ok but no possibility to tap to change display. For instance I was using the « sr » watch face on my Sv. I was able to see ctl/hrv…in the bottom and changing by taping. Not possible anymore. For me that’s a regression. But I’ll get use to that.
It’s a pity to lose this nice WF, also would it provide direct compass information together with sunrise/sunset etc.
And why should these colors be so bright, more faint colors should also be nice next to the bright colors.
-
@mheesbeen_forum said in SOFTWARE UPDATE 2.35.34 Q2:
Is there an official way to report this to Suunto?
Contact support
https://www.suunto.com/en-gb/Support/ -
@mheesbeen_forum Hi, there is an open discussion about this : https://forum.suunto.com/topic/8851/no-map-problem
-
My Race S is also suffering from battery drain and so far nothing has helped. I have turned pretty much everything off (AOD, 24/7 heart rate tracking, sleep monitoring, WiFi, weather complications) and it is draining about 1% in every 1 hour 15 minutes even if I’m not wearing it. So without any activities and basically not using the watch at all, it drains 20% of the battery in a day. According to Suunto, it should last 13 days with similar minimalistic use.
-
@sracer said in SOFTWARE UPDATE 2.35.34 Q2:
My Race S is also suffering from battery drain and so far nothing has helped. I have turned pretty much everything off (AOD, 24/7 heart rate tracking, sleep monitoring, WiFi, weather complications) and it is draining about 1% in every 1 hour 15 minutes even if I’m not wearing it. So without any activities and basically not using the watch at all, it drains 20% of the battery in a day. According to Suunto, it should last 13 days with similar minimalistic use.
Hey 🥱the battery calibration is not more as a funny Thing… Didnt work… You can read so much Statements here in the specific topic with this Problem. This should have the FIRST priority from SUUNTOs fix list for a new Update!
If Not – The big feature with looooongest battery is not more than a Joke. Was better at the release of the watches. Garmin now comes little bit closer to the people if suunto didnt fix this battery Problem
-
@GiPFELKiND said in SOFTWARE UPDATE 2.35.34 Q2:
@sracer said in SOFTWARE UPDATE 2.35.34 Q2:
My Race S is also suffering from battery drain and so far nothing has helped. I have turned pretty much everything off (AOD, 24/7 heart rate tracking, sleep monitoring, WiFi, weather complications) and it is draining about 1% in every 1 hour 15 minutes even if I’m not wearing it. So without any activities and basically not using the watch at all, it drains 20% of the battery in a day. According to Suunto, it should last 13 days with similar minimalistic use.
Hey 🥱the battery calibration is not more as a funny Thing… Didnt work… You can read so much Statements here in the specific topic with this Problem. This should have the FIRST priority from SUUNTOs fix list for a new Update!
If Not – The big feature with looooongest battery is not more than a Joke. Was better at the release of the watches. Garmin now comes little bit closer to the people if suunto didnt fix this battery ProblemI’m writing this post only to statistically reinforce the arguments for fixing the biggest problem of the new update: the battery draining far too quickly (even more than 10 times) even when the watch is at rest. The problem affects a large number of us, it’s no longer a matter for a few people. All the other bugs the new update has caused are completely dominated by the battery problem. It’s abnormal to have to charge the watch at least once a week even when it’s not in use. I hope that the message of my post and others will be suggestive enough to make the issue a No. 1 priority and speed up the bug fixing procedure.
-
@mheesbeen_forum same for me, sometimes I have to zoom out to 500m to see something and sometimes it’s just blank. Reporting black grids could be a full time job
-
@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.
Suunto watches: Ocean, Race, Vertical (Titanium Solar Sand), 9 Baro (Ambassador Edition), Spartan Ultra (Copper Edition), Ambit 2, S6
Suunto Wing -
@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.
S9PP 2.37.48
-
@Ł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 ) -
@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.
-
@Ł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.
-
@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.
-
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:
-
@Ars-Vitae this seems app related, not watch related
Watch: Suunto Vertical Ti
Blog: isazi's home
-
@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.
-
@isazi You can delate my post if you want, I will put it elsewhere.
-
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.
-
@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 -
@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.
