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

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

The following users thanked this post: 0709, LocusUser#1, freischneider
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 :

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

The following users thanked this post: Andrew Heard
I found it as the second topic of the maps section in expert settings.
You can also go into settings top page and then search for "dual".
The following users thanked this post: CabrioTourer
PS: a sustainable support of the Locus team is easily manageable: they now offer LM4 via subscription.
I have both, LM Pro and LM4 installed and they share the maps (LoMaps plus OAM) as well as the track/points DB.
PPS: and the hiding works - "INTERNAL THEMES" - "Hike&Bike" - "Hiking Trails" - nice place near Mt. Rainier, WA :-)
The following users thanked this post: freischneider
Locus Map / Re: [APP] - version 4.3.+ ( 28. 7. 2021 )
September 21, 2021, 21:24:04
Trying the latest Beta today: the new track naming I consider a joke, sorry ;-)
Pls. bring back the time stamp naming, and if someone needs the location of the latest point in the default naming for their peace of mind - pls. add it AFTER the time stamp.
TXs for your understanding.
The following users thanked this post: freischneider
Danke für die Warnung, Joska.
Ich hatte damals alles durchgetestet, und es war OK, jetzt aber geht es auch bei mir weder mit LMP noch mit LM4. Der Pfad löst nicht mehr korrekt auf - ich muss mit Christian reden, was sich da geändert hat. Interessehalber.

Denn der Pfad der bei den funktionierenden händischen Downloads verwendet wird, geht auch in den Locus Actions.

Werde das jetzt ändern und hochladen.
The following users thanked this post: Joska

Hier die wesentlichen Neuerungen – Feedback willkommen:

Versionsinformationen 202108-1.0

Die Dichte von Siedlungsnamen ist jetzt (*) signifikant reduziert für Gebiete mit Namen in 2 Alphabeten (lateinisch plus kyrillisch, arabisch, chinesische, hindi, etc.) und hoher Siedlungsdichte.

Die Namen von Orten (nicht im Sinne von größeren Siedlungen) erscheinen jetzt (*) in Bereichen die siedlungsfrei sind, mit bräunlicher Umrandung. Mit dieser Ausgabe werden auch Farmen so dargestellt (kaum in Ost-China, Mitteleuropa etc., aber in Australien und im mittleren US-Westen, z.B.).

Die regionalen Addons zur ZL-10-Weltkarte mit einem transparenten obersten Zoomlevel für Locus werden aufgegeben. In Locus 4 gibt es den max. Re-Scale-Mechanismus, der diesen Overhead unnötig macht. In Locus 3 wird die oberste Ebene für 2 Zoom-Schritte vergrößert, bevor die Vektor-Karte ebenfalls sichtbar wird.

Auf Anregung von Sonny (Spezialist für DTM) bekommen die Weltkarten einen Präfix, der die Namen weniger kryptisch macht. Aus W1-10-J70.mbtiles wird z.B. OAM-World-1-10-J70.mbtiles. Für ein paar Ausgaben werde ich allerdings beide Namensschemata bereitstellen, um den Nutzern mehr Zeit zu geben die Einstellungen in ihren Apps anzupassen (wobei das Auslaufmodell als solches gekennzeichnet wird).

Korrektur der Staatszugehörigkeit von Agaléga Islands (SC -> MU).

(*) nun ja, schon seit April, aber undokumentiert
The following users thanked this post: freischneider

Here are the most relevant news – feedback welcome:

Release notes 202108-1.0

The density of settlement names has been reduced considerably for areas with names in two alphabets (latin plus cyrillic, arabic, chinese), hindi, etc.) and higher settlement density.

The names of places (not in the sense of settlements) now appear (*) in areas that are settlement-free, with a brownish border. With this edition, farms are also shown this way (hardly in Eastern China, Central Europe, etc., but in Australia and the US Midwest, e.g.).

The regional addons to the ZL-10 world map with a transparent top zoom level for Locus are dropped. In Locus 4 there is the max. re-scale mechanism which makes this overhead unnecessary. In Locus 3 the top level is zoomed in for 2 zoom steps before the vector map becomes visible as well.

At the suggestion of Sonny (specialist for DTM) the world maps get a prefix that makes the names less cryptic. For example, W1-10-J70.mbtiles becomes OAM-World-1-10-J70.mbtiles. However, for a few releases I will provide both naming schemes to give users more time to adjust the settings in their apps (with the discontinued model being marked as such).

Correction of the nationality of Agaléga Islands (SC -> MU).

(*) well, since April in fact, but undocumented
The following users thanked this post: T-mo, Andrew Heard, Viajero Perdido
Let's wait for Menion's final tests.
I fear the worst.
What I expect from Menion then is to allow read-only configuration for alternate srtm and mapVector, and of course adding read-only for extra vector maps and raster maps.
So people can at least populate those alternate via connection to PC or via ftp or alike.
Menion should also introduce something like "look at alternate srtm folder" (read-only), if not available, then find or supplement from/in private folder.
If he cannot fight Google head-on, then he must allow people to help themselves.
All stuff in private folders is unacceptable.

