@zhangschmidt after the last update the Bluetooth heart rate belt connectivity crashes while Trailrunning. Again and again and again. Please solve this issue!!! Have to stop and restart the workout.

Hi guys! I’m new here, made this forum just for this problem: Since the firmware update as you guys report 2.50.28 on my Race S I have big battery drain about 1% an hour even in airplane mode and the dumbest digital watch face. From some Chat GPT help I uninstalled offline maps, made a soft reset, factory reset, now I’m leaving it in airplane mode overnight to see. But it’s doesn’t look good, it already dropped from 74% at 18:45 to 71% 21:45.

I was showing this before, but the problem still exists: [image: 1770752589150-1000069798.jpg]

@sky-runner no worries we keep it also for others to see. Yeah I had the same with one of my watches.

@Manuel-Extreme I have the same issue since upgrading to 2.50.26. The HR sensor stopped working correctly while running. I have fairly long and dark hair on my wrists and they seem to be causing the issue. Once I have shaved those under the sensor off, the watch started to show correct HR values.

@Dieter1960 said in Subject: Feedback on Zone Sense accuracy: Short intervals and Zone 2 threshold shifts: Analyzed the data through a specialized AI model to identify physiological breakpoints I’d be curious to know which model you used. If you ask an LLM to interpret your R-R data it generally uses the same (or similar) model that DFA-alpha1 is based on, but you can then tweak the prompt to ask it to compute the data using an “adaptive” model that should be more similar to what Suunto uses. At least this is something I tried long time ago, and eventually the computation was too heavy for the model to produce a result. AI models have evolved enormously since then. Nevertheless, I no longer look at ZoneSense data during my runs, simply because it just seems to “adapt” to my intensity. If I run at my typical aerobic effort, the shift between green and yellow is very likely where I expect it to occur, but if I run something more demanding (trail, tempo, race, etc.) it puts me in the aerobic zone when I actually have ±10 bpm above my aerobic runs.

I uninstalled on both the watch and the phone. Restarted both. Reinstalled the app. It seems to be better. No crashes so far… But I still have the app is sometimes struggling locking me on the route. Waves of beeps… Have to deselect the route and reselect it.

@Niels-Søren-Bøgh Great idea, you take a picture of for example the divemap at the location or resort, and have that switchable on the screen.

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

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