It’s slow in general, they’re not using vector maps like organic maps do. I love what OsmAnd does but it’s definitely slower to render and more sluggish to navigate than other maps on my FairPhone 5.
Yes and no. OsmAnd tends to have far more details to display — more data to display or filter out. I’m guessing that if you had a smaller rendering file (instruction for painting) along with a smaller obf (less data due to prefiltering), it’d be closer to comparable.
Edit: The link, which addresses slowness with GrapheneOS not experienced with stock ROM, seems to specifically address the (non-stock) FairPhone too.
Stock ROM or possibly GrapheneOS?
It’s slow in general, they’re not using vector maps like organic maps do. I love what OsmAnd does but it’s definitely slower to render and more sluggish to navigate than other maps on my FairPhone 5.
Yes and no. OsmAnd tends to have far more details to display — more data to display or filter out. I’m guessing that if you had a smaller rendering file (instruction for painting) along with a smaller obf (less data due to prefiltering), it’d be closer to comparable.
Edit: The link, which addresses slowness with GrapheneOS not experienced with stock ROM, seems to specifically address the (non-stock) FairPhone too.
Yes, graphene
You enabled exploit protection compatibility mode as mentioned in the link?
Yes, exploit protection is not responsible for osmands slowness. It could impact startup, but nothing more
It’s not related to graphene. I’ve seen osmamd being snaily on other flagships as well