Quote:
Originally Posted by taa1
So I'm doing it correctly then.
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.