The device ownership application is a pre-configured application with special privileges to perform tasks, such as monitoring settings, managing settings, and other privileged tasks. In a COPE device use case, the organization will have complete ownership of the device by using this concept. See the subsections given below to fully understand the device ownership concept.
Device ownership application functionality
Let's take a look at how an application having the device ownership settings enabled, function.
- Once the device ownership is assigned to an application, it gets access to a set of Android APIs, such as adding a user restriction policy on Android devices. These APIs are only accessible by the device ownership application.
- At a given time a device can only have one application with the device ownership settings. It prevents another application that has the same device ownership settings from overriding the policies that have already been enforced on the device.
- If you wish to remove the device ownership application, you need to factory reset the device. For example, in a situation where the device needs to be given to a different user, you need to factory reset the device to remove the application.
Configuring the WSO2 EMM service application
Before you begin
Make sure to have the system service application installed on your device. For more information, see Integrating WSO2 EMM and the system service application.
Let's take a look at how WSO2 EMM configures the device ownership settings on the service application.
Assign the device ownership settings to the service application using one of the following methods.
The device ownership settings only work for SDK API levels 21 and above.
A command issued through the Android Debug Bridge (adb).Click here for more information.
Integrating Android for work.
For more information on how this is done, see the content under Google account method in the Android Developer Guide.
- Reboot or restart your Android device.
When your Android device restarts or boots up, it will check for the configured
device-owner.xmlfile. If the file exits, the application mentioned in the XML file is assigned the device ownership settings.
Before restarting your device, make sure that the system service application is installed on the device. Not having the system application on your device can lead to device restarting/rebooting issues, after you have configured it for device ownership.
Integrating the service application with WSO2 EMM
To successfully integrate the service application with WSO2 EMM you need to have the WSO2 EMM Android agent installed as well. Take a look at the diagram given below to clearly understand the role of the EMM agent in this scenario.