Messages

I'm really shocked that none of the geo app providers joined forces and went up in arms to wake up Google.
The limitations are a disaster, as explained many times.

As far as I understand an existing Locus install (BEWARE OF UPDATES!) will continue to use full power of the existing app, right?

Was die Einstellungen betrifft: ich konnte Menion vor längerer Zeit überzeugen eine Suchfunktion einzubauen: gehe in den Einstellungen auf die Suchlupe und gib (kurzes) Wort ein.
Manchmal hilft es.

Hast Du zufällig den Track mitschreiben lassen? Und "springt" der dann auch mit einer langen geraden Linie zu einer älteren Position?
Dann kann eine Android-Batterie-Optimierung schuld sein. Je nach Hersteller und Android-Version gibt es da verschiedene Einstellungen. Meist kann man auszuwählende Apps von der "Optimierung" ausnehmen.
Bei Huawei z.B. hat es nur bedingt geholfen. Bei meinen Galaxies hatte ich bei o.g. Ausnahme-Einstellung keine Probleme mehr.

Map center move Was the quicker way  ;-)

But there is sharing with other apps, too!
Until now ...

All geo App developers should unite and kickk Google's ass.
Now all of them - and their customers and users are suffering separately.

Unacceptable.

Hi Menion,
I conclude from earlier remarks that for LM4 and LMP and Locus GIS - all from your company - you would have to triple the amount of data. Maps, SRTM, everything.
And maps (both vector and raster) are currently shared between completely different apps.
In the future multiplying the amount of data???
Cheers
Michael

Just tried your scenario - went to Sierra Leone, loaded the OAM from there, then pushed the GPS center button. Germany OAM was loaded automatically.
I just looked at my resp. settings: Maps -> Offline Maps -> Automatic map loading
It is enbaled for LoMpas and other vector maps.
What about your setting?

Make it a proposal at https://help.locusmap.eu/topics

Enjoy the trip!

Menion, what will happen if people on Android do not update Locus? Will the existing folder access continue to work?

The restrictions you mention are simply not acceptable.

Maybe this one  (see attached) is a good start?
I did not try, but remembered the other thread about this subject.

https://www.openandromaps.org/oam-forums/topic/einfaches-leeres-theme-fuer-v4-karten

Good luck and cheers
Michael

For OAM Christian uses different base settings for different parts of the world to exactly address the problem you are highlighting. The elements theme is the right counterpart for those areas of the world.
Give it a try.

Looking at Canada OSM data, there is also TONS of work to do for the OSM mappers :-)

If noone had ever tried the near impossible, we'd still climb on trees - without any maps :-)

And BTW: would your product FAMILY be able to use the stored maps across the board?
You have  LM4, LMP, and some GIS stuff, right?
Double or triple the maps for the same area - Google must be kidding to insist on such!

And sharing between multiple apps beyond is not an advanced user thing.

TXs for the additional details, Menion.

I think you have to take the bull by the horns head-on!

The whole scoped storage thing is for the Instagram world, only good enough for images and videos.

All other big data sets suffer by deadly performance issues.

So, to summarize your (and similar apps) scenario:
- huge data sets
- random access needed (database and alike)
- shared between different apps
Forgot something?

If I were Asamm, I would create a dummy geo app with request for MANAGE_EXTERNAL_STORAGE, with above justification. Hence no danger to Locus itself, just for the battle with Google.

Quote from : https://support.google.com/googleplay/android-developer/answer/10467955#zippy=%2Cexceptions

Google Play may provide a temporary exception to apps that do not qualify as permitted use designated above, when;

    Use of the permission enables the app's core functionality; and
    There is currently no alternative method to provide the core functionality; or

use of the privacy friendly alternatives (e.g., MediaStore API, or Storage Access Framework) has a substantially detrimental impact on the critical features of the app that are tied to the core functionality.

    The impact on user privacy is mitigated by security and privacy best practices

The developer must justify in their Console declaration why the Storage Access Framework or MediaStore API is not sufficient for their app's purpose.

You can fulfil all three conditions. And if Google finally comes up with an enhanced framework that goes beyond Instagram (and alike) use cases, such exception can be ceeded. But not before!

Good luck and kind regards
Michael