What is Reddit's opinion of
Automate?
From 3.5 billion Reddit comments
➔ Automate website
By popularity on Reddit, this Service is:
100 reviews of this app found across Reddit:
For sure their updates are complete bullshit. As an Android developer, their "Sending and Receiving Messages blah blah..." section specifically caught my eye.
Apparently the argument listings came from the components in Android "intent", a basic building block of Android apps. It's nothing to do with Aido or robotics or whatsoever. It absolutely makes zero sense.
But hey, I just found out the entire section is a direct copy and paste from the Llamalab's Automate documentation with slightly changing the title. Now it's making some sense...
You can download the Automate app and use my script to alert on your desired charging %
This doesn't use root so it can't actually stop the charging, but give you a alert.
You can download the Automate app and use my script to alert on your desired charging %
This doesn't use root so it can't actually stop the charging, but give you a alert. [Copy/paste from another reply]
Try this flow, which uses the UI to turn on the hotspot. It's also got a subroutine to unlock the phone. Neither require permissions. Feel free to take what you need 🙂
Use the dateformat function: https://llamalab.com/automate/doc/function/date_format.html
Also I haven't always managed to get creation dates from image files. In some files the creation date may not be saved. Be sure you're not confusing date created with date modified.
Not really possible, since only the system is allowed to assign default apps. The only workaround is to use the Interact block to simulate the clicks to do so.
Recent versions of Android don't allow mobile data to be turned on and off via APIs anymore, which those blocks rely on. It might work if you've rooted your phone. Do you see any errors in the log when you run your flow?
I wrote something similar which tries to use the blocks to set the mobile data state the very first time the flow ever runs. If that fails, it uses the Quick Setting button in the Android user interface forevermore. You can probably adapt it to your needs:
https://llamalab.com/automate/community/flows/38810
Also see: https://llamalab.com/automate/community/flows/21295
Use the Keyboard visible block to detect when a physical keyboard is visible/slid out. If that's not what you meant, then please explain.
To wait for a duration use the Delay block. To await a specific time use the Time await block.
You'll have to use the related block to await a particular condition, e.g. Wi-Fi connected, there's no generic "wait for expression to change".
You can change the option to " When changed " within both the blocks ( accelerometer and device unlocked blocks ). So, only when the change is detected, the flow will proceed further instead of looping and logging continously ( solving your first problem of log piling up continously ). The acceloremeter block does state that it consumes 0.180 mA of battery. So , it adds up to the power consumption.
If you still want to use it in " Immediately " for both blocks and just want to delete the logs...then use this flow from the community... https://llamalab.com/automate/community/flows/37342 ( credit : Patrick Corgan )
It clears the log... just try it out and check if it actually cleared your log... Add a " pick time " or " time await " block before this flow and then select your time...at which the flow clears the logs...
Hope this helped you...
Apps can't record touch event "live", so implementing something similar to the "record interaction" of the Interact blocks is not possible. Another problem was how the represent the "gesture" data as input arguments, for single-touch an array of vertices (X,Y) would suffice, but multi-touch would be difficult. Anyhow, that's why the Interact touch block was implemented as it is.
A way to pick or preview the screen coordinate is on the to-do list.
hello bro, here is the flow that you wanted. I made it. https://llamalab.com/automate/community/flows/39740
basically you have to enter the query you want youtube to show when you open your phone. like e.g..news, todays news, ....anything you want... then enter the time you wake up daily so that your phone will be ready to open youtube and play the video. after waking up,just unlock your phone and it will do the rest of it...
im not a pro in this flow making...but i thought i might be of help so i did my best...hope it works...
(sorry if my English is bad, English is not my native language).
I'm a software developer by profession. So I would skip the tutorials (Automate has some basic tutorials on Youtube), and go straight to the "APIs" or the technical documentation. (https://llamalab.com/automate/doc/index.html)
The alternatives to Automate is MacroDroid and Tasker.
MacroDroid is more or less like Automate, but it lack the user-friendly UI of Automate.
So, for those who's trying automation for the first time, Automate is a good starter.
Tasker is alot more powerful than MacroDroid and Automate, but it will be more intimidating to beginners.
Use the included "Settings finder" flow, or try the "settings browser": https://llamalab.com/automate/community/flows/37254
I don't see the use of assigning the current value, also getting the setting requires different Privileges which may not have been granted.
Above is a link to the flow. It's not perfect so please adjust it to your needs or make a comment here or on the flow page and I can try change it for general use.
As the documentation say, the secure option may not work on all device. It probably hasn't worked for a long time. Sadly i don't think there's any new "hack" available, to make it work again.
Android has no specific event/broadcast for detecting it. It may be possible using the Inspect layout block to detect some unique UI element of the notification drawer.
Only set the Package field to com.android.chrome and the app will start just like the launcher does. If you want to open a particular webpage then use Action View, see: https://llamalab.com/automate/doc/block/activity\_start.html
You should be able to do something like this with the file monitor block. Just await a change in the default image directory of your device and capture the file in the alteration path variable.
Try removing block #6, as the documentation say, "Android doesn’t support checking the currently connected devices, for proceed Immediately check, Automate tries to work around this limitation, but it may be unreliable." If you need to check two cars, just create two flow instead, or two sub-flows.
A more reliable alternative is to use the Audio device connected block, since it's likely the car has one.
Try using the Broadcast send block
- Action=
"android.intent.action.MEDIA_SCANNER_SCAN_FILE" - Data URI: file:///storage/emulated/0
If that doesn't work then use the Media store add block.
From what I'm hearing, the Mobile and Wi-Fi Quick Setting tiles are getting rearranged, so a new UI workaround will be necessary as well. I'll be updating this rather popular flow after my Samsung device gets Android 12 (One UI 4 seems to be close):
The Location at block doesn't proceed until you actually enter or exit the location. If you want it to check if you're already at the location when the flow is started, then you need to insert another Location at block with Proceed=Immediately.
"Generic" NFC payload data is returned as an Array of Dictionaries, i.e. NDEF records with properties. If the tag holds a single "text" record, then to access it, use: payload[0]["text"]
Nothing related to the Audio volume set block has changed in years. If you click the *f*x icon next to the Audio stream, then Ring should have value 0x2 and Notification value 0x5.
If you add the Focus Mode button to your phone's Quick Settings, you'll be able to use the UI to toggle its setting without extra permissions. Then you can use this flow I wrote to generate the XPath the Interact block uses to toggle the Quick Setting tile, and to test it:
https://llamalab.com/automate/community/flows/39656
You'll most likely just need to tell it the tile's text ("Focus mode"); you won't need its ID or class name. You can also look inside that flow for hints on how to incorporate the Interact block into your own flow to toggle Focus mode.
Try using the Broadcast receive block with action Camera button., see: https://developer.android.com/reference/android/content/Intent#ACTION\_CAMERA\_BUTTON
You might be able to use the Interact or Inspect layout block to detect some on-screen "account name" text in the Reddit or Instagram apps.
- Flow beginning
- Wi-Fi network connected
- Bluetooth set state
It maybe using an overlay, that's not an Activity which is what the App in foreground block detects. Try using the Interact or Inspect layout block to detect some content its displaying.
That's a correct flow. I guess the flow is overriding the "Headset hook" button which an audio player is using for play/pause? Maybe only activate the Media button block when audio is actually playing, i.e. using the Media playing block.
The "Headset hook" is button is handled a separately, it's "capture" can't toggled dynamically. If you've used the "Override voice search" option in setting, try the following flow to restore it: https://llamalab.com/automate/community/flows/7614
Alarm times should only appear if the "Debug logging" option is enabled in settings. However, sent SMS/MMS and called numbers are always logged, and failures unless caught.
Standard Android doesn't have an "list of startup apps". If your device, e.g. Xiaomi or Huawei, has some custom option you'll need to enable/disable them manually. The Chinese manufacturer often grant "big" apps special privilege and exclude/while-list them from their non-standard features, like app breaking "power save" and startup features.
See: https://llamalab.com/automate/doc/faq.html#automate_not_running
- Please read: https://llamalab.com/automate/doc/faq.html#flow_stopping
- You likely can't, soft keyboards usually don't send key events.
- Enable the "Consume" option. But it might not be possible for hardware buttons.
- Filter/match only the key (event) with those flags set.
- "No flags" means the key event should have no flags set, long-click the field to clear it, i.e. ignore flags entirely.
Try:
- Flow beginning
- Power source plugged
- Audio player control: Play
This flow can help with that. You give it any or all of the id/class/text of the element (like the Interact block used to take), and it'll generate a much simpler XPath expression and copy it to the clipboard for you. It'll also generate Quick Setting XPaths directly from their text:
Try using the Expression true block with a matches function:
- Expression:
matches(name, "\\bPankaj\\b")
Here are a couple I wrote - the Battery Charge Alarm does a lot of stuff, including having an alarm snooze function:
The Airplane mode set block should work without root on Android 6, but it seems Google may not have implement the feature until Android 8. If your device is rooted, change the Airplane mode workaround option in setting.
Any error message?
Android version?
The system should usually do this when a BT headset it connected. Anyhow, the only way to affect BT audio routing is by using the Bluetooth SCO set state block.
Works as expected on my device, it should on Samsung too, otherwise the Contact query block wouldn't work. Also working is to use the Contact pick block to get the URI then append "/data", e.g. uri ++ "/data"
You likely want to limit the resulting rows to a particular mimetype, with a Where clause like: mimetype = 'vnd.android.cursor.item/name', the actual value is then in an data1, data2, data3, etc. column. See Android docs.
Sure. Here is the link for the download. https://llamalab.com/automate/community/flows/39942
Then I just used a tasker scene to launch the flows
Key/button presses shouldn't be "consumed" unless you've enabled the Consume option in the Key pressed block. Also, the "key filtering" part/feature of the accessibility service is only activated/enabled while an Key pressed block is being executed.
If it doesn't work on Android 11 it's likely because of bug: https://issuetracker.google.com/issues/163120692
Welcome to the wonderful world of UI interaction. It usually helps to put a short 0.1-second Delay before and/or after clicking on a UI element in order for the UI to have a chance to react. This flow can also help you build much shorter and more reliable XPaths:
- Yes, but failures and Log append message may still be logged.
- No "polling", please read, use Proceed = When changed instead. Anyhow, Automate still has to process the accelerometer data which will use power, but it's far less than the flow doing it.
It's not possible to toggle a widget without using the Interact block. A non-root alternative is to use the ADB shell command block to execute: svc data enable/disable
It should be possible by using an additional Flow beginning block with an Variable give block which sending "trigger" messages to an Variables take block in the "main" sub-flow, using the Atomic blocks to storing the Taker fiber URI.
Here my thinking about your question:
1) there is a SIM card info example which could help (did not work on my phone, maybe that's because my phone is also not rooted). If you can detect the current SIM card number, store it and regularly compare it with the current number. Then you can react by sending the new number by sms/mail/GCM.
2) and 3) As long as you are connected to WiFi, you can communicate through mail/GCM. Firstly you should make sure Wifi does not get disabled. Furthermore you can look for unsecured networks and connect to them. If there is no sim/wifi connection, I cannot think of a way to communicate...
In addition the phone must stay turned on (learned that the hard way after my previous phone got stolen). I did the shutdown prevention for my phone (Realme X2) by canceling the "swipe up/down to reboot/shutdown" message (detect with interact->inspect) and open an input dialog for password. On correct password, the phone reboot/shutdown is done. For WiFi, mobile data and location this can be done in a similar way. Cancel the quick tile bar if the phone is not unlocked.
It seems apps can't use the fingerprint gesture API since Android 9 due the an Android bug, or they've purposely disabled it. Please enable the Debug logging option in settings, test the Fingerprint gesture block, then post the flow log.
This came up in the other channel today, too. You can grab the "unlock" subroutine from this flow I wrote. If it can't unlock your phone with the API, it'll use a UI workaround. (You might notice an error in the log the first time it runs when it figures that out.) You'll also need to have set up Smart Lock to let the flow unlock your phone:
https://llamalab.com/automate/community/flows/21295
With Smart Lock active, the flow can unlock the phone without a passcode.
The app has to be designed run in the background, using a Service. If it's designed with automation in mind, it may allow you to start its "task" using the Service start or Broadcast receive blocks. You have to look for public documentation, or inspect the app manifest, to figure out how to configure the blocks, i.e what "Intent" it accepts.
Hello bro, here is the flow I made for you based on what you asked... https://llamalab.com/automate/community/flows/39751 If this doesnt work, message me bro, and I will try to update the flow based on your outcome. Im not pro in this, if there was another way of doing it, please go for it bro,...I did this flow based on what I know about the condition you wanted....
Hope this works for you bro...
There's no Android API nor Automate block for sending DTMF tones. It might be possible when dialing a call, i.e. by appending the numbers after a comma, e.g +1123412341234,1,2,3
If that doesn't work the only alternative is to use the Interact block to simulate clicks on the numpad in the dialer app.
no idea if that phone model does this thing. You can check, if you have google messages on the (should-be-)receiving phone. how to find, and where it says type is "text message" means automate should be able to see that it's an SMS. If you see anything else, automate doesn't see it.
>Is it supposed to work if I have a "sms receive" [...] I onlyhad that 2 simple blocks and it never goes through the receive sms part
yes, it's supposed to. If the logs are just saying "sms received", it's waiting for an SMS received, as opposed to an MMS.
What you can do is use a content changed block and watch content://mms-sms/conversations. I'm not 100% sure the right way to deal with android "content", but I believe that will detect incoming MMSs.
You've set the Maximum fix age to 0 (zero), that will force the Location get block to request a new location fix, which the system doesn't seem to deliver until almost an hour later. Why it takes so long is difficult to know, maybe an "power save" feature interfering, or you remained indoors so the GPS didn't work. Try enabling the Google Play Services location option in settings, or use an higher Maximum fix age to use the "last known" location fix.
Automate is compatible with Tasker plugins
https://llamalab.com/automate/doc/block/plugin\_setting.html
Use the ADB shell command block to execute: am force-stop <package of app>
See: https://developer.android.com/studio/command-line/adb#am
The Shell command block doesn't actually execute commands in a shell, it just does an exec, so it needs an executable, cd is a built-in, as the documentation say:
>Built-in shell commands like printf, echo and test which aren’t stand-alone executables may not work.
To make the command run in a proper shell, use: sh -c "cd Android"
Also the Android directory may by inaccessible since it contain private app data.
Apparently only audio and messaging notification is supported. I might add support for it in the Dialog input block. See also: https://developer.android.com/reference/android/app/Notification.CarExtender.Builder
Use the Google Assistant action block to interact with Automate without screen interaction, or the Speech recognition block to do so after a notification, shortcut, widget, or QS tile click.
Automate can add networks prior to Android 10 by using the Wi-Fi network connect block. Since Automagic is not longer available on the Play Store it doesn't target Android 10, which published apps are now required to do.
There are some nasty gotchas with the Google Calendar API. I wrote this flow to figure it all out. It's written as a subroutine to make it easier for others to use in their flows:
https://llamalab.com/automate/community/flows/21077
Hope it helps!
The "Connectivity permission extension" app can't "run" since it's just an XML file, it contains no code. Android incorrectly show the battery usage for the Automate (main) app. Automate using 4% of battery doesn't seem excessive, especially if you have a flow preventing the device from sleeping for 5 minutes every hour. Please read: https://llamalab.com/automate/doc/faq.html#excessive_battery_usage
if you use android, this will automatically press the approve button on the push notification: https://llamalab.com/automate/community/flows/25731
another idea: set up a twilio number that auto presses 1
A Tasker plug-in shouldn't really be needed, the IFTTT "webhook" feature may be able to send a request to the the Cloud message receive block online endpoint, see: https://ifttt.com/maker_webhooks
Well you can export a backup of all your flows or individually If you want to backup everything go to Setings > Backup > Create backup. It's near the bottom of the settings page.
You may also want to look at the "Daily Automate backup" flow it is downloaded by default on all automate installations if you can't find yours you can download it here, just a word of caution, every week or so delete the old backups because this flow does not delete old backups, and you will eventually run out of storage. https://llamalab.com/automate/community/flows/1020
If you want to export every flow individually open the flow, tap the sharing icon (3 dots in a triangle) and "Flow," that will export a .FLO file. Note: Descriptions are not stored in .FLO backups, snd the flow title is whatever the file name is minus the ".flo" To import a individual flow, on the main screen tap the 3 dots in the top right corner and tap "Import".
Hope this is helpful ; )
I doubt the Google Lens app support "decoding" an image, or whatever you're trying to do? If it does, maybe it just can't read from the file system, try Extra= { "android.intent.extra.STREAM" as Uri: fileUri(path) }
See: https://llamalab.com/automate/doc/function/file_uri.html
Damn! I thought about doing this with the 15-puzzle, but seeing the linked comment with python code, I guess I'll do this as it gives more stars :)
I don't really speak android, so I just finished messing with python running in termux, sending move commands to [Automate](https://llamalab.com/automate/) to do the moves...
Use this flow to get the exact ID and content of the notification, then use a "notification present?" block set to "when present" to scan for the notification to come in, and when it does, use the "interruptions set" block to turn off DND, then a "notification show" block to send a new notification with a loud sound every 15 mins or what have you until you dismiss it.
>To implicitly start the “main” activity, like the launcher does, specify only the package.
See: https://llamalab.com/automate/doc/block/activity_start.html
I'm also a novice but would like to share my example since it works.
Automate flow: YouTube Vanced & Map
Also if anyone know there's room to improve the flow please comment. I'm eager to learn more about this wonderful automate stuff
You can use webhooks on ifttt to send to cloud message receive on automate
goto https://llamalab.com/automate/cloud/ to create a key
the in ifttt webhook
set url - https://llamalab.com/automate/cloud/message
method - post
content type - json
body -
{ "secret": "<your_key_goes_here>", "to": "<the_email_of_your_cloud_message_receive>", "device": null, "priority": "normal", "payload": <your_payload_goes_here> }
The payload can be a
string - "as_string"
interger - 123
array - ["val1", "val2"]
dictionary - {"key1": "val1", "key2": "val2"}
Ensure any Delay or Time window/await block has Proceed=Exact and Awake device enabled. Enable an "timer accuracy workaround" in settings. Please read: https://llamalab.com/automate/doc/faq.html#automate_not_running
I just started automating some thing, TV turning on when alarm goes off and music turning on when I get home stuff like that. I setup Home Assistant to be my hub and I use Automate to send webhooks to Home Assistant like when I am near home or my phones alarm goes off.
From what I have researched try your best to stay away from closed eco systems.
Then it's already a text value, see: https://llamalab.com/automate/doc/block/dialog_input.html
To compare it, use the expression true block:
"0123" = optionalpassword
Does this flo give the same error? https://llamalab.com/automate/community/flows/15573
Have you tried just creating a flo that takes a picture while not on the lock screen? ( just to make sure your camera permissions are good)
https://www.techotopia.com/index.php/Android_Broadcast_Intents_and_Broadcast_Receivers
in short apps can ask the operating system to inform them of certain events, like a wake up call at the hotel.
if your other app can send broadcasts, register the broadcast in automate and thats it.
https://llamalab.com/automate/doc/block/broadcast_receive.html
Please read: https://llamalab.com/automate/doc/faq.html#power_save_android6
The flows pausing while the device is asleep, being left unattended, is expected as it's likely Dozing. Use the Device keep awake block to prevent it.
Flows not resuming until the app is opened is non-standard behavior, if excluded from Battery optimizations.
Automate can be battery optimized like any other app, but it's not advised since the app may become unreliable. You may have to exclude any geofencing related services from battery optimization as well, see doc.
It seems to be able to, but I'm not sure how.
The one I implemented does it with a Quick Settings Tile.
If you need any help using it, just comment here .
The second argument to timeMerge is seconds since midnight, not a unix timestamp, e.g. today at 8pm: timeMerge(Now, time(18,00))
Also, using durationFormat with a unix timestamp, as returned by timeMerge, makes no sense. To format a unix timestamp use the dateFormat function.
Not a typo, as a unix timestamp doesn't include information about its time zone, so that has to be specified.
I second that. It will certainly give apps a way to innovate.
In the meantime, you can use this in Automate app (free is fine). It gives more flexibility as it does popup google search and you can modify it to your liking!
%varName is how Tasker does string interpolation, that will not work in Automate as it uses {varName} instead, e.g. "Battery level is {batteryLevel}%"
See: https://llamalab.com/automate/doc/value.html#string\_interpolation
Something like...
Flow beginning +->+ | Power source plugged --+ | | | | Fiber stop: childUri Fork --+ +--+----------------------+ | Delay: 30m | (Device shutdown)
Caution! Replace the Device shutdown block with some other block during testing, e.g. Sound play, and disable the "run on system startup" option in setting, until you're sure the flow works as expected.
On Android 12+ the Mobile network preferred block also require root. On lower Android version this information was stored as a regular system setting, i.e. category=Global name="preferred_network_mode", but now it's stored in some lower-level hardware/API, this caused the Proceed=When changed to break as well.
Seems like i forgot to update the documentation, and to add a notice box, i'll fix that.
Simply click the "Install generated key" button on the ADB shell command block configuration screen, that will generate and install a new key on the device, which you can then select when clicking the Keychain alias field. There's no need to extract anything since the key is already installed, as the documentation say, "the secret/private key material remain inaccessible, e.g. to export or backup."
As the documentation say the Command should NOT be prefixed with: adb shell
The "RequiredArgumentNullException: alias" failure means you forgot to specify the key alias field.
In the Zip compress block:
- Source path: /storage/9C33-6BBD/Screen Recorder/Zip Files/Pictures/ScreenShots{Now;dateFormat;yyyy-MM-dd}/
- Destination path: /
- Recursive: enable to include sub-folders
I can share a discord webhook example that I was testing. Not sure if IFTTT is the same, but maybe it will point you in the right direction. link
There's no built-in block for it since regular apps doesn't have access to such features. The Interact block should be able to simulate the clicks to do so, but it will probably be unreliable.
I just tested the Airplane mode set state block on the Android 12 emulator and it works, with and without the Root workaround.
You need to use the Shell command superuser block to execute commands as root.
If you can't get that to work and you'd like to try using the Quick Settings tile UI workaround, you can grab what you need from here and change the variable that holds the tile text:
https://llamalab.com/automate/community/flows/21295
Yeah, sometimes it comes to this 😕
There's no standardized way, it depends on the Messaging app. Try using an App start block with View action and Data URI set to an "contact URI", e.g from the Contact pick block.
Try using the Broadcast receive block with action Battery changed, its result Extras include such related info, see: https://developer.android.com/reference/android/os/BatteryManager
Use the App start block with just the Package set to open the app just like the launcher does, which usually just brings it to the foreground.
Try looking at the community made flows, there's lots of sending WhatsApp message examples: https://llamalab.com/automate/community/?q=WhatsApp
Then use the Location at block to do so when reaching a location.
You might start with a simple two-block flow which just turns the hotspot on. You may need to play with the "Wi-Fi hotspot workaround" Automate setting to get it to work. You can then use this flow to start flows (or apps) at boot, or use parts of it as an example (most of it is a UI to manage the flow and app lists):
https://llamalab.com/automate/community/flows/37092
If you still can't get the hotspot working, try using the appropriate subroutines from this other flow I wrote which will use the Android UI to set it by using the the Quick Settings tile. It also has a subroutine to unlock your device without root, also using the UI:
Maybe my flow will help - you can give it element ID and/or class and/or text and it'll generate the XPath for you, way less (and less fragile) than the inspector will give you: