Lines Matching full:mmi
114 // MMI code '#' don't get confused as URI fragments.
287 // The MMI started dialog can actually be one of 2 items:
288 // 1. An alert dialog if the MMI code is a normal MMI
378 // handle the mmi complete message.
384 // finish, this includes any MMI state that is not
1041 // register for the MMI complete message. Upon completion,
1964 * Brings up the "MMI Started" dialog.
1973 // an MMI code while the radio is off or out of service.)
1980 // generic error dialog displaying the "Starting MMI..." message)
1981 // take it down before bringing up the real "MMI Started" dialog
1995 * (labeled either "OK" or "Cancel") on the "MMI Started" dialog.
2002 // First of all, cancel the outstanding MMI code (if possible.)
2005 // Regardless of whether the current MMI code was cancelable, the
2007 // take us to the MMI Complete dialog (see
2012 // partially-constructed state as soon as the "MMI Started" dialog
2416 // Need to treat running MMI codes as a connection as well.
2574 PhoneUtils.isRoutableViaGateway(number)) { // Filter out MMI, OTA and other codes.
2632 if (DBG) log("placeCall: specified number was an MMI code: '" + number + "'.");
2633 // The passed-in number was an MMI code, not a regular phone number!
2635 // fired an ACTION_CALL intent to dial an MMI code, like for a
2639 // (and we'll bring up the "MMI Started" dialog), or else
3231 // is up, or an MMI is running.)
3327 // Our initial phone number was actually an MMI sequence.
3331 // In-call MMIs do not trigger the normal MMI Initiate
4883 // while displaying an MMI result).
