Differences

This shows you the differences between two versions of the page.

--- manual:faq:problems_points_tracks_database [2022/01/21 11:45] – [How to fix it] mstupka
+++ manual:faq:problems_points_tracks_database [2025/12/12 15:33] (current) – mstupka
@@ Line 1: / Line 1: @@
-====== Problems with points&tracks database ======
+====== Problems with the database of points&tracks ======
 ----
-===== Basic information =====
+Locus Map uses the SQLite database system for storing data. This database is supported by all Android devices and is considered safe and convenient. However, it can happen that the database gets damaged and the app ends up with an error.
+===== How does it look? =====
+Usually, the app displays an error message during initialization, informing about the problem with the user database and the **error number 11556**.
-Locus Map uses the SQLite database system for storing data. This database is supported by all Android devices so it is easy for developers to use the SQLite database in their applications.
+===== How to prevent it =====
-At many places you may read how safe and convenient the SQLite system on Android is. The reality is somewhat different.
+  * **Use the default private directory for the app's data in the internal storage** - working with the data is faster, more stable, and there is almost no chance of damaging the internal memory of the mobile phone - your data is protected better than on an SD card.
+  * If you decide to place the Locus directory on the SD card, please **check occasionally that your card is in good shape**. Use some of the Windows/Linux diagnostic tools for the SD card check-up. We also suggest not to keep Locus backup files only on your SD card, but also at some location outside your phone (Dropbox, OneDrive).
-In the following paragraph the most common errors you may encounter in Locus are described, as well as the methods of fixing them. These methods are based on the experiences of our users so if you have any other, share them with us, please.
-**Generally speaking, when you get any error with Locus database, it is wrong.** For this reason there is the [[manual:user_guide:tools:backup|Backup function]] from the 2.8.0 version. The Backup function allows regular updates (on background, when you are not using Locus) of all your data in Locus.
-===== Methods helping to prevent database corruption =====
-  *  If you hesitate between selecting either “Place Locus directory on the SD card, or into the internal memory” - select the internal memory. Working with the data is faster and more stable. There is almost no chance of damaging  internal memory of the mobile phone. Therefore your data are protected better than on the SD card.
-  * If you have Locus directory placed on the SD card, please check occasionally that you card is in good shape. Use some of the Windows/Linux diagnostic tools for the SD card check-up. We also suggest not to keep Locus Backup files only on your SD card but also at some other location. Your desktop computer (PC) or Dropbox, for example.
 ===== How to fix it =====
-There is no guaranteed method of repairing corrupted database.
+Unfortunately, there is no guaranteed method of repairing a corrupted database. Actually, there are **three methods that you can try**:
-Actually, there are **three methods that you can try**:
-**1.** Some errors may be caused by reading or recording on your SD card. Violation of the card may result in database locking, for example. In most cases simple **restart of your phone** helps. Then it is highly recommended to check your SD card.
+**1. Restart your phone** - some errors may be caused by reading or recording on your SD card. Violation of the card may result in database locking, for example. In most cases, a simple restart helps. Then it is highly recommended to check your SD card.
-**2.** The second method - database **restoration from the automatic backup**. All backup files are stored in Locus/backup directory (or in “auto” directory intended for automatic backups). This backup is a simple zip file.
+**2. Restore backup of your database** - all backup files are stored in Locus/backup directory (automatic backups in the Locus/backup/auto/ directory). This backup is a simple zip file.
-    * Close Locus
+    * Close Locus Map
-    * Go to the Locus/data/database directory. Move tracks.db and waypoints.db into your PC (it is not necessary, just for greater safety)
+    * Connect your phone to a PC via USB and allow data transfer
-    * Move to the directory Locus/backup/auto and find the latest backup file (*.zip)
+    * Open a file browser on the PC and navigate to the Locus/data/database directory on your phone. Move tracks.db and waypoints.db into your PC (it is not necessary, just for greater safety)
-    * Expand *.zip file and open data/database folder
+    * Navigate to the directory Locus/backup/auto and find the latest backup file (*.zip)
+    * Unpack the *.zip file
     * Copy the unzipped tracks.db and waypoints.db to the Locus/data/database folder
-    * Start Locus
+    * Start Locus Map
-**3.** If all previous fail, try this:
+**3. If 1 or 2 fail** - try the following:
   * go to your phone file browser > find /Locus/data/database/ directory and copy files tracks.db and waypoints.db somewhere out of this directory
-  * uninstall Locus
+  * uninstall Locus Map
-  * delete whole /Locus/ directory
+  * delete the whole /Locus/ directory
-  * install Locus from Google Play
+  * re-install Locus Map from Google Play
   * copy your original files tracks.db and waypoints.db to /Locus/data/database/ - overwrite the newly created ones
-**4.** The last method (advanced) is described **[[manual:advanced:map_tools:corrupted_sqlite|here >>]]**
+**4. Advanced method** - visit [[manual:advanced:map_tools:corrupted_sqlite|here >>]]

knowledge base

User Tools

Site Tools

Differences