This object is in archive!
Locus under Android 11
Closed
Hi there,
last week I received the update to Android 11 on my Pixel 3a and since then I have had the problem that my beloved Locus App very often reacts very slowly.
For example, it takes a long time to open the datails to a cache and then switch to the listing or the waypoints etc. and also deleting temporary data takes an extremely long time.
And when closing Locus an error message appears every time after a few seconds (see appendix) and then disappears again a bit later.
Maybe the problem has already come to you and we can hope for a remedy soon? It's no fun at the moment ...
Many greetings and thank you!
Martin
P.S. other apps show a similar behaviour since the Android 11 update
Files:
Screenshot_2020...
The same problem 
Hi Martin,
we don't register any performance issues generally on Android 11. Perhaps you have too much content active on the map? Please check it out. More about maintaining Locus performance: https://docs.locusmap.eu/doku.php?id=manual:faq:locus_performance
Hi Martin,
we don't register any performance issues generally on Android 11. Perhaps you have too much content active on the map? Please check it out. More about maintaining Locus performance: https://docs.locusmap.eu/doku.php?id=manual:faq:locus_performance
Hi Michal,
I don't think so: I haven't changed anything at Locus at all, runs with the same content for years without problems. The difficulties are clearly due to the Android 11 update. But like I said: there are other apps that are a bit bitchy. I have the feeling that it is related to a somehow changed memory management in the new Android version.
I'll observe how it behaves; if necessary I'll have to uninstall Locus and reinstall it and see how it works then ...
And maybe with further feedback you'll get more information?
Many greetings
Martin
Hi Michal,
I don't think so: I haven't changed anything at Locus at all, runs with the same content for years without problems. The difficulties are clearly due to the Android 11 update. But like I said: there are other apps that are a bit bitchy. I have the feeling that it is related to a somehow changed memory management in the new Android version.
I'll observe how it behaves; if necessary I'll have to uninstall Locus and reinstall it and see how it works then ...
And maybe with further feedback you'll get more information?
Many greetings
Martin
Hi Martin,
of course, we'll be grateful for further updates. Please, stay in touch.
Hi Martin,
of course, we'll be grateful for further updates. Please, stay in touch.
Hi Michal,
maybe an addition based on new findings: similar problems as with Locus I had with the "Simple Gallery Pro" since the update to Android 11. For this app there was an update today with "Improved file loading performance" and the problems are completely gone!
I had already expressed the assumption that the problems are somehow related to a changed memory addressing under Android 11 ...
May help with further considerations?!
Best Regards
Martin
Hi Michal,
maybe an addition based on new findings: similar problems as with Locus I had with the "Simple Gallery Pro" since the update to Android 11. For this app there was an update today with "Improved file loading performance" and the problems are completely gone!
I had already expressed the assumption that the problems are somehow related to a changed memory addressing under Android 11 ...
May help with further considerations?!
Best Regards
Martin
Hi Martin,
as I had written, we don't register any performance issues generally on Android 11. To be true, you are the only one so far. So we're waiting for some more feedback from other users before we take action.
Hi Martin,
as I had written, we don't register any performance issues generally on Android 11. To be true, you are the only one so far. So we're waiting for some more feedback from other users before we take action.
Hi Martin,
we've registered another case of this type. Surprisigly, deleting Locus/data/geocaching solved the problem (don't worry, the app creates a new directory after restart). So you may try it.
Hi Martin,
we've registered another case of this type. Surprisigly, deleting Locus/data/geocaching solved the problem (don't worry, the app creates a new directory after restart). So you may try it.
Hi Michal,
and thanks for the update!
I completely uninstalled Locus before the weekend (settings saved before), deleted all data and folders etc. and reinstalled everything again. Since then, the performance is a bit better, but not yet back to the pre-Android 11 level, especially the crash message when closing the app is reliably reproducible (see appendix) ...
Greetings
Martin
Hi Michal,
and thanks for the update!
I completely uninstalled Locus before the weekend (settings saved before), deleted all data and folders etc. and reinstalled everything again. Since then, the performance is a bit better, but not yet back to the pre-Android 11 level, especially the crash message when closing the app is reliably reproducible (see appendix) ...
Greetings
Martin
Hi Martin,
if the app really crashes (i.e. switches off, not just stops responding), please create a bugreport and send it for analysis. Thanks! (more at https://docs.locusmap.eu/doku.php?id=manual:faq:how_to_create_debug_log)
Hi Martin,
if the app really crashes (i.e. switches off, not just stops responding), please create a bugreport and send it for analysis. Thanks! (more at https://docs.locusmap.eu/doku.php?id=manual:faq:how_to_create_debug_log)
Hi Michal,
on monday I got a new Android 11 version but the "App doesn't respond" message when closing Locus and the lagging when switching e.g. through cache details remain :(
The other day I also received an update of c:geo (which you may know) that returned an interesting information - I attach a screenshot of that.
Best
Martin
Hi Michal,
on monday I got a new Android 11 version but the "App doesn't respond" message when closing Locus and the lagging when switching e.g. through cache details remain :(
The other day I also received an update of c:geo (which you may know) that returned an interesting information - I attach a screenshot of that.
Best
Martin
Hi Martin,
yes, we know about the different handling of the apps data in Android 11 and Locus Map is ready for it. What about the deleting Locus/data/geocachig folder? Have you tried it? Did it help?
Michal
Hi Martin,
yes, we know about the different handling of the apps data in Android 11 and Locus Map is ready for it. What about the deleting Locus/data/geocachig folder? Have you tried it? Did it help?
Michal
Hi Michal,
yes, I did that and also a complete new installation of Locus - didn't improve anything.
btw. I'm running the same Ver. (3.48.2) on my former Nokia 8 (still on Android 9) and it is much faster without any of the mentioned problems ...
Martin
Hi Michal,
yes, I did that and also a complete new installation of Locus - didn't improve anything.
btw. I'm running the same Ver. (3.48.2) on my former Nokia 8 (still on Android 9) and it is much faster without any of the mentioned problems ...
Martin
Hello Martin,
I'll try to help here as the app developer. Just to make it correct (also to Michal): the app is not ready for the new Android 11 file-system change! Fortunately, Google provided the option to still use the old system on the new Android 11 (not on the future releases like A12+), so Locus Map works still the same as on the older systems.
I personally use older Pixel 2 with Android 11 and no problem so far. I also have reports from a few more people that Locus Map works correctly on the new Android version.
What device are you using? Is it official ROM from the device manufacturer?
Jiří M. aka Menion
Hello Martin,
I'll try to help here as the app developer. Just to make it correct (also to Michal): the app is not ready for the new Android 11 file-system change! Fortunately, Google provided the option to still use the old system on the new Android 11 (not on the future releases like A12+), so Locus Map works still the same as on the older systems.
I personally use older Pixel 2 with Android 11 and no problem so far. I also have reports from a few more people that Locus Map works correctly on the new Android version.
What device are you using? Is it official ROM from the device manufacturer?
Jiří M. aka Menion
Hey Menion,
and thanks for taking care!
Here are a few details:
- i use a Pixel 3a without any modifications - OS (Android 11, RP1A.201005.004) and Locus version (3.48.2) are up to date,
- i mostly work with the offline "Freizeitkarte Westdeutschland DEU+WEST", installed directly from the website (https://www.freizeitkarte-osm.de/android/de/mitteleuropa.html),
- by default I have a PQ with 1000 caches of my Home Zone stored,
- with this setup Locus ran without problems until the update to Android 11 and is still running fine on my Nokia 8 under Android 9.
The main issues I observe now:
- the app start and loading of the map takes longer than before,
- opening a cache and switching through the information is sometimes very tough (no matter if it is a cache from PQ or from the Geocaching4Locus-live map),
- temporary data removal takes up to 15 - 20 seconds (before: 2 sec.),
- Every (!) time i close the app, a message "App does not respond" appears after about 10 seconds and disappears after 20 seconds,
- i have the feeling that these are all things that have something to do with memory allocation,
- i already deleted the Locus/data/geocachig folder as suggested by Michal and also did a complete re-install of Locus; both didn't bring any improvement.
Maybe it helps with the diagnosis ...
Regardless of this, I would like to take the opportunity to thank you for the great app, which I have been using intensively for a long time and which my colleagues with their apples regularly envy me for :)
Best regards
Martin
Hey Menion,
and thanks for taking care!
Here are a few details:
- i use a Pixel 3a without any modifications - OS (Android 11, RP1A.201005.004) and Locus version (3.48.2) are up to date,
- i mostly work with the offline "Freizeitkarte Westdeutschland DEU+WEST", installed directly from the website (https://www.freizeitkarte-osm.de/android/de/mitteleuropa.html),
- by default I have a PQ with 1000 caches of my Home Zone stored,
- with this setup Locus ran without problems until the update to Android 11 and is still running fine on my Nokia 8 under Android 9.
The main issues I observe now:
- the app start and loading of the map takes longer than before,
- opening a cache and switching through the information is sometimes very tough (no matter if it is a cache from PQ or from the Geocaching4Locus-live map),
- temporary data removal takes up to 15 - 20 seconds (before: 2 sec.),
- Every (!) time i close the app, a message "App does not respond" appears after about 10 seconds and disappears after 20 seconds,
- i have the feeling that these are all things that have something to do with memory allocation,
- i already deleted the Locus/data/geocachig folder as suggested by Michal and also did a complete re-install of Locus; both didn't bring any improvement.
Maybe it helps with the diagnosis ...
Regardless of this, I would like to take the opportunity to thank you for the great app, which I have been using intensively for a long time and which my colleagues with their apples regularly envy me for :)
Best regards
Martin
Hello Martin,
thanks for the useful information. I still do not have any useful idea, but my colleague just yesterday orderer Pixel 3, so we will have a very similar device to test, so I'll let you know.
Meanwhile, may you try to use any online map instead of these Freizeitkarte maps? Just to be sure, it is not a problem caused by vector maps. Thank you!
Jiří M. aka Menion
Hello Martin,
thanks for the useful information. I still do not have any useful idea, but my colleague just yesterday orderer Pixel 3, so we will have a very similar device to test, so I'll let you know.
Meanwhile, may you try to use any online map instead of these Freizeitkarte maps? Just to be sure, it is not a problem caused by vector maps. Thank you!
Jiří M. aka Menion
Hello Menion,
I have tried a little bit around:
- with the Freizeitkarte there is always an "app not responding" message on exit,
- if I have OSM online already activated at app start and only display the location, there is no error message on exit,
- when I start a navigation and leave the app (stop and quit), it is not really closed but just put into the background,
- If I then open and close it again, I get the message every time - no matter if I used OSM or Freizeitkarte and no matter if I used BRouter or GraphHopper.
If there is anything else I can test - with pleasure!
:)
Martin
Hello Menion,
I have tried a little bit around:
- with the Freizeitkarte there is always an "app not responding" message on exit,
- if I have OSM online already activated at app start and only display the location, there is no error message on exit,
- when I start a navigation and leave the app (stop and quit), it is not really closed but just put into the background,
- If I then open and close it again, I get the message every time - no matter if I used OSM or Freizeitkarte and no matter if I used BRouter or GraphHopper.
If there is anything else I can test - with pleasure!
:)
Martin
Hello Martin,
thanks for the tests. Generally, vector maps (LoMaps, Freizeikarte, ...) need a more CPU than basic raster maps (like the online maps). So it looks like Locus Map on your device has some problems with performance.
Unfortunately, even with your device on my desk, I'm not sure I should fix it. My colleague uses Locus Map on Pixel3 without any problems so it does not look like some global problem of Locus Map on Android 11 or Pixel 3 devices.
I may offer only a refund of your purchase if you purchased Locus Map during last year and send me your order ID. Sorry and thanks for understanding.
Menion
Hello Martin,
thanks for the tests. Generally, vector maps (LoMaps, Freizeikarte, ...) need a more CPU than basic raster maps (like the online maps). So it looks like Locus Map on your device has some problems with performance.
Unfortunately, even with your device on my desk, I'm not sure I should fix it. My colleague uses Locus Map on Pixel3 without any problems so it does not look like some global problem of Locus Map on Android 11 or Pixel 3 devices.
I may offer only a refund of your purchase if you purchased Locus Map during last year and send me your order ID. Sorry and thanks for understanding.
Menion
Hello Menion,
and thanks for your answer - which of course does not make me happy, but anyway ...
I don't believe in a general lack of performance -to be honest- because Locus ran absolutely smooth and without problems under Android 10 on this very device. I still think it has something to do with the changed memory allocation on Android 11.
I don't need a refund - on the one hand because I bought Locus a long time ago and on the other hand because I will continue to use it and observe the further development ... maybe you or I will gain new insights at some point ;)
Regards
Martin
Hello Menion,
and thanks for your answer - which of course does not make me happy, but anyway ...
I don't believe in a general lack of performance -to be honest- because Locus ran absolutely smooth and without problems under Android 10 on this very device. I still think it has something to do with the changed memory allocation on Android 11.
I don't need a refund - on the one hand because I bought Locus a long time ago and on the other hand because I will continue to use it and observe the further development ... maybe you or I will gain new insights at some point ;)
Regards
Martin
I fear what happens here may only be a glimps of what disaster is looming when the Android 11 storage will be enforced some time next year, with no escape route.
I read reports that their new storage API is 100 times slower than direct file access.
Now imagine 100s of hgt files accessed for map shading or other IO instensive tasks ...
I hope I am wrong!
I fear what happens here may only be a glimps of what disaster is looming when the Android 11 storage will be enforced some time next year, with no escape route.
I read reports that their new storage API is 100 times slower than direct file access.
Now imagine 100s of hgt files accessed for map shading or other IO instensive tasks ...
I hope I am wrong!
Hello Michael,
100 times ... it's correct, but only for some operations (like "list of files in the directory"). I believe it won't impact LM performance.
The only serious problem we will have to solve by September 2021 (as I know so far), is to transfer all app data from the root of internal memory to the app private storage in internal memory/Android/data subdirectory. I already have this partially done ...
This is anyway different story :).
Hello Michael,
100 times ... it's correct, but only for some operations (like "list of files in the directory"). I believe it won't impact LM performance.
The only serious problem we will have to solve by September 2021 (as I know so far), is to transfer all app data from the root of internal memory to the app private storage in internal memory/Android/data subdirectory. I already have this partially done ...
This is anyway different story :).
Replies have been locked on this page!