Android来电识别应用：自定义Dialog被其他Activity遮挡问题求助

Hey there! Let's work through that dialog overlay issue you're hitting with your caller ID app. The root problem here is likely that when you trigger the ACTION_CALL intent, the system's dialer activity launches and takes priority over your custom dialog, pushing it into the background. Here are a few solid solutions to fix this:

1. Adjust Dialog Window Properties for Higher Priority #

You can configure your dialog's window to sit above other system activities by setting specific window types and flags. Note that this requires a special permission on newer Android versions.

First, add this permission to your AndroidManifest.xml:

<uses-permission android:name="android.permission.SYSTEM_ALERT_WINDOW" />

Then, when creating your dialog, tweak its window settings:

Dialog customDialog = new Dialog(this);
customDialog.setContentView(R.layout.your_dialog_layout);

Window dialogWindow = customDialog.getWindow();
if (dialogWindow != null) {
    // Set overlay type to appear above other apps/activities
    dialogWindow.setType(WindowManager.LayoutParams.TYPE_APPLICATION_OVERLAY);
    // Add flags to ensure visibility even over locked screens or keyguards
    dialogWindow.addFlags(WindowManager.LayoutParams.FLAG_SHOW_WHEN_LOCKED);
    dialogWindow.addFlags(WindowManager.LayoutParams.FLAG_DISMISS_KEYGUARD);
    dialogWindow.addFlags(WindowManager.LayoutParams.FLAG_LAYOUT_IN_SCREEN);
}

customDialog.show();

Important: For Android 6.0 (API 23) and above, you'll need to request the SYSTEM_ALERT_WINDOW permission dynamically via the app settings, since it's classified as a special permission. You can prompt users to open the settings with this intent:

Intent overlayPermissionIntent = new Intent(Settings.ACTION_MANAGE_OVERLAY_PERMISSION,
        Uri.parse("package:" + getPackageName()));
startActivityForResult(overlayPermissionIntent, REQUEST_OVERLAY_PERMISSION);

2. Delay the ACTION_CALL Intent Until Dialog Interaction #

A more user-friendly and reliable approach is to only launch the dialer after the user interacts with your dialog. Instead of triggering the call immediately when the list item is clicked, first show your dialog, then start the ACTION_CALL intent when the user confirms (e.g., taps a "Call" button in the dialog):

// Inside your setList method, update the row click listener:
row.setOnClickListener(v -> {
    final String phoneNumber = tvNumber.getText().toString();
    
    // Initialize and show your custom dialog
    Dialog confirmDialog = new Dialog(YourActivity.this);
    confirmDialog.setContentView(R.layout.your_confirm_dialog);
    
    Button callButton = confirmDialog.findViewById(R.id.btn_call);
    Button cancelButton = confirmDialog.findViewById(R.id.btn_cancel);
    
    callButton.setOnClickListener(dialogBtn -> {
        // Launch dialer only after user confirms
        Intent callIntent = new Intent(Intent.ACTION_CALL);
        callIntent.setData(Uri.parse("tel:" + phoneNumber));
        startActivity(callIntent);
        confirmDialog.dismiss();
    });
    
    cancelButton.setOnClickListener(dialogBtn -> confirmDialog.dismiss());
    
    confirmDialog.show();
});

This way, your dialog stays visible until the user explicitly chooses to proceed with the call, eliminating the chance of it being covered by the dialer activity.

3. Verify Dialog Initialization Timing #

If you absolutely need the dialog to appear automatically before the call, make sure you're showing it before starting the ACTION_CALL intent, and add a small delay if necessary (though delays are not ideal, they can help in edge cases):

row.setOnClickListener(v -> {
    // Show dialog first
    showCustomDialog();
    
    // Add a short delay to ensure dialog is fully rendered before launching dialer
    new Handler(Looper.getMainLooper()).postDelayed(() -> {
        String phoneNumber = tvNumber.getText().toString();
        Intent callIntent = new Intent(Intent.ACTION_CALL);
        callIntent.setData(Uri.parse("tel:" + phoneNumber));
        startActivity(callIntent);
    }, 500); // Adjust delay as needed
});

The second solution (delaying the call until dialog interaction) is generally the best practice here—it's more intuitive for users and avoids permission complexities.

内容的提问来源于stack exchange，提问作者PeterB