Lines Matching full:dialog
22 import android.app.Dialog;
127 // Amount of time that we display the PAUSE alert Dialog showing the
222 // The MMI started dialog can actually be one of 2 items:
223 // 1. An alert dialog if the MMI code is a normal MMI
224 // 2. A progress dialog if the user requested a USSD
225 private Dialog mMmiStartedDialog;
234 // NOTE: if you add a new dialog here, be sure to add it to dismissAllDialogs() also.
324 // a system dialog in PhoneUtils.displayMMIComplete(), we
621 // is able to see the error dialog!)
665 // error dialog (see "showStatusIndication()" above).
669 // InCallScreen when the user presses the dialog's OK
684 // user (like a dialog), and the in-call UI itself is
759 // If there's a pending MMI code, we'll show a dialog here.
761 // Note: previously we had shown the dialog when MMI_INITIATE event's coming
764 // Now we instead check pending MMI code and show the dialog here.
773 // Also we show pre-populated in-call UI under the dialog, which looks
934 // This means that the user has been opening the "Respond via SMS" dialog even
936 // In that case we just close the dialog and exit the whole in-call screen.
940 // when OTA Activation, OTA Success/Failure dialog or OTA SPC
941 // failure dialog is running, do not destroy inCallScreen. Because call
942 // is already ended and dialog will not get redrawn on slider event.
1095 // PhoneUtils will bring up a system dialog instead of the
1642 // mSuppServiceFailureDialog is a generic dialog used for any
1644 // instance at a time. So just in case a previous dialog is
1648 mSuppServiceFailureDialog.dismiss(); // It's safe to dismiss() a dialog
1746 // with a dialog instead of going through the normal disconnect
1780 // Show the dialog now since the call that just failed was a retry.
1785 // Show the dialog for failed call if Auto Retry is OFF in Settings.
1790 // the dialog if *this* call fails.
1867 if (DBG) log("- onDisconnect: Respond-via-SMS dialog is still being displayed...");
2025 * Brings up the "MMI Started" dialog.
2033 // mainly since in the Dialog.show() might fail if we don't have a
2042 // Also, if any other dialog is up right now (presumably the
2043 // generic error dialog displaying the "Starting MMI..." message)
2044 // take it down before bringing up the real "MMI Started" dialog
2058 * (labeled either "OK" or "Cancel") on the "MMI Started" dialog.
2069 // take us to the MMI Complete dialog (see
2074 // partially-constructed state as soon as the "MMI Started" dialog
2174 * Pop up an alert dialog with OK and Cancel buttons to allow user to
2197 public void onClick(DialogInterface dialog, int whichButton) {
2205 public void onClick(DialogInterface dialog, int whichButton) {
2218 * Pop up an alert dialog which waits for 2 seconds for each P (Pause) Character entered
2291 public void onClick(DialogInterface dialog, int whichButton) {
2305 public void onCancel(DialogInterface dialog) {
2377 if (DBG) log("- updateScreen: Show OTA Success Failure dialog");
2424 // Forcibly take down all dialog if an incoming call is ringing.
2428 // Wait prompt dialog is not currently up. But it *should* be
2446 if(DBG) log("show the Wait dialog for CDMA");
2539 public void onClick(DialogInterface dialog, int which) {
2546 public void onClick(DialogInterface dialog, int which) {
2552 public void onCancel(DialogInterface dialog) {
2559 // When the dialog is up, completely hide the in-call UI
2626 // progress dialog) that we need to continue to display.
3065 // But it might be nicer for the dialog to offer the option
3126 // CDMA-specific "call lost" dialog. (If an outgoing call fails,
3128 // call fails too, we display this specific dialog.)
3148 // make sure the Dialog handles both OK *and* cancel by calling
3157 // that, neither the dialog's clickListener *or* cancelListener seems
3162 * Utility function to bring up a generic "error" dialog, and then bail
3174 public void onClick(DialogInterface dialog, int which) {
3178 public void onCancel(DialogInterface dialog) {
3183 public void onClick(DialogInterface dialog, int which) {
3187 public void onCancel(DialogInterface dialog) {
3200 // When the dialog is up, completely hide the in-call UI
3211 // Don't need to show the dialog if InCallScreen isn't in the forgeround
3217 // Don't need to show the dialog again, if there is one already.
3231 * Displays the "Exiting ECM" warning dialog.
3239 * So bring up a dialog explaining what's happening. There's nothing
3242 * this, but toasts are pretty easy to miss, so instead use a dialog
3249 * Instead, this warning dialog should really be triggered by our
3254 * display this dialog when exiting ECM because of an outgoing call,
3271 // When the user dismisses the "Exiting ECM" dialog, we clear out
3273 // dialog), but do *not* bail out of the InCallScreen.
3277 public void onClick(DialogInterface dialog, int which) {
3281 public void onCancel(DialogInterface dialog) {
3304 // Now that the user has dismissed the error dialog (presumably by
3310 // dialog is supposed to persist across orientation changes or if the
3331 * a dialog and want to pre-empt any currently visible dialogs,
3337 // Note it's safe to dismiss() a dialog that's already dismissed.
3339 // possible that the actual dialog(s) may have already been
