Messages

Hello Thomas,
sorry to see this. You may create an error log, but I'm worried it won't by clear by this failure. So I have to ask if you will be willing to share a full backup of Locus Map (made by app settings > Backup & filesystem > Backup manager > manual backup) with me. So I should be able to simulate this issue on my own device.

I guarantee that data remains save and private and will be deleted once the issue is fixed. You may share it over any cloud service here on the forum over PM or over locus.map@asamm.com support email. Thanks a lot!

Hello Hispanico,

interesting. On the first screen is visible that map is tilted in some pseudo-2D view. This may be done only in a special version by sliding with two fingers on the map up and down.

When you close the app with two back press, wait a while and start again, does not help?

Hello Davidos,
display full-screen chart in the track detail and then select heart rate as Y axis value. Hope this helps.

Hallo mwdd

wenn ich deinen ersten Beitrag richtig übersetzt habe:

- dynamische Zeit bis zur Benachrichtigung zum nächsten Navigationspunkt > bereits jetzt über Konfigurationsdatei, Parameter "navigation_announcements_times" zu ändern

- weniger Abbiegehinweise auf Wanderwegen, dafür mehr in der Stadt > schwer zu lösen

- Bildschirm nach Passieren des nächsten Navigationspunktes ausschalten > Das sollte schon so funktionieren

- Display schaltet sich nicht aus, wenn man von der Route abweicht > das ist doch eine Idee, oder? Hmm könnte nützlich sein, also schlage ich hier vor, was kodela & freischneider > Idee auf unserem help desk geschrieben haben

- schneller Zugriff auf einige Einstellungen > zu viele Einstellungen und zu wenig freier Platz dafür. Wir können darüber diskutieren, aber es könnte schwer zu verbessern sein.

Menion

@john_percy
LoMaps of UK + Germany for the test are prepared here.

[Beta version 4.17.1.2]

New Beta version with a big bunch of minor fixes and various updates. Enjoy the weekend!

Beta version 4.17.1.2, download.

@CabrioTourer
thanks for the description. I'll have to read and check it more carefully after the weekend!

[@CabrioTourer]

Hi guys, sorry for the small delay in answers > hiking (testing) vacation.

@CabrioTourer
maybe you see a problem I still don't. When you pick a point as a via-point during planning, it gets duplicated. One is attached to the track and one remains as before. Isn't this a problem you see? I'm thinking how to do it better because currently track needs to have all via-points placed directly on any existing trackpoint ...

@joeloc
status bars and navbars > we fought with them a lot! The current solution is the result of desperate tries how to hide them completely. And the old system is really what you found > expert settings. There is nothing more you may do. Ah, as @T-mo wrote ... option in Expert settings use on own risk. It won't work 100% correctly on all devices.

@Will C
give a try to the Menu > Share > Screenshot 

@Andrew Heard
Presets ... hmm, I do not like problems that contain the word "sometimes" . Please try to find a reliable way to simulate it and I'll gladly look at it.

Hello Pix,
thanks for the bug report. The issue has finally been found ... seems to be in Locus Classic since 2019, uff.

So in the next version, it should work as expected, thanks.

Michael, in the test directory, is a Beta version with
- logs
- a little optimized caching of HGT files

Give it a try. If consumption will be the same, please enable "Log to file" and create a small log for me, thanks!

The world map in V3 is not a problem. Simply download and set as a "world map" in the settings.

[version 4.17.1/3.68.1]

Hi guys,
bug-fix version 4.17.1/3.68.1 published!

Hi guys,

hmm, I may suggest a
- check used map theme (in the side map content panel)
- download from the Store "World map" and set it in the app settings > Maps > Advanced > Pre-load global map (this should be done automatically, I know). This should highly improve your 90km resolution
- or using online LoMaps

Android version should make no difference. Anyway, the app currently loads HGT files into memory and then computes elevation from these in-memory files. I have a suspicion, that aggressive memory management force app to discard these loaded files and app then has to re-load them again ... and again. So I've added some logs into the app to see, how often app re-loads these files from disk. The beta will be published, hmm hopefully tomorrow ...

[EDIT]

Thanks for the log Michael. Unfortunately, I see nothing useful inside ...

Will have to try on another device next few days because on my main Pixel5, no problem as I wrote before. Still, no idea why this should happen ...

Btw. you are using 1" files from Sonny from here right https://sonny.4lima.de > Germany DTM 1" ?

EDIT: I've added some more log messages into the app, so in the next Beta version, "Log to file" may produce some more info. I have one idea what may cause it so want to try.

Hi guys, I have to post a few info here as well 

Google API for search is not technically available to us. Its license for public API prohibits us to use it on our server. It should be also complicated to merge these results into our LoPoints system, but it is another story ...

Google search system was anyway used in the app till now, right? It was because Locus Map used a system directly integrated into the Android and that is free to use for any Android device.

Anyway, we are here creating a united search system on our server, that will be able to use more sources, user history and later also user-based personalization and return the best possible result to the user. This is not possible to do on the device => simply: Google API can't be used because of technical and license limitations. This is the fact, sorry.