Recently, I learned about Android Automatization (e.g., with Tasker, LLamaLab, and MacroDroid). However, several hours of Googling have not led to the desired automatization routine. Perhaps somebody has already observed a similar problem or challenge and has already found a solution. The configuration: Lineage OS 21, Pixel 4a, Not Rooted The desired automated blocks are(without explaining why): 1. Download the Lineage OS update if it is available and install it. The problem with this step is that it requires a reboot. 2. Open the app store and update the apps and app store. Wait for completion, and close the app store. Note that I have several different app stores for different apps. 3. Open the antivirus, update the databases, scan everything, wait for completion, and close the antivirus. 4. Open Termux, update packages, synchronize some files with git, wait for completion, and close Termux. 5. Copy some files to Google Drive, wait for completion, and close Google Drive. These steps are repeated weekly or monthly, so automating them would make things easier for me. If you have ideas on some particular steps but not for all, your response is appreciated regardless. Whether the approach requires root or not is important.

I need to set up an app-killing service for **unrooted** Android 9 devices using [Automate](https://llamalab.com/automate/) . The service has to launch automatically at device start and keep sending kill commands to selected system (!) services at regular intervals unless said services are in focus/in the foreground. Unfortunately, setting up and running Automate seems unnecessarily [cumbersome](https://llamalab.com/automate/doc/adb.html) . I have used adb extensively, so no problem there. However, [step 5 in the setup manual](https://llamalab.com/automate/doc/adb.html#setup) says > 5. On the PC, execute the shell command adb tcpip 5555. **This step has to be repeated after every device reboot.** [Also](https://llamalab.com/automate/doc/adb.html#privileged_service) : > Once paired/authorized the service will start automatically when it’s first used, e.g. by a block using it, then run in the background **until** the system kills it, **the device is rebooted**, or the app is uninstalled or updated. Having to hook up a *mobile* device to a PC after each and every reboot (e.g. due to empty battery) is completely impractical and contradicts the use of Android itself. Is there a way to set up Automate either 100% locally from within Android, or at least only once from a PC at the very beginning and then have the app run automatically even after a device reboot? I have already set up a simple Automate flow as a minimal example and granted all necessary privileges, such as access to the SD card, executing shell commands, and access to Samsung accessibility service. Also, USB debugging is enabled in the developer options. But when running the flow, I get the following errors in the log output: Flow beginning Delay App in foreground? App kill Failed to start privileged service java.util.concurrent.CancellationException: Please execute: sh /sdcard/Android/data/com.llamalab.automate/cache/start.sh java.util.concurrent.TimeoutException: Service startup timeout Stopped by failure

How can I allow an app to automatically take screenshot? I'm not talking about apps disabling screenshots on them, I can take screenshot of the thing manually, but I'd like to automate it. I use the app Automate, which has a screenshot action, but when I run it, a dialog appears asking me if I want to allow the app to see everything what is on screen, and that happens every time. I basically want to autoapprove this dialog. Is there a way to do that? Thanks

How do I programmatically set the Minimum Width in Android's Developer Options from Llamalab's Automate app? I use Your Phone on Windows 10 to view my phone's screen. I maximize the window to get the full size of my monitor. With a minimum width of 1500, the phone is kind of like a tablet. I would like to set the Minimum Width to 1500 when viewing the screen on my monitor and 486 (the default?) when viewing the screen on my phone. Using the "Settings finder" flow from the Community, it told me the following: Category: secure Name: display_density_forced Value: 188 I then used a System setting set block in Automate. This threw an exception because Automate does not write permissions. I connected my phone to my PC via USB and ran the following command to grant write permissions to Automate: adb shell pm grant com.llamalab.automate android.permission.WRITE_SECURE_SETTINGS Now the System setting set block does not throw an exception. However, changing the setting via the block does nothing to the UI. If I run the following command on my PC, then the UI changes. adb shell wm density 188

I am struggling to count the time difference between the next new year, 0 o'clock at January 1 and the current time and to obtain the number of days, hours, minutes and seconds. According to the LlamaLabs help, Now gives a unix timestamp for the current time and date() a timestamp of for the specified time date. However, computing the number of days, hours etc. in the obvious way from the timestamps doesn't yield the expected result. I also don't find appropriate blocks for the flow. How would you solve that in Automate?

I'm responsible for an automation lab with many Android phones connected to Linux servers via adb for testing. We have an issue where devices will sometimes disappear from adb which means that someone has to manually find the phone and reboot it before it will come back. I'm interested in finding solutions to reduce this need for manual intervention. One idea I had was that we could periodically send a ping to the device from the host and if the device did not receive a ping in a specific period it would assume it was disconnected and reboot itself. The issue is that we cannot root these phones so I'm not sure if that is possible. I do however, have the ability to write and install my own apps on the devices and I don't need to worry about any playstore rules. Is there anyway I can achieve this without rooting the device?

I'm using the app 'Automate', in order for it to work I have to turn it on in Settings/Accessibility: But after a short time I doesn't work anymore and it's back on 'off' again. I think it may have something to do with my battery saving mode because I've seen it in a different question but no idea how to fix it because my gui doesn't have the same properties as suggested in an answer I've seen somewhere else. I'm using an Honor 9 phone from Huawei, my software versions: So my question is: **How can I prevent my phone from changing the app's accessibility setting without giving up on the battery saving feature (if that is the reason for it)?**

I use several home launcher apps. At my school, i use system launcher.And at my home or any other cases,i use nova launcher. And,ther are secret apps that i don't want to show my friend in nova home. So,i want to swich default launchers automatically at a certain time. I think i can use macrodroid.But I'don know how. Are there any shortcut to swich default launcher in app? (it's not good idea to touch the app icon to swich to go to nova or another home) (I don't want to root if possible)--edited

I tried doing it myself (On Automate) but it's a bit too advanced. Can I get your help? Also, I think Android overriding data connection when wifi is on might have to be factored in. I could use Afwall (and Netguard?) to control what connection they use but if the wifi is on, then the app won't be able to use data. For example, on Afwall, I have app x restricted from using Wi-Fi and enabled for it to only us data. But if both WiFi and data connections are on, then the app gets no connection. But if I turn Wi-Fi off, then it will get connected. Turn Wi-Fi back on and no connection again. How do I get around this? Android 7 | Rooted

My goal is to configure my Android LG G5, running the stock ROM, to enable Wi-Fi calling when I'm at home. I downloaded the Automate app from the Google Play Store. Next, I created a new workflow, and searched for a "block" (workflow step) to enable/disable WiFi calling. I searched under the **Connectivity**, **Telephony**, and **Settings** sections, and couldn't find this block type. However, there are all sorts of other settings for setting the cellular network type, enabling / disabling WiFi in general. Is this a gap in the Automate app?

The intercom dials my number and the phone needs to press '9' to open the gate (the call disconnects when it does). I want it to do this by itself any time someone uses the intercom (I can't answer when I sleep or am driving or on silent etc.).

I recently started playing with the app called 'Automate'. The starting block for each Automate flow provides a URI. Can this URI be used to initiate a flow? Can I accomplish this from the command line? Specifically, I would like to call Automate flows from within a Termux environment. I assume this can be done with am start ... but I haven't had any luck trying different commands (and I have successfully used am from within Termux before, so I don't think that's an issue). I have very limited knowledge of Android intents. I tried running am start -d content://rest-of-uri and I received a prompt asking which app to open, I chose Automate and the notification appeared for a second but the flow didn't run.

I have a flow diagram in [Automate](https://play.google.com/store/apps/details?id=com.llamalab.automate) that starts automatically with system. I want to add few blocks which will launch monitoring/diagnostic applications (CatLog, Network utilities, etc.) and will press certain buttons. How do I do this?

There are many tasks I do repetitively, like connect a Bluetooth headset or connect to a hotspot. How do I typically "code" this? How do I execute? Is there a consistent library or package manager, or do I have to collect from everywhere? Any community projects? Anything that works consistently over several platforms? Is there some framework to execute over several devices? (In the Bluetooth example I might want to disconnect other devices at the same time)

I'm using the Automate app to adjust my screen brightness when the phone is charged as well as alert me when the battery is full. From the above screenshot, I want to connect the YES from When power source plugged in to the IN of When battery level >= 100. But when I try to do it, the line that connects When power source plugged in to the IN of Is screen brightness gets broken. I can only connect either Is screen brightness **or** When battery level >= 100. How do I solve this?