Messages

Hello Ivo, almost ten years based on your profile here on the forum, amazing!

Locus Map for iOS is currently in preparation and will be for sure published during the year 2023. But expect really limited functionality compare to Android version. Well, we are 10 years behind on the iOS so ... 

[@Žajdlík Josef]

@Žajdlík Josef
The huge benefit of the new auto-pause system is, that it is independent of the GPS! So the app may turn GPS off and wait till get info that some movement was detected.

@Tapio
hmm, "Presets" and "Dashboards" are included in the "full" backup. Routing profiles are missing, good point (added). What I was thinking, was removing these two dummy manual backup systems and allowing manual & automatic backup to be fully customizable > so where and what to backup...

@Andrew Heard
version name, ah typo, sorry. There was a minor and very quick 4.12.2 version, so it caused a little mess.

[Beta version 4.12.1.5]

New Beta version 4.12.1.5

With a nice bunch of interesting news, for example:
- add: Ski routing to online & offline LoRouter
- add: support for SVG http icons (mainly used in the online LoPoints for now)
- chg: "recalculate all" available in "Set router" dialog instead of the side menu
- chg: new settings menu for backup & filesystem

---

Auto-pause: I still do not know what to think about it, cause I also noticed some malfunctions and see no space for some improvements on my side. Will test it, but from my point of view, it is currently not ready to release.

I've not yet looked on memory problems, sorry @balloni55 , but I'm keeping it on my mind.

I would not be so strict with "does not get any new features anymore"  . As visible in the changelog of every version, I still do a lot of modifications also in the Classic version. But to be true, by intent I try not to add bigger new functions to the Classic.

The new version will be published probably at the start of December. Google forces us to do a big update in internal libraries so I need a little more time to test the app and fix a few more problems that appeared (mainly on Android 13).

Thanks for understanding guys.

[@freischneider]

@freischneider & @Josef Žajdlík
hmm long pause cause a problem ... will have to test but it may be a major problem 

@Tapio
what I use is called "Activity recognition". "Significant motion sensor" > did not know about it, thanks for the info. It does not give much info, but I'll check how it works, thanks!

@CabrioTourer
yes sorry, this is a really really really old problem without a simple solution for now, already reported a few years ago by @joeloc and never solved. It needs a massive rework of the whole system on background, unfortunately.

[@Andrew Heard]

Hi guys,
"auto-pause" without explanation > sorry for this.

Old system: "Record only when moving" option is based on the known speed of the GNSS unit. The recording service only checks if the last received location has any "speed value" and if not, it simply ignores this location, nothing more!

The new "Auto-pause" system is based on the magic logic of Google Play services that use device sensors, not the GNSS. The app is then able to receive the probability of certain activities and act based on it. Because GNSS is not required here, the app may finally pause/unpause recording!! This also means, that if Locus Map is on background, it may also turn off GPS if not needed by any other function!

If this will work correctly, old system will be removed.

@Andrew Heard
"auto-pause" is not visible in the search because all internal recording profile settings are not there. It is a little more complicated here.

battery consumption > manual pause will still be more efficient because no extra sensors except your brain will be needed. On the second side, gravity and other sensors should be very very battery friendly so I believe that difference will be minimal.

"Track name format" > improved, thanks

@michaelbechtold
you mean the secret "_split"? 

[version 4.12.2.3]

And another nice (of course) version 4.12.2.3 is ready for testing.

Auto-pause was finally tested and seems to work very nicely. Expect a delay of 10-30 seconds till the system correctly recognizes the change in the movement. So it is not as fast and accurate as may be with a system based on the bike BT speed sensor as mentioned @Andrew Heard  (btw. good point, I'll look at it), but it perfectly covers pauses and forget-stopped recording.

And yes, this uses various sensors in the background to detect motion. But don't ask me exactly how it is computed as it is a black box hidden in so-called "Google Play Services".

@Tapio
1. I'll check it
2. track that you use to start navigation should be hidden during navigation!! Does this happen all the time to you? You start navigation by click on the track and then the "Navigation" button at bottom menu?

I was stuck on geocaching stuff and some stupid requests from Google, so I was not yet looking at your email. Will check it tomorrow and let you know, thanks!

Hello Bob,

this really looks like a typical problem of battery optimization. Check please our manual here if you find a tip suitable for your phone.

[@balloni55]

Hi guys

Auto-pause: I was testing it during the weekend and have to say: it does not work at all, sorry! As I wrote, the first attempt: will have to test it more and let you know.

Record only when moving: this option simply ignores locations, when the app receives a location with speed = 0 (or close to 0). This new option should really pause & unpause recording based on the movement. In the best case, also disable/enable GPS when the app is on the background!! Once the new option will work, the old one should be removed.

@balloni55
I'll discuss texts with Michal anyway if you select all cache sizes or select NO cache sizes has no effect on the result. Because in all cases, app returns all sizes .

And does it make sense to select for caches with "no sizes"? "Nothing selected" is always considered equal to "all selected".

Extra options > I'll look at it.

[new Beta version 4.12.1.2]

Hi guys,
interesting new Beta version 4.12.1.2 just published.

What to expect?
- downloading of geocaches directly over the app > future of G4L is unsure so I've decided to implement all necessary features directly into app
- a test version of the new system for full-screen mode ("Expert settings" where probably remains)
- a test version of the activity recognition system for track recording > new option "Auto pause" in the setting of recording profile. I've not tested it in the field yet so use on your own risk. The top bar on the main screen may display a "Custom" panel with current info about the detected activity.
- and many fixes ... uff. Enjoy weekend!

---

@balloni55
- NMEA simulation is visible only if any NMEA message is in the Locus/cache/nmea directory
- memory problem > I was not checking it yet, but thanks, next week

@joeloc
not as easy, but I'll look at it and let you know

Hmm thanks, but I'm not sure it worth the work. Two maps of the same type and region: why to have them on the device? Anyway, problem is that app loads and use both, understand. This I believe happens only with OAM maps, because LoMaps had precisely defined area of coverage so this should not happen there.

Hmm ... I probably know why this happens, but I'm not sure there is anything I may simply do with it 

[@slarti76]

@slarti76
hmm, so another attempt with a "split track". In case, the track "Creation time" will match first trackpoint (this means recorded track), "Creation time" for each new track will match the time of its first trackpoint.

Ah, same as @Tapio suggested later ...

@balloni55
Bottom buttons > I'm testing on an older (and really small) Samsung S2! and it works correctly. So I've added few log events into the code and create me a log with the next Beta version (end of the week) please, thanks.

Memory problems > this will be hard. @jordyke wrote that he is not using geocaching so it won't be probably connected to caches. I'll need to test it on more devices and find the core (just moving with map? Track recording? Navigation? ...) what causes this issue.

@Andrew Heard
https://forum.locusmap.eu/index.php?topic=8129.msg69415#msg69415

Android Auto > does this happens every time when you connect the phone to Auto?

"Add X point" good idea, I'll look at it thanks

@Tapio
missing overview for webp photo > may you share with me some sample webp image? Thanks

@CabrioTourer
As a developer, I would prefer 250m, done.

[@michaelbechtold]

@michaelbechtold
hehe, ich benutze es schon seit einiger Zeit, aber ich lese und antworte einfach nicht in allen deutschen Themen. Du kannst mich aber gerne erwähnen, wenn du mich brauchst.

@zweifler
Ich teste es gerade und kann es auf dem Locus Classic nicht simulieren. Seltsam, dass Sie dieses Problem mit der neuesten Version haben. Aber das Backup wird benötigt, danke.