Slow/impossible routing since update 4.8.6

[Cwpute]

Description

Routing between two points that are a kilometer apart from each other in a big city can take up to 20 seconds. Routing between two point sin a rural area that are 2 kilometers away takes up to 15 seconds.
Some bigger routes (starting at points being 25km apart) cannot be processed as the process seems to get stuck at about 15% of the way to completion.
Using the bike profile lowers the distance starting with the process gets stuck, but this issue affects all profiles.
The issue started after updating to 4.8.6, prior to this the routing process could take time for long routes (500kms and more), but it wouldn't get stuck at the same place over and over again. At least OSM would tell me to try and place waypoints in between the startpoint and destination so as to help it calculate. I tried using the Nightly build but the issue was the same.
Here is a link to my exported preferences file in case it might be of any use. It has been limited to a handful of downloads so download only if you intend to help fix this issue: https://nuage.girofle.cloud/s/8zgqtNmpEQ6yS5c

May be related to issue #20221 in some way.

Steps to reproduce

1. Select a starting point and destination that are more than 25km away from each other
2. Wait for the routing process to end

Actual result

The routing process gets stuck at about 15%

Expected result

Routing should process at the same speed it was before the update.
At least warn the user the process is taking an unprecedent amount of time and something might be wrong.

Your Environment (required)

OsmAnd Version: 4.8.6
Android/iOS version: Android 11
Device model: Nokia TA-1157
Crash-Logs: non

[vmicho]

Have similar issues.
I think the problem is on some device the default routing algorithm is the superslow HHxC++ (my main phone whe I updated osmand since long time).
On my other device with pretty fresh install everything is working...

Activate development plugin, then go to Navigation settings / Route parameters / Development : Routing type
There select HHxJava or A*any if you have the HHxC++ selected. You will also need to update maps as some algo do not work with very old maps (like 1y old)
HHxJava is like 10 seconds VS 5 minutes calculation.

[yuriiurshuliak]

Additionally, please ensure you update to the latest version of OsmAnd. The current version is 4.9.7.

[Cwpute]

Activate development plugin, then go to Navigation settings / Route parameters / Development : Routing type

This was NOT easy to find ! haha. My interface not being in english didn't help.
OSMand could really use reorganizing its options and settings at some point.

But it worked ! Thanks a whole lot.
So in the end it was indeed the same problem as the issue i linked. I had tried to find the correct options but i couldn't manage it, and the issue went into such details and specifics that i wasn't sure it was the same problem.

I'll close this issue in favor of #20221 and continue the discussion there.

[Cwpute]

Or maybe i'll keep this one open since it's more specific about the issue at hand.
Maintainers, feel free to close the issue if i'm wrong.

[Cwpute]

I think the problem is on some device the default routing algorithm is the superslow HHxC++ (my main phone whe I updated osmand since long time).
On my other device with pretty fresh install everything is working...

@vmicho what i understand here is that, old devices on which OSMand has been installed since a an undefinite time, the routing algorythm either stood as or was changed to HHxC++, which lately turned out really slow at its job or was modified and became slow afterwards.
Is that correct ?

In that case, an update to change the routing algorythm on these old phones is warranted.

[vshcherb]

Yes it was changed to HHxC++. However it shouldn't be slow, it should be same speed as fresh installation.