User Tools

Site Tools


manual:faq:android_11_filesystem

This is an old revision of the document!


Using Locus Map on Android 11+ file system

UNDER DEVELOPMENT


What is this all about?

In November 2021, Google launched a new file management system in Android 11 and the following versions), bringing a major change to the way Locus Map and other applications handle their data:

  • the app has a full read/write access only to its PRIVATE FOLDER in /Android/data/ system directory (either in the internal storage or in the external storage - removable SD card)

Advantages

  • The app shows a better performance in stability and responsiveness
  • Its data is secured against access from other apps (possible attacks from malware etc.)
  • After the uninstallation, it leaves no garbage in the device storage.

Drawbacks

  • All app data is deleted upon uninstall - the majority of devices show a warning prompt with the option to retain the app data in the storage. But especially Chinese products erase the data without an option of restoring.
  • No use of other apps data - it is no longer allowed to share one common directory between Locus Map Pro and Locus Map 4.
  • No custom sub-directories - the app can read/write vector maps and SRTM data only in its private directory (only backup files can be stored elsewhere). Also, custom directories with geotagged photos are not supported - Locus can read from the default system media directory only.
  • Disabled linking to maps from external folders - all raster maps can be stored only in /Locus/Maps/ directory, all vector maps in /Locus/mapsVector/ directory.

As a precaution we urgently recommend:

What to do with it?

The original default setting of the Locus Map main directory was in the root of the internal storage of the device. Plus, custom sub-directories could be set elsewhere in the internal or external storage (removable SD card), and external maps could be linked to the app from anywhere in the device storage.

As this setup is no longer possible on Android 11+, we've prepared a few scenarios for smooth and secure transfer of your data after the app update:

Update when a single Locus Map is installed

When only a single app is installed on the device (the other Locus is not installed), the app update goes through the most simple and straightforward process.

How to do it >>

Update when both Locus Map 4 and Locus Map Pro are installed

Older Android versions enabled sharing of the main app directory between Locus Map 4 and Locus Map Pro. This is no longer possible, each app can use only its own private folder. After the update, you have to decide whether to use only one of the apps or both with the data size doubled.

How to do it >>

Transfer of the custom sub-directories

Originally, Locus Map could place subdirectories with vector maps, offline elevation data (SRTM) and backups out of its main directory. This is no longer possible for the vector maps and SRTM data.

Vector maps and SRTM data

If you had this data stored in custom sub-directories, Locus Map detects them and offers to merge them into the main app directory during the app data transfer:

What if I refuse?

You lose access to the data via Locus. The data will remain in the device storage though.

Backup sub-directory

The only sub-directory that can be placed out of the main app directory.

Transfer of external maps

Linking of the maps from external directories is also no longer supported. The external maps can be used only within the default /Locus/Maps/ directory.

Unfortunately, it is not technically possible to include external maps into the automatic transfer of the app data. You have to move the maps to /Locus/Maps/ directory manually via the system file manager.

Surprisingly, some system file managers do not have access to the /Android/data/ directory. In such a case, please use a third-party file manager, e.g. X-plore or Total Commander.

Custom folders with geo-tagged photos

Locus Map on Android 11+ can access only the default system media folder (usually /storage/emulated/0/DCIM)

If you want to display photos from custom directories on the map, you have to move/copy them to this default media folder via a system file manager.

New installation of Locus Map on a device with the other one installed

Older Android versions enabled sharing of the main app directory between Locus Map 4 and Locus Map Pro. This is no longer possible, each app can use only its own private directory. Many users had both apps installed for various reasons. After the update, they have to decide whether to use only one of the apps or both with the data size doubled.

Locus Map in the internal storage

Locus Map in the private folder

The process is the same as in the previous case - the app moves/copies the other app data to its directory. With one exception:

Main directory in the internal storage

If the other Locus is in the private directory, Locus does not detect the internal-storage directory. If you need to use its data, you have to migrate it manually in Locus settings > Miscellaneous > Default directories > Load app data

Both Locus Map 4 and Locus Map Pro on the device

Quite a few users have both apps installed. For such a case, we've prepared the data transfer in three scenarios:

Update of one Locus Map when both in the internal storage

After downloading and installing the update, the newly updated app detects the other one and offers to migrate its data:

Moving data

  • data of one app is transferred to the main directory of the other app
  • the first app (and other possible apps) loses access to its data (the first app can go on with a new empty database - no maps, no tracks/points etc. - that is created automatically)
  • custom sub-directories and external maps are not transferred - both apps lose access to this data - therefore, we recommended merging the custom sub dir data to the main directory before the whole app data transfer (you can do it later via a system or third-party file manager)

Copying data

  • data of one app is copied to the main directory of the other app
  • both apps continue to work independently, each using its own database of tracks, routes and points. The databases are not synced.
  • custom sub dirs and external maps are not copied - only the first app keeps access to them

One Locus in private folder, the other one in internal storage

In both cases, the updated app detects the other one primarily. But then you will be prompted to select and confirm the directory of the other app manually via a system (or third-party) file manager.

manual/faq/android_11_filesystem.1638270691.txt.gz · Last modified: 2021/11/30 13:11 (external edit)