Autostart Recording on Start of Navigation/Guidance

Fred - recording can be set to auto-start but there is no auto-stop setting. It is always manual/user stop/ recording off. Maybe you are confused with navigation setting to auto-stop navigation at end of the route?

No, I understand the difference. I just wanted to say that in that eventually new feature of autostart track recording when guiding starts, I would not have autostop in recording when guiding stops.

That was not a statement that it works. It was a question if that was possible. Just in case if the proposal is not implemented.

Hi guys, an interesting idea with "tasker" support. Currently, the app does not forward any events about own activity to external services. Not sure if this is now easily doable because the latest Android versions have quite a lot of restrictions on how the app may communicate. Maybe it should be possible to watch somehow notifications in the top status bar? Locus Map during navigation display notification bar.

I am also interested in capturing the start of navigation with tasker. I have tasker profiles/tasks to switch between dashboards in a list. Some of the dashboards are only meaningful when navigation is active, so the list is shorter when with no navigation active. At the moment I solved this with a UI popup where I have to activate navigation button If I plan to use navigation in this "session". This popup is shown when I start the "session" by attaching the phone to my bike mount (NFC-triggered).

Dynamically adapting the dashboard list would be very nice. I could omit the popup. I'll try to detect notification from Locus in a first step, though. (Thanks for the tip). Although this might work, I would prefer a "proper" direct communication.

Would it also be possible to detect stop of navigation with the notification method?

Notification bar works only conditionally. Tasker detects the navigation in the notification. But he recognizes them every 2s.

@ Menion: maybe they can check if events via their own activity to forward external services is possible.

Is there a possibility to register so-called "Broadcast receiver" over intent? This is probably the only option of how to send some events from Locus Map to any other "target".

You mean in tasker? Yes, there is. In fact, only "broadcast receiver" intents are supported.

See https://tasker.joaoapps.com/userguide/en/intents.html (scroll down to "Receiving Intents" section).

Any news on this? It seemed you looked into the possibility to do this with "Broadcast receiver" Intents, which are supported by tasker, as I wrote.

So any chance to get some events from Locus to other apps (like tasker)? Would be happy to test it...

Locus writes a notification when starting the navigation. This I use now for Tasker. But it still has to be tested in practice. But the locus support for "broadcast receiver" intents would be better. and it offers many more possibilities.

Hi guys,

so I have hopefully something for advanced users to play with. I've just published Beta version 3.42.0.1 with enabled notify system over so-called Broadcast receivers.

I've tested it only internally over the app itself, but it should work.

To test it, simply to register a receiver for action com.asamm.locus.map.EVENT_RECEIVER . For all "start guidance/navigation" and "stop guidance/navigation" events, you should receive "Intent" with data. The indent should contain simple JSON as "data" parameter. Content may be improved anyway important is to test, if you will be able to receive these intents. Let me know.

I just did a quick test, but it didn't work. Maybe it has something to do with the intent having data attached to it. The tasker doc (https://tasker.joaoapps.com/userguide/en/intents.html) says for the Scheme and Mime Type parameters, if they are not specified, only intents without data can be matched. So maybe I have to specify one or both of these, too. I assume mimetype is application/json? But what to specify for scheme?

Thanks... I've installed a tasker, to rather test your use case by myself and indeed, I've found one remaining issue also on the Locus Map side. I'll write more once the new Beta will be out.

With the new Beta, I'm able to receive intents on start/stop of navigation in tasker :-D

How to distinguish the start and the stop event? There seems to be no data associated with the intent, but an extra (Bundle[mParcelledData.dataSize=108])? Should I evaluate this extra somehow? If yes, do you know how to do it in tasker?

Hello, promised additional info:

Seems you already made a progress, perfect. Anyway just for all ... steps:

1. create in "Tasks" task, that will handle received data. For this, tap on "+", write a name like "Handle start nav".
2. as a sample, add "Notify" task and into text insert exactly `Data: Úta` (also write some title)
3. the create in "Profiles" new "Event" > "Intent Received"
4. set it's action to mentioned `com.asamm.locus.map.EVENT_RECEIVER`
5. confirm (back) and choose as target previous created task "Handle start nav"

And that's all. I had to turn the "Tasker" off/on to start to react correctly, do not know why. Then after the start/stop of the navigation, I've correctly saw notification with JSON text. I hope this helps to start.

Thank you. I just realized that I tried to display so much information in a tiny popup that the output of %data variable was truncated. Therefore, I assumed there was no data attached.

Now I see it and can distinguish between Nav Start, Track Guidance Start and Point Guidance Start, as well as Stop of all of them. Type of stop action is always "guide", so I assume I have to keep track of what nav mode was started before by myself.?

Thanks a lot again! Now I can automate my locus experience even more :-D

The enhancement for Tasker is different to what the originator of this help topic Ulrich Kiermayr proposed 2 years ago.

zossebart comment should probably be in this thread: https://help.locusmap.eu/topic/autostart-recording-on-start-of-navigationguidance#comment-78985 .

Anyway, I'm definitely not marking this idea as "completed" just because of this support for the Tasker. Tasker solution is overcomplicated and not usable for basic users. On the second side, if the tasker or any other app will be able to catch such "notifications" from Locus Map, it may open a nice field of user customization.

I totally agree, such an option (autostart rec. on nav) should be natively available, it's good not to forget recording and good for newbies. Locus is already complex and Tasker would make their heads explode.

I also would prefer autostart the recording when I start a navigation. Perhaps there could be the question bevor starting "Start recording yes/No".

For me, just auto-start recording, I don't want to be asked.

It's both, along an existing track or to a point. I don't have it twice, because I mean a downloaded track which I will drive on another day an perhaps with some other ways.

To avoid double tracks I asked for an Question before recording (Yes/No.

Yo, obviously tracks have different purposes. Either for navigation/travel along and/or offering real world data / personal performance data.

Rather a question of track organisation in Locus folders. No problem to keep both. Especially since own recordings can be more fuzzy than, say, a track made by the route planner.

Now that is an achievement, congratulations!

:)))