Firmware 3.19.16

[A Former User]

@ShinJCD Now it works fine for me. At first it seemed not, but after a while it synchronised.

[ShinJCD]

@6iovanni said in Firmware 3.19.16:

@ShinJCD Now it works fine for me. At first it seemed not, but after a while it synchronised.

I still have different values ‍

[Egika]

@Alpha-156.42 maybe I still don’t understand your question, because for me it is very clear.
rpm: how many steps (left foot to left foot) you did on average per minute (<- this has been the Suunto approach to steps in other models)
spm: how many steps (left foot to right foot) you did on average per minute.

spm = 2x rpm. the maths seem to be correct.

[A Former User]

• Pause/resume reminder

In my opinion, it is still a little sensitive

[isazi]

@brechtvb maybe Suunto will do the same for other watches too

[9ppuser]

@isazi Thanks for the update. Unfortunately, two things I would have liked to see in the update are not included.

• an option for “raise to wake up” - display only, not fully awake!
• global switch for sounds and vibrations off

[ShinJCD]

@ShinJCD said in Firmware 3.19.16:

@6iovanni said in Firmware 3.19.16:

@ShinJCD Now it works fine for me. At first it seemed not, but after a while it synchronised.

I still have different values ‍

I solved it with the restore.

Returning to the update, for me the option to reduce the minimum time for the display to turn off is still missing, since 5 seconds are already more than enough (the minimum that is now, that is 10 seconds, is definitely too much). Furthermore, I do not see anywhere the option to activate/deactivate automatic brightness (I understand that there is a display brightness sensor anyway).

[A Former User]

@ShinJCD said in Firmware 3.19.16:

since 5 seconds are already more than enough

Yep!

[danyel]

@isazi said in Firmware 3.19.16:

Support for cycling power meters

Oh wow, that’s quite big, really makes the Run a proper watch for triathlon.

[brechtvb]

@danyel I wonder, is the suunto run compatible with a seperate cadence and speed meter?

Linking a garmin cadence and speed meter is not possible.

[ShinJCD]

This afternoon’s run: same 1km route repeated 8 times (4 out and 4 back). The GPS position at the start is already completely off, the road is quite narrow (two cars can barely fit) so all the gap you see in the various passages is definitely too much. All this to say that, if it’s true that the chipset is the same as the higher models, either it isn’t or there’s some problem in the firmware here too.

[A Former User]

@ShinJCD Uh! I’m assuming you waited for a GPS fix and synced your watch before the activity, right? You didn’t say: multiband?

[ShinJCD]

@6iovanni said in Firmware 3.19.16:

@ShinJCD Uh! I’m assuming you waited for a GPS fix and synced your watch before the activity, right? You didn’t say: multiband?

Yes to both questions (although I’m not 100% sure about the multi and), and it’s not the first time that I’ve had such crazy results, only this time they were quite significant.

[A Former User]

@ShinJCD If it keeps recurring as you say, I would send all the gory details to support via SA (feedback).

although I’m not 100% sure about the multi and

battery set to Performance

[Mff73]

@ShinJCD
In term of GPS accuracy, one day can be “bad”, and in parallel to chipset, each watch also have its specific antenna.
That said, this track is not super good.

[ShinJCD]

@6iovanni said in Firmware 3.19.16:

@ShinJCD If it keeps recurring as you say, I would send all the gory details to support via SA (feedback).

although I’m not 100% sure about the multi and

battery set to Performance

Yep

[ShinJCD]

@Mff73 said in Firmware 3.19.16:

@ShinJCD
In term of GPS accuracy, one day can be “bad”, and in parallel to chipset, each watch also have its specific antenna.
That said, this track is not super good.

In fact, as I was saying, it’s something I noticed right away. And that’s not a good thing, because it’s one thing to flaunt technical data to showcase a sportswatch’s features, but it’s another thing for these features to be real and usable by the end user.

[Gunnar]

@ShinJCD Did you have better tracks on this route before? With Suunto Run or other GPS watch?

[ShinJCD]

I’m returning to the topic of “GPS quality.” This afternoon’s run: in the first red circle on the left, you can see a noticeable deviation from the main road. I enter my town’s sports field: there’s no running track (there used to be, now it’s just dirt and grass, but I can more or less run a 400-meter lap regularly), so I start running several laps, using predefined points as reference points (to ensure the laps are as “regular” as possible). As you can see from the rightmost circle (I highlighted this one because the deviation is more glaring), there are some errors in the GPS that, in my opinion, are too serious to be real… I should point out that, in this case too, I waited for a GPS signal before starting the run, with the battery set to “performance,” and that the sports field is completely outdoors.

[ShinJCD]

@Gunnar said in Firmware 3.19.16:

@ShinJCD Did you have better tracks on this route before? With Suunto Run or other GPS watch?

Before the Suunto Run, I used a Huawei Fit 3, and the GPS tracking was nearly perfect. I’ve previously owned several Amazfits and a couple of “WearOS” smartwatches (Ticwatch and Oppo), but I’ve never encountered any issues like this. The Suunto Run is my first “serious” sports watch, and obviously, I wasn’t expecting such poor quality in this regard.