Android Enterprise Recommended requirements

Minimum OS version

Android 16.0

Speed

1.4 GHz

Architecture

64 bit

Memory

6 GB RAM REQUIRED. The device MUST NOT be marked as a low RAM device.

flash

32 GB

Encryption

The device MUST be encrypted by default. The encryption algorithm implemented SHOULD be BoringSSL, which is the AOSP default.

Cameras

If the device contains front or rear-facing cameras, they MUST be a minimum resolution of 2 MP and 8 MP, respectively.

Speed

1.4 GHz

Architecture

64 bit

Memory

3 GB RAM (4 GB RAM recommended). The device MUST NOT be marked as a low RAM device.

flash

16 GB (32 GB recommended)

Encryption

The device MUST be encrypted by default. The encryption algorithm implemented SHOULD be BoringSSL, which is the AOSP default.

Ingress protection

IP 54 certified

Drop test integrity

MIL-STD-810G or IEC 60068-2-31:2008

Cameras

If the device contains front or rear-facing cameras, they MUST be a minimum resolution of 2 MP and 8 MP, respectively.

Provisioning flows

Device setup flows MUST comply with the UX Guidelines.

Approved branding

Google MUST review and approve all enterprise branding, including assets and strings, for consistency with the Android brand. Devices using the AOSP assets and strings are exempt from review.

Security update support

For device security updates:

• Device manufacturers MUST publish the following security update information on the device manufacturer website and link the published information to Google`s security bulletins.

○ SMR support end date (that is, the last month and year the device is guaranteed to receive security updates).

○ Fixes contained in the security patch, with any included OEM-specific fixes.

For an example of published security update information, go to Sample Security Patch Support.

• Device manufacturers MUST publish the frequency of security updates the device will receive (for example, every 30 days, every 90 days).

Emergency Security Maintenance Releases (ESMRs)

Device manufacturers MUST support the ESMR process until the SMR support end date. For details on the ESMR process, refer to

Emergency Security Maintenance Release (ESMR).

Vulnerability Rewards Program (VRP)

Device manufacturers SHOULD operate and maintain a VRP with Bug Bounty and link it to Google`s VRP site. For details on VRPs, refer to

Android Security Rewards Program Rules.

Global System for Mobile Communications Association (GSMA) Certification

Device manufacturers SHOULD submit devices for certification with the GSMA Mobile Device Security Certification (MDSCert) at Level 2 (third-party validation) or higher.

Major OS update support

• Devices MUST support +1 OS version update from the OS version on which the device is AER validated. Devices SHOULD support +7 OS version upgrades from the version on which the device is AER validated.

• Device manufacturers MUST publish information about the guaranteed Android OS version upgrades that the AER device will receive. For an example of published OS upgrade support information, see Sample Security Patch Support.

Revalidation

A version update MUST comply with all the AER requirements for that release to maintain the device`s AER status. Exceptions for Android 16 revalidation include the following:

• Minimum hardware requirements

• OS update support

OEMConfig

OEMConfig apps allow IT admins to set custom policies created by device manufacturers (OEMs). This work removes the necessity for Enterprise Mobility Management vendors (EMMs) to customize each device feature. For details, go to Creating OEMConfig Apps.

Device manufacturers MAY support custom enterprise APIs specific to their devices. Manufacturers that support custom enterprise APIs such as custom device policies MUST comply with all CDD and GMS requirements.

These custom enterprise APIs MUST be managed using an OEMConfig app.

Minimum OS version

Android 15.0

Speed

1.4 GHz

Architecture

64 bit

Memory

3 GB (6 GB RAM STRONGLY RECOMMENDED). The device MUST NOT be marked as a LOW-RAM device.

flash

32 GB

Cameras

If the device contains front or rear-facing cameras, they MUST be a minimum resolution of 2 MP and 8 MP, respectively.

Speed

1.4 GHz

Architecture

64 bit

Memory

3 GB RAM (4 GB RAM recommended). The device MUST NOT be marked as a LOW-RAM device.

flash

16 GB (32 GB recommended)

Ingress protection

IP 54 certified

Drop test integrity

MIL-STD-810G or IEC 60068-2-31:2008

Cameras

If the device contains front or rear-facing cameras, they MUST be a minimum resolution of 2 MP and 8 MP, respectively.

Provisioning flows

Device setup flows MUST comply with the UX Guidelines.

Approved branding

Google MUST review and approve all enterprise branding, including assets and strings, for consistency with the Android brand. Devices using the AOSP assets and strings are exempt from review.

Security update support

For device security updates:

• Device manufacturers MUST publish the following security update information on the device manufacturer website and link the published information to Google`s security bulletins.

