Messages

Je nach Hersteller schlägt die Batterie-Optimierung unterschiedlich brutal zu.
Auf Android-Seite ist für Locus die uneingeschränkte Hintergrundnutzung zuzulassen und jegliche Batterie-Optimierung auszuschalten.

...
Bei Neigungswinkel könnten die Leute an ihr Smartphone denken.

NeigungsWINKEL halte ich auch für problematisch.
NeigungsRICHTUNG war der Vorschlag, den Wolfgang genommen hat.

Ist zwar nicht der geo-wissenschaftliche Begriff (den ich auch nicht kannte), aber mensch kann ihn verstehen ohne in der Wikipedia zu suchen :-))

PS: allerdings ist bei Locus die Semantik der Farbe anders als bei arcgis :-((

Am Großen Feldberg kann man das schön sehen, noch besser am Puy de Dôme

Das habe ich bei www.arcgis.com gefunden als Definition:

This map provides a colorized representation of aspect, generated dynamically using the server-side aspect function on the Terrain service. The orientation of the downward sloping terrain (0° – 360°) is indicated by different colors, rotating from green (North) to blue (East), to magenta (South) to orange (West).  Flat areas having no down slope direction are given a value of 361° and rendered as gray. This service can be used for visualization or analysis.

"Neigungsrichtung" ist im Moment das einzige deutsche Wort das mir dazu einfällt.

Schöne Grüße
Michael

@Menion: re. "@michaelbechtold Can't simulate any problem with overlay. What map should I use for testing, is there anywhere available for download?"
My bad - apologies! When trying to find the smallest possible map combination (world plus overlay) for your reproduction, I immediatley came across an overlay that worked perfectly fine on my device. Next step was to check the Europe overlay (highest resolution (png) private version) - which was missing ZL 12 entirely :-((
Hence Locus did fill in the vector base map - as expected.
Filling ZL 12 now into that special map :-)
Cheers
Michael

@Menion: global map works like a charm (I use one for ZL 1 to 11). What used to work is the overlay: 100% viasibilty for .sqlitedb/.mbtiles for ZL 12 and 13. ZL shows the correct content, ZL 12 uses vector map content, zero from the overlay map.
Cheers
Michael

Das ist aber keine Locus-Policy, sondern ein technisches Problem, oder ein Account-Problem.
Ich habe 3 Geräte mit gleichem Google-Account mit Locus Gold im Betrieb. Silber sollte sich diesbezüglich gleich verhalten (siehe Feature-Tabelle aus Ballonis Hinweis). Wichtig ist der identische Google-Account.

Like Tapio I had a loss of ongoing work with the route planner.
The routing was purely manual. And with each point added the response got slower and slower.
Until crash, without recovery of the track I was building.
Memory issue?
Maybe plus non-linear algorithms?

@Menion: something in the overlay mechanics seems to have changed.
Before (correctly), ZL 1-11 were by World map, overlay covered ZL 12 and 13.
Now the behaviour is weird:
- going up the zoom levels, ZL 12 shows a 50% view of ZL 13 content, ZL 13 is OK, ZL 14 is a useful and meangingful vector map
- going down to 13 is OK, going to ZL 12 from there shows ZL 12 the slow vector map view, ZL 11 is OK again.
TXs and cheers
Michael

V1.2 mit Christians OAM-Vektor-Karten vom Nov. 2023 - für Europa - als Hintergrund (ZL 8+) ist jetzt online, als direkte Downloads und als Torrents.

V1.2 with Christian's Nov. 2023 OAM vector maps - for Europe - as background (ZL 8+) is online now as direct downloads and torrents.

Too bad - Android 13 or 14?

The standard file manager is not able to look into the private data. Tools like TC or x-plore can do that when you grant permission once asked by Android.

In any case I recommend to back up your 18+ GB of data by connecting via USB cable to a PC, Laptop or OTG drive, before taking further action to move data on the device itself.

Also, you can move all the maps to the semi-private structure in /storage/emulated/0/Android/media/menion.android.locus. Folder maps and mapsVector for the respective files. The .../media/... structure is accessible by more file managers.

No problem.
Where I'm scratching my head is: the painful restrictions by Google for the file system access do exist since Android 11. Hence, if you came from Android 11+ and it worked before until recently (upgrade to 14): what was special about your Android 14 upgrade? HHas the device been wiped on the way to Android 14?
If not wiped, then you can try x-plore or Total Commander to get access to the private data structures where your data should be residing still. But then, on the other hand, also Locus should work seamlessly as the structure would not have changed.
I.e. still some digging to find essential facts ...