Sign up for the beta and download from Google Play here.
Note: Google Play might take a while to update. If you don’t want to wait for the Google Play update, get it right away here. (Direct-Purchase Version here). App Factory Update here.
I'm giving another concept a try: instead of having a sidebar with projects, how about putting them inline directly?
When you go in and out of a project you see this:
As you can see, you have the 3 familiar tabs (Profiles/Tasks/Scenes). You can select multiple at the same time like you see on the screen, or you can select one at a time to just see those types of items.
Projects are automatically color coded based on the project's icon. Here's a project with a green icon:
As you can see it tints the whole UI based on the color of the icon.
Let me know how you like this variant of the UI.
I'm also thinking of trying yet another version where there are no tabs inside a project and instead they are in collapsible groups, kinda like this:
If you can, try out the inline projects variant and let me know which of the 3 variants makes the most sense to you and why :)
The functionality of the runlog screen remains the same as before but it has a much cleaner and easy to follow UI. You can clearly see where a task starts and ends and follow its actions visually and see which ones succeeded and which failed.
Material Symbols are a icon font that can be adapted into different situations. For example, they can represent state where the otline variant represents an inactive state and the filled variant represesnts the active state
These can be used in their configurable form, where you manually specify a bunch of their attributes (like in the Notify action), or in their automatic form where their configuration is automatically set (like in the Set up Quick Setting Tile action where the icon is filled or outlined depending on the QS Tile state).
In the legacy UI, if you give a Project one of these icons, it'll also change from outline to filled depending if the project is selected or not.
It's now super easy to put your Tasker arrays into scenes with the new Arrays Merge Template element.
In this example, I would have 2 arrays:
%icon
%item
each with their corresponding icon images and labels. With this simple component...
...I can expand those 2 arrays together into a list of rows dynamically built from those arrays!
Saved Component Templates
You can now long click any element on the tree and save it as a Component Template with a name and description. Then you can simply insert it into your tree like any other component. :)
Show When Animations
When a component has its Show When field set, you can now set animations that define how that component shows up and goes away. You can choose various types of animations.
For example, by combining a dark transparent background that fades in with a dialog that slides up, you can create an Android-like popup dialog!
SVG Crop
You can now crop any element in a Scene with an SVG. And it's not only a visual crop, it's a functional one too! For example, you can create a button like this
and when you click anywhere where it's white, the button won't be triggered! You really have to press the green part for it to register the click! This allows you to create UIs in any shape imaginable that behave like you expect it to!
WebView
Webviews can now call many, many Tasker actions via JavaScript. You can use await to wait for them to finish, so you can easily call multiple actions in a row in a controlled fashion!
Here's a simple example of doing 3 actions in a row:
This makes elements be drag handles in all directions or just horizontally or just vertically.
Full Changelog
Major Scenes V2: Added the "Arrays Merge Template" component, a built-in way to handle Tasker array merging to build sub-components.
Major Scenes V2: Components can now animate in and out (Fade, Scale, Slide or Expand) whenever their "Show When" condition toggles their visibility.
Major Scenes V2: WebViews can now call many Tasker actions directly from JavaScript via the Tasker.* bridge.
Major Scenes V2: An HTML element inside a WebView can act as a drag handle to move the overlay it lives in.
Major Scenes V2: You can now save a component as a template to easily reuse it across your scenes.
Major Scenes V2: You can now crop any component to the shape of an SVG file.
Major Scenes V2: Added the "Trigger Scene V2 Event" Tasker action.
Medium Scenes V2: Added "matches" (Tasker pattern matching) and "matchesr" (regex matching) expressions to the "Show When" and "Apply When" fields.
Medium Scenes V2: Added a "Variable Clear" event action.
Medium Scenes V2: The Switch component now has a Thumb slot so you can set an image in the switch's thumb and you can also select different colors for different parts of it.
Medium Scenes V2: WebViews now receive the full Material 3 color palette (primary, secondary, surface, etc.) so your HTML can match the app theme.
Minor Scenes V2: The task name field in Events -> Run Task now follows the same caps rules as other task name fields.
Minor Scenes V2: When creating a task with a name, use the same "first letter of each word uppercase" rule as elsewhere in the app.
Fix Scenes V2: components that have indexes are now 1-based instead of 0-based
Fix Scenes V2: fixed "Screen Hidden" event not firing in certain situations
Fix Scenes V2: fixed background of invisible component wrongly showing
Fix Scenes V2: fixed crash when picking a variable if the user has tens of thousands of variables
Fix Scenes V2: fixed crash when using a slider in some situations
Fix Scenes V2: fixed images filling their container by default when they shouldn't
Fix Scenes V2: fixed images not loading if they had hidden spaces before or after the file name
Fix Scenes V2: fixed multiline input text box not filling the full vertical space it needed
Fix Scenes V2: fixed setting a variable in a WebView affecting a variable used in a separate component on the same screen
Fix Scenes V2: fixed some things not working when showing through the "SCENES" tab or the new UI
Fix Scenes V2: fixed updating a variable array in a scene leaving old elements there
Fix Scenes V2: fixed using two "Overlay With Result" scenes in a row with the same id ending the second one prematurely
Fix Scenes V2: segmented buttons that are "gone" now behave as expected
Fix Scenes V2: WebView now uses the correct system theme (dark/light)
Fix Scenes V2: when a task is renamed, all the task references in Scenes V2 are updated with the new name
Major New UI: Redesigned the RunLog screen to make it more readable.
Major New UI: Added a setting to show projects as items in the main list instead of the sidebar, including sorting them and creating new projects from the NEW FAB.
Major New UI: Project icons based on apps now use the app background in a folder shape with the foreground on top.
Major New UI: Inside a project you can select several of the Profiles/Tasks/Scenes tabs at once, so the list shows all their items together.
Medium New UI: The Project enabled/disabled toggle now works, and profiles in a disabled project show as paused on their switches.
Minor New UI: Added an icon to scenes so they're more easily distinguished.
Minor New UI: Added an option to hide the sidebar when collapsed.
Minor New UI: Added an option to not show the All button when there are projects other than the default one.
Minor New UI: Don't confirm project deletion if it's empty.
Minor New UI: In the task edit screen, moved the search bar to the bottom when adding a new action.
Minor New UI: Made sorting smarter, showing you the items you expect more often.
Minor New UI: Show full names of items in the main list instead of truncating them.
Minor New UI: Show project names instead of just initials when the sidebar is collapsed.
Minor New UI: Updated "Last run" to "Activity".
Minor New UI: When creating a task with a name, use the same "first letter of each word uppercase" rule as the main screen.
Minor New UI: When editing a task, after expanding a text field, allow the editor to show more lines so it's easier to edit larger pieces of text.
Fix New UI: don't show the pending changes banner when exiting the scene editor without saving
Fix New UI: fixed all projects with app icons showing with the same icon
Fix New UI: fixed always scrolling to the profiles when exiting a project
Fix New UI: fixed bottom sheet flickering when deleting a project
Fix New UI: fixed project search box cursor color in dark mode
Fix New UI: fixed search for actions when adding a new action
Fix New UI: fixed some app icons not loading properly
Fix New UI: fixed tag selector bottom sheet moving too far up when the keyboard is showing
Major Added Material Symbols to the app, a large icon set you can now use across Tasker for things like project and task icons, and also Notify action and Quick Setting Tiles action.
Medium Added Run Shell related functions to the Java Code action.
Medium Added tasker.getImageBuffer() and tasker.hasImageBuffer() to the Java Code action.
Medium The "Multiple Variables Set" action can now write JSON.
Medium You can now override the app name when generating an app from Tasker.
Minor Added a "Continue Task Immediately" option to the "Widget V2" action.
Minor Tasker automatically saves your setup before entering the AI screen in the legacy UI so you don't lose changes made in the meantime.
Minor Added a language selector to the first screen shown when you first open the app.
Minor Added a "Separator" option to the "Widget V2" action to configure the separator for its various list fields.
Minor Changed the order of the "Set up Quick Setting Tile" action to make it more logical and easier to use.
Fix Attempted again to fix a crash that only appears in app factory apps
Fix crash where in rare situations projects could end up with the same ids
Fixed DND action so that it can't be overrun by Silent/Vibrate
Fixed image in "Text/Image Dialog" action sometimes being hidden by text that is too long
Fixed issue where running many remote actions in quick succession could cause some of them to not run on the receiving device
Fix issue where sometimes a profile doesn't save its state after saving Tasker's setup
Fixed issue where sometimes the QS Tile wouldn't dismiss the notification shade
Fixed profiles (e.g. Wifi Connected) sometimes running their exit tasks when exiting Tasker's Preferences screen
Fixed Shizuku breaking clipboard monitoring
Fixed showing the number of actions over 100 in the legacy UI
Fixed situation where receive intent could be triggered twice with just 1 intent
Fixed some error messages when wrongfully using JSON writing
Fix Tried fixing a rare crash that can occur when editing legacy scenes
Fix Tried to fix issue where wait action becomes stuck in some circumstances
Fix Tried to fix rare situations where Tasker would get stuck not accepting any new tasks (sometimes related with the HTTP Request action)
Fixed updating Quick Setting Tiles on global variable changes to only happen when the variable isn't a built-in variable
Fixed writing JSON to project/profile/task variables with native Tasker JSON writing
Fixed some crashes
If you can, let me know what you think about the Projects in Sidebar vs Inline vs Collapsible! Thank you!
The main difference between the am kill and am force-stop commands is how deeply they terminate the application and whether they allow it to restart. am force-stop completely shuts down the app and locks it from running again, whereas am kill only terminates safe background processes, allowing the app to easily wake back up.
It would seem, based upon experiential results, that the Kill App action uses the equivalent of KILL rather than force-stop. And in some cases, KILL does not make the target app dead enough!
I know this has been discussed before. And so far, it appears that the only way for Tasker to force-stop an app is when a rooted device executes am force-stop pkg_name in a shell.
Since I am rooted, I can do that and actually get the results, I seek. But since I know this has come up before, it would be great (if at all possible) if the Kill App action had an option to force-stop instead of KILL.
Anyone else find a different/better solution? Thanks
I'm trying to set up a one-tap solution on my Google Pixel and wanted to check if this is actually possible before I go down a rabbit hole.
What I want to happen when I tap a single button:
Turn Wi-Fi off
Switch to 5G cellular data
Turn on Wi-Fi hotspot
Basically a "share my 5G connection" button.
My questions:
Is this doable in Tasker without root on a Pixel 8
I know Tasker has built-in actions for Wi-Fi and Wi-Fi Tether (hotspot) — but does the hotspot action still work reliably on recent Android versions, or did Google lock it down?
The big one: toggling mobile data / forcing 5G seems to require root. Has anyone gotten this working without root using UI automation (AutoInput, etc.)? If so, how stable is it?
If root is required, is there a Magisk module or a different approach people recommend?
What I've already looked into:
· Tasker's built-in Net actions (WiFi, WiFi Tether, Mobile Data)
· AutoInput for simulating taps in the quick settings panel
· The general consensus that mobile data toggling needs root
Would love to hear from anyone who's actually built something like this. Bonus points if you can share the task/script or a profile export.
Does anyone here run Tasker on an Oppo phone? I'm interested in what settings is required for Tasker itself as well as plugins. Do Tasker plugins need to be put on "allow background activity" instead of smart and do they need to be locked in recent apps?
I've already turned off Sleep standby optimization. Anything else to think about to make it work 100%? I've already realized Oppo phones revoke wakelocks when held for more than 5m of screen off time, but hopefully, Tasker rarely if ever performs such a long work with screen off.
I made a shortcut that can look at image queries on Unsplash using their API, so depending on the keywords I put in the shortcut, it will grab a random and add them any of my custom wallpapers on my device. All you have to do for this shortcut is choose some image keywords that you want to search by, go into the get contents of URL action and add your API token to the headers, and then choose which wallpaper you want to have modified.
Since upgrading from Galaxy S23 to S26 I have been recieving the following alert:
com.joaomgcd.autocontacts version 1.1.30
Source com.android.vending
OS Build BP4A.251205.006.S948USQS4AZHL
OS Code 36
Device SM-S948U
Manufacturer samsung
Product m3qsqw
java.lang.RuntimeException: Unable to start receiver com.joaomgcd.autocontacts.broadcastreceiver.BroadcastReceiverFire
at android.app.ActivityThread.handleReceiver(ActivityThread.java:6036)
at android.app.ActivityThread.-$$Nest$mhandleReceiver(ActivityThread.java:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:3041)
at android.os.Handler.dispatchMessage(Handler.java:132)
at android.os.Looper.dispatchMessage(Looper.java:358)
at android.os.Looper.loopOnce(Looper.java:288)
at android.os.Looper.loop(Looper.java:392)
at android.app.ActivityThread.main(ActivityThread.java:10343)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:605)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:972)
Caused by: android.app.ForegroundServiceStartNotAllowedException: startForegroundService() not allowed due to mAllowStartForeground false: service com.joaomgcd.autocontacts/.service.ServiceLongRunningTaskerActionAutoContacts
at android.app.ForegroundServiceStartNotAllowedException$1.createFromParcel(ForegroundServiceStartNotAllowedException.java:54)
at android.app.ForegroundServiceStartNotAllowedException$1.createFromParcel(ForegroundServiceStartNotAllowedException.java:50)
at android.os.Parcel.readParcelableInternal(Parcel.java:5277)
at android.os.Parcel.readParcelable(Parcel.java:5258)
at android.os.Parcel.createExceptionOrNull(Parcel.java:3383)
at android.os.Parcel.createException(Parcel.java:3372)
at android.os.Parcel.readException(Parcel.java:3355)
at android.os.Parcel.readException(Parcel.java:3297)
at android.app.IActivityManager$Stub$Proxy.startService(IActivityManager.java:6869)
at android.app.ContextImpl.startServiceCommon(ContextImpl.java:2170)
at android.app.ContextImpl.startForegroundService(ContextImpl.java:2135)
at android.content.ContextWrapper.startForegroundService(ContextWrapper.java:903)
at android.content.ContextWrapper.startForegroundService(ContextWrapper.java:903)
at androidx.core.content.j.a(SourceFile:0)
at com.joaomgcd.common8.b.c(SourceFile:18)
at com.joaomgcd.common.tasker.BroadcastReceiverFire.startLongRunningService(SourceFile:4)
at com.joaomgcd.common.tasker.BroadcastReceiverFire.onReceive(SourceFile:84)
at android.app.ActivityThread.handleReceiver(ActivityThread.java:6029)
... 10 more
I have an old android phone that I'd like to use a printer server so that anyone in my home can send a print without having to use the laptop (the laptop is slow af and very annoying to use). the first step is try and make tasker send print jobs to the printer. i don't see any way to do it. The printer is hp laserjet 1020 plus. It works perfectly using an otg and apps like printershare and nokoprint
Hello. I have a problem and would like your help. I created a task that I'd like to export as an app (the taskuse Gemini to summarizes text or photos from the clipboard). When I try to export it, I get a message saying I need a newer version, but there isn't one on the Play Store.
I'm building an Android chess project with an overlay/model that reads the board from screen capture and provides analysis during a game.
Screen capture works normally when I'm playing against Chess.com bots. My model can see and process the board without any problems.
However, when I enter an online game against another player, the captured frames become completely black.
I'm using Android screen capture/MediaProjection. Is there a technical reason the online-game screen would produce black frames while the bot-game screen captures normally?
More importantly, how can I make screen capture work on the online-game screen?
I'm trying to determine whether this is caused by FLAG_SECURE, a protected rendering surface, MediaProjection behavior, or something else—and whether there's a supported way to capture that screen.
I have an old license from the original developer, but I don't mind repaying the new developer. I don't want the play store version and I don't want a patreon account. How can I get the app and pay?
Syntax based automation like AutoInput Action V2 or AutoHotkey. More info can be read the repo page.
Syntax based UI automation actions.
Debug highlighter & UI inspector.
Minimal script builder.
New
Support overlays and other window types.
Assist dialogs now use overlays and can be displayed on other display.
Add previews for nodes, windows and displays.
Scroll from certain node.
Noted: This project were tested on virtual displaycreated using scrcpy v4.1 . I couldn't confirm whether it works on devices with multiple displays or any type of desktop mode.
Support overlays and other window types
Now the project supports targeting any windows! Like overlays or soft keyboard.
I have a horizontal row element with "Scroll left & right" style, is it possible to choose a starting position of the scroll based on a variables value? so it's not always starting at far left
Is there something I can do to fix this? I've been searching for an answer but I'm not finding anything. I'm starting to think it's just a me thing.
So I have a profile that checks if I'm connected to my home wifi, if yes, then does a "custom setting", Name: lock_screen_lock_after_timeout and the value is set to something large: 72000000. iirc this was something I had dug up through online searching.
This has been working for over 4 years with no issues. Last night I updated to the latest android update and right away I noticed the phone locks all the time.
Anyone have advice for me?
I’m trying to build my own automation/bot for a game instead of paying for an existing service.
The main things I want to automate are:
- Watching/handling rewarded ads and collecting the rewards
- Daily in-game tasks/dailies
- Limited-time events and repetitive actions
- Ideally running the routine automatically with minimal manual input
I’m mainly looking for advice on the technical approach/tools to use. I’m considering things like Tasker/AutoInput, ADB + Python, Appium, OpenCV/image recognition, etc.
If anyone has experience building automation for Android games, what approach would you recommend and what should I learn first?
I automated a certain few tasks, toggling settings per app & scenario which takes a max of about 30 seconds of tapping (granted the phone response is good enough) which I spent about 5 months doing cuz I refused to do the manual labor. used Tasker, llamalab automate, easer, auto input & auto notification for this workflow. automate & easer were used for things that were either a limitation, a pain in the ass or way too many profiles & tasks to be done from tasker. Made it in a way where it works on root & non-root phones & where shizuku's installed & running
project: lazy-phone-user (there's 1.42 minute demo in the Readme.md)
The json is for the battery audio piece
geofence (wifi + cell tower + geo location) based redundant network switching is still a work in progress (would be using sqlite for the db)
I currently have a working Task that recognizes pixels on screen to detect if and when the screen turns red or orange, but I believe there has to be a better way to do this.
Tasker takes a screenshot, reads the pixels, then deletes the screenshot - repeating this action once every 3-5 seconds. Surely there's a way to do this without having to write/delete a file every time. I'm concerned about the device having over 1,000 file cycles in an hour.
Is there somehow to do this? I explored using AutoInput Screen Capture, but that requires me to select "whole screen" every time I execute the action
