V5.52 - Feedback

Status
Not open for further replies.
dhj49er

dhj49er

Well-known member
Installed v5.52.1 beta and I can confirm the Bluetooth triggers are working.

Thank you for quickly resolving the issue.
 
G

GamBIT

Active member
dhj49er said:
I think it depends on the phone & the restrictions added by the device manufacturer.
I have had phones that it happens when installing over a beta and phones that it didn't occur.
I seem to remember a Xiaomi phone I had briefly did.
My current phone, a Honor, does not when installing over a beta.
Click to expand...
It depends on Android version and a source of apk.
In A12 and earlier everything is running with ease.
In A13 and further If MD is from GP, apk is signed by Google and usually is installed and running immediately. But the beta-apk from this forum (and any other non-GP source) isn't signed by Google, so you have to try enable the accessibility helper first, getting the 'restricted' error message, then go to the MD app info, find there and enable the new 'allow restricted' item and then try again to enable the helper (now with success).
This way is for ANY android app that isn't installed from GP and has its helpers for accessibility in Android13 and later. A security feature of this OS.
 
dhj49er

dhj49er

Well-known member
GamBIT said:
It depends on Android version and a source of apk.
In A12 and earlier everything is running with ease.
In A13 and further If MD is from GP, apk is signed by Google and usually is installed and running immediately. But the beta-apk from this forum (and any other non-GP source) isn't signed by Google, so you have to try enable the accessibility helper first, getting the 'restricted' error message, then go to the MD app info, find there and enable the new 'allow restricted' item and then try again to enable the helper (now with success).
This way is for ANY android app that isn't installed from GP and has its helpers for accessibility in Android13 and later. A security feature of this OS.
Click to expand...
My Honor phone is on Android 15 and doesn't have the issue updating a beta from here.
 
W

Wibbly

Active member
@MacroDroidDev Does 1.52.1 attempt to further resolve an issue after 1.52.0 that the Notification Received trigger misses some notifications when the notications come in very rapidly, say, every 0.5 sec or less, even when Prevent multiple triggers is unchecked?

This isn't a new issue & was a problem with 1.51 (already reported). I wasn't clear from the change log, but suspect you've not had a chance to look at this yet.
 
MacroDroidDev

MacroDroidDev

Administrator
Staff member
Wibbly said:
@MacroDroidDev Does 1.52.1 attempt to further resolve an issue after 1.52.0 that the Notification Received trigger misses some notifications when the notications come in very rapidly, say, every 0.5 sec or less, even when Prevent multiple triggers is unchecked?

This isn't a new issue & was a problem with 1.51 (already reported). I wasn't clear from the change log, but suspect you've not had a chance to look at this yet.
Click to expand...
No at the moment I am unsure of what to do about this and I don't have an easy way to recreate it. I will try further to fix in 5.52 if I can think of anyting else to fiddle with.
 
MacroDroidDev

MacroDroidDev

Administrator
Staff member
LF0 said:
Hello,

I just installed version 5.52.1 and found another issue while testing floating text. When enabling "Scrolling Text," the background width is affected by the Magic Text and variable names. The longer the name, the wider the background.

As a result, if the actual displayed content is short, the text does not scroll properly, and there is a large empty space in the background.
Click to expand...
Thanks, I shall aim to improve this!
 
W

Wibbly

Active member
MacroDroidDev said:
No at the moment I am unsure of what to do about this and I don't have an easy way to recreate it. I will try further to fix in 5.52 if I can think of anyting else to fiddle with.
Click to expand...
Hmm. I tried creating a couple of test macros using MD to generate notifications in a tight loop and triggering off the notifications. I couldn't get it to miss any of those notifications with 100 of them coming in to the User log over 15 seconds. Maybe the problem is with the source of the notifications I'm using elsewhere skipping some, even though that app's display updates for each one. (That source is Google Maps as it updates the distance to the next turn, when close to the turn)
 
LinerSeven

LinerSeven

Well-known member
@MacroDroidDev ,

From v5.52.1 Release Note at today,
>Fixed issue where exostomg drawer ...
exostomg = extoming...

Yes or No?
Which is it?

I'm translating the beta release notes for the Japanese...

Regards,
Liner Seven,
 
Last edited:
A

alexhee

Member
MacroDroidDev said:
If you install the beta over the existing install then you should not hit this problem. I think it only happens when you clean install from outside the play store.
Click to expand...
No. Existing version is from Play Store, I just download the file from here & install but had this issue. Before this version 5.52, all done with no issue.
 
G

GamBIT

Active member
dhj49er said:
My Honor phone is on Android 15 and doesn't have the issue updating a beta from here.
Click to expand...
It is very strange but may be a part of the Honor OS that isn't now a pure Android. On the stock Android since A13 you cannot simply enable the accessibility helper if it isn't signed like the GP apps are. It's made due to prevent installing a malware outside the trusted sources like GP.
 
dhj49er

dhj49er

Well-known member
GamBIT said:
It is very strange but may be a part of the Honor OS that isn't now a pure Android. On the stock Android since A13 you cannot simply enable the accessibility helper if it isn't signed like the GP apps are. It's made due to prevent installing a malware outside the trusted sources like GP.
Click to expand...
An update.
After installing v5-52.1 I had an issue where the WiFi disconnect trigger stopped working, which was resolved by doing a fresh install of v5-52.1.
This install had the restricted accessibility issue, which I hadn't had previously.
I have Shizuku installed and may have used the "install with Options" app to install an earlier beta update with the allow restricted permissions enabled. That could explain why I haven't had the issue.
I know I didn't use it for the fresh install and had the issue.
I will use Install with Options with the allow restricted permissions enabled to install the next beta and will let you know the outcome!
 
A

alexhee

Member
An issue when backup file made on latest beta version 5.52 cannot be used or restore on 5.51 & below. It will make the MacroDroid cannot be launched after restored.
 
Jacob L

Jacob L

Moderator (Lawsonator)
alexhee said:
An issue when backup file made on latest beta version 5.52 cannot be used or restore on 5.51 & below. It will make the MacroDroid cannot be launched after restored.
Click to expand...
I guess that's because of the home screen tiles. One was removed and another added
 
Jacob L

Jacob L

Moderator (Lawsonator)
"Twitter account" button in settings is broken! Thank goodness. I haven't bothered with Twitter for years
 
JoeReMi

JoeReMi

Member
I very much appreciate the extra information that the enable/disable trigger action displays! Would it be possible to do something similar with the UI Click trigger?

There is no way to tell at a glance whether it's a long or short click. I have a macro that contains both and the text clicked is identical so I would really like this :)
 
C

cadguy

New member
Jacob L said:
That's because you've installed it from the forum. Android has introduced new annoying security. What you need to do is install something from the play store if you can, SD Maid SE for example. Don't need to open it. Head to MacroDroid > settings > keep accessibility services alive > SD Maid and MacroDroid. Go to system settings > accessibility and toggle SD Maid on and then off. Go back a page and MacroDroid should now be enabled. You no longer meed SD Maid, although it's a great tool. To fix this in the future, there's an app called "Install with options" which will set MacroDroid as being installed by the play store which will fix this
Click to expand...
Thanks for posting proposed fix. This however didn't work for me on S22 Ultra running android 14
 
Status
Not open for further replies.
Top