chaoscreater
Active member
I've noticed that in the latest MacroDroid version, one of my macros (which I haven't modified for months) suddenly stopped working.
This particular macro is really simple. It just has "Bluetooth Enabled" as trigger and "Bluetooth Disabled" as constraint. When my Bluetooth is off and I turn it on, it should trigger the macro to run, but it doesn't. It used to work fine, but I think it broke either in the last MacroDroid update or the current one. If I remove the "Bluetooth Disable" constraint, then it works fine.
I'm not sure if it's because of the recent fix from here that broke it?
I've tested and confirmed the issue on 2 different phones, both running Android 11.
This particular macro is really simple. It just has "Bluetooth Enabled" as trigger and "Bluetooth Disabled" as constraint. When my Bluetooth is off and I turn it on, it should trigger the macro to run, but it doesn't. It used to work fine, but I think it broke either in the last MacroDroid update or the current one. If I remove the "Bluetooth Disable" constraint, then it works fine.
I'm not sure if it's because of the recent fix from here that broke it?
Bug with system logs and bluetooth constraint
I'm noticing that on different phones, MacroDroid is occassionally showing the following wakelock: macrodroid:BluetoothTriggerReceiver I've pinpoint the issue down to the Bluetooth constraint. If I'm using a constraint like "Bluetooth Enabled/Disabled", then it somehow creates that wakelock...
www.macrodroidforum.com
I've tested and confirmed the issue on 2 different phones, both running Android 11.
Last edited: