V5.46 - Feedback

Status
Not open for further replies.

MacroDroidDev

Administrator
Staff member
For obvious bugs, please use report a bug in troubleshooting section with a clear description.

For other issue and discussions (related only to this beta), please leave all feedback here.
 

Dm114

Well-known member
I just downloaded v5.46 from the link but it doesn't want to install on my Android v9 device... ¯\_(ツ)_/¯
 

Endercraft

Moderator
Maybe v34 is incompatible with your device. I'll check...

I didn't see any reference to that so it could be what @Jacob L said. What's the error you're getting?
 

Jacob L

Moderator (Lawsonator)
MacroDroid is now saying not title and notification instead of the actually notification title and notification content!
 

Dm114

Well-known member
MacroDroid is now saying not title and notification instead of the actually notification title and notification content!
Exactly! I wanted to investigate a bit more before pointing this issue but it happens on "old" macros I've been using for years without modifying them.
 

EDawg

New member
For obvious bugs, please use report a bug in troubleshooting section with a clear description.

For other issue and discussions (related only to this beta), please leave all feedback here.

Hi there,

I updated my app to this version to work with Shizuku.

I get Shizuku to run on boot already and it works with aShell.

However when I try to run a script with Macrodroid with Shizuku selected it gives an error that Shizuku hasn't been initiated yet
 

dhj49er

Well-known member
When MD is disabled should this event be recorded in the system log? Likewise when MD is enabled.
I seem to remember these events were recorded in the log prior to 5.46, but I could be wrong.
The reason I ask, I found MD disabled this morning ( I installed 5.56.2 yesterday), I don't have any recollection of disabling it and there was no entry in the system log recording the event.
 

MacroDroidDev

Administrator
Staff member
Hi there,

I updated my app to this version to work with Shizuku.

I get Shizuku to run on boot already and it works with aShell.

However when I try to run a script with Macrodroid with Shizuku selected it gives an error that Shizuku hasn't been initiated yet

You are probably not being prompted correctly to grant permission to Shizuku in some cases. I will try and improve this in the next beta update.
 

EDawg

New member
You are probably not being prompted correctly to grant permission to Shizuku in some cases. I will try and improve this in the next beta update.
Tried the newest beta, still same issue.

Only time it works is when Macrodroid toggle is disabled in Shizuku Application Management section. Then go to macrodroid and it requests to be granted to use Shizuku and click allow all the time. Once I reboot it stops working again until I toggle it off and redo the granting
 

EDawg

New member
Tried the newest beta, still same issue.

Only time it works is when Macrodroid toggle is disabled in Shizuku Application Management section. Then go to macrodroid and it requests to be granted to use Shizuku and click allow all the time. Once I reboot it stops working again until I toggle it off and redo the granting
So. After restarting Shizuku I need to force stop Macrodroid (Device Admin disabled to be able to force stop) and give accessibility permissions again then it works.

Figured this out after testing AShell without Shizuku running then starting Shizuku, I had to reload AShell for it to work. Looks like the apps to get reloaded after starting Shizuku to work properly
 

Jacob L

Moderator (Lawsonator)
Tried the newest beta, still same issue.

Only time it works is when Macrodroid toggle is disabled in Shizuku Application Management section. Then go to macrodroid and it requests to be granted to use Shizuku and click allow all the time. Once I reboot it stops working again until I toggle it off and redo the granting
Make sure Shizuku is running after reboot. It says running or not at the top. It can't run itself unless rooted
 

EDawg

New member
Make sure Shizuku is running after reboot. It says running or not at the top. It can't run itself unless rooted
No, I know. I have a setup that runs Shizuku after booting. And it is running. I verify that

It's running as aShell works directly after boot that requires Shizuku to run as well.

Once my device boots, Macrodroid enables Wireless debugging(if connected to my wifi), then runs an Automate Flow to Start Shizuku. This part all works

The problem is that Macrodroid starts first then Shizuku is started after. I need to reload Macrodroid(force stop and give accessibility permissions again) for it to work.

Other option is toggle Macrodroid off in the application management section in Shizuku and grant it to allow all the time again and give accessibility permissions then it also works..

Either way that you do it, Macrodroid is killed than reloaded for it to work. Either manually or through Shizuku Application Management settings
 
Last edited:

EDawg

New member
No, I know. I have a setup that runs Shizuku after booting. And it is running. I verify that

It's running as aShell works directly after boot that requires Shizuku to run as well.

Once my device boots, Macrodroid enables Wireless debugging(if connected to my wifi), then runs an Automate Flow to Start Shizuku. This part all works

The problem is that Macrodroid starts first then Shizuku is started after. I need to reload Macrodroid(force stop and give accessibility permissions again) for it to work.

Other option is toggle Macrodroid off in the application management section in Shizuku and grant it to allow all the time again and give accessibility permissions then it also works..

Either way that you do it, Macrodroid is killed than reloaded for it to work. Either manually or through Shizuku Application Management settings
I did a little workaround to get it working for me.

Once booted, Macrodroid enables Wireless debugging, then runs my Shizuku Automate flow that starts Shizuku, then force stops Macrodroid with a shell command, then once Macrodroid relaunches it self I get the Accessibility permissions required notifications which then initiates a Tasker task to automatically re-enable the 4 Macrodroid Accessibility permissions.
 

Winny57

Active member
Hello everyone 🖖

I have the problem that when I try to "reduce or open" the macros via the button at the top right it forces close on the macrodroid application
 
Status
Not open for further replies.
Top