Messages

[völlig überraschend]

Hallo,

ein verspätetes Danke für die Antwort und ich habe den Fehler gefunden ... und er lag völlig überraschend bei mir. 

Erläuterung für Leute, die evtl. auch mal auf dieses Problem stoßen.

Wenn ich ein Preset erstelle, dann kann ich auswählen, welche Voreinstellungen ich ändern möchte, z. B. beim Radfahren "Automatischer Zoom" und diesen dann durch einen Haken aktivieren.

Beim Wandern möchte ich aber eben nicht "Automatischer Zoom" und habe das deshalb in meinem Preset auch gar nicht ausgewählt und konfiguriert in dem Glauben, dass eine Nicht-Auswahl einem Deaktivieren von "Automatischer Zoom" entspricht.

Dem ist aber nicht so.
Wenn ich eine Einstellung nicht auswähle, dann bedeutet das offensichtlich nur, dass die vorige Einstellung einfach übernommen wird.

Deshalb muss ich beispielsweise beim Wandern ebenfalls "Automatischer Zoom" in mein Preset aufnehmen, aber den Haken zur Aktivierung weglassen, es also quasi aktiv deaktivieren. 

Gruß
mire2

[Tip]

Tip: best zoom system by one finger ... tap > up tap > tap and hold ... now swipe with your finger up and down.

You mean, generally? It's not in Locus, right?

@Freischneider: But less (e)MTBs in the woods would be even better 😁😁👻 Where I was alone 10 years ago, say, on a 15% up slope,  today a family, with their fat uncle and 100 year old granddad overtake me. Nah seriously, it is as it is, we gotta make the best of it. Even though I don't like that development.

There seems to be some misunderstanding or I'm too stupid to understand this cyclic communication.

So again (summary)
- I'm aware that there is a problem with brightness on some (not confirmed on all!) Samsung devices
- I also think that on 90% it is caused by my code in the app
- I have device for test with this problem
- I've spent 10+ hours by searching and testing ... no effect
- I've spent a lot of time comparing Locus Map Pro and Locus Map 4 code that differ and that may have effect ... no discovery
- You may send me any devices you want, you may pay me a million, but I currently DO NOT SEE ANY OTHER OPTION TO TEST, I'm currently out of ideas!
- I'm not stupid enough to let satisfied paying users leave because of any issue in the app, but again, I simply DO NOT SEE ANYTHING TO DO NOW!

Sorry.

Ok, hat sich erledigt. Ich habe die Einstellung Auto-Zoom deaktiviert, Locus neu gestartet und wieder aktiviert. Jetzt geht alles wie immer.

Well the OS is complex, unfortunate problems, where sometimes you find a solution just because you hear of another dev who struggled with the same and luckily found an answer... or his users... it happens. Unfortunate, but this is reality. And please compare with the big company realities. Google. They never answer, they have no changelogs mostly, I wouldn't ever waste time on reporting them anything. Apple. They give you tools which aren't open to do what you need. You have to need what they offer... and look no further.
Let's keep our eyes and ears open, there is no doubt Asamm does the same.

[@Radim V]

Hello eldron, freischneider

existing offline LoPoints solution is very old and we are aware, it needs a bigger update. We have anyway decided to set order of priorities as
1) online LoPoints service (mostly done, working on better search, support for categories)
2) integration of extra content like Wikipedia, photos, optionally comments
3) big update of the offline solution

So, offline LoPoints should work, but if possible, we suggest using online LoPoints solution (available for free in LM4) that offer already a lot more points with a clever grouping and visibility based on the current zoom level. And data usage is really minimal ...

Maybe @Radim V may add few notes as the main guy behind our new LoPoints system if wants.

---

And your problems. I see mainly a problem in your point 3) as this should really not happen. I'll be using the offline version a little more and watch it as well. Thanks.

Hey, I may be weird or annoying, but this very small thing always confuses me...

I am expecting "Select all" on top - anyone else? It is the most likely thing to do. "Deselect all" is probably rarely or never used...

And in point screen it is at second place, in tracks on third...

Minor, I know 😁

Ich habe die waagerechte Ausrichtung der Schrift bisher auch nicht vermisst.

Das Problem sehe ich darin, dass das Display jetzt schon so wenig Platz hat. Schrift zu klein und man kann nichts lesen oder Schrift zu groß und es wird zu viel verdeckt.

Aber im Augenblick liegt die Schrift zumindest häufig an ungenutzer Stelle, z.B. in Straßen.

Wenn die Schrift quer zur Straße wäre, dann würde die Schrift vermutlich noch mehr Kartenbereiche überdecken und die Übersicht nicht gerade fördern.

Für diesen Fall drehe ich die Karte lieber kurz zurück.
Aber die Anforderungen sind ja auch nicht bei jedem Nutzer gleich.

MIUI offers the option of hiding the navigation bar for certain apps. But Locus does not react to this setting.

I suggest to not use those specialties as this might bring nightmares to Menion to deal with all those gimmicks with potential misbehaviours, cornercases, whatever..

Nun, gesagt, getan. Habe die aktuelle DB gesichert, das letzte Backup eingespielt, alle Tracks aus dem LAUF-Ordner exportiert (in einem Rutsch), danach das erste Backup wieder eingespielt und dort die LAUF-Tracks wieder importiert.
Hat alles ohne Probleme gut funktioniert.

Nochmals Danke

In den Einstellungen von Locus kann man sich die Standard Verzeichnisse ansehen. Wenn ein Standard Verzeichnis auf einen nicht existierenden Ordner führt, dann meckert Locus.

Also schau nach, in welches Verzeichnis die Backups gespeichert werden.

Wenn Du ein brauchbares Backup gefunden hast, dann würde ich wie folgt vorgehen.

1.) Jetzt ein aktuelles Backup machen. Mit einer Bezeichnung, die Du auch wieder findest.
2.) Spiele ein altes Backup mit den verlorenen Tracks ein.
3.) Gehe auf den Ordner Deiner Lauf Tracks und exportiere die Tracks. Wenn ich mich richtig erinnere, dann kann man mehrere Tracks markieren und in eine Datei schreiben.
4.) Spiele Dein Backup aus 1.) zurück.
5.) Erstelle wieder einen Ordner Deiner Laufträcks und importiere die gerade exportieren Tracks aus 3.)

Ah, very good idea, thanks! Just keep on mind, that it is more a "device ID"  ... every device has its own ID. Maybe incorrectly, I started to call it "user ID".

[Beta version 4.3.2.3]

New Beta version 4.3.2.3 just uploaded.

Most of the problems should be fixed. At least the random stuck when panning with the map. @fresichneider reported that full-screen still cause problems. I'm unable to find or simulate any problem, stupid . Anyway, I'll keep looking, but full-screen on Android 9+ is something I would really like to remove completely ...

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
Michael

4.2.1.1: run LM4 > opened track recording panel totally blank

@menion - further testing: all foreground apps killed, phone not restarted during testing, single 6km walk with new track started each ~500m, exit/ restart LM4 if track recording panel is blank. Nothing is 100% repeatable, just more/ less likelihood of blank panel occurring. Track recording is auto-started.

• new observation/ not previously reported: when the track recording panel is blank, the map content panel is 100% also blank
• if track recording panel is not tapped immediately after start of recording there is more likelihood of blank panel occurring after further 500m
• so reverse, if track recording panel is tapped immediately after start of recording there is far less likelihood of blank panel occurring after further 500m
• generally when the recording is saved then viewed in the list, the track is duplicated
• the most recent track(s) remain visible (Eye icon) while for the older tracks something is turned off visibility
• the #visible tracks in the folder is displayed as 0 even though some are visible (screen cap)
• database corruption?
• One time the panel was OK, then 30s later on next tap blank. But another time all OK for 5 minutes.

I can upload the database but it is very large 300MB.