@2b2bff said: @dreamer_ said: Personally, I don’t see anything wrong with Suunto deciding to release watches every year if it helps the company improve its financial numbers. After all, Garmin has been doing this for a long time, and now Amazfit is doing it too. Perhaps the 2 year wait does not have any sense if you maintain the older devices. This is also common in other devices like smartphones. The key should also be to maintain support for older devices for a period of time. The faster pace you release new devices, the more devices you have to support… That is the problem about releasing devices in shorter intervals. Or perhaps the revenue is a lot more than the cost of maintaining an additional device. That is something that only Suunto will know…

@aiv4r is [image: 0UA9ixY] not a sign? Has been there since I dunno when. There are, from my understanding, already SuuntoPlus apps running natively on the Run, don’t ask me which as I’m not sure.

@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.

@matus69 I don’t even touch my phone. It is in standby. Then I tap update in the widget, and the watch seems to fetch data via SA in the background.

I haven’t got this yet (am enrolled beta tester), is this an iOS update or is it out for Android as well?

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

@isazi said: @elbee I reported the problem internally to Suunto on the 14th of April, and the fix to this issue was assigned to Q2 release (the one only Race 2 and Vertical 2 got so far). I (and others) also reported it before Q1 release, but the timing was not good, the reports were for the production firmware and the developing firmware was too far ahead for the bug to be acknowledged at the time. This issue is still present after the latest update – nothing has changed in over half a year. Vertical 2

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.

I’ve been having the same problem. It happens while in activities (the activity still saves afterwards but always looses 9.1seconds off the end.) if I have a guide running it restarts about 3 out of 5 times at the end of guide/interval. I’ve tried disabling all suunto + guides, navigation etc it also happens when not inside an activity but while on the normal, day to day watch face also. I’m reverting back to the previous firmware now (April’s version) because I know it didn’t do that then, which is a shame as I was getting used to the map labels.

@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.

@2b2bff Right, I think in a Race the first 10 minutes are critical. A lot of people get too excited and start too fast. This is where I check the Heartrate very often. Not possible with Zonesense in the first 10 minutes and I am also not sure if it would react fast enough too warn me pushing too hard

@Squirrel correct, not a typo.

@muellersjens Did you check again your previous activity in the app? HR is computed in the backend and sometimes it doesn’t appear good initially (if appearing at all). After this, what is saying your watch logbook for zones duration for this activity? Correct or same discrepancy?

@Nelson-Diogo That’s why I didn’t keep my Suunto Run

@KSGravelJunkie Wahoo can’t choose between ANT+ and BT, whereas Karoo can, so it doesn’t have a problem with this … but I’m not sure if there isn’t also an identification error on Suunto’s part

@elbee Thanks!

@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.

@HonzaS one more question Regarding cadence sensor. Should I remove it or just set in right way? I can see that I can set wheel size and turn on or off something like sinc speed and cadence (but it cannot sync speed because it’s only on cadence mode) I removed sensor and at least distance is correct

Well, scratches or cracks are permanent, even if the watch is well built. Since it’s a dive watch (close proximity to metal equipment / coral objects), I would rather change protective screen/case than the whole watch in case of an accident Anyways - print is couple of grams of filament and looks better in real life than in close up photo (could be even better if printed on smooth plate). Someone will definately find this useful.