@Manuel-Extreme said in I’m waiting for…: Let’s slow down a bit. I think I understand the misunderstanding. I’m not criticizing the excellent work of the people who are directly involved in building a great outdoor product, within an iconic company that competes against giants with revenues 100 times higher. On the contrary, full respect and appreciation. As a user, I’m simply looking forward to a new firmware update so I can fully enjoy my device with new features and bug fixes, especially considering the last update was almost three months ago. I think others in the community are also eagerly waiting for the next updates I think I got your message right from the beginning. But the update issue ran a bit out of control in the last months, with that I mean with not adequate posts and statements. You should be part of the mature users here. For my part, I appreciate some of your latests posts (just a thank you at this place). So take it easy if your post is misunderstood.

@Horizontal_2 That initial steep decline is probably related to charging without charging. The current cycle does not show a similar steep discharge at the beginning. Basically, I am currently satisfied with the consumption/battery life of the watch. I have had the watch for 1 year, but it was purchased second-hand. The original owner claimed that he had only used the watch for a few months.

@cumbrian-runner OHR is highly dependent on the individual. For me Race2 OHR works well with steady runs and poorly on intervals. I almost always use a belt because I want better HR data. I often wear Race2 on one wrist and Vertical on the other. I get nearly identical distances and altitude gains/losses with both. I can share many instances of data if you wish.

I had this problem too. Also my son, with the same watch, who pointed me out. It was introduced with the latest FW. In my case, a soft reset seems to have solved it (a couple of weeks ago, no more ghost vibrations or sounds). J

@Dimitrios-Kanellopoulos This has been as issue for a while now (first documented with software 2.40.38). And it always comes up when someone oversleeps because the alarm goes off later than expected. I’ve actually seen the alarm touchscreen react to simply touching the bed sheets, so it doesn’t even necessarily have to be skin contact that dismisses or snoozes an alarm.

My run today was spot on. Used the Run with the Coros HRM and it was exactly the same as the Polar chest strap. Before I had followed the suggestions and uninstalled and reinstalled the app. So it does seem that at least for this run it has eliminated the spiking. However it has been mentioned in previous posts that uninstalling and reinstalling the app solved the problem each time in occured suggesting it is a temporary fix and not a permanent solution. It also doesn’t alter the data that is already present and incorrect from previous runs so I do believe it’s an issue Suunto need to look into.

@mdavis121212 said in Using Suunto Progress: @Brad_Olwin Well I wanted to do Mt Rainer but that’s not going to happen at my age. lol. I want to go faster at Century rides. Why Not!!! I have skied Rainier but many, many years ago. I am nearly as old as you, 69. I have a 100 mile race with 23,000 feet vertical gain in June. I am not letting my age dictate what I can do. I would develop a good training plan for riding or get a coach if you need to. There is no reason you cannot build your fitness. So some good goals.

@Manuel-Extreme only on the device for now heard it’ll come to app in a future update