@osmand why are you so slow? this is a brand new samsung galaxy s24+
@osmand why are you so slow? this is a brand new samsung galaxy s24+
@osmand why are you so slow? this is a brand new samsung galaxy s24+
You're viewing a single thread.
Make sure that you're using the "Version 2 (OpenGL) map rendering engine in the OSMAnd settings.
Using offline maps can also help, but I've never found it to be smooth like Google Maps (from years ago that I was using it).
I'm using an older Samsung Note, and don't have issues with the speed. It has improved quite a bit from maybe 2 years ago.
Looks like V2. That one shows the grid for not-yet-rendered areas
I wonder if it's a cache/internet issue. Yes, zooming to extreme levels causes some delay. But scrolling through a map zoomed at a reasonable level should catch up very quickly on both offline and online map layers. At least, it does for me, and my phone is like 4+ years old.
@Showroom7561 @pietervdvn @openstreetmap
This is an offline render, internet speed shouldn't have any effect.
The lack of caching of previously rendered areas is annoying.
That is annoying.
Even though I use an offline layer, the online is actually faster to render. It's like the cache system is broken, even though it clearly works when the device is in airplane mode.
However, I will admit that OSMAnd is the least performant of the map apps that use OSM data (or any other map/navigation app, really).
@Showroom7561 @openstreetmap
Well yeah, if you get some beefy server somewhere else to do the rendering it will be quicker.
I don't know if Organic Maps and the like actually store vector tiles locally to get the speed up or what, but they're clearly doing something better.I tend to only run mapping/navigation software offline, and this type of poor performance has only been noticeable on OSMAnd.
It's nowhere near as bad as it once was, but it's still not great.
I just realized that the Version 1 renderer feels much snappier for me.
Just tried it, and it's unbearable on my device. It may also depend on what map layer(s) you're using, and the device capabilities.
V1 was the previous render engine, when pretty much everyone complained that it was too sluggish. LOL