Messages

Re. mapsVector on INT:
on my Tab device I first migrated to internal, with a number of subfolders in mapsVector.
Then I moved the mapsVector from INT to EXT private folder. And downloaded some stuff. But there is still stuff left on INT. No harm to me, though.

...
I think with this function only writing is allowed but not reading.
So it is only usable for backup.

Then exports can go there easily, too :-))) If Menion allows (would be an easy switch: option to combine exports with backup folder - done).
Imagine: you have a new track of 500K and back up 1 GB - instantly  to be safe. Cloud (Locus Gold or other) in the forests ?

@Menion: after rereading carefully I understood that the backup folder can be outside of the private Android/data realms.
I tried and it worked.
From your earlier explanations I do not understand why such would work. And why not for all the other needs.
Can you pls enlighten me?
TXs and cheers
Michael

PS: copying FOLDERS to ext. SD even works when they come from int. SD.
Once they have files inside, those fail, but the folder hierarchy is copied.

Another screw up on Google's part. Michal (from x-plore) should give them the whips.

export is the poor men's backup of tracks. Hence the database and the export folder have to be on different storage, I think.

One other funny finding: before you put the maps on ext. SD in place, I had downloaded some vectore maps, without thinking about proper structure.
Now I tried x-plore to move the things - and it worked.
Next I tried to copy some other unrelated file from ext. SD into the Locus structure - it WORKED!
Next I tried to copy any file from int. SD to the Locus ext. SD place - bummer!
Also creating and moving folders on ext. SD works with x-plore.

WHERE IS MY MAPS ON internal sd GONE!
To the external SD structure. Worked like a charm. The online thing I want to keep internal.

PS: the external SD location for the export directory for the GPX would be important, too.
In particular for silver and free.

Cool - really quick progress, Menion!

Happy to run a special test version for the slow start issue. Here some more food upfront:
- status "Initializing" is associated with 11% progress. There it rests for minutes. Also after new Locus starts
- this happened with very few maps only in the whole system
- and also happens with some douzen maps (OAM all of Europe), for which you see nice progress in % after the 11% stop point is overcome.

@tapio: I just put my W1-11 MBtiles world map into the EXTERNAL SD private mapsVector folder.
Locus did recognize it :-)) May be not academic approach, but I do not care as long as it works.

@Menion: two things:
1) although my Tab is fully migrated, it stays at "Initializing" for minutes. For nothing.
You mentioned that the full storage capacity overview is extremely time consuming.
But once an installation is migrated, there should be no need for such exercise, right?
2) re. above: as you have the migration code at hand anyway, it would be easy to offer an INTprivate <-> EXTprivate copy function. That would not turn Locus into a file manager, but rather help the poor users to manage their capacity more easily. Fully compliant with crazy Google :-)

@tapio
I agree re. the wodring with unclear semantics.
When it comes to backup folder: on my test device I have the Locus main folder on internal SD, so I put the backup folder on external SD. Migration worked like a charm.

I fully agree that the maps folder needs to have the same flexibility as the mapsVector one.
And same applies to the export folder!

English is OK. Translation error ...

The naming duplicate is in German.
My English Locus install on S10 I will not touch for now.

TXs Menion.
File browser thing clear, and also seen it in practise now.
PC connect to Windows is also easy as you write and successfully tested.

The last two topics relate to settings - maps - standard folders - file manager.

After migration to private internal two new entries appeared under "App Data Transfer"
There is the naming problem.
And the option of Locus writing to root folder. Grandfathering of existing install?

App Data Transfer: there are two entries with the same title doing opposite things. Not good.

But how on earth can Locus WRITE to the root folder? Is that the grandfathering of an existing installation?

Would this go away after a re-install?

TXs, Wolfgan. Was late last night, and I mistook external for internal.
So, while this is nice, it does not help offloading large non-vector maps to external.

@Menion: can you PLEASE do the same thing that you did for mapsVector also for maps?
Also it seems that you look for mapsVector on internal although it is configured to external SD.

So, writing to the configured location, but always reading from both locations is the most powerful approach. And easy to implement ...

Thank you.