Scripts not executed in standby, only after phone is activated / unlocked or with big delay

[HerrBert233]

I noticed that Easer does not execute scripts when the phone is in standby. Only if I actively use my phone (unlocked, display on), the scripts are properly executed.

For example I have a tree like this: When after 7 am (condition) -> When Wifi is off (condition) -> When at home (by cell location) (condition) -> Activate Wifi (scenario)

Now I checked my phone at 7:56 am, and I could see that the Wifi was just about turning on. The activity log confirms this: Wifi was turned on at 7:56 am, not 7:00 am. I noticed this multiple times now, also after coming home, where wifi didn't turn on immediately, but only after I unlocked my phone.

P.S. Sometimes I noticed the events are eventually executed with a great delay. For example today I didn't touch my phone until 9 a.m., Wifi was active at that time and the activity log shows it was activated at 8:36 a.m. So a big delay from the scheduled 7 a.m. but still before I unlocked the phone.

Battery optimization for Easer is disabled. No energy saving mode used. LineaseOS 18.1, rooted. Easer 0.8.2.3.

Otherwise, really awesome app!

[renyuneyun]

Thanks for reporting. I've heard this another time from another people, but not from most others. (And sorry for the delay. It was quite some busy and anxious time in the last few months.) The interesting thing is that I'm not experiencing anything on my phone (OnePlus 6 with OxygenOS 11.1.2.2, Android 12). Of course, I'm using cutting-edge one, which is more similar to the beta version...

There are several possibilities. Hope with the community we can rule them out one by one and find the right problem:

1. [ ] Easer's problem:
   1. [ ] Easer is not responding to ANY condition/event when phone is locked/phone is stand-by.
   2. [ ] Some specific condition/event does not work when phone is locked/phone is stand-by.
   3. [ ] A specific way of chaining Scripts will make it not evaluate correctly.
2. [ ] LineageOS's problem:
   1. [ ] It does not broadcasting the right event (or calling the right callback/handler) when phone is in stand-by, while it should.
   2. [ ] It has a special design which can broadcast, but requires additional set up.
3. [ ] OOS's problem:
   1. [ ] It should not broadcast the events when phone is in stand-by, but it did.

Let's assume this is Easer's problem first. Could you please try the following and report your findings:?

1. Use the beta version, and see if it happens (you can export and import the data).
2. Simplify the Script chain, and see which ones will not be triggered on stand-by.

[mddvul22]

I appear to have this problem. In my case, I'm trying to get Easer to open my Pandora app when my phone connects to my car's bluetooth. With the non-beta version, it works if the phone is awake. But not if the phone is "sleeping" in my pocket. I did just try @renyuneyun 's request that of the beta version (from F-Droid). However, for me, the beta version crashes when I try to select a bluetooth connection. My phone is running Lineage OS for Microg version 19.1 (Android 12).

Also, my script chain is simpler: If BT connection is established, then open Pandora.

[primesun]

I seem to have a similar issue. Using Easer 0.8.2.3, on a pixel 6a.

My script is fairly simple:

• A condition of day of the week, with all days enabled.
• A time event, with a specific time configured.
• And the profile is an HTTP GET request.

I ran 4 tests.

• The first time, Easer sent the GET request ~10 minutes late, with the phone being locked and unused.
• The second time, Easer sent it ~3 minutes late, phone also locked and unused.
• The third test Easer did not send the request, even after ~20 minutes, with the phone being unlocked for a few minutes, and locked for the remainder. I did not wait to see if it would eventually work.
• The fourth test it sent the request ~11 minutes late, with the phone being locked and unused.

[carlo318]

I have a similar issue with Easer 0.8.2.3, on a OnePlus Nord with Android 12.

In my case, the script I have made, sometimes doesn't run at all, with no apparent reason. I have tried when phone locked or in standby, but sometimes ignores the script also when phone is active and unlocked. I have tried with App closed (even if the notification says it is runnin in background), or with App open in background. I cannot figure out what is the condition which makes it run. The script is:

• Event: on receiving an SMS containing specific Text
• Profile: send the Text to a WebPage Link in QueryString.

I thought it was because the webpage is slow answering, but it is not the case, since in activity history there is nothing. (I have never experienced the delay). Anyone with similar issues? Thankyou.