Some macros are turned off automatically

[davisgodoy]

I have just been having the problem that some macros are turned off and this message appears in the system registry.

Has anyone been through this problem and what would be the solution???


Service Created 07:59:16 (ERROR} Could not enable macro: Cerato Jerson (java.lang.IllegalStateException: Maximum limit of concurrent alarms 500 reached for uid: u0a233, callingPackage: com.arlosoft.macrodroid) {ERROR}

 

[Jacob L]

The error is saying you have 500 alarms set. If you strip out personal details and post the macros here, we can rewrite them to be more efficient. Also, please check for updates to MacroDroid as there have been many bugs fixed.

You can make a macro that disables the macros you do not need, this might allow for those that you do need to be enabled.

 

[davisgodoy]

Greetings, I do not have 500 alarms or macros so I do not understand what it means with concurrent alarms 500 reached :-(

 

[Dm114]

Greetings, I do not have 500 alarms or macros so I do not understand what it means with concurrent alarms 500 reached :-(

...maybe a loop somewhere, setting alarms repeatedly?

 

[Pseudocyclic]

Greetings, I do not have 500 alarms or macros so I do not understand what it means with concurrent alarms 500 reached :-(

How many macros do you have?

 

[davisgodoy]

There are 118 Macros of which the 75, 12 and 4 Macros that are grouped do the same and only change the value that the Notification expects in the trigger.

 

[davisgodoy]

El error dice que tienes 500 alarmas configuradas. Si elimina los datos personales y publica las macros aquí, podemos reescribirlos para que sean más eficientes. Además, verifique las actualizaciones de MacroDroid ya que se han corregido muchos errores.

Puede crear una macro que deshabilite las macros que no necesita, esto podría permitir que las que sí necesita estén habilitadas.

There are 118 Macros of which the 75, 12 and 4 Macros that are grouped do the same and only change the value that the Notification expects in the trigger.

For example here I share the macro that does the same in 91 macros and where it only changes the value that expects to receive the notification in the Trigger and a date for according to it I sent sms and where the actions are the same

 

[davisgodoy]

How many macros do you have?

There are 118 Macros of which the 75, 12 and 4 Macros that are grouped do the same and only change the value that the Notification expects in the trigger.

 

[Jacob L]

I think the ideal will be for you to reduce the actions and constraints. I see there are if statements (si) and then you have individual constraints on the action that perform the same checks. try to check your logic and it may be fixed. Besides this, I am unsure what to suggest

 

[MacroDroidDev]

It's possible that your macros really have scheduled 500 alarms (which just means it wants to wake up the device at some point in the future). It's also possible that there is an issue somewhere that an alarm doesn't get cleaned up when it is finished with. If this is the case then I don't think it's a common problem so likely to just one case some where. I can perform some kind of audit to check all cases but it will take me a while because there are lots of places.

 

[davisgodoy]

It's possible that your macros really have scheduled 500 alarms (which just means it wants to wake up the device at some point in the future). It's also possible that there is an issue somewhere that an alarm doesn't get cleaned up when it is finished with. If this is the case then I don't think it's a common problem so likely to just one case some where. I can perform some kind of audit to check all cases but it will take me a while because there are lots of places.

I have gotten to eliminate several macros and established other conditions and it still keeps turning off the macros ........ However, if I migrate the macros to another cell phone, everything works fine and according to reading on the internet I am not the only one who has that problem anymore that many say it is because of the android version ..... what opinion do you have about it?

 

[Jacob L]

You had a lot of triggers at one time, maybe you should catch all events with one trigger and use if statements to determine the actions. Are you in the beta channel for MacroDroid? I wonder if some of the bug fixes will help you. Take a backup before joining though. Also, maybe making the other macros more efficient will reduce the alarms. I have a power saver at night that turns off entire categories and individual macros when I do not need them. If we could determine when an alarm is created we can mitigate this issue.

 

[MacroDroidDev]

@davisgodoy I don't know if you are able to do this but if you have ADB tools installed (i.e to do the adb hack) could you please run the following command:

adb shell "dumpsys alarm | grep com.arlosoft.macrodroid"

And then send the output of this to support@macrodroid.com

This should tell me where all the alarm allocations are coming from so if there is a leak somewhere there should be a large number of one particular type.

 

[Jacob L]

I tried the command in MacroDroid and it worked!

 

[davisgodoy]

@davisgodoy I don't know if you are able to do this but if you have ADB tools installed (i.e to do the adb hack) could you please run the following command:

adb shell "dumpsys alarm | grep com.arlosoft.macrodroid"

And then send the output of this to support@macrodroid.com

This should tell me where all the alarm allocations are coming from so if there is a leak somewhere there should be a large number of one particular type.

sorry for the delay, I was traveling ... I don't know how to execute this command on the cell phone ... if there was a guide on how to use the ADB tool and how to execute the command, I would appreciate it

 

[davisgodoy]

@davisgodoy I don't know if you are able to do this but if you have ADB tools installed (i.e to do the adb hack) could you please run the following command:

adb shell "dumpsys alarm | grep com.arlosoft.macrodroid"

And then send the output of this to support@macrodroid.com

This should tell me where all the alarm allocations are coming from so if there is a leak somewhere there should be a large number of one particular type.

ready! I managed to execute said command and this is the result by email

 

[MacroDroidDev]

Just to follow up on this thread, I have identified a possible issue with the day/month trigger where in some edge cases there could be a leak of an alarm. I have patched this in the latest beta. I can't say for sure this will stop the issue but it could be the solution.

 

[davisgodoy]

Just to follow up on this thread, I have identified a possible issue with the day/month trigger where in some edge cases there could be a leak of an alarm. I have patched this in the latest beta. I can't say for sure this will stop the issue but it could be the solution.

Thanks a lot!!! reset macros i removed to test ...

 

[davisgodoy]

Hello, apparently the same problem follows that some macros are turned off automatically. I have installed the version v5.12.3 Pro and I share the image of the same problem that just appears again. :-( :-( :-(