SOFTWARE UPDATE 2.33.14 - HOTFIX Q1 2024

[Brad_Olwin]

@murphyp228 Already reported to Suunto.

[murphyp228]

@Brad_Olwin Cheers

[false]

400 messages including lots of annoying bugs in the previous update thread… I wonder how did Suunto choose what to fix and why they stopped on these two bugs only

Fixed a problem with SuuntoPlus device communication

and then
@murphyp228 said in SOFTWARE UPDATE 2.33.14 - HOTFIX Q1 2024:

Hi since the update the sunnto app is no longer saving edits to a workout - doesn’t seem to be saving or syncing

The first ever product on which I’ve turned auto updates off is my Suunto watch

[freeheeler]

@false said in SOFTWARE UPDATE 2.33.14 - HOTFIX Q1 2024:

I wonder how did Suunto choose what to fix and why they stopped on these two bugs only

maybe time? it seems to be a limiting factor in several projects and tasks…

[Brad_Olwin]

@false said in SOFTWARE UPDATE 2.33.14 - HOTFIX Q1 2024:

400 messages including lots of annoying bugs in the previous update thread… I wonder how did Suunto choose what to fix and why they stopped on these two bugs only

Fixed a problem with SuuntoPlus device communication

and then
@murphyp228 said in SOFTWARE UPDATE 2.33.14 - HOTFIX Q1 2024:

Hi since the update the sunnto app is no longer saving edits to a workout - doesn’t seem to be saving or syncing

The first ever product on which I’ve turned auto updates off is my Suunto watch

The app issue is unrelated to watch firmware and is only an issue with the beta version of the Suunto App. Beta versions may have bugs, after all they are beta versions.
Suunto does not post a detailed list of fixes, we do not know which are bugs or which are user issues, certainly some of the posts are the latter. Improving the firmware will introduce bugs and during testing not all bugs are seen. The forum certainly helps with this. My auto updates are on.

[A Former User]

@Brad_Olwin said in SOFTWARE UPDATE 2.33.14 - HOTFIX Q1 2024:

Beta versions may have bugs, after all they are beta versions.

…and the watch firmware isn’t beta, so no bugs!

[JonasLarsson]

Saving edits to a workout is working again.

[SuperFlo75]

I updated yesterday, I was late because I didn‘t want to charge the watch earlier, and until now, I didn‘t found any problems! I‘m really lucky…

[Francesco Pagano]

I installed this update last week and this morning I charged my watch for the first time since then. It didn’t charge beyond 73% even after putting off the charger and back on.
Has this been already mentioned or experienced by anyone? I couldn’t find anything similar on this thread nor on the forum

[Mff73]

@Francesco-Pagano
is your watch showing the screen that it is plugged to the charger (the screen with big % in the middle ? )?
did you softreset your watch to see if it changes something ?

[Francesco Pagano]

@Mff73 no during the whole time the screen went dark, I could only see the charge advancement on the watch face if I moved it.
I did a soft reset but then went to work, I’ll try again when I go back home

[Александр Даниленко]

I found a bug.

I don’t know if it is related to this firmware or any of them.

It is about roller skating. It seems that “ascent” and “descent” calculation is totally wrong. I had now 40km inline skates ride and it shows me only 10m ascent/descent, which is definitely wrong! (there were tons of uphills on my way made me swear 2nd half of the way ). I also checked a bike ride on similar route, which was recorded with strava in the past and it shows me 650m ascent.

You can see it doesn’t even make sense to have only 10m ascent/descent, when highest point is 35m, and lowest 12m. However, even this ascent/descent plot doesn’t look realistic.

[sartoric]

@Александр-Даниленко
Still have to ride after the hotfix, but it was ok before

[Александр Даниленко]

@sartoric at least as far as I see, it calculated ascent/descent correctly for walking with current firmware.

Also, for other activities like cycling, running, skiing it was fine (with old firmwares).

This was the 1st time it tried roller skating. The distance, speed seem was fine, but climb hight is wrong as we can see. Even the plot doesn’t make sense (for example, it should be descent in the beginning, but the plot is completely flat), despite even there ascent/descent should be more than 10m.

I also checked in the watch - it is the same there:

So it is watch problem, not the app.

[Sami Turunen]

@Tieutieu said in SOFTWARE UPDATE 2.33.14 - HOTFIX Q1 2024:

’m not concerned, but do you know if this update also fixes the sync issues that some users are experimenting

No its not. I fixed that bug by switching to Garmin.

[A Former User]

@Sami-Turunen so you’re ready for the new ones

[Sami Turunen]

@cjanevate

[misu763]

@Александр-Даниленко

I found a kind of bug too. No clue if it came with the latest upd.

I use the light stripe watch face. I had to occasion to travel trough different time zones and now the stripe doesn’t appear as right. Now it looks as a full closed ring and it doesn’t show the light time anymore.

It basically doesn’t come back to a current time zone.

It is not a major problem in my opinion…but it happened!
No problem for me to change the watch face. I will sync the S9PP again, (and more than once time) with the app…maybe it needs more time to identify the current position…

Just to say!

[Egika]

@misu763 this is not a bug and has been like this before.
Please get a GPS fix at your current position - voila, the daylight ring will be back

[misu763]

@Egika
oh! Does it mean I have to set a running session in order to fix it? I will do it later today!
Many thanks for your suggestion!
This forum is plenty of preciuos tips and tricks!! Thank you!!!