@Stefano-M64 I don’t mean to change that watch face, just showing they have scope to make watch faces with larger complication fonts.

@Ger43 I have a Race 1 (and Race 2)… the Race 1 has been great, with none of the distance loss / trimming of the Race 2. Lots of comparisons of features online, but from my practical experience, what I’m most concerned about is accurate ascent/descent, and accurate distance. The Race 1 is great in these regards.

Commentary zone has been improved : we now see all text when we want to modify it ; great !

@sky-runner it remembers an old experience with my Spartan Ultra. Searching a lot with the community why it would have strange baro / altitude behaviours, while after repairing it was so perfect. It happens unfortunately that HW is just the cause. (fridge test was the eye opener in my case). It is also why it is important that when issues are raised by some (not you specifically ), Community users should also answer “no issue in the same circumstances”, to orientate the analysis. Good luck with repair / warranty.

@JebClydeNC said in Suunto Routeplanner: Overall, excellent work—I do GIS for my “day job,” and the map styling has to be some of the best I’ve ever seen, on ALL baselayers! Only bugs I’ve found are units settings and login not being stored when returning later (might be a cookie issue on my end though), and when changing the units to imperial, the route library (when logged in) still shows overall route distances in km. For a future tweak, It would be awesome to have elevation and sunrise/sunset time pop up as a label when clicking (or tapping) a position like in the Suunto App. And perhaps, for manual point-to-point routes, labels on the lines with bearing and distance? Just thoughts from my overly map-heavy brain though. Seriously, excellent work on this project! Thanks. The login is stored but clearing cache will remove it. Some browsers may by default clear cache between sessions. Regarding the imperial problem, I am not able to reproduce it. Make sure you reload the page in case you have had it open for long and try to find a way to reproduce it. Nice feature ideas, need to think about them. Difficult to support these on both touch and desktop use though.

said in Nap detection off: @Brad_Olwin I have set dnd only for sleeptime 21:30-4:45. Gonna try factory reset next I would hold off on Factory reset unless absolutely necessary. I am similar and have sleep DND set for 21:00 to 6:00 but fall asleep at 21:30 and wake up at 5:30. When on the couch for TV I am not motionless, I usually have water and will get up once or twice an hour.

@Mff73 I just tested it with a new battery, no improvement on the Race S side. I tried connecting the heart rate monitor to the “Elite HRV” Android app, same result : the frequency is detected for a few seconds and then the app loses the signal with the heart rate monitor.

@stbuk Atleast on android you can set time in bed in the phone apps sleep widget. Daily sleep goal->Time in bed

@Jose-Luis-Merino-Parra wasn’t sure how I’d feel about the white ones from the website, but this looks great!

@Audaxjoe I agree with you. The best would be choose one option in the setting menù of activity. Like this for the handlebar bike/mtb use insn’t usefull. One compromise would be to choose (with option) to stop the display brightness to the first step after 8 sec without AOD. Would be a solution for bike activity where you use the watch on handelbar.

@OutdoorMan А если серьездно ?

@emkei is this app/watch discrepancy fixed after the past months?

Search the forum, it was written recently that Ocean is not dead. But saying when something will be out, the answer is the usual one…

@Nikolai-Simonov said in Live location S+ app: @Antoine I had an idea to measure this, but haven’t gotten around to it yet. Honestly, measuring power consumption properly is not as simple as it looks. Battery percentage is a very subjective metric, especially just on-eye observation. To do it right, we would need to use a multimeter and run controlled A/B tests (baseline vs. tracking in background/UI) across different devices multiple times. That’s the only way to get real consumption milliamp numbers instead of just rough estimates. But 3% per hour looks great for continuous live tracking. @nikolai-simonov : thanks for aswer. Of course. It wasn’t a criticism. I just wanted to get a rough idea of the battery drain on the Suunto Vertical. My measurement isn’t super precise, but I’m usually at around 1.6% per hour during an activity (100% ≈ 65h). With the SuuntoPlus Live Tracking app enabled, it’s around 3%, but i just want to confim that (or not). My goal is simply to estimate the overall battery life of my suunto vertical 1 for a long race while using live tracking.

After the 2.50.28 update, I also have some battery drain issues. It’s not as bad as what you guys have, but the battery goes down twice as quickly as before.

@SamuelP @voigas My watch is fine too, but hers isn’t. We trained together and I saw her watch, so it’s not something fake or something

ah okay, thanks for the replies. That is unfortunate. It happened twice already that I didn’t manually switch to the other device (i switch between the two every day so they can properly dry before I use them again) and I only got pulse based heart rate without zonesense for the activity.

@Squirrel It says 3.1.9