I will have a close look at what other geo apps are doing with Android 11 ...

Quote from: tapio on August 10, 2021, 22:30:54
Michael Bechthold, didn't read your whole text, but MapsVector and SRTM will be able to reside on the external SD?! I've set them up this way. On Android 10 that is.

Edit. Oh. To quote Menion "Everything in the private folder is the expected result ... start count with it. Deadly?"

Oh, that would hit hard. SRTM+MapsVector is currently 30+ gig here.
The following users thanked this post: T-mo, Andrew Heard
Hi Wole,
definitely no need to lose faith, but rather look at the very details of the fact collection.

There is an impressive collection of Samsung MODELS that MAY suffer from the issue (you named them below).
But NOT ALL of the DEVICES of those models suffer the issue!

So, same Samsung model, but different behaviour - with the exact same software (as far we can tell - there is a lot of jungle beneath the surface and the app code of a smartphone).

And we can assume that the issue is not hitting the majority of the devices of those models. Otherwise there would be much more complaints. And believe me, if my Samsungs were affected, I would be loud and clear (Menion knows a bit of that :-)

Up to now, nobody knows what differentiates a device of the same model having the problem from one that does not suffer.

A typical strategy in IT for such situations is to revert to a safe ground. Which here can mean two things:
1) a factory reset: heavy impact to the user (and not yet done yet, if I screened all the thread pages correctly). Only realistic for devices not regularly used. Maybe someone has such.
After restart NOT apply Google recovery of ANY kind. ONLY install LMP and LM4 and then re-test.
2) an Android SETTINGS reset, which should be possible at least in newer Android releases on Samsung devices. To be accurate and take out assumptions as far as possible, backup the SETTINGS in LMP and LM4. Import settings of the other kind to LMP or LM4. Test. Then use the other settings backup for both, LMP and LM4. Test.

After 4 decades in IT and SW trouble shooting I learned to not believe in magic. Not regarding the root causes, nor for the remedy of issues. But that it can be tedious, lenghty, yet SYSTEMATIC work.

Good luck and cheers
The following users thanked this post: balloni55, Tapio, freischneider
It was NEVER a good idea to use Android/Data/menion..... - neither on internal nor external SD.
Only recently someone uninstalled Locus - without a current backup ...

I am using LMP and LM4 on A11 (Samsung flavor) without hassle.
But we have to see what the Google enforcement of the new API level (Sept. 2021) will bring.
The following users thanked this post: francisco
Willkommen an Bord!
Was Du suchst ist einfach:
Datenmanager - Tracks - "+" - Import
oder im Android-Dateimanager die GPS-Datei aufrufen und Locus als Handler wählen.
Danach sicherstellen, dass der Track auf sichtbar gestellt ist.

Android-GPS einschalten

Locus-GPS einschalten


Generell: oben rechts ist meist das Handbuch erreichbar (Web).
Und die Einstellungen haben eine Suchfunktion (Volltext)

Viel Spass!
The following users thanked this post: uenue
Zur POI-Suche: die LoPoints sind nur im Pärchen mit der Karte zu installieren, denn Locus erkennt sie so bei App-Start. Danach allerdings bis Du frei zu wählen. Die Automatik nimmt m.W. (ich nutze das praktisch nie, weil es Locus langsam macht) immer die zur aktuellen Vektorkarte gehörenden POIs (können auch von OAM stammen). Aber wenn Du direkt in die POI-Suche gehst, kannst Du oben frei den Datensatz wählen aus den installierten POI-DBs.
The following users thanked this post: Heinerich
Quote from: tapio on June 15, 2021, 11:19:48
Wenn hier jemand weiß, ob man den Zoomlevel definieren kann, ab dem Locus zur globalen Karte springt, wäre ich dankbar. Ich meine, da gab es eine Möglichkeit, ich fand es aber nicht mehr. Ich persönlich mag die Hike+Bike von Asamm ganz gerne, möchte aber, dass sie früher erscheint.

Diese Diskussion habe ich mit Menion seit Jahren, aber etwas verallgemeinert. Aktueller Stand der SW ist, dass man die Weltkarte auswählen muss mit dem gewünschten max. Zoom Level. Ich gönne mit die mit ZL 11 (9 GB), aber das ist eher mein privater Spleen :-) Es gibt sie bis ZL8, 9 und 10 ebenso. Und Ergänzungskarten für die Kontinente bis ZL 11.
The following users thanked this post: Tapio
PS: the world map up to level 10 (in 0709's example) is nearly 2 GB in download volume (zip) and more than 6 GB in storage size on your device. In case you have enough free space on your device, Locus will directly do the download and unzip and putting into the right place for you when you click the respective button on the OAM page. Download size may matter in the place you currently are. ZL8 world map has a decent size, and ZL 9 is somewhere in the middle.
The following users thanked this post: ziellosreisen