I think it would be very helpful for there to be an action to get the names of Project, Profile, and Task variables.

The action settings would have the user indicate whether they want to get a list of the Project, Profile, or Task variables. By default, the action would get the variables from its local context, but an option could be added to get variables from a named profile, project, or task.

By default, the action would return an array of those variable names, but a checkbox could enable returning a JSON object containing the variable-value pairs.

Joao, thanks for this wonderful app. 

I think that would be nice to permit bigger scenes than physical display and that can be scrollable.

Thanks in advance

It would be nice if Tasker was capable of displaying scenes in full screen including behind any notches and camera holes. Right now there's no way for a scene to extend all the way to the top and bottom of a screen if the phone uses a notch or hole-punch for the front facing camera.

Please enable a Tasker scene to be moved onto the status bar. A potential use case is to design a pseudo-notification LED for AMOLED displays

As a user of Tasker, I need the way to be able to ensure that a scene is, and remains, a certain size, even after the scene has been edited through the Tasker Scene Editor UI. Often it is needed for the scene to be fullscreen and that any actions that alter the screen size/orientation cause the scene to be resized to fill the new screen size.

Sometimes, it is nice to be able to resize a scene programmatically to a specific size (not necessarily fullscreen) from a Task's or Scene's actions for a variety of reasons. An option in Create

Greetings! I would like to leave a tip: in the next update, you can put the option to use percentage (%) to change the size of the resolution of the scenes, besides the pixels? It would help a lot to fit all screen sizes. Ex: to cover the entire screen, just place 100% vertical and 100% horizontal. Thank you.

There should be an action to change the size of scenes so that scenes could be created dynamically depending on the screen size of the device they are being run on. There is already a set element size action, an additional set scene size action is needed.

Optionally variables should also be settable for both the geometry of scenes and the geometry of scene elements if someone wants to use that instead.

João is already aware of this missing feature and adding this idea is just for his convince. 

Creating a scene for several device is just a pain, the activity layout should scale according the screen size of target device, it shouldn't use any absolute layout or fixed aspect ratio.

Currently, the Calendar Insert action lacks a "Color" field. To set a specific color, users must:

​Create the event.

​Use Test Get Calendar Events to find the newly created Event ID.

​Use Calendar Update to apply the color.

​The Solution: Add a Color input field directly within the Calendar Insert action. This field should ideally support:

​Alternatively, you can slightly optimize the process by outputting the event id as local variable from the Calendar Insert action.

​If

Currently, the Calendar Entry (State) context is only active during the exact event time.

In real-world usage, calendar events often don’t strictly follow their scheduled time. Meetings can start earlier or run longer than planned.

Example: An event is scheduled from 10:00 to 10:30

• It may start at 09:45

• It may end at 11:00

To handle this, it would be very useful to add offset options directly to the State context:

• Start Early (minutes)

• End Later (minutes)

Example usage:

• Start Early = 20 → profile activates at 09:40

• End Later = 30 → profile remains active until 11:00

This would

It's been a hard thing to transmit messages from one device to another. Such as simple  sending a long text message from a computer to a android phone. 

Using the Join to share clipboard requires connecting to Internet and exposing your content go Google. 

Using Chat softwares has much much limitation. 

Even if our devices are under same wifi network, it's hard for us to send a simple message from one device to another. 

So, if Tasker can run a background http server, when there is a http post or http get sent to this server, tasker can triger an

He could change Java Functions and declare the complete code, since this action is very confusing and often does not even like how it should, I went to test a Java action to make a toast on the top of the screen and the taste made this action but did not then close.

Add Java tag support for public taskernet to make it easier to find uploads that contain Java function or Java code action. It might be a good idea to automatically assign the tag when uploading to taskernet as well if the the file contains those actions. This can be done in the upload dialog in Tasker app.

As of now, Java function in Tasker only allows the user to define the code line by line, only with one action. We also have to handle the flow control with Tasker actions. Tasker tries to show a limited of character per action by default as well.

Thanks to all of them, the code becomes hard to read and debugging the code is not easy either since the code are branched into multiple actions.

Having a Java interpreter like BeanShell would fix them. https://beanshell.github.io/license.html

We could write full scripts in one place like with JavascriptLet action. Handling flow control and error

Samsung's Modes & Routines (M&R) app exposes a few different hidden content providers that can be used by Tasker to run Routines and turn Modes on/off. The advantage of M&R is that it's a system app, so it can control many things that Tasker cannot do alone. For instance, users can toggle Wi-Fi or disconnect a Bluetooth device without needing Shizuku/ADB Wi-Fi. Additionally, there are many other Samsung-specific actions (not going to list them all here). If Tasker could tap into these actions, it would really open up the door for Samsung users to automate things more easily and automate

Being able to create apps within Tasker is probably its neatest feature, but there's one rather annoying caveat: there's no option to export with additional files!

You have to use convoluted workarounds such as this: Reddit

There's also an app that helps you do it but it has file size limitations. Play Store

Shizuku:

https://github.com/RikkaApps/Shizuku

Using system APIs directly with adb/root privileges from normal apps through a Java process started with app_process.

Sui:

https://github.com/RikkaApps/Sui

Modern super user interface (SUI) implementation on Android. It mainly provides the ability to use Android APIs directly (almost in Java as the identity of the root, and start app's own AIDL-style Java service under root.

Swiftbackup,sai and icebox already support shizuku,and greenify will supoort it soon.

https://github.com/RikkaApps/Shizuku

The very, very short description of Shizuku is that it is an App that allow other apps to use actions reserved for ADB or Rooted devices.

Shizuku is on the PlayStore, and the whole procedure is incredibly easy in comparison to Root, and even ADB Wifi.

And yeah, I know you've implemented ADB Wifi shenanigans, but If the user has Tasker and any of these apps, then they are likely not going to want to do a separate procedure for Tasker. Unlike ADB Wifi and the Permissions App, it also means that tutorials and guides are offloaded to Shizuku

It would be nice to acquire ADB privilege from Shizuku rather than having it separately.

It'd be great to be able to copy the If section of one action to another.  There are certain criteria I use over and over, and typing them each time leads to typos.  And it's so frustrating to get a complex If tweaked just right and then realize I should have used a different action.  It'd be nice to be able to use Switch Action without losing the criteria, or to be able to copy the existing criteria and paste them into a new action.

I'm not talking about copying the variable or value individually.  I know that's already possible.