We need Updates!
-
@Tomas5 you did not suffer of excessive battery consumption with latest fw version ? I rollback to the previous one (2.46.4.25276) and see almost double battery life on a fresh installed watch without any sensor paired
I have to admit that I did not perform a battery calibration when I was on 2.46.14.2621. With 2.46.4 the battery life is like expected 5-6%/day. With 46.14 it was more like 10% a day and some people also revert because of this battery drain (here and on Reddit) -
@Josaiplu after 7 days i have 40% battery left. I did only 2h of GOS activities. Maybe it was little better before but really not sure. So maybe 20% worse than before?? Didn’t notice until now but yes it is worse.
-
@Tomas5 thanks yes, what I have is a bit better
I still have 25% battery after 12 days and 8h of gps + lots of activities without gps (roughly 6.5% a day with activities each day almost)
But not as much difference as I remember. Thanks for your numbers ! -
Just came back to using the SR2 again.
1.Used to have heart rate dropouts while running.
2.After the latest update, the screen keeps locking by itself.
3.Battery drains unusually fast.
4.The app keeps showing “busy.”
5.And well… the watch can’t think on its own — it’s not that smart. You’ve got to sync it with the app first before the data shows correctly on the watch face.
I’ve turned the watch off for now, just waiting for the next update.
Honestly, pretty disappointed to come back to this. -
We don’t need updates we need better QA, maybe more developers and in the end less bugs in the next updates.
But as a sw-developer I know there are all the things that are more important to managers than hard ass bugfixing - new features, for new watches … and of course they are important to keep a company alive.
But somehow they have to figure out that Suunto has always been standing for high quality, durable, outdoor equipment and make this the brands key value.
-
@Ecki-D. hear, hear.
I once learned in a marketing lesson that it is 7 times harder to get a new customer than to keep an old one. That alone should be sufficient to convince managment to improve software quality. As those customers are deciding how to talk about their products…
-
Yes suunto is taking the absolute pi$$ with this battery drain issue. Mine is a the vertical 1 but seems it’s happening on other watches as well. Absolute core feature of suunto is battery life and they are failing hard.
-
Haha, not trying to be negative here, but funny thing — these days even $100 watches seem to have “a mind of their own.”
They update data on their own, no need to beg the app for permission first
Anyway, let’s not take it too seriously… I’ve turned mine off and joined the waiting club for the next update. -
@Josaiplu how to roll back to older firmware?
-
@Tomas5 Hi I follow the process from Tami and I found the fw url if missing see it here https://forum.suunto.com/post/177895
The link is few post below if needed
-
@Josaiplu thanks after rollback to 2.46.4 blood oxygen works when manually measured. But it still measures quite low 88-93%.
-
@Tomas5 ok I don’t use the feature, I’ve read that a hit fix is planned for the next days let’s keep fonget crossed for all these being fixed
-
@Josaiplu i am more curiouse about battery life too. I had to charge after 9days only with very little of GPS activity. So it was noticable.
Esit: after rollback, after 3 days battery consumption is between 5-6% per day with no GPS activities. Just 24/7 tracking.
-
Hello everyone,
I’ve been a Race 2 owner for 10 days (after 4 years with the Fenix 6 Pro) and am actually quite happy with the Race 2, but I’ve read about some issues and bugs with the software here in the forum. To those who have been Suunto users for a long time: how does it work at Suunto? Can we expect regular updates that fix the bugs? I’ve heard a lot of good things about the Race 1.
Does that mean we just need to be a little patient with the Race 2 and the Software? -
@pgrob In general it’s good. But bug fixes take quite a time. If you don’t have any serious bugs, then the best is just not to read complaints from other users, otherwise it’s easy to fall down the “complaint spiral”, I have experienced it by myself. To sum it up, with Suunto patience is the name of the game. (Just my view)
-
@pgrob I have been with Suunto for years, and must admit I have no issues. A lot of the bugs don’t affect me, I’m not saying they don’t exist they just don’t affect me.
I have found the three modern Suunto watches I have had to be well made and reliable.
I think as mentioned above, it is easy to read this forum and see the worst…
-
@Audaxjoe It depends on what features of the watch you use. If you just use basic features like recording activities, it is all good. The minute you start using advanced features like navigation, climb guidance, customized modes, S+ apps, there are bugs that have been ignored for months and months. I can easily make a list of probably 10 bugs that I see regularly, at least 3 bugs that I experience almost every time I use navigation.
For example, how hard it is to fix this graph added to a custom sport mode so that it doesn’t always start with a flat line for the first 30-40 minutes? It should be an easy fix. But it has been over a year since I reported it, and nobody bothers to fix this very obvious bug:
This is something I see every single day because I use a custom sport mode.
-
@sky-runner this is weird. I also use custom sports modes for all activity types, but my HR graph doesn’t look like this. Hmm… Will test it tomorrow.
-
@sky-runner I use navigation all the time. I navigated from Faro to Andalusia this year. 2500km around Norway and lots in the UK.
Last year I navigation from Croatia to the Netherlands via ten countries.
And also use the watch in the mountains.
Hopefully that at least close to advanced usage…
And I always use custom sports modes… Well except for yoga.
I don’t use HR graph.
-
@OutdoorMan May it is because I have pace at the top and HR at the bottom. I’ll try to modify it and see if is different. It works correctly for one time after the watch is restarted, which I guess resets some internal state. But it consistently looks like this on the majority of runs. The “flatline” is always at a different HR - sometimes at a high HR like in the above example and sometimes at a low HR.
Also, to make it clear the “flatline” represents the time before the beginning of a run. In the above example I have been running for 22 minutes but the graph shows about 40 last minutes.
