Broadcast malfunction or wished behavior

Wolfgang shared this question 1 week ago
Answered

Hi,

when I use the new great broadcast feature I'm not sure if the following behavior is a little bug or not...

When I send a "track record start" then the track recording seems to be started even locus is not running itself.

Wolfgang

Comments (4)

photo
1

Good day Wolfgang,

"by start itself" you mean full starting initialization with progress? It is correct. Try it for example with widget for track recording, it will work same.

Why this is unexpected for you? Intent just start recording service on background, almost nothing more. Whole big Locus core does not need to be initialized.


Jiří M. aka Menion

photo
1

Hi Menion,

for me it was surprising and an unwanted feature because I did not start locus and just used Google Maps for home drive and then I mentioned that the track recording did start, because of MacroDroid trigger. I only want this, when I start locus manually. But no problem then I will change the macrodroid behavior and check if locus is running or not.

I just wanted to know if this is wished or changes once.


Thanks Wolfgang

photo
1

Understand.

I'm little worried if "Check if Locus runs" will work. You will see. If not (false positive responses), let me know and I think we may try to improve this as well.

Jiří M. aka Menion

photo
1

I just did one test:

Trigger: button

Action : notification

Contraint: App Alive in Background


Locus is running as service. Seems to work :D

photo