App Limits
What AndroMate cannot do today, so you can plan around it.
Supported devices
| Limit | Detail |
|---|---|
| Brand | Samsung phones only. Xiaomi (HyperOS) and Google Pixel (native Android) are being adapted next. |
| Android version | Android 13 (API 33) or later, tested up to Android 16 (API 36) |
| Processor | ARM only. x86 emulators are not supported. |
Installation
- AndroMate is not on the Play Store yet. The install goes through an APK, and Google Play Protect may warn about it or block it. Turning Play Protect off may be required. See Installation.
- Device Owner mode needs a factory-reset phone with no account, and cannot be removed from the app: only another factory reset removes it. The installer runs on Windows only for now.
Permissions
The app needs the permissions listed during Device Registration. Tasks that drive the screen (the Android UI tasks) also need the AndroMate accessibility service to be enabled.
Executions
- One execution per device. A job launched on several devices creates independent executions.
- An execution that stays Pending or Running for more than 60 minutes (default) is marked timed out. The check runs every 15 minutes.
- Only timed out executions can be retried. A failed execution must be launched again.
- The device reads the workflow when it starts the execution: saving a workflow later does not change an execution already started.
- If the phone loses its connection at the end of a job, the result stays in Sync Entries on the phone until it is uploaded. See Menu and Settings.
API
- Requests need an API key with the right permission (for example
TRIGGERto launch a job). - A key is shown only once, when it is generated.
- A job and its devices must belong to the key's owner. See Run a Job.