Android Enterprise device testing

The devices listed below have been tested against a current, Android Enterprise-compatible Enterprise Mobility Management (EMM) platform for one or more of the following:

• Android Enterprise work profile
• Android Enterprise fully managed (work-managed)
• Android Enterprise work profile on a fully managed device (COPE/COMP)
• Android Enterprise dedicated (COSU or kiosk)
• Multiple provisioning methods, including zero-touch enrolment

Advanced testing

The following devices have undergone advanced testing. Introduced in June 2019, advanced testing follows the same process as standard testing, but each individual restriction/function is documented and verified irrespective of outcome across at least two EMMs.

A report containing 700+ touch points is provided to the OEM on completion along with any recommendations.

• Google Pixel 3a Android Enterprise validation report
• Moto G7 Power Android Enterprise validation report
• Sony Xperia L3 Android Enterprise validation report

Standard testing

The following devices have undergone standard testing. Standard testing involves the same process as advanced testing, but without in-depth documentation and additional verification across multiple EMMs.

For each of these use-cases, the device will be provided a pass (), a warning ( / ), a fail () or untested (), along with the party who verified the functionality (as some information may be externally sourced). The OS version (if) listed is valid at the time of testing. It’s normally safe to assume newer OS versions will support at a minimum the below tested functionality.

BQ

Aquaris X2 Pro

Tested August 2018, build 1.3.0

CAT

CAT S61

Tested Feb 2019, build LTE_D0201121.0_S61_0.053.02

Notes: On NFC and QR provisioning, the device passcode is not enforceable via multiple EMM solutions. In COPE, system applications aren’t disabled in the parent profile despite this being set.

Google

Google Nexus 5x

Tested 2017

Notes: With older EMM agent versions, NFC provisioning is broken against MobileIron and AirWatch as the WiFi payload is not correctly interpreted by the Nexus. Ensure you are using the latest available agents to avoid this issue.

Google Pixel 2

Tested 2018

Huawei

Huawei MediaPad M5 (8.0)

Tested June 2018, build 8.0.0.151

Notes: Due to the amount of T&C pages, zero-touch provisioning is anything but. Huawei include non-mandatory system applications (the Microsoft Suite) in the fully managed environment, which should not be done. Builds prior to 8.0.0.151 had provisioning issues.

Huawei P10

Tested 2017

Notes: NFC provisioning is interrupted by the First Run Wizard, prompting for a Google account, WiFi information and more, before eventually landing on the home screen. The DPC agent does not automatically launch, and DPC extras are not passed to the agent. It does then work as expected. DPCi enrolment fails with MobileIron, as the device is not recognised as a fully managed device by the DPC. QR provisioning is not supported.

Motorola

Motorola Moto Z

Tested 2017

Notes: In a work profile deployment it is possible to access and manipulate data on an SD card. This is again an OEM issue to be rectified.

Motorola Moto Z Play

Tested 2017

Notes: NFC provisioning is interrupted by the First Run Wizard, prompting for a Google account, WiFi information and more, before eventually landing on the home screen and launching the DPC directly after. NFC provisioning appears to be partially broken.

Motorola Moto C Plus

Tested 2017

Notes: As part of enrolment, the device is prompted to encrypt. From Nougat (7.0) encryption should be default and this is therefore unexpected. Encryption may take some time. Interruptions from the Wizard during both QR and DPCi enrolment. DCP doesn’t automatically launch following QR provisioning, but DPC extras are successfully passed through. There is no NFC radio, and so no NFC provisioning.

Motorola Moto E4 Plus

Tested 2017

Notes: As part of enrolment, the device is prompted to encrypt. From Nougat (7.0) encryption should be default and this is therefore unexpected. Encryption may take some time.

Motorola Moto G5

Tested 2017

