I'm attempting to set up a contract entry to automatically dial my home voice mailbox, put in my mailbox number, do the "#" etc., but I need to be able to do a pause in the dialing sequence. Here's what I've tried:
xxx-xxx-xxxx,1,#,yyyyyyyyyy#,zzzzzz#
Where x's are for the mailbox service phone#, y's are my home phone# and z's are the pin#. The G1 put in the dashes for me.
When I touch the contact to have it dial, I see:
USSD code running....
"Connection problem or invalid MMI code."
you're getting the errors because of the "#" symbols
did you try to put +1 in front of the number?
Thanks for the prompt reply!
If I change to:
+1xxx-xxx-xxxx,1,#,yyyyyyyyyy#,zzzzzz#
I get the same error(s).
Any ideas on what else I could try?
On my RAZR you inserted a "W" or a "P" for a wait or a pause. I wonder if there is something analogous to that.
[
To insert a pause, open the keyboard and type a "," (comma) for a pause. The more commas, the longer the pause.
You can also use the keyboard to enter phone numbers that advertise as words, like 1-800-BUY-4EVER (when you press the letter key, the associated number appears in the dialer window).
ya i think the error is cause of the "#"'s.
my banks telephone banking requires #'s after the account number. it errors out.
then, i have this preset deal that gives me the condiotions on the mountain passes. the code goes 511,1,3,90,1,5 aand it works fine.
so if youre having the same troubles, i assume its the "#"s. i hope there will be a chaange to that as now i cant do ant telephone banking or banking via androids browser. so its pretty irritaiting.
So I'm doing it correctly then.
This explains why when I tried to change the commas to "p" and "w" per MrGibbage's suggestion they appear as "7" and "9" respectively. I like this feature.
So I guess I'll just have to wait for a software update to fix the "#" problem. Is there a separate email or forum area for reporting bugs?
Sorry, guess I didn't read your post carefully enough. I thought you were trying to use "#" as a pause character.
The "USSD code" thing is what is used to query the carrier for information. For example, with T-Mobile (and probably others) using "#646#" as the number to dial will cause the phone to send a USSD code to T-Mobile requesting how many minutes you've used (you will get a status popup that displays the information). Other USSD codes are "#225# for balance, and "#768#" for last payment info.
So the problem is that using "#" in a number, pre-dial, causes the phone to send a USSD code to the carrier (and probably an invalid code, since they're usually 3 digits).
It should be possible to patch the dialer so that it only tries to send USSD codes for known codes, and for all others it uses as is the pound key was hit on the dialer. Since it's now open source, this is definitely possible. It's just a matter of priorities.
I realize this thread is somewhat confusing since (I realize now) the real issue is about the "#" character and not about a "pause" character. I can't figure out how to change the thread title to make it more meaningful.
Cool. Maybe the patch would be as simple as saying if the first character of the number to dial is a "#" then treat as USSD, otherwise treat as-is? Are there any valid USSD's that DON'T begin with a "#"?
What is the proper venue for reporting the problem I'm encountered -- email or some other forum? Not sure how to get this info into the hands of the people who can make the patch?
Bookmarks