I had this too, and it went away with a restart. My suspicion is that it has something to do with offline map updates. I got the “map update” screen while starting charging yesterday with no update ongoing (AFAIK). After the firmware install, I kept getting that notification every time I was checking the map. Gone after the restart. Hope it won’t bother me this we in Berlin

@elevationpain Yes, I have checked the iPhone/iPad logs. They show several fatal crashes. I’ll DM you the recent ones. Have just updated to iOS26, so the older ones were deleted. Thanks!

@gone-troppo said in Battery drain after update 2.44.46 (2025 Q3) on Vertical Watch: 44% to 4% in last 24 hours wtf is going on? I have tried every possible fix to that this forum and fb groups have recommended and nothing works. Is suunto aware of this issue? Is there a fix coming for it ? My suunto vertical which was so great when it was released is now nothing more than an Apple Watch that needs constant charging. I have been with suunto for many years but this is a disgrace. My old ambit 3 peak doesn’t have these issues. I love the suunto app and how suunto ecosystem is I don’t want to change but this is borderline unusable. Watch drains more than 1% per hour when not even doing anything and every battery sucking setting disabled. What a joke You can stop (throught parameters) and restart the watch. It seems it has solved temporarily the problem… (now 4% in 24h as before). But sure there is something to correct, because before restart i was at more than 12% per 24h. I hope that suunto team is avare of that and it will be solved soon.

@kamarasm Hm, you could be right. Then 2.46.x would be the last version for the old watches while Run and Race 2 will get 3.x.x updates. Sounds plausible

I also encountered that bug and first thought it wouldn’t work. If you look closely, you should be able to see a marker in the grey area after 10min. The good side of the bug: when it turned green I know that I temporarily crossed LT1

@Chen-Avinadav said in Suunto Race S pace track problems: Still I get a very weird looking pace graph, see below. I stand corrected regarding the simplicity of my assumptions. I have only ever seen it being dependent on pace variations, but your latest example really proves it to involve other things as well - could be a time element. When I suggested uploading the .fit file to an analysing site, I specifically had those in mind that unpack the data so that you can examine the raw numbers, like at https://www.fitfileviewer.com/ But using a site which displays a nice overall graph view obviously works just as well.

@peegee Why don’t you simply zoom out by rotating the crown? That should be easier than panning the map around, especially when moving fast I know that may be a rhetorical question because trails disappear from the map when zooming out, so the question is more towards the Suunto team.

Well : it’s quite very very strange… At wake up this morning it’s was still displaying the same message error. I have tried a « desperate » soft reset… Then it has switched to « improving you watch… » Then error message with fw, the « decide has woke up after an error » …then watch turned ON…without all parameters ok, personnal sport modes…only sleep and vfc history seems to have been reseted, and hr zones have been also reseted (and running specific zones was pinned again). Seems that 2.44.46 has been reinstalled automatically Very very strange ….

@Marro What I realized is that the first time you use a new sport mode that you haven’t used before, whether it is one of pre-built sport modes or a custom one, you have to manually connect to a sensor. That can be done in the beginning of an activity at the start screen, by scrolling down to Exercise Options and then to Sensor Data. Once you’ve connected once, the last used sensor is stored in the sport mode and next time it connects automatically. I think this is a poor implementation on the Suunto side because this is not discoverable, not how Suunto watches worked before, and not how other brands work. This should be addressed.

@Francesco-Pagano Today I tried a different interval workout and that screen appeared. In the meantime, I found a bug which might be related to the missing screen in the previous workout: if you set an interval with a pace target between 3:40–4:00, the app changes it to 3:39–3:59 after creating the interval. At least on iOS, this happens. I don’t know why, and I’m not sure if that’s what caused the screen not to appear. There are also some other strange bugs across the app — for instance, my height is set to 181 on the watch, but the app shows 180. But going back to the intervals screen: At the top, it shows the target pace for the interval. In the middle: current pace, interval target pace, heart rate, and remaining distance. It would be interesting not to repeat the target pace twice – next to the current pace it should instead show the lap average pace.

My training plan for week 3 doesn’t sync to the watch. How can I fix this?

Today possibly cadence lock in first half? Not sure but strange change in middle of activity while i walked same speed all the way.[image: 1758175867575-img_0893.png]

@David-Kleman I generally don’t trust HR from the watch for any serious considerations. I agree with @brave_dave I have the same experiences with HR. I mainly use it for GPS, recording my daily routes, speed, Altitude and distance. Even SPO2 is not that accurate; it shows 92-94% and the actual monitoring system goes to 96-98%.

@duffman19 thank you very much. I did not change max hr and set the other ones and it worked

Interesting video on zone sense on the nakan. ch channel Sorry it’s French but YouTube now allow live translation hope it will help some to better understand zone sense There is also a blog post to read that I did not had time yet to discover

@jannis