Anyone else having a problem with voice commands and google?Support

Last Updated:

  1. Serpentine

    Serpentine Well-Known Member

    This just started happening this week, and it's getting worse. I've noticed when using voice commands using Google, that the "speak" prompt does not initialize properly. I tap the microphone icon on the screen and Google prompt to speak just hangs there doing nothing.

    I'm on Verizon. Trying figure out if it's a phone setting, a carrier problem, or a Google problem before I get riveted to resolving this on my own and waste three days if you know what I mean?

  2. FitchVA

    FitchVA Well-Known Member

    I think it's just SVoice sucking. I'm coming from a GNexus and loved the stock voice recognition. It was amazingly accurate. I used to use a lot of voice dialing while using my bluetooth headset while driving. My old phone, with stock voice rec, never had an issue calling my girlfriend (with an Asian name). Svoice cannot get it right to save it's life. I'm going to start looking for a way to revert it back to the Google voice recognition. I saw a few threads in the SIII section that showed how it can be done. I'm hoping it'll work for the Note2
  3. Serpentine

    Serpentine Well-Known Member

    Is it S-Voice then? S-Voice seems to be adapting to me on making calls and leaving S-Note memos. But on other applications, where the keyboard comes up in a separate window and a Google microphone icon is pressed the resulting screen below just hangs in an initialization loop.
  4. FitchVA

    FitchVA Well-Known Member

    ah, yeah, that sounds like a different issue. when using anything svoice - it cannot understand me (i only have a slight southern draw). but the google voice recognition for speech to text when using the microphone on the keyboard, works AOK for me.

Share This Page