Rather, here in my rooted Nothing OS system, this "wait" action causes the device to go to sleep, and the lock screen pops up, and this occurs both under Tasker and MacroDroid. ![]() (2) If a Tasker or MacroDroid "wait" action is invoked, it doesn't simply perform a delay like it's supposed to do and which has always worked under all other OS's and devices that I've used. (1) If I set a "run on boot" task or macro to fire off during Tasker's or MacroDroid's booting (which always has worked on all other devices and OS's), I get the following error as Tasker or MacroDroid start running on my rooted Nothing OS system: Specifically, there are 2 problems that I've encountered so far when running Tasker and MacroDroid under Nothing OS, and no one in the official highly used Tasker forum has seen this problem under any other Android 13 OS's - nor under any other OS's on any other devices. Therefore, think this is specifically related to Nothing OS or maybe the code that's installed via rooting-via-booting. I have used Tasker under various other rooted devices for something like 10 years with no problems, and I have also used MacroDroid on many of those phones, as well, again with no problems. The problem is that neither the Tasker utility nor the MacroDroid utility work properly on my rooted Nothing 2 phone under that OS. I have encountered a problem with the rooted-via-booting version of OS 2.0.0 2.0.2a that I'm running on my rooted Nothing Phone 2 ( rooted via boot per the instructions and resources in this thread: ) ![]() See the message below at the following link for more details: ĮDIT: I originally described this solely as Tasker issues, but it turns out that the exact, same problems are occuring with MacroDroid. Although the errors manifest both in Tasker and MacroDroid, this actually seems to be due to GravityBox A13 badly interacting with the Nothing OS's System UI, and the problem is therefore also likely to manifest in other ways under Nothing OS. EVEN MORE UP-TO-DATE EDIT: It turns out that this issue is due to interaction between GravityBox A13 and Nothing OS.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |