• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Speech-to-text intermittently not working

With no particular reason, my speech-to-text intermittently stops working.

I use it to text (Handcent), fill in search fields in my browser, and find destinations within Navigator.

Seems like less than half the time I get "Please try again when you are connected to the network."

Well....when it happened tonight on the drive home (30 minutes of trying) I had full bars of 4G so not sure what other network it wants.

At home on my wifi it works some of the time.

I have rebooted during these episodes and that doesn't help. Then...all of a sudden...it works.

Any thoughts?


Will
 
Will... I have had my Note II for a week and am having the same issue as you have described.. I have really only tried it with texting, but the same thing happens to me: Voice to text works fine.. and then I randomly get that same message about "not being connected to the network" (even though I have 4 bars of 4G) and it is totally useless. I am not sure it how long it is "out of commission"... I just give up and then it may work in the next minute or later int the day.
I called Samsung tonight as any phone I have absolutely must have reliable voice to text ( if it doesn't work, its a deal-breaker and the phone is going back). The person I spoke with was totally less than helpful, said there was no known issue, and told me multiple times that if I wasn't connected to the network it wouldn't work!!

What network???

Is anybody else out there having this problem?
 
Upvote 0
Ah gotcha. I just did a dozen tests and here's the deal. You CAN have BT on and it works just fine, you just can't be connected to a BT device.

I run BT 24/7 and most of the time when I try to use TTS I'm in my car, connected via BT to my radio and no go. I get home, and it works again.

Sitting at my desk at work..BT on but not connected...it works great. I fire up my BT headset and once connected...TTS no longer works.

So...BT on is fine as long as you aren't connected to a BT device.

Thanks for the help : -)
 
Upvote 0
Thanks donas.. I did not have any clue about the Bluetooth issue..and turning it off indeed did fix the problem! ( should I be surprised that the Samsung tech person didnt think to mention this?)

And unlike Renthorin, simply not being connected to a device makes it better but doesnt cure it. Now deciding if I can live without (Ford) Sync :(

Anyway now if I have a question, I'll know to come here first!

Thanks guys...
 
Upvote 0
Interestingly enough...I can make TTS work WHILE connected to a BT device. There is a similar thread/problem on PowerAmp's site in a thread that I'm part of too.

When a call comes in, my music pauses as it should (settings) but when the call ends..the music never starts back up. The minute/sec marker for the song resumes but no sound. All I have to do is hit the volume up/down and I get my sound back.

Same thing for me with this problem. When I hit the microphone button in SYWPE keyboard while connected to a BT device...I get nothing. It's like the microphone isn't listening.

While it is NOT listening, hit your vol up/down and suddenly the microphone is listening and TTS now works : - )

I can now use my TTS with any BT device.


Will
 
  • Like
Reactions: ijhutch
Upvote 0
the op problem relates to how data connections work. even when ir phones been on network all day, you haft to send a request ping wate on a reply, then data can run. and before thats done u get the error. i het if u use svoice and make a call to a contact itll say network error, then try again right after and it works.

is this the case?
 
Upvote 0
Here we go...bluetooth causes an interference with Voice commands, notably on Google Voice, speech-to-text (like text messaging), or S-Voice. This is clearly a bug.

My setup: T-Mobile Samsung Galaxy Note 2 running Android 4.1.1 (JellyBean), Bluetooth headset RF-MAB2 (supports HSP, HFP, A2DP, AVRCR, and Bluetooth 2.1)

There are two known workarounds for these bugs:

1. Hit the volume up or down button (only one click needed) on the phone (not from the bluetooth headset). Yes, it should be totally un-necessary, but it does work--magically, the microphone will pulse again with life and the Note 2 will take input from your bluetooth. This works for Speech-to-Text, Google Voice, and S-Voice. Kudos to Renthorin in this thread.

2. Activate Touch Sounds (Settings->Device->Sound->System->Touch sounds). This adds a(n annoying) "beep" when making any selection on a screen. This only works for Google Voice (headset fully enabled). For me, it does not fix the other two issues. Credit to topshelf95 in this thread

Please visit: https://code.google.com/p/android/issues/detail?id=35737, register, and STAR the issue. It is currently about 140th on the list of most squawked items (234 stars). If we can get more people to star it, it will move up the ranks and hopefully get fixed sooner than later.

HTH.

* ijhutch *
Original thread of mine that went unanswered with lots of screenshots
 
Upvote 0
Here we go...bluetooth causes an interference with Voice commands, notably on Google Voice, speech-to-text (like text messaging), or S-Voice. This is clearly a bug.

My setup: T-Mobile Samsung Galaxy Note 2 running Android 4.1.1 (JellyBean), Bluetooth headset RF-MAB2 (supports HSP, HFP, A2DP, AVRCR, and Bluetooth 2.1)

There are two known workarounds for these bugs:

1. Hit the volume up or down button (only one click needed) on the phone (not from the bluetooth headset). Yes, it should be totally un-necessary, but it does work--magically, the microphone will pulse again with life and the Note 2 will take input from your bluetooth. This works for Speech-to-Text, Google Voice, and S-Voice. Kudos to Renthorin in this thread.

2. Activate Touch Sounds (Settings->Device->Sound->System->Touch sounds). This adds a(n annoying) "beep" when making any selection on a screen. This only works for Google Voice (headset fully enabled). For me, it does not fix the other two issues. Credit to topshelf95 in this thread

Please visit: https://code.google.com/p/android/issues/detail?id=35737, register, and STAR the issue. It is currently about 140th on the list of most squawked items (234 stars). If we can get more people to star it, it will move up the ranks and hopefully get fixed sooner than later.

HTH.

* ijhutch *
Original thread of mine that went unanswered with lots of screenshots

Thanks, Stared.
 
Upvote 0
It is a known issue that if the Bluetooth is turned on this will happen 100% of the time.....do you two possibly have it turned on? I have found that even if my phone isn't connected to any bluetooth items, as long as it is turned on I get the same problem.

Incorect
I use bluetooth 100% of the time
And this happens alot but not always
Ill get network error cuz of the way gsm connects
Sorry its just the nature of the beast

Ill get the svoice app not loading sometimes but thats probably due to the rom. [Click the button and it beeps I talk, nothing, not network error, do it again, it works]

Neither happen 100% of the time. Even together or one pr the other meaning about half the time it works perfect.

Ive used both tmobile and att and im on jedix11 but have had solid working time thru jedix
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones