SW update 2.37.34 Q3

[isazi]

@false default is breadcrumbs because if default was “off” 90% of the users would complain that maps do not work for them. And what if a user uses route navigation once, why should that be remembered? Do you always navigate the same route? I think this is the best default.

[Jonas Vestberg]

@isazi Ok… thanks for the fast reply. It’s strange to have a ring in just that data field that you can’t remove and in a colour you can’t change.
Anyway… I have a Vertical and it’s an awesome watch and I appreciate all the work you guys are putting in to this!

[Mitch9]

@Mitch9 said in SW update 2.37.34 Q3:

I can’t find my favorite watchface for my SV with graphic (solar or height) on the bottom.

I could find it now - only on watch not app. This is really unorthodox!

[isazi]

@Mitch9 each watch has a default watch face that cannot be uninstalled by mistake, and is part of the firmware. The other watchfaces you find in the S+ store.

[pumarkin]

The transfer of the update seems very long (it’s dowlnoading since 1h15 now and at ~39%). It doesn’t look like I have network issue.
Is it same for you ?

[Egika]

@Jonas-Vestberg said in SW update 2.37.34 Q3:

Hi,
And there’s still this ring around one of the data fields that you can’t remove or change on the watchface Modern Analog. I think that was reported as a bug the last FM update.

Reported - yes.
Still Suunto decides how their watch faces look like. This one still looks strange without a data field on the left…

[isazi]

@pumarkin no, it took very little time, but what you see is not the transfer from Suunto to your phone, it is the transfer from you phone to the watch.

[Marius Jacobsen Eggerud]

@jussim To me it seems like it`s still there, but I am not sure if this is a bug. I think it might designed this way.

[timecode]

@Jonas-Vestberg not sure why people refer to this as a bug if it’s also displayed on the package of Race S. So clearly not a bug.

[duffman19]

@timecode said in SW update 2.37.34 Q3:

not sure why people refer to this as a bug if it’s also displayed on the package of Race S. So clearly not a bug.

True. Just a weird design choice.

[false]

@isazi Personally, I navigate so rarely that I was more than happy when the navigation menu was off because I don’t need it on my runs. But since a few updates ago (two, I guess), breadcrumbs have always been on by default (I still believe it’s a software bug). I also wonder for whom such a ‘default’ could be useful. From what I see in running, biking, and trail running accounts on the internet, people usually go from A to B or in a circle, but very rarely back and forth. So maybe if you go deep into the forest to harvest some mushrooms and berries or hike, breadcrumbs might be useful for you, I don’t know…

And what if a user uses route navigation once, why should that be remembered?

Because of the same reason why the choice between an optical HR sensor, HR belt, feeling, autolaps, etc., is saved from one activity to another. The answer here is consistency

[jussim]

@false said in SW update 2.37.34 Q3:

Could anyone tell me if they fixed the always-on breadcrumb option? I mean, on the pre-activity screen, the breadcrumb is always turned on (for the last two releases), even if you didn’t use it during your previous activity

Doesn’t remember the setting, just as speculated

@isazi said in SW update 2.37.34 Q3:

No, I do not even think it is a bug, it is just one option that is not remembered and breadcrumbs is the default.

An odd decision, I must say. My argument against it that if you make a custom sports mode for track running, what’s the use for navigation?

Unless of course Suunto were to somehow leverage it into a proper track mode like seen on competitor’s watches to provide exact 400 m laps

[herlas]

@false @isazi I agree here, if the navigation not being remembered is not a bug, then it’s a decision taken couple of firmwares back, for me it’s going to disable it every single time

Remembering what was used is a far better approach. That way users can have their sports modes where they use navigation turned on, and in others (road running) where you don’t necessarily use it, turned off.

Any time you introduce extra steps needed to be taken, user experience decreases.

I’d vote to revert this to previous behavior

[isazi]

@herlas you are not alone, it has even been requested internally. But, it is not a simple binary setting. What I guess makes sense for you is not remember the navigation setting, but only the off navigation setting. I do not see any point in remember route, POI, and snap-to-route navigation settings for example, users would just be surprised why did they get an “off route” message first thing after starting an activity.

[herlas]

@isazi yes, default breadcrumb is fine those who will use navigation, they can select whatever they want to navigate with, case being made here, when you don’t navigate at all, you have a extra screen you don’t use, so we have to turn off navigation every single time.

I’d like to see this offered in a feature SW update.

[Brad_Olwin]

@Tami999 Not a bug, these are design changes. I believe that color will be coming to some of the complications, this is the start and will make watch faces faster and easier to develop so they are not tied to firmware updates.

[Tami999]

@Brad_Olwin but i noticed it only happena to Vertical watchface. I changed for many others, like Race watchface and colors works. Not gonna lie my favourite watchface is changed and i dont like it white

[orzechszek]

@herlas said in SW update 2.37.34 Q3:

Remembering what was used is a far better approach. That way users can have their sports modes where they use navigation turned on, and in others (road running) where you don’t necessarily use it, turned off.

Great idea, but… when amount of defined sport modes will increase
Why there is a limit in amount of user defined sport modes? Because of architecture or memory? Memory in Race/Vertical seems not be a problem now?

[vlado]

When is this expected to come to Ocean?

[duffman19]

Turn-by-turn notifications are still f-ed up.

If you scroll forward (short middle button press) to the map screen, yes, tbt notifications are now only a vibration/beep, not full screen. If you scroll backward (long middle button press) to the map screen, the notifications are full screen again, same as always. Scrolling forward all the way back through the screens seems to fix it… for awhile. Eventually full screen notifications will pop up again, for no apparent reason.

Seems the simple code “fix” was to cancel the on-screen notifications when scrolling to the map screen so we’re left with just the “tooth” directions (which were already there). But someone forgot that we can scroll both directions now.

And, Suunto, please. Why, why, why, why are we still getting turn notifications for the NEXT turn when we are at the CURRENT turn? If there is anybody anywhere who can tell me why this makes sense, I’ll shut up about it. This has to be the simplest fix. When we get the end of a route it shows “END.” So when we get to a turn, show us that turn! I know you can do it, Suunto.