@0709Hi Willy, I probably do not get all your points.
Anyway:
- your file imports correctly to me. I do not see any problem, not even with the GIF image
- the increasing size of the "Locus/data/import directory > I know, this is terrible behavior

- improvements in export/re-import > this will have to wait a little more, sorry
@dyoghenesWhy you would like to attach existing points (LoPoints) to track during track recording?
@lucehmm, an interesting problem with the volume. I'm unable to simulate this issue on own device but found something in the automatic bug-reporting system. Seems you are not allowed to change volume in case, Do-not-disturb mode is enabled in your device. I've improved this method so it should only display some ugly warning, but app should not crash anymore. Give it a try in the next version, thanks!
@john_percy,
@michaelbechtoldthanks for the feedback regards the "Overlay" system.
1. interesting idea. Currently, I see main problem that map theme is unique across whole app. So the button in the overlay dialog change also theme for the main map, not just for the overlay.
2. this seems to happen only when picking from "recently used" section right? Fixed, thanks
3. nice, thanks. Fixed
4. blend modes were reduced some time ago. I simply can't remove some of them based on discussion here. It needs some deeper analytics and check which are really not used. So maybe later.
5. good point and exact explanation John! Interesting problem. Technically, when Locus Map decide to set base raster map rescale to 200% (and vector maps remains at 100%), raster map simply can be used at X/100%. If I disable this "100%" option in selector, it may still cause a problems on huge-DPI devices where base rescale for raster maps may be +-300%.
For now, in the dialog will be at least visible base scale parameter for the overlay so it will be easier to see reason why overlay is not visible. I'll anyway think about better "solution".
@joelocthere is still something wrong with your device. Please double check device settings, there have to be some more optmization settings. Don't you have any other app that do some memory optimizations?
My colleague Jan has S10 with A11 as well, and he does not have any issue with latest app version(s). Anyway as you pointed on topics in Android issue tracker, as well as many many topics on the internet, over-optimized Android devices are causing huge problems, not just to Locus Map. Unfortunately ...
Killing apps together with overcomplicated system internal memory/SD card is making me mad and forcing me to waste weeks of time testing and searching for hacks that may work ...

About heatmap: yes, I'm keeping denying it because I'm unable to simulate any problem. I was playing with your heatmap today during improving of the overlay dialog and now it works fast and without any problems.
I'm not against any improvements in loading of online maps, but only in case, it makes sense. Here, you use some russian server to hack Strava heatmaps. There is no reliability, no certainty that server will work tomorrow and I already received few compains from the map providers that ended with blocked custom user-agent for online maps in latest app version. So sorry, I do not plan any improvements here for now.
@tapioah, this is really nice usage of quick bookmarks

All existing add-ons should remain working. Locus Map 4 is for them (add-ons) still Locus Map Free, so no problems are expected.
@Raddinothanks for the report. Exactly this was already reported by @balloni55 some time ago, but unfortunately I'm still unable to simulate this problem on own device ... weird

.
@Rainman2dethis probably happens because imported track does not have any navigation instructions, so app simplify track a little bit and try to generate instructions based on it's shape.
Re-calculation after import: something similar is planned, but it really is not so easy task so it will take some more time. Anyway, my main question: why you import track from Komoot to navigate in Locus Map? Why do not using navigation directly in Komoot or plan your route in Locus Map?
And as @freischneider wrote, this topic is mainly for finalization of new LM4. Thanks for understanding.