Possible improvement to the computation of *lap speed/pace*

[NiaJ3oE2LM]

Is your feature request related to a problem? Please describe.

I've tried to keep an eye on issues related to the computation of the lap statistics but I'm still not convinced by the way the app computes the interval (lap) speed/pace. Here is my feedback from field testing; assume you're moving at 5 min/km (12 km/h) and that GPS signal is sufficiently strong (for example, on an open field).

• if you set Time interval= 1 minute and Lap length= 500m you will hear the exact same lap speed/pace twice since the app does not seem to recompute the statistics based on the last interval (500m) from the position when the announcement was triggered;
• if you set Time interval= 1 minute and Lap length= 100m you will still hear the exact same statistics twice but the value will update more frequently.

Describe the solution you'd like

Use the last Lap length meters from the position/time of the announcement trigger in order to compute a more meaningful lap speed/pace. The Lap length used for this computation should be independent from:

• the length that triggers a voice announcement
• the length associated to GPS recording precision

Additional context

May be related to:

• Interval Stats announced incorrectly #443
• Voice announcements: trigger on both time and distance frequency #921

App version v4.16.1 installed from f-droid on android 10 and used for tracking running sessions.

[dennisguse]

Any PR on this is welcome.