Hey there, let's tackle this PiP black block and residual frame issue you're facing with ExoPlayer and Fragments. I've debugged similar quirks before, so here are targeted, actionable fixes to resolve the problem:

1. Fully Release ExoPlayer Resources for Inactive Fragments #

The residual frames from the closed player suggest its instance isn't being properly cleaned up. Make sure you destroy the ExoPlayer instance and clear references when its Fragment is destroyed:

Kotlin Example: #

override fun onDestroyView() {
    super.onDestroyView()
    player?.apply {
        stop()
        release() // Critical to free up surface and memory
    }
    player = null
    playerView?.player = null // Break the view-player binding
}

Java Example: #

@Override
public void onDestroyView() {
    super.onDestroyView();
    if (player != null) {
        player.stop();
        player.release();
        player = null;
    }
    if (playerView != null) {
        playerView.setPlayer(null);
    }
}

This ensures the inactive player's surface is completely freed, preventing its frames from leaking into the PiP snapshot.

2. Optimize PiP Snapshot by Hiding Inactive Views #

Android generates PiP windows from a view snapshot—if other fragments/views are still visible (even off-screen), they can cause black blocks or residual content. Update your Activity to hide non-active player fragments when entering PiP:

override fun onPictureInPictureModeChanged(isInPiP: Boolean, newConfig: Configuration) {
    super.onPictureInPictureModeChanged(isInPiP, newConfig)
    
    // Hide all other player fragments when in PiP
    supportFragmentManager.fragments.forEach { fragment ->
        if (fragment is NonPiPPlayerFragment && fragment != currentActivePlayerFragment) {
            fragment.view?.visibility = if (isInPiP) View.GONE else View.VISIBLE
        }
    }
}

For Java, the logic is identical—loop through fragments and toggle visibility based on PiP state.

3. Adjust ExoPlayer Surface & Layout for PiP Compatibility #

Your player uses MATCH_PARENT layout, but SurfaceView can sometimes have sizing quirks in PiP mode. Try these tweaks:

• Switch to TextureView: Update your PlayerView to use TextureView instead of SurfaceView by adding this attribute to your layout:

  app:use_texture_view="true"
  

  TextureView is more flexible for dynamic sizing like PiP.
• Force Player Aspect Ratio Match: Ensure ExoPlayer scales to your 16:9 PiP ratio. Add this to your player setup:

  playerView.setResizeMode(AspectRatioFrameLayout.RESIZE_MODE_FIT)
  

  This ensures the player fills the PiP window without leaving black bars or extra space.

4. Validate Activity PiP Configuration & Snapshot Behavior #

Double-check your Activity's manifest settings and PiP initialization:

• Ensure you're explicitly setting the 16:9 aspect ratio when entering PiP:

  val pipParams = PictureInPictureParams.Builder()
      .setAspectRatio(Rational(16, 9))
      .build()
  enterPictureInPictureMode(pipParams)
  

• Avoid overlapping views: Make sure no other UI elements (like toolbars, status bars) are included in the player's view hierarchy when entering PiP. You can temporarily hide these views before triggering PiP.

5. Update ExoPlayer (If Possible) #

While you're on version 2.11.0, newer ExoPlayer releases include fixes for PiP surface management and snapshot issues. If your project allows, upgrading to a more recent stable version (e.g., 2.X.X) might resolve the problem out of the box.

Start with steps 1 and 2 first—those are the most common fixes for residual frames and black blocks in PiP setups with multiple player fragments. If the issue persists, move to adjusting the SurfaceView/TextureView and aspect ratio settings.

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