Messages

Exit Locus with or without pause does the job, as long as you keep the recording alive (do not touch the upper part of the Exit window!).
Just tested on LM3 and LM4.

V1.1 mit Christians OAM-Vektor-Karten vom Sep. 2023 als Hintergrund (ZL 8+) ist jetzt online, als direkte Downloads und als Torrents.

V1.1 with Christian's Sep. 2023 OAM vector maps as background (ZL 8+) is online now as direct downloads and torrents.

...
Until then, we didn't removed old offline address and POI searches. They are still there in its current old-school form. With those the app for sure would not be returning results from countries of which it hasn't downloaded map.

As a Computer Scientist and IT professional since more than 40 years I appreciate that your roadmap is havy lifting. But by the same token I can confirm that you and your search team completely fail re. rule #1: "Do not screw your customers!"
You are "proud" to not have removed offline POI and address search? Well, removing the last straw would have been complete suicide.
Keeping Google based search in its place as it worked for 10 years, alongside your new search, would have been professional. You would get feedback from the geeks who dare the new stuff, while offering propoer search results for all others, while you do your homework for step #2 and #3.
And if there should be pride and emotions in the way of doing that: both do not pay your bills. Be smart instead.
Cheers
Michael (from Radium Hot Springs)

I think it is time for a drastic correction of approach here: whatever you do for iOS should not screw the 100000s of users from whom you make your living.
As long as the new search function is not professional, give the Android users back the Google based search.
Equal functionality is not a valid argument against this request, as the iOS version will lack essentials for years to come anyway.
At least give the existing and fully functional Google based search as an option to your (Android) users, PLEASE!

Those are the changes:
- The OAM background from ZL 8 up now is rendered from the July 2023 edition of Christian's OAM vector maps (YES, OAM goes on - thank you, Christian!).
- Increased and earlier visibility of offshore energy and power sources for ZL 4 to 8, while reducing visibility of the land based installations for those low zoom levels.
Have a good time
Michael

Es gab eine Zeit da hat Locus die Themes für die Vektorkarten auch von SDs gelesen, falls so konfiguriert. Das war ab Android 11 eine Tragödie. Daraufhin hat Menion Locus befähigt die Themes als ZIP zu lesen. Dabei wird einmalig eine interne Kopie des extrahierten ZIPs in internen Speicher erzeugt. Das kann ein paar Sekunden dauern.
Ansonsten erlebe ich auch kein Geschwindigkeitsproblem bei SD-Benutzung.
Die Unterschiede zwischen den Themes sind weitaus massiver (Luxus versus schlicht).

Gibt es denn auch ein automatisches Beenden, Holger??

Auch Europa hat Christian bis auf wenige Staaten schon neu gerendert.

Hi Mips,
ich kann nicht für Christian sprechen, aber ich kann berichten, dass Christian aus dem Urlaub zurück ist und an einem Preprocessing arbeitet, das die Verwüstungen (*) in Nordics kompensieren soll. Erste Erfolge hat er bereits.
Haben wir also noch ein wenig Geduld.
Gruß
Michael

(*) die sind akademisch nicht einmal falsch, aber für die Nutzung der OSM-Daten ein Problem.

Hi Tapio. Would it be possible to create a Quick install like Andrew at Voluntary? When I give the Tapiola.zip to the Android/Media folder ... Mapsvector/_Themes, my locus doesn't see him.

Tapio's zip alone works like a charm.
Download, click (in a file manager), select Locus as handler, wait some seconds until Locus has created its internal extract, enjoy!

AllTrails Web Site does a good thing: put the top level name in all the places where a segment name was.
But that would be tedious.
You can do a similar thing yourself using Notepad++ e.g. on a PC to do a "substitute all" for each file.
Maybe there is a program for PC that does that, too.

Another 1%/h battery saving (down to 5%/h while recording track, with a 1" hgt for  the region of the track, on a Galaxy S10), now that the hgt evaluation once per second is avoided.
TXs a lot, Menion!

Using online search a little bit and thinking about it a bit more, this is my summary:
- Google data repository is unmatched, beating Locus and any other searches hands down, whatever they try, for years to come
- Locus, for strategic reasons, also with iOS support in mind needs this independent online search
- on Android the Google API search is at no cost to Asamm, as Menion stated
- combining both searches technically seems not feasible, as per Menion's response
- to me, the obvious approach is
-- to have a Locus Search for Android and iOS alike
-- put a Google Search as separate function into the Android version

That would stop any need for tough comparisons and discussions, a d empower users to make their own choice, based on their needs.
Giving USERS a choice may not be a technician's first emotional approach, but is beneficial for all parties in the end.

And above approach would not add complexity to the UI a d user experience.

Hope is the last thing to die ;-)

Cheers
Michael

Very good background information, Menion, TXs a lot!

Yet, while on your server you must not use Google API, it would be not too hard to merge the local Android Google Search results with those from your server. Data feeds and presentation are two different architecture layers. And merging two feeds is no rocket science.
Once Locus server search is as comprehensive as Google Android API, the latter can be dropped. However, this may take years rather than months, I fear.
Do not get me wrong - I understand your strategy, and if you never start something new, you would never get there. But for the time being I strongly advise to combine the strenghts of both approaches rather than leaving the users with mediocre results (to be friendly) for unknown time.

Just my 2c.
Michael