Tasker automatically creates variables for the extras in an Intent Received trigger, but those variable names can (rarely) conflict with existing Tasker variables:

https://groups.google.com/g/tasker/c/k03Lw8tGSHA

Giving an option to add a prefix to the extras' variable names, like in the Get Calendar Events action, would fix this issue without impacting the functionality of existing tasks, e.g. the conflicting %priority extra could be changed to %ntfy_priority.

Please add a native Profile State and variable for IMS / Wi-Fi Calling registration status.

Useful values: - IMS registered: true/false - IMS transport: WLAN/IWLAN/WWAN/none - VoWiFi active: true/false

Use case: Trigger automations when VoWiFi drops while Wi-Fi is still connected, without polling dumpsys connectivity through ADB/Shizuku.

If Android does not allow this as a normal app permission, please consider supporting it through ADB Wifi, Shizuku, root, or a helper plugin.

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.