Messages

For displaying realistic values in the bottom bar "Include navigation commands" has to be checked.

Someone else asked for it, I want to ask again.

The options of themes are not in reach, too deeply nested. WThey deserve to be easy to reach, so that we can easily change them.

The idea was to include Longtap on the theme button, which would instantly jump into theme options. Or maybe vice versa would make sense.

See screenshot.

Settings, Navigation, Appearance - keine Ahnung bzgl. LM3

In other words, we suggest to all German speaking testers to test again as search results may or may not behave quite a lot of differently for you now.

First tests give good results now, great.
I noticed it zooms to the first result. This should not be done by Locus. As a user I lose the big picture, I don't know the place of zoom and want to decide, what's having my interest. So maybe first result should not initially be selected?

Map is on Dortmund, Nordrhein-Westfalen, Germany. GPS off, device located in the area.

I search for "Halde", those are artificial hills, results of former coal mining. There are quite a few in this federal state, they have "Halde" in their osm name, usually.

Now after pressing enter it shows some inappropriate results. In the south of Germany.

https://youtube.com/shorts/fhv1RJWkurw?feature=share

Hi Andrey, I created a fork of it, I hope this is OK. But still I'm a bit clueless about Github though, wasn't even sure if forking is the right thing to do.

I have some different preferences. Tamed peaks a bit, gave weight to city/town/village/neighborhood names, also to parking/shelters/picnic_sites/viewpoints.

Wanted to have friendlier greens, it's a difficult affair, probably due to partial transparency and layering. What I wanted to achieve is what I now have in ZL14+. But lower ZL are different. Didn't find the issue yet.

Code: https://github.com/tortuosit/oam_theme_tapiola
Release: https://github.com/tortuosit/oam_theme_tapiola/releases/tag/Theme

Ach so, LM3, da kann ich nicht gut mitreden. Viel Erfolg, im Helpdesk ist ja schon eine Antwort.

When entering street names, some kind of auto completion is needed. If we know street and no. of house it's cumbersome to enter.

Yes it's tragic, search system will be compared with Google Maps 😁

Also I was thinking it's not perfect to add every searched item to the history entries. A more user organised approach is missing.

Hallo Kodela, vielleicht liegt ja ein Bug vor, was eine Neuverbindung angeht. GPS aktiv ausschalten kann m.E. nur "GPS Auto-Off". Was ist bei Dir (Screenshot) eingestellt?

Lief eine Track-Aufnahme, war das Routing aktiv (vmtl. ja, ergibt sich ja aus Deinem Posting)?

"GPS On for guidance" - ist ja durchaus denkbar, dass Menion dies nur beim Start des Routings prüft und GPS einschaltet, nicht aber während des Routings.

Theorie: GPS Auto-OFF hat GPS ausgeschaltet, als das Signal ungenau wurde. Danach hat keine Funktion es mehr eingeschaltet.

(8.) if you are zoomed enough and all points from the selected category are already displayed, we show also points from another categories. There is the same solution on web.

But I didn't ask Locus to show something else... IMO that makes no sense in a search context.
And tapping those points (without without really knowing what they are) makes the search results disappear.

Speaking of "making sense" - sometimes the whole bottom window is just not useful. Of course depends on the results, but maybe you can add something useful, like distance, idk... Screenshot related.

Will you unify the offline LoPoints system as well at some point?

A problem: see screenshot, if I tap on the parking icons on map one by one, then accidentally miss one and tap beside it, the search is gone.

Oh, I notice a disadvantage: there is no possibility to browse POI categories hierarchically.

If I pick a category like "Shelter", it displays other categories like peaks, as dots. But I didn't ask for those. Their color permanently changes while moving map.

Man kann übrigens die beiden tracks*-Dateien aus /storage/emulated/0/Android/data/menion.android.locus/files/Locus/data/database/
rausnehmen, Locus legt dann beim Start eine neue, leere Trackdatenbank an.

Wenn es also dann durchgestartet ist, kann man wieder Backups einspielen, Importe machen etc.

Ich würde ein Backup von vor der Operation einspielen

Locus startet ja nicht durch. Da ich auch von einer kaputten Datenbank ausgehe, würde ich diese gezielt durch eine aus dem Backup ersetzen.

@zobo. Backups sind in etwa hier: /storage/emulated/0/Android/data/menion.android.locus/files/Locus/backup
Darin siehe zip-Dateien, in der zip ist die data/database/tracks.db von Interesse.

Und hier liegt die derzeit aktive Datenbank: /storage/emulated/0/Android/data/menion.android.locus/files/Locus/data/database/

Falls Hantieren mit Dateien nicht so Dein Ding ist, lasse Dir besser im Locus Helpdesk helfen.
 

Was soll das?

Ein Hinweis (den ich wieder löschte) darauf, dass ASAMM ein Unternehmen ist, das Ergebnisse erzeugt und kein 50-köpfiges Philosophie-, Diskussions- und Dokumentationsgremium hat. Menion ist sich des Preset-Systems sicher sehr bewusst. Es ist einfach gehalten - er hat auch gelegentlich darauf hingewiesen, dass das so bleiben soll.

Ich ahne, Du meinst es gut. Du bist aber unheimlich nervig.