Offline maps only working once
Hi,
After several attempts to install offline maps in Locus Pro, latest version, I get it temporarily working....
My System:
Samsung Tab Pro 8.4
Cyanogen Mod 13.0 mondrianwifi nightly
Android: 6.0.1
64 GB SDCard extern
My Problem:
Offline Maps from OpenAdroMaps are not working. I copied them to the mapsvector folder but locus will not load them.
So I bought the following maps from the locus store:
Chile, Argentinia, Bolivia and Peru.
After the downloads are finished, all maps are available as offline maps and working fine.
After locking an unlocking the screen Locus is restarting and get stuck at 0% right at the beginning.
My workaround:
I renamed mapsVector to mapsVectorx. After restarting the tablet locus is starting fine without any problems.
Then I rename mapsVectorx to mapsVector again and after some seconds all offline maps are available and working again untill the next restart of Locus.
Does anybody has some clue what's causing this strange behaviour ?
thanks
Michael
The same problem 
Hello Michael,
If the maps on the external SD card?
If so, then I think it is up to the new SD Card Management in Android 6.0,
Is the SD Card registered as external or internal memory?
If then as External Memory Locus has no access to it, but it would have at the start of Locus a message coming which the directory must be re-selected.
I've got it only makes sense under CM13 when migrating the SD card as internal memory.
Hello Michael,
If the maps on the external SD card?
If so, then I think it is up to the new SD Card Management in Android 6.0,
Is the SD Card registered as external or internal memory?
If then as External Memory Locus has no access to it, but it would have at the start of Locus a message coming which the directory must be re-selected.
I've got it only makes sense under CM13 when migrating the SD card as internal memory.
No, all maps are on internal memory.
I know that you can use the sd card as external memory or as internal memory with all the drawbacks...
(Whatever you decide, there are always massive drawbacks in my opinion. But I want to stick to use the sd card as external memory, even a lot of apps seems to can't use it properly right now )
Changing the storage options in locus to use offline maps from sd card is also not working, by the way....
So I decided to use only internal memory for all maps and so on be "free of side effects" which comes from the sd card handling in Android 6
No, all maps are on internal memory.
I know that you can use the sd card as external memory or as internal memory with all the drawbacks...
(Whatever you decide, there are always massive drawbacks in my opinion. But I want to stick to use the sd card as external memory, even a lot of apps seems to can't use it properly right now )
Changing the storage options in locus to use offline maps from sd card is also not working, by the way....
So I decided to use only internal memory for all maps and so on be "free of side effects" which comes from the sd card handling in Android 6
Hello guys,
I have to say that such weird behavior really looks like some problem in CM rom and not in Locus. Sorry to say that, but I see nothing I (as a Locus developer) may help here.
Vector maps should cause no troubles no matter if they are on read-only SD card or in internal memory. No matter if they are from Locus Store or from OpenAndroMaps or other sources.
Only what you may try is right after it stops working, create for me a log with CatLog application. Maybe there will be any clue that may helps ...
Hello guys,
I have to say that such weird behavior really looks like some problem in CM rom and not in Locus. Sorry to say that, but I see nothing I (as a Locus developer) may help here.
Vector maps should cause no troubles no matter if they are on read-only SD card or in internal memory. No matter if they are from Locus Store or from OpenAndroMaps or other sources.
Only what you may try is right after it stops working, create for me a log with CatLog application. Maybe there will be any clue that may helps ...
Hi Menion,
I took the log. How can I send it to you rather than attaching it in the forum ?
Hi Menion,
I took the log. How can I send it to you rather than attaching it in the forum ?
Hello Michael,
you may pack log as zip and attach it here (best solution) or send it to our not-a-lot-used-email: locus@asamm.com , thanks
Hello Michael,
you may pack log as zip and attach it here (best solution) or send it to our not-a-lot-used-email: locus@asamm.com , thanks
Hi Menion,
Here's the log file
Hi Menion,
Here's the log file
Hello Michael,
thanks for a log. Unfortunately I do not see any useful information that make sense to me and say something about this problem. Only in the end (line 2651 for example) is line:
01-04 19:22:19.198 W/menion.android.locus.pro( 3717): type=1400 audit(0.0:1861153): avc: denied { getattr } for comm=4173796E635461736B202332 path="/sys/kernel/debug/clk/mdss_mdp_clk/list_rates" dev="debugfs" ino=1421 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:debugfs:s0 tclass=file permissive=0
Which looks like Locus tries to access system files in "/sys/kernel/..." directory and many others, but Locus never touch such places in device. So sorry, but I have no idea, what may cause this.
Another help here should be creating some special Locus version that will print out some more information about this problem. But to be true, few years ago, usually original roms caused a troubles and alternatives like CM and some others, had these problems fixed and worked well. Unfortunately during last year, most of serious problems are mainly in CM as I see. And because I see you use even a nighly version, I think it is waste of time to try to find some solution inside Locus. Sorry.
Hello Michael,
thanks for a log. Unfortunately I do not see any useful information that make sense to me and say something about this problem. Only in the end (line 2651 for example) is line:
01-04 19:22:19.198 W/menion.android.locus.pro( 3717): type=1400 audit(0.0:1861153): avc: denied { getattr } for comm=4173796E635461736B202332 path="/sys/kernel/debug/clk/mdss_mdp_clk/list_rates" dev="debugfs" ino=1421 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:debugfs:s0 tclass=file permissive=0
Which looks like Locus tries to access system files in "/sys/kernel/..." directory and many others, but Locus never touch such places in device. So sorry, but I have no idea, what may cause this.
Another help here should be creating some special Locus version that will print out some more information about this problem. But to be true, few years ago, usually original roms caused a troubles and alternatives like CM and some others, had these problems fixed and worked well. Unfortunately during last year, most of serious problems are mainly in CM as I see. And because I see you use even a nighly version, I think it is waste of time to try to find some solution inside Locus. Sorry.
Hu Menion,
thanks for your help !
Maybe I have to switch back to CM 12 which worked great with Locus.
Locus is more important for me than Android 6.
cheers
michael
Hu Menion,
thanks for your help !
Maybe I have to switch back to CM 12 which worked great with Locus.
Locus is more important for me than Android 6.
cheers
michael
Replies have been locked on this page!