Software Update 2.40.44 Beta (2025 Q1 Hotfix)

[pavel.samokha]

@cosme.costa Just to clarify:

The thing mentioned in notes is about fixing issue when with every S+ watchface update settings were reset.
For example: you installed a watchface from S+ store, configured complications, we updated this watchface in S+ store => your complications reset to defaults. Now this should be fixed, S+ WF updates should not reset your WF settings.

[dulko79]

SRS updated without issues.

[suzzlo]

no stepcounter upgrade for Race?

[pavel.samokha]

@suzzlo basically all other watches will use the same step counter algorithm as Race starting from this release

[Artus Diver]

@pavel.samokha

Any changes to swimming in the pool?

[cosme.costa]

@pavel.samokha said in Software Update 2.40.44 Beta (2025 Q1 Hotfix):

@cosme.costa Just to clarify:

S+ WF updates should not reset your WF settings.

In my experience, with all the firmware updates since the introduction S+ watchfaces, the watchface is reseted after some hours out of the blue, then you need to configure it again and no issues anymore until next update. I do not know if the watchfaces update in s+ have happened at the same time or some hours later after the firmware update and for that reason I relate them.

[Miroslava]

@Artus-Diver yes we want correctly swimming breastroke because watch no counts meters.

[Łukasz Szmigiel]

S9PP, it works

[James Eastwood]

@Łukasz-Szmigiel shame that TSB complication not updating unless an activity is started is not in this bugfix release.

[pavel.samokha]

@Artus-Diver Sorry, no changes in this release as far as I know. There should be some improvements in Q2, but I cannot say if they solve all the issues.

[larrybbaker]

Installed with no issues. Will run later today.

[SailingP]

Installed successfully on Race S.

[SailingP]

@James-Eastwood said in Software Update 2.40.44 Beta (2025 Q1 Hotfix):

@Łukasz-Szmigiel shame that TSB complication not updating unless an activity is started is not in this bugfix release.

I agree, I would like to see this problem resolved. I know that there are worse bugs and there is a workaround for this issue, but even there I would welcome it if it was resolved.