HotFix release 2.25.66
-
@unocz
what swim style do you practise? -
@freeheeler Open water swimming (basic)
-
@unocz
this is the selected sport mode, as I understand.
I just wonder if you did a simple breaststroke (hands always in the water) or freestyle (hands out of the water to move them forward again)?living sideways
-
@unocz I swam today. When your hand is in the water, you lose the gps connection. Now and then you have to get hand out of the water at surface.
-
Just the normal swimming with hands under the water all the time ….
-
@Highlands
But that’s a joke or? That means it’s impossible to record your track while swimming. It tought this update should fix it. Older models don’t got that problem or? -
@unocz
In fact, if you keep your watch always under water there is no way for the GPS signal to reach it. -
Wow, ok so I have to deal with that….
Thanks anyway
-
@unocz
yes, but that’s the same for every watch.
satellite signals do not enter the water at all. no chance to calculate your position when the watch is submerged only a tiny little bit -
@freeheeler
Yes I just realised that
-
@unocz
what you could do, if you prefer breaststroke, get an inflatable safety buoy with a small wallet compartment and put the watch in there. of course you need external HR and stroke will not be counted, but distance will be correct. downside: you can’t see your time and distance during the activity.
alternatively put the phone in there and track with SA? -
I got another crash, Had battery performance, target distance, heart rate z1, S+ weather insights and active look, breadcrumb nav, it crashed exactly before target 50% notification. This also happened before right at 50% of target set last time.
-
This weekend, while navigating an MTB route with my SV, the watch reset iself to “clock mode”. I had to initiate MTB activity again… I have two records in the app, one with the first part of my workout and another one with the second part.
Is this a known issue?
Thank you.
-
Same thing happened to me today.
I went for a run, and after 900m Vertical exited to watch screen and i had to start activity again.
I had Aerobic Decoupling and Ghost Runner turned on and everything else default for Running (Basic). -
I can’t reproduce any of my previous crashes. I try same route and settings.
-
Small bug I noticed. I am using quite a lot the flashlight during the night when reading the last story to my daughter, having a deem light like the watch is perfect to create the sleeping atmosphere I am looking for .
I have set my watch to get very few notifications, and if I receive one during the flashlight, it makes the light power going down, like I was in watch mode. And I have to reset the flashlight again to get the flashlight potential light.
It repeats after each notificationIt is not much, put yeah, I think it is worth mentioning… May be it is the willing behavior?
-
@Antoine-Lancrenon You could try turning off ‘Recieve Mobile Notifications’ before you do your nighttime routine, that way avoiding the notifications.
-
@mikekoski490 Yes true. But it doesn’t bother me receiving a notification, as I said I only receive the most critical one… I would rather a quick fix… The work around is easy to do
-
How are losing bluetooth connections handled? Last weekend I went on a bike ride and had watch on handlebars. While on pause I went out of BT range (I guess), because I got – after resuming ride. After 15mins belt connected and showed HR for the rest of activity. Is that normal? I am using H10. Please do not recommend Suunto HR belt as it does not meet my requirements. I just got a powermeter and it goes off after 5min (it can be changed) of inactivity. Is this going to be the same? I tried yesterday with a dummy activity and after 10min of pause (powermeter was off) resume resulted in watch reboot. Second test went ok, powermeter woke up and watch received watts. Should this work or am I going to be anxious on every ride?
-
@markeczzz said in HotFix release 2.25.66:
Same thing happened to me today.
I went for a run, and after 900m Vertical exited to watch screen and i had to start activity again.
I had Aerobic Decoupling and Ghost Runner turned on and everything else default for Running (Basic).Same thing again.
Weird thing is, it crashed almost same like last time. It crashed after 900m, on exactly same route, with same s+ apps running.
No crashes between this 2 activities, and there were like 30 activities between, some on same route.
