Plugins needs to be continually CONFIGURED to work

ReiWei

Member
I have tried to search for this problem, but was unable to find anything, so I apologize if it's already been covered.

Whenever I use a plugin (any plugin, but I'm trying to use the Blokada one currently), it will work the first time, and maybe work a few more times after that... but very shortly, often just the second time I try to use it, I have to "configure" it and then just hit ok/done. Nothing needs to be changed, and then it'll work for one, or a couple, more times.

This issue has been going on for the past two years, now... So I figured I'd finally ask about it. 😅

Thanks to any help that can come my way. 😁
 

MacroDroidDev

Administrator
Staff member
I have never heard of this issue reported before I'm afraid and never experienced it myself. I suspect this is yet another classic device battery saving issue. In case you haven't already seen it, please check the site dontkillmyapp.com for any advice related to your device type.

You should also ensure that you have disabled battery optimization from any plugin you are using. These typically run as services so it's likely that the OS gets into a state where it doesn't allow the service to run because it has decided it will drain you battery.
 

ReiWei

Member
Thanks for replying.

With other plugins I've used in the past, that may very well be... But with the blokada plugin, specifically, it acts very strangely on my phone.

I thought it always worked the first time after a configure, but that's because I always tested it with the relevant macro open... (btw, only one instance needs to be configured, so ie. I have one to turn it on and one to turn it off, but I only need to configure either one of them for it to start working again)

I just realized, though, that if I configure, then immediately close the macro, but stay in macrodroid, the plugin works most of the time, but not all the time. If I go to the home screen, with the home button, it never works...but if I go to the home screen with the back button, it usually works. It's very odd...

If I bring blokada to the foreground (it's always open in the background) it also works, seemingly at any time.

It might just be my phone that's funky, I'll try with another device when I get access to one later today.
 

ReiWei

Member
So I tried with another phone and exact same result. If you press the home button it stops working, seemingly no matter what. I can go to other apps and it works, I can back out of them, and it works, but if I hit the home button it, it stops working.

It also just stops working randomly at times, as well. But those above are consistent.


If there is no way to fix this weird behavior, is there another way to turn off and on blokada without opening it, using any nifty tricks? 😁


Thanks so much.
 

Endercraft

Moderator (& bug finder :D)
This seems to be a plugin issue and not a MacroDroid issue.. Can you confirm it works fine with another app like Automate or Tasker ?
 

ReiWei

Member
I probably can't, personally. I went to college for programming and still can't figure out Tasker. 😅 (it's a mystery to me why it's so much more popular than macrodroid). And I've never used automate... I'll try it out and see if I have any luck. 🤞
 

sampleuserhere

Active member
Maybe it's those plugin issue that starts appearing on Android 13? What's your OS?

Anyway, If you're on Android 12, I could test the plugin with Tasker if you want.
 

Dimlos

Well-known member
I don't know what version of Blokada you are using, but I verified this with Blokada 5.
This phenomenon is specific to Blokada and I found the answer in the Blokada community.

Sending the intent before sending the command from the plugin will ensure that Blokada can be controlled on/off.
 

Attachments

  • Macro.jpg
    Macro.jpg
    341.1 KB · Views: 8
  • Intent.jpg
    Intent.jpg
    325.7 KB · Views: 8
  • Blokada_Control.macro
    4.2 KB · Views: 3

ReiWei

Member
Oh wow, thank you very much. I really appreciate your time and help. 🙏😁

(for the record, not that it matters now, I am using Android 12 👍)
 

ReiWei

Member
Maybe it's those plugin issue that starts appearing on Android 13? What's your OS?

Anyway, If you're on Android 12, I could test the plugin with Tasker if you want.
I'm so sorry, I just realized I sounded a bit dismissive. I totally didn't mean to, I really appreciate your offer to help, thank you very much.

For the record, it's working perfectly great, now (except my current phone opens Blokada when I turn it off, but that's not a big deal. It doesn't open it when I turn it on, btw, in case anybody cared 😁)
 
Top