Bug with system logs and bluetooth constraint

[chaoscreater]

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, which doesn't seem to make sense.

The other issue is with the system log. Sometimes, I'll click on the macro in the log and it takes me to a completely different macro. This is quite consistent across phones.

 

[MacroDroidDev]

I've just been checking through and I can see the "macrodroid:BluetoothTriggerReceiver" is incorrectly used as a label in the speak text action. I will correct this in a future release. Is there any chance this could be what is causing you to see this on your device? Apart from this it is only used in the Bluetooth Trigger so I don't understand how it can be caused by the constraint in this case.

I will look into the issue with the system log going to the wrong macro. I haven't noticed that myself but I will do some more testing to see if I can recreate.

 

[chaoscreater]

I've just been checking through and I can see the "macrodroid:BluetoothTriggerReceiver" is incorrectly used as a label in the speak text action. I will correct this in a future release. Is there any chance this could be what is causing you to see this on your device? Apart from this it is only used in the Bluetooth Trigger so I don't understand how it can be caused by the constraint in this case.

I will look into the issue with the system log going to the wrong macro. I haven't noticed that myself but I will do some more testing to see if I can recreate.

Ah yes, I do use speak text action as well and this happens around the same time when my Disable Bluetooth action (with Bluetooth constraint) is performed, so maybe the Bluetooth constraint is just a red-herring.

Regarding the system log issue, I think the way to replicate it would be to use "Run macro" action inside another macro. I create multiple template macros that do a bunch of tasks (actions) and I use these templates in other macros. In the system log, I can see that macro 1 is calling the template macro and if I click on the template macro, it shows me a completely different macro.

UPDATE:

Actually, I noticed that after charging my phone to 100%, I'll unplug it and shortly after, it'll show the Bluetooth trigger wakelock. No speak text is happening at this time.