v5.49 - Feedback

[MacroDroidDev]

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.

 

[shlomo]

Yay! I just wanted to open a topic and ask for the addition of a Wear OS Complication Click trigger and here it is added

But I guess it requires waiting for the official release on Google Play for it to appear on the watch, right?

 

[Jacob L]

But I guess it requires waiting for the official release on Google Play for it to appear on the watch, right?

It does but since the warning is no longer in the release page, it must be coming imminently

 

[Jacob L]

I bet the vast majority of us don't want analytics so be best to disable them by default

 

[shlomo]

It does but since the warning is no longer in the release page, it must be coming imminently

What warning do you mean?

 

[Jacob L]

What warning do you mean?

There was a message in the release page saying we needed to wait for release, it has since been deleted

 

[johnskydraw]

I have an S24 Ultra Android 14, One UI 14, after installing this version the phone became impossible to use, because the touch does not work properly making it difficult to touch the screen, after trying a lot I managed to uninstall Macrodroid and the device came back.
After that I did a clean installation and started using Macrodroid normally, but after giving the adb commands, the problem came back, and it only resolved when I uninstall Macrodroid, please check this.

 

[Endercraft]

I have an S24 Ultra Android 14, One UI 14, after installing this version the phone became impossible to use, because the touch does not work properly making it difficult to touch the screen, after trying a lot I managed to uninstall Macrodroid and the device came back.
After that I did a clean installation and started using Macrodroid normally, but after giving the adb commands, the problem came back, and it only resolved when I uninstall Macrodroid, please check this.

Likely one of your macros was broken after the update.

 

[Endercraft]

I disabled crash logs and analytics, and I still see MacroDroid constantly accessing location. The location update rate is set to 5 minutes.

 

[MacroDroidDev]

There was a message in the release page saying we needed to wait for release, it has since been deleted

The new version of the Wear OS app is now available on the Play Store, so hopefully this should auto update and if not can be upgraded manually by visting the Play Store on the watch.

 

[MacroDroidDev]

I have an S24 Ultra Android 14, One UI 14, after installing this version the phone became impossible to use, because the touch does not work properly making it difficult to touch the screen, after trying a lot I managed to uninstall Macrodroid and the device came back.
After that I did a clean installation and started using Macrodroid normally, but after giving the adb commands, the problem came back, and it only resolved when I uninstall Macrodroid, please check this.

@johnskydraw I've not really got any idea how this could happen with the new version without any further information. If you are able to please share your full macro set directly to support@macrodroid.com (mentioning this issue) and I will try and recreate what you have seen. Thanks!

 

[MacroDroidDev]

I disabled crash logs and analytics, and I still see MacroDroid constantly accessing location. The location update rate is set to 5 minutes.

Sigh.... How are you determining this, are you certain you don't have any macros that use location enabled?

 

[Endercraft]

I just noticed something, the system says MacroDroid last accessed location at 7:57AM (it's 8:00AM now), but it still says that MacroDroid is using location.


Could it be that this is because MacroDroid is constantly listening from location updates from all apps, instead of regularly making a check by itself?

 

[MacroDroidDev]

How did that "sensitive permission reminders" popup appear?

 

[Endercraft]

 

[Jacob L]

I'm getting the same thing and I've disabled BOTH analytics and crash toggles. I DO have some wifi/location macros but not seeing any less location requests.

 

[dhj49er]

Attached are 2 screenshots showing MD location access times.
The first screenshot was taken when I was away from home and have macros with geofence triggers enabled using the default 10 minutes trigger update rate.
The MD location update is around 10 minutes, if you compare last update time and the time of day in the status bar.
The second screenshot was taken at home when I disable the macros with geofence triggers - pointless leaving them enabled.
The MD update rate is hours. I've just looked again and last access is still showing 8:20.

All the above is with crash and analytics reporting disabled ie both boxes ticked

So I'm not seeing MD constantly accessing location.

I have recently changed my phone and on my previous phone, Sony Xperia 5V, I was seeing the constant accessing whenever I enabled the geofence macros.

I will check with the crash and analytics reporting enabled over the weekend and report my findings here.

 

[johnskydraw]

@johnskydraw I've not really got any idea how this could happen with the new version without any further information. If you are able to please share your full macro set directly to support@macrodroid.com (mentioning this issue) and I will try and recreate what you have seen. Thanks!

Done!

 

[dhj49er]

Attached are 2 screenshots showing MD location access times.
The first screenshot was taken when I was away from home and have macros with geofence triggers enabled using the default 10 minutes trigger update rate.
The MD location update is around 10 minutes, if you compare last update time and the time of day in the status bar.
The second screenshot was taken at home when I disable the macros with geofence triggers - pointless leaving them enabled.
The MD update rate is hours. I've just looked again and last access is still showing 8:20.

All the above is with crash and analytics reporting disabled ie both boxes ticked

So I'm not seeing MD constantly accessing location.

I have recently changed my phone and on my previous phone, Sony Xperia 5V, I was seeing the constant accessing whenever I enabled the geofence macros.

I will check with the crash and analytics reporting enabled over the weekend and report my findings here.

I've managed to do more testing today.

With the crash & analytics reporting enabled I found that with geofence macros enabled, MD was constantly accessing location. However, disabling all the geofence macros resulted in the MD update rate in hours.

It would appear that disabling crash and analytics reporting has resolved the constant accessing of location observed when geofence macros are enabled, at least on my phone, a Honor Magic 6 Pro.

 

[GamBIT]

5.49 has become very freezy, I'm shocked.
The Selection Dialogs are very slow, between them now is a big pause. And they are drawn very slow too.
Loops/cycles have become very slow. A loop that took 1 second to run all the iterations at 5.48 now at 5.49 takes about 30 seconds or more! I used to have a very good performance at the last MD versions, so have to reinstall the previous one.
The first time MD has become fast about this summer, later it became slow again but this autumn it became very fast again, and I was happy with it and thought it is forever now. I have even deleted all the time pauses between the Selection Dialogs and inside the loops (I did it earlier as it could lead to the error and break the macro). Now I have no errors but it looks like MD itself is inserting that large pauses to many of the actions. And the performance is fallen down greatly.
Please fix it. Make MD fast again!