In this tutorial, you are enrolling your Android device also known as Bring Your Own Device (BYOD) with WSO2 IoT Server. WSO2 IoTS supports devices on Android version 4.2.x to 7.0 (Android Jelly Beans to Nougat). If you want to enroll a Corporate-Owned, Personally Enabled (COPE) device, you need to configure WSO2 IoT Server is the system service application and install the configured Android agent on the device.
The following subsections explain how you can work with the Android device type:
Enroll an Android device
Follow the instructions given below to enroll an Android device:
Try it out
You can view device details and carry out operations on your device, after successfully enrolling it with WSO2 IoTS. Let's take a look at how you can do it:
Navigate to the Device Management page to view all the created devices.
Click the view icon on the Android device you enrolled.
Example:
You will be directed to the device details page where you can view the device information and try out operations on a device.
Example:
View device details
The details of each registered devices will be shown on separate pages within the Device page.
| Description |
|---|
| Device Details | The following device information will be retrieved automatically when you register with IoTS. | Device | This shows the name the user has given his/her device (e.g., Kim's iPhone). | | Ownership | Indicates if the device is your own device/Bring Your Own Device (BYOD) or if it's a Corporate-Owned, Personally Enabled (COPE) device.
For the device to be a COPE device, WSO2 IoT Server must be configured to use the system server application. | | Status | Indicates if the device is active, inactive or removed from WSO2 IoTS. |
|
| Policy Compliance | If your device does not comply with certain criteria in the enforced policy, the aspects in which your device is none compliant will be highlighted under this section. |
| Device Location | Provide the location of your device. |
| Installed Application | A list of all the applications that have been installed on your device and the memory consumption by each application will be listed under this section. |
| Operation Log | A list of all the operations that have been carried out by you and its current status.
The operation logs shows the following statuses:
IN-PROGRESS - The operation is processing on the IoT server side and has not yet been delivered to the device.PENDING - The operation is delivered to the device but the response from the device is pending.COMPLETED - The operation is delivered to the device and the server has received a response back from the device.ERROR - An error has occurred while carrying out the operation.
|
Device operations
The default operations that are available for Android devices are accessible for BYOD devices. The COPE devices can only carry out selected operations. If you want to enable the COPE devices to carry out more operations or if you want to limit BYOD devices from carrying out selected operations, you can do so via policies.
Click on the operation you wish to carry out and provide the required details (if requested) to apply the selected operation on your device.
| Operation | Description |
|---|
Device Lock | Ability to lock a device via the IoT Server. |
Device Unlock | Ability to unlock the device via the IoT Server |
Location | Ability to receive the location of the device. |
Mute Device | Ability to enable the silent profile on a device via the IoT Server. |
Enterprise Wipe | Ability to unregister a device from IoTS. |
Clear Password | Ability to remove a device lock via the IoT Server. |
Change Lock-Code | Ability to change the provided passcode or lock-code. |
Ring | Ability to ring the device via the IoT Server. |
Message | Ability to send a message to the device via the IoT Server. The IoTS admin can use
this device operation to send group messages or even private messages to the IoTS users. |
Wipe Data | Ability to carry out a factory reset operation on your own device via the IoT Server. The user will have
to provide the PIN, which he/she entered when registering to IoTS, to be able to wipe his/her device. |
Reboot | Ability to reboot or restart your Android device. |
Upgrade Firmware | Ability to upgrade the firmware to a newer version, over-the-air (OTA) |
Logcat | Ability to push logcat of the device to the analytics server. Logcat displays messages in real time and keeps a history so you can view the old messages. |
System service application operations
WSO2 IoT Server provides a separate service application that can be signed by a firmware signing key and installed on the devices as a system application alongside the Android agent application. This enables you to have better control over the devices registered with WSO2 IoT Server. to install the system service application on the devices, you need to integrate it with WSO2 IoT Server. For more information, see Integrating the Android System Service Application.
You can perform the following operations if you have the system service application installed on your Android device.
- Schedule firmware upgrades on the device.
- Reboot or restart your device.
- Install and update applications in silent mode that is without the user's confirmation via the system service application.
- Hard lock an Android device, where the Administrator permanently locks the device.
- Unlock a device that was hard locked.
icon.