Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - michaelbechtold

#466
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.
#467
Other features / Re: Android 11+, changes
December 03, 2021, 15:51:07
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.
#468
PS: the external SD location for the export directory for the GPX would be important, too.
In particular for silver and free.
#469
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.
#470
@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 :-)
#471
@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!
#472
Other features / Re: Android 11+, changes
December 03, 2021, 10:41:28
English is OK. Translation error ...
#473
Other features / Re: Android 11+, changes
December 03, 2021, 10:40:07
The naming duplicate is in German.
My English Locus install on S10 I will not touch for now.
#474
Other features / Re: Android 11+, changes
December 03, 2021, 10:37:52
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?
#475
Other features / Re: Android 11+, changes
December 03, 2021, 09:30:04
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?
#476
Other features / Re: Android 11+, changes
December 03, 2021, 09:21:51
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.
#477
Other features / Re: Android 11+, changes
December 02, 2021, 23:37:58
Update: Test from PC

From a W10 PC I could even write to external SD private folders. Puuuuhhhh.
That allows some room to maneuver for quite a number of people.

Still a shame on Google's part. Arrogant, not thinking, not listening, not trustworthy on the technical side either.
#478
Other features / Re: Android 11+, changes
December 02, 2021, 23:09:05
Update: Total Commander allows WRITING into the INTERNAL SD private folder (hence more powerful than Solid Explorer or x-plore - interesting).

However: this is was the TC wizzard also posts:

ghisler(Author) ยป 2021-06-20, 06:33 UTC
Unfortunately as I already wrote:

    Note that Android/data on the external SD card cannot be accessed with any method.

I have tried the tricks to pass the correct path to the Android file picker, but it doesn't want to go there. So even the Android files app cannot access this folder. The only way to access it would be to "eject" the card via settings, take it out of the phone, put it in a card reader, and then access it from a PC or via OTG adapter from the phone.

We need someone who can beat the sh.. out of these Google so called Android architects. Narrow minded morons they are.
#479
Other features / Re: Android 11+, changes
December 02, 2021, 22:48:28
Definitely long times, hence my request to put a warning into the documentation.

But things get worse than that:
- also connection to linux via file system integration (Nautilus and alike) stop at the /Android/data/.../Locus folder, which is shown empty, although it is not.
- trying to migrate a huge SRTM folder makes Locus die after quite some time.

Has someone tried to use adb file system access to those private folders?

If the latter does not fly, dire times are ahead.
As long as Locus does not provide 1" resolution DEM files, there will be no way - that I know - to make Locus work with better DEMs than Locus download provides.
Also it would be bye-bye to side loading other map files than LoMaps. You could only use map sources that provide Locus-Actions to install with the help of Locus itself.

For 1"-SRTM Menion would need to provide some download feature for Sonny's DEM data e.g. With wild card selection.

Someone has smarter ideas to overcome those limitations?

As of now (late 2021-12-02) today's findings mean: stay away from the latest Locus version for now.
And NEVER EVER deinstall the current version.
#480
Other features / Re: Android 11+, changes
December 02, 2021, 21:15:07
@Menion:
I could not wait until next week because I am so curious ...
So I started trying, not on my S10 for daily use, but on the Tab S6 light (64 GB total internal space, large external SD) and found some essential problems.
My plan was to use the private section of internal SD (/Android/data/menion/...) as the main Locus location, then set the external SD for mapsVector and SRTM.
What happens?
1 long start - question: do or postpone
2 offers move
3 LMP loss of access warning
4 selection private - long pause 3 GB free - not enough - cancel
See attached for the situation: need for 1 GB (see external SD option), 3 GB free on internal SD.
Why is that? Most probably because of the SRTM and mapsVector that sit on external SD and require 75 GB in total. So I should have unchecked the two choices, right?

Which brings me to an overall judgement:
1) the steps and explainations are quite OK, but
2) it lacks overview for the user and
3) a plan

And there is a good chance that a user has ONE view of the storage reality, while Locus has another. Recipe for disaster, pain and discussions.

Hence I propose you do not offer the migration immediately, but produce a full storage picture how Locus sees it.
All the elements, with their sizes, and the options how and where to move them. And send this as a mail (share ...)
Something like:

Current Locus storage layout
=======================
Locus main: internalSD/Locus 1 .5 GB
Locus mapsVector: externalSD/LocusMaps/mapsVector 20 GB
Locus mapsVector: externalSD/LocusMaps/SRTM 55 GB

Internal SD capacity total/free: 64 GB / 3 GB
External SD capacity total/free: 256 GB / 151 GB

Next: what should a non-IT person do with a non-trivial situation?
1) understand the picture
2) understand the options

Can people derive that themselves? Hardly, hence they need advise.

A text that explains the options given various scenarios should be added to above report:
1) the total Locus storage fits fully into internalSD: do whatever you want, but internal preferred for data safety and performance reasons
2) current data on externalSD does not fit into internalSD: ...
3) ...
some homework here for all potential cases.

My setup above would need the following actions:
1) /Locus goes to internalSD
2) AT THE SAME TIME (!!!) current SRTM and mapsVector need a choice for their final target (I know you could uncheck both and doe manual stuff later, but that is not good, because it leaves a number of people stranded, in particular as the file managers fail so far)

Also: give warnings about long wait times for steps that take long, and tell users to click "Wait", not abort. Some of the steps 1-4 take unexpectedly long. I trust for a good reason, but people may wonder ...

So far my 2c

Cheers
Michael