For clear bugs, please use report a bug in troubleshooting section with a clear description.
For other issue and discussions, please leave all feedback here.
For other issue and discussions, please leave all feedback here.
V5.29 - Feedback
- Thread starter MacroDroidDev
- Start date
Endercraft
Moderator (& bug finder :D)
S+1
dhj49er
Well-known member
I have changed Airplane mode actions to use the adb hack option and have an initial observation.
The airplane mode on or off action using the adb hack option appears to take longer to change the mode.
I have macros where I need to turn on WiFi after turning on airplane mode. Previously using MD as digital assistant app a wait of 500ms was sufficient for the WiFi on to work reliably. Just changing the airplane mode to use the adb hack and WiFi didn't turn on. Progressively I tried different wait times until I found 1.25s worked reliably.
This may not be an issue for many, but I thought it would be useful to point out the extra time required for those with similar macros.
The airplane mode on or off action using the adb hack option appears to take longer to change the mode.
I have macros where I need to turn on WiFi after turning on airplane mode. Previously using MD as digital assistant app a wait of 500ms was sufficient for the WiFi on to work reliably. Just changing the airplane mode to use the adb hack and WiFi didn't turn on. Progressively I tried different wait times until I found 1.25s worked reliably.
This may not be an issue for many, but I thought it would be useful to point out the extra time required for those with similar macros.
Last edited:
FrameXX
Well-known member
I already reported it. No text manipulation in 5.29.0 is getting saved into output variables.
Endercraft
Moderator (& bug finder :D)
I also reported it just after updating
This is the reason my weather here is SSSScattered clouds. It may have changed ?
Yes it did. SSSSSScattered clouds.
Endercraft
Moderator (& bug finder :D)
I looked at it and saw no duplicate.
Endercraft
Moderator (& bug finder :D)
SSSSSSScattered clouds. Incredible weather ! Maybe there are snakes in the clouds ?
dhj49er
Well-known member
In addition, I have 2 methods of turning on WiFi in airplane mode. One is UI based to click on the WiFi icon and the other uses adb shell command.
The 1.25s wait mentioned above was needed using the WiFi UI method.
I have found that the wait for the WiFi adb shell method is 500ms.
The macro action steps in my macro are
Airplane Mode On
Wait (1.25s or 500ms)
Run Macro WiFi On (UI or adb)
Jacob L
Moderator (Lawsonator)
I see this twice: com.arlosoft.macrodroid.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION using this app: https://play.google.com/store/apps/details?id=com.wt.apkinfo
FrameXX
Well-known member
I am suspicious that both lines are needed, since they are not exactly the same and use different tag and attributes.
XML:
<permission android:name="com.arlosoft.macrodroid.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION" android:protectionLevel="0x2" />
<uses-permission android:name="com.arlosoft.macrodroid.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION" />Endercraft
Moderator (& bug finder :D)
SSSSSSSSScattered clouds.
I've created a new V5.29.1 release
Of course the V5.29.0 release is still waiting in review on Google Play. I cannot pull this release as it needs approval for some new rule for accessibility service usage and if I pull it now I go the back of the queue again. I have no idea how much longer this is going to take, but I will queue up V5.29.1 for Google Play (or whatever release I'm up to then) if and when this finally gets approved.
The manifest stuff mentioned above is nothing to do with me and is added as part of the Android build system based on the compile SDK version I am now using.
Of course the V5.29.0 release is still waiting in review on Google Play. I cannot pull this release as it needs approval for some new rule for accessibility service usage and if I pull it now I go the back of the queue again. I have no idea how much longer this is going to take, but I will queue up V5.29.1 for Google Play (or whatever release I'm up to then) if and when this finally gets approved.
The manifest stuff mentioned above is nothing to do with me and is added as part of the Android build system based on the compile SDK version I am now using.
Endercraft
Moderator (& bug finder :D)
I installed it with success. Note that arm64 doesn't work for all devices :
Maybe it changes depending on the version ?MacroDroidDev said:
Personally I am not able to install any universal package of MD.
Endercraft
Moderator (& bug finder :D)
It seems wait action still waking macro after macro was disabled was fixed, but I'm not sure if this was in v5.29 or v5.29.1
Snurre
Well-known member
No problem here
Just a heads up that after about 8 days of the app being in review, the update has been rejected for a whole new reason.
This very forum is apparently violating the user generated content policy because it doesn't:
Allow users to flag or report objectionable content. (It does)
Allow user to flag or report abusive users. (It does)
Allow users to block abusive users. (I'm not sure the forum even supports this).
There is also some additional requirements about how I need to clearly define the policy with respect to objectionable content and behavior.
It seems like every year Google are determined to make life harder for developers and make publishing apps a continuous struggle. I will now enter a cycle where I make some adjustments, wait about a week for another rejection, talk to some more bots and repeat.
I need time to absorb all this but my first thought is that I will have to make the forum take you out to the chrome browser so I can clearly prove that it is an external to the application functionality.
I probably also have to think about the template store as this will surely come under the same umbrella and will no doubt be hit with the ban hammer at some point in the future.
So in conclusion don't expect to see this release on the Play Store any time soon and don't expect much in the way of new features for the forseeable future as I spend all my development time firefighting this nonsense.
This very forum is apparently violating the user generated content policy because it doesn't:
Allow users to flag or report objectionable content. (It does)
Allow user to flag or report abusive users. (It does)
Allow users to block abusive users. (I'm not sure the forum even supports this).
There is also some additional requirements about how I need to clearly define the policy with respect to objectionable content and behavior.
It seems like every year Google are determined to make life harder for developers and make publishing apps a continuous struggle. I will now enter a cycle where I make some adjustments, wait about a week for another rejection, talk to some more bots and repeat.
I need time to absorb all this but my first thought is that I will have to make the forum take you out to the chrome browser so I can clearly prove that it is an external to the application functionality.
I probably also have to think about the template store as this will surely come under the same umbrella and will no doubt be hit with the ban hammer at some point in the future.
So in conclusion don't expect to see this release on the Play Store any time soon and don't expect much in the way of new features for the forseeable future as I spend all my development time firefighting this nonsense.