Tasks getting stuck is a common problem (often from plugins that don't timeout, etc.) and there isn't a current global option to kill a task that is stuck. Although you can setup timers using that Timer project that is floating around, I think another method would be to add another %TRUN variable as %TRUNT (Tasks Running w/Time). It would receive the same data as %TRUN, except it would have the current (at reading of the %TRUNT state) elapsed task times (visible in the Running Tasks view).

This would allow users to more easily monitor %TRUNT variable (either on a timed

Right now the Flash Notices with "Tasker Layout" are pretty powerful; I use them basically everywhere as a cheap way to get user notices/interactions and have some aesthetic flexibility.

One enhancement I'd like to suggest is to add a special variable that gets passed to the "Perform Task" option for how it was dismissed, alongside adding swipe up/down/left/right and click/long-click detection.

*Note: Might need a bool checkbox to "enable gesture swipes" since some users may not want swiping enabled for some notices.

The various gestures would all act like the current "dismiss", except they'd pass a "dismiss method" variable.

• If

We should be able to import and export APK signing keys in tasker.

If we have our own key, we want to use it both in tasker and android studio.

My next feature request is to update the sqlite version in the sql query action. I would like to use many of the date time functions only available in later versions.

When I query "SELECT sqlite_version();" it outputs "3.39.2

Compare the two user guides' pages on date and time functions:

[3.39.2 - September 2022](https://web.archive.org/web/20220902005517/https://www.sqlite.org/lang_datefunc.html)

[3.53.0 - Latest Version ](https://www.sqlite.org/lang_datefunc.html)

The latest version has the timediff function that is missing from the earlier one. It also has 14 more substitutions and 9 more modifiers. Those would be very useful for a few of my projects. 

Thanks! 

Hi João, per your reply on reddit to add a ticker here... I am hoping you would consider extending the back button navigation you introduced in Scenes v2 to the main Tasker navigation menu as well.

Currently, navigating two or three levels deep into a submenu, only to realize you are in the wrong place, requires returning all the way to the three dots menu to start over. A small back button at each menu level would resolve this and meaningfully reduce friction for frequent users.

Given that the component already exists in Scenes v2, this feels like a natural

When some apps (KWGT is one such example) need to prompt the user to select an image, installed icon packs (as well as other image sources like gallery apps) show up in the Open from menu. If the user selects one, he can search through the icon pack to select any icon in it as an image.

However, when Tasker needs the user to select an image, the resulting file picker does not contain image sources in the Open from view. It's just a plain file picker.

As it is now, user must extract icons from packs and place the

Add Ollama as the third configurable AI provider, with a configurable username+password and IP Address+Port.

This is one area of Android I don't think Tasker has hooked into, infact many apps don't seem to hook into it, and I only became aware it was possible when I saw Anki do it (screenshot below). The menu I'm talking about is the selected text long press contextual menu that often has Copy/Paste/SelectAll (and occasionally Define) in it. This would serve as a quick way to copy text to a specific Task you want to use to process said test.

A Google searched yielded this: Google Copy/Paste Menu

I would suspect that there might be a way for Tasker

Long-press a task or profile → open menu → View Log.

The current Run Log is powerful but becomes hard to read with many automations running. Seeing only that specific task or profile's past runs would make debugging faster, clearer, and more approachable while keeping the global Run Log unchanged.

The current tasker share activity com.joaomgcd.taskerm.datashare.export.ShareDataConfig doesn't provide any information about what's included during export.

Tasker will by default include everything that is included in the project. Even those who doesn't belong to the project, which the user may not want to share to begin with. 

While I must acknowledge that including them may be very convenient to ensure the export works properly, it looks dubious to me that the user is not informed at all about this. Furthermore the default behaviour is that we have to back out to export. Which is not the usual way to handle confirmation.

As of now only Notification listener and Accessibility service is available. Whereas there are a several others that hasn't been exposed yet.

BIND_APPWIDGET BIND_VOICE_INTERACTION BIND_QUICK_SETTINGS_TILE BIND_DEVICE_ADMIN BIND_JOB_SERVICE BIND_INPUT_METHOD BIND_CONTROLS BIND_SCREENING_SERVICE BIND_INCALL_SERVICE BIND_REMOTEVIEWS Shizuku

Hello,

I'm writing to report an issue with the "Notify Live Update" action on my Google Pixel 10 Pro. Currently, the notification content is not appearing on the lock screen or the always-on display.

I believe this is due to the "Show sensitive content on lock screen" setting being disabled.

Would it be possible to add a checkbox on the action that allows users to specify whether a particular notification's content should be treated as sensitive or not?

I have attached screenshots of my lock screen both with and without the sensitive content setting enabled for reference.

Convert regular variables to Task/Profile/Project variables - Something similar to if blocks.

Having some kind of indication that there are variables Task/Profile/Project - Sometimes coming back to an old project you don't remember if you had your variables as a Task/Profile/Project.

It would be really nice if we could default "continue after error" to be checked by default, either by action type or at least in general for all actions.

I have some projects that have an complex connection of tasks that call other tasks, and sometimes this spans across multiple projects.

So just like you have the "Show Linked Projects" action on each task, I would like a similar action that shows which other tasks are calling the selected task (i.e. tasks that call this task from the "Perform Task" action). 

You could call this "Show Linked Tasks". :)

I know this can be done from the search option by entering the name of the task, but this is cumbersome and shows a whole lot of other noise than

Hello! I beg you, please solve the problem with speech recognition, this problem has been around for 10 years and no one is talking about it. When I use recognition from Bluetooth headphones, the microphone of the headphones does not work, but the microphone of the phone, which makes it impossible to use such a profile when the phone is far away. This is not a problem with the headphones, I tried 15 from different brands and it's the same everywhere, which is interesting, everything works correctly with Google Assistant/Gemini. I tried AutoVoice, but it works unstable on Android 13.

Currently, names of profiles, tasks, scenes and variables are cut off if they are too long. If there are many of them and you categorize them (for example with dashes in the name) - it becomes hard to differentiate between them, because you have to edit the name to read it fully. Therefore, i suggest to make them either running or wrap in multiple lines if too long (in all 4 tabs).

Additionally, i suggest to put the values of variables under its names instead of right from it (on the "Vars" tab), because these can be long as well

With Java Code actions, the possibilities in Tasker are endless. I’ve been thinking about the reusability of some of my Tasker projects that rely on this action, and it would be great if we could create custom Tasker actions (similar to Flash or Notify) using the Java Code action. It would work much like what we can already do with AutoTools WebScreens.

This would also be a great way to share complex tasks while providing an easy configuration method for non-advanced users.

Let %select_indices control which rows should be marked as already selected when a multi scene menu is about to be displayed. 

For example:

1. Labeling an action.
2. Commenting projects, profiles, and tasks.
3. Explain projects, profiles, and tasks.