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.

Device key mapping for non-rugged devices

Supported devices

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

These are some of the most popular Galaxy devices that are supported:

Licenses

• A free Knox license key is required to use this functionality, but license activation isn’t required to be built into the partners’ app.

• Knox Service Plugin (KSP) handles the license activation on behalf of partners.

• A KSP policy needs to be set up in your unified endpoint management solution (UEM). All major UEMs are compatible.

• Partners can retrieve Knox licenses through our Knox Partner Program or a request from their Samsung representative.

UEM and KSP (Knox Service Plugin)

• A UEM and Android Enterprise are required to use KSP.

• For devices where the power key is mapped to Bixby by default, you might need a UEM policy that disables Bixby.

• Depending on the device, the screen might switch on and off when the Home key is pressed. The partners’ app must take this into account and work around the issue.

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.

IT admins

If you’re an IT admin looking for information on how to map keys on non-rugged devices, go to Device key mapping for non-rugged devices.

Device key mapping for rugged devices

Go to Device key mapping for rugged devices.