Locus Activity for start Track recording (in Tasker or similar app)

Matej shared this question 11 months ago
Answered

I need setup Automate app to start Track Recording in Locus when certain action occur.

What is name of Locus Activity for Track recording please?

Thank you.

Comments (16)

photo
1

Good day Matej,

track recording is not controlled over any activity. You need an direct intent with defined action to start this feature.

For this exists this manual: http://docs.locusmap.eu/doku.php?id=manual:advanced:locus_api:public_intents#track_record . Hope this helps.

photo
1

Hi Menion. It really works.

Except parameter INTENT_EXTRA_TRACK_REC_AUTO_SAVE. Even if I set it to true or 1, it always ask me for saving.

Parameter INTENT_EXTRA_TRACK_REC_PROFILE works good.

Do you know how can I fix it please?

Also is there a way how to close Locus if it is running as a service?

Thank you.

photo
1

Hello,

are you sure you add "auto save" parameter to same request as "stop"? As I see in code, it should work correctly. It just needs to be a single request to stop track record with optional parameter to "auto save".

And closing Locus is not possible, because it should not be needed. Such request does not make sense. Android take care of applications by itself.

photo
1

Yes, I am sure. I copy whole macro and only changed action to record stop instead record start, changed parameter to INTENT_EXTRA_TRACK_REC_AUTO_SAVE and changed parameter value to "true". I also tried parameter value "1".

Locus can running in normal mode and as a service. In normal mode it is like most app and if it goes to background, Android handle it as it needs.

Locus as a service is always running, even in background. It has permanent notification and even if phone has low memory it persist running.

I use Locus as a service since I bought it years ago because it is better for my needs.

But now I am handling automatization in car and I need a way how to close Locus if is running as a service.

photo
1

Please check your configuration:

0f6e58917ba1f5aaba903f02d7a6c655

b947e3064d40368cf7ff590b0fdc0b49

47e0399ee6e851e2180149b4053db924

photo
1

Configuration checked. But auto save still does not work.

photo
1

There is some option to backup your settings ( like wrote here http://forum.xda-developers.com/u/tasker-tips-tricks/guide-backup-restore-import-export-t3277104 ), so you may try to backup it, so I may try to restore and simulate a problem.

About task to stop Locus - understand, but I still cannot agree that it may be needed. Locus that is running as a service, should have zero impact on battery and so I see no reason to kill it somehow. You can also disable "Locus as a service" in case, you use it mainly for track recording. Because active track recording has exactly same effect on life of Locus as feature "Locus as a service".

photo
1

I attached settings backup file.

And about task to stop Locus. I use Locus for many tasks. Navigation, view maps, recording track, geocaching, etc. I have only 2GB RAM and I usually have many applications running in background (mainly while geocaching), so in order to Locus be locked in memory while in background, I need use Locus as a service.

But with my current plan for automatic track recording, I need after finish track recording also stop Locus.

photo
1

Matej, I need a backup of tasker settings not a Locus :). I'm sure it is a problem in some of your incorrect settings in tasker so I need your current configuration to try it and suggest a solution.

About closing Locus - understand, sounds logical. Anyway your use-case is so specific, that when I add such feature, it will be one-men show. Sorry.

photo
1

I see. Okey. I attached .macro. I had to zip it because this site do not allow .macro files.

I do not use Tasker. I use MacroDroid - it is free and simpler alternative for Tasker. So the .macro file is for MacroDroid.

And about task to stop Locus: I understand...

photo
1

Good day Matej,

I'm finally testing this application. Problem is that when you write into "Extra" field number like "1" or text like "true", it is always considered as simple text. Locus then expect boolean (true/false) value and instead there is a text value. I can improve it to next version 3.19.0 because for today release it's too late.

EDIT: sorry, not possible to fix it. No matter what I try, it just do not work, interesting. With "tasker", no problems.

photo
1

Hello Menion. Thanks for try. But I do not understand how is it possible that recording profile works and auto save do not. So there is no other help than recommendation for purchasing Tasker?

photo
1

Auto-save is just a sub-parameter that should give Locus some additional information.

If developer of this app is responsive, you may forward him to this discussion and I'll gladly help him to fix it.

Problem here is that received intent contains value parameter under correct key, but commands

getBooleanExtra and also getStringExtra returns null, which is interesting.

photo
1

Okey. I wrote to MacroDroid and also sent him link to this conversation.

So I hope he check this out and you figure out how to solve it.

Thank you for your time for solving this my problem :)

photo
1

Author of MacroDroid here. Intent sending in MacroDroid is still an experimental feature and the current release does not support boolean parameters, that is all.

I am responding to Matej to give him a test version to try where true and false values will be interpreted and sent as booleans so this should work and this will role into the next update.

photo
1

Hello,

thank You for looking into it. Appreciate it. If there will be something I may help with, feel free to write me.

photo