Related
I just finished installing all the stereo parts in my car only to find out that my Captivate won't work with the voice dialing of the stereo. I guess it's the phone's fault as my wife's Focus works just fine as did my old HTC Pure. She won't trade phones with me so I'm stuck trying to find a ROM that has this.
With Samsung stating it will be fixed (added) in 2.2.1; does that mean only the 2.2.1 ROMS will have this feature? I'm currently running Cognition 4.3.1 and it does not have it; but would like to only try new ROMS that have it. What ROMS do have the feature?
Thank you for your input.
Firefly supports voice dialing. You have to start the Voice Dialling app and then say the command.
What I'm looking for is what the Droid Incredible has. I paired it to my stereo and when I hit the call button on the stereo; it launched what appeared to be a bluetooth voice dialer application that allowed me to speak into the stereo.
I just tried firefly and it did have that app, but it crashed as soon as I tried it. It also crashed the music app, failed to mount the storage drives, crashed when trying to put it in debugging mode and pretty much was unstable since it booted. I then tried to use one click odin and it went to a blue screen half way through the process. It'll be a fun night.
Probably not what you want to hear, but my BT in the car works great on my 'stock' set up. I think it has more to do with the kernel/ modem configuration than the ROM though.
dragon has this. many people are pairing it with choice dialer.
Dani897 said:
dragon has this. many people are pairing it with choice dialer.
Click to expand...
Click to collapse
I can't get Choice Dialer to work well at all. ONe example: "CAll Tom Jones", it says "CAll Tom Jones?", I say "Yes", it says "Try again". Argh...
ANd most of th time it just doesn't understand me at all.
I believe this is the apk you need. I know cog doesn't come with it. This is an old one so I don't know if there is a newer version available but when you pair your bluetooth and hit the voice command on your stereo or bluetooth set, make this the default app when the prompt shows up. It won't give you a voice prompt but if you wait 2 secs and then speak it should dial for you. Only problem is that your phone has to be awake but at least you can use voice commands from your bluetooth set. Just leave your phone plugged in and awake while your in the car. This is the only option I have found.
That worked.
Thank you for the apk. That works.
ewingr said:
I can't get Choice Dialer to work well at all. ONe example: "CAll Tom Jones", it says "CAll Tom Jones?", I say "Yes", it says "Try again". Argh...
ANd most of th time it just doesn't understand me at all.
Click to expand...
Click to collapse
It's not unusual to be called by anyone
It's not unusual to have a text from anyone
but when I try to use voice dial for anyone
It's not unusual to see me cry
Roflmfao!
studacris said:
It's not unusual to be called by anyone
It's not unusual to have a text from anyone
but when I try to use voice dial for anyone
It's not unusual to see me cry
Roflmfao!
Click to expand...
Click to collapse
Boy, ain't that the truth. It really chaps me that the one thing that should be solid on a Cell now-a-days is voice dial. Can't believe that OLD OLD technology from Microsoft on Winmo SHINES so much better than Android. Maybe that's the only thing that does, but in my opinion, one of the most important things for a cell phone...at least if you anticipate wanting to use it while driving.
That was a tom jones joke ...
I'm glad the Voice Dialer apk worked. I couldn't get it to work on any Captivate ROMs. Most reoriented i9000 ROMs have a working version, but I find all of the i9000 ROMs to be severely lacking in performance compared to KB1 ROMs.
My preferred solution in either case is to use Bluetooth Launch and Voice Search. Bluetooth Launch can be found here. Run it from the app drawer, it brings up a full list of installed apps and available activities. Choose Voice Search, and then the "VoiceRecognition" activity (must have Google's Voice Search installed first of course). Then, hit your call button, and set Bluetooth Launch as the default activity when it asks. From then on, your call button will launch Voice Actions, which support not only "call <contact>" but also a ton of other commands, including controlling music, text msgs, etc. I love sending texts without touching my phone, and it works flawlessly for me so far.
Using the stock voice dialer in my Inspire.
On the occasions that it misunderstand me and if asks me if I want to dial the wrong person, I say no -- yet it still dials the wrong person anyway.
I've tried "no", "NO!", "cancel", "stop", "kiss my butt", and a host of other things not acceptable in this forum. Seriously, though, the voice dialer misunderstands me about 25% of the time, so I get plenty of opportunity to say no. iI've tried saying no immediately and I've tried a delay of half-a-second to 2 seconds or so.
Is there something I'm missing?
Did you root your phone and are you running any ROMs?
It did it on the stock ROM before I rooted, and does it after rooting with the modified stock rom (Ace_Cingular_US_SL_1.84.502.11_Radio_26_06_06_30_M_PD98IMG.zip).
Try it in Japanese
Not sure whats wrong, possibly hardware failure?
I would try a voice dialer off the market and see if it works and if it doesn't you know it a hardware failure.
Try using TopVoiceControl or Vlingo.
A hardware issue that causes the voice dialer to recognize everything I say except for "no"?
Pretty unlikely. as it recognizes "call...", "dial...", "open..." with at least 75% accuracy. It just refuses to hear the "no" when confirming something.
Interesting one, and can't figure out why it's happening - so if anyone has any thoughts x)
Flashed L tonight, all went smoothly and generally everything is fine. The only weird thing is that Google Voice search has stopped working. I press the Voice search button, and it just doesn't pick up any sound. I trying saying "ok google", and it doesn't pick that up either. Also, along with that, Text to Speech refuses to work too, tried with different languages and different voice packs.
Any ideas?
I know I had to go into the Google Now settings and activate the "OK Google" from any screen, to get it to work.
I had the same problem when setting another language as the primary language, then switching back to English, but something seemed bugged.
Removing all the other languages and restoring English (US) only, and finally rebooting, resolved the issue. Hope this helps.
themcfly said:
I had the same problem when setting another language as the primary language, then switching back to English, but something seemed bugged.
Removing all the other languages and restoring English (US) only, and finally rebooting, resolved the issue. Hope this helps.
Click to expand...
Click to collapse
Hmm, just gave that a try, no dice Was it just the Voice language or the whole phone that you had to change?
The weird thing is, it's like it's not even connecting to the microphone, just sits there listening and not hearing anything x)
Yes, that was exactly the same behavior i had with mine. I also ended up trying to configure Ok Google from any screen, and the voice training feature didn't hear anything, remaining stuck on the 1st of 3 verifications.
Maybe you can try going to Settings > App > All > Google Search and deleting cache/data to restore it brand new.
themcfly said:
Yes, that was exactly the same behavior i had with mine. I also ended up trying to configure Ok Google from any screen, and the voice training feature didn't hear anything, remaining stuck on the 1st of 3 verifications.
Maybe you can try going to Settings > App > All > Google Search and deleting cache/data to restore it brand new.
Click to expand...
Click to collapse
Tried that, and reflashing it, factory reset etc. Turns out the problem is slightly wider than just that not working though - It's killed the Microphone completely, can't make voice calls, it's like it's just not picking up the mix exists for some reason :S
It takes time to activate, there is a backend update of google going on while you select your language, but eventually comes back on.
Try voice typing if your believe the mic is not doing any good for "ok google"
gamer.11 said:
It takes time to activate, there is a backend update of google going on while you select your language, but eventually comes back on.
Click to expand...
Click to collapse
Wouldn't really explain why my Microphone doesn't work at all, even in phone calls though
Reoryn said:
Wouldn't really explain why my Microphone doesn't work at all, even in phone calls though
Click to expand...
Click to collapse
just to try it out to rule out whether it's the telephony app or in effect a bug which affects 5.0 as a whole(which i highly doubt, because i have mine working like a charm) Hell mine even works on off-screen while charging.
gamer.11 said:
just to try it out to rule out whether it's the telephony app or in effect a bug which affects 5.0 as a whole(which i highly doubt, because i have mine working like a charm) Hell mine even works on off-screen while charging.
Click to expand...
Click to collapse
Ok, voice search nothing, voice typing nothing, Making Phone calls, nothing x) The only thing I haven't managed to try yet is downloading a 3rd party voice recorder app - but unfortunately I'm on GSM at work and for some reason, Lollipop is refusing to connect to the wifi as well. Good times
Might just flash it back to 4.4.4 and wait for the OTA upgrade to see if that does it better
Just as an additional - managed to download a voice recorder app.... Nothing either. So the whole OS isn't picking up the Microphone. Curiouser and curiouser
Oh hell.... I'm going to hang my head in shame now and hand in any tehcy credentials I may have once had.
I have a Pressy.... I forgot it was plugged in... I didn't install the app. Lollipop saw it as a headset and mic.
In conclusion: I'm an idiot. That is all x) Thank you for anyone who tried to help though.
I have the exact same problem but no pressy. Could it mean that there is a fault with the headphone jack?
Reoryn said:
Oh hell.... I'm going to hang my head in shame now and hand in any tehcy credentials I may have once had.
I have a Pressy.... I forgot it was plugged in... I didn't install the app. Lollipop saw it as a headset and mic.
In conclusion: I'm an idiot. That is all x) Thank you for anyone who tried to help though.
Click to expand...
Click to collapse
Lol
My mic is not working, i dont know what to do????? any help, just update to lollipop cuz receive the update message, but now i dont have mic. need help...
Anyone having issues with voice (system, US English)? In that it only works once or twice, then constantly fails with the error "voice input fail".
I can change language (to German for instance) it will work a few times, then stop... back to US English (works a few times...then, yep, stops....).....
Anyone else see this?
Thanks!
Edit/Update - - Try UK ?? English!
..
I have the same issue. Don't know what's wrong.
Seems to work now....
mcaspe1 said:
I have the same issue. Don't know what's wrong.
Click to expand...
Click to collapse
Yours working yet? I factory reset the watch after backing it up and did the whole set-up dance....no difference. Then, later in the day, it started working....haven't thoroughly tested it....but it seems be better....
..
I have an S2, but the underlying implementation is the same.
S-Voice uses a remote server for decoding and interpreting voice input. Occasionally Samsung's servers are unresponsive or failing in some other way. I've experienced this a few times over the last year I've had my S2.
So this may be what was going on, particularly since it started working again later. I didn't use S-voice yesterday, so I can't comment on any outages.
Finally, I will add that since the rollout of the recent update adding a bunch of S3 features to the S2 (reminders, etc.) and updating the entire Tizen OS, S-voice is working much better than it used to. Still doesn't hold a candle to Google's "okay google", but has crossed the threshold to being a useful, value-add feature now rather than a cruel tease. In my opinion, of course.
I had this problem with my S3. You might have hit a setting that you did not realize you hit. When you were able to enter speech and hit send, you had a choice to choose send as text or send as voice. Just below these two choices there is a small circle, if you accidentally touch that, it turns off the speech input and only uses the text. The only way I have found to get out of this mode is to open the main settings, scroll down to messages, select messages, you should see "send as audio". Click it so it is "on".
This should take you back to where it will let you dictate messages. Just be careful when selecting the send as text or audio option as that little circle will be below them and it is easy to touch accidentally.
I hope this helps
I have the same problem and it has not been corrected by resetting or the message sound option.
Same issue here
Well it seems to be at it again.
Interesting part is that using U.S. English, it does not work. If I switch it to U. K. English it does work. (I'm in the US..)
... C'mon Samsung, how about getting your current software working correctly before introducing any new buggy stuff.
Skeeter123,, I am having the same exact problem since I installed the new software update , very frustrating hopefully they will fix this issue soon ?
Yup.
Fix the old buggy software before you give us a new buggy stuff.
Ridiculous Update
I have had my watch for one week and it worked great and then the voice input just stopped. I called Samsung and they offered NO help other than for me to mail it back to them, REALLY! So, back to Best buy for an exchange. Well, same issue will another brand new $450 watch. Is the Gear S3 going to another Note 7 debacle? It is a Samsung product. Get your crap together Samsung! If anyone finds a fix, Pease post.
I'm having this problem
Indeed setting the language to English(Great Britain) actually works! Hats off the person who posted this earlier in the thread
tamerelnaggar said:
Indeed setting the language to English(Great Britain) actually works! Hats off the person who posted this earlier in the thread
Click to expand...
Click to collapse
You're welcome!
But now you have to speak that funny English that they speak over there.:silly:
While I never tried it till this morning, it did work. US.
Still not working for me. And UK English is not working very well either.
Are you in the US?
For all of my tests I am attempting to dictate a message.
I just switched mine over to the English (UK) and it appears to be working right now. I am in the good ole US of A, and have a pretty thick southern accent and it works, but we should not have to change it this way, but at least it works again.
Yup. I hear ya! Too bad Sammy doesn't. I'm going to check out some of the Android Wear 2.0 watches soon.....If I like one, then it's bye-bye Sammy. For good....sigh...
That's too bad that they will lose customers over their inability to get it right the first time. Crazy thing with voice input, I have to have it set to UK English to respond to text messages, or to send a text, but it has to be in US English to speak a reminder in?. Do you think Samsung even monitors this forum?
Chief19 said:
That's too bad that they will lose customers over their inability to get it right the first time. Crazy thing with voice input, I have to have it set to UK English to respond to text messages, or to send a text, but it has to be in US English to speak a reminder in
Click to expand...
Click to collapse
Hi all, I use a lot of voice dictation as input methods on my smartphones. The best one was the Pixel 7 Pro, but thi is another story. Now I have a Galaxy S23 and since May I've been facing a very strange issue with Gboard when "typing" text using my voice as an input.
First of all, I have to say what IS working fine
- Google voice "keyboard" as a standalone input method (which you can choose from the list of keyboards) works like a charm
- Also, If I set Google as default voice input method and use Samsung keyboard, things work fine: when I click on the microphone in the Samsung Keyboard, the system invokes the Google voice "keyboard" and everything works fine.
What is NOT working fine is Gboard and its embedded voice dictation. When I click on the mic, it starts listening but sometimes it types in what I'm sayng and some other times it keeps listening without typing anything.
I have already made a number of attempts under different contitions: good or bad Internet connection, wifi on & off, BT headphones or smartphone as input device, uninstall & reinstall the app, clear cache and data... Really I have no idea why this happens. Sometimes it works for a sentence and doesnt' work for the following one... Do you guys have any suggestions?