This data field shows the estimated time of arrival for a configurable common running race distance among theses values : 5k, 10k, 21.1k and 42.2k.</p><p>It uses the average pace from the activity start to estimate the final time.</p><p>Example : your average pace is 5'15/km, the displayed ETA (for marathon distance) will be 3:41:31.</p><p></p><p>New feature : The last 5 minutes average pace is taken into account to adjust the ETA. This feature is deactivatable to keep the standart algorithm based on the average pace only.
Please contact me if you find a bug before write a bad review :)</p><p></p><p>1.1.1 : Manage pause activity : the timer state is not available for old devices (before 2.1.0 sdk version).</p><p></p><p>1.1.0 : Improvement : ETA ajusted with the last five minutes average speed.</p><p></p><p>1.0.1 : Rounding bug fix.</p><p></p><p>1.0.0 : First version.
Gareth
4 de agosto de 2021 | Versión 1.1.1
Not very useful in it's current form. Ideally we need a configurable number of fields, eg, 5k, 5mile, 10k, 20k, 13.1mile, 26.2mile, 50k, 100k, 100mile, etc There should be 6 fields available for the user to populate with the appropriate mileage. These fields can then be chosen to be displayed on the watch (eg 4 common fields could be displayed on one data screen). It would be nice to see 5k, 10k, 13.1mile, 26.2mile on one page for a marathon runner for example. The ETA's should stop at the value acheived at the specific distance (ie they hold their value when the distance is met).