Device key mapping

Overview

Hardware keys on both rugged and non-rugged devices can be mapped to app functions. For example, you could press the side key on a non-rugged device to launch a push-to-talk (PTT) app, or press the top key on a rugged device to launch a camera or navigation app.

This intent doesn’t replace the intents available for rugged devices, and works alongside them.

Device key mapping for non-rugged devices

You can map the side key on non-rugged Samsung devices.

Device support

All Samsung Galaxy S, A, Tab, and Note series devices are supported.

Additionally, devices with the following features are supported:

• Non-rugged devices running Android 12 and higher.
• Non-rugged devices that receive future Android 12 maintenance releases.

Map the side key

To map the side key, you must disable the Bixby package and configure the side key press-and-hold setting, as described in the following procedure.

1. Deploy a compatible push-to-talk (PTT) app with your UEM through Managed Google Play.

2. Disable Bixby with your UEM. You can also do this using Knox Service Plugin by adding the Bixby package com.samsung.android.bixby.agent to the Disable Application without user interaction policy. For details, see Application management policies.

3. In the Knox Service Plugin managed configuration, go to Device Key Mapping and set Enable Key Mapping to True. Then configure the following under Side Key Mapping for specific application:

   • Package Name — Enter the package name of the app that will receive the intent when the side key is pressed.

   • Use Samsung Intent — Set True to use a Samsung Intent. Otherwise, set False to define your own intent below.

   • Intent for Key press — Specify the intent to be sent when the side key is pressed. Note that on devices running Android 14 and higher, this intent is only sent when the side key is pressed and held. On devices below Android 14, the intent is sent the moment the key is pressed down.

   • Intent for Key release — Specify the intent to be sent when the side key is released.

Independent software vendor (ISV) partners

If you’re an ISV partner, see Knox Service Plugin managed side key mapping for non-rugged devices for detailed information about setting up side key mapping on non-rugged devices.

Device key mapping for rugged devices

You can map app functions to a rugged device’s hardware keys with Device Key Mapping policies on Knox Service Plugin.

In the Knox Service Plugin managed configuration, go to Device Key Mapping and set Enable Key Mapping to True. Then configure the policies below.

• Enable XCover/Active Key Mapping for Microsoft Teams — Set True to enable key mapping support to pass an intent for a Microsoft TEAMs application package.

• Map specific app intents for the XCover/Active key, Top Key, and Side Key under their respective policies. For each key, enter the following:

  • Package Name — Enter the package name of the app that will receive the intent when the key is pressed.

  • Use Samsung Intent — Set True to use a Samsung Intent. Otherwise, set False to define your own intent below.

  • Intent for Key press — Specify the intent to be sent when the key is pressed. Note that on devices running Android 14 and higher, this intent is only sent when the side key is pressed and held. On devices below Android 14, the intent is sent the moment the key is pressed down.

  • Intent for Key release — Specify the intent to be sent when the key is released.

• Enable Key Mapping to Launch applications — Set to True, then go to Device Key Mapping to Launch application Configurations and add a configuration to launch an app when a key is pressed. For each configuration, set the following:

  • Device Key Mapping — Select which key press intent launches the app.
  • Package Name — App package to launch when the key intent above is triggered.

Key mapping considerations

When enabling key mapping controls, policies are applied according to a set order of precedence.

Keep the following usage scenarios in mind when planning your key mapping configuration:

• Among B, C, D, and E, the precedence order is B > C > E for the XCover Key, and D > E for the Top Key.

• If just B and C are enabled, B is applied.

• If just B and E are enabled, B is applied for the XCover Pro. E is supported on both XCover Key and Top Key, with Top Key settings applied.

• If just C and E are enabled, C is applied for the XCover Key. E is supported on both XCover Key and Top Key, with Top Key settings applied.

• If just D and E are enabled, D is applied for the Top Key. E is supported on both XCover Key and Top Key, with XCover Key settings applied.

• If B, C, D, and E are all enabled, B is applied for the XCover Pro. D is applied for the Top Key.