Messages

Hi Andrew, you seem to use also some middle "Screen zoom" so together with little bigger fonts, it causes these problems. Anyway, the issue is on my side of course. The app should be prepared for this.

As I see, most easy is to remove units in case of this hh:mm:ss time format. So done, hope this helps.

Hi guys, this sounds like a serious problem. Balloni has this problem with geocaching and without the navigation & jordyke during navigation. So common here is the work with map > zooming & panning right?

I've noted a TODO task and will test it next weeks a little.

@ta-ka
One user reported that a new change in "jpg" in Onboard calibrator broke his new maps. He uses semi-transparent PNG files as a source images. I was firstly thinking about extra optional settings, but maps from photos are so small, that I think it does not worth it. So sorry, in the next version, PNG will be used again. Thanks for understanding.

[@slarti76]

@slarti76
Are you using explicit intents? So you directly specify the package of the Locus Map app (menion.android.locus(.pro))?

The time of splitted tracks > can't confirm. Even in the code - the app assigns the "Creation time" of the original track to both two newly generated tracks. Please check it again, thanks.

Btw removing intents, as discussed with @Tapio should be equal to the end of Android. (Almost) everything is inside based on "Intent"s .

@balloni55
oki, what may I do to simulate it. What about some GPX with caches > if you import any PocketQuery, are all caches affected by this? Weird I've not noticed this problem 

@Viajero Perdido
thanks for the info. Keep me informed if something won't work in the app, but such changes should make no problems.

[@Andrew Heard]

@Andrew Heard
thanks for the report Andrew. Weird, will have to test it.

@balloni55
content of the point bottom panel is generated automatically based on the point. So it depends from where the cache point comes.

@plu-irin
the name may already be changed in the profile > open the main menu > click on the top profile > Manage account.

@Tapio & others
"record only when moving" use speed reported by the GNSS unit. Anyway even if not moving, it still only ignores location data but does not pause recording at all. For this, I already have prepared a system using "Google activity recognition", but I was never able to finish it for some public test  . This should allow to detect of changes in movement style so react on pauses or inform about activity & paused recording.

Hi guys,
it is a more complicated topic and currently, implementation is not perfectly reliable to be true. Currently, if we talk about BRouter or LoRouter service, time is computed internally by this service. During the navigation, the app deals with users' average speed during the last hour and uses it a little bit to modify computed ETA.

You are too fast. New setting is in the end not available in the points/tracks settings, but added into "Expert settings" as "Track previews during import".

Ah sorry, I wrote I've published 4.13.1 > it is 4.12.1 and it already is available on the Google Drive.

Hello,
just a few hours ago was published a new version of the Locus Map was on Google Play, so give it a try.

Hi guys,
thanks for opening this topic > interesting and useful.

Changes in the next version
- I've detected that the app saved previews in PNG format, sorry for this. It will be changed to compressed JPEG so the average size will be around 40kb (instead of the current average size 250kb!).
- I've also added an option into Points/tracks settings to disable generating of previews upon import (Locus Map 4.12.1+).

Makrodroid, hmm. Ich war auf der Suche nach ein paar Informationen, wie diese App dies tun und: https://www.tapatalk.com/groups/macrodroid/alternative-screen-lock-with-fingerprint-sensor-su-t4227.html . Siehe. Es ist wieder ein verrückter Hack, weil keine solche offizielle Methode existiert.

Ich habe versucht, dies auch zu implementieren, aber es funktioniert (noch) nicht 100% zuverlässig. Es ist bereits in der Beta-Version von Locus Map 4 verfügbar, und da Sie nicht der einzige sind, der Probleme mit der Bildschirmsperre hat, ist es vielleicht an der Zeit, es noch einmal zu überdenken und fertigzustellen ...

Übersetzt mit www.DeepL.com/Translator (kostenlose Version)

[@Andrew Heard]

@Andrew Heard
ah thanks, amazing observation. This is it! I'll improve it, so next version will be for sure > perfect 

Test version 4.12.0.1 with 15+ small fixes and improvements uploaded for testing.

Seems that an official bug-fix version next week will be necessary . Btw. have a nice weekend!

Ehm, was genau wurde in den letzten Monaten/Jahren neben dem sehr problematischen Vollbildschirm entfernt?

[@balloni55]

@balloni55
hmm I see no report on my email or support locus.map@asamm.com email. May you please check it? Thanks

@Tapio
regards the navigation line coloring issue here, it is currently not a problem. The app draws only a part of the route right "before you" in defined color. Rest till the target is then drawn in a little less visible style, to distinguish the route in case it overlaps.