Hi Ed,
This actually goes right along with the OP's question. The "Kill App" does not work because there really is nothing to "Kill". JARVIS only runs when a text is received, and kills itself when finished.
You might ask yourself how is it JARVIS can run when a text message is received, without already having a running process? That is the beauty of "Intents". Basically, your phone stores a list of actions to run when a particular Intent is fired, so the actual turning on/off that happens within JARVIS is simply adding/removing itself from that list.
Unfortunately at this point there is no way for a tasker to replicate this turn off process, unless it could manipulate the "action list" as described above. Even then, without JARVIS knowing of this change it could cause some funky issues :blink:.
I will make note of this and possibly implement a way in the future, thanks for the suggestion.
BT compatability is on the way.