Device profiles ensure proper use of devices, protection of sensitive data, and workplace functionality. Profiles serve many different purposes, from letting you enforce corporate rules and procedures to tailoring and preparing Glass devices for how they are used.
The individual settings you configure are called payloads. Consider configuring only one payload per profile, which means you have multiple profiles for the different settings you want to push to devices. For example, you can create a profile to integrate with your email server and another to connect devices to your workplace Wi-Fi network.
The way profiles are deployed for Google Glass depends on the edition. The chart below explains the differences:
|Google Glass EE13||Android (Legacy)|
|Google Glass EE14||Android (Legacy)|
|Google Glass EE15||Android (Legacy)|
|Google Glass EE2||Android|
Deploying Profiles with First Edition Google Glass
- Recovery code needs to be configured. This is achieved by running the following adb command (in this example, 12345 is the recovery code).
- $ adb shell am broadcast -a com.google.glass.action.STORE_RECOVERY_CODE --el RECOVERY_CODE 12345
- Navigate to to configure this option.
Deploying Profiles with Second Edition Google Glass
Google Glass EE2 uses Android Work Managed Device mode functionality. In the steps for creating a profile for Google Glass, select Android platform. For Google Glass EE15 and lower and other smart glasses, use Android (Legacy) platform.