Develop Bugs

Voice to text issue with 2.3 Gingerbread.

Well, I was having the notorious "voice to text" issue with gingerbread. Not the Google Search issue. That was resolved by uninstalling then reinstalling the app.
I just flashed this mod from the MikMik.com forum. The " Stock_v2.3_HTC_IME_Revert-signed.zip". It instantly fixed the issue and haven't had any problems since. Both on my phone and my wife's.
Just thought I would share this for those of you that have had the same problems as me.
Sent from my HTC EVO 4G/MikG(v2.3) using XDA Premium App

Thank you
Great...thank you.....going to try right now....most annoying thing with my phone recently

OK...spent the last hour over at MikMik and could not find file...Stock_v2.3_HTC_IME_Revert-signed.zip
could post link...

1. Boot into recovery.
2. Wiped cache & dalvik/cache.
3. Flashed zip from sdcard.
Put www in front of the link.
mediafire.com/?he1b1x63tyq6xd2

Thanks for the prompt response.....let me ask you...I've read that checking "Personalized Recongnition" in voice input settings will help or fix....have you tried that before...or know....???

I tried everything I could think of. As mentioned in the OP, the voice to text was an independent issue from the Google Search issue. So none of the Google Search solutions work for this problem.
I even unistalled then re-installed the voice search.apk. I noticed that the only time it didn't work was when I was using the keyboard then pressed the voice button. That is what gave me the idea of using a keyboard mod.
Sent from my HTC EVO 4G/Kinged Kingdom RLS2 using XDA Premium App

psyv01 said:
I tried everything I could think of. As mentioned in the OP, the voice to text was an independent issue from the Google Search issue. So none of the Google Search solutions work for this problem.
I even unistalled then re-installed the voice search.apk. I noticed that the only time it didn't work was when I was using the keyboard then pressed the voice button. That is what gave me the idea of using a keyboard mod.
Sent from my HTC EVO 4G/Kinged Kingdom RLS2 using XDA Premium App
Click to expand...
Click to collapse
Thanks again for the response, advice and tips....I did download and flash the mod....and sorry to say no real difference...other than my only keyboard choice now is the sywipe....which is OK...it works perfectly at home, office and modest sound, but did not work today in the car....not at all...did work when I stopped, like at a light....my main use of the voice to text was "texting or emailing while driving"...ha-ha....apparently I shouldn't do that anyway.....I suppose a "real" fix like a modified mod will come along...by the way I have a Sprint EVO that's rooted with the latest Fresh Rom...hardware version 0003...

psyv01 said:
I tried everything I could think of. As mentioned in the OP, the voice to text was an independent issue from the Google Search issue. So none of the Google Search solutions work for this problem.
I even unistalled then re-installed the voice search.apk. I noticed that the only time it didn't work was when I was using the keyboard then pressed the voice button. That is what gave me the idea of using a keyboard mod.
Sent from my HTC EVO 4G/Kinged Kingdom RLS2 using XDA Premium App
Click to expand...
Click to collapse
I may point out....to give light on this....muted mic background noise theory......I have a blueAnt bluetooth headset with "noise cancellation high" as an option.....in the car, the voice to text works OK with my blueant on....meaning...the"mic" doesn't hear the background noise....the new fancy bluetooth ear pieces work pretty good...

Problems with voice dialing on Jelly Bean

I am experiencing problem voice dialing from bluetooth headset on jellybean roms on the vzw gNexus.
On any non jellybean rom i can say... for example... "call mom on mobile" and it will, 95% of the time call mom. On jelly bean if i say the same phrase, it will 100% of the time return "calling tim, on mobile". In fact, it doesn't mater what contact name i say, it it ALWAYS suggests the wrong contact.
I thought, ok, lets try google now. If i open google not, tap the mic(voice input) option, and say, "call mom on mobile" it will fill in the search box with "call mom on mobile" so its understanding me correctly, then below that is says
"did you mean call tim on mobile"
and lists tim then mom in a list of numbers to call.
I spent over 3 hours trying to get this to work right, flashed every JB rom i could find, wiped and rewiped and reflashed. Finally went back to ICS and retested, sure enough it works awesome on ICS.
Can anyone atleast try to replicate this problem, or is anyone already experiencing it?
THanks!

Bump

Bump again.
Almost 50 views, if anyone using a bluetooth and Jellybean can at least try it and let me know if it happens to you or not. Thanks

Works fine for me.
Sent from my Galaxy Nexus using xda premium

