SOFTWARE UPDATE 2.35.34 Q2
-
@Mff73 a FW change does not wipe all settings. Some are reset like the autopause, but everything else is kept.
You are completely right in saying that some effects are independent of the FW and some things just seem to be.
-
@false the battery drainage actually has been fixed in the latest firmware. Just do a full circle charge as discussed.
-
I still have some HR Sensor issues. When leaving the watch on a table for a few hours, sometimes it stops the sensor. Putting the watch on charger re-activates it, a reboot too.
-
has been fixed
Do you know if it was the first fix of that type?
Anyway, I’ve just sold my 9pp and I hope my next watch won’t have such problems. Deciding between race and 265/955
-
@false yeah I know. It was related to the map / navigation screen.
-
@darxmurf I had the same problem with my 9PP. I had to restart it every time. The downgrade finally helped. But maybe not a solution for everyone
-
During exercise (running), only the map interface beeps when the guide message display ends. Can this beep be removed or can it be set by itself? A great feature has been added to automatically center my location on the map with settings after what time it should happen. Is there an idea to create a personal setting for the time the guide displays during the exercise?
-
@Dimitrios-Kanellopoulos Nice, thanks for the info
-
I noticed that synchronization of pool swimming is not correct. Watch vs. application: 450 vs. 400 m and 1000 vs 975 m. In both cases I stopped during swimming. Yesterday I did 1050 without break and synchronization is correct. Before update I never noticed issue.
-
I’ll gently leave it here and, immediately after posting, dash away like a madman
-
Thank you, @Elipsus, for your informative elaborations. They allow, based on reasonable grounds, to better understand thoughts and decisions behind the further development of the firmware.
Am I right to assume that all your explanation is informed by the actual design considerations of the SUUNTO development (not just good hypothetical explanations), and that they - in that clarity - have not been documented for users to reconstruct elsewhere? If the latter is wrong, I’d appreciate if you could let me know where users like me can inform themselves on such matters.
I understand and fully agree with you that the conversion of the UX between watches makes sense from a SD POV (and from a manufacturer’s budget perspective), and that choices have to be made, i.e., compromises on performance, functionality, usability, warranty level of functionalities, “costs” etc.
Re scrolling: as long as the Vertical has no wheel, the design conversion with the race might be thankful for the devs but with no value per se for Vertical users, or even outrightly irritating.
Re “full vertical”/“full horizontal” and doing whatever with any cake: there might be some middle-way… Maybe even a middle way with more than one widget pinned. But in that case particularly, I understand that memory, battery-life, and smoothness argument etc. weight heavy on what’s possible at all.
Re “do as the others”: I largely follow your argument, with some limitations. Yes, transitioning to the SUUNTO platform form another one should be intuitive from a UX perspective. However, that is, transitioning away from SUUNTO becomes easier too. Also, a watch manufacturer certainly wants to be well-aligned with the established dominant design of a certain device/platform. However, going too far there means risking originality, copying bad design decisions from others, and not making use of (hard-/software) design idiosyncrasies of ones own platform. Yet, this certainly is a strategic decision. Accordingly, it would not surprise if the recent design decisions are also informed by the changes in ownership of the brand…
Your explanations simultaneously imply, as reasonable as they are, that quite some design decisions by SUUNTO making for more or less constructive controversies here in the forum
a) would originate in the (over-)weighing of the developers perspective over the users perspective, and/or
b) have been poorly understood by quite some users (or have been poorly communicated by SUUNTO?).Both, (a) and (b), could be addressed by some transparency on the decisions and the evidence behind them. That is: “If I (at least could) know that I’m the only user who likes a certain feature, who am I to complain if it’s stripped away…?”.
As a side note, with your elaborations (to a large extent) being a good counterexample: My impression is that quite often in discussions on new developments in this forum the tone tends to tilt towards a not very constructive direction. As answer to legitimate requests on firmware design decisions after the fact (like: what just happened to my watch in the update last night?!), rather than good evidence and reasonable explanations (maybe even offered preventively, as announcements?), mockery and an “I like the new better, basta”-attitude even by informed users prevail…
-
@alschmid please remember - this is a user forum. That means an exchange between Suunto users.
There are some exceptions, where Suunto devs chime in for certain aspects like S+ development.That means it is totally fine to speculate what is going on behind the scene in Suunto product management. Still I don’t know what results a discussion based on speculation could yield…
You can be assured that we will never know the technical or dev resources or any other constraints that drive decisions.
t6, S6, Elementum Terra, Ambit 3 Sapphire, Spartan Ultra Copper, Traverse Alpha, S7 Graphite LE, S9B Ambassador, S9P Granite Blue Titanium, S9PP Titanium Sand, Vertical All Black, Race Titanium Charcoal,
Race S All Black - TI Canary - Titanium Courtney -
Hi @Matúš , I get that same phenomenon with the distorted pixels on my Vertical Solar Titanium on quite some of the screens, too. Any idea what’s the problem here, display vs. software?!
-
Hi @Egika. No worries, I’m aware of the limitations of a user exchange. Which is also why I was asking about the degree of speculation or knoweldge…
At the same time, one could assume that its in the interest of the brand product management, running a forum with early-adopters and engaged users (under the official brand domain), to “harvest” the power of the community… That would include providing “sneak peeks” as well as announcements, and using feedback to manage the development roadmaps.
-
Every three weeks again. Heart rate measurement of the 9PP stops at night. No sleep recording, no HRV measurement. Soft reset and on to the next 3 weeks.
-
Hello . My synchronisation problems continue. One week without any problems and then… yesterday, a big 57 km trail and this morning… no synchronisation of activity possible (sleep and everything else ok). So standard procedures + soft reset. except that things are going wrong. I’m using the latest update of the app on iOS and it’s impossible to pair the watch. It takes me an average of 10 attempts to receive the pairing code and then the watch displays paired mobile while the application says pairing in progress before displaying the message impossible to pair. The watch then appears in the Bluetooth-connected devices on the phone but is not paired… strange and annoying. I have to admit that the cup is starting to fill up dangerously. It’s clear that it’s either a problem with the watch’s internal software or a problem with the application.
-
@ODo67 uninstall and reinstall the app please. Keep me posted.
-
Bad swimming distance synchronisation Vertical -> iOS App
Same as @Tomas-Fejfar. Vertical does not count pools properly but OK…it does not even synchronise distance to Suunto app right.
-
Sunrise / Sunset complication is draining battery
May be it is just coincidence but when I put Sunrise / Sunset complication to my watch face it starts to drain battery. With “seconds” instead it seems to be ok.
-
I’m new to Suunto and as I read through all the issues above I can’t help my self to ask:
Is Suunto working on some hotfix release? Or is 2.35.34 considered to be successfull update and users have to wait next few months for all the issues to be potentialy fixed?
Thank you
