[solved] [bug] Macro not invoking (application launched)

roughnecks

Active member
Hi,
I have this macro which should set music volume when launching or closing foobar2000. For some reason it doesn't trigger anymore - worked at first.

I have also tried the legacy mode for app launched/closed trigger and I have rebooted my phone. Accessibility for MD is also on.
In the system log there's no trace of this macro.
 

Attachments

  • Set_Foobar_Volume.macro
    2.6 KB · Views: 1
  • Set_Foobar_Volume (1).png
    Set_Foobar_Volume (1).png
    49 KB · Views: 16

Qarboz

Well-known member
Hi,
I have this macro which should set music volume when launching or closing foobar2000. For some reason it doesn't trigger anymore - worked at first.

I have also tried the legacy mode for app launched/closed trigger and I have rebooted my phone. Accessibility for MD is also on.
In the system log there's no trace of this macro.

You change the ELSE IF with ELSE (only) and try

Ps
Sorry for my english
 

roughnecks

Active member
Testing this with the calculator app - never activated.

Can you try on your phone?
 

Attachments

  • photo_2021-07-13_17-45-36.jpg
    photo_2021-07-13_17-45-36.jpg
    9.4 KB · Views: 6

dsnz

Well-known member
I used a similar test macro (other app because I have disabled calculator and popup message instead of vibration)
and it works but only with "legacy" option enabled
(but why ? 🤔 I don't like "legacy" mode, I like modern 😂)
 

dsnz

Well-known member
however I have another macro that triggers on Chrome launched and it has worked without legacy mode long time

now that I checked this macro again I see it doesn't work (I just didn't notice ..)

I am sure it must be the last update to 5.15.4 that messed with this trigger
 

roughnecks

Active member
I used a similar test macro (other app because I have disabled calculator and popup message instead of vibration)
and it works but only with "legacy" option enabled
(but why ? 🤔 I don't like "legacy" mode, I like modern 😂)
Well, you're right. I tested again legacy adding both checkboxes and it's working..
This a new bug, yeah.
 

dsnz

Well-known member
but as I said it worked for me without legacy mode before last update
so it's a new bug indeed !

(it's for you too a bug since it worked for you in past and now you must use legacy mode)
 

dsnz

Well-known member
a strange thing happened to me which perhaps is related and is also mentioned in another thread

I had to reboot (after 2+ days up)
in the boot process I received a md notification that accessibility permission is needed (first time I have ever seen this !)
on pressing the notification I was brought to the accessibility menu where md was already enabled

I tried again the test macro (without legacy mode) but still not worked

I removed accessibility and gave it again to md, but still nothing

strange behavior 🤔
 

roughnecks

Active member
I rebooted my phone, as I said earlier, while testing this but didn't receive any notification by MD. I checked accessibility on my own to make sure it was still set - and it was.
 

dsnz

Well-known member
still this issue and the one in


are related (and both related to the last update)

I am sure @MacroDroidDev will solve it in the end
let's have some patience
 

roughnecks

Active member
Can you tell how to open the accessibility menu by apps?
I am on MIUI 11 and in settings - accessibility I can see a menu with some apps which are granted permission, but I'm not sure it's the same menu MD opens when requesting accessibility permission..
 

Drberns

New member
I've been having the same issue in the last week or two (never had the problem before). I'm on latest MIUI 12 and every time I reboot I always get the "accessibility off" notifications, but turning them on again always solved every issue. Now everything is granted to macrodroid, but it fails to recognize launched apps. I don't think it's an issue with the accessibility services since other triggers that use them work fine.
 

dsnz

Well-known member
yes, good point

only application launched is not working
other triggers that use accessibility work fine

and some people get accessibility off notification on boot (and this not on every boot)


( your description is a bit vague and conflicting though at one point,

you say "but turning them on again always solved every issue"
but I'm sure your accessibility was already on and you did not have to turn it on, and of course no other issue was solved ...)
 

Mcrazy

Member
Hello!
We have a similar problem on several phones. (Samsung, Huawei).
Since the last update, the Application started/stopped trigger does not work.
 
Top