greyphil said:
Works fine for me.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
what phone and rom are you using? Looks like GSM, and OTA.
I just checked it again and i got:
"Call mom on mobile"
**Did you mean -Mark**
Mark
Mom
Kathy
thats from google now.
If it activate the voice dialer directly from the bluetooth, it will call bob, mark, tim, or funniest a business name that starts with "borderview". Even after 20 tries it will not dial "mom" lol.
Alternatively, I tried dialing mark, tim, bob, and borderview directly, and after 10 tries each, they will not dial if i try to dial them, only if i try and dial mom. lol very frustrating.

Yes stock gsm JB with root. Does it only happen with your headset? If so, try a different BT headset.
Sent from my Galaxy Nexus using xda premium

It happens using a $150 bose headset, as well as a $20 plantronics.
If it don't use the bluetooth i still get terrible suggestions, such as..
"call mom on mobile"
Did you mean call tim?
Tim
Mom
Mark
wtf???

That's weird. Only thing I'd try now is flashing a different JB rom, but I can't really imagine that being the problem. Have you let someone else try it? Maybe it is you after all.

In have tried 3 different roms, and have been using the voice dialer since android 2.1 on over 10 devices. Also it works flawlessly on ISC using the same hardware. Is anyone able to successfully Bluetooth voice dial on jelly bean on a vzw gnexus?
Sent from my Galaxy Nexus using xda app-developers app

I just flashed my Sprint Nexus to JB last night and have exactly the same problem. I hadn't tried any calling on ICS before I flashed, so I can't compare on the same phone.
I just came from an Epic 4G Touch that used Vlingo, and it was always about 95% accurate. I hate to step backwards, but I may have to switch back to that.
Why can't anyone mimic the old MS voice dial where it asked for confirmation before dialing? If I said, "Call mom on mobile", it would ask, "Call mom on mobile?" I said "Yes" and it would dial.
The way it is now goes against all safety concerns for hands-free driving. Now I have to look at the screen as it starts to dial and madly grab at the End Call button when it guesses the wrong name to call.

JimSmith94 said:
I just flashed my Sprint Nexus to JB last night and have exactly the same problem. I hadn't tried any calling on ICS before I flashed, so I can't compare on the same phone.
I just came from an Epic 4G Touch that used Vlingo, and it was always about 95% accurate. I hate to step backwards, but I may have to switch back to that.
Why can't anyone mimic the old MS voice dial where it asked for confirmation before dialing? If I said, "Call mom on mobile", it would ask, "Call mom on mobile?" I said "Yes" and it would dial.
The way it is now goes against all safety concerns for hands-free driving. Now I have to look at the screen as it starts to dial and madly grab at the End Call button when it guesses the wrong name to call.
Click to expand...
Click to collapse
Im glad someone finally responded and said yes i have this problem, or no i use this feature and it works every time.
THis is a huge concern and i feel its only happening on the ported(CDMA) roms.
Can anyone else confirm this on a toro or toroplus, and confirm that this is not an issue on GSM gnexus's?
Thanks!

urushiol said:
Can anyone else confirm this on a toro or toroplus, and confirm that this is not an issue on GSM gnexus's?
Click to expand...
Click to collapse
Fully stock 4.1 GSM Galaxy Nexus, no issues with voice-dialing any name.

UnknownFearNG said:
Fully stock 4.1 GSM Galaxy Nexus, no issues with voice-dialing any name.
Click to expand...
Click to collapse
This makes me feel very strongly that the issue has been caused by something in the porting process. I will PM on of the devs. and see if he can reproduce it.

i am also having this problem on my CDMA nexus with JB. Everytime it's not even remotely close to properly detecting my call request.

I absolutely love the cyberon voice dialer because it works and it has verification.
Unfortunately, under JB when you press the dial button on the bluetooth headset the google now voice dialer overrides my cyberon voice dialer. The only way to make cyberon work is to completely disable google search. This completely disables all the new voice command support and google now as well.
Basically 3rd party voice dialers are no longer compatible!
No, the built in dialer is still unusable especially without verification.

For me, I've always had absolutely horrible results when using voice dial initiated from the Bluetooth earpiece (two different Jawbone Icons, three different Android phones, Eclair through Jelly Bean, official or custom ROM.)
Using voice search, Google Now, JB voice typing, or Dragon with Swype, it's perfect..
Sent from my Galaxy Nexus using xda premium

