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