@Adamhert restart your phone

@jamie-bg said in Suunto 7: I really don’t think you can go wrong these days no matter which fitness platform you use Wow, impressive review, thanks for that! I wrote a long post about my own odyssey through the Smartwatch jungle but I found, that I got lost in all the features and I could not find the ideal watch. For me Suunto has some „sophisticated simplicity“ which makes me feel „home“. It does want I need and I can trust the data (besides Resources atm ). The only other brand I really trust like that and that has the same “magic” for me is Polar and I still have my trusted Vantage M which I use from time to time. My son owns and is a great fan of Apple Watches and I can use one whenever I like. The battery is just too weak for me using it as a sportswatch, but the sensors are really great and HR and other data from it is impressively correct and trustworthy.

Hey all, When using other sports outdoor (sport non précisé outdoor), the elevation recorded by the watch is very unstable. For example, from yesterday hike which was 3km with 250m d+, watch give me more than 800m of d+. This has been observed with other activities. When using Hiking sport mode, elevation is spot on. Why is the elevation not correct when using other sports outdoor ?

It would be useful to start an activity at the end of a countdown.

@Brad_Olwin It has a MEAN absolute difference (median error of means) of ±10 BPMs and a 95% confidence interval of around 4 BPMs. Meaning that for most of the 58 tested subjects the estimated value deviates by 10 BPMs and 95% of all tested subjects are in the range of 6-14 BPMs deviation. The data points also seem to be gaussian distributed. So for only less then 5% it has a lower deviation of around 6 BPMs and for some of these 5% it has even a deviation of more then 14 BPMs. Of course, accuracy is highly subjective…but statistically seen, from the available data that I have, I do not use ZS at all. For me personally, when I know that on average, even under perfect conditions, the ZS estimated threshold is off by 8-10 BPMs in either direction, it is not usable for me. Even the authors discuss that there set-up is highly artificial and it needs to be seen if it even works under normal run conditions and without exercise until exhaustion…also 10 BPMs above my threshold is for me all-out running for 1km while 10 BPM below, is the HR that I have on the first kilometers of a Marathon. For me that is just way too much deviation to rely on it for proper training control and also dangerous for people that believe they can trust the value and base their training on. That I am not the only one this applies to, is already reflected by the statistics and the numerous posts from people in this forum that struggle with the value that ZS gives them and are looking for help to understand and interpret it. Communicating the average accuracy under perfect conditions to the average non-expert consumer, would already help them a lot to interpret the value for themselves. For the future, I am looking forward to more data and studies and maybe an improved algorithm, as the concept is really nice! But right now, it’s not there yet, in my eyes.

@Egika said in Suunto 9 Peak: @Rust-Ab if you have tried upper button (for a really loong time), please also try upper+middle button didn’t help, I’m attaching a photo - https://drive.google.com/drive/folders/1ylNNSSWw0HcZevB_kc46LCeU-WOxXcss?usp=sharing

@Klaane said in Battery drain: The battery on my Suunto Vertical Solar has dropped from fully charged to 55% in only two days. Last night it dropped by 15% while I was sleeping with the watch on. I have mobile notifications and 24/7 HR turned on but it still shouldn’t drain that fast, right? Standby backlight is off and I’ve used GPS for less than 10 minutes during those two days. Do I have a defective battery or could this be some other issue? It sounds frustrating! While mobile notifications and 24/7 HR can drain the battery, a 15% drop overnight seems excessive. Try resetting your watch or updating the firmware. If the issue persists, contacting Suunto support might help.

I expect trail visibility regression on the maps to be addressed. This should have been fixed immediately without waiting 3 months for the next update. If that isn’t fixed I’ll be very disappointed. Ideally I’d also want map contrast improvements and improvements of the climb guidance feature which is nearly useless on rolling terrain with moderate hills where it seems fairly random and doesn’t reflect the actual terrain. Finally, I’d like the glitchy route auto-reversal to be addressed or perhaps eliminated and replaced with a menu command.

@Lluís-Gou - you should get longer than that - were you using fused GPS - and or were you using maps?

When i went to sleep, everything was fine. When i woke up, and wanted to put my Race S on my wrist (i don’t sleep with my watch), I needed to select the language, let the watch know my weight and length and needed to make a new connection with the Suunto app. Could still see my old Spartan in the app. I do not let Android automatically update my apps. Pixel 7, Android 16 Suunto app: 5.3.7 (5003007) Current software watch: 2.44.46

@regger said in So, what are you going to do after Movescount closes?: Is there any possibility to transfer the tags of the moves to another plattform? I will miss them…I used movescount for searching of activity data of past activities still quite often in the last months. It’s more of a general question and by “another platform” you don’t mean Suunto App? If that platform can import tags or you just want to append those to the description field and you can go though data wrangling step yourself and all you are missing are Movescount tags (and perhaps descriptions and all other meta-data) in some machine-readable format (like json) or you just want to create a spreadsheet with descriptions and tags and dates and everything for searching for your past activities, then sure, it’s all in the MoveList - https://www.movescount.com/Move/MoveList