Work around some functional but nonstandard MMI codes.
http://code.google.com/p/android/issues/detail?id=2226 http://code.google.com/p/cyanogenmod/issues/detail?id=1575 The MMI code "#190*1660#*" is nonstandard, not ending with #. The "*" at the end gets parsed as the dialingNumber portion, and processCode raises an error instead of treating it as a generic MMI code with no special handling and passing it on verbatim. Treat the * at the end as part of the # terminator, so it doesn't get dropped into dialingNumber. I can't fully test this; I don't know any T-Mobile MMI codes like this and I'm not going to dial mysterious MMI codes into my phone. I've tested that normal MMI codes still work by stopping and restarting call forwarding to GV on my phone. Someone affected by this issue needs to test this. Updated the "dialing number" comment, which was incorrect. If this isn't fixed in the 2.2 source drop, this commit can probably be pushed upstream after confirmation.
Loading
Please register or sign in to comment