Search results

Is it possible to save the system log as HTML like sharing log? maybe even so that it happens in the background and not via clicking

It shows that there are problems with the trigger because it is not fixed and it was done right there I also have that with variables that they shouldn't exist, but there is the variable and sometimes there is an error that he couldn't find the variable, which is normal if the variable isn't...

the problem is still there in Version 5.42.6

- Dialog selection does not save the value in string - Text input with a string also displays True and false

Oh, and what's the best way to figure out which macro is responsible?

But why even if MacroDroid is disabled?

Maybe someone here can help me figure out why it is like that. For a week now, loading the Macros category always takes 3 seconds, no matter what I do in connection with the category, I create macros and save it, it takes 3 seconds, if I go to Macros from the home page, it takes 3 seconds again...

Ich kann dir zwar nicht direkt helfen, aber meine Recherche hat ergeben das man #31# Rufnummer machen muss, damit man anonym anrufen kann

Try deactivating the sound playback and see if it still turns off

I actually didn't know that. I have Android 9, so it's a bit older

I use the “Screen Coordinates” app for cases like this.

No problem ^^ You can also do this with the Selection dialog (see picture) then you have a button and it still works

or as a picture

I think that's what you wanted

No problem, I have the solution for you

Do you happen to speak German or just English?

I hope this gets fixed urgently, it's extremely annoying

If anyone else has problems with this, it's a bit annoying (See GIF)

Does it make a difference if I move variables into a dictionary so that the global variables look better or does it take longer to load or are more likely to cause problems?

I suspect that it was due to a macro that was executed a few times, to be exact, around 270,000 times because I hadn't installed a pause. At least it came shortly afterwards, but in the meantime I've been able to solve the problem by uninstalling the app and reinstalling it again and since then...