POCO F1 Android Enterprise validation report

Model: POCOPHONE F1 M1805E10A (6GB RAM, 128GB storage)
Acquired: Early November
OS: Android 8.1.0 Oreo (MIUI 10.0.4.0)
Build: OPM1.171019.026
Security: 1 October 2018

This device has been tested against the public validation process, and the following mix of (non-exhaustive) issues and recommendations have been noted:

Upon attempting to complete EMM token (DPC identifier) provisioning, the device fails to complete and returns to an earlier point in the setup wizard.

This will continue until the device is factory reset via recovery (power + vol up on this device).

No fully managed (work-managed) provisioning methods are supported on the POCO F1.

There is no NFC radio on the device, thus not supported.

Does not initiate.

Fails to provision, results in a loop which cannot be escaped without a factory reset via recovery (see 1.1)

This provisioning method is not supported

Despite EMM token provisioning failing, when provisioning fully managed (work-managed) with a managed Google account, the device brings down the Google DPC without issue, however the setup wizard continues to interject throughout this process, which it should not do.

A. The policy to enforce encryption at boot (requiring a passcode to turn on the device) is not enforced, and has to be set manually.

A. Work widgets are not available

B. Deployed VPN connection requests credentials storage password, after which the VPN app crashes if a password is input, or continues to prompt if cancelled

C. No work app folder is created on the home screen

D. Work applications show placeholder icons:

### 3.3. Fully managed with work profile

Unable to test due to provisioning issues.

Unable to test due to provisioning issues.

Based on the findings above, it is not recommended to use the Pocophone F1 in the enterprise.

As a fully managed device, it was only possible to provision it in this way via managed Google accounts, rather than the more popular and easier to implement managed Google Play accounts; without NFC, QR and EMM token provisioning methods available (the latter actively causing a loop) the device is basically unsuitable, even if it does enforce almost all of the limited number of restrictions offered by G Suite.

As a BYO device it behaved far better, however basic expectations such correct app icons and a work folder created on the home screen let it down. Furthermore, limited VPN testing highlighted a potential issue with certificate authentication.