What is Android Enterprise?
For information regarding Android Enterprise, including what it is, the deployment scenarios stated below and how it can benefit organisations, have a read of What is Android Enterprise and why is it used?
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 work-managed
- Android Enterprise fully managed work profile (COPE/COMP)
- Android Enterprise Corporate Owned Single Use (COSU) or “kiosk”
- Android Enterprise zero-touch
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 listed is valid at the time of testing. It’s safe to assume newer OS versions will support at a minimum the below tested functionality.
OEM or reseller?
I welcome additional devices for testing! If you’re an OEM or reseller of Android devices, you can join Sony, Nokia and others in lending me anything from Android 6.0.1 or later to independently test. This is a free service, devices can be returned within a week or so. Use my contact page to get in touch or email me directly.
For more information on what’s involved in testing, please head to: Android Enterprise independent validation process and information.
BQ
Aquaris X2 Pro
Tested August 2018, build 1.3.0
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 work-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 work-managed device by the DPC. QR provisioning is not supported.
Motorola
Motorola Moto Z
Tested 2017
Notes: In a Kiosk deployment it is possible to access system settings via WiFi/Bluetooth/etc due to Motorola not locking this down. Additionally, 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 work-managed provisioning and therefore offered no work-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 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
Notes: A current bug results in a device crash when adding a fingerprint, everything works as normal once the device reboots.
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 Plus
Android One – Tested March 2018
Notes: This is an Android One device, offering stock Android and extremely fast online (A/B partitioning) updates.
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 Sirocco
Android One – Tested March 2018
Notes: This is an Android One device, offering stock Android and extremely fast online (A/B partitioning) updates.
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 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 work-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 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 work-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.
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.
Interesting topic! But Google really need to focus on fixing the issues with Android 7.1 devices. For the better success should really need to offer Android Enterprise only for > Android 8.0 devices only ? as an BYOD managers we are facing various AE compatible device but not all devices are really not eligible. Google should really open an exclusive corporate Android Enterprise support contracts
Can you elaborate? I’ve covered a lot of 7.x+ devices which behave as I’d expect and generally recommend 7.x+ (rather than 6.x or lower) because of it.
On 1. the option is certainly there to allow for one universal passcode, however:
So arguably it’s not ideal, and is addressed in Android P, but equally it’ll enforce a passcode that’s compliant with company policy that will take precedence if required.
On 2. Chinese phones normally aren’t GMS certified and likely won’t have the necessary APIs to correctly run Android enterprise solutions adequately. If they are, it’s on the OEM to fix any issues they have.
Hello, I am new.
and I face a problem about zero-touch
My phone is Sony xperia XZ
I load default, and in welcome page it ask me to click 3 times to get QR scanner and need QR code.
I don’t know where to get the code.
Could help to guide how to do in next, or where I can to get some help.
You’ll need to connect an EMM to G Suite as Google Apps (the legacy free version I also use) doesn’t have proper Android management built in (thanks Google).
Once you have an EMM which supports the QR code then you’ll be able to get the QR code from that vendor. MobileIron do their provisioner app for QR generation, Workspace One UEM generates them in-console, so on.
very thanks
I don’t order this function (EMM), so I don’t know how to add EMM 3rd part and use mobileiron.
find a app from mobileiron “provisioner”
and try to typing and scan qr from my phone
scan qr done, and downloads mobileiron admin app from internet, then ask
me to provide username and password.
Try all I have accounts, but it doesnt accept and can’t go in next step.
Does It must do on android cloud from PC browser or have other way ?
You need a valid MobileIron tenant or installation to use the provisioner with it. Without a valid EMM there’s no Android management in the free G Suite version, good opportunity to start looking for one!
I upgrade G suit to enterprise(evaluation), and make a token.
Register mobileiron free 30 days, but it doesn’t any response.
Use above register email and can’t login to mobileiron cloud.
Do I lost any step ?
I’m normal user, maybe I turn on or install a app to active this function.
For now, I would like to find a solution to disable and use this phone normally.
Could help to provide the QR code, let me scan and active my phone, then
remove this account to disable this feature?