in one of the screenshots, you can see a "stopped time" and "T(otal) Stopped" time.
These 2 times are based on cadence over the last 5 seconds (I think) and thus when it detects you are not moving (adequately), then the timer will start to count-up automatically, (it does not auto-pause).
The reason for this feature is actually for users to be aware of how long they are staying in once specific location (rest stop / Race Checkpoints)
AppBuilder 5: Simple data field which displays 1 custom value based on the formula of your choice. (Can be placed in any kind of layout alongside other fields -- e.g. 4-field layout).
AppBuilder 5+: Full screen data field which displays 6 custom values based on the formulas of your choice. (Only works in 1 field layout)
Run Power: Full screen data field which displays 6 values, 2 of which can be based on the formulas of your choice. (Only works in 1 field layout). Any of the 6 fields can also display values from standard metrics, and certain power-based metrics. (The power features are optional)
(Out of AppBuilder 5+ and Run Power, I would probably recommend Run Power, unless you have a need for more than 2 custom formula-based fields on the same screen.)
Based on Strava's cut-off for moving (about 2 miles per hour), you can use the following settings for total moving time:
Label: Moving Time
Formula: sum(speed_raw gt 0.89408)
Display Format: Time
(speed_raw is your speed in metres per second, and 0.89408 metres per second is 2 miles per hour)
For total stopped time (based on the same "algorithm" as above), you can use the formula: timer - sum(speed_raw gt 0.89408)
Def not as user-friendly as the other app, but the possibilities are endless (if you have a certain formula in mind)
