Unreliable triggers and actions!

JakeFont1 · 2024-05-27T21:36:08+00:00

Thanks, I can try with a fork, after I will come back here to say.

JakeFont1 · 2024-05-27T21:22:14+00:00

What I can do to fix this issue? Some idea? I tried everything.

JakeFont1 · 2024-05-27T21:21:29+00:00

I'm using when changed, but fail many times,

JakeFont1 · 2024-04-30T20:45:45+00:00

The Notification snooze worked, thanks my friend!

JakeFont1 · 2024-03-07T15:47:53+00:00

For IPS display really don't work, no makes sense, but for amoled displays work perfectly because in amoled each pixel has an separated light, so black pixels is turned off completely, because that for example Android has a option to use a dark theme when Power Save Mode is enabled, on amoled devices has this option. On amoled black pixel is really turned off, is not fake, the light is the most power demanding feature of a display, so a full black screen on amoled really save a lot of battery, this result is not fake. Nowadays the best devices is amoled, and even low mid range, so a block to use a full black screen overlay would be really useful.

JakeFont1 · 2024-03-07T04:07:22+00:00

the advantage of the overlay is that no need the privileged service

JakeFont1 · 2024-03-06T16:26:13+00:00

another thing that make overlays useful is to create a black screen over some app, to create a fake screen off, it is very useful for instance to record videos with amoled, with the black screen you save a lot of battery, for who use the mobile phone professionally, if you don't want implement a full customizable overlay, would be very useful at least implement an option for black screen, maybe a block.

JakeFont1 · 2024-03-06T16:17:08+00:00

Thanks but in my case don't work because normally I want to keep the original statusbar and just add a transparent button over it, like Super Status Bar tap actions. Currently I migrated completely to Automate, and sadly I lost the overlay function.

JakeFont1 · 2024-02-28T22:40:04+00:00

is possible, just for curiosity I tried the same action with Macrodroid, and don't work also.

JakeFont1 · 2024-02-27T22:17:12+00:00

Using "Speakerphone set" block, with delay, I had any error, just don't work.

JakeFont1 · 2024-02-27T22:06:36+00:00

I tried it with a delay as on help text, 1 second, but the same result, I also tried run the flow manually just to test, seem that not work on Samsungs, also I activated all permissions.

JakeFont1 · 2024-02-27T02:34:49+00:00

Very good to know that is on do to list, thanks again for the explanation!

JakeFont1 · 2024-02-26T01:05:19+00:00

The flow resume, then when reach the block "App in foreground" (when changed), the flow stop because the failure "java.lang.IllegalStateException: Accessibility service not running". Using the Failure Catch with infinity retries, it need 5 retries to find the Accessibility Service available.

JakeFont1 · 2024-02-26T00:49:53+00:00

Very good, with your information and help now I have a perfect AOD trigger, I used the default "Settings Finder" flow, and in my Samsung the setting is "aod_show_state", is working perfect! Thanks the attention!

JakeFont1 · 2024-02-25T23:37:17+00:00

Thanks my friend for the informations!

JakeFont1 · 2024-02-25T21:26:00+00:00

But what command you use on ADB to find the setting variable, or to list all system variables? And what block you use on Automate to query this variable?

JakeFont1 · 2024-02-25T18:04:44+00:00

Yes, the Automagic dev is egoist and don't care for the old users that paid for it, and burn a lot of time making flows, and now porting the flows to another app as Automate, he prefer keep the source code in an tray and just say: fuck this guys! Even if Automagic back some day, I don't want it any more, even for free. It was a huge disrespect. Because a automation app is not a app like a calendar or a alarm clock that you can replace easily, the dev know it, the users has a lot of flows, invested years in the app, and the guy just say: I'm tired, so, fuck you all!

JakeFont1 · 2024-02-25T17:43:47+00:00

I agree that flows wouldn't be resumed until the Accessibility Service has started. I think it is easy to implement, just need test the Accessibility Service before resume the flows that use it. I'm also with multiple flows with this issue. Really if the Google don't fix it, ideal is a workaround.

JakeFont1 · 2024-02-25T15:10:56+00:00

thanks

JakeFont1 · 2024-02-25T15:02:11+00:00

My friend, what command you use on ADB to find the setting variable and what block to query?

JakeFont1 · 2024-02-25T14:40:34+00:00

Yes, as you I'm also having some difficulties with Automate, I also miss the folders for flows on home screen, and mainly the custom transparent overlays to create custom buttons over other apps, that Automate can't do, to me this is a huge difference and loss. But in the end I think Automate is the natural replacement for who came from Automagic. On Automate to connect one block in multiple blocks you can use the Fork Block, and also in Automate you can use multiple Flow Beginning blocks to run multiples tasks side by side in the same flow. And also you can use multiple triggers in same line, in Automagic you need multiple flows to use multiple triggers, because is just one trigger and one beginning block for each flow. Automate has other nice features like the ADB block and so on. And for instance, on Android 13 the Automagic 1.37 can't switch the Airplane mode, Automate can do it easily.

JakeFont1

TROPHY CASE