I'm working on a project to intercept the android.bluetooth.device.action.BATTERY_LEVEL_CHANGED intent using tasker and shunt the battery level to display as a widget on my smartwatch. I'm planning on sharing this to the r/pebble subreddit community, but I've run into a performance problem.
When a headset connects, or it's battery level changes, the watch updates in less than 3 seconds, which I consider acceptable -- however when the headset disconnects, the intent is recieved immediately but tasker processing takes 20-30 seconds, which is less responsive than I'd like.
I'd like to determine which step in the task is taking so long; I've considered adding statements to write timestamps to files in order to determine which step or steps is the culprit, but adding ~20 statements and then deleting them is tedious; before I start in on that I thought I'd check if tasker had any native performance profiling -- unfortunately googling for that is proving near impossible (any set of terms I can come up with means something different in tasker jargon than it does in optimization jargon).
TL;DR -- Does tasker have some native tools to diagnose slow running tasks?