Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Managing Android Doze Mode for Workspace ONE (78710)

Last Updated: 7/30/2020Categories: InformationalTotal Views: 5312Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

Starting with Android 6.0, Android introduced Doze Mode, a power-saving feature that defers background CPU and network activity for apps when the device is unused for long periods of time. When a device enters Doze Mode, most applications are unable to connect to the cellular or Wi-Fi network the device is connected to.

As Doze Mode affects Workspace ONE UEM applications, this can lead to a reduced ability to manage the device in real time when devices are idle for extended periods of time. For example:

Workspace ONE Intelligent Hub may be unable to process administrative actions like Enterprise Wipes immediately when limited by Doze Mode.

Workspace ONE Assist sessions cannot be started for a device in Doze Mode unless you take some of the actions below. Please see the "Using Workspace ONE Assist in Doze Mode (Samsung and Zebra only)" section for more information.

More information on Doze Mode is available in this Google article.

Disclaimer: VMware is not responsible for the reliability of any data, opinions, advice, or statements made on third-party websites. Inclusion of such links does not imply that VMware endorses, recommends, or accepts any responsibility for the content of such sites.

Solution

Overview

Currently, you can take two actions to manage how Doze Mode affects your devices – using Firebase Cloud Messaging (all devices) and exempting apps from Doze Mode (Samsung and Zebra only).

Firebase Cloud Messaging

You can choose to use Firebase Cloud Messaging (FCM) over AirWatch Cloud Messaging (AWCM) to maximize your ability to manage devices in real time.

Workspace ONE UEM uses push notification systems to allow you to manage your devices in real time. When an admin sends an Enterprise Wipe or pushes a new profile to a device, UEM initiates the change in real time by sending a push notification system to the Intelligent Hub app on the target device. The two push notification systems for Android are AirWatch Cloud Messaging (AWCM) and Firebase Cloud Messaging (FCM). The Intelligent Hub app can receive only FCM notifications while the device is in Doze Mode – not AWCM.

Exempt Apps from Doze Mode (Samsung and Zebra Only)

On Samsung and Zebra devices, you can completely exempt applications from being affected by Doze Mode. This allows the apps to behave as they normally would while running in the background on an active device.

Note: For Samsung and Zebra devices, exempting the Intelligent Hub from Doze mode achieve the same benefits as using FCM.

First, identify the PackageIDs of the applications that you wish to exempt from Doze Mode. For example, the PackageID of the Workspace ONE Intelligent Hub is “com.airwatch.androidagent”.

Then, use one of the methods below to exempt these apps from Doze Mode:

Samsung:

(Android Enterprise Only) Configure and deploy KNOX Service Plugin, the Samsung OEMConfig application. For more information on OEMConfig, please see OEMConfig on Android Enterprise Devices.

Leverage the “Exempt Apps from Doze Mode” Custom Profile listed in our KB article - Custom Profile Support for Samsung Android Features (2960204) .

Zebra:

(Android Enterprise Only) Configure and deploy the Zebra OEMConfig application. For more information on OEMConfig, please see OEMConfig on Android Enterprise Devices

Use the Apply Custom Settings action in Files/Actions. The Zebra StageNow application can be used to generate XML instructions to add applications to a whitelist of apps that bypass Doze Mode. For more information on Files/Actions, please see Files-Actions Manifest Options for Android.

Using Workspace ONE Assist in Doze Mode (Samsung and Zebra only)

To provide admins the ability to start Assist sessions in Doze Mode, use the methods provided in this article to exempt Workspace ONE applications from Doze Mode. What applications you must exempt depends on whether your devices use AWCM or FCM.

If using AWCM: Exempt both the Intelligent Hub (com.airwatch.androidagent) and Assist Agent (com.airwatch.rm.agent) applications from Doze Mode.

If using FCM: You will only need to exempt the Assist Agent (com.airwatch.rm.agent) application from Doze Mode.

Related Information

Google - Optimize for Doze and App Standby

Disclaimer: VMware is not responsible for the reliability of any data, opinions, advice, or statements made on third-party websites. Inclusion of such links does not imply that VMware endorses, recommends, or accepts any responsibility for the content of such sites.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
vCenter Server 7.0 环境中，外部解决方案的 vCenter Server 证书验证错误 (78709)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

Take Our Survey

Support Assistant