Why do only some Android pages turn black when mirrored?

Distinguish protected windows, single-app sharing and stopped MediaProjection sessions before treating every black screen as a connection failure.

If your phone's home screen mirrors correctly but one app page turns black, that alone does not prove the device disconnected. First distinguish protected content, single-app sharing and a stopped capture session from transport or decoding trouble. Reconnecting repeatedly may not address those causes.

This guide is based on Android documentation checked on September 13, 2026. It is not a device test or a description of a particular mirroring product. MediaProjection rules apply to that capture mechanism; do not assume every USB, debugging or customized-system solution behaves the same way.

Start with what turns black

On a device you are authorized to use, compare a harmless ordinary page with the affected page, then return to the first page. Note whether the entire image or only part of it disappears, and whether it recovers.

This narrows the problem. It does not identify a particular protection mechanism by itself.

Some windows intentionally block capture

Android's FLAG_SECURE lets an app prevent a window from being captured in screenshots or shown on a non-secure display. Official guidance describes blank screenshots of protected content. A working connection and an uncapturable page can therefore coexist. Android sensitive-window protection

Do not promise that another mirroring tool will reveal it. For passwords, payments or other sensitive tasks, let the device owner act on the phone. Where appropriate, use the app's supported sharing or export feature rather than disabling protection.

Did you share one app or the whole screen?

Single-app screen sharing on Android 14 QPR2 lets users select one app window. System elements such as the status bar, navigation bar and notifications are excluded. Android app screen sharing

If you expected to see a notification panel or another app, first check the scope selected during consent. Missing content outside that scope is not necessarily a dropped frame. Switch to supported full-screen sharing only when necessary and after considering what else it could expose. Controls vary between tools and systems.

A locked screen can mean the session ended

For the MediaProjection scenario described in Android's documentation, devices running Android 15 QPR1 or later automatically stop projection when locked. Users can also end sharing through the status-bar indicator. This does not establish a universal rule for every Android 15 screen-off event and every capture technology. Android 15 behavior changes

Unlock the phone and check whether the tool needs a fresh capture authorization; do not assume unlocking revives the old session.

Developers should inspect MediaProjection.Callback.onStop(). It signals an invalidated session: release its resources and update the interface. Starting another capture session can also stop the existing one. MediaProjection callback reference

When should you investigate the connection?

If ordinary pages remain black, or the mirrored image freezes while the phone continues changing, app protection alone is not a sufficient explanation. A useful support note includes:

  • Phone model, complete Android version and mirroring-tool version.
  • Capture mechanism, or “unknown.”
  • Whether you switched apps, locked the phone, ended sharing or opened another recorder.
  • Whether an ordinary page recovers, and whether the output is black or an old frozen frame.
  • The incident time and displayed error, with private content and identifiers removed.

For a separate explanation of network measurements, see RTT versus visible response delay. A good network number does not establish that capture is active.

Check content restrictions, sharing scope and session validity first. Then decide whether to renew consent, let the owner finish on the phone, or investigate transport.

参考来源