Related
After I upgraded my ROM to DCD's latest, whenever I try dialing from contacts or speed dial, I get this error message:
"Press END key to stop intercept tone" and it never dials.
Anyone got any ideas?
which carrier?
never seen or heard of that, did you install the right rom for your carrier?
The carrier is Verizon and I chose Verizon from the kitchen when I created the ROM. I have made ROM's before on my 6700.
if I dial the number manually, it works fine. It's only when I dial from contacts or speed dial.
Strange.
Confirmed
I'm running the NexVision Hybrid ROM (based on DCD's ROM) on my XV6800, and I can reproduce this issue at will. I've narrowed it down (at least in my case) to the international dialing prefix being used. That is, if a contact's number is stored as (e.g.) "+1 212 555 1212", the dialer chokes on the "+1" - I hear a short beep, and then (usually) see the "Press END key to stop intercept tone" message.
If I edit the contact's phone number to remove the "+1" (or just the "+", leaving the 1), it dials just fine. Basically, it seems to always come down to the "+"...
The problem (for me, at least), is that I have a "+" prefix for most of my (many) contacts. Plus, most of the numbers in my employer's Company Directory (which I can search and dial from my device) have this prefix. I've had a few people ask me what the "+" prefix is all about, thinking the mistake is on my side for using some alien format for the country code prefix. Just to head that off, I'll point out that this format comes from the ITU-T Recommendation E.123, "Notation for national and international telephone numbers, e-mail addresses and Web addresses". So there. Plus, it's worked on every other phone I've ever used, including this one - at least I did, until I upgraded the ROM. ]
BetaMan, does this apply to your case at all? Either way, does anyone have any suggestions?
Thanks,
-roach
Has anyone noticed that when you put a pound key (#, aka number symbol, octothorpe etc) in a contact's number, it doesn't work? I.e. the # dtmf tone is not sent when you call the number, while other tones are sent properly.
For example, I set my voicemail number to *86,,5555# (the 5555 part is just for illustration, and should be filled in with the voicemail pin)
Whenever my phone calls voicemail, it says "Sending Tones 5555" but it doesn't mention the #, and I can tell that the # tone is not sent, because the voicemail system waits a few seconds after the password is sent, which is exactly what it does when I dial it manually and neglect to press #. When I do press pound manually, the system continues immediately without a pause.
Has anyone else experienced this? Or has anyone else been able to sucessfully send the # key?
hi, i haven't had this happen personally, but would puting space between the password and the # give the sytem time to receive it.? don't know if it will but i never had this happen either.hope this helps. hp
I don't think you can add spaces, but I added a comma (which indicates a pause) after the pin. That didn't help. Thanks for the suggestion though.
##7764726(spc=000000) and *#*#4636#*#* are hidden menus so the # may be handled special.
I actually noticed this today when I was trying to get through a damn automated menu. It kept asking me to hit the # key after things but kept telling me "Invalid Entry". I literally used every other button, to include * during the call and everything else worked. This is no bueno!
What version of Android and what Rom(if any) are you running? I am on 2.3.4 w/Eclipse v1.1
Thanks, AtLemacks, It's nice to know someone else has experienced the same thing (misery loves company I guess).
I'm using the same android version and ROM that you are. But I'm pretty sure I had the problem even back when I was using using P3Droid's Rooted Gingerbread without any ROM. I don't remember if I tried it when I was on stock Froyo.
I didn't have this problem before, I call/go through that menu fairly often.
did anyone figure it out?
I am suffering the same problem. Did anyone ever figure out how to send pound sign #?
Try a alternate dialer like Dialer One or the like.
Edit try voicemail *86, the # key skips to the next msg on my Milestone x2 port.
Found a solution
Found a solution, not sure if everyone can use it. I am using Motorola Photon with Sprint. My solution is to create a contact like this for google voice dial out
15125553010,,2,3235551110,#,,,1234,0118521234567,#
and it works for me. I can now use a direct dial icon on my home screen to call. The trick is the first pound sign. It needs comma before the pound sign and the three comma behind it.
Anybody else find a work around?
I am glad to hear that I am not alone, but a little dismayed to not see any answers to my days of searching for a solution. Has anyone else come up with an alternative work around? The direct dial method above didn't work for me.
Using a Galaxy S i9000 rooted with paranoid android 2.52 (although I did have this same problem with other mods as well)
Thanks!
I've been working at getting the voicemail for my first Android device, the SGH-i777, switched to GVoice for a bit now and I can't seem to get it working.
During the setup process [account selection, etc.] it goes to setup the voicemail and I get this error that reads:
"Error
Forwarding number changed failed"
So I found another route via the web interface with the string of numbers that reads: *004*googlenumber#.
Upon entering that in the dialer, I get:
"Call forwarding
Connection problem or invalid
MMI code
conditionally for All Basic Services"
Then I found a lead, on disabling all the settings under "Settings -> Call -> Call forwarding -> Voice Call". That gives me two errors:
"Unable to deactivate call diverting for unanswered calls. Unsupported by operator"
&
"Unexpected response from network."
Online, the web interface does show:
"Deactivate Google voicemail on this phone"
This is occurs when the device is stock and rooted, and running a new ROM. I've also tried deleting and re-adding my phone's number to my list of phones and reinstalling the GVoice app. [NOTE: It's stock and rooted right now though]
Ideas?
Check if the call can go into the voicemail message system first. If not, I will call ATT to reset the condition forwarding.
I do have a real AT&T voicemail setup and I can call it and leave a message [from another phone of course].
As for the condition forwarding, where should I take that? Tech Support via customer care? I did have to get on with tech support after they didn't switch my voicemail over from the iPhone's to a "standard" voicemail service.
SquidLord said:
I do have a real AT&T voicemail setup and I can call it and leave a message [from another phone of course].
As for the condition forwarding, where should I take that? Tech Support via customer care? I did have to get on with tech support after they didn't switch my voicemail over from the iPhone's to a "standard" voicemail service.
Click to expand...
Click to collapse
Squid,
I am trying to help you here but I may have misunderstood some things that you said. Anyways, I had gVoice forwarding my voice mail just fine - actually, against my will because I wanted to stay with ATT voice and only use gVoice for text messages. Thus, if you go into settings>call>call forwarding - what does it say there? List your google number or does it list your ATT voice number? In my case it listed my google voice phone number and not my carrier number. I changed that back to my carrier, but maybe you go the opposite route. Sorry if I missed your point.
AtlanM87 said:
Squid,
I am trying to help you here but I may have misunderstood some things that you said. Anyways, I had gVoice forwarding my voice mail just fine - actually, against my will because I wanted to stay with ATT voice and only use gVoice for text messages. Thus, if you go into settings>call>call forwarding - what does it say there? List your google number or does it list your ATT voice number? In my case it listed my google voice phone number and not my carrier number. I changed that back to my carrier, but maybe you go the opposite route. Sorry if I missed your point.
Click to expand...
Click to collapse
When I go "Settings -> Call -> Call Forwarding" there's another option in there with "Voice Call". There's then 4 lines, "Always Forward", "Forward When Busy", "Forward When Unanswered", "Forward When Unreachable". All of those [EXCEPT "Always Forward"] have text that reads "Forwarding to [presumably the AT&T voicemail number]".
I couldn't disable it manually, but I see where your going with it. Sadly, I cannot change any of the settings in there. Refer to the OP when I mention the lead on "disabling" the settings.
SquidLord said:
When I go "Settings -> Call -> Call Forwarding" there's another option in there with "Voice Call". There's then 4 lines, "Always Forward", "Forward When Busy", "Forward When Unanswered", "Forward When Unreachable". All of those [EXCEPT "Always Forward"] have text that reads "Forwarding to [presumably the AT&T voicemail number]".
I couldn't disable it manually, but I see where your going with it. Sadly, I cannot change any of the settings in there. Refer to the OP when I mention the lead on "disabling" the settings.
Click to expand...
Click to collapse
ok. Have you tried to uninstall gvoice, reboot, and re-install? Probably did, just saying.
AtlanM87 said:
ok. Have you tried to uninstall gvoice, reboot, and re-install? Probably did, just saying.
Click to expand...
Click to collapse
Yes I have. I've tried a bunch of things.
But amazingly, I get to close this thread now! I called up AT&T and asked about conditional call forwarding and the guy walked me through a bunch of stuff. What ended up being the issue was the number set for the 'conditionals' in call forwarding and the "carrier number" for the voicemail [just below the radio button to select Google Voice] were different by one digit. Changing the carrier number to match the conditionals let the whole operation happen smoothly.
So, thanks to the two of you who responded!
SquidLord said:
Yes I have. I've tried a bunch of things.
But amazingly, I get to close this thread now! I called up AT&T and asked about conditional call forwarding and the guy walked me through a bunch of stuff. What ended up being the issue was the number set for the 'conditionals' in call forwarding and the "carrier number" for the voicemail [just below the radio button to select Google Voice] were different by one digit. Changing the carrier number to match the conditionals let the whole operation happen smoothly.
So, thanks to the two of you who responded!
Click to expand...
Click to collapse
Glad it works for you! Just for my information, the "conditional" is in which menu - call forwarding? I can't find a "conditional" option. I am sure this will come up again sometimes, so I try to fully grasp it. Thanks man!
I don't understand. I've had this same problem since I got my new phone, the SGH-i727 Skyrocket. My number in the carrier setting exactly matches the number for the "conditionals"... So what gives? I'm rooted and running a custom ROM, but the issue was present before I ever rooted, when I was stock.
I had some issues setting mine up, I am also rooted. Have you tried looking at voice.google.com -> Settings -> Phones -> Mobile and seeing if its checked or even there?
Also I reinstalled all the google apps so that might have also helped.
I had a similar problem. I'm guessing you have the Google voice app installed? I would try to reset to defaults the dialer info.
Try this
1. Remove Google app.
2. Clear dialer and dialer storage cache
3. When you go to dialer, the settings should be reset. Configure it as if you have no Google voice.
4. Install Google voice, but make sure you have both WiFi internet and cell phone reception.
5. Hopefully it succeeded, regardless go to the dialer --> Preference --> voice-mail handler for me its either Google voice, or voice mail, or none(dial voice number)
Like wise if you have the number is correct on the Google voice website and you have configured the phone with the app try entering this code. Remember the number is your Google voice mail.
Remove the dashes, and the X's correspond to the Google number, these are to be entered on the standard dialer. I do recommend this be your last step
AT&T
*004*1XXX-XXX-XXXX#
Verizon
*71XXX-XXX-XXXX
T-Mobile
*004*1XXX-XXX-XXXX#
Sprint
*28XXX-XXX-XXXX
not trying to revive a dead thread, but I was going at this all night and nothing worked, (new gs3 ATT)
have used gv for everything for a long time now and nothing has worked with this phone.
Went through and tried all the stuff above, and finally I tried putting in the mmi code in the dialer as *004*(area code and number)# and it went like normal, like a regular nexus phone.
This is without the "1" before the are code.
It went through fine and changed all the forwarding numbers in the forwarding menu, and set GV as voicemail.
The reason is that inside the phone- settings- voicemail-setup, you get what looks like a GB screen with your google voice number without the +1 infront of it, and no way to change it I don't think.
this is what the guy above was taking about I think with the att person on the phone. I hope this helps someone, I could have used it yesterday
jbrinkley said:
not trying to revive a dead thread, but I was going at this all night and nothing worked, (new gs3 ATT)
have used gv for everything for a long time now and nothing has worked with this phone.
Went through and tried all the stuff above, and finally I tried putting in the mmi code in the dialer as *004*(area code and number)# and it went like normal, like a regular nexus phone.
This is without the "1" before the are code.
It went through fine and changed all the forwarding numbers in the forwarding menu, and set GV as voicemail.
The reason is that inside the phone- settings- voicemail-setup, you get what looks like a GB screen with your google voice number without the +1 infront of it, and no way to change it I don't think.
this is what the guy above was taking about I think with the att person on the phone. I hope this helps someone, I could have used it yesterday
Click to expand...
Click to collapse
This isn't the s3 section
Sent from Zanpakuto using Getsuga Tensho!
Wow really? Thanks dude. Let me know when gv.apk and att vm settings get phone specific across the board.
jbrinkley said:
Wow really? Thanks dude. Let me know when gv.apk and att vm settings get phone specific across the board.
Click to expand...
Click to collapse
Not sure if you're trying to be a smartass or not, but....either way this is the i777 forum. Post in the forum relative to your device.
why are you guys so touchy about specific forums? Looking for help from wherever it comes from is a good thing.
That little clue about numbers matching would have helped me yesterday, regardless of what phone I was using. ANd it will help someone in the future.
If it was an htc forum I might have said something different, but I still would have said something.
Telling someone to gtf out of your forum for no good reason is just silly.
Everyone is here to help. That's all there is. If no one needed help, there wouldn't be an XDA.
but ya, I'll stay out of your guy's forum. not that I post alot or anything.
Don't choke on your lollypop
And here I thought I was being nice. I don't remember telling anyone to gtfo....I simply said to post in your phones forum. Well good luck. Happy flashing.
All I said was that this isn't the S3 section. Was that so wrong? Many things are device dependent. So many things can't be given support for unless you have our device.
Sent from Team Pirate! Using Tapatalk 2
Prior to the latest update to Google Search 3.5.16.1262550 a couple weeks ago, I used to be able to do a long press on my BT headset to bring up Google Now, which let me say, "Call Joe Blow home" and it would make the call to his home number. Now it brings up Google Dial which tells me to say "Call someone" but pops up with a numbered list of the cell, home, and work numbers on the screen that I either have to touch to choose the one I want, or say, "Select Two" to dial his home number. This requires that I either touch or look at the screen to make a call, which totally defeats the purpose of "hands-free" calling.
I have switched back to S-Voice for now, which I hate because she talks too much before I can actually make a call, but at least I don't have to dig my phone out to push or see which phone I want to call. I hope someone can help us get back to BT dialing the way it used to be.
This is on a Sprint Galaxy Note 3 running KitKat, but I imagine this is affecting all phones.
Yes I have a note 3 kitkat and Google search issue is affecting my phone as well. Instead of Google now voice prompt when pressing headset hard button on my LG bluetooth headset....Goople dial is not default which sucks!
Bump! Surely someone must use Bluetooth dialing from a headset and noticed this major change besides the two of us. Please help if you have any ideas to revert Google Search to work the way it used to.
Bump again! Doesn't anyone else use their Bluetooth headset to initiate calls?
I think I have finally found an acceptable workaround using Bluetooth Launch from the Play Store. Install the app and follow the directions as described in this thread: http://forum.xda-developers.com/showthread.php?t=2794883
Step one shouldn't be needed as when you long press, it will detect the new app and let you select Bluetooth Launch as the default.
I've had this issue for a long time now, I can't figure out why this is happening, when someone dials my google number, both the dialer applications ring, the google dialer and hangouts dialer.
Under Handgouts Dialer i do have "Incoming phone calls" checked, I also see both my numbers listed under confirmed phone numbers.
Any ideas? I can't find anything about this anywhere.
Shemploo said:
I've had this issue for a long time now, I can't figure out why this is happening, when someone dials my google number, both the dialer applications ring, the google dialer and hangouts dialer.
Under Handgouts Dialer i do have "Incoming phone calls" checked, I also see both my numbers listed under confirmed phone numbers.
Any ideas? I can't find anything about this anywhere.
Click to expand...
Click to collapse
You wrote that you have the "incoming phone calls" box checked in Hangouts but are complaining that it's ringing through Hangouts… Is that what you meant to write?
What's the end result you're looking for?
If you don't want your phone to ring when someone calls your GV number (i.e., as a forwarded call) you should still be able to turn it off in the GV settings on a desktop browser. I'm still new to the board, so I can't post links yet. google/com/voice/#phones
Hope that helps.
Yea, i didn't want my google phone number to ring my android dialer, i went to https://www.google.com/voice/#phones and found the option to forward calls to, and my telecom number was listed there to forward to, i turned it off and it fixed the problem.
Thank! - This fixed it!.