v5.47 - Feedback

[Dm114]

Hi, @Dm114,

As a provisional response,
a count variable was provided inside the loop and a weight was inserted based on the number of counts,
resulting in the macro working reliably.

FYI,

View attachment 10565
Best Regards,
Liner Seven,

Hi @LinerSeven,

Thanks for the suggestion but I would have to add this delay to a great number of my macros.

In addition, I discovered a big mess with some Date Shell Script commands I use in many of my macros. So I followed Jamie's suggestion to temporarily restore v5.46.10

Moreover I just had to change my "old" Android v9 device and couldn't find less than Android v12 (now automatically upgraded to v13 before I had time to stop upgrade process). I'm even thinking about a factory reset to remain on Android v12 but I'm a bit fed up with reinstalling everything...

 

[LinerSeven]

Hi @LinerSeven,

Thanks for the suggestion but I would have to add this delay to a great number of my macros.

In addition, I discovered a big mess with some Date Shell Script commands I use in many of my macros. So I followed Jamie's suggestion to temporarily restore v5.46.10

Moreover I just had to change my "old" Android v9 device and couldn't find less than Android v12 (now automatically upgraded to v13 before I had time to stop upgrade process). I'm even thinking about a factory reset to remain on Android v12 but I'm a bit fed up with reinstalling everything...

Wow, It is definitely hard work!!
I hope @MacroDroidDev picks up on this issue...

 

[Dm114]

Wow, It is definitely hard work!!
I hope @MacroDroidDev picks up on this issue...

I beleive that some of these "system" problems come from SDK change. If so, I'm afraid Jamie won't be able to do anything : he's not responsible of new SDK limitations or changes in behavior.

 

[MacroDroidDev]

Hi, @MacroDroidDev,

Macrodroid Beta v5.47.3 and v5.47.4 now generate 'Too many macros processed' errors.
It does not occur in the existing stave v 5.46.10.

Is the step count stricter in the beta version?

A sample macro is attached.
It is reverse geocoding and will be tested for users who care about non-Japanese services.

Best Regards,
Liner Seven,

This is almost certainly a result of all the text handling being faster with the new version that causes it to go over the threshold. I will look at tweaking the threshold to kick in at a less strict time.

 

[MacroDroidDev]

Ok, so I have multiplied by 10 the previous max number of invocations per second for the next update so hopefully the problem will go away for real world use cases.

 

[dhj49er]

I updated to v5.47 from v5.46.10 a couple of days ago. Initially using v5 47.4 Pro from the Play Store and then to v5 47.5 beta
Read screen content triggers stop working - so far it has happened once yesterday and again today.
I disable and re-enable MD and the read screen content triggers start working again.
Anybody else had read screen content trigger stop working?
I never had this issue prior to v5.47.

 

[LinerSeven]

Hi, @dhj49er,

I followed you and confirmed the phenomenon.

In my case,
the user assistance Macrodroid UI Sceen Operation could no longer be allowed.

That seems to be a limitation of Android 13+,

but previously I could allow it without any problems.



Best Regards,
Liner Seven,

 

[Dimlos]

I've only done a short-term test, but it seems to work fine on the Pixel 8 Pro.
I can turn on accessibility features on my Android 14 device without any issues.

 

[LinerSeven]

Hi,

I contacted @Dimlos and was able to resolve the limitation issue.

I had to allow restricted settings from 3point-Reader, which appears in the top right-hand corner of the screen when selecting the Macrodroid application from the user assistance.

I will follow up and see if I can reproduce the screen content.

Regards,
Liner Seven,

 

[dhj49er]

Hi,

I contacted @Dimlos and was able to resolve the limitation issue.

I had to allow restricted settings from 3point-Reader, which appears in the top right-hand corner of the screen when selecting the Macrodroid application from the user assistance.

I will follow up and see if I can reproduce the screen content.

Regards,
Liner Seven,

When the screen contents trigger stops working, I checked the accessibility settings and the 2 MD settings were on.

So I don't think my issue is related to accessibility settings.

Also, when I updated to v5.47.4 Pro the issue was immediately present. That's when I checked the status of the MD accessibility services. It started working after I disabled & immediately enabled MD from the MD home screen.

I have reset my phone last night & so far the issue hasn't returned.

 

[dhj49er]

I have done further testing and think I've identified the cause of the screen content triggers stopping.

Create a macro with a popup message trigger. This needs to the only instance of a popup message trigger.

Delete the macro and the screen content triggers no longer work.

Disable & Enable MD and the screen content triggers work.

The bug appears when the last popup message trigger is deleted.

So if you never delete all your popup message triggers, you shouldn't see this bug.

 

[Endercraft]

