I cant enable the Voice match on my phone , I am using 7 pro with H2os Beta 5,
the selection just goes grey
Related
As per the title, since the google search / google now update where by it can be used on any screen locked etc... when activated (it currently is not as it isn't compatible with English UK language) When I press my BT headset button it brings up the old voice dialler instead of google now, if I uninstall google search and try my headset it works but then if I apply the update it goes to the old voice dialler which is naff for anyone that has over 4 numbers and limited features.....
Any suggestions?
How many of you experiencing this too? I literally just switched back to Android specifically to use Google Voice, ported my number back over to Google, bought a Note Edge and upgraded it to 5.1.1 immediately (stupid). Found out GV outgoing calls are broken.
This is a known issue and google says they're working on it (https://productforums.google.com/forum/#!topic/voice/urpXxSfS-kE) but it's definitely irritating.
Yep..same thing here!
dimex said:
How many of you experiencing this too? I literally just switched back to Android specifically to use Google Voice, ported my number back over to Google, bought a Note Edge and upgraded it to 5.1.1 immediately (stupid). Found out GV outgoing calls are broken.
This is a known issue and google says they're working on it (https://productforums.google.com/forum/#!topic/voice/urpXxSfS-kE) but it's definitely irritating.
Click to expand...
Click to collapse
I am using GV to make weekly International calls, better to pay $0.07/minute than T-Mobile's $1.25/minute!!!
But since 5.1.1 it's broken....Here is the solution (in the mean while), that I have been using - and it's working again.
Say you want to call the number: 000-123-4567
Say your own GV-number is 111-222-3333
Reprogram the contacts you need to call from GV, with the number in this format:
111-222-3333 , , your-passcode# , 2 , 000-123-4567#
This will dial your own GV number, will prompt you for your passcode followed by #-sign, Option 2 will allow you to make calls, followed by #.
Each ',' is a few seconds delay - I have not tried it without the delays, but it also makes it easier to understand (for us humans).
Ya, no thanks. That's just a huge hassle.
Same problem here Google Voice does not work on the Note 4
I've got the same problem with the Note 4 (not the Edge version). I'm thinking this is an Android 5.1.1. problem. I never had this before I did the upgrade to 5.1.1.
What I see happening is this:
- You dial to make the call.
- I have Google Voice set up to ask me each time
- While the prompt for Google Voice is on top of the dialer, I see the dialer is already making the call.
So the dialer is not waiting for GV before making the call.
I'm trying to find out how I can go back to the previous version of Android, but so far it looks like I'm not able to do this.
I have a t-mobile Note 4. Hopefully t-mobile will release their 6.x version and that will fix this issue.
Just updated my honor 8 to emui 5 and when I try to use the dialer to make a call through Google Voice it says "call not sent". Anyone else having issues with the update and GV? Normal dialing through the carrier works fine.
I get the same message sometimes. But not always. Usually i just disconnect and retry again and the call will go through Google Voice just fine.
For me it's not an EMUI 5.0 specific problem. This used to happen occasionally in previous version as well.
I have had this problem on EMUI 4.0, 4.1 and 5.0 on a Huawei Mate and my Honor 8. I have not found any solutions. It was more prevalent on 4.0 on the Mate 8, than 5.0 is. Huawei support simply says they do not support apps. By the way, if you use Android Auto, you will find it fails when trying to make calls from the car. Something Huawei is doing with dialers is not compatible with other apps. For what its worth, a Le Eco Pro 3 was worse. It failed to dial every time, whereas with Huawei it is hit and miss.
fauxfive55 said:
Just updated my honor 8 to emui 5 and when I try to use the dialer to make a call through Google Voice it says "call not sent". Anyone else having issues with the update and GV? Normal dialing through the carrier works fine.
Click to expand...
Click to collapse
I've had this problem after the Nougat update too. The best way around this right now (from Mate 9 threads) is to use Google Voice in "ask for every call" mode and select "use google voice". That has been working consistently for me.
I had the same problem with Nougat. Couldn't find a fix so I rolled back to Marshmallow.
Try this
I am on 4.x eagerly awaiting 5.
I open Voice just prior to opening the Dialer. Then, dial immediately.
If there is too much delay before you place the call on the Dialer, you will get the error.
Anyone in the US still getting "call not sent" error?
crusht said:
Anyone in the US still getting "call not sent" error?
Click to expand...
Click to collapse
Yes, still getting this issue. Have not find or gotten a fix.
The work around is to dial immediately, but is a hit or miss.
Does anyone know how to get into ue menu with Google dialer or other means. 9860 or 986u1. I have both and 11 broke it on both
Hello.
I recently bought the Xiaomi Redmi Note 11 Pro 5G (2201116SG)
I'm on MIUI Global 13.0.8 Stable RKCEUXM
Android shows up as 11 RKQ1.211001.001
I used the feature that synchronizes apps and settings from my old phone (Redmi Note 8T)
I used third-party apps (DW Contacts & Dialer and Textra) and I wanted to carry that over.
I noticed however, that if those are set as defaults on the new phone, they don't fully work as expected.
Whenever I call or receive a call, the phone app doesn't pick up the contact name.
I get a notification that the App is not responding and the call was handled using the built-in phone app.
With Textra, I'm not sure, but it might not be getting my messages - If I switch defaults to the Xiaomi app, I gett notifications for all the missed messages and only then do they apear in Textra.
I'm not sure how to debug this or what other info I could give.