This object is in archive!
Map Overlay Disappears after Official Updates
Solved
Everytime Locus gets updated, the map overlay (MBTILES in the "Maps" directory and specified as a personal map) disappears and has to be selected again. This is not much of a problem for me, but I help support over 30+ users with quite a varying skillset. After an update, I usually get a flood of calls - "My map is gone, how do I get it back? Or some users will go make the overlay map their base map. The process to add an overlay is 7 clicks and I think that is part of the issue with some of the users.
Is there a way to retain the existing map configuration (with overlay) when Locus gets updated?
The same problem 
Good day Brandon,
how exactly you use your maps? You (and your users) use one map (online, vector?) as a base map and MBT map as overlay? And there is no problem when you close Locus by double-back button and after a while starts again? Problem happen really just after an update?
Good day Brandon,
how exactly you use your maps? You (and your users) use one map (online, vector?) as a base map and MBT map as overlay? And there is no problem when you close Locus by double-back button and after a while starts again? Problem happen really just after an update?
I use an online aerial map or a local SQLite aerial cache (under personal) for my basemap and then select an MBTILES map for my overlay. Locus runs great and loads & exits fine every time. The overlay always disappears when the app is updated via Google Play Services. This occurs on all of our devices and does not matter if I am using Locus default directories or external SD card for my maps.
I use an online aerial map or a local SQLite aerial cache (under personal) for my basemap and then select an MBTILES map for my overlay. Locus runs great and loads & exits fine every time. The overlay always disappears when the app is updated via Google Play Services. This occurs on all of our devices and does not matter if I am using Locus default directories or external SD card for my maps.
Hmm this is really interesting.
For Locus update over Google Play or! close Locus by back button - it is exactly the same. There is no difference in this process. Locus is just completely terminated and then re-opened.
Is this overlay only settings that is lost after update? Because if there is something lost, it should be all settings (mainly content of menu > settings) or nothing. Base map is selected same as was before previous close? What about access to map? I'm asking because right after restart of device, SD card may not yet be ready, so it worth to wait a minute till you start Locus.
Hmm this is really interesting.
For Locus update over Google Play or! close Locus by back button - it is exactly the same. There is no difference in this process. Locus is just completely terminated and then re-opened.
Is this overlay only settings that is lost after update? Because if there is something lost, it should be all settings (mainly content of menu > settings) or nothing. Base map is selected same as was before previous close? What about access to map? I'm asking because right after restart of device, SD card may not yet be ready, so it worth to wait a minute till you start Locus.
The overlay is the only setting that is changed. The same base map still loads after the update. My MBTILES overlay maps are betweem 1GB & 2GB each, not sure if that is relevant. The overlay map is easily accessed and can be selected again. I will record my session on one of my devices after the next update if that would help.
The overlay is the only setting that is changed. The same base map still loads after the update. My MBTILES overlay maps are betweem 1GB & 2GB each, not sure if that is relevant. The overlay map is easily accessed and can be selected again. I will record my session on one of my devices after the next update if that would help.
Thanks. Can't imagine what may this cause. There is no serious reason for this, weird.
Anyway if you may right after an update, create for me a log by this method http://docs.locusmap.eu/doku.php?id=manual:faq:how_to_create_debug_log , I should check if there is recorded any clue. Thanks
Thanks. Can't imagine what may this cause. There is no serious reason for this, weird.
Anyway if you may right after an update, create for me a log by this method http://docs.locusmap.eu/doku.php?id=manual:faq:how_to_create_debug_log , I should check if there is recorded any clue. Thanks
I just emailed the bugreport and a video showing the process. As mentioned, every device is exhibiting this behavior after the most recent update.
I just emailed the bugreport and a video showing the process. As mentioned, every device is exhibiting this behavior after the most recent update.
Hello Brandon,
thanks for logs and videos. Unfortunately in log were nothing useful for me. I've anyway tried to also update from Google Play in same way as you and may confirm, that issue exists also on my device! After some digging, I finally found a reason for this! It was caused by start screen with list of news, which caused by accident, overwrite of a few settings.
So thank you for a patience and help with solving, should be working OK in next version.
Hello Brandon,
thanks for logs and videos. Unfortunately in log were nothing useful for me. I've anyway tried to also update from Google Play in same way as you and may confirm, that issue exists also on my device! After some digging, I finally found a reason for this! It was caused by start screen with list of news, which caused by accident, overwrite of a few settings.
So thank you for a patience and help with solving, should be working OK in next version.
Replies have been locked on this page!