Locus Map Does Not Run Since Device Update to Android 4.4.2 KitKat
Leider ist der Eintrag nur auf Čeština und English verfügbar.
Mögen Sie Locus Map?
Comments
8
Leider ist der Eintrag nur auf Čeština und English verfügbar.
Mögen Sie Locus Map?
Comments
8
hey devs,
the current version only works with locus on internal storage (sd)? why you dont check if device is rootet or not? i can’t copy locus folder to the internal storage because there is no more space.
this is a dissatisfying situation 🙁
Hi,
please see section Solution C – Devices with ROOT permission in this article. Users with rooted devices don’t need to move data into internal memory. You only need to change android permission.
Locus Map do you developers read the release notes? All you have to do is create a sub folder in your applications folder on the external sdcard and everything will work fine. For example:
Android/data/com.locus android/files
Downloaded maps etc go into the files sub folder and everything will work just fine.
Simply update your app to the new requirements
Hello Keith,
thank you for you comment. I’ll forward this discussion on Google+ ( https://plus.google.com/118282045438155427142/posts/JCAER8nGWAW ) to keep it on one place.
Hi,
I’m not Android developer, but AFAIK there are already available applications (non-system, not-rooted) which are able to write (delete, rename) files on external SD card. Hope you will investigate in this ‚issue‘ to find some solution for Locus to work again with SD card.
BTW: no problems with Locus moved to internal storage so far (on Galaxy Note 3, KitKat).
Just FYI, thanks for great product anyway!!
Hi,
can you give me please some example, please? We’d like to solve it, so every idea is welcome. Maybe additional note: Application can save data into private folder managed by Android system. But this is not applicable to Locus because we need/want to have data in folder called Locus.
Hi.
Latest (3.1.1) version of ES File Explorer can create or write to any folder on extSD. Previous can’t – verified. 🙂
Hi,
It seems that ES File Explorer uses probably some hack via the media content files. We’ll be watching it.
Thank you