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).
!smartphone_required@lemmy.sdf.org captures these kinds of cases. @FoxyFerengi@lemm.ee, if you know of any situations where your prof faced difficulty for not having a smartphone, consider posting about it there.