I had multiple galaxy notes in the past and every time I use the microphone feature I am able to use Google Voice typing but on the note 7 I am forced to use S voice typing. I have searched every single option to try to remove the s voice typing feature and replace it with google voice typing but no luck. Is anyone else having the same problem or perhaps found the solution to this issue.
Thanks
Related
Does anybody know of a voice dialer software out there better than the one Google put out? If not, can someone PLEASE develop one? These things are supposed to be used in conjunction with a bluetooth headset and are supposed to avoid user input because of traffic laws yet the one Google put out prompts the user every time!
Isn't the bluetooth function coming in donut?
What do you mean "the bluetooth function"? Cupcake has full bluetooth capability and the voice dialer technically works with the voice dialer, just not even remotely well enough.
In reference to what your asking. Using your bluetooth to start voice dialing.
That's available right now. I can press the button on my headset to activate voice dialing. It works about 80% of the time. The problem is with the voice dialer application itself. Simply put: it sucks balls.
Does anyone know if the Quick Search Box's voice dialing feature is replacing the actual voice dialer? The teaser video for 1.6 shows it working well (ie figuring out WHO you want to call and doing it automatically without user input) but I also noted a voice dialer icon in the video and technically they pressed a button on the Quick Search Box to activate it. I'm wondering if that can be activated with a BT headset.
rickytenzer said:
Does anyone know if the Quick Search Box's voice dialing feature is replacing the actual voice dialer? The teaser video for 1.6 shows it working well (ie figuring out WHO you want to call and doing it automatically without user input) but I also noted a voice dialer icon in the video and technically they pressed a button on the Quick Search Box to activate it. I'm wondering if that can be activated with a BT headset.
Click to expand...
Click to collapse
I hope so - i've been waiting (im)patiently for voice dial in the UK for a loooooong time
I love the way you have to put on an American accent to get the google voice dialer to work
Call home
English English - "Cawl hoeme" = random results
US english - "kahl hom" = call home
Rubbish
I had to rename the girlf in my phone to "love of my life" which works well. "K" offered me to call "Ed"... So its not great really. Voice search in google seems accurate though.
Direct dial shortcuts ftw. They actually require one less click than trying to voice dial.
BT headset voice dialling would be great though.
Real voice dialing for Android please! It's ridiculous how a 3 year old Windows Mobile device can have 100X better voice dialing...
I'm trying to use voice actions since Google added spanish support. It works fine in the sense that it recognizes commands easy enough. But when I tell it to "Call whatever" sometimes it will look up a contact in my contacts but some times, to my infinite annoyance, it will show some random person I'm assuming it found on the internet or google or god knows what.
Any idea how this is happening??
Thanks
Hi!
Just notices this very annoying and strange behavior of my XZ (Vodafone Stockrom 4.2/.67)
When I receive a call I cannot use the keyboard anymore. As a matter of fact, the keyboard does not pop up when I open e.g. the notes-app or any app waiting for text-entry. The cursor is there and blinking but the keyboard does not show up, no matter which app (notes, quickoffice, kingoffice, sms, even google play store the search field.) I cannot take notes during the call or change any contact/calendar details. Really annoying.
Does anyone ever experienced the same?
Thanks in advance,
Michael
When Verizon pushed out the KitKat update for the G2, one of the "features" I discovered is that voice dialing from a bluetooth headset got all messed up. Long-pressing the headset button still brings up a voice dialer, but it's an idiotic voice dialer that can't understand what I'm saying and even if it does, certain numbers it just goes "no entry" even though I have multiple numbers in that person's contact file. It's garbage.
There is a way to completely get rid of this and instead use Google Now when you long-press the button on a bluetooth headset. Steps are as follows:
1. Find and disable the pre-installed app called Voice Command
2. Install the app Bluetooth Launch - https://play.google.com/store/apps/details?id=com.kin.bluetooth_launch&hl=en
3. Open Bluetooth Launch. It's going to be a bit funky looking because it's not optimized for higher-resolution screens. You'll see a bunch of really small text with overlapping buttons on the left. It's ugly, but it'll still work.
4. Scroll down to Google Search, tap on it, and it'll expand a list of a bunch of things. Tap on the one that says 'com.google.android.googlequicksearchbox.VoiceSearchActivity'
5. Pair up your bluetooth headset, and long-press the button like you would to voice dial. You should get a popup that asks which app you want to use. Select Google Search and then 'do this always' to set the default.
This should pop you over to Google Now, which can recognize voice commands just fine, unlike the worthless LG Voice Command. It should also make Google Now the default behavior for long pressing the bluetooth headset button.
Nice write up. Stock voice command works well for me along with non NOW search. I've boycotted NOW for it's ridiculous battery drain. At one point NOW and location services were decent in battery saving, recent service updates have made it worse though.
Thank you sir for showing us how to get back to using Google Now. After the latest Google Search update, BT dialing activated Google Dial instead, and this is the only fix I have found for it. So far this is working great on my Sprint Note 3, and I bet it will work for everyone's phone.
Looks like there is an issue when using Google Voice and this phone . I get the error "call not sent limit exceeded". Blu support said that they are aware of the issue. Basically instructed me to get another dialer on the play store :laugh:. I tested a few dialers and only the Hangouts Dialer app worked.
Same issue seen on the Blu Pure XL.
Happens on the blu advance 5.0 too even after the Blu software update :-/ . Will try the hangouts dialer.
Same issue with BLU Energy XL
Hey guys,
The same issue is found on the BLU Energy XL. Just bought one for my wife and this drives her crazy since it forces her to use WhatsApp for calls which burns through data.
I've found two fixes for this, but they only seem to be temporary:
1. Restart your phone.
2. Open your phone settings, go into the Apps, and view All apps list, then scroll down to Dialer or Phone (depending on which you have), then clear all data within the Dialer/Phone app.
Once again, these are solutions found using Google and they seem to only be temporary since the problem comes back after calling 2-3 people afterwards. I'm still searching for a permanent fix, perhaps someone can try replacing the Dialer/Phone app with an older version apk? I can't do this since it's my wife's phone, but if someone tries it please post your results!
Yes, This is a problem and it's annoying. I take the following steps and it works 9/10 times, for the 1 time it doesn't work, I just restart the phone.
1. Dial a 1800- number. This way the phone call will go through and register in the cache. ( I usually dial Customer Service)
2. Dial the other number you wanted to call using Google Voice.
Please note: I use Google Voice to only dial international numbers. (That's the option setting in Google Voice)
Anyone found a permanent fix for this?
I believe you can use only the native dialer app for Google voice calls to work.