"Unusable" bicycle routing on old devices in dense area

[natolh]

iPhone 5S
iOS 12.3.1
OsmAnd 2.82
Region : Lyon, France

Bicycle routing in Lyon area is nearly unusable. Computing route through or inside Lyon greater than 30-40 km is really slow and, most of the time, the app is crashing before the end of calculations. On other areas it is possible to compute longer distances, but routing is still really slow. The only workaround, apart from buying a device with more memory, seems to alter the heuristicCoefficient to compute routes faster (but less optimal). But this workaround is not possible on iOS devices... This problem also concern pedestrian routing, although 30 km is less likely to be travelled by foot.

[vshcherb]

We plan to introduce customization for routing.xml if it is present in Documents. We will check how it is working on 5C.

[max-klaus]

It should be possible in the current release: use routing.xml if it is present in Documents.

[natolh]

I've used it during the summer because it was introduced around early august I recall. Significant improvement, at least for me. But the experience is horrible as it's impossible to edit a routing.xml on the phone plus it is cumbersome to reverse. Hope you will provide something settings in the app preferences soon ! 😊

[nabilys]

In iPhone 7, using osmand 3.23 bicycle routing is also extremely slow. I can’t route lyon-grenoble for example. But it seems that this issue also occurs as pedestrian or car driver