Product Documentation

How Scheduling Policies Affect Android Battery Usage

Dec 21, 2015
When you create a scheduling policy in Device Manager for Android devices, the way you create the scheduling policy can affect battery usage. For example, compared to a device that does not have an XenMobile client agent running on the device, the following may occur:
  • If you create a scheduling policy that is set to permanently alive, with app monitoring enabled and basic MDM policy, tests reveal an additional 4 percent battery drain per hour.
  • If you create a scheduling policy that is set to permanently always alive, without app monitoring, but with basic MDM policies, tests reveal a 2.5 percent battery drain per hour.
Policy and connection conditions Effect on Android device battery over time
You do not configure an app control policy, but configure thefollowing policies: password policy, TouchDown Email policy, and scheduling policy 8-9 percent over 5 hours equaling approximately 1.6 percent battery drain per hour
You configure an app control policyd, but do not configure a scheduling policy 10-12 percent over 5 hours equaling approximately 2.4 percent battery drain per hour
You do not configure an app control policy, but you configure the following policies:
  • Password policy
  • Software inventory policy
  • WiFi configuration policy
  • Credentials policy
  • SharePoint configuration
  • TouchDown Email policy
  • Scheduling policy of permanently alive with a default connection timer set
10-13 percent over 5 hours equaling approximately 2.6 percent battery drain per hour
You configure the following policies:
  • App control policy (a type of blacklist policy)
  • Password policy
  • Software inventory policy
  • WiFi configuration policy
  • Credentials policy
  • SharePoint configuration
  • TouchDown Email policy
  • Scheduling policy of permanently alive with a default connection timer
12-20 percent over 5 hours equaling approximately 4 percent battery drain per hour