@dreamer_ said: @GratefulDeadpan said: I have a hypothetical question since there seems to be a lot of se in here. IF (big IF) Suunto moves away from the old OS running in V1/V2/R1/R1S/R2 and instead Run future watches on the Run OS. What does that mean for the current line of watches? Can they be flushed with the new OS or are they relics (albeit working still, but still abandoned in a sense). Wondering if I should return my V2 and just wait this out as my Run is working just as well as the day I bought it. Why not? Considering the upgraded resources and what we are seeing in Q1/Q2 (and if the new OS is coming), I think Suunto will flash the R2/V2 with the new OS but not the previous watches (this is speculation, of course) Oh lol noticed my embarrassing typo now, flash not flush. Yeah it was a reflection/question on my part—wether or not it was possible for the V2/R2 to be flashed with the newer OS. I don’t know much about how these things work but that was my hope when raising the question.

@Kowalski I don’t know. I’m not a Reddit admin, so I don’t know the tools they have at their disposal to detect stuff like this. It may have been that there was malware hidden in the file hosted in the Google Drive file, and the Core 2 leak was the bait to get you to open it? Just speculating.

@Nandodiver I have the tank POD, i believe the transmitter only works with the older computers like Vyper and the D Range of dive watches. I bought the POD in the beginning of this year and i’m not aware that there is a new version available.

I am in Scotland within a mile of the sea. I’m noticing a pattern with the tide widget. The last 2 weekends it has updated without me doing anything different and then will not update again for the rest of the week until the next weekend. I think it will update again this weekend if this pattern continues.

@aiv4r yes, that’s the way to go! I always ask my athletes and myself, how quick and how many repetitions were run in the last successful intervall session and how the feeling was the days after. That will be the initial target for the beginning, where RPE does not work yet because everything feels easy. Mostly this prediction over pace from past workouts or races is already very close to what one is capable of at the moment and minor adjustments then come over RPE. The feeling for RPE, one learns over time. But as in ever other sport, experience is key.

ah here https://www.suunto.com/en-gr/sports/News-Articles-container-page/suunto-core-2-vs-core-1-whats-new-and-why-it-matters/

@safari nice! Thank you, hopefully that makes it way to Android soon. Looks sleek!

@elbee you are funny. Often the car manufacturer will not even give an indication of the needed update We have a couple where we are negotiating for a buy back as they can’t solve a software issue. Life isn’t that hard with Suunto. I do have a wahoo and also have the issue. But I didn’t buy the V2 expecting to be able to broadcast to the bike computer so when I can it will be a bonus.

@VoiGAS for the EON, thats correct as they hold both tables. You can switch over or set Buhlmann as default where locks do not occur. But this does not downplay the fact that the ceiling was not followed and decompression was not finalized. This will have impact on further calculations as Buhllman uses its nitrogen buildup for further calculations. So better not to have these sitiations and allways follow the indicators on the computer to the letter. Suunto does make the difference between voluntary or mandatory decompression stops. The RGBM lock only applies to the latter. The screen showed in the link indicates a mandatory situation which is explained by Suunto… you get a warning to go to the ceiling of 6,5 meter. You need to do that within 3 minutes and sit out the deco as long as indicated by the EON, in this case 75 minutes which is far from beeing recreational… If you fail - after warnings like the red ceiling indication and audible signal - to comply within 3 minutes, the computer locks for 48 hours. So you might say it indeed locks during the end of the dive.

@2b2bff Yes, I’m aware. I would expect the watch to refuse executing a 3rd app, regardless if it’s an app or Guides workout, rather than hard crash and reboot.

Thought I’d add an update as I’ve just received a new sensor & belt from Suunto support who tested the old one & agreed that it was faulty. Also worth mentioning, whilst it was away at support I had to use the watch based optical sensor as I don’t have a back up & it performed surprisingly well

@maszop can you give me some details about your disconnects with Vertical 2 and the new firmware? I will forward them to Suunto.

Tiny fonts again - poor.

@Egika yep, I stiil have it in one of my drawers loved it so much!

@Squirrel don’t know. This is iOS beta 3.13

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.

@bbx100 Thanks for sharing your insight, much appreciated. My race2 is only 10 months old, so I have another 14 to go before it is out of warranty. So far, everything is still working again as expected after doing about 10 ‘moves’ and daily use. Let’s see how it goes with the next firmware update and onwards. If this happens again, I’ll definitly report to Suunto support.

I don’t see this too much on trails but 100% on roads. I think they over corrected a bit with this last update. I constantly get “off route” notifications simply being on the other side of the street running in the correct direction.

@Egika @maszop I can only share my experiences. I sometimes get the notification when my speed is clearly under 5.4km/h and quite often I don’t get a notification when I walk faster than 5.4km/h. I live in the Netherlands, not a really challenging gnss surrounding. Current pase with gps isn’t the most accurate, but I sometimes continue to hike for over 500 meter and then gps should have a fairly accurate pace.