Notes: While undertaking wireless (AFW#) provisioning the DPC temporarily stalled while requesting a newer version of Google Play Services. GPS is pushed from EMM as a managed work app and updated automatically after a few minutes. Eventual enrolment was not prevented.

Motorola Moto G4 Play (XT1604)

Tested 2017

Notes: While undertaking wireless (AFW#) provisioning the DPC failed to apply the managed Android Enterprise account due to an outdated version of Google Play Services. No further tests were performed. Not all variants of this device carry NFC, therefore success with NFC provisioning cannot be guaranteed.

Nokia

Nokia 1

Oreo Go edition, tested on release 2018

Notes: This device is not Android enterprise supported and is not designed to be as it primarily targets emerging markets, there are more appropriate enterprise-supported devices available from Nokia below.

Nokia 2

Tested on release 2018

Notes: There is no NFC radio on the Nokia 2. The device is not encrypted out of the box for performance reasons, requiring this is completed each time the device is provisioned. With only 8GB onboard storage and 1GB RAM, this device has limited suitability in an enterprise environment and outside of a BYOD context, there are more appropriate enterprise-supported devices available from Nokia below.

Nokia 3

Tested March 2018, build 00WW_3_250

Notes: Ensure the device is on the latest available Android version prior to provisioning! Earliest 7.x builds hard-failed during fully managed provisioning and therefore offered no fully managed capabilities. All functionality is confirmed supported as of Android 7.1.1.

Nokia 3.1

Tested Nov 2018, build 00WW_0_46E_SP02

Nokia 3.2

Tested May 2019, build 00EEA_1_03D

Notes: Fingerprint sensor is available on the 32GB variant.

Nokia 4.2

Tested May 2019, build 00EEA_1_17I

Notes: A prompt to enable face unlock is occasionally seen after provisioning.

Nokia 5

Tested March 2018, build 00WW_5_22A_SP01

Notes: In some cases after provisioning via NFC, the DPC doesn’t reliably auto-launch meaning it’ll need to be opened from the app drawer manually. Ensure all software updates are applied before provisioning as this is rectified

Nokia 5.1

Tested Nov 2018, build 00WW_0_38E_SP03

Nokia 6

Tested June 2018, build 00WW_5_600_SP01

Notes: Ensure the device is fully updated! Earlier Nougat versions had some issues. Once updated all provisioning methods work as expected.

Nokia 6.1

Android One – Tested March 2018

Notes: This is an Android One device, offering stock Android and extremely fast online (A/B partitioning) updates.

Nokia 7.1

Android One – Tested December 2018

Nokia 7 Plus

Android One – Tested March 2018

Nokia 8

Tested March 2018

Notes: A prompt to join the Nokia improvement program will pop up after provisioning. This can be declined. The 8 series is the first to support Android zero-touch enrolment.

Nokia 8.1

Successor to the 7 Plus, not the 8. Tested Jan 2019, build 00WW_2_47A

Nokia 8 Sirocco

Android One – Tested March 2018

Notes: This is an Android One device, offering stock Android and extremely fast online (A/B partitioning) updates.

Nokia 9 Pureview

Tested May 2019, build 00WW_4_22C

Notes: Fingerprint sensor can be unreliable.

OnePlus

OnePlus 6T

Tested November 2018, build ONEPLUS A6013_41_181024 

Notes: This device has an in-depth, public report documented here.

Pocophone

Pocophone F1

Tested November 2018, build OPM1.171019.026

Notes: An in-depth report on this device can be found here.

Samsung

Samsung Galaxy Note 8

Dual N950FD, tested 2018

Notes: Following completion of provisioning, the user is presented with a number of agreements to accept, only the top two are mandatory and others can be skipped. For those searching for zero-touch compatibility, Samsung will not support it for the foreseeable future. As of Android 8.0, Samsung switches from the unified work profile to Workspace. The UX is similar but different. Additionally, when provisioning managed work profile in MobileIron (COPE), the settings app crashes whilst setting a passcode and can not be recovered.

Sony

Sony Xperia 10

I3113, tested March 2019, build 53.0.A.4.74

Notes: Will prompt a signup request from Swiftkey, the default keyboard on this device. Request should be declined. During DPCi and ZT enrolment, a Google services prompt is shown.

Sony Xperia L1

Dual G3312, tested 2017

Notes: After initiating provisioning via NFC, the L1 reverts back to the setup wizard, requiring the user to go through device setup entirely before the DPC launches. With AFW# provisioning, the wizard interjects to prompt for passcode and Xperia account setup before completing. In both cases fully managed mode is functional following this. Other things to note include a prompt for app recommendations when opening the app drawer and a signup request from Swiftkey, the default keyboard on this device. Both requests should be declined.

Sony Xperia L3

I3312, build 54.0.A.3.94, tested March 2019

Notes: Will prompt a signup request from Swiftkey, the default keyboard on this device. Request should be declined.

Sony Xperia XA1

Dual G3121, tested 2017

Notes: After initiating provisioning via NFC, the XA1 reverts back to the setup wizard, requiring the user to go through device setup entirely before the DPC launches. With AFW# provisioning, the wizard interjects to prompt for passcode and Xperia account setup before completing. In both cases fully managed mode is functional following this. Other things to note include a prompt for app recommendations when opening the app drawer and a signup request from Swiftkey, the default keyboard on this device. Both requests should be declined.

Sony Xperia XA2

Tested 2018

Notes: Will prompt a signup request from Swiftkey, the default keyboard on this device. Request should be declined.

Sony Xperia XZ Premium

Dual G8142, tested 2017

Notes: Ensure the device is fully up to date! Android 8.0 fully supports all provisioning methods while 7.1.1 failed to correctly provision via NFC. Will prompt a signup request from Swiftkey, the default keyboard on this device. Request should be declined.

Sony Xperia XZ1

G8341, tested 2017

Notes: The XZ series is the first to support Android zero-touch enrolment. Will prompt a signup request from Swiftkey, the default keyboard on this device. Request should be declined.

Sony Xperia XZ1 Compact

Tested 2018

Notes: The XZ series is the first to support Android zero-touch enrolment. Will prompt a signup request from Swiftkey, the default keyboard on this device. Request should be declined.

Sony Xperia XZ2

Tested June 2018, build 51.1.A.4.173

Notes: Will prompt a signup request from Swiftkey, the default keyboard on this device. Request should be declined.

Sony Xperia XZ3

Tested January 2019, build 52.0.A.3.163

Notes: Will prompt a signup request from Swiftkey, the default keyboard on this device. Request should be declined. During DPCi and ZT enrolment, a Google services prompt is shown.

Wileyfox

Wileyfox Swift 2 X

Tested 2017

Notes: Wileyfox use a non-standard Phone application – “truecaller” – which prompts a registration request during setup (this can and should be skipped). Recommend to disable this and distribute an alternative dialler via Managed Google Play.

Xiaomi

Xiaomi Mi A1

Android One, tested 2017

Notes: There is no NFC radio on the device, therefore NFC provisioning is not possible. This is an Android One device, offering stock Android and extremely fast online (A/B partitioning) updates.

Zebra

Zebra TC25

Tested 2018

Notes: There is no NFC radio on the device, therefore NFC provisioning is not possible.

Zebra TC56

Tested 2018

Notes: Previously tested on Android 6.x, where DPCi provisioning failed and QR provisioning wasn’t supported. Updating to 7.1.2 resolved both of these issues.