Profile cover photo
Profile photo
jeremy barrett
62 followers
62 followers
About
jeremy's posts

during various executions of a task, i see different results in logcat output, some of which involve the issuing of an android BACK KeyEvent. 

for instance:
sample run a:
V/GOOGLENOWINTERCEPT( 4020): It's a new voice command
V/GOOGLENOWINTERCEPT( 4020): Should do google search: false
V/GOOGLENOWINTERCEPT( 4020): Results checker: Command matched
V/GOOGLENOWINTERCEPT( 4020): Text isn't present: press back
V/GOOGLENOWINTERCEPT( 4020): Text isn't present yet: wait
V/GOOGLENOWINTERCEPT( 4020): Text isn't present yet: wait
V/GOOGLENOWINTERCEPT( 4020): Text isn't present yet: wait
V/GOOGLENOWINTERCEPT( 4020): Text isn't present yet: wait
V/GOOGLENOWINTERCEPT( 4020): Text isn't present yet: wait
V/GOOGLENOWINTERCEPT( 4020): Text isn't present yet: wait
V/GOOGLENOWINTERCEPT( 4020): Text isn't present yet: wait
V/GOOGLENOWINTERCEPT( 4020): Text isn't present yet: wait
V/GOOGLENOWINTERCEPT( 4020): Text isn't present yet: wait
V/GOOGLENOWINTERCEPT( 4020): Text isn't present yet: wait

sample run b:
V/GOOGLENOWINTERCEPT( 4020): It's a new voice command
V/GOOGLENOWINTERCEPT( 4020): Should do google search: false
V/GOOGLENOWINTERCEPT( 4020): Results checker: Command matched
V/GOOGLENOWINTERCEPT( 4020): Text is present: press back and wait

sample run c:
V/GOOGLENOWINTERCEPT( 4020): It's a new voice command
V/GOOGLENOWINTERCEPT( 4020): Should do google search: false
V/GOOGLENOWINTERCEPT( 4020): Results checker: Command matched
V/GOOGLENOWINTERCEPT( 4020): Text isn't present yet: wait
V/GOOGLENOWINTERCEPT( 4020): Text isn't present yet: wait
V/GOOGLENOWINTERCEPT( 4020): Text isn't present yet: wait
V/GOOGLENOWINTERCEPT( 4020): Text isn't present yet: wait
V/GOOGLENOWINTERCEPT( 4020): Text isn't present yet: wait
V/GOOGLENOWINTERCEPT( 4020): Text isn't present yet: wait
V/GOOGLENOWINTERCEPT( 4020): Text isn't present yet: wait
V/GOOGLENOWINTERCEPT( 4020): Text isn't present yet: wait
V/GOOGLENOWINTERCEPT( 4020): Text isn't present yet: wait
V/GOOGLENOWINTERCEPT( 4020): Text isn't present yet: wait

sample run d:
V/GOOGLENOWINTERCEPT( 4020): It's a new voice command
V/GOOGLENOWINTERCEPT( 4020): Should do google search: false
V/GOOGLENOWINTERCEPT( 4020): Results checker: Command matched
V/GOOGLENOWINTERCEPT( 4020): Text is present: press back and wait
V/GOOGLENOWINTERCEPT( 4020): Text is present: press back and wait
V/GOOGLENOWINTERCEPT( 4020): Text is present: press back and wait
V/GOOGLENOWINTERCEPT( 4020): Text is present: press back and wait
V/GOOGLENOWINTERCEPT( 4020): Text is present: press back and wait


note that all four runs recognized the user's speech as the same text string.

i don't claim to understand the output posted above, but it is very unsettling that seemingly identical input results in such different output. i don't know what it means for text to be present, but it's striking that sometimes the text is there, and sometimes it is not. more disturbing is that sometimes a BACK KeyEvent is dispatched, and sometimes not. because my purpose in using tasker/autovoice is to communicate with a launcher to start/control other apps, activity stack manipulation is a big deal that i very much want to avoid.

my question is threefold:
1) what could be causing the autovoice task to be responding unpredictably
2) why is tasker/autovoice issuing a BACK KeyEvent as part of its response to a recognized command
3) is there a way to ensure that the BACK KeyEvent is never issued by a task/profile?
Wait while more posts are being loaded