OSMand used to only crash 1 or 2 times per trip. It was usable enough. Now recently something changed with my config somehow and it shows extreme detail no matter how zoomed out I am. Every tiny street is being rendered. This is killing the app. It crashes so chronically it’s unusable.
Anyone know how to control this?
In “configure map” I have disabled everything except cycling routes. The “details” shows 0/9, which apparently only configures objects, not street details.
(edit) I think the “map magnifier” might be the issue. It was at 25% (the lowest), which I would intuitively think means less road detail. But it’s apparently counter-intuitive. I chose 100% and I seem to get less map detail – which is what I need because the more detail, the more crashes. So I might have solved this… need to experiment.
It’s comfusing, I know, but the trick is the bigger the percentage the bigger, and less dense, the items and roads are. So 25% are very small and dense items which looks like more details. “Map magnifier” is an unfortunate name but thus is because the devs are mostly speaking Russian and this might be the best description they could’ve thought of.
Ah, interesting point. I didn’t realise the devs were Russian. That might explain this issue as well:
https://github.com/osmandapp/OsmAnd/issues/15927
OSMand is so glitchy and crash prone it would be useful to know which features are more inclined to hog resources, since resource insufficiency seems to be the reason for crashes. Things like the animation boolean and Kalman filter. I’m not sure if I should avoid those features.
For one person it crashes on long routes. For me a long route is more likely to have crashes just because the app must run for longer. My workaround is to save every route as a track before starting, so every time it crashes I don’t have to wait to recalculate the route (but I have to keep my eyes on the screen).
They’re adding tons of features, but invest less effort on stabilizomg the app.