@mikekoski490 Suunto support is leaving some strange impressions… I tend to think that AI is in use quite a lot. I made a ticket out of your Vancouver DST issue. It will find it’s way to the development department.

For those of you with iOS devices, have you received the update yet? I still haven’t seen it…

Let me add my use case here as well: During a recorded activity (e.g., 30-hour Backyard Ultra), if an external BLE optical HR sensor (In this case I use Polar Verity Sense) is powered off to recharge on USB and then powered back on, my Suunto Race changes the HR field from last-known value to ‘–’ and refuses to re-initiate the connection again, even from the Pause screen. It also fails to fall back to internal Wrist OHR. It would be super nice to access the settings from the activity to connect again the sensor or connect a new one (if you have several of them and don’t want to charge). Even better auto-connect the sensor when its back on.

@Žan-Škorja said: Are there any settings, diagnostic steps, or fixes I should try? Maybe try the same running form as if running freely (off the treadmill). i.e. What is the hand wearing the watch doing? Holding the treadmill somehow?

@Nikolai-Simonov Hi Nikolai, I’m developing GEO LINK, a SuuntoPlus radar app for the Race S. Our radar already works on the physical watch, but we want to receive friends’ live GPS coordinates from an iPhone. I saw that Live.τ supports bidirectional communication between iOS and SuuntoPlus, including messages sent to the watch. Could you share some technical guidance on how your SuuntoPlus app exposes or accesses BLE GATT services during an activity? Specifically, is this possible with a normal .fea Sports App, without requiring a .dev device connection app and the watch’s pre-activity sensor search? We’re not asking for your proprietary source code, just guidance on the supported API or connection architecture. Thank you!

@blabla said: @André-Faria - Great, i was also looking to vibe code something for it. @maryn - Yes, i cant believe that is working this good after almost 10y. check my app sommet maybe I can integrate something that may be missing to you.

@Egika said: @Nandodiver you can ask whatever you want. Still please be awayre, that this is a user forum, not official Suunto support. While many users here do have quite some knowledge and can answer many questions, the user base of Nautic dive computers here is pretty small. The answers you received so far are the common knwoledge (and are factual): I summarize again: activities recorded with two sport watches at the same time: only one will sync. No idea if this applies to Nautics as well. at some point old activities in the log can be overwritten (less likely nowadays since there is big memory in the watches that is used for some years to store activity logs) Again no idea, if and to what extent this applies to Nautic Activities loose their details and will not sync anymore after an update of the watch firmware. I hope that there is someone who has more detailed knowledge about the specific questions you asked. But I think they are too special for the users here. Why not give the option to end user to select their Depth Sample rate intervals to 1second ??? This is only a matter of Firmware upgrade on Suunto Side… If they can put 1s depth sample intervals on freedive mode, im sure will work in scuba option… Difference from 10s to 1s depth sample intervals Draws more battery (its a diving watch, Nautic uses 40% battery in 20 dives ) larger data file ( all of them has 32gb internal memory ) Sync will take longer over bluetooth (at least would be accurate sync) store less dives data ( 10s depth sample gets+400 dives, 1s get 40 dives) In the end of the day its an end user option, but at least would solve this mismatch data of air consumption between Dive computers and unable to sync dives…

@sky-runner I have removed generated Waypoints as they seem to be useless. and harmful. (I added them to generate the same format as https://turnbyturn.apert.be/) I also added fork and bearing sensitivity into options. For now, best results for me are when set both to Low. Please let me know if https://dushino.github.io/addturngpx/ works better for you now.

@mickywickyftw yea I agree with all you’ve said, the current firmware is stable with everything I’ve done. No crashes or issues on anything and super responsive so apart from the higher battery drain in standby I’m not to fazed but it was more a curiosity if someone else has downgraded previously? I might try if I pluck the courage one day in the new year

@Egika said: I spit a little on both contact pads This is the only sensible method. If we had to resort to wardrobe changes or gels regularly there’s a design floor. (Based on two decades of licking so, so many chest straps!)

@elbee I wish I had a contact on a developer that would implement my wishes without thinking

@Karlo_Spearfisher Not sure as I don’t have an Ocean. But I see something like this in the release notes: Feature: Add switch window customization to freedive (Ocean, Nautic S) Not sure if it is helpful for you.

@snow It should be called the Suunto Walled Garden as it doesn’t support any 3rd party integration.

This is the response I got from Suunto Customer Support: “This behavior is a known software quirk in Suunto’s Imperial unit logic rather than a defect with your individual watch. There is currently no setting on the watch or in the Suunto App to force decimal miles (such as 0.83 mi) below the 1-mile mark.” “Why This Happens & Which Watches Are Affected The “Sub-Mile” Conversion Logic: Suunto’s software designers modeled the Imperial unit display directly after the Metric system—just as Metric switches from meters (850 m) to kilometers at 1.00 km, Suunto’s Imperial logic defaults to displaying feet (0 to 5,279 ft) for any total distance, lap, or interval under 1 mile, only switching to decimal miles once you pass 5,280 ft (1.00 mi). Affected Models: This behavior is specific to watches running Suunto’s newer UI architecture—most notably the Suunto Run (which runs a distinct, streamlined RTOS/Lite operating system compared to older models) as well as recent firmware builds on the Suunto Race, Race S, and Vertical. Legacy models (such as the Suunto 9 Peak Pro and earlier) displayed decimal miles from 0.00 mi upward, which is why long-time American users have frequently flagged this regression on the Suunto Community Forums.” So that’s that! No way to change it, you just have to read 2,436 feet and try to estimate what that means.

Problem fixed in 3.16; the app is working again. Many thanks to the suunto team.

@tvial Can this hook into an interval session? The paces and tolerances are already set there so this would be a handy readout until the next interval.

@Łukasz-Szmigiel muito obrigado pelo retorno.

@snow If I look at the version history in the app store: a 3.x.0 version has a description of the one biggest change. a 3.x.y version has Fixed known issues and improved system stability.