Avoid loop in the announcement of Route Recalculation about osmand

[yuriiurshuliak]

As I understood, in specific situations, the announcement of route recalculation loops continuously. Please clarify whether this error can be related to the fact that you are using Brouter? Try to change the routing algorithm and bind the track to the road: Menu > Settings > Driving > Navigation settings > Route Parameters > Development > Routing algorithm.

Also, can the fact that you have your own compiled version of the application affect it? Have you tried that, and does this bug reproduce on the release version?

Please also explain why the distance should be exactly to the next highway? How does it affect the issue?

And also specify why you chose the minimum distance of 20m? Perhaps if you choose 50m, this error will not be reproduced.

[EssBee59]

Hello,

I agree, the route reclaculation is much faster using the Brouter. As example in my test on a route of 6 km:
-Osmand (standard bike profile) needs nearly 3 seconds
-Brouter (Trekking) needs only 30 milliseconds

And this impact the behaviour!
Using Osmand routing, the loop also exists, but somtimes a short delay occurs between 2 messages.
AND of course no messages are queued!

The problem occurs with the standard/release Osmand version that I am using on the bike.
(I compiled an own version to test my changes)
If I right remember, many issues exist on the same subject

==> Please also explain why the distance should be exactly to the next highway? How does it affect the issue?"
no, this is only to reproduce the problem: If the distance to the next highway is > the min distance to recalc, we have the situation where the loop occurs.

20 m or 50 m: same problem...of course, if min distance to recalc is 50, to reproduce the loop the next highway should be > 50m away!

Note:
Also if the loop in his worst form only occurs when using the Brouter, I think there is no risk to wait 12 seconds between 2 recalc announcements?
I so, please consider my suggested change!

Regards