Can the long button press be changed from voice dial to voice search? (I think those are the right terms.) Voice search understands and dials much better. Plus, it sucks to be limited to just dialing from the headset.

kynolin said:
For me, I've always had absolutely horrible results when using voice dial initiated from the Bluetooth earpiece (two different Jawbone Icons, three different Android phones, Eclair through Jelly Bean, official or custom ROM.)
Using voice search, Google Now, JB voice typing, or Dragon with Swype, it's perfect..
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Cyberon is awesome. I wouldn't use a voice dialer without confirmation. I don't want people calling me back because my dialer got it wrong. Sometimes this can cause serious problems. If google adds a confirmation option that's when I'll give them a serious try. I've been told even the iphone voice dialer has confirmation.

UnknownFearNG said:
Fully stock 4.1 GSM Galaxy Nexus, no issues with voice-dialing any name.
Click to expand...
Click to collapse
Same.

martonikaj said:
Same.
Click to expand...
Click to collapse
Are you both dialing through bluetooth? Honestly it hasn't got one right for me yet. Not one where cyberon is dead on.

[Q] Rogers S3 stock JB replace voice dialer with google now

Upgraded my rogers s3 to latest stock JB last night. however today when I tried bluetooth headset dialing (Sony MW600) I was surprised to hear S Voice as i thought it was completely replaced by Google now, but it was still there. Fixed that issue by disabling S Voice under Settings-->Applications
Now when I price dial button on headset, it launches Voice Dialer, however I was expecting it to launch Google Now which includes voice dialing and other functions. Not able to figure out how to do that.
So far I tried clearing defaults and data for Google search app (as suggested in some threads) but no other solutions specified worked for me.
Anybody successful in changing this behavior without rooting?

Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

I'm not currently getting the proper screen either all I get is the search box I was expecting it to look like the Note 2 app as I want the travel time indicator.
Sent from my SGH-I747M using xda app-developers app

127kmph said:
Upgraded my rogers s3 to latest stock JB last night. however today when I tried bluetooth headset dialing (Sony MW600) I was surprised to hear S Voice as i thought it was completely replaced by Google now, but it was still there. Fixed that issue by disabling S Voice under Settings-->Applications
Now when I price dial button on headset, it launches Voice Dialer, however I was expecting it to launch Google Now which includes voice dialing and other functions. Not able to figure out how to do that.
So far I tried clearing defaults and data for Google search app (as suggested in some threads) but no other solutions specified worked for me.
Anybody successful in changing this behavior without rooting?
Click to expand...
Click to collapse
I have root and just froze s voice. That fixed it for me. Is it possible to just disable that app with stock?
Sent from my S3

sirooga said:
I have root and just froze s voice. That fixed it for me. Is it possible to just disable that app with stock?
Sent from my S3
Click to expand...
Click to collapse
I did disable s voice but thats what caused "Voice Dialer" to come up for headset call button press, however I want it to launch Google Now.

[Q] Google Voice Speech to Text often unavailable since JB update

Ever since the Jelly Bean update the Google Voice function has been intermittently unavailable. If I keep canceling it out and opening it back up eventually it works. I did a factory reset and it didn't help. No one has posted about the issue so I wondered am I the only one? And is there a fix for it? Thanks, Jeff.
Note: Sometimes if I wait long enough the error that pops up says server unavailable.
App is called "Voice Search" by Google Inc and is version 2.1.4

You need to download "google search" that is google now. Both should be downloaded and in tts settings should be set to whatever you use. I use ivona because it sounds much better like a real voice.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

Also every portion of the phone needs to be set to US english... the google now settings, tts settings, and the keyboard i believe....

It's not either of those. It's installed already and set up correctly. I even have english downloaded for offline use. I forgot to mention I'm all stock touchwiz never rooted, so there's no excuse for this issue. I don't know if the JellyBean data Keis put on my phone was corrupted somehow, or if everyone else has this issue but found a solution. That said does anyone have this problem or just me?

jeffdaman said:
It's not either of those. It's installed already and set up correctly. I even have english downloaded for offline use.
Click to expand...
Click to collapse
Well not everything gets spoken, but try to duplicate the issue again.... Ask it the same question over and over... ask it what time is it, it always reads that... then ask it who is the president of the united states, or what is the date.... all of those get read back... see if stumbles, and report back, and also report have u tried any resets or anything... stock jb?

