SOFTWARE UPDATE 2.33.12 - Q1 2024

[A Former User]

@Mff73 The navigation option is not remembered once set to another value

[false]

@cjanevate said in SOFTWARE UPDATE 2.33.12 - Q1 2024:

@false Regression in sw development unfortunately can happen

For sure, but I am, but actually “we are”, talking about extremely basic scenarios and not even an edge cases (i.e “push this button 3 times then push that button 4 times then turn around and get a bug”)

Always-on breadcrumb is only nuisance imo.

Yes, it is, but, imo, such easily reproducing bugs (one button push away from a user) must be eliminated before rolling a release. Really, I can’t believe. All in all, Suunto isn’t a small indie dev company that can afford to neglect such matters.

PS: especially when users have to wait for months till next firmware update

[A Former User]

@false said in SOFTWARE UPDATE 2.33.12 - Q1 2024:

For sure, but I am, but actually “we are”, talking about extremely basic scenarios and

unfortunately, until they discover the problem, there is nothing they can do, and rehashing the same concerns does not help them. if you do not tolerate this, you know the solution…

[false]

@cjanevate said in SOFTWARE UPDATE 2.33.12 - Q1 2024:

if you do not tolerate this, you know the solution

Yes, make it open-source

[enriqueescoms]

@Mff73 Now, by default, when we start an gps activity, the breadcumb screen is always activated. Of course, you can deactivate it before starting the activity. But it doesn’t save the settings for the next one. It’s not a big problem but it can be a bit of a nuisance.

[Mff73]

@enriqueescoms
Ah OK.
Any one has its own level of nuisance tolerance.

[Łukasz Szmigiel]

@Mff73 I find it problematic not because it’s there, but because it’s another screen to cycle.

The workaround that I have for being unable to cycle workout screens to the left is to have just two of them and no navigation (if I don’t intend to use it). This way I either see first or the second screen upon middle button press. Or one S+ if I (rarely) use it.

It’s the same as being unable to disable the vertical navigation screen, which is strangely glued to the navigation if the route is active.

[Mff73]

@Łukasz-Szmigiel
i was just questionning myself, no judgment.
It was an option, it was remembered, it is not anymore, it is not nice, it is a “bug”.
Then, it is just few clicks to remove it, and “remove it each time” is the definition of a nuisance I got it

[Łukasz Szmigiel]

@Mff73 no problem, just wanted to shed some more light on the context of it.

[The_77]

Small bug (9PP): When using usual touchscreen off, if you go into navigation during an activity, and then go down to options like routes/POI/etc, touchscreen works, which surely can’t be intended. Can swipe in menus.

[Wilson75]

I am facing strange behavior with map also.
I don’t know if I’m misusing the map function but I remember (before update) that when I used my map during an activity, a few seconds after manipulating the map with the touchscreen to look around me, the display automatically returned to my current position. It was sometimes annoying because I hadn’t finished my research.

Now I have the opposite problem, after my search on the map, the map remains at the same location of my research and I sometimes have difficulty to get back to my current location.

I hope that I am clear

[Arnaud Lclr]

@Wilson75 double tap on the screen and the map returns centred on your position.

[Wilson75]

@Arnaud-Lclr I feel so lonely … thanks

[Tieutieu]

@Arnaud-Lclr For me it’s a “simple tap” that make the map centered again.
Anyway for me it’s a nice improvement

[Brad_Olwin]

@Wilson75 This behavior was implemented for the ruler on the map. If the map auto-centered while using the ruler it would be quite frustrating. One tap should re-center.

[fleblanc01]

@Brad_Olwin kudos to suunto, this is simple and works great

[DrSilverthorn]

I was using the treadmill activity with a custom S+ guide for an interval workout. I started the activity. I then decided to change the S+ guide to the manual interval app. So I went into settings, enabled the manual interval app and disabled the custom S+ interval guide, and then resumed the activity. What I found was that the originally selected custom S+ guide was used instead of the manual interval app.

Maybe you can’t change s+ apps during an activity and this is by design - but if so, the watch should not allow you to change any of them via settings.

And on a different matter - the OHR is ever so slightly improved for me. On a very warm day (32C+), the readings can be quite good. But even at 30C or lower, they can be spotty or cadence locked. In fact, cadence lock seems to be an issue for the OHR (at least for me).

[zanxion]

@Tami999 I solved it on my watch by doing nothing on Thursdays
Kiddin’ of course. I just realized it on mine too and it seems to always happen on the first column of the five.

[cemoi71]

I had a strange issue on my s9pp with the firmware, which leads to think that some bugs are still inside else where.
somehow a king of buffer overflow or something like that.
One day last week I trigger a training as aerobic, and 1st i activated the bleep test from suuntoplus. But delete it and and make a new one and deactivate the function (wasn’t needed obviously).
Then the next days i made the same training, and every time that i triggered it, appeared around 10 or 12 min some beep and vibrations from the watch at irregularly moments until the end of training sometimes 2 or 3 time spaced on few seconds, and was really hard for some session to concentrate me because of this.
The watch displayed nothing special different when it came.
And after a week I had a look on the app by each training, and by some of them, the bleep test data appears , by other not.
The only action that I found to stop it, was to deactivate (uninstall the suuntoplus bleep test) and restart the watch…
Had someone experiences a similar issue ?
I’m thinking about to create a separate topic of this eventual issue or bug…

[Artus Diver]

@Ecki-D, @Brad_Olwin
I would also like to get detailed information about this new functionality, but it is not in the documentation.
For me it sometimes works and sometimes it doesn’t.
To be precise, to force this new function to work, the speeds must be much higher than, for example, “autopause” and the reaction time is very long.
The guys from Suunto support suggested a factory reset, but I don’t need this function that much to lose the collected data on the watch.

P.S. I checked several times on two SV copies and this function has difficulty working in non-standard modes.
Maybe it’s accidental?
I’m curious about other users’ comments.