SYSTEM ONLINE ZYGISK · REZYGISK · KPATCH · A16-A17
← Back to use cases

Test Android Apps on Different OS Versions

Use this checklist for OS compatibility, not for generic multi-device coverage. For the complete API-level guide, continue to Testing Android Apps Across OS Versions.

Real OS behavior

Run critical scenarios on every real Android version you support. Check API availability, permissions, background execution, notifications, storage, WebView, media, and any feature that relies on platform services. Record the actual OS build and device firmware; changing a profile label cannot validate these behaviors.

Profile-based checks

Use profiles separately to test what an app does with different build fields, identifiers, model values, or network context. These runs are useful for app logic, but they do not prove compatibility with another Android release. Keep the two result categories separate in the release report.

Compatibility evidence to save

  1. App version and the scenario inputs used for the run.
  2. Real Android version, device model, and firmware or emulator image.
  3. Profile name and changed values for profile-based checks.
  4. Expected result, actual result, logs, and screenshots for failures.

Related guides

Android 17 compatibility · Compatibility matrix · Physical versus profile device matrix