# Android 10 and 11

## Deploying BlueFletch Enterprise Applications on Android 10 and Android 11 <a href="#deploying-bluefletch-enterprise-applications-on-android-10-and-android-11" id="deploying-bluefletch-enterprise-applications-on-android-10-and-android-11"></a>

With the introduction of Android 10, Enterprise devices will benefit from improved security. These improvements will have an impact on how a device is ultimately provisioned.

To find out more about Android 10 improvements review the official Android developer documentation at <https://developer.android.com/about/versions/10/features>.

### Relevant Android 10 Security Changes <a href="#relevant-android-10-security-changes" id="relevant-android-10-security-changes"></a>

The major changes that affect BlueFletch Enterprise applications on Enterprise devices:

* Restrictions on accessing the Device Serial Number.
* Restrictions on an application's ability to start Activities from services.

#### Device Serial Number <a href="#device-serial-number" id="device-serial-number"></a>

For BlueFletch Enterprise applications to properly communicate the status of individual devices, the [Device ID](/bluefletch-enterprise/product-guides/device-applications/device-id/technical-guide.md) application will need to be installed and started. This application allows all the BlueFletch device applications to use the same device id. On Zebra and Honeywell devices, this application will be able to use the device *Serial Number* as the id.

#### Starting Activities from Services <a href="#starting-activities-from-services" id="starting-activities-from-services"></a>

As some of the BlueFletch Enterprise applications work in the background using services, these applications will need a new permission granted to them: android.permission.SYSTEM\_ALERT\_WINDOW. This permission will allow the applications to start activities from services.

**Affected Applications:**

* Enterprise Launcher
* Messaging
* Support Agent
* Remote Agent

**Note**: If running Android 10 on Zebra devices, the BlueFletch Launcher will set this permission, no further work is needed.

### Device ID within EMM <a href="#device-id-within-emm" id="device-id-within-emm"></a>

Within an EMM Policy, ensure the following steps are completed. The Device ID application will be automatically installed and can not be removed by the user. Additionally this will prevent device setup from completing until installation is done.

#### 1. Setup Actions <a href="#id-1-setup-actions" id="id-1-setup-actions"></a>

Utilize the *Setup Actions* feature within **Device Provisioning** to install the Device ID application during device provisioning. Note: If your organization utilizes Playbook within device provisioning, the latest version of Playbook will ensure the Device ID application is properly installed and running.

<figure><img src="/files/RvyWoCUD0IvcOecHDi8Y" alt="" width="563"><figcaption></figcaption></figure>

#### 2. Select Application <a href="#id-2-select-application" id="id-2-select-application"></a>

Ensure the Device ID application is defined within the **Account and App Management** section.

<figure><img src="/files/xCPpecs4YHsP9Ya518M6" alt="" width="563"><figcaption></figcaption></figure>

#### 3. Set Permissions <a href="#id-3-set-permissions" id="id-3-set-permissions"></a>

Within **Account and App Management** ensure default permissions are allowed for SYSTEM\_ALERT\_WINDOW.

<figure><img src="/files/LIh2KD7WrVOLz5j1eJet" alt="" width="563"><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bluefletch.com/bluefletch-enterprise/technical-documentation/deploying-bluefletch-enterprise/android-10-and-11.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.