@brechtvb You’re right, unfortunately I didn’t pay much attention to the title… I apologize.

@LGoSo nice, then I got you now! Yeah, you are absolutely right and good observation! Yes, if they would correct for that systemic error, they would get less average absolute deviation while also having more consistency. Therefore, they would need to say that measuring the HRmax with their all-out test and then estimating the T2 by x% of measured HRmax, outperforms ZS/DDFA! That’s why they probably did not try to optimize it and just discussed that it is ok to take the 85% of HRmax, as that is what is always used. Maybe with their test somewhere around 88% or 90% would be really accurate. That’s really disappointing…

@cheetah694 thank you for the answer

@Hari-Seldon yes

“What I read at its launch is that this was excluded since it is a new system and design, but that it would be integrated in the future—let’s see if that’s true.”

@akimserkam I agree! I don’t mind the standard watch face but some new ones might be nice. Real time ZS would also be great to have.

@Brad_Olwin The only way you can pair double tap the case and search for headphones on the Run.

@timefall said in Bug with H10?: Related to the OHR notes above, I’ve seen some weird behaviour on this first run where I had a belt (Wahoo TRACKR HR) paired and connected. During the run I think the watch was displaying OHR readings for heart rate, (with the usual spike at the beginning that I often see with OHR sensors, it peaked at like 191 during the warm up when it should have been something more like 120-130), but the synced fit file appears to be the data from the belt, with no huge spike at the beginning I’ve been struggling with a similar issue for some time now. When I asked support if it was possible for me to see different values ​​on the watch than those actually recorded, they answered with a clear yes. This is possible in certain scenarios because the internal sensor always works, even when a strap is connected. btw: The heart rate recording is asynchronous, right? In the end, it’s a minute too early

Right, so “unknown error occured” appears to happen if the media player menu/app is open on the watch. Go back to home screen and playlists can be created/edited. That appears to solve that part. A related issue I’ve noticed it is possible to reorder tracks in a playlist using the iOS app, but that order gets lost at some point and everything ends up jumbled again. Not sure what the ordering is based on or if it’s just random. I like to listen to some albums in their intended order, but that seems impossible with this watch right now.

@Hari-Seldon I no longer have the Suunto Run to test it, but the Garmin HRM Pro+ does these things: ****RUNNING DYNAMICS HRM-Pro Plus captures running dynamics — such as vertical oscillation, ground contact time, stride length, vertical ratio and more — to help improve your form and enable running power on your compatible Garmin watch**** I am assuming that you can now see these things when you use the HRM with your Run.

@Daniel-Anderson said in Resuming downloaded podcasts.: Is there a way to save your place in long podcasts in the media player? afaik it’s not possible

@Jonathan-Berthe I’m having the same issue! Hope they fix this soon.

@Hari-Seldon tqvm

@Steven-Hambleton très bonnes idées !!

this is the AOD display. it is reduced to save battery. If you enable the full display by raising your wrist or pressing a button, additional information will be shown on the right part of the screen. I guess the design decision was made, so that the time numbers don’t jump around too much between the two displays.