this post was submitted on 19 Apr 2025
60 points (100.0% liked)
OpenStreetMap community
4692 readers
1 users here now
Everything #OpenStreetMap related is welcome: software releases, showing of your work, questions about how to tag something, as long as it has to do with OpenStreetMap or OpenStreetMap-related software.
OpenStreetMap is a map of the world, created by people like you and free to use under an open license.
Join OpenStreetMap and start mapping: https://www.openstreetmap.org/.
There are many communication channels about OSM, many organized around a certain country or region. Discover them on https://openstreetmap.community/
https://mapcomplete.org/ is an easy-to-use website to view, edit and add points (such as shops, restaurants and others)
https://learnosm.org/en/ has a lot of information for beginners too.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Stock ROM or possibly GrapheneOS?
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
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.
@przmk
They're both vector based. Purely from usage it feels like OsmAnd is rerendering everything from scratch every time with little caching. If you pan away and pan back it takes effectively the same amount of time to recreate the previously rendered view as a fresh view. This time seems to increase with addition obfs for "live" updates etc.
When Organic Maps updates slowly it tends to feel like vector tiles "falling back" to lower zoom until more detail is retrieved.
@goldfndr
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.