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

Test Android Apps on Multiple Device Profiles From One Phone

Build a repeatable profile matrix on one real phone. This page covers profile-based scenarios; use the physical device matrix for real OS, firmware, and hardware differences.

Build a profile matrix

  1. Save an unchanged baseline profile and record the real phone and Android version.
  2. Add only the profiles required by your test goals, with complete and internally consistent values.
  3. Assign one short scenario to each profile and keep the app build, account state, and inputs unchanged.
  4. Record the profile, changed fields, expected result, actual result, and evidence for every run.

Example matrix

RunChanged valuePurpose
BaselineNoneConfirm the starting scenario
Second modelModel and matching build fieldsCheck model-dependent app logic
New identifiersAndroid ID and related identifiersCheck account and identifier behavior
Network profileNetwork and location contextCheck context-dependent flows

When one real phone is not enough

Move to physical devices, emulators, or a device farm for real OS versions, firmware, WebView, camera, sensors, and OEM behavior. Keep those results separate from profile checks instead of claiming full device coverage.

Related guides

Apply and verify one profile · Test without a device farm · Debug inconsistent profile results

Profiles are explained on the device simulation page, and Android testing covers the test environment. The software page has the Device Changer downloads. Downloading needs a free account and login, and using Device Changer's features needs a license.

Start testing