Map display takes forever
Hi all,
I have updated Locus on my Pixel 3a (Android 11) to Ver 4.0.0 and also subscribed to the Gold membership.
I mostly use the "Freizeitkarte Westdeutschland" (https://www.freizeitkarte-osm.de/android/de/mitteleuropa.html#DEU) as map and I had the problem that it takes every time almost 30 seconds to display it. This map is the only that is installed.
I have now found that it is faster if I change the memory to "Internal memory (private)", but this is
1. not the preferred default setting and
2. impractical, because you can't access the maps stored there with other apps ...
Seems to me a similar problem as we have already discussed here: https://help.locusmap.eu/topic/22113-locus-under-android-11
Maybe there's another idea or solution?!
Best regards
Martin
The same problem 
Hello Martin,
really interesting problem. Slow loading of this map happens only when the app starts and the map is loaded for this first time or also when scrolling with the map? What about when you choose a different map, like online LoMap? Is there a significant difference? And the last question, if you choose a different map theme for the Freizeitkarte map, for example, some internal predefined in the app, is there any difference?
Thanks for answers,
Jiří M. aka Menion
Hello Martin,
really interesting problem. Slow loading of this map happens only when the app starts and the map is loaded for this first time or also when scrolling with the map? What about when you choose a different map, like online LoMap? Is there a significant difference? And the last question, if you choose a different map theme for the Freizeitkarte map, for example, some internal predefined in the app, is there any difference?
Thanks for answers,
Jiří M. aka Menion
Hi Menion,
I did some tests following your questions:
- slow loading only appears when the app is started and the map is loaded - once it is loaded, scrolling works smoothly (within the same session),
- closing the app (completely) and starting again results in the same behaviour,
- when a different theme ("Allgemein") is chosen, it makes (almost) no difference in performance (although it takes some time to apply the FZK themes) ,
- online LoMaps start immediately and work without any delay,
- when memory is set to "internal memory (private)" the problems are gone!
Best Regards and thanks for taking care
Martin
Hi Menion,
I did some tests following your questions:
- slow loading only appears when the app is started and the map is loaded - once it is loaded, scrolling works smoothly (within the same session),
- closing the app (completely) and starting again results in the same behaviour,
- when a different theme ("Allgemein") is chosen, it makes (almost) no difference in performance (although it takes some time to apply the FZK themes) ,
- online LoMaps start immediately and work without any delay,
- when memory is set to "internal memory (private)" the problems are gone!
Best Regards and thanks for taking care
Martin
Hello Martin,
thanks for the tests.
Your device does not have SD card so we talk about the root of the internal memory and app private directory right? I work on a Pixel 2 device and I've just downloaded exactly the same map as you into the default directory (so directly in the internal memory). And unfortunately, I see no problem here, the map works smoothly immediately after the start. The only huge slowdown is in selecting the map themes, which takes quite a long time. This probably means that the theme definition is quite complex.
Because the change to private internal memory completely solves your issue and I do not have such an issue on my own device, I currently do not see an easy method how to find out why this happens. Thanks for understanding.
If you find out anything that may help here, please let me know. Maybe suggest to re-install mainly mentioned map themes, as they really may be a source of trouble.
Jiří M. aka Menion
Hello Martin,
thanks for the tests.
Your device does not have SD card so we talk about the root of the internal memory and app private directory right? I work on a Pixel 2 device and I've just downloaded exactly the same map as you into the default directory (so directly in the internal memory). And unfortunately, I see no problem here, the map works smoothly immediately after the start. The only huge slowdown is in selecting the map themes, which takes quite a long time. This probably means that the theme definition is quite complex.
Because the change to private internal memory completely solves your issue and I do not have such an issue on my own device, I currently do not see an easy method how to find out why this happens. Thanks for understanding.
If you find out anything that may help here, please let me know. Maybe suggest to re-install mainly mentioned map themes, as they really may be a source of trouble.
Jiří M. aka Menion
In the German forum there are also people who have this problem.
https://forum.locusmap.eu/index.php?topic=7295.0
In the German forum there are also people who have this problem.
https://forum.locusmap.eu/index.php?topic=7295.0
Hmm, thanks. I've read with Google translate the whole topic. Seems to me the with FZK maps, but the internal theme (not FZK) map works as expected. Martin here wrote that there is no difference, but Martin, did you tried to use any other than FZK theme?
I do not know guys. I was quite sure that there should be no difference between root of internal memory and private space in the internal memory. Seems I'm wrong, but it does not make much sense to me :/. If same issue happens to me as well, this should help a lot, but no success so far (tried two devices).
Menion
Hmm, thanks. I've read with Google translate the whole topic. Seems to me the with FZK maps, but the internal theme (not FZK) map works as expected. Martin here wrote that there is no difference, but Martin, did you tried to use any other than FZK theme?
I do not know guys. I was quite sure that there should be no difference between root of internal memory and private space in the internal memory. Seems I'm wrong, but it does not make much sense to me :/. If same issue happens to me as well, this should help a lot, but no success so far (tried two devices).
Menion
Ah, I was able to simulate the issue on one device. Well, not 30 seconds, but only 10 seconds delay on the old S7.
The issue seems to be connected to loading SVG images. Seems that MapsForgeV4 system loads all images at the moment, the theme is loaded into memory. As I see, all SVG images in FZK themes have defined really huge canvas (580x580px!!!) and I believe, this may cause this issue.
The best solution should report this to the theme creator and reduce the width & height of all SVG images, it may help here.
Ah, I was able to simulate the issue on one device. Well, not 30 seconds, but only 10 seconds delay on the old S7.
The issue seems to be connected to loading SVG images. Seems that MapsForgeV4 system loads all images at the moment, the theme is loaded into memory. As I see, all SVG images in FZK themes have defined really huge canvas (580x580px!!!) and I believe, this may cause this issue.
The best solution should report this to the theme creator and reduce the width & height of all SVG images, it may help here.
Hi there,
i did some more testing this morning:
- when "private" memory is selected, FZK takes 2-3 sec. until it is displayed - regardless of the chosen theme (FZK theme or Locus internal!),
- when "standard" memory is active, it takes 30-40 sec (!) also regardless of theme,
- I completely de- and re-installed both maps and themes before starting the tests.
As mentioned earlier: I think this is somehow related to the new memory allocation in Android 11 ...
Martin
Hi there,
i did some more testing this morning:
- when "private" memory is selected, FZK takes 2-3 sec. until it is displayed - regardless of the chosen theme (FZK theme or Locus internal!),
- when "standard" memory is active, it takes 30-40 sec (!) also regardless of theme,
- I completely de- and re-installed both maps and themes before starting the tests.
As mentioned earlier: I think this is somehow related to the new memory allocation in Android 11 ...
Martin
A few new findings: I tried to set only the mapsVector directory to the default "public" and leave the rest to "private". The loading of the Freizeitkarte now takes slightly longer, but it is now available again for other apps (for me e.g. c:geo).
A few new findings: I tried to set only the mapsVector directory to the default "public" and leave the rest to "private". The loading of the Freizeitkarte now takes slightly longer, but it is now available again for other apps (for me e.g. c:geo).
Replies have been locked on this page!