I think I figured it out. My Smart Keyboard wants to use the voice and so did Google Voice Typing, so I unchecked the one I don't use and for the last minute I've had no issue. It will be a few days before I can be sure but I usually have this problem pretty frequently.
View attachment 1582431

jeffdaman said:
I think I figured it out. My Smart Keyboard wants to use the voice and so did Google Voice Typing, so I unchecked the one I don't use and for the last minute I've had no issue. It will be a few days before I can be sure but I usually have this problem pretty frequently.
View attachment 1582431
Click to expand...
Click to collapse
Say, "Google, do a barrel roll"

Quasimodem said:
Say, "Google, do a barrel roll"
Click to expand...
Click to collapse
It's just "do a barrel roll." Unless saying google is supposed to open search for me.

jeffdaman said:
It's just "do a barrel roll." Unless saying google is supposed to open search for me.
Click to expand...
Click to collapse
Saying google while in google now makes it listen...

I was wrong about figuring this out by un-checking one of the voice keyboards in the keyboard menu. That solution worked out of coincidence.
I found that I could fix it every time I restarted; then I found I could go into airplane mode and back out to fix it; then I tried all the things airplane mode affected and found that I could turn off Bluetooth and it would work, and when I turned on Bluetooth it would stop working. I found this while sitting in my car which connects my Bluetooth to the radio and a microphone above my head. I will try to narrow the problem down further to see if any other Bluetooth situations cause the issue, and I will report back.

I've the the problem with bluetooth as well, but I literally just started experiencing the issue without bluetooth enabled about 5 minutes ago. No matter what I do Google can't connect to the server.

goodtimes50 said:
I've the the problem with bluetooth as well, but I literally just started experiencing the issue without bluetooth enabled about 5 minutes ago. No matter what I do Google can't connect to the server.
Click to expand...
Click to collapse
Ugh don't tell me that, I've even finally rooted this thing and tried roms but they still had the issue. Now the only other solution is to set in on fire and push it down a hill....That's how we had to deal with Yeller as well

jeffdaman said:
Ugh don't tell me that, I've even finally rooted this thing and tried roms but they still had the issue. Now the only other solution is to set in on fire and push it down a hill....That's how we had to deal with Yeller as well
Click to expand...
Click to collapse
Turns out it's something with my router's configuration. When I disabled wifi on the phone it started working. Anyone have any ideas what router settings might interfere with Google's voice recognition?
---------- Post added at 05:13 PM ---------- Previous post was at 05:05 PM ----------
Okay, after some Googling I setup port forwarding for port 19294 and now it's working. Not sure why this new router is blocking that port as none of the others I've used ever have...

I am experiencing this issue as well. At home on wifi, google voice comes on right away and listens. On the road (in the car and with bluetooth on) it keeps saying initializing. Today I will try voice recognition in the car with bluetooth turned off and will report back.

[Q] Voice apps other than S-Voice not working over bluetooth

I have been searching everywhere and have not found a solution to this, so I apologize if I missed it somewhere. As I've learned and have read from others, S-Voice is crap! Google Now is much MUCH better at voice recognition, particularly with names. The problem is, over bluetooth, my voice commands are only picked up by S-Voice. Google Now gets stuck at the "Initializing" then says "Didn't catch that" and closes. I've gotten it to intermittently work with Utter!, but I can't rely on that. Google Now works great over headphones or from the phone itself. It's just over Bluetooth when it doesn't work. After researching I'm almost convinced Samsung (or Vlingo) set it up that way; it's as if the mic is disabled with any app other than S-Voice. My question is, has anyone figured out how to get Google Now, or any other voice app for that matter, to be recognized over bluetooth?
I'm running stock JB with root (fyi, this was going on before I rooted). I know it'll probably work just fine if I flashed CM10, but I actually like the setup I have.
Edit: After looking more, I found this thread. I tested out turning off the "Media Audio" and Google Now works, but in further investigating when I click the button on my bluetooth, it's the voice dialer that pops up and that is what doesn't work, not Google Now. I can't see, to figure out how to get Google Now to show up and not voice dialer.
Edit 2: I forgot to mention I'm using a Motorola Roadster bluetooth speaker, but I don't think that's the problem.

Same issue here. Exists on every rom I try. Bluetooth in general is buggy as heel on the S3. It's really disappointing. I don't see many answers here on XDA...

Same here and I am on a new s2 ROM sbean v12 any fix would be great
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

Try going into google voice search and downloading the language you want to use
Sent from my SAMSUNG-SGH-T989 using xda app-developers app