Now, the AOSP version can operate like the AFW (Android for Work) version on non-rooted devices, as long as Device Owner permission is granted to Urmobo on the device.
To perform this procedure, the following are required:
- An Android AOSP device
- The Urmobo client already installed on the device
Attention: To install the Urmobo client, follow the detailed instructions in this manual:
Manual de Instalação - AOSP (PDF)
Preparing the Environment on Your Computer
1. Download and unzip the Android platform-tools package, available at this link:
Download platform-tools (Windows)
Configuring the Device
On the AOSP device, go to the Settings menu.
If the Android version is 8.0 or higher, select System.
Scroll down and select About phone.
In About phone, scroll down and tap Build number seven times until you see a message indicating that Developer Mode has been enabled.
Go back to the previous screen (Settings) and scroll to the bottom. You will now see the Developer options menu.
Enter Developer options and enable USB debugging, as shown in the image below.
Next, connect the device to your computer using a USB cable.
The device will display a prompt asking to authorize USB debugging. Tap "Allow" to confirm the authorization, as shown in the image below.
If the device does not automatically display the USB debugging permission prompt, follow these steps:
- Go to Developer Options on the device.
- Tap Revoke USB debugging authorizations.
- Disconnect and reconnect the USB cable to the computer.
If the prompt still doesn’t appear after that, proceed to the next step:
4. On your computer, open the terminal (CMD), navigate to the folder where the platform-tools were unzipped, and run the following command:
adb devices
This command can force the permission prompt to appear on the device.
If the prompt still doesn’t show up, it’s possible that the device drivers are not properly installed. Even if the device allows file transfer, ADB drivers may be required for it to be correctly recognized as a debugging device.
After clicking OK on the debugging request on the device, run the command adb devices again in the CMD. The expected result should look similar to the example below:
List of devices attached 0123456789abcdef device
With the device connected and authorized, enter the following command in the terminal (CMD):
adb shell dpm set-device-owner com.urmobo.mdm/com.urmobo.mdm.DeviceAdminReceiver
This command sets the Urmobo app as the Device Owner of the device.
✅ Done!
From this moment on, all the advanced features that were previously exclusive to Knox or Android for Work (AFW) — such as status bar locking, for example — will now be available in your entity for full management of the AOSP device.