@MikeC30 @markg pretty sure this is a bug in the app.

@bbx100 Same issue here (vertical 2)! It looks like an old bug that had already been fixed, but somehow it seems to be back again. Also, I’m not completely sure, but it seems that some OTA updates may be installed on the watch without any notification.

@colakovitz You just need it for the pairing (initial connection), afterwards not. Eats a lot of battery…

@zhangschmidt while looking for some material in order to get back some old movescount features like training plan I stumbled uppon what maybe was your site. You had a lot of material, which unfortunately is not up anymore, if you still have some of them ,specially in what would concern movescount training plans I would be keen to have it to see if I can reproduce something.

Is there a difference in oxygen saturation settings? You want that turned off. It uses quite some battery, the measuring on the wrist isn’t accurate and, quite frankly, even with accurate numbers isn’t that useful for most people.

@hhouter Yes, this was my personal experience. I usually wear watches on left hand and with my scuba configuration, POD is on the right side. First dive in a pool with left/right configuration resulted in multiple disconnects. After changing to right/right configuration, I did not notice any distinct disconnects (either in pool or outdoors). Worked great for like 10-15 dives, until POD suddenly did not wake up at all (probably not related to weak POD/watch connection, still trying to get it working again). ps. since left is usually reserved for physical pressure gauge, we don’t have any other option, but to put POD to the right side and depending on how low you put your tank, POD needs to penetrate neck or even spine area in cross pattern configuration. pps. max distance for POD/Watch is 1,5m (by manual documents for connecting without obstacles), POD distance is like ~50cm to neck area, so it’s 1/3 of max theoretical distance, so the only option is to eliminate as much resistance for signal as possible.

@Kowalski I’m waiting for a successor of the Race S as well, decided not to go with the Race 2. But it felt surprisingly small for its size…

@isazi thanks! This is the first time I’ve seen it too (and I use navigation very often)

@VoiGAS thanks!! I’ll look into it. My hope is to get him thinking about training sessions using RPE first, and HR as secondary feedback. So this might be the way I go.

@MarTej_cz thanks, I will try

@viduc Hi, I got my Race 2 4 days ago and I had two crashes as well. On getting the watch I updated it to 2.56.18 immediately. I had my first crash on Friday just before my 100km race therefore I was worried it could happen again med race, but it didn’t. The second crash happened today. In comparison with your crashes they are not so frequent, but there must be some kind of issue here to resolve. I have yet to see how the watch will be behave in the future and am a bit worried and I shouldn’t be for the watch of that price tag. Regards.

@Migsey The DM5 still exists, it shouldn’t be a big deal to bring a new version with Nautic / cloud support. Then we could see the same dives in both applications. Suunto app for eyecandy and overview, DM5 for details

I don’t know about the Vertical 2, but the charger on my Race s is quite tricky to get aligned right. You always have to turn the charger a bit to get it right and the watch starts charging. When the watch is on you at least get instant feedback, but when it’s of, it’s more of a problem. You could try to rotate the charging puck a bit and see if it starts charging.

I’ve had my V2 since mid October and so far not a single crash. I always run 3 S+ non-third party apps. No other issues either.

@sky-runner Yep, that’s exactly the same thing. I just upvoted your post.

@2b2bff it happens the same to me, but I haven’t understand the pattern yet. Sometimes I see only one activity type, sometimes more than one. The only thing I have discovered is that the summary discards always at least one activity, it is never complete.

[image: 1786344212040-29362.jpg] [image: 1786344212067-29363.jpg]

@Martin-Tuharský Hi Same issue here. 4 Days old Race 2 watch updated to the latest firmware on day one rebooted twice. Luckily only in time mode and not during my 100km race a day ago therefore there must be some kind of issue with this

On my Race S, black grids occur at least once on every walk or hike. I have not noticed a change in frequency over several watch updates.

Back to back days with reboots in the middle of an activity. Logs sent at 930ish CST. Custom run mode No suunto apps or guides Coros HRM I had just received notification of a phone call on my watch and had accepted the call with my Wings headphones FWIW. Looked down in the middle of the call and had the “Suunto” logo staring up at me from my watch. REALLY hope there’s something coming to address this. Back to back days on long runs 5 weeks out from Wasatch 100 miler. Not instilling a lot of confidence.