Navigation ignores setting "use elevation data" in calculation of ETA/duration

[Macchiato17]

System: Osmand: 3.7.3 (Android 10) Using Offline Maps (general map, roads only map, hillshade and contour) Routing profile: pedestrian

Issue: Navigation does not take into account, if "use elevation data" is activated in the options / the active profile. The expected travel time is the same, no matter if this option is turned off or on. I'm pretty sure, that this already worked in the past, when I was using 3.6.3. I switched to 3.7.2 (and then to 3.7.3) recently and experienced this problem when doing a route planning based on a stored track. Downgrading or a fresh install did not solve this issue.

Expected behavior: When turning on "use elevation data", the estimated time should be longer than the time calculated with this option being turned off, due to taking into account the reduced speed given for elevation terrain compared to a walk in the plain.

[Macchiato17]

Addition: I just entered a new track and found, that starting the navigation takes the elevation information into account right after creating the track.

Reproducable like that:

• Set a starting point and a target point (my track will be a round-trip)
• I build up my track by adding each new point as "add as last target"
• When the track is complete, I change to the navigation but don't press "start" yet. I go into the details and store the track.
• The option "use elevation data" is on, the estimated walking time seems plausible. When I turn off "use elevation data" the time is reduced to the plain distance walking time, which also looks plausible. In this status, you may turn off and on the "use elevation data" and the resulting time is always plausible.

But as soon as you leave the navigation the issue kicks in and starts confusing the user: simply start the navigation mode again, then choose the just created and stored track. The estimated walking time will now and ever be the "walking in the plain" time. No mater if you activate "use elevation data".

I'm sure, that this behavior is the reason, why I was thinking that it worked in 3.6.3. So this issue could also be given in 3.6.3. (didn't double-check that).

I would highly appreciate a fix of this issue...

[vshcherb]

As of now it is used for route calculation but not for ETA estimation where it takes only default pedestrian speed. So if route is the same, ETA is the same as well. It could be improved of course.