Messages

The new "Auto-pause" system is based on the magic logic of Google Play services that use device sensors

Does that API have a name? I guess it is the same system which Tasker offers as an event trigger, "Significant motion". TBH my experience was bad... and too much of a black box. But we'll see how it turns out in Locus.

Do you use this one?
https://developer.android.com/guide/topics/sensors/sensors_motion.html#sensors-motion-significant

How does the new Auto-pause setting differ from the combined action of the existing Distance/ Time Interval/ Trackpoint recording condition settings?

LOL, I didn't understand the 2 sliders yet and now you come and make things more complicated...
Ugh, my brain currently cannot process this topic. I GUESS the question you should ask yourself is this: With no auto-pause options, only the settings you mentioned, how can you Locus tell to pause recording on "longer" period of no movement? (I think impossible in a meaningful way)
At the very least you need to tell it to only record tp's like every 25m because gps derivation. But what if you want it to record, say, every 5m? Just a first thought, cannot think it through rn, my brain 😂

I'm on Android 10. I have both sliders on. I haven't seen the recording button set to pause yet, but I will observe it more properly. What I see is, the resulting track is now clean from those tons of trackpoints at one place. Good.
Menion please optionally leave an embedded Pause WP. This is easy to detect in the post process now, IF difference between neighboring trackpoints > n seconds. With n being user def.
I think "where and how long did I pause" is one of the most interesting performance informations.
Currently I add pause wp manually with help of the elevation profile graph (x axis set to time), but that's exhausting.

Recent version is crashy? I experienced a ctd. When I tap on an embedded wpt in the track details, screen goes blank and it goes out of track, to the folder view in track manager.
EDIT: Ah I see, 4.12.2.4 fixed it

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

... on Android 12+ only?

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.

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.

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.

Today Auto Stop activated. Looks quite good.

I'm wondering, what's the difference?

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.

[@Tapio]

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

Hi, I attach it here, didn't find a way to attach in PM.

Karte in Presets, bitte Menion überzeugen, ich habe das schon zweimal versucht, bisher vergeblich.

Genau, ist nur in der Configdatei. Bei mir liegt sie hier:/storage/emulated/0/Android/data/menion.android.locus/files

Ich entschied mich für:
navigation_announcements_times=15|45

Drei Ansagen waren mir auch zu viel. Eher reicht nur eine.

Preview of geotagged webp photos isn't shown. If I tap on it, it loads fine.
You cannot view this attachment.

What I'm asking for is sort-by-start-time, sorting by the date/time of the first timestamped point in the track.

I can see your point, but that would be too much sorting for the users. Because usually there's no difference.
But good observation.
Solution:
Menion should just set "creation time 2nd split = first trackpoint time 2nd split". That would feel alright imo.
Thank me later 😉

Definitely works, starting/stopping recording, with save/without is something my Tasker triggers daily a few times.
I'd guess as for actions Tasker Plugin just translates UI into intents.

@Menion, removing Intents, i. e. Locus Action system at some point, pls comment?
Feeling no itch to rework my numerous tasks.