○ SMR support end date (that is, the last month and year the device is guaranteed to receive security updates).

○ Fixes contained in the security patch, with any included OEM-specific fixes.

For an example of published security update information, go to Sample Security Patch Support.

• Device manufacturers MUST publish the frequency of security updates the device will receive (for example, every 30 days, every 90 days, and so on).

Emergency Security Maintenance Releases (ESMRs)

Device manufacturers MUST support the ESMR process until the SMR support end date. For details on the ESMR process, refer to

Emergency Security Maintenance Release (ESMR).

Vulnerability Rewards Program (VRP)

Device manufacturers SHOULD operate and maintain a VRP with Bug Bounty and link it to Google`s VRP site. For details on VRPs, refer to

Android Security Rewards Program Rules.

Major OS update support

• Devices MUST support +1 OS version update from the OS version on which the device is AER validated. Devices SHOULD support +2 OS version upgrades from the version on which the device is AER validated.

• Device manufacturers MUST publish information about the guaranteed Android OS version upgrades that the AER device will receive. For an example of published OS upgrade support information, see Sample Security Patch Support.

Revalidation

A version update MUST comply with all the AER requirements for that release to maintain the device`s AER status. Exceptions for Android 15 revalidation include the following:

• Minimum hardware requirements

• OS update support

OEMConfig

OEMConfig apps allow IT admins to set custom policies created by device manufacturers (OEMs). This work removes the necessity for Enterprise Mobility Management vendors (EMMs) to customize each device feature. For details, go to Creating OEMConfig Apps.

Device manufacturers MAY support custom enterprise APIs specific to their devices. Manufacturers that support custom enterprise APIs such as custom device policies MUST comply with all CDD and GMS requirements.

These custom enterprise APIs MUST be managed using an OEMConfig app.

Minimum OS version

Android 14.0

Speed

1.4 GHz

Architecture

64 bit

Memory

3 GB (4 GB RAM recommended). The device MUST NOT be marked as a LOW-RAM device.

flash

32 GB

Cameras

If the device contains front or rear-facing cameras, they MUST be a minimum resolution of 2 MP and 8 MP, respectively.

Speed

1.4 GHz

Architecture

64 bit

Memory

3 GB RAM (4 GB RAM recommended). The device MUST NOT be marked as a LOW-RAM device.

flash

16 GB (32 GB recommended)

Ingress protection

IP 54 certified

Drop test integrity

MIL-STD-810G or IEC 62-2-32

Cameras

If the device contains front or rear-facing cameras, they MUST be a minimum resolution of 2 MP and 8 MP, respectively.

Provisioning flows

Device setup flows MUST comply with the UX Guidelines.

Approved branding

Google MUST review and approve all enterprise branding, including assets and strings, for consistency with the Android brand. Devices using the AOSP assets and strings are exempt from review.

Security update support

For device security updates:

• Device manufacturers MUST publish the following security update information on the device manufacturer website and link the published information to Google`s security bulletins.

○ SMR support end date (that is, the last month and year the device is guaranteed to receive security updates).

○ Fixes contained in the security patch, with any included OEM-specific fixes.

For an example of published security update information, go to Sample Security Patch Support.

• Device manufacturers MUST publish the frequency of security updates the device will receive (for example, every 30 days, every 90 days, and so on).

Emergency Security Maintenance Releases (ESMRs)

Device manufacturers MUST support the ESMR process until the SMR support end date. For details on the ESMR process, refer to

Emergency Security Maintenance Release (ESMR).

Vulnerability Rewards Program (VRP)

Device manufacturers SHOULD operate and maintain a VRP with Bug Bounty and link it to Google`s VRP site. For details on VRPs, refer to

Android Security Rewards Program Rules.

