Menu

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

#61
Versionsinformationen 202406-1.0

    Der OAM-Hintergrund für ZL 8 und höher ist jetzt aus Christians Mai/Juni-2024-Vektorkarten generiert (inkl. Naher Osten - die OSM-Vandalismus-Reparatur scheint abgeschlossen).

    In weniger dicht besiedelten Gebieten hat nicht jeder - selbst signifikanter - Gipfel einen Namen, und selbst falls er einen haben sollte, ist solch ein Gipfel noch lange nicht in OSM. Auf Basis des 30m-Copernicus-DEMs habe ich für alle Kontinente außer der Antarktis Gipfel identifiziert mit Dominanz 100 km bzw. 200 km. Falls einer dieser Gipfel keinen in OSM bekannten in seiner Nähe hat, wird er in diesen neuen Weltkarten als "Loc.HP" (für 200 km Dominanz) bzw. als "loc.HP" (für 100 km Dominanz) angezeigt, jeweils mit der Koordinate (2 Dezimale) und seiner Höhe. Es gibt davon gut 1000 Stück.
    Falls also ein Nutzer einen Namen für solch einen "local high point" kennen sollte, sei sie oder er aufgerufen das in der OSM-Datenbank einzutragen, damit ich den (virtuellen) Hilfsgipfel durch den echten OSM-Gipfel ersetzen kann im nächsten Release der Karten. Ich erwarte, dass in den Weiten von Nord-Kanada, Alaska und Sibirien sowie den tropischen Regenwäldern viele davon namenlos bleiben werden. Aber in Relation hoch und isoliert sind sie trotzdem 🙂
#62
Hast Du den automatischen  Export  aktiviert?
Der schreibt für jeden Track die zugehörige gpx-Datei in das export-Verzeichnis von Locus.

PS: es ist auch (für die Zukunft) ratsam, tägliche Backups zu konfigurieren (gerade wenn mensch unterwegs ist). Locus überschreibt dann automatisch immer die ältesten.
#63
Interesting case indeed. Root cause of differences are the two fundamentally different data sources
- track recording, regardless if by Locus, any other app or Garmin is they rely on GPS signals from satellites. Reflections, blockages, spoofing and alike impact those, by physical effects. In particular the elevation data is not too reliable. You can see horizontal and vertical fluctuations when you look at the graph.
- update elevation on the other hand gets its data from DEM data files. Typically 3" (90m) resolution, but Sonny's data has 1" (30m) resolution for most of Europe. Typically an "update elevation" will reduce the flucuations, hence reduce the gain/loss totals rather than inflating them.
I'd look at the graphs to see if the updates curve as visual anomalies.
And I'd check if using Sonny's 1" data gives better results.
Cheers
Michael
#64
Hi selfishchalk,
you should report this to the help desk rather than the form.
They will guide you to take detail logs e.g. to look "under the hood".
20-30%/h is EXTREME (I never read of such in my Locus history since 2012), so there should be a "smoking gun".
Cheers
Michael
#65
I just tested with a Discovery_Walking_Guides map and can tell you that you can be lucky with your view.
Above map has a solid white border, all legends - like a scan of a paper map. Which definitely is not created by Locus, but rather integral part of that map itself.
Can you test your case by displaying one of your maps exclusively, alone (i.e. no overlay mechanics of any kind) and check how it looks like at its border.
If there is such border like in your screenshot, then it would smell like my experience with DWG maps - only "nicer" ...
#66
Die Beschwerdeadresse ist: Google Inc, Mountainview. Seit Android 11 sind die was Dateizugriff betrifft auf einem Paranoia-Trip.
Aber es gibt jetzt einen einfachen Weg: schaffe Deine Rasterkarten nach /Android/media(!!!)/menion.android.locus.pro/maps
Auch das Nachbarverzeichnis mapsVector richtet Locus Pro beim ersten Start ein.
Solche Strukturen gibt es auf der internen und - falls existent - der externen SD. Locus liest diese Ordner bei jedem Start.
Also einfach Deine Sammlungen per Dateimanager hinkopieren (x-plore, Solid Explorer und TC können das auf jeden Fall).
#67
providers.xml im Unterverzeichnis mapsOnline/custom
#69
- map shading?
- dynamic elevation?
#70
That's a brutal one ...
I very rarely had a crash related to memory in more than 10 years, but blank popup menues and screens and alike have been a regular issue.
Hence I suspect there might be more than one leak OR one root cause leak that develops towards different, more or less serious consequences, based on still unknown conditions.
Good luck!!
Cheers
Michael
#71
TXs, Menion. After deleting this 1.1 GB sync.db and adding a test waypoint and later deleting that one again, my sync.db is 4kB. And the operation is correctly showing "uploading" or so in the first place.
#72
I did not dispute that - I thought and wrote about a practical chance to ease pain a bit for the time being.
Analysis and fix has to be on Locus side for sure.
#73
I have the same impression, although from another scenario. Locus running in the background as a service basically 7 x 24 (even when not out of the house), over time it will eat up memory. This makes some popup menus pure white. Most of the cases it recovers some time later, but sometimes I need to restart Locus to get it back "on track".
As memory leaks are one of the hardest things to catch in development, I recommend to switch off shading while traveling. For planning I understand shading is very helpful. While "executing" it's not, for sure not when you go 100 mph + :-)))
Anyway, just my 2c, trying to "buy time" until resolution, which might take quite some time.
Cheers
Michael

PS: I am not claiming that shading IS the culprit, but for sure it is a load for battery and memory alike, hence low hanging fruit - without guarantees, though ...
#74
@Menion: if doubling the tracks.db (a copy comes as sync.db) shouold be a common problem (see my help desk post), this would need a fix prior to publishing, I suppose.
#75
Troubles & Questions / Re: android 13 no access
April 02, 2024, 11:27:05
Since Android 11 Google has been infested with Apple's craziness about restricting user's ownership of their own devices. And it got worse release after release.
Total Commander and x-plore found loopholes to a certain extent - up to Android 12 (incl.).
Both fail with Android 13, though (at least I could not make them access the App private folders under /Android/data).
HOWEVER, since latest release Menion managed to place Locus root under /Android/media!
That has the benefit that apps like TC or x-plore can read and write from/to it - without AfA privileges.
And Locus now offers the convenient option to relocate the existing content from /Android/data to /Android/media.
BUT: a de-install may still remove also this folder (I have not tested the "keep data" option when de-installing, though. That might help - or not.