Im looking for an alternative to the pathetic google voice dialer for when you have your bluetooth headset connected, something that will dictate texts or you can speak texts etc. also Id like to be able to call alot easier than having to wate 30 seconds for it to finish speaking.....
cheers
Related
I've downloaded the latest fring windows mobile cab and installed it, but when I launch it - nothing happens.
I'm trying to get my google voice to integrate with my phone.
I have a Gizmo account and using Nimbuzz, I can dial out from
voice.google.com and talk over my TP2, but I can't use for instance iDialer to call out. I did set up my gizmo/google voice callbacks for iDialer.
I can't answer incoming calls over nimbuzz either, I answer but cant press 1 to accept the call
edit: disabled the "confirmation" on google voice but now it just keeps ringing even after answering?
I'm using Energy Leo WM6.5.3 ROM
Any help would be much appreciated!!
edit:
Been looking at why it wont work all morning, some say HTC Messaging, some say Sense 2.5, some say it flat out won't work with Energy Leo... o.0
bump.
i cant call out via idialer, i can dial out via gv web interface.
i cant answer incoming calls, only dialed out calls
my incoming sound isnt friendly except speakerphone (bluetooth/earpiece/headset i cant hear, but the other person can hear me)
edit:
got my SIP set up in the registry for WM InternetCalling, just need some codecs now and i need to test iDialer more.
I just noticed something wacky with my phone while experimenting with trying to figure out why Google Voice wasn't working. It looks like the dialpad tones/touch tones do not sound when connected to an incoming call.
If you can, please try the following:
1. Call your Epic from another phone
2. Pull up the Dialpad
3. Push a bunch of buttons on the Epic and see if you can hear them on the other line
I called from my office phone to my Epic, pushed buttons on the Epic, and didn't hear squat. I can't find a setting to turn this on - turning on "audible touch tones" didn't work.
Update: to be clear, this is not an isue I'm having with Google voice, it is an issue on any incoming call made directly to my sprint number.
Seriously? I can't get any help on this?
I've noticed many time when using google voice that the touch tones won't work when on a prompt syatem.
I just set it to ask me for each call and use my sprint number for calls that require that sort of input.
Aridon said:
I've noticed many time when using google voice that the touch tones won't work when on a prompt syatem.
I just set it to ask me for each call and use my sprint number for calls that require that sort of input.
Click to expand...
Click to collapse
That's fine but this is not a google voice issue... this is an issue on my phone that I found while testing google voice. ANY incoming call fails to register keypresses on the dialpad, hence the help I'm looking for; nobody so far has apparently tried this.
is there any
Voice apps like those where seen in NOKIA phones that Tells the contact name when an incoming call arrives ?
voice app that Speaks/Tell the message
so that it would be useful while driving !!
unfortunately, the application calls Announcer only available for Android phone http://getandroidstuff.com/call-announcer-android-app-download-v110/
That buggy pos called Voice Talk from gs2, now called S-Voice, is back to being a buggy pos on gs3.
It has a hard time doing the actual voice recognition. I actually had to rename a contact because it just can't match simple phonetic words with contact names.
Sometimes it fails to recognize and dial a bluetooth call, and then you have to reboot the phone. Sometimes it will stop listening half a seconds after starting to listen (with a bt car kit).
Your standard google Voice Dialer is much better. It doesn't require an internet connection either.
Could someone please make a flashable zip to replace s-voice with voice dialer.
EDIT: BTW, if you disable "double click home button to start s-voice" in s-voice settings, the home button lag magically disappears.
Is everybody else's bluetooth voice dialing just god awful?
S voice is crap, so it's frozen. Google's Bluetooth dialer is just the worst thing I've ever seen. Has anybody found out how to get Bluetooth dialing working properly?
Why in the world can't they just make Bluetooth launch voice search?
Sent from my SAMSUNG-SGH-I337 using xda premium
switters1 said:
Is everybody else's bluetooth voice dialing just god awful?
S voice is crap, so it's frozen. Google's Bluetooth dialer is just the worst thing I've ever seen. Has anybody found out how to get Bluetooth dialing working properly?
Why in the world can't they just make Bluetooth launch voice search?
Click to expand...
Click to collapse
Old thread, but I'll revive it because I want to talk about the same subject. I agree with the OP, and I'm surprised how badly Android/Samsung handles blutetooth voice dialing. (My last phone was an iPhone 3GS, and voice dialing worked great from day 1 back with iOS 3 or 4, whatever it originally came with.)
I frequently use bluetooth voice dialing in my car, either from a headset or speaker phone. This is a must-have feature for me.
Svoice is completely unacceptable because it requires the phone to be unlocked. If you have to mess with the phone to unlock it, then that defeats the purpose of voice dialing. I do understand that Svoice can do other things besides voice dialing, things which should be restricted by the lock screen. What I don't understand is why they don't give the users the options to enable selected features such as voice dialing while the phone is locked. But they don't, so Svoice had to go.
With Svoice uninstalled or disabled, Google Search takes over the voice dialing duties. It works ok, or at least it used to with Google Search v2.x. One thing about it that I don't like is that it wakes the phone (activates the screen) when you initiate voice dialing, so you can end up with accidental screen touches while voice dialing (if you don't have a pass code, or if it hasn't timed out yet). The screen should remain locked.
In recent versions of Google Search (starting in v3.x?), they decided to make voice dialing worse! If a person has multiple numbers, you can not directly select one, you have to wade through a stupid menu every time.
Say for example I have a contact named Tim Brown who has 3 numbers: home, work, mobile
With Google Search 2.x, you can do this:
Me: Call Jim Brown Home (or I can even just say "Call Jim Home" if I only have one Jim in my contacts)
Phone: Do you want to call Jim Brown at home? Say OK or Cancel.
Me: Ok
Phone: dials
With Google Search 3.x it ignores the location and always presents a menu:
Me: Call Jim Brown Home (the word "Home" is ignored)
Phone: Say Select 1 for Jim Brown Home, Say Select 2 for Jim Brown Work, Say Select 3 for Jim Brown Mobile, or say Cancel
Me: (If I can remember which freaking number was Home) Select 1
Phone: Do you want to call Jim Brown at home? Say OK or cancel
Me: (Yes I do, you stupid phone, I just told you so!) OK
Phone: dials
What a pain in the butt that is. Ironically, if you open Google Search by launching the app (i.e. by interacting with the screen), then it will listen to the "Home" part. It just ignores it if you are voice dialing, which is where you really need it. Does anybody from Google actually use this stuff?
My solution is this. Since my phone is rooted, I have the option of uninstalling Google Search v3.x, find v2.8 on the Internet, and install it on my phone. Then be sure to ignore any updates in the Play store. This works good enough. I can select a specific number when voice dialing, and I can voice dial while the phone is locked. It still turns on the phone screen when I voice dial, but I can live with that.
Note that I don't use Google Now, so I don't care about any new features that are included in the newer versions of Google Search. If you do use Google Now, this solution may not be acceptable to you.
If anyone else has a better solution, please share it.
Thanks
I tried using the Bluetooth Launch app to activate google voice search instead of the voice dialer, but that didn't work while the screen was locked. So for now, I'm sticking with the solution mentioned above (i.e. using google search v2.8).