Supported OS
Android version support
Artifact support by Android version. A cell is marked validated only on a version Loadout has actually passed the Gate A read-back and a real forensic parse (ALEAPP) against. The remaining versions are in active validation through a scheduled OS conformance run.
Android support matrix
| Android | Contacts | Call logs | Photos | Video | SMS | MMS |
|---|---|---|---|---|---|---|
| 17API 37 | Planned | Planned | Planned | Planned | Planned | Planned |
| 16API 36 | Validated | Validated | Validated | In validation | Validated | Validated |
| 15API 35 | Validated | Validated | Validated | Validated | Validated | Validated |
| 14API 34 | Validated | Validated | Validated | In validation | Validated | Validated |
| 13API 33 | Validated | Validated | Validated | Validated | Validated | Validated |
| 12API 31 | Validated | Validated | Validated | In validation | Validated | Validated |
| 11API 30 | Validated | Validated | Validated | In validation | Validated | Validated |
| 10API 29 | Validated | Validated | Validated | Validated | Validated | Validated |
Notes
"Validated" means Loadout injected a persona on that Android version, read every artifact back through the on-device content providers, and diffed it against the ground-truth manifest with zero failures. On the reference build (Android 15) the injected data is additionally confirmed to parse in a real open-source forensic tool (ALEAPP), for both the rooted and the fielded on-device-app injection paths. "In validation" means the same method applies and the version is in the scheduled conformance matrix, not yet confirmed. "Not yet" means the matrix found that artifact failing on that version. "Planned" means the version has no public emulator image to validate against yet.
The five core artifact types (contacts, call logs, photos, SMS, and MMS) are written by the on-device companion app (the path used on lab devices) and verified field by field on Android 10 through 16. This conformance matrix re-runs weekly in CI for the six versions whose emulator images boot on cloud runners (Android 10, 11, 12, 14, 15, and 16), so support is maintained, not asserted once. Video, newly added, shares the same MediaStore path as photos and is confirmed on Android 10, 13, and 15, with the remaining versions in validation as it is added to the scheduled matrix. On Android 15, ALEAPP (a free proxy for the parsers in MSAB XRY and Magnet GrayKey) independently surfaces every injected type, including video, from the app-injected device. Android 13 was validated on a local emulator (the full provision, field-level read-back, and clean removal all pass) because its image will not boot on our cloud CI runners (an infrastructure limitation, not a device one). Android 17 is in developer preview with no public emulator image yet, so it is marked planned.
iOS support is under evaluation and is not represented here. See the roadmap. Validation evidence and the conformance reports are described on the Security and Compliance page, and available on request: dayel.ostraco@accelerasolutions.com.
Last reviewed: