@maszop Thanks. And weirdly it has now synced correctly some 20+ hours after finishing the activity. That’s what usually happens an hour or two after I’ve grumbled about it on here. I’m inclined to suspect some sort of Bluetooth issue but whether it’s the phone or the watch I can’t say. It’s annoying.

@PhilBee said in new Vertical 2 - auto vs manual laps: yes i guess it must mean that coros record auto 1km laps since the previous auto or manual lap - but what’s wrong with that? to me that makes far more sense Nothing wrong. With that. With Suunto’s approach you can have an automatic lap on each km and an manual lap/interval whatever you wanna call it (in German they are called “Runden”) that are connected with some meaning. Especially if you follow a guide you might have something like 5 Minutes warmup 20 Minutes easy pace 1.6km as fast as you can 10km easy open end - run back home Each of these will become an individual “Runde”. This approach makes sense as well, doesn’t it?

@GiPFELKiND yes, all the time. Haven’t you asked this question in another thread?

@Hashly-Iian but isn’t this an easy to implement Upgrade which would be very heplful! All data and technical basis is already given. Maybe with the step from beta workout plans to the final version…hope so.

@Thibault-B. The PREV INT panel does not bother me and is probably very useful to most runners. My problem, and probably simalar for other older runners, is that I have troubles to read the small numbers. Thus, a temporary screen after an INT would be perfect (maybe 3 sec). I guess most runners would like that in INT REST mode but maybe in INT INT mode it might disturbs some. One other idea, of which I do not know if it possible: Is it possible to show a blow-up screen with the information about the previous lap for a short time after tapping on the PREV INT panel?

@larrybbaker Only pressed pause, and start again 3 times pausing, produces 3 more running activities. The vertical 2 and suunto app is new for me. Last suunto watch was ambit 2/movescount.

@duffman19 Thanks for those links. You’re exactly right—all those navigation features are independent. How that’s even possible is a mystery to me

Yesterday I also had a soft reset during activity. It was simple walking activity, no navigation, no interaction with the watch, and 3 SuuntoPlus apps active. Suunto Vertical 2 with latest firmware. I had soft resets quite often before. Then I did a hard reset and for about one week everything was OK. Now I had another soft reset during activity. I am quite sad about it.

16/05/2023 : first time I used my SV1 (it was release date or very close) Best watch I ever had. Awesome since the beginning, unmatched autonomy

@Egika Ahh ok. Many thx

The watch and phone are connected via Bluetooth, and I’m receiving notifications, but the app shows no connection. I turned Bluetooth off and on on the phone, but it didn’t fix the problem. What else can I do? [image: 1776097483350-a11.jpg]

@Nelson-Diogo ohhh, at least this makes sense also for Suunto … let’s see if they implement in there Race and improve in the Run

Received the Spark today after a weekend order. Paired & updated quickly and have supreme sound. Haven’t tried them in action (on the bike trainer or out for a run) but are quickly becoming my favorites in spite of owning multiple sets of Sonics. [image: 1776298642069-sonic.png]

@simspi https://forum.suunto.com/post/188102

@bobbyfw03 Frankly, I still don’t know who’s responsible for these Suunto Plus Guides, whether they come from Suunto or from Runna.

@inkognito Re random bug: yup, that’s what I’m worried is the truth. Removing & re-syncing didn’t work for me. I have managed to correct a route that was similarly inconsistent by exporting it, opening it in Plotaroute, deleting all hidden auto-created WPs in the “Directions” panel, downloading, importing to SA, etc. Tedious but so far effective for the routes I consider important enough to bother beforehand. A fix for all? No idea. But if you’ve got such a route you’ll do again … give it a go and report back, please!

I experienced the same with distance based zooming. Did report it.

After ANOTHER instance of this same issue again today, I can confirm more closely what is happening: when the issue occurs (after a GNSS-based activity), the calibration feature locks out until the watch is restarted, even if that’s days later. What this means is the altimeter drifts from reality as time goes on, and manually calibrating it won’t stick in the readings more than a few seconds, when the old value overrides. It does not appear linked to rinsing the watch (aka quick pressure changes from water), as it happened without that occuring.

@Brad_Olwin It will be great for Suunto Coach AI !

@Kevin Suunto’s heart rate strap is “smart” in the sense that it has build in memory, meaning that if the watch looses connection for example when swimming, data still gets recorded. Then when ending the activity, the data gets sent over to the watch.