Search results

I'm going to swear I saw a message that helper file version 9 or 19 was required. That's my story and I'm sticking to it.

Thank you. I could not see it for the trees.

May there please be a static link to the current helper apk, updated as needed, without 15 pages of comments? I apparently now need version 1.9 which I cannot find. In MD v5.37.12 Pro, Troubleshooting, there is a Get Helper File link. If v1.9 is in that thread, I haven't found it.

I got a little further. I was able to connect via wi-fi, but adb devices -l shows "unauthorized device". Normally, on my phone, there is a popup requesting validation of the adb connection. The laptop doesn't show that popup. I may be out of luck.

I've installed LineageOS, a port of Android x86, on a laptop. The "standard" Android x86 iso installed but got hung up in a loop during the welcome phase. Lineage works OK, so far. Doesn't run Angry Birds, wrong hardware. Doesn't run Microsoft Edge. Could be a 386 vs 686 thing. What it is...

Yes. I don't have a password on the app yet here I am on the forum 😀 Maybe there is a way to reset it from the developer's side.

If I were running a macro you guys might be right, but I was not. Neither do any of my macros, when they are running, which they were not, use or store much data. If I have three dozen variables I'd be surprised. None of them is a dictionary. This occurred,again not while running a macro, but...

I was only saving changes to macros. This is not action related. It is on the device I've been using for two years. Motorola G Power. I very well could have been adding waits to the macro when I clicked the save button, but I had added a constraint to an action.

This looks like one for our developer. I added a constraint to an action in several macros. It was slow, I saw this in the log. @MacroDroidDev

But you were right on the money 💰

I think we're talking about two different problems. How to handle restart and how to handle abnormal end. Abend, we called it... Restart is easy. We've discussed it here with trapping shutdown and initialize triggers. Multiple ways of doing that. All good Abnormal end, harder. The app may...

The macro I posted in my first response....

Perhaps you should make a feature request for this. It sounds useful.

Why do you think this is necessary? I'm sure you have a good reason. I'm not aware of any triggers due to Macrodroid restarting, at least I do not see any when I toggle the enable/disable switch. The only thing I know how to do is detect device start, as previously described. I don't see a...

I know that I can run another macro, so whatever actions currently triggered by macrodroid Initialized can be a new macro and executed after the special actions and the mode changed to Startup. You may have to rearrange some code or be creative about how you get that code executed. I'm no...

I believe that is exactly what would happen. On shutdown, set a mode that keeps all maroos but one from starting. How? Add a constraint to all macros but one. For that one unconstrained macro, triggered by Macrodroid Initialized, you remove the constraint.

You can detect shutdown and set a boolean or macrodroid mode, say Shutdown. Add a constraint to all macros "mode not Shutdown". They will never run when you restart.... In you start up macro, trigger on macrodroid initialized. Do your stuff. Change macrodroid mode from Shutdown to Startup...

Nothing I can see. I submitted a single macro in case you want to consolidate. Depends on your preference and style.

It is as far as I am concerned.

This hasn't been a problem since I last posted.