[APP] - version 4.12.+ ( 09/2022 )

[balloni55]

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

i don't understand...

for me it is not logical when reading "All caches" or "All selected" and no checkbox is ticked in the selection

[Tapio]

Expert setting of immersive view doesn't bring me the working fullscreen system back. Not using it. Because UIs (dashboard/top bar) are still below the notch and Android Status bar.

EDIT: After a restart of Locus, it uses full view/fullscreen as before. Awesome, I've got fullscreen back which is good, because it worked with my phone.

You cannot view this attachment.

[freischneider]

Today Auto Stop activated. Looks quite good.

[Tapio]

Today Auto Stop activated. Looks quite good.

I'm wondering, what's the difference?

[slarti76]

Today Auto Stop activated. Looks quite good.

I'm wondering, what's the difference?

Yeah, that should probably be re-worded to make clear that first setting is about "device movement" and second about received GPS positions. Well, or vice versa

[Žajdlík Josef]

Hi Menione, the first test "Autapause" on the Samsung A53 (A12). According to the upper bar is reading the activity OK. But there is no control when AutoPause is active. Upon arrival in the building and laying the phone on the table, "drift" was created in the record. See SCR.

[Tapio]

Does not auto pause yet. Menion, can you tell a bit about the algorithm?
Quite common situation here in screenshot, sitting here for 15 minutes, gps radius is 6m. Both of the above pause options are turned on. You cannot view this attachment.

[Menion]

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 .

[balloni55]

Logs manager > "log your visit" isn´t possible, see screenshot

"Upload draft" work

[Tapio]

Thx for working on auto pause. Do you use some kind of shake sensors for this? Because Locus asked for Android access.
Please consider an option to auto add a waypoint upon pause end, at pause start position, with pause length info...

I found problems.

1. On track recording + navigation, embedded WPs are added here from outside, via intent. They are visible on the track. But it's almost impossible to tap those WPs. As if there is just one pixel tap area. I think it worked before.

2. Screenshot. Navigation of a track x. Locus then shows track x PLUS the upcoming navigation. Useless? At least a problem with distance markers.

[Andrew Heard]

Auto-pause: I was testing it during the weekend and have to say: it does not work at all, sorry!

@menion - doesn't this feature https://help.locusmap.eu/topic/improved-stop-detection-and-distance-calculation-with-a-speed-sensor need to be implemented before auto-pause can be reliable?

[Menion]

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?

[Žajdlík Josef]

Clicking on any Lopoint Locus crashes. Android 12 on the phone and 11 on the tablet.

[Tapio]

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?

Will observe. Happened once. I thought it was due to the last update. But it does not happen now.
Yes,that's how I start navigation.

[Tapio]

Auto-pause was finally tested and seems to work very nicely.

... on Android 12+ only?