Major OS update support

• Devices MUST support +1 OS version update from the OS version on which the device is AER validated. Devices SHOULD support +2 OS version upgrades from the version on which the device is AER validated.

• Device manufacturers MUST publish information about the guaranteed Android OS version upgrades that the AER device will receive. For an example of published OS upgrade support information, see Sample Security Patch Support.

Revalidation

A version update MUST comply with all the AER requirements for that release to maintain the device`s AER status. Exceptions for Android 14 revalidation include the following:

• Minimum hardware requirements

• OS update support

OEMConfig

OEMConfig apps allow IT admins to set custom policies created by device manufacturers (OEMs). This work removes the necessity for Enterprise Mobility Management vendors (EMMs) to customize each device feature. For details, go to Creating OEMConfig Apps.

Device manufacturers MAY support custom enterprise APIs specific to their devices. Manufacturers that support custom enterprise APIs such as custom device policies MUST comply with all CDD and GMS requirements.

These custom enterprise APIs MUST be managed using an OEMConfig app.

Minimum OS version

Android 13.0

Speed

1.4 GHz

Architecture

64 bit

Memory

3 GB (4 GB RAM recommended). The device MUST NOT be marked as a LOW-RAM device.

flash

32 GB

Cameras

If the device contains front or rear-facing cameras, they MUST be a minimum resolution of 2 MP and 8 MP, respectively.

Speed

1.4 GHz

Architecture

64 bit

Memory

3 GB RAM (4 GB RAM recommended). The device MUST NOT be marked as a LOW-RAM device.

flash

16 GB (32 GB recommended)

Ingress protection

IP 54 certified

Drop test integrity

MIL-STD-810G or IEC 62-2-32

Cameras

If the device contains front or rear-facing cameras, they MUST be a minimum resolution of 2 MP and 8 MP, respectively.

Provisioning flows

Device setup flows MUST comply with the UX Guidelines.

Approved branding

Google MUST review and approve all enterprise branding, including assets and strings, for consistency with the Android brand. Devices using the AOSP assets and strings are exempt from review.

Security update support

For device security updates:

• Device manufacturers MUST publish the following security update information on the device manufacturer website and link the published information to Google`s security bulletins.

○ SMR support end date (that is, the last month and year the device is guaranteed to receive security updates).

○ Fixes contained in the security patch, with any included OEM-specific fixes.

For an example of published security update information, go to Sample Security Patch Support.

• Device manufacturers MUST publish the frequency of security updates the device will receive (for example, every 30 days, every 90 days, and so on).

Emergency Security Maintenance Releases (ESMRs)

Device manufacturers MUST support the ESMR process until the SMR support end date. For details on the ESMR process, refer to

Emergency Security Maintenance Release (ESMR).

Vulnerability Rewards Program (VRP)

Device manufacturers SHOULD operate and maintain a VRP with Bug Bounty and link it to Google`s VRP site. For details on VRPs, refer to

Android Security Rewards Program Rules.

Major OS update support

• Devices MUST support +1 OS version update from the OS version on which the device is AER validated. Devices SHOULD support +2 OS version upgrades from the version on which the device is AER validated.

• Device manufacturers MUST publish information about the guaranteed Android OS version upgrades that the AER device will receive. For an example of published OS upgrade support information, see Sample Security Patch Support.

Revalidation

A version update MUST comply with all the AER requirements for that release to maintain the device`s AER status. Exceptions for Android 13 revalidation include the following:

• Minimum hardware requirements

• OS update support

OEMConfig

OEMConfig apps allow IT admins to set custom policies created by device manufacturers (OEMs). This work removes the necessity for Enterprise Mobility Management vendors (EMMs) to customize each device feature. For details, go to Creating OEMConfig Apps.

Device manufacturers MAY support custom enterprise APIs specific to their devices. Manufacturers that support custom enterprise APIs such as custom device policies MUST comply with all CDD and GMS requirements.

These custom enterprise APIs MUST be managed using an OEMConfig app.

Minimum OS version

Android 12.0

RAM

3 GB

Storage

32 GB

Speed

1.4 GHz

Architecture

64-bit

Default Systems Apps - work profile devices

• Contacts

• Downloads

• Play Store

• EMM app (if bundled in the system image)

Default Systems Apps - fully managed devices

• Camera

• Contacts

• Downloads

• Google (if bundled in the system image)

• Messaging

• Dialer

• Play Store

• Settings

• EMM app (if bundled in the system image)

Other apps

• Contacts

• Dialer

• Settings, etc.

App install permissions

Besides Google Play and the EMM DPC, no apps can install into the work profile or fully managed device except with express approval from Google.

Approved branding

Use standard branding and strings

Provisioning workflow requirements

Devices must adhere to standard provisioning screen flows from AOSP

Security update support

Device manufacturers must publish security update information on their websites and link to it from Google’s Security Bulletins. This includes:

• End date (month-year) through when device is guaranteed to receive security updates

• Fixes contained in the security update, including any included device manufacturer-specific fixes.

Major update release support

• Support current shipping release + one major OS upgrade

• Publish information about the guaranteed Android OS version upgrades that the device will receive.

Revalidation

Every major OS upgrade must comply with all the Android Enterprise Recommended requirements for that release to maintain the device’s program status

OEMConfig

Device manufacturers may support custom enterprise APIs specific to their devices. Manufacturers that support custom enterprise APIs such as custom device policies must comply with all CDD and GMS requirements. These custom enterprise APIs must be managed using an OEMConfig app.

Minimum OS version

Android 11.0

RAM

3 GB

Storage

32 GB

Speed

1.4 GHz

Architecture

64-bit

Default Systems Apps - work profile

• Contacts

• Downloads

• Play Store

• EMM app (if bundled in the system image)

Default Systems Apps - fully managed devices

• Camera

• Contacts

• Downloads

• Google (if bundled in the system image)

• Messaging

• Dialer

• Play Store

• Settings

• EMM app (if bundled in the system image)

Additional apps for work profile and fully managed devices

If devices have additional applications that are visible in the launcher by default then the following requirements apply:

• The applications must be business- or wireless account-focused (i.e., cannot be a game or consumer-focused app).

Other apps

• Contacts

• Dialer

• Settings, etc.

App install permissions

Besides Google Play and the EMM DPC, no apps can install into the work profile or fully managed device except with express approval from Google.

Approved branding

Use standard branding and strings

Provisioning workflow requirements

Devices must adhere to standard provisioning screen flows

Work profile experience

Device must comply with the defined work profile experience including the following:

• Work apps must be grouped into a single UI container, as follows:

○ Device must either have a Personal and Work apps tab.

Security update support

Device manufacturers must publish security update information on their websites and link to it from Google’s Security Bulletins. This includes:

• End date (month-year) through when device is guaranteed to receive security updates

• Fixes contained in the security update, including any included device manufacturer-specific fixes.

Major update release support

• Support current shipping release + one major OS upgrade

• Publish information about the guaranteed Android OS version upgrades that the device will receive.

Revalidation

Every major OS upgrade must comply with all the Android Enterprise Recommended requirements for that release to maintain the device’s program status

Unlocked device availability

Unlocked device must be available for purchase by enterprise customers through either:

• A 3rd-party distributor

• Direct from manufacturer

*Devices that are targeted exclusively for one specific country may apply for an exemption.

Minimum OS version

Android 10.0

RAM

2 GB

32 GB

1.4 GHz

64-bit

• Zero-touch enrollment

• QR Code (If device includes camera)

• NFC (if device is NFC-enabled)

Default Systems Apps - work profile

• Contacts

• Downloads

• Play Store

• EMM app (if bundled in the system image)

Default Systems Apps - fully managed devices

• Camera

• Contacts

• Downloads

• Google

• Messaging

• Dialer

• Play Store

• Settings

• EMM app (if bundled in the system image)

Other apps

• Contacts

• Dialer

• Settings, etc.

App install permissions

• Besides Google Play and the EMM DPC, no apps can install into the work profile or fully managed device except with express approval from Google.

Approved branding

Use standard branding and strings

Provisioning workflow requirements

Devices must adhere to standard provisioning screen flows

Work profile experience

Device must comply with the defined work profile experience including the following:

• Work apps must be grouped into a single UI container, as follows:

○ Device must either have a Personal and Work apps tab or

