Managing Location Services on Android Devices with MaaS360

Configuring location services
To manage location services on Android devices, the device must be enrolled as a Device Owner. Once enrolled, administrators can configure the device's location permissions with the policy from the MaaS360 portal by navigating to Security > Policy > Select the policy applied to the device > Android Enterprise Settings > Restrictions > Location Sharing Settings. These settings provide control over location permission of the device and location sharing mode.

When the location data is collected and reported

• Data Collection Frequency: MaaS360 collects location data based on the time interval set within the security policy. This can be configured within the policy on the MaaS360 portal by navigating to  Security > Policy > Select the policy applied to the device > Android Enterprise Settings > Device Management > Application Timers > Location Data Collection Frequency.

• Data Reporting Frequency: Location data is only reported to the MaaS360 portal if the device moves approximately one mile from its last recorded location. This ensures that location updates are relevant and prevents unnecessary data transmissions.

Impact on battery performance

Efficient location tracking requires balancing data collection frequency with battery consumption. Consider these factors when configuring location services:

• Higher Data Collection Frequency: Setting a shorter collection interval allows for more precise tracking but may increase battery usage.

• Lower Data Collection Frequency: Reducing the frequency of location updates can help conserve battery life, but may result in less frequent location updates.

Best Practices and Recommendations

To optimize location tracking on Android devices while maintaining battery efficiency, organizations should:

• Set appropriate update intervals to balance accuracy and power consumption.
• Ensure devices are enrolled as Device Owner to enable location tracking capabilities.
• Regularly review policies to align with security and operational requirements.