14
Completed

Add a wait period to the flash action

The newer versions of Android have created what I would definitely call a bug with the wait action. Now if I have multiple flashes no matter if the first flash is set to long or not the second flash will immediately overwrite the first. This happens so fast I can not even see the first flash action, leading me to believe it never occurred which makes debugging very difficult. The fix for this is to add a wait action after the flash action. Which means every flash action now I will have to add a wait action after it to ensure I can see it.

I propose adding a wait feature to the existing flash action with the default set to 500ms. This seems to be enough time to be able to see the flash, then if I need it to be longer I can increase the wait time, but at least I will see the flash with the default setting of the flash action and not have to add a wait action for every flash action. 

Follow

3 replies

Votes Newest Oldest

Good idea, thanks!

Comment

I thought it was just me! The new behaviour is so irritating. Can we set the default wait in preferences? 500ms seems short to me.

Comment
RD

I did not make that clear in my suggestion. The way I was thinking it would have a adjustable wait period within the action (just like a "wait action" only the default setting for that wait period would be 500ms, so  you would not have to set it every time you use the action. 

This is now available in the beta: https://www.reddit.com/r/tasker/comments/qwwenb/dev_tasker_5152beta_target_api_30_for_everyone/

Comment
Reply