Messages

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

First let's understand if we talk about the same device. If not - do you have access to the previous one?

The contour lines mentioned in the news are embedded into the .map files. And display (or not) is controlled by the theme.
The hgt files are optional and allow the dynamic elevation Feature.

If the A5 (2017) runs Locus 3 Classic (Pro in old terminology) and the A14 runs LM4, this is correct behaviour.

"Pro" in LM4 terms means a silver or gold subscription.
If you have LM 3 Classic as "Pro", you will have a discount for the first year (if I recall correctly, Silver is free in year 1 in this case)

x-plore does it, on Galaxy A52 and S6 lite, both on Android 13. And on S10, Android 12.

I'm using x-plore, grant access as requested, and can read/write from/to /Android/data, even on Android 13, Sept. security level (tested this morning). And even on EXT SD/Android/data

Hi Jochen,
until now the Google policy re. /Android/media is less perverted than the one re. /Android/data.
Locus also scans /Android/media/menion.android.locus on both, internal and external SD.
Also file Android - on device - file managers can handle that folder more easily than /Android/data. My experience ...

"Smooth movement" maybe a better zerm - native speakers, pls. advise :_)

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.