I am really impressed with the new handling of large strings. Before, doing literally anything involving them would cause the app to hang. But now I have only a few milliseconds of hangs at best, and a few seconds at worst (it used to be minutes!).

---

One new issue I found: the strlen magic text doesn't work for dictionary keys (it returns 0). When selecting a dictionary from the magic text screen, I don't get any option to select a string key, I just return back to the previous screen with the whole dictionary used as value (I mean if I have a dictionary named "texts" then it will select [strlen=texts] with no keys). If I add it manually to the magic text it doesn't work.

Another one (using the same example): the [size=texts[somearray]] doesn't work properly, instead of returning the size of the sub array (somearray), it returns the size of the top dictionary (texts).

 

[LinerSeven]

Hi,

I have additionally identified strange behaviour in Beta v5.47.5.
That is the Photo Taken trigger is firing on unintended occasions and the path of the photo that is retrieved in the magic text also has a strange value.

Could you please refer to the attached video and macros?

Best Regards,
Liner Seven,

 

[MacroDroidDev]

I am really impressed with the new handling of large strings. Before, doing literally anything involving them would cause the app to hang. But now I have only a few milliseconds of hangs at best, and a few seconds at worst (it used to be minutes!).

---

One new issue I found: the strlen magic text doesn't work for dictionary keys (it returns 0). When selecting a dictionary from the magic text screen, I don't get any option to select a string key, I just return back to the previous screen with the whole dictionary used as value (I mean if I have a dictionary named "texts" then it will select [strlen=texts] with no keys). If I add it manually to the magic text it doesn't work.

Another one (using the same example): the [size=texts[somearray]] doesn't work properly, instead of returning the size of the sub array (somearray), it returns the size of the top dictionary (texts).

I'm glad to hear the effort to change this has been worth it for the string speed stuff. It really was disastrously bad before!

I've looked into all those issues reported and they were just a few things I'd forgotten to implement fully so these will be fixed in the next beta. Thanks for reporting!

 

[MacroDroidDev]

Hi,

I have additionally identified strange behaviour in Beta v5.47.5.
That is the Photo Taken trigger is firing on unintended occasions and the path of the photo that is retrieved in the magic text also has a strange value.

Could you please refer to the attached video and macros?

Best Regards,
Liner Seven,

Thanks for reporting the issue. In this case it's not related to the beta as this issue almost certainly exists with previous versions as well. As such I'll add it in to my normal list of bugs to investigate in the future.

 

[KawaNinja]

Xiaomi 12 Lite (5G) Snapdragon 778G
NOT Rooted, ADB Hacks applied
Xiaomi HyperOS 1.0.8.0
Android 14

Everything except the "Magic Texts" is working fine with release v5.46.10.
Upgraded to v5.47 to solve the Magic Text issues (it solved the problem).
After installing the 5.47.xx the accessibility settings are grayed out and cannot be changed (Restricted Settings Error)
I didn't have this problem with my old phone (Xiaomi Redmi Note 10 PRO, MIUI 14, Android 13)

 

[Endercraft]

After installing the 5.47.xx the accessibility settings are grayed out and cannot be changed (Restricted Settings Error)

I cannot enable "Accessibility Permission" after updating to Xiaomi HyperOS. What do I do?

Can I enable "accessibility permission" via ADB?

www.macrodroidforum.com

 

[KawaNinja]

"Enable restricted settings" doesn't show in the menu of the released version (5.46.10), does it appear in the bata version?
Going back and forward to Beta and release is a time-consuming process, I have to fix many macros manually (Play FileName has to be re-pointed) to the file again)

 

[Endercraft]

Issue: when you click on end if/end loop, you are given the option to delete them, which doesn't delete the if or loop start and breaks the macro.

 

[dhj49er]

"Enable restricted settings" doesn't show in the menu of the released version (5.46.10), does it appear in the bata version?
Going back and forward to Beta and release is a time-consuming process, I have to fix many macros manually (Play FileName has to be re-pointed) to the file again)

View attachment 10622

I have the same issue and have adopted the following procedure when updating with a beta

1. Disable MD from the home screen - if you don't do this MD will generate a multitude of errors when the new beta runs because the accessibility services have been disabled.
2. Update MD using the new beta.
3. In phone system setting open accessibility.
4. Click on one of the MD services - clear the popup that states this a restricted service ...
5. In phone settings selects apps
6. Select MD
7. Click top right 3 dots
8. Follow the prompts for turning on restricted settings.
9. Repeat steps 3&4, except this time turn on all the MD accessibility services
10. Enable MD

It looks long winded but it doesn't take long and works without MD generating lots of error messages

Steps 3 & 4 are essential. Not doing them prevents access to the restricted setting prompts in MD.

I think you may not be doing steps 3 &4 and this is the reason for not seeing the restricted setting prompts.