setPictureInPicture

Tell the SDK whether the content player is in picture-in-picture.

You normally do not need to call this. The Android runtime's OverlayAdRenderer resolves the Activity from the Context it was built with, or from the overlay's own view tree, and watches it — so a transition is picked up on its own, including one the VIEWER started with the system button or the swipe-home gesture, which no app-level callback would tell you about either. Web and iOS have always detected picture-in-picture themselves; this closes the gap on Android.

Call it only when the SDK reports DA-PIP-AUTODETECT-UNAVAILABLE, which means no Activity could be reached either way (an application Context under an overlay that hangs under no Activity, or a host that is not an Activity). Then forward Activity.onPictureInPictureModeChanged(isInPictureInPictureMode, ...) here, and once at startup if the app can be launched straight into picture-in-picture.

While active, every break plays as BreakFormat.SINGLE: one fullscreen ad, no companion, content paused, and on live the usual single-break latency restore on resume. The declared format still reaches diagnostics via DA-PIP-FORMAT-OVERRIDE; the public events report what actually plays.

Idempotent — repeated calls with the same value are ignored. So a host that forwards the lifecycle callback anyway costs nothing: whichever path sees the change first wins and the other is a no-op.