Messages

Nice, but parsing of OLC still lacking ("HGVV+465, Lünen" not working).

I think this is the root cause for this: Autobahn parking fails to share to Locus, Locus finds another parking in the town. Umlaut issue?
👉 https://maps.app.goo.gl/FXxfijJBTn62PGDV7

Still something power management related on Android side. Vendor dependent.

Not my experience. In case of Android crash/reboot I never lost a track and Locus continued recording the restored track. Happened to me ~3 times over the years.

Will check it. Needs to be part of OAM, needs an svg icon (and me on PC) etc.

v1.2.7

• Menu reorganisation
• POI are included in basic profile
• Hide (place:locality) if suburbs are hidden
• Color correction: primary_link, tertiary roads.
• Access restriction indicators on roads were missing, fixed.

OLC Search (4.18.2) failure:

HGVV+465, Lünen - not found.
should be
51.592763,7.543109

For some reason, I don't like the presentation of the new searches results.

Would you please elaborate a little?

a) I mean on map
b) Eg search a category like "parking". A lot of other POI are displayed. Didn't ask for those
c) Tap beside poi, on map - under some circumstances the results stay on map, sometimes they disappear. Need to go into search again.

So your question is how to import tracks? (Your database says 0/0).

r/tasker ist, wo Du suchen musst.
https://www.reddit.com/r/tasker/comments/vqei62/unable_t_import_a_profile/?utm_source=share&utm_medium=android_app&utm_name=androidcss&utm_term=1&utm_content=2

Same what I do. Send position (plus retry if necessary), gmaps link and address on a regular basis, when hiking. Address lookup needs internet but failure is treated and won't stop task. Also I allow retrieval of position via incoming sms. Yes, SMS because it's the most robust system we can use.

PS. No love for "Multiple Variables Set"? 😀 I think %err is unreliable in case of SMS (that was my experience), I use additional "SMS Success"/"SMS failure" profiles (triggers). But more complexity then.

Livetracking nutze ich nicht. Wenn es per Intent nicht steuerbar ist, muss man das Menion sagen. Wenn das Plugin scheitert, Falco auf Github melden (er wurde aber lange nicht gesehen).

Intentsteuerung funktioniert allgemein sehr gut. Ich lasse bspw. alle meine Anwesenheiten als Track autom. aufzeichnen, seitdem Smartphone +Akku das erlauben.

Ja, das kann zunächst sehr verwirrend sein. Mit Tasker geht alles, was Du vorhast.

Ich habe Dir Beispiel-Intents für Tasker hochgeladen. Du musst da nur den Befehl unter "Extra" entsprechend Deiner Wünsche anpassen:

https://taskernet.com/shares/?user=AS35m8kdDIMDeveQcQfRglam%2Fah1mTW%2FWcg05FZ39c0i1q%2F77iY3E7cIwxCkXqJTaTA%3D&id=Task%3AExampleIntentsLocus

Hier findest Du alle Befehle:

https://github.com/asamm/locus-api/wiki/Action-tasks-(Broadcasts)

Diese Steuerung ist der direkte Weg, sollte man bevorzugen (wg. Minimierung der Abhängigkeiten). Das Tasker-Addon kann das auch, macht bzgl. o. g. Befehle auch nichts anderes, stellt nur ein bisschen UI davor.

Soviel zu Befehlen, die man an LM sendet, und dann macht es irgendwas.

Das Tasker-Addon ist alternativlos wenn es um die Abfrage von Werten geht (bspw aktuelles Kartenzentrum abfragen) - es gibt keine andere Möglichkeit für uns, da sonst ranzukommen.

"Verlassen des Hauses" lässt sich im Prinzip leicht erkennen (WLAN verlassen z. B.) - aber es gibt so viele Randprobleme und Ausnahmen, da musste selber durch. Man muss Toleranzen einbauen. Mein Screenshot lässt das erahnen. Kann ein bißchen Horror werden. Triggerprobleme, zu oft, zu selten...

I do not want so that important users (geeks) are annoyed and jump off.

Nobody jumps off or should jump off just because of search. And there's no alternative to LM anyway. People shouldn't forget what we have.
Personally I don't care about the new search too much. For some reason, I don't like the presentation of the new searches results.
Offline POI handling needs improvement, Menion knows that.
I either use Gmaps->Locus or do Nominatim based search, Tasker->Locus.

This is not practical. So the user must first set the zoom level and can only then search.

No I'm saying it could use the maps current zoom level (and map position) for its priority decisions. But well, they may already do that.

Maybe zoom level as an indicator of users scope wish? Zoom level low: User likely wants to find "New York City" in the US. ZL high: wants to find the local "NYC brothel".