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!
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
Hi,
I've got the HD2 WM6.5 and I reaaly love it. One problem though: I can't call numbers from within google maps. The device stops dialing before the slash ("/"), so it only dials the prefix of each number. I googled this problem and found others to have the same issue, but no result as of yet. Does anyone in here know a solution or workarround?
Thanks in advance
Tim
Hold on, not all at once. Cmon, I know this is an issue. Nobody with a solution/workarround?
Tim
Have you got the latest Google Maps?
I'm not having any problems. If I select a business for instance, it says tap for options. Tapping brings up all the things I can do (set as start point, call, etc.) Selecting call places the call correctly. I don't see where there's a "/" in the number.
I had a friend root my X10 with the MIUI rom but before hand had not set up my voicemail. I'm needing to set up my voicemail on the phone but I keep getting automated messages asking for "ten digit mailbox number of the person I'm calling or press pound"....when I press pound, it asks for a mailbox number, (which I dont have)....how do I get around this problem?
one thing I have noticed is that there is an extra setting under voicemail settings that says "voicemail service". This is not there on a stock x10.
Any help on this issue at all would be greatly appreciated. thanks.
I finally got it figured out! It ended up being a problem with AT&T and not with the MIUI rom
I've tried searching, but haven't found an answer, so here we go,
when I use the voice dialer to call someone that's already in my phonebook, it dials and calls properly, but if I try to call a place such as autozone or any other business by just saying, "call autozone," it finds the number and tries to call it but it puts a + in front of the phone number and never goes through. I have to end the attempt at calling and go back and edit the number to remove the + from it. Does anyone know how to fix this?
I'm running cm7x2 and haven't changed any performance settings.
Thanks, Curt
EDIT: it works now after a couple resets and sbfs later
When I open the phone dialer and start dialing someone's name it will give me the normal suggestions below the phone number but at least like 50% of the time it will show the person's non-mobile number. So I'll start dialing Steve or whatever and it'll suggest Steve Lastname Home with the dropdown that shows:
Search Results
<********************>
Steve Lastname
Home 123-456-7890
<********************>
Steve Lastname
Mobile 321-456-7890
<********************>
For the life of me I can't get the Mobile to be the first suggestion. On previous phones I just set whichever number I wanted to suggest first as default but it's like this phone doesn't check which one is default. And I can't determine any rhyme or reason as to the order it chooses. It sometimes put work first, sometimes even work fax. I think it's consistent for each person (ie whichever it puts first, it always puts first for that person) but honestly I've been so frustrated by it that I might have even missed that changing. I had a problem like this on the Samsung S5 a while back when I first got it, but then it stopped happening.
Anyone have any idea how to fix this?