@sartoric - apologies, I misread and didn’t realize these are the repro steps: start training with 10s screen timeout pause training, allow the screen to timeout click the lower right button when screen is timeout, note new lap created on SSU I’m able to repro this on an SSU but not on the S5 with older FW 2.14.16. The SSU is reasonably logically behavior. If the training is ended by clicking the “End” button when the display is lit, the new lap will have 0 seconds as its lap duration. Presumably resuming the training will start into the new lap created during the pause. On the older FW S5, the lower right button press in screen timeout will bring up the anticipated training status screen ( Resume, Paused time, End ) and will not create a new lap. This also seems like the better choice.

@lorenzo12375 said in Suggestions to improve some running apps: Manual intervals Possibility to switch between pace/average pace (via upper left button for example) Oh, I second this suggestion. That would be great!

@scafroglia93 a dedicated step mode might be a bit too specific, but maybe a step (stairsteps) counter as an S+ app would do it if you could activate it in your preferred “gym” mode?

@trailcafe apparently when I said months, I meant weeks. The app developer is super fast

@Felttie And add support for multiple sensors of the same type. Not one HR strap and if I grabbed a different one, I have to pair it again.

@isazi @surfboomerang thanks very much

Agree, this would be really helpful.

@pilleus the 9 Peak (same size) has a great basic watch face — could someone move it to the Peak Pro?

@Mojtaba-Ebrahimi

@Durri definitely not necessary. While I am not really sure if you off-time sleeps will be handled as sleeping or napping, just leave it on and let it do it’s thing. Then we like to hear about your experience!

Yes, regardless of the language, it would be really cool (and useful) to use a color code for end/save - continue - pause - discard our activities.

@isazi ok thanks for your feedback. So I guess it’s more accurate then when there are « few » sections » with big elevations than on routes with lot of sections and few elevation. (By the way I realize that the exemple I’ve taken was not good => in mountains I experimented that it was working pretty well)

@GiPFELKiND As part of calibrating the barometric altimeter, the temperature of the sensor is required as part of the calibration as pressure is also temperature dependent

Orthostatic test would be great. I’ve bought the polar only for that test and for me it is the best tool for analyzing potential overtraining so far

@far-blue said in [UPDATE] Disable notification ONLY during trainings: Just to add to this (which I also noticed), When DND is on it also silences all alerts for structured workouts. This isn’t a very helpful or expected behaviour so can DND mode when in an activity please allow actual activity alerts to still, um, alert? Yes, that is a bug in my opinion. It needs to disable system notifications for the duration of the activity while allowing activity related alerts (Guides, + Apps, etc.)

Ok, I’ve been experimenting and this is what I’ve found so far. Firstly, it seems clear to me that the behaviour of the watch’s presentation of pace changes when a stryd pod is used so I’m pretty sure the pace data is used and is used in preference to in-watch fusedspeed data. When I use the stryd pod, pace appears to be updated pretty consistently every 2 seconds or so. I actually think Suunto could do some work to tune this to improve it because my iPhone app (iSmoothRun) can update every second but that’s an aside. When the stryd is paired, no level of mucking about with gps or holding my arm to see the watch for extended periods makes any difference so I’m going to say when a stryd is paired fusedspeed isn’t used and pace comes from the stryd, not gps. When not using the stryd pod I can def. create scenarios where I can tell the difference. With a recently sync’d watch, over 20% battery, performance level gps and a solid gps signal I actually think the watch updates pace faster than when using the stryd. However, not sync’ing before a run, having less than 20% battery and running deliberately where I know the GPS signal is weaker (under trees, along canals etc) the pace update rate drops significantly. Here it seems to update every 5 or so seconds and is also more likely to react to a slowing of pace than an acceleration. I’m guessing this is the frusedspeed stuff kicking in. If I go further to ‘break’ the fusedspeed capability by holding my wrist up to view my watch continuously (therefore preventing the accelerometer from doing it’s job) then in a poor signal area the pace can easily freeze for 20 seconds or more until GPS catches up. So my conclusion is that the watch adopts behaviour 1 from my original post. As a result I’m not going to be retiring my Stryd any time soon And as a PS maybe Suunto could improve the refresh rate for pace and power from the stryd to every second I’d be interested to hear if other people have different experiences

@fritzbt2013 I can confirm that it is the least used custom activity that gets deleted. I recently got back to using my Vertical and had 4 custom activities (only). I noted which one was at the top on the watch (the least used). I then performed the update, and it was gone, and I was down to 3 activities. I’ll continue to keep track of this, but it’s pretty easy to reproduce the problem and I would think Suunto could solved this fairly easily (if there is a good way to submit the issue where it might get some traction). For now, I’ve added ‘Stretching’ to both my watches and will (easily) make sure it will be the least used activity as a workaround to the problem.

@Egika Yep.

@stromdiddily The watch will use HR but the other values can affect the TP calculations from what I have seen. See if this helps.