manual:user_guide:settings:backup_fsys
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| manual:user_guide:settings:backup_fsys [2024/04/03 11:18] – mstupka | manual:user_guide:settings:backup_fsys [2025/09/24 16:06] (current) – mstupka | ||
|---|---|---|---|
| Line 6: | Line 6: | ||
| ==== Set the main directory ==== | ==== Set the main directory ==== | ||
| - | By default, Locus Map's main data is stored in its **private folder** in /// | + | By default, Locus Map's main data is stored in its **private folder** in /// |
| - | * /// | + | * /// |
| - | * both /// | + | * both /// |
| === How to do it: === | === How to do it: === | ||
| - | * tap the selected | + | * tap the selected |
| * tap " | * tap " | ||
| * the app calculates the size of the data for transfer | * the app calculates the size of the data for transfer | ||
| Line 18: | Line 18: | ||
| {{ : | {{ : | ||
| - | If you want only to select a different location for the main app directory | + | If you only want to select a different location for the main app directory **without data transfer**, tap {{: |
| <WRAP center round info> | <WRAP center round info> | ||
| On Android 10 and older versions of the operating system, Locus Map has its main directory at the root of the internal storage - /// | On Android 10 and older versions of the operating system, Locus Map has its main directory at the root of the internal storage - /// | ||
| Line 24: | Line 24: | ||
| ==== Set custom sub-directories ==== | ==== Set custom sub-directories ==== | ||
| - | Some sub-directories can be placed | + | Some sub-directories can be placed |
| 1) in the app's **private folders** in internal storage, external SD card or /// | 1) in the app's **private folders** in internal storage, external SD card or /// | ||
| * **Maps** - raster maps | * **Maps** - raster maps | ||
| * **MapsOnline** - definition files, temp data of online maps | * **MapsOnline** - definition files, temp data of online maps | ||
| - | * **MapsVector** - vector maps, e.g. LoMaps or OpenAndroMaps | + | * **MapsVector** - vector maps, e.g., LoMaps or OpenAndroMaps |
| - | * **geocaching** - user images, spoilers, HTML listings, | + | * **geocaching** - user images, spoilers, HTML listings, |
| * **SRTM** - offline elevation data | * **SRTM** - offline elevation data | ||
| 2) **anywhere** in the device storage: | 2) **anywhere** in the device storage: | ||
| * **Backup** - ZIP files with the backup of tracks, routes, points, and settings | * **Backup** - ZIP files with the backup of tracks, routes, points, and settings | ||
| + | |||
| + | If you want to **CHANGE** the location of any sub-directory, | ||
| + | * **tap** the selected sub-directory | ||
| + | * select the **target storage** | ||
| + | * **confirm** data transfer (without confirming, the custom subdirectory will be set, but the original data will remain in the default one) | ||
| + | * after the change, the app needs a **restart**\\ {{ : | ||
| ---- | ---- | ||
| Line 44: | Line 50: | ||
| === About === | === About === | ||
| - | Tracks, routes and points can be **synchronized across many devices** through our cloud sync service. This is done automatically always after any change made to the database - when a track is recorded, route planned, a point imported... The sync unifies the database content with all other devices **running the same Google account**. | + | Tracks, routes, and points can be **synchronized across many devices** through our cloud sync service. This is done automatically, always after any change made to the database - when a track is recorded, |
| ==== First sync ==== | ==== First sync ==== | ||
| * take the device on which you have the **oldest Locus data** (tracks, routes, points). This device should ideally have all your complete data | * take the device on which you have the **oldest Locus data** (tracks, routes, points). This device should ideally have all your complete data | ||
| - | * open your **track/point manager** and tap the sync button in the topbar:\\ {{ : | + | * open your **Library** and tap the sync button in the topbar |
| * **confirm manual synchronization** and let it go all the way through:\\ {{ : | * **confirm manual synchronization** and let it go all the way through:\\ {{ : | ||
| * **your personal database on the cloud has been created** – you can sync other devices or plan/save routes in the [[https:// | * **your personal database on the cloud has been created** – you can sync other devices or plan/save routes in the [[https:// | ||
| Line 59: | Line 65: | ||
| **How does sync work?** | **How does sync work?** | ||
| - | The synchronization algorithm is based on modification time. The last modification wins. During each synchronization, | + | The synchronization algorithm is based on the modification time. The last modification wins. During each synchronization, |
| - | But you should be careful about one situation - during a sync process on multiple devices also DELETINGS | + | But you should be careful about one situation - during a sync process on multiple devices, also DELETIONS |
| </ | </ | ||
| ==== Settings ==== | ==== Settings ==== | ||
| {{ : | {{ : | ||
| - | * **Automatic sync** - here you can turn it ON or OFF (ON is default) | + | * **Automatic sync** - here you can turn it ON or OFF (ON is the default) |
| * **Wifi-only connection** - turn ON if you want to save your precious cell data | * **Wifi-only connection** - turn ON if you want to save your precious cell data | ||
| - | * **Show new points** - when turned ON the newly synced points are shown on the map screen (not applied for the initial sync) | + | * **Show new points** - when turned ON, the newly synced points are shown on the map screen (not applied for the initial sync) |
| - | * **Show new tracks** - when turned ON the newly synced tracks/ | + | * **Show new tracks** - when turned ON, the newly synced tracks/ |
| ==== Troubleshooting ==== | ==== Troubleshooting ==== | ||
| - | When there is any problem with syncing you can get information about the last sync action in the topbar menu:\\ {{ : | + | When there is any problem with syncing, you can get information about the last sync action in the topbar menu:\\ {{ : |
| - | * **Last update** - generates a log with information about the last syncing action. Use when communicating with helpdesk | + | * **Last update** - generates a log with information about the last syncing action. Use when communicating with the helpdesk |
| ==== Advanced options ==== | ==== Advanced options ==== | ||
| Also available in the topbar menu. | Also available in the topbar menu. | ||
| * **Compute sync plan** - simulates the future syncing process | * **Compute sync plan** - simulates the future syncing process | ||
| - | * **Full download** - removes all tracks, routes and points from Locus Map and downloads the synced data from the cloud | + | * **Full download** - removes all tracks, routes, and points from Locus Map and downloads the synced data from the cloud |
| ==== Cloud ==== | ==== Cloud ==== | ||
| Line 89: | Line 95: | ||
| ==== Automatic backup ==== | ==== Automatic backup ==== | ||
| {{ : | {{ : | ||
| - | ... saves Locus data periodically to // | + | ... saves Locus data periodically to // |
| - **Enable** automatic backup | - **Enable** automatic backup | ||
| - set what you want to backup - the default is all:\\ {{ : | - set what you want to backup - the default is all:\\ {{ : | ||
| - Set **repetition frequency**, | - Set **repetition frequency**, | ||
| === Backup to cloud === | === Backup to cloud === | ||
| - | Automatically backs up selected Locus data to your selected directory at Dropbox, One Drive, or Google Drive: | + | Automatically backs up selected Locus data to your selected directory at Dropbox, One Drive, or <del>Google Drive</ |
| * **enable** the option | * **enable** the option | ||
| * select your favorite **cloud drive**:\\ {{ : | * select your favorite **cloud drive**:\\ {{ : | ||
| Line 101: | Line 107: | ||
| <WRAP important round> | <WRAP important round> | ||
| * **Attached media (photos, videos...) are not backed up** | * **Attached media (photos, videos...) are not backed up** | ||
| - | * **Maps are not backed up this way.** They are automatically backed up on our servers, some third-party maps are backed up a [[manual: | + | * **Maps are not backed up this way.** They are automatically backed up on our servers; some third-party maps are backed up a [[manual: |
| * Xiaomi devices with MIUI 12+ - make sure you have **" | * Xiaomi devices with MIUI 12+ - make sure you have **" | ||
| + | * **Since September 2025, Locus Map has not supported Google Drive as it was denied full access to the service.** | ||
| </ | </ | ||
| ==== Manual backup ==== | ==== Manual backup ==== | ||
| {{ : | {{ : | ||
| - | Saves a single backup file with Locus data to // | + | Saves a single backup file with Locus data to // |
| - **set** what you want to backup (the same selection as with the automatic backup) | - **set** what you want to backup (the same selection as with the automatic backup) | ||
| - set backup to **cloud** (optionally, | - set backup to **cloud** (optionally, | ||
| + | ==== App migration backup ==== | ||
| + | {{ : | ||
| + | This command triggers a process of packing **all the app's data** (maps, tracks, points, settings, attachments...) **into one ZIP file**, which can be used as a general backup when you need to start using Locus Map on another device. The file can be very large, and the app informs about the **required space** for storing it:\\ {{ : | ||
| + | The backup file is stored in the /// | ||
| ==== Restore from backup ==== | ==== Restore from backup ==== | ||
| * select **storage** where the backup file is stored:\\ {{ : | * select **storage** where the backup file is stored:\\ {{ : | ||
| Line 117: | Line 127: | ||
| * **restart** Locus Map | * **restart** Locus Map | ||
| <WRAP center round important> | <WRAP center round important> | ||
| - | Restore from backup **overwrites all related data**. Keep this in mind, especially regarding your tracks, routes and points. | + | Restore from backup **overwrites all related data**. Keep this in mind, especially regarding your tracks, routes, and points. |
| </ | </ | ||
| Line 125: | Line 135: | ||
| <wrap info> | <wrap info> | ||
| ==== Load app data ==== | ==== Load app data ==== | ||
| - | It searches the device storage for the app's main directory provided it is not placed in the current location. Used in case the user cancels the data transfer after an update on Locus Map version 4.5.x. and newer. | + | It searches the device storage for the app's main directory, provided it is not placed in the current location. Used in case the user cancels the data transfer after an update on Locus Map version 4.5.x. and newer. |
| ==== Unload app data ==== | ==== Unload app data ==== | ||
| It moves all data of the app out of its main directory to a selected part of the storage. Used above all when reinstalling the app with the main storage in the private directory, which is usually removed by the uninstall. | It moves all data of the app out of its main directory to a selected part of the storage. Used above all when reinstalling the app with the main storage in the private directory, which is usually removed by the uninstall. | ||
| Line 140: | Line 150: | ||
| <WRAP round alert > | <WRAP round alert > | ||
| - | **Warning**: | + | **Warning**: |
| </ | </ | ||
manual/user_guide/settings/backup_fsys.1712135906.txt.gz · Last modified: by mstupka
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
