Skip to content

OpenTasker v0.2.95

Choose a tag to compare

@SysAdminDoc SysAdminDoc released this 08 Nov 03:52
· 481 commits to master since this release

Most of this release comes from the issue tracker. Shizuku and its forks can finally reach OpenTasker, and Setup no longer crashes on some Android 8 to 12 phones. MacroDroid backups import now. You'll also find the new actions and contexts people asked for, plus several fixes for Android 17's background rules. It's signed with the same key as v0.2.93 and v0.2.94, so it installs straight over either.

Added

  • OpenTasker speaks Simplified Chinese, a full translation contributed by coolLitterBear (#24). Pick it under Android's per-app language setting, or it follows your phone.
  • Run Task has an Inputs section. Each input becomes a variable in the task it runs, so a shared "Weather" task can read {{ city }} from whichever task called it. A lowercase name stays inside that task and a capitalized one sets a global. The engine already passed these along, but until now the only way to add one was to edit an exported bundle by hand.
  • An incoming call can start a task while the phone rings. The task gets {{ event.incoming_number }} and {{ event.incoming_known_contact }}, and the profile can match strangers only or part of a number. Reading the number takes a new Call log permission, which Setup asks for. A hidden caller, or one nobody could check, never counts as a stranger.
  • Two new templates search an unknown caller's number on a site you choose (#19): Search incoming phone numbers puts a Search button on a notification, and Search incoming phone numbers automatically opens the search right away. Both take an address like https://duckduckgo.com/?q={number}.
  • Notification buttons can open a web address, with the same allowed links as Open URL. Tapping one works from the background without any extra permission.
  • A new urlencode template filter makes a value safe to put in a web address.
  • A new Bluetooth device nearby context turns a profile on when a device you name is close by, even if it never connects (#25). You can use its name or address, and the Inspector lists what's around. Pairing a phone once lets Android recognize it after its address changes.
  • A new Connect or Disconnect VPN action turns a WireGuard or Tailscale tunnel on or off, and two new templates use it to drop the VPN on your home Wi-Fi and bring it back when you leave (#16). Neither app says anything when it ignores a request, so the action watches for the VPN to change and tells you what to check when it doesn't. Templates can now carry an exit task, which is what makes the "bring it back" half work.
  • A new Toggle Wi-Fi Hotspot action turns the phone's hotspot on or off through Shizuku on Android 11 and newer. It only reports success once Android says the hotspot changed, and when it can't, the run log says why, whether that's a carrier's plan check or a phone without tethering. Tasker's WiFi Tether action now imports to it and exports from it.
  • Play Sound and Say have an Audio stream choice, Music or Alarm. On Android 17 a task started in the background can't be heard on Music, and Android lets it through on Alarm once exact-alarm access is granted in Setup. Alarm follows the alarm volume, so it's opt-in. Tasker's alarm stream comes across on import and export.
  • Each Shizuku action's Setup note now says what it can do to your phone, like dropping every connection or restarting without asking.
  • A new Run Shizuku Script action runs your own shell script as the Android shell user, so it can do what rish or adb can (#15). Approve the script's path and SHA-256 under More > Settings first. OpenTasker reads the file once, checks the hash and runs those same bytes, so swapping the file after the check gets you nothing. Output goes into the same capped variables as a Termux script, and the Shizuku kill switch stops this too.
  • The README now says OpenTasker doesn't use an accessibility service, so Android's Advanced Protection limit on those services doesn't touch it. It also got a cleanup pass for wording.

Security

  • Text from outside the phone can't run as a template anymore. A variable filled by a text message, a web response or a broadcast could hold {{ API_TOKEN }}, and forwarding it through %sms_body read that as an expression, so the secret's real value went out with the message and a condition could be steered the same way. What a variable holds now stays plain words, and templates you type into an action work as before.
  • The build moves to Kotlin 2.4.20 and KSP 2.3.12. Kotlin 2.4.20 fixes CVE-2026-53914, where the compiler could be fed a tampered build cache. OpenTasker has only ever built with a local cache, so no released APK was exposed, and now a build from source isn't either.

Fixed

  • A Termux script that works when you type it can fail from OpenTasker, because Termux starts these runs with a plain PATH and doesn't read .bashrc or .profile. A rish you added to your PATH comes back as not found (#15). The run log now says that when a script exits with code 127, and every failed script's entry says where its error output went. The Approved Termux scripts card mentions it too.
  • The file actions' sandbox now refuses a symlink whose target is missing. The check asked whether the path existed first, and that follows the link, so a dangling one slipped past it until the write itself.
  • When Shizuku was ready, the only control on its Setup row was an arrow labelled Review app settings, and tapping it turned power mode off. The row now has a Disable power mode button that says what it does.
  • Tasker XML import read several actions wrong, which real exports made obvious. For had its variable and its list swapped, Display Timeout read hours as minutes, and Launch App could take the Data field as the package. A variable or a sum in a number field (Perform Task's priority, Wait, volume) got dropped, the Toggle choice on the on/off actions was lost, and HTTP Request read its method from the wrong list. Import now follows Tasker's own action table. It also understands Lock, Kill App, Send SMS, Custom Setting, Bluetooth, Airplane Mode, Read File, Music Play, Media Control and the older HTTP Get and HTTP Post, which used to arrive as placeholders. Imported profiles still start disabled and wait for your review.
  • Tasker XML export now writes what Tasker expects to read. The Log action used to go out as code 905, and in Tasker that's Location Mode, so it's reported as skipped instead. Playing a file, the media keys, on/off actions, Display Timeout, Wait and app fields all use Tasker's real layouts now, and Wi-Fi, Bluetooth, Airplane Mode, Lock, Kill App, Custom Setting, Send SMS, Read File, Write File and Set Clipboard export too. If you re-import a Tasker file an older OpenTasker exported, check any For and Display Timeout actions, because those were written the old wrong way.
  • Bluetooth connect and disconnect triggers couldn't fire on Android 12 and older. The permissions Android 11 and older ask for weren't declared, and the way the receiver was registered shut out the Bluetooth app's own broadcasts on anything below Android 13.
  • A task started by a text message can read it (#27). The profile could match on the sender or the words, then the task got none of it. It now gets {{ event.sms_sender }}, {{ event.sms_body }}, {{ event.sms_kind }}, {{ event.sms_message_count }} and {{ event.sms_subscription_id }}, and a Notification trigger hands over {{ event.notification_package }}, {{ event.notification_title }} and {{ event.notification_body }}. All of them show up as chips in the action editor. An HTTP Request forwards the real text, while the run log and any held trigger keep a placeholder for who wrote and what they said. Only the phone's own telephony service can deliver a text to OpenTasker now, so another app can't start one of these tasks with a fake message.
  • MacroDroid backups import (#30). The token limit that protects imports was hit by any whole-app .mdr of more than about 1.5 MB, and a password-protected .emdr was read as broken JSON. A MacroDroid file now gets a limit that fits a real backup, while what it converts into stays under the ordinary limits, and an .emdr asks for its export password and opens. When any import goes over a limit, the message names that limit. MacroDroid's Fill Clipboard action now comes across as clipboard.set, and if its text holds magic text the review says that part won't be filled in.
  • Shizuku and its forks can reach OpenTasker (#22, #26, #31). OpenTasker never declared the small provider Shizuku uses to hand an app its connection, so Setup said Shizuku wasn't running even with the service up, and no elevated action could work. Setup also insisted on the stock Shizuku manager app, which shut out Sui and the forks, so a running service now counts however it got there. Open Shizuku opens Shizuku instead of its App info page, and Setup tells you when the permission was granted or refused. An elevated action that can't reach Shizuku, or finds power mode off, now tells you what to do about it in the run log.
  • OpenTasker's Shizuku helper process now ends when it should. Shizuku asks it to stop when OpenTasker closes, updates or has power mode turned off, but the helper was listening for the wrong signal, so each one stayed running as the shell user until Shizuku restarted, and every restart added another. A script still running at that moment gets stopped with it. Helpers left by older versions go away the next time Shizuku restarts.
  • The airplane mode action now turns the radios off. It used to write the setting and report success, which moved the switch on screen and left the modem and Wi-Fi on. It goes through Android's own airplane mode command now, and on a version without that command (Android 8) the run log says the change didn't happen.
  • Setup and Settings no longer crash the app as they open on Android 8 to 12 phones that can pair companion devices, which includes Galaxy phones (#20, #21, #23). If one of Setup's checks fails on a particular phone, even because that phone's Android build lacks the call it makes, its row now says "Couldn't check" and the rest of the screen carries on. The same goes for the list of paired devices.
  • A time trigger that can't be delivered no longer wakes the phone every five seconds to retry. Recovery now waits 5 seconds, then 30, then 5 minutes, and after that leaves it to the engine's own watchdog.
  • On Android 17, a Temporary State action that changed the volume or the ringer now puts it back afterwards. The restore ran without the automation service's permission to change audio in the background, so Android refused it and the phone stayed at the temporary level.
  • The home screen widget, the launch screen and the notification accent use the app's current colors. They were still on the old sage palette.
  • Flow shows what a State context watches. Every one read key=<redacted>, because the field that names the state looked like a secret to the display filter.
  • The import review counts what it is importing. A bundle of three profiles and three tasks read "across 6 profiles", and now says 3 profiles and 3 tasks.
  • Picking a project no longer hides a profile whose task lives in another project behind the first-run screen, and the header counts match the list under them.
  • Three removals no longer happen silently. Deleting a watched setting in the Inspector or revoking a Locale grant in Settings shows what was removed, with Undo. Removing a companion device names it and says how to add it back, or says so if Android refused. Undo puts back only what's still missing when you tap it, so a watched setting added in between isn't lost, and a grant whose task was deleted stays gone.
  • Variable, scene and project-name editors stay open until the save is accepted. A refused save, like a duplicate name or a secret the keystore wouldn't take, used to close the dialog and lose what you typed. Move up is off on the first project and Move down on the last, where they used to report a move that never happened. A double tap on Save makes one scene, not two, and moving projects quickly can no longer leave two of them sharing a place in the list. The next move tidies up any that already do.
  • The context editor says which field is wrong. A time like 25:00 or a latitude out of range greyed out Save with nothing marked.
  • Setup and Diagnostics no longer flash "Ready" or a red "Needs attention" for a moment before they have checked anything.
  • The Inspector no longer flashes "Context inspector unavailable" as it opens. It waits for your profiles to load and says there are none only when that's true.
  • Diagnostics says so when its health check fails or hasn't answered after 15 seconds, and offers Retry. It used to read "Loading" forever.
  • Stopping an import or a preflight no longer reports it as failed. Stop used to show an error and write one to the log for something you asked for.
  • Times in the run log, the Inspector and Diagnostics follow your phone's date order and 12- or 24-hour clock instead of always reading like 2026-09-26 18:40:00.
  • A backup taken while tasks are running is a clean copy. It used to copy the database file while other writes could still land in it, so a busy moment could leave a backup that failed its integrity check or mixed two points in time without saying so.
  • Play Sound on the Alarm stream was muted on Android 17 when a trigger started it in the background, even with exact-alarm access, and the run log still said it played. Android only honors that access once its audio server has refreshed its record of it, and a media player never asks it to. Play Sound now requests audio focus first, which does.
  • The actions that open an app, a link, the home screen or an activity intent logged success when Android had silently blocked them in the background. They now log a failure that names the setting that fixes it, Overlay access in Setup. The contact picker and the app archive confirmation stop right away for the same reason, where they used to wait on a screen that never opened. A home screen widget or shortcut tap can still open them without that setting. A Quick Settings tile tap needs it, even though Android's docs list tiles as allowed.
  • A Quick Settings tile with no task went dead once you backed out of its setup screen, because Android ignores taps on a tile marked unavailable. It now stays tappable and says Tap to choose a task.
  • The Reboot action handed Android the word false as its reboot reason, so the phone recorded reboot,false as why it restarted. It now restarts with no reason given.
  • A restore keeps the database it replaced, including whatever the app wrote just before it closed, and Setup offers to roll back to it. That copy and the file from a restore that failed were missing from every list and count, so they sat at full size until app data was cleared.
  • At a large font size or in a short window, dialogs cut off whatever didn't fit with no way to reach it. The task editor's Run both and Wait choices were out of reach, and so was the app picker's search box. Dialog bodies scroll now, and the action number badges in a task grow with the text instead of clipping it.
  • In a short window at a large font, the keyboard covered every match in the app picker while you typed. The keyboard's search key now puts it away and scrolls down to the matches.
  • Sharing something to OpenTasker no longer takes the app down if Android refuses to start its engine at that moment. The share stays queued and the engine picks it up the next time it runs.
  • Every task started from another app wrote a warning with a stack trace to the system log, because the receiver read the protocol version number as if it were text. It now reads only the variable extras.
  • On a tablet or another wide screen, the header covered the top of the side navigation, so there was no way to open Profiles or Tasks. The navigation starts below the header now.
  • Setup called Screen recording Ready on phones older than Android 15, where that trigger can't fire at all. The row is gone there. Setup now shows a card naming each enabled profile that waits on something a newer Android added: camera or microphone use before Android 11, a broadcast from one named app before 14, screen recording before 15, and Advanced Protection or Bluetooth key changes before 16. The Inspector says the same on that profile's card. Those profiles used to sit there never firing, with nothing in the run log to say why.
  • TalkBack read every bottom tab twice ("Tasks, Tasks"), and the More menu, the Create variable, Create Scene and Add Element buttons and a few card headers did the same. Each Re-trigger behavior choice in the profile editor said its own name twice, on screen as well, and now says what it does. Each screen's title got read a second time from the icon beside it. The Profiles search box announced itself as "Search variables" and the Tasks one as "Search task or message". The Run Log search box has a label now, its filter button says Show filters instead of Expand, and the script allowlist cards count approved scripts instead of reading "0 action(s)".
  • After a template sent you to Setup, the "Finish setting up your new automation" banner stayed for the rest of the session and kept saying the template needed access, even with every item on the screen marked Ready. It goes away once nothing the template needs is still pending.
  • The Flow screen's summary showed a check mark next to its issue count. It shows a warning sign when there are issues now, and TalkBack no longer reads "Flow" from that icon.

Changed

  • Setup now lists Display over other apps for any enabled profile that opens an app, a link, the home screen or an intent, since without it Android drops those from the background and says nothing.
  • The Install section of the README lists the release signing certificate in the form AppVerifier reads, and a release build now refuses to publish an APK signed with any other key.
  • Text throughout the app drops its long dashes. Ranges read "1 to 5", and separators use a dot.
  • Before a release is tagged, tools/smoke-old-api.ps1 installs it over the previous release on Android 8 and Android 10 emulators set up like a Galaxy phone and opens every screen. Any crash stops the release. This is the check that would have caught #20.
  • The main screen's view model hands the Run Log and the Setup card's backups to two classes of their own, and a test holds it under 2,000 lines. Nothing changes on screen. It was two lines short of its size limit, so the next feature on any screen would have failed the build.
  • The launch screen says what it's waiting for, like restoring a backup or encrypting an older database, instead of only spinning.
  • The external intents guide no longer tells Home Assistant Companion users to send RUN_TASK. Only apps signed with OpenTasker's own key may send it, so Android refused Companion without a word. The guide now shows the token-checked PUSH_EVENT route with a push profile, says where Android 17 records a refused broadcast, and covers the engine having to be on.
  • The performance benchmarks also time the automation engine's start, from the service coming up to its first load of your profiles, next to cold start and the first trip to Tasks. The Baseline Profile shipped with this release was regenerated from the current code.
  • A running backup shows a progress bar under its button. So does a preflight rerun, and its Close button turns into Stop until the run finishes. Reading an automation file fills its bar in two steps instead of looping. Backups still can't be stopped partway, because a stopped Export would leave a broken file where you asked for the backup.

Reports this release changed something for

#15, #16, #19, #20, #21, #22, #23, #25, #26, #27, #30, #31, and pull request #24 (Simplified Chinese).

Install

Download OpenTasker-v0.2.95.apk below, or let Obtainium pick it up. Coming from v0.2.92 or earlier? That build used a different key, so export a backup from Setup, uninstall it, then install this one.

Verify

OpenTasker-v0.2.95.apk SHA-256: c5435e8ea4f27ab529f60f95a16f64ab4143756bc126b2245142e58a2c6310f9

Signed with the same certificate as every release since v0.2.93. AppVerifier reads it like this:

com.opentasker.app
DB:A1:AA:88:E3:7B:90:15:5F:CA:31:35:CA:3B:78:1D:E9:2C:22:51:07:E4:7C:98:06:E7:5B:F8:80:55:FD:D8