Table of Contents

Screenshots and screen recordings: important ways to record AR visual anomalies

When using augmented reality (AR) applications, you may encounter visual experience issues such as model misalignment, content jitter, tracking loss, and occlusion anomalies. Because the quality of AR content depends heavily on the device, ambient lighting, and algorithm performance, these issues are often instantaneous and context-dependent. Vague text alone, such as "the model drifted away", cannot accurately convey the specific details of the issue. Therefore, promptly using screenshots or screen recordings to record anomalies is essential for subsequent issue diagnosis, technical reproduction, and user experience optimization.

Why screenshots and screen recordings are needed

When the behavior of an AR application does not match expectations, screenshots and screen recordings have the following key roles:

  • Accurately restore the issue scenario

    Screenshots can capture the exact moment when an anomaly occurs, such as a specific content jitter or model clipping issue, while screen recordings can fully record the entire process and environmental interaction that led to the anomaly.

  • Assist technical diagnosis by the development team

    By viewing the visual evidence you captured, technical support teams or developers can quickly locate the root cause, for example whether it is a device performance issue, SLAM tracking loss, or rendering pipeline error, avoiding tedious guessing and repeated questioning.

  • Preserve device environment information

    Screen recordings not only include the in-app image, but usually also include the system status bar of the device, such as time, battery level, and network signal. This is critical for diagnosing loading issues caused by device overheating and frequency throttling or network fluctuation.

Common operation methods on mobile devices

Before taking a screenshot or screen recording, make sure the AR scene has finished loading and the abnormal behavior is occurring or about to occur. Keep the device as stable as possible so that the image is clear and identifiable.

General operation principles

  • Screenshot: suitable for capturing static visual errors, such as content clipping or model misalignment. It is recommended to take multiple consecutive screenshots to cover different stages of the anomaly.
  • Screen recording: suitable for capturing dynamic behavior, such as image shaking caused by tracking loss or stuttering during interaction. It is recommended to keep the recording duration within 15-30 seconds and focus on the core process of the issue.

iOS devices (iPhone/iPad)

Screenshot:

  • Devices with FaceID: quickly press and release the Power button + Volume Up button at the same time.
  • Devices with a Home button: quickly press and release the Power button + Home button at the same time.
  • Screenshots are automatically saved to the Photos App .

Screen recording:

  1. Go to Settings > Control Center > More Controls, and add "Screen Recording".
  2. Swipe down from the upper-right corner of the screen to open Control Center.
  3. Tap the screen recording button to start recording; tap the stop button to stop recording.
  4. To record system sound or microphone audio, press and hold the screen recording button to configure it.
  5. Recorded videos are saved in the Photos App .
Note
  • When recording the screen, make sure Settings > Control Center > Access Within Apps is enabled.
  • Screen recording may reduce the effect due to performance limitations. It is recommended to record as soon as possible after reproducing the issue and avoid long running that affects the result.

Android devices (mainstream brands as examples)

Screenshot:

  • General method: quickly press and release the Power button + Volume Down button at the same time.
  • Some manufacturers support gesture screenshots, such as three-finger swipe down, or smart assistant shortcuts.
  • Screenshots are automatically saved in "Gallery > Screenshots".

Screen recording:

  • Native Android (Android 11 and later):
  1. Pull down the notification shade and find the "Screen Record" shortcut icon. If it is not available, add it in "Edit".
  2. Tap to start recording. You can choose whether to include microphone audio.
  3. Tap the recording icon in the upper-left corner of the screen again to stop recording.
  4. Recorded videos are saved in "Gallery > Movies".
  • Manufacturer-customized systems, such as Samsung One UI, HyperOS, ColorOS, and OriginOS:
  1. A screen recording entry is usually provided in the quick panel. If it is not available, tap the plus sign to add it.
  2. Tap to start recording.
  3. Tap the stop button at the top of the screen, which may vary by manufacturer, to stop recording.
  4. Recorded videos are saved in "Gallery > Screen recordings".
Tip

Specific path examples:

  • Samsung: swipe down from the top shade > Screen recorder
  • Xiaomi/Redmi: pull down the notification shade > Screen recording
  • OPPO/Realme: swipe down from the top notification bar or pull-down menu bar > Screen recording
  • VIVO/iQOO: swipe down from the upper-right of the screen (older models swipe up from the bottom) > Super Screenshot > Record screen
  • Huawei: swipe down from the upper-right of the screen > Screen recording
  • HONOR: swipe down from the status bar to open the notification panel, continue swiping down to expand the full notification panel > Screen recording
Note
  • Some Android devices may restrict background screen recording permissions when running high-load AR applications. Before recording, make sure power saving mode is turned off and the necessary permissions are granted.
  • Screen recording may reduce the effect due to performance limitations. It is recommended to record as soon as possible after reproducing the issue and avoid long running that affects the result.

Best practice recommendations

By mastering the operations above, you can capture key evidence as soon as an anomaly occurs in the AR experience, significantly improving issue communication and resolution efficiency. When submitting a technical support request, it is recommended to provide screenshots/screen recordings, device model, operating system version, EasyAR SDK version, and AR application logs together to build a complete troubleshooting context.

For log collection methods, refer to: