I'm up against the same issue, glad to see I'm not crazy. Did you ever find a workaround or get any resolution?
On Apr 25, 6:26 am, Lee <[email protected]> wrote: > Encoding # works fine. An encoded comma or semi-colon doesn't display > and stops further parsing of the number at that point, as far as the > phone app is concerned (Nexus here). > You can manually add them with the phone app via the menu options but > that doesn't help me much when the purpose is auto-dialling. > > Any other workarounds or does this need reporting ? > > Lee > > On Apr 13, 2:38 pm, Mark Murphy <[email protected]> wrote: > > > > > > > Gustavo wrote: > > > I'm trying to place a call with Intent.ACTION_CALLand a tel uri > > > including pauses and dtmf codes to be sent when the call is > > > established (i.e. tel:+1777777777,,,,,,,,,,5555555). > > > > Android strips all the special characters and place the call to the > > > rest of the uri (i.e. tel:+17777777775555555) > > > > Any workaround? > > > > I'm testing it with HTC Hero (1.5) > > > Commas are not valid URL characters and need to be escaped. Either use a > > URLEncoder or just convert each of them to %2C. > > > -- > > Mark Murphy (a Commons > > Guy)http://commonsware.com|http://twitter.com/commonsguy > > > Android Training in US: 14-18 June 2010:http://bignerdranch.com > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group > athttp://groups.google.com/group/android-developers?hl=en- Hide quoted text - > > - Show quoted text - -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
