User defined text or allow the setShowWhen tag to be used.

https://developer.android.com/develop/ui/views/notifications/live-update#status-chips

Would love to see a few additions to tasker widget v2! I'd be able to leave kustom entirely if it had the following:

1. the ability to rotate elements (either around centre or other defined anchor points)

2. the ability to filter elements by other elements (i.e. remove portion of element that's overlapped by another element)

3. Adding a "blurr" option in addition to color would be sick as well!

In AutoInput v2, there is a "Wait For Element" action that waits until an element appears on the screen.

My current AutoInput workflow is like this: click(id, %button_id) --> waitForElement(id, %loader_id) --> click(id, %button_id)

Since the loader's element ID is often hard to get (as it disappears instantly due to fast loading), could you add a "Wait For Element to Disappear" action that waits for an element to disappear?

This way, the workflow would only depend on %button_id and would become like this: click(id, %button_id) --> waitForElementDisappear(id, %button_id) --> click(id, %button_id)

*Note: The loader element makes the button disappear from

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.

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

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

I have an idea I suggest the developer add the following feature would be interesting if it were possible to trigger a task through a trigger triggered by a simple clap Either with the snapping of fingers picking up the sound generated through the palms or snapping the fingers through the microphone obviously and with that the task assigned to that respective trigger would be started.

Hii, in some devices (including mine Lenovo) Tasker can't detect logcat (it always shows no log captured) with READ_LOGS permission because device manufacturers modified the device in someway. Not any other app which relies on READ_LOGS permission can do it too but I found an App which reads logs with adb_wifi permission (adb tcpip 5555)

So I'm wondering if Tasker can add it too.

Additionally : could you bring back Android 6 support for logcat detection.