Locus Does Not Run Since Update Device To Android 4.4.2 KitKat

Post 7 of 44
Locus error message - Android KitKat
  • Problem

After upgrade on Android 4.4.2 Locus does not run correctly. Crash or does not run either.


Unfortunately, Android 4.4.2 has a new feature, that prevent all installed application from writing data on external SD card. Locus cannot correctly store and read your maps, points or tracks if are stored on SD card. For this reason Locus is not able to start.


Who is involved

  • Current Locus users are affected (issue does not affect new users)
  • Only devices with SD card are influenced.
  • The issue does not occur on devices with custom ROM


Solution A – General solution for all devices

Solution B – Sony devices with pre-installed File Commander App

Solution C – How to leave my maps on external SD card

Solution D – Devices with ROOT permission


A. Move Locus to the internal storage

  • Install arbitrary Android file manager – for example ES File Explorer
  • Open it and go to your external SD card (often marked as sdcard1)
  • Long tap on Locus folder and choose Copy
Long tap on Locus folder

Long tap on Locus folder

Copy Locus folder to the internal storage

Copy Locus whole Locus folder to the internal storage

  • Navigate to the internal memory (often marked as sdcard0) and Paste Locus folder
Paste Locus folder on internal storage

Paste Locus folder on internal storage

  • Check that process was successful and you can see all Locus data on internal storage
  • Pull out the external SDcard from phone and connect it with to your notebook or desktop computer
Rename Locus folder on SDcard

Rename Locus folder on SDcard

  • Remove (or rename for safety) Locus folder on external SDcard. The goal is to have only one folder Locus that is located on internal storage

B. Sony devices with preinstalled File Commander App

The latest Sony devices have installed File Commander app. This application has permission for write/remove data from SD card. For this reason you can move using this app whole Locus folder from SDcard to the internal storage

  • Open File Commander app and go to your external SD card
  • Select Locus folder and from bootom panel choose Cut
  • Navigate to the internal memory and choose Paste
Locus folder from Sd card
Sony kitkat paste Locus

Please note: if you get warning that File Commander has no permission for writing to the SDcard then use Solution A.

C. How to leave my maps on external SD card

Locus personal maps and Locus vector maps can be stored in external directory on SD card. Please follow steps bellow:

  • Connect card to the PC and create arbitrary folder on the SDcard for your maps e.q. MyLocusExternMaps
  • Move maps from folders (Locus/maps and Locus/mapsVector) to the folder MyLocusExternMaps
  • Move folder Locus from SDcard to the internal memory. (Without map files)
  • Start Locus (choose internal folder)
  • Open Menu > Maps > From top right menu choose “Add Maps” > Add > navigate to the folder MyLocusExternMap and tap on “checkmark” in top panel

The result is that the Locus working directory will be placed on internal memory and all maps will located in external folder on SDcard. This issue is also described in article: Saving offline maps on SD-card under Android 4.4 (KitKat)

D. Rooted devices

  • In case that your device is rooted you can fix it by editing the system configuration
  • Install application SDFix and perform the system changes
  • After that simply start Locus

For more information please see:

Why Locus developers didn’t fix it?

Every application can create own package-specific directories on SD card and use it for writing the own data. Unfortunately there are more reason why this solution is not suitable for Locus app.

  1. Locus has more then one version where every version has special package name (it has to be), which means every version will have own unique directory.
  2. These directories are automatically removed after you un-installation of Locus app. This is not convenient in case that you can have GBytes of map files


General information about this issue


This article was written by Voldy