Failure to process request when using Raise to Speak feature

[usagora]

I've experienced this on both AW Series 4 and 6. Often when I raise my watch and say, for instance, "Remind me Monday at 3pm to call [name]," I'll see my words transcribed onto the display, but then they instantly disappear and nothing happens. Does anyone else experience this fairly frequently? Any idea why this happens? I'd say 80% of the time raise to speak works and 20% of the time it does this.

 

[usagora]

So NO ONE else that has read this thread has experience this issue? Happens to me multiple times per day!

 

[Apple_Robert]

I haven't experienced it with my series 6. What happens when you press the crown and say remind me...? The latter method is what I use.

 

[usagora]

I haven't experienced it with my series 6. What happens when you press the crown and say remind me...? The latter method is what I use.

Well if you're not using Raise to Speak, that's why you haven't experienced it I prefer this method, because it's far more convenient, especially if my hands are messy, such as when I'm cleaning or when preparing food and my hands are dirty or wet. For instance, I count calories and I use this feature all the time to note how many grams of each ingredient I'm using as I'm preparing something so I can go back to my reminders later and enter those weights in a spreadsheet. E.g. "Remind me yogurt 72 [grams]" It's just frustrating when it fails and I have to keep repeating myself 2-3 times (and continue to do the "raise" motion) for it to start working again.

Just to repeat for clarification - I'm not talking about Raise to Speak not activating properly - it activates reliably and transcribes exactly what I'm saying - but then about 20% of the time the transcribed text just disappears off the watch screen and nothing happens (instead of the expected "Ok, done!" etc. that Siri says as the reminder is created), as if I've pressed the digital crown to cancel it or something.

 

[usagora]

Just an update. I've now made a habit of saying "Hey" at the start of each raise-to-speak request and that seems to work much more consistently. So instead of raising my wrist and saying "set a timer for 10 minutes" I'd say "hey set a timer for 10 minutes". For some reason that little extra word (it could be any word as long as it's not a key word/command) helps Siri to "lock in" the request consistently, even though it shouldn't be required.

 

[Itinj24]

I haven’t experienced this but at the very least, have you tried a hard reboot of the Watch? That will clear up some issues. For example, past week if I got a notification on my watch and raised my wrist, it wouldn’t open the notification. Hard reboot corrected that. (Press and hold both crown and side button till you see the Apple logo, then release).

 

[usagora]

I haven’t experienced this but at the very least, have you tried a hard reboot of the Watch? That will clear up some issues. For example, past week if I got a notification on my watch and raised my wrist, it wouldn’t open the notification. Hard reboot corrected that. (Press and hold both crown and side button till you see the Apple logo, then release).

See my workaround solution in post #5 that I just posted a few minutes ago. But, no, I had rebooted the Watch and in fact even unpaired and repaired it at one point (though not because of this issue) and it made no difference. 20% of the time it would still "hear" my request (indicated by the on-screen transcription) but then just disappear as if I had pressed the digital crown to cancel it or something. So far (a few days) with my new method of adding a filler word at the beginning, my success rate has been 100%.

 

[Itinj24]

See my workaround solution in post #5 that I just posted a few minutes ago. But, no, I had rebooted the Watch and in fact even unpaired and repaired it at one point (though not because of this issue) and it made no difference. 20% of the time it would still "hear" my request (indicated by the on-screen transcription) but then just disappear as if I had pressed the digital crown to cancel it or something. So far (a few days) with my new method of adding a filler word at the beginning, my success rate has been 100%.

Yes I saw your workaround but you ended it with, “even though it shouldn’t be required.” Thought you were still looking for a solution rather than a work around. I also didn’t realize this thread originated back in May. Apologies.

 

[usagora]

Yes I saw your workaround but you ended it with, “even though it shouldn’t be required.” Thought you were still looking for a solution rather than a work around. I also didn’t realize this thread originated back in May. Apologies.

No, I resurrected my own thread, so your comments are welcome! The workaround is so simple, I can live with it. It's just a mystery why it fails about 20% of the time without it, especially since I can see my full sentence on the screen, so I know it heard me. It just decides to randomly cancel my request that 20% of the time (if I don't use a filler word at the beginning).

 

[Itinj24]

No, I resurrected my own thread, so your comments are welcome! The workaround is so simple, I can live with it. It's just a mystery why it fails about 20% of the time without it, especially since I can see my full sentence on the screen, so I know it heard me. It just decides to randomly cancel my request that 20% of the time (if I don't use a filler word at the beginning).

I think it’s even more of a mystery that prefacing the query with only “hey” makes it work 100% of the time lol.