I use GVoice for incoming/outgoing calls. When I receive a call, I swipe to answer, GVoice then announces the caller, and tells me to enter "1" to connect. When I activate the dialer touchpad, there is no response when I hit "1" and the screen blanks. I'm sure there is no touch tone sent.
What's wrong here. I've had to turn off GVoice's caller announce because I can't connect to incoming calls.
This is a VZW Nexus FWIW.
Are you running a custom ROM? perhaps something has been disabled. I run codenamedroid, and when I press 1 I here no tone yet Google voice still connects me to the call.
Sent from my GalaxyNexus using xda premium
Pure "out-of-the-box" ROM. No root. Plain vanilla.
EDIT... this is interesting... I ran into a related problem. I answered a call I was expecting on the first ring, and GVoice told me to press "1" to ensure I wasn't an answering machine. Of course I couldn't do that since the keypad was disabled on received calls. Out of curiosity I disabled the pattern lock I was using, and now I can answer immediately. Just wondering if the pattern unlock is related to my keypad disable, since my incoming calls come to a locked phone. I haven't tried other lock mechanisms because frankly I'm tired of this problem... waiting on CM9
Related
When my phone is locked, I simply just dont recieve calls. It rings on the other persons end, but it doesn't pop up, there's no ring tone playing on my phone, and there's no missed call indicator even. I just dont get the call. I get the voicemail afterwards at least.
When my screen is on I get the call immediately. However, there is a pretty bad delay either in incoming voice or outgoing. People respond 3 seconds after i finish talking and I'm constantly cutting them off. What's up?
I don't have any issues on the nightlies; maybe you should update to a more recent rom.
it's the latest release candidate - i've had it installed for like 2 days.
I have this weird UI functionality issue where the phone redials the last dialed number exactly when I want to hang up. This actually is not a bug in the system. Its just a design issue.
Here is what happens: I make a call using the dialer. The call connects fine but when I'm about to hang up and if at that instant or just before that, if the person on the other side hangs up, my end key becomes a dial key and a new call is initiated to the same person.
I want to be able to exit the dialer once I hang up a call that I've initiated. Is there a setting for it? Can I do some mod that can allow me to do this?
The same problem isn't noticed with an incoming call. Basically I'm doing something or the phone is idle. Once I'm done with an incoming call, the hang up / end button sends me back to the previous state. This is exactly what I want the outgoing call to do.
Any ideas? Is someone else facing the same issue with some other handset?
I'm on an HTC Desire (Bravo) SLCD with an InsertCoin Sense 2.1 ROM 1.1.4 release.
a temporary workaround is to install a sencondary dailer, so when you do press dial again, it prompts you to choose one, thus preventing the call to go through. Although this can be irritating sometimes.
I am running stock rooted Android 2.3.4. My dialpad works except while I am in call - it becomes glitchy. Any numbers I dial on the dialpad while in-call usually registers twice. For example, I work in the hospital and usually need to page someone but when I press keypad during a call to leave numeric #: 12345, it instead leaves 1122334455 or some times 111223445. Tried rebooting, long presses and short presses without any help.
This also happens for anything that requires dialpad during a call: voicemail pin: 1234 but it says invalid "you entered 11223344". It also happens with bank account, calling cards....
My keyboard/dialpad work without problems during regular use.
Tried to use Dialer One app but it pushes me to stock dialpad while in-call. The one app that has worked is TalkaTone VOIP - its uses its own dialpad while in call without problems but its a voip program.
Anyone know of any other dialer apps that uses its own dialpad while in call?
Others had the same problem but no solution:
http://code.google.com/p/ice-cream-sandwich-sgs/issues/detail?id=319
Are you on speaker phone during those calls im not rooted or custom rom but my phone does that while on speakerphone
Sent from my SPH-D710 using xda premium
Tried with and without speakerphone but it didnt work. But I have noticed switching speakerphone on and off sometimes helps with the first few digits but its not gauranteed.
See if this helps:
[HowTo] Make e4gt touch tones work with voice mail and other ivr systems
Hello- was not able to search for this but here it goes:
Using stock 4.04 but rooted
straightalk ATT as my carrier
when I get a call to my GV number and try to slide (to left) to reject the call, the phone momentarily stops ringing but then starts ringing again until it times out and goes to voicemail- anyone else with this problem?
Mine does the same thing. I think Google Voice will keep placing new calls to any connected phones that hang up until it goes to voicemail. I've gotten it to ring again 2 times a few times. I've been told that you can silence the call with volume down instead of rejecting it, which will actually keep it from ringing until it goes to voicemail, but I haven't tried it yet. Personally, I'm planning on getting rid of Google Voice partly because of this.
This has always been a problem I am just now getting around to posting it. I must be doing something wrong. If I am on the phone with someone and someone else calls. I tell them I will call them back and take the latest incoming call but it never hangs up. I sit there and talk to the other person and it will continue to say they are there. Then once I am done talking to that person what will happen is I will hang up and the first caller will make a dial tone like beep beep beep then hang up it's weird.
Have you tried hanging up on the existing call, then accepting the incoming? When that happens [rarely ever for me], that generally works, and no issues.
teh roxxorz said:
Have you tried hanging up on the existing call, then accepting the incoming? When that happens [rarely ever for me], that generally works, and no issues.
Click to expand...
Click to collapse
I never have. I always just accepted the call. Also, I noticed lately that whenever I get a call a voice comes on and asks do I want to accept the call. Must be a setting I changed but I thought that I changed it back. Doesn't matter if it is a contact or unknown number or landline or cell.
.Bambino said:
I never have. I always just accepted the call. Also, I noticed lately that whenever I get a call a voice comes on and asks do I want to accept the call. Must be a setting I changed but I thought that I changed it back. Doesn't matter if it is a contact or unknown number or landline or cell.
Click to expand...
Click to collapse
Hmm, maybe a bug? Oh, well to fix the voice issue:
> log into voice on the chrome browser
> go into call settings
> UNCHECK call screening
Someone told me it could be Google Voice which I recently installed. But I uninstalled that and Skype and I still get a message once I accept a call. It says press one to accept or two for voicemail. Never used to do this. I am on FreeGS3. Not the latest update.
Call waiting
.Bambino said:
This has always been a problem I am just now getting around to posting it. I must be doing something wrong. If I am on the phone with someone and someone else calls. I tell them I will call them back and take the latest incoming call but it never hangs up. I sit there and talk to the other person and it will continue to say they are there. Then once I am done talking to that person what will happen is I will hang up and the first caller will make a dial tone like beep beep beep then hang up it's weird.
Click to expand...
Click to collapse
What you've found is the call waiting feature. When you accept the incoming call, it places you current conversation on hold while you answer the new call. If you would complete the second call and end it, it would reconnect you to the first call. Since you told the first caller that you would call back, he hung up but you placed that call on hold, hence the dial tone. If you would actually "end" the first call before taking the second on you wouldn't have the issue.