After working for 3 hrs with Wilfried, these are the findings, and they are concerning:
- setup: Android 11, Samsung device (not a Galaxy), Locus 4 latest, free, data saved, then Locus data wiped by Android, login via Google Account
- the wiping was necessary, because Locus got stuck in the attempt to migrate the base folder from EXT to INT SD. This is definitely a flaw on Locus part - there should be the offer to enforce INT SD private folder regardless.
- Locus is able to establish mapsVector on EXT SD in settings
- Locus also can download LoMaps from Locus Store
- the downloaded map is then available as base map without further user activity
- HOWEVER, listing the offline maps will tell you that there is NO offline map at all
- reproducable at will
- putting that SD card into an external reader shows the Locus structure in private /Android/data, but even x-plore, the most potent file manager when it comes to Android obstacles, cannot access the /Android/data on EXT SD, nor can the Samsung file manager, NOR can an USB connected PC!
- the resolution was:
-- wipe Locus data after backup
-- use INT SD private folder as base
-- put the saved maps in EXT SD/Android/media (!!) menio...n structure
-- luckily (I remember well the disputes last year about /Android/media) Locus screens those folders at startup
I definitely advise to offer /Android/media as a folder home for any custom sub-directories. Why? Android/media seems safe from Google restriction insanities so far. Other apps can access those structures, PCs as well, despite vendor hassle around /Android/data (I guess above specialiity is a Samsung "feature" for this device type, and other vendors may screw up, too). And this /Android/media should become the recommended (best practise) location for mass data.
It makes Locus more resilient and user friendly
Cheers
Michael
I also have the same problem either since the last LocusMaps Pro (Classic) update (from around July 22) or the latest Android 11 update (Security Patch Level June 2022) on a Galaxy Tab Active Pro SM-T540
The last selected map (a mbtiles) still works (loads the tiles as expected) but the displays in LocusMaps are empty and I cannot select one of the other maps stored in the SD card's private locus directory.
What is also interesting is, that when I click the + button on the offline maps section, select the import option and then the "Hauptverzeichnis" ("Main directory"?) - I only get an empty file picker, as if locus wouldn't have any directory listing rights there...?
I also have the /Locus directory listed from an earlier install.
I prefer not to uninstall and reinstall it, as reinstalling 60GB of mbtiles maps is just hours of work...
I also have the same problem either since the last LocusMaps Pro (Classic) update (from around July 22) or the latest Android 11 update (Security Patch Level June 2022) on a Galaxy Tab Active Pro SM-T540
The last selected map (a mbtiles) still works (loads the tiles as expected) but the displays in LocusMaps are empty and I cannot select one of the other maps stored in the SD card's private locus directory.
What is also interesting is, that when I click the + button on the offline maps section, select the import option and then the "Hauptverzeichnis" ("Main directory"?) - I only get an empty file picker, as if locus wouldn't have any directory listing rights there...?
I also have the /Locus directory listed from an earlier install.
I prefer not to uninstall and reinstall it, as reinstalling 60GB of mbtiles maps is just hours of work...
Hi Zdenek and Matthias,
Thanks for the advice.
Hmm, it's curious that sdcard/Locus was was set as a Supplementary Directory after a fresh install. That directory hasn't existed since I had to make a private folder for Locus Map to work with Android 11. I don't think it was specified in any of the directory settings, so not sure where it got that from.
Anyway, I uninstalled Locus Map completely and made sure that no menion or Locus directories existed anywhere (using X-plore, and the card reader in my PC). Then reinstalled Locus Map Classic and, without changing any default directory settings, downloaded LoMap NZ East to internal storage. This works fine and shows in the Offline Maps list - see screenshot.
I then set the Main Directory to the Private folder on SD card. I was expecting this to move the LoMap to the SD card and take a while, but it was very quick and the LoMap remains in internal storage. However it still shows as available in the Offline maps list. Attached is a screenshot of the About page, showing the emulated SD card as a Supplementary Directory. It also no longer shows sdcard/Locus as a Supplementary Directory :).
I then tried to import the NZ topo tile maps. This did get copied to the private folder on the SD card, and was initially viewable, but is not recognised in the Offline maps list!
So I agree with Matthias, it seems that from a recent update, Locus Map can no longer recognise maps in the private folder on the SD card. I'm also shown an empty folder when trying to import another map from the Main Directory.
I haven't got enough internal storage to store the tile maps there. Is an SD card solution possible?
Cheers, Matt.
Hi Zdenek and Matthias,
Thanks for the advice.
Hmm, it's curious that sdcard/Locus was was set as a Supplementary Directory after a fresh install. That directory hasn't existed since I had to make a private folder for Locus Map to work with Android 11. I don't think it was specified in any of the directory settings, so not sure where it got that from.
Anyway, I uninstalled Locus Map completely and made sure that no menion or Locus directories existed anywhere (using X-plore, and the card reader in my PC). Then reinstalled Locus Map Classic and, without changing any default directory settings, downloaded LoMap NZ East to internal storage. This works fine and shows in the Offline Maps list - see screenshot.
I then set the Main Directory to the Private folder on SD card. I was expecting this to move the LoMap to the SD card and take a while, but it was very quick and the LoMap remains in internal storage. However it still shows as available in the Offline maps list. Attached is a screenshot of the About page, showing the emulated SD card as a Supplementary Directory. It also no longer shows sdcard/Locus as a Supplementary Directory :).
I then tried to import the NZ topo tile maps. This did get copied to the private folder on the SD card, and was initially viewable, but is not recognised in the Offline maps list!
So I agree with Matthias, it seems that from a recent update, Locus Map can no longer recognise maps in the private folder on the SD card. I'm also shown an empty folder when trying to import another map from the Main Directory.
I haven't got enough internal storage to store the tile maps there. Is an SD card solution possible?
Cheers, Matt.
I think I have a solution!
Locus Map Classic creates a non-private menion.android.locus.pro folder under Android/media on the SD card. I moved the tile maps out of the private folder on the SD card, and the LoMaps out of internal storage, into their respective positions into this media folder - and it seems to work! See screenshot.
Thanks for the help :)
Matt.
I think I have a solution!
Locus Map Classic creates a non-private menion.android.locus.pro folder under Android/media on the SD card. I moved the tile maps out of the private folder on the SD card, and the LoMaps out of internal storage, into their respective positions into this media folder - and it seems to work! See screenshot.
Thanks for the help :)
Matt.
Yes, same - Samsung Galaxy Xcover 4s, Android 11, Kernel 4.4.177-23020803, Android security patch July 1st 2022.
A difference between 'data' and 'media' is that data is private. It appears that apps now don't have write access to even their own private folders on the sdcard!?
I still can't export tracks and waypoints though. I presume this might be because Locus Maps constructs the export file locally in its private folder first before moving it to the selected destination.
Cheers Matt.
Yes, same - Samsung Galaxy Xcover 4s, Android 11, Kernel 4.4.177-23020803, Android security patch July 1st 2022.
A difference between 'data' and 'media' is that data is private. It appears that apps now don't have write access to even their own private folders on the sdcard!?
I still can't export tracks and waypoints though. I presume this might be because Locus Maps constructs the export file locally in its private folder first before moving it to the selected destination.
Cheers Matt.
Samsung Galaxy Xcover 4s is the device, as in
https://help.locusmap.eu/topic/29156-offline-maps-list-is-empty
Samsung Galaxy Xcover 4s is the device, as in
https://help.locusmap.eu/topic/29156-offline-maps-list-is-empty
@Zdenek: Menion CAN help, I suppose:
I definitely advise to offer /Android/media as a folder home for any custom sub-directories. Why? Android/media seems safe from Google restriction insanities so far. Other apps can access those structures, PCs as well, despite vendor hassle around /Android/data (I guess above specialiity is a Samsung "feature" for this device type, and other vendors may screw up, too). And this /Android/media should become the recommended (best practise) location for mass data.
(copy from https://help.locusmap.eu/topic/29219-findings-from-case-28548-resolution-locus-unable-to-work-with-ext-sd-private-folder)
I even would go so far to streamline the initial Locus (non-AFA) setup to this combination:
- INT SD /Android/data base folder
- EXT SD (if such exists) /Android/media as default folder for maps, mapsVector and SRTM, otherwise INT SD /Android/media
Show that choice to "OK" and add another line "Expert settings" where people have other choices, and the sub-directory choices should be offered right there - for the Experts.
Non-geeks cannot judge the hidden consequences of their choices, so a full best practise setup should be one-click, also for the sub-directories.
@Zdenek: Menion CAN help, I suppose:
I definitely advise to offer /Android/media as a folder home for any custom sub-directories. Why? Android/media seems safe from Google restriction insanities so far. Other apps can access those structures, PCs as well, despite vendor hassle around /Android/data (I guess above specialiity is a Samsung "feature" for this device type, and other vendors may screw up, too). And this /Android/media should become the recommended (best practise) location for mass data.
(copy from https://help.locusmap.eu/topic/29219-findings-from-case-28548-resolution-locus-unable-to-work-with-ext-sd-private-folder)
I even would go so far to streamline the initial Locus (non-AFA) setup to this combination:
- INT SD /Android/data base folder
- EXT SD (if such exists) /Android/media as default folder for maps, mapsVector and SRTM, otherwise INT SD /Android/media
Show that choice to "OK" and add another line "Expert settings" where people have other choices, and the sub-directory choices should be offered right there - for the Experts.
Non-geeks cannot judge the hidden consequences of their choices, so a full best practise setup should be one-click, also for the sub-directories.
Thanks for the advise Zdenek and Michael!
I see some commentary on the Samsung forums about their last security update in July, so I suspect that might have something to do with it too.
Thanks for the advise Zdenek and Michael!
I see some commentary on the Samsung forums about their last security update in July, so I suspect that might have something to do with it too.
Hello Matthew,
you are probably 5+ user this month who report any (not just file-system) problem with Samsung XCover 4s, weird. There seems to be something really wrong with this device.
I've now created an option to set the default directory into the Android/media directory for all types of maps as mentioned @Michael Bechtold. It will need some testing on our side (and Beta testers) anyway this feature should be available in the next app version in September.
Jiří M. aka Menion
Hello Matthew,
you are probably 5+ user this month who report any (not just file-system) problem with Samsung XCover 4s, weird. There seems to be something really wrong with this device.
I've now created an option to set the default directory into the Android/media directory for all types of maps as mentioned @Michael Bechtold. It will need some testing on our side (and Beta testers) anyway this feature should be available in the next app version in September.
Jiří M. aka Menion
Hi Menion,
Thanks for implementing that solution. The Xcover problem seems to affect anything in the private sdcard folder, including export work files and waypoints. Eg, I couldn't see geocache hints last weekend.
I don't think the Xcover gets the same attention at Samsung as their main Galaxy series of phones. :(
Thanks for your help.
Matt
Hi Menion,
Thanks for implementing that solution. The Xcover problem seems to affect anything in the private sdcard folder, including export work files and waypoints. Eg, I couldn't see geocache hints last weekend.
I don't think the Xcover gets the same attention at Samsung as their main Galaxy series of phones. :(
Thanks for your help.
Matt
Great news, Menion!
And I hope it will not be in a private sub-structure, but in a freely definable folder.
Which also would survive a (temp.) de-install of Locus. AND it would allow LMP und LM4 to use the same maps ...
Good luck and cheers
Michael
Great news, Menion!
And I hope it will not be in a private sub-structure, but in a freely definable folder.
Which also would survive a (temp.) de-install of Locus. AND it would allow LMP und LM4 to use the same maps ...
Good luck and cheers
Michael
Replies have been locked on this page!