Orin your mind (like I've done for some weeks now), while the Siri tone is playing, think a phrase like "Hey Siri"; coinciding when the tone ends, you've done thinking the phrase. This has definitely gotten awesome results!
Gera Enviado desde mi iPhone SE (2nd Generation) de Telcel > El 28 dic 2022, a la(s) 1:38 a.m., M. Taylor <mk...@ucla.edu> escribió: > > Hello All, > > For the first 48 hours or so after activating my new 14, I thought the > device might be defective as almost 90% of my Siri requests were not being > understood by the phone. > > For example, when making requests such as, "Call Richard" or "Call Sieghard, > mobile", Siri would respond with something like, "Could you say that again? > I didn't quite understand you." > > Even when I asked Siri for the current weather conditions in a particular > city, I would receive an error response. This even happened when I had my > Apple Earpods, attached. Now that I think about it, I couldn't even get > Siri to open the Calendar app. > > Now keep in mind that it wasn't until I purchased the 14 that I had any > experience with OS 16, let alone OS 16.2. > > I was so tired during that first 48-hour period, after purchasing iPhone 14, > because of a lack of sleep, that I blamed myself for doing something wrong > even though I could not pinpoint my error. > > Of course I searched Google for solutions but could not find any articles on > the subject. This led me to believe that the issue was not widespread, at > the very least. > > I was just beginning to consider taking the new phone back to the Apple > Store when, near the end of that first 48-hour period, I decided to upgrade > my beloved iPad Pro 2017 from iPad OS 15.x to iPad 16.2. Immediately after > doing so, I experienced the exact same phenomenon on the iPad. > > To say that my mind was blown, would be the understatement of the holiday > season. > > After experiencing the same glitch on two devices, one new and the other > that, until the update to the latest OS, had performed flawlessly, I > realized that the issue was with 16.2 and not a hardware problem. > > So I asked myself what had changed between OS 15.x and OS 16.x. The answer, > which I had read about in this community, was the Siri beep prompt. > > As many had reported and discussed, on-list, Apple, in its infinite wisdom, > changed the beep prompt that VoiceOver users hear, when activating Siri. > > Now I do my best to read virtually every thread posted to this list. This > can be an overwhelming task, at times, so, sometimes I simply miss the > proverbial "meat & potatoes" of a thread. I write this to say that what I > discovered, organically, has most likely already been described, on-list. So > I apologize if this is redundant. > > Okay, what occurred to me was that the most significant difference between > the legacy Siri beep prompt and the new Siri beep prompt was the length of > time it takes the new prompt to end. The difference is less than one second > but it is a significant difference, all the same. > > So I asked myself, what would happen if, instead of speaking to Siri near > the beginning of the prompt, as I have always done, I waited until the > prompt completely ended. > > So, I tried it and . Yes, you guessed it; that is all it took in order to > bring Siri recognition back to virtually 100% on both devices. > > After that, I realized that I have been, to a much lesser degree > experiencing the same problem on both of my Apple TV models. These models, > also, use the new Siri beep prompt. Waiting just that extra little moment, > before speaking to Siri made a universe full of difference. > > So, if you are finding that Siri is not as accurate in its responses as it > was in previous versions of the OS, after activating Siri, wait until the > new beep prompt has completely ended, before speaking, and you should notice > quite a difference in the results. > > When using Siri with VoiceOver, remember to give that beep a chance, to end, > that is, (smile), before speaking. > > Mark > > > -- > The following information is important for all members of the V iPhone list. > > If you have any questions or concerns about the running of this list, or if > you feel that a member's post is inappropriate, please contact the owners or > moderators directly rather than posting on the list itself. > > Your V iPhone list moderator is Mark Taylor. Mark can be reached at: > mk...@ucla.edu. Your list owner is Cara Quinn - you can reach Cara at > caraqu...@caraquinn.com > > The archives for this list can be searched at: > http://www.mail-archive.com/viphone@googlegroups.com/ > --- > You received this message because you are subscribed to the Google Groups > "VIPhone" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to viphone+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/viphone/005501d91a8f%2448952640%24d9bf72c0%24%40ucla.edu. -- The following information is important for all members of the V iPhone list. If you have any questions or concerns about the running of this list, or if you feel that a member's post is inappropriate, please contact the owners or moderators directly rather than posting on the list itself. Your V iPhone list moderator is Mark Taylor. Mark can be reached at: mk...@ucla.edu. Your list owner is Cara Quinn - you can reach Cara at caraqu...@caraquinn.com The archives for this list can be searched at: http://www.mail-archive.com/viphone@googlegroups.com/ --- You received this message because you are subscribed to the Google Groups "VIPhone" group. To unsubscribe from this group and stop receiving emails from it, send an email to viphone+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/viphone/11C1F30F-FBB7-4AAB-8B0F-990E7CEEF929%40gmail.com.
