Messages

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.

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