HotFix release 2.25.66

[Ollipolli]

Thats all???
Rly 🥺

[surfboomerang]

@Ollipolli Look at this the other way… Suunto released it to fix this bug as soon as possible.
They could also choose to wait until the next feature update which could be months from now.

[A Former User]

@Ollipolli said in HotFix release 2.25.66:

Thats all???
Rly 🥺

I am no suunto employee, but being part of a product development (not software), testing takes time, and if there are adjustments to be made, testings need to be re-done, so if Suunto “just launched” this, maybe they are making sure that when they correct the other bugs reported they are trully corrected for everyone.
At least I hope.

[Jose Luis]

On my device I have 2.25.48 and I have automatic updates.
Do you have to force them somehow?
Thank you

[Mff73]

@Jose-Luis
i checked version in SuuntoApp before having notification, and it found this new version.
Notification came just after upgrade

[Dimitrios Kanellopoulos]

@Ollipolli what do you mean ? After 2 weeks another update as a hotfix is not ok for you for fixing an issue for openwater ? It’s June and the watch is released late may.

[Jose Luis]

@Mff73 I have the version of the App in iOS 2.260

[surfboomerang]

@Dimitrios-Kanellopoulos Yeah, shame on you Suunto for bringing out too much hotfixes!

[Tieutieu]

@Jose-Luis updates are automatically downloaded into the watch when available, and installed at night (if battery>50%). You can manually launch it without waiting night automatic update : parameters/general/updates

[Jose Luis]

@Tieutieu said in HotFix release 2.25.66:

updates are automatically downloaded into the watch when available, and installed at night (if battery>50%). You can manually launch it without waiting night automatic update : parameters/general/updates

The battery is at 28%

[runomatic]

@Jose-Luis said in HotFix release 2.25.66:

@Mff73 I have the version of the App in iOS 2.260

That is the version of the Suunto App and not of the firmware.

[Likarnik]

@Dimitrios-Kanellopoulos is snorkeling also affected in this fix as it is also loosing gps when under water? I am asking this because today I had worse results than last two days without hotfix. I am not expecting miracles here, but basic info where I was snorkeling. I think I was not on land after 20min it measured 3,5km… maybe it needs to warm up as this was first activity after fix

[Dimitrios Kanellopoulos]

@Likarnik hmm I did snorkeling like crazy with his firmware. It works great.

It takes for me 3 - 10 seconds max to get signal after a 1minute dive at 7m or so.

Go to the maps screen and see if you have signal before you fall to some illusion that you are covering longer distances. In this hotfix has exactly this issue covered that it should not create 500m jumps after a dive. Do you have an activity that this happened ?

But yeah the rule of thumb is to get really good gps before entering the water. Like 2minutes warmup.

[dulko79]

@Jose-Luis wait for 1 week or charge the watch

[Likarnik]

@Dimitrios-Kanellopoulos gps fix was ok, jump happened after 20min and 17 dives (not below 5m). I always try to hold my hand floating on water… maybe it was just a glitch. I’ll send you link in PM.

[Dimitrios Kanellopoulos]

@Likarnik are you sure you are on .66 because this is the exact issue we should have fixed. (saw your activity)

[herlas]

I know hotfix is targetted at OWS, however it also helped correct almost all the issues my GPS track was presenting while I run on a bridge where GPS signal gets temporary blocked from direct sky visibility.

On the left today’s hotfix installed vs on the right before .66 hotfix coincidence? Maybe

[Likarnik]

@Dimitrios-Kanellopoulos yeah, I updated 1h before activity. I’ll try again today and keep you posted.

[Dimitrios Kanellopoulos]

@herlas that is correct. We fix all unexpected jumps lets say. (if possible)

[Likarnik]

Watch recorded only 44min of sleep last night