Messages

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.

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 ...

Nach einem ausführlichen Beta-Test wurde gestern die neue Locus-4-Version in Google PlayStore veröffentlicht, die es erlaubt Locus auf /Android/media zu beheimaten.
Damit kannst Du mit TC, x-plore und anderen fähigen Dateimanagern noch zugreifen (wobei ich dies mit Android 14 noch nicht selbst testen konnte, aber mit Android 13, das ja weitere Restriktionen einführte selbst im Vergleich zum schon bescheuerten Android 11, was die vermeintliche "Sicherheit" betrifft).

For Android there is still the option to have Google results via API, free of charge (as per Menion, last year's discussion).

But it is a decision by the Asammm search folks to not integrate that. It would be easy to merge those  results or keep this Google search as an additional option in your list, druki.

The earlier argument that Android and iOS should have same features is not valid anyways and a pretty bad excuse. Because the feature set for iOS will be smaller, for many years to come.

A solid search feature incl. Google search API is simply a question of will, not effort or anything else, I think.

I triggered this feature years ago and have been happy ever since, although I have 1000s of tracks in the database. You see about 10 tracks in the result list, and they are properly ordered by increasing distance.
So, what's the problem, as the distance is indicated in red in the second results line.

Ich habe diese Funktion vor Jahren angestoßen und bin seitdem sehr zufrieden damit, obwohl ich Tausende von Tracks in der Datenbank habe. In der Ergebnisliste werden etwa 10 Titel angezeigt, und sie sind korrekt nach zunehmender Entfernung geordnet. Wo also ist das Problem, insbesondere da die Entfernung in rot in der zweiten Zeile angegeben wird.

Wow, Locus root directory on Android/media!
That solves the Locus photo access, too, I suppose.

Seems so:
https://docs.locusmap.eu/doku.php?id=manual:advanced:customization:online_maps

The URL string has to have x/y (lon/lat) included. Are they in the right place (order)?

Arghhhh, meine Formulierung in Post #16 war etwas mehrdeutig. Mein Thema waren die Dateinamen und Umrisse der jeweiligen Karten, nicht deren Karten- oder POI-Inhalte für die abgedeckten Flächen!
D.h. es gibt nicht für jede OAM-Karte eine LoMap mit gleichem (Außen-) Zuschnitt; und umgekehrt. Für die meisten aber sehr wohl.

If there is a recovery possible or not totally depends on the backup strategy you employed over the years:
- if you had set up the Locus backup to Google Drive, you are fine
- if you had the backup to another folder on the old Pixel and copied manually (does not sound like that, though), you'd be fine as well
- if you have LM 4 Gold with tracks and points replicated into the Locus remote storage, you'd be fine, too (but would have noticed on the new device, I suppose, as Locus should download the stuff)
- if you have another third party cloud feed for tracks (and maybe points), there is a way at least.
The POI and the track databases reside in /Android/data/menion.android.locus/files/Locus/data/database folder.
If you should have zip backup files from Locus, you can re-import them from Locus.
If you have only gpx or kml files from somewhere, you can import them into Locus and re-populate its database.
Other than above, I fear your tracks would be history.

Any more thoughts from a Locus export colleague?

Das sind die Neuigkeiten:
- Der OAM-Hintergrund für ZL 8 und höher ist jetzt aus Christians Dezember-2023-Vektorkarten generiert (ausgenommen der Nahe Osten, für den die OSM-Vandalismus-Reparatur noch immer andauert; Status ist dort Sept. 2023).
- In Zoom-Level 5 bis 7 werden Ländergrenzen in rot eingezeichnet und Regionen (in Russland), Teilstaaten (in USA) und Provinzen (in Brasilien und Kanada) in violett.
-Die Anzeige von Ortschaften wurde von Stand 2021 auf den aktuellen Stand gebracht nach einigen Korrekturen und Aufräumarbeiten. Falls dabei etwas schiefging, bitte ich um Nachricht. Danke.

These are the news:
- The OAM background from ZL 8 and up now is rendered from the December 2023 edition of Christian's OAM vector maps (except Near East, for which the OSM vandalism repair is still ongoing - status there is Sept. 2023).
- In ZL 5 to 7 country borders are shown in red, while regions (in Russia), states (in US) and provinces - Settlement rendering was updated from 2021 state uo current, after a number of corrections and cleanups. If you spot something that went wrong, pls. let me know. Thank you.

While this is good news, it does not resolve the dilemma: if you want to have all your track history with you (without sharing it with the world in some online service), you have to swallow enpormous backups in every cycle.
That is something only Menion can fix, right?

Mine has exceeded 1 GB, a real challenge, for backups e.g. and space in general.
I had proposed long time ago to support a second "archive" track DB, that may reside on ext. SD e.g. and will be part of searches, but not part of backups (you do that once to an offline device like OTG USB drive or a PC).
That mechanics should of course include the pruning of the original DB (your point in the post).

PS: der Backup-Folder sollte (im Betrieb) niemals in der privaten Struktur unter /Android/data/... liegen. Denn bei einer eventuellen De-Installation wird der seitens Android zerstört.
Beim S22 gibt es keine externe SD mehr, aber die Backups funktionieren auch mit Foldern auf der oberen Ebene (haben also nicht die Restriktion auf /Android/data).