○ Provide a pre-populated Work Folder containing all pre-loaded Work applications.

Security update support

90-day security updates

Major update release support

• Support current shipping release + one major OS upgrade

Unlocked device availability

Unlocked device must be available for purchase by enterprise customers through either:

• A 3rd-party distributor

• Direct from manufacturer

*Devices that are targeted exclusively for one specific country may apply for an exemption.

Minimum OS version

Android 7.0+

RAM

2 GB

Storage

32 GB

Speed

1.4GHz

Battery life

8+ hours (active)

Camera (front / rear)

2MP / 10MP

Architecture

64-bit

Enrollment methods

• QR code

• Zero-touch enrollment (Required for Android 8.0 devices)

Default Systems Apps - work profile

• Contacts

• Downloads

• Play Store

• EMM app (if bundled in the system image)

• Camera

• Contacts

• Downloads

• Google

• Messaging

• Dialer

• Play Store

• Settings

• EMM app (if bundled in the system image)

• Contacts

• Dialer

• Settings, etc.

• Use standard branding and strings

• Managed devices

• Work profile

• Enrollment

Security update support

90-day security updates

Major update release support

Support current shipping release + one letter upgrade

Unlocked device availability

Unlocked device must be available for purchase by enterprise customers through either:

• A 3rd-party distributor

• Direct from manufacturer

*Devices that are targeted exclusively for one specific country may apply for an exemption.

Minimum OS version

Android 9.0-10.0

RAM

Storage

Speed

Architecture

Ingress protection

Drop test integrity

MIL-STD-810G or IEC 62-2-32

Enrollment methods

• QR code

• Zero-touch enrollment

Default Systems Apps - managed devices

• Camera

• Contacts

• Downloads

• Google

• Messaging

• Dialer

• Play Store

• Settings

• EMM app (if bundled in the system image)

Provisioning flows

Devices must adhere to standard provisioning screen flows

Security update support

90-day security updates

Security updates

Security updates must be made available to customers for five years from the initial ship date of the device.

Major update release support

• Support current shipping release + one letter upgrade

• Future dessert upgrades, including carrier certification, must be available to all Enterprise Recommended devices within 18 months of the board support package (BSP) drop.

Minimum OS version

Android 11.0-12.0

RAM

2 GB

Storage

16 GB

Speed

1.1GHz

Architecture

32-bit

Ingress protection

IP54 certified

MIL-STD-810G or IEC 62-2-32

Enrollment methods

• QR code

• Zero-touch enrollment (Required for Android 8.0 devices)

Default Systems Apps - fully managed devices

• Camera

• Contacts

• Downloads

• Google (if bundled in the system image)

• Messaging

• Dialer

• Play Store

• Settings

• EMM app (if bundled in the system image)

Additional apps for fully managed devices

If devices have additional applications that are visible in the launcher by default then the following requirements apply:
• The applications must be business- or wireless account-focused (i.e., cannot be a game or consumer-focused app).

Provisioning flows

Security update support

• 90-day security updates

Device manufacturers must publish security update information on their websites and link to it from Google’s Security Bulletins. This includes:
• End date (month-year) through when device is guaranteed to receive security updates
• Fixes contained in the security update, including any included device manufacturer-specific fixes.

Major update release support

Revalidation

Management sets

• Solution offering will be validated against advanced features for two of the following Android Enterprise management sets:

○ Work profile management

○ Full device management

○ Dedicated device management

Product console

Product standardizes on Android Enterprise-based management methods as the primary method of setup for Android device management for new deployments of compatible Android devices with legacy methods available after exhausting all Android Enterprise options.

Established support structure with Google

Documentation guidance: Setup and migration

• Documentation and/or instructions that clearly outline for customers how to set up the various Android Enterprise management sets that partner supports.

• Availability of documentation or instructions on guiding customers to successfully migrate from legacy DeviceAdmin based management to modern Android Enterprise management.

Proven experience

Partner will have demonstrated experience in being able to deploy Android Enterprise with established base of successful deployments.

Field sales readiness

Partner will ensure availability of expertise on Android Enterprise certified through Android Academy. across relevant customer engagement teams to deliver relevant product and technical expertise.