capturing-screenshots-and-screenrecord

To capture a binary-clean Android screenshot, use `adb exec-out screencap -p` instead of `adb shell` to stream the PNG data directly and avoid binary corruption. This method ensures the resulting image file is encoded correctly for CI artifacts and golden-image workflows.

You can automatically capture screenshots and logcat dumps on test failure by implementing a JUnit4 `TestWatcher` rule. This capture-on-failure pattern triggers `adb exec-out screencap -p` and `logcat -d` commands simultaneously when a test fails, providing targeted visual and textual evidence for triage.

The maximum recording time for `adb shell screenrecord` is 180 seconds. You can use the `--time-limit` flag to bound the recording duration, along with other practical flags like `--size`, `--bit-rate`, `--rotate`, and `--bugreport` for generating MP4 clips.

Broken PNG files typically occur because `adb shell screencap -p` introduces carriage returns that corrupt the binary stream. Using `adb exec-out screencap -p` prevents this issue by ensuring a binary-clean stream, which is required for reliable PNG encoding in CI environments.

Yes, `adb screenrecord` works with scoped storage by using scoped-storage aware output paths for saving the MP4 files. It also requires reliable shutdown behavior to ensure the recording stops correctly and the file is properly finalized before retrieval.

Yes, you can record video of flaky instrumentation tests using `adb shell screenrecord` with a 180s time limit. Pairing this MP4 recording with a logcat dump and a final PNG screenshot allows for fast root-cause analysis and golden image generation during CI failures.