Custom Profile Support in AirWatch Launcher 4.0

AirWatch Launcher uses custom profiles to allow administrators to push advanced MDM features and other settings to Android devices that are not supported through the Workspace ONE UEM Console. The functionality discussed in this article apply to AirWatch Launcher 4.0.

 

Using Custom Profiles

The Custom Settings payload allows administrators to enter their own XML into a profile and apply the profile to devices. Follow the steps below using the custom XML code found in this article.

  1. Configure the General profile and deployment options as desired.
  2. Navigate to the Custom Settings profile and select Configure.
  3. Add the associated XML below to the Custom Settings text box. 
    1. This XML should contain the complete block of code as listed below. 
    2. Administrators should configure each setting from <true /> to <false /> as desired. 
    3. If certificates are required, then configure a Certificate payload within the profile and reference the PayloadUUID in the Custom Settings payload.
  4. Select Save & Publish.

Be sure you’re using the right characteristic type for your profile type:

  • For Android profiles, use characteristic type = "com.airwatch.android.androidwork.launcher"
  • For Android (Legacy) profiles, use characteristic type = "com.airwatch.android.kiosk.settings"

 

HomeFloatingButtonSetting:

In COSU, HOME and RECENTS buttons are disabled hence its not easy for user to switch between the apps but launcher provides a way to have a similar home screen experience by adding a floating home button.

Functionalities of the floating button:

Floating button is a view, which will be shown on top of any app. Clicking on the floating button will launch the home screen which is launcher since launcher is the default home app.
Floating button can be moved across any part of the screen
Floating button if not touched for a particular amount of time will fade itself so that it allows to read the content below it.
Floating button becomes active again when the user touches it back.

Note: By default Home Floating button will be added in AFW mode for MULTIAPP and TEMPLATE mode.

 

The floating home button can be configured by using the below setting:

<characteristic type="com.airwatch.android.kiosk.settings" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="HomeFloatingButtonSetting" value="
{&quot;Size&quot;:&quot;Small&quot;,&quot;Color&quot;: &quot;#F377F7&quot;,&quot;TimeToFade&quot;:&quot;5&quot;,&quot;FadeValue&quot;:&quot;3&quot;}"/>
</characteristic>


Things that can be configured for floating button:

  1. Size of the button: Indicates the size of the home floating button. Possible values: Small, Medium, Large.
  2. Time to fade: Indicates the time in seconds for home floating button to fade away.
  3. Color: Indicates the color of the home floating button. color must be specified in hex code Eg:#F377F7
  4. FadeValue: Indicates the amount of fading required. This specifies the alpha (transparency) of the button.

 

RemoveHomeFloatingButtonSetting:

In COSU since HOME and RECENTS buttons are disabled, launcher provides a home floating button to switch between applications. This button is enabled by default
for MULTIAPP and TEMPLATE mode. But if admin wants to remove this button he can use the below setting:

<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="RemoveHomeFloatingButtonSetting" value="True"/>
</characteristic>

 

AllowHomeFloatingSetting:

Home floating button is enabled only for AFW compliant devices. On some of the devices default home button may be inaccessible and if admin wants the home button functionality then he can add this button by using the below flag.
This is applicable only for non AFW devices and only in MULTIAPP and TEMPLATE modes.

<characteristic type="com.airwatch.android.kiosk.settings" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="AllowHomeFloatingSetting" value="True"/>
</characteristic>

 

SingleAppFloatingButtonSetting:

In Single app mode launcher provides a Floating action button for users to access different launcher settings.
This button can be configured by using the below setting:

<characteristic type="com.airwatch.android.kiosk.settings" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="SingleAppFloatingButtonSetting" value="
{&quot;Size&quot;:&quot;Small&quot;,&quot;TimeOut&quot;: &quot;2&quot;,&quot;FixPosition&quot;:&quot;true&quot;}"/>
</characteristic>

Things that can be configured for floating action button:

  1. Size of the button: Indicates the size of the floating action button. Possible values: Small, Medium, Large.
  2. Timeout: Indicates the time in seconds for floating button to fade away. Should be an integer only.
    FloatingTimeoutValue custom flag is now deprecated from version 4.0 instead we should use this flag
  3. FixPosition: When enabled, the user will not be able to move the floating action button. It will be positioned at right end corner.
    FixSettingsPosition custom flag is now deprecated from version 4.0 instead we should use this flag

 

AllowLocalizedAppNames:

Currently in Launcher application names are displayed according to the names that are set on the console. Admin can use this flag to display application names according to the language set on the device.

<characteristic type="com.airwatch.android.kiosk.settings" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="AllowLocalizedAppNames" value="True"/>
</characteristic>

 

ExtraLockTaskPackages:

This setting specifies the packages that are allowed to be launched but are not whitelisted.By default launcher automates the process of whitelisting settings and other applications ,but in any case if some application cannot be launched then we can use this flag.

Note: This is only for troubleshooting purposes.

<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="ExtraLockTaskPackages" value="com.android.settings,com.google.android.chrome/>
</characteristic>

 

SkipUsageAccessPermission:

In case the customer has no use case of using usage access permission they can use the below custom profile to skip this permission being asked from launcher during configuring.

<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="SkipUsageAccessPermission" value="True"/> </characteristic>

 

SkipCosuSetup - COSU

Launcher 4.0 uses new native Android APIs for Google EMM Registered enrollments in the standard Android profile. These new APIs fall under the umbrella of Corporate-Owned Single-Use (COSU) mode. Some features are removed while using COSU mode, this is purposeful to be able to drastically increase the security of the Launcher application. Please see the drawbacks and benefits below, use this custom XML tag to skip COSU mode setup.

  • Impacted features include the removal of the Notification / Status Bar at the top of the screen, and the Home & Recent Task soft keys at the bottom of the screen.
  • By using COSU mode (default), the level of security is greatly improved within the Application.
  • In DO mode COSU will be configured by default, In case the customer's use cases are not satisfied then they can disable COSU setup.

    <characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
    <parm name="SkipCosuSetup" value="True"/>
    </characteristic>

Additional Information

For additional information regarding Custom Profile Support in previous versions of AirWatch Launcher visit the articles below:

Other Languages: 日本語

Have more questions? Submit a request

0 Comments

Article is closed for comments.