- Basics
- About Knox
- Knox licenses
- Knox white paper
- Sign up for Samsung Knox
- Latest release notes
- General Knox FAQ
- General Knox KBAs
- Submit a support ticket
- User Acceptance Testing
- For IT admins
- Knox Admin Portal
- Knox Suite
- Knox Platform for Enterprise
- Introduction
- How-to videos
- Before you begin
- Get started with UEMs
- Introduction
- Blackberry UEM
- Citrix Endpoint Management
- FAMOC
- IBM MaaS360
- Microsoft Intune
- MobileIron Cloud
- MobileIron Core
- Samsung Knox Manage
- SOTI MobiControl
- VMware Workspace ONE UEM
- Knox Service Plugin
- Release notes
- Migrate to Android 11
- FAQs
- Troubleshoot
- KBAs
- Knox Mobile Enrollment
- Knox Configure
- Mobile
- Wearables
- Shared Device
- FAQ
- KBAs
- Knox Capture
- Introduction
- How it works
- How-to videos
- IT admins: Get started
- Getting started with Knox Capture
- Step 1: Launch Knox Capture
- Step 2: Create a scanning profile
- Step 3: Select apps and activities
- Step 4: Configure the scanner
- Step 5: Set keystroke output rules
- Step 6: Test apps in your configuration
- Step 7: Share your configuration
- Step 8: Deploy Knox Capture in Managed mode
- End users: Get started
- Features
- Release notes
- FAQ
- KBAs
- Troubleshoot
- Knox Asset Intelligence
- Knox Manage
- Introduction
- How-to videos
- Get started
- Video: Getting started with Knox Manage
- Integration with Managed Service Provider
- Access Knox Manage
- Configure basic environments
- Create user accounts
- Create groups
- Create organization
- Set up devices and profiles
- Create a new profile
- Assign profiles to groups and organizations
- Enroll devices
- Shared Android device quickstart
- Non-shared Android device enrollment quickstart
- Android Management API device enrollment quickstart
- Apple User Enrollment quickstart
- View device information
- Apply profiles to organizations
- Set up Knox Manage deployment with a Knox Suite license
- Manage Chromebooks
- Manage Android devices with the Android Management API
- Manage Shared iPads
- Configure
- Licenses
- Organization
- Users
- Sync user information
- Groups
- Devices
- Content
- Applications
- Profile
- Knox E-FOTA
- Certificates
- Advanced settings
- Monitor
- Kiosk devices
- Knox Remote Support
- Active Directory
- Microsoft Exchange
- Mobile Admin
- Appendix
- Release notes
- Features
- FAQ
- KBAs
- Knox E-FOTA
- Introduction
- How-to videos
- Get started
- Features
- EMM integration
- Appendix
- Release notes
- FAQ
- KBAs
- Troubleshoot
- Knox E-FOTA On-Premises
- Legacy Knox E-FOTA products
- Knox Guard
- Introduction
- How-to video
- Get started
- Using Knox Guard
- Dashboard
- Manage devices
- Device management
- Accept or reject devices
- Upload devices
- Delete devices
- Complete device management
- Send notifications
- Enable or disable SIM control
- Download devices as CSV
- View device log
- View device deletion log
- Start and stop blinking reminder
- Lock and unlock devices
- Update lock message
- Send relock timestamp
- Turn on/off relock reminder
- Manage policies
- Manage licenses
- Manage resellers
- Manage admins and roles
- Activity log
- Knox Deployment App
- Release notes
- FAQ
- KBAs
- Support
- Open API reference
- Samsung Care+ for Business
- For Knox Partners
- Knox Deployment Program
- Knox MSP Program
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:
| Series | Model series |
|---|---|
| Samsung Galaxy S | Samsung Galaxy S22 series |
| Samsung Galaxy S21 series | |
| Samsung Galaxy S20 series | |
| Samsung Galaxy S10 series | |
| Samsung Galaxy A | Samsung Galaxy A53 series |
| Samsung Galaxy A52 series | |
| Samsung Galaxy A33 series | |
| Samsung Galaxy A32 series | |
| Samsung Galaxy Tab | Samsung Galaxy Tab S8 series |
| Samsung Galaxy Tab S7 series | |
| Samsung Galaxy Note | Samsung Galaxy Note20 series |
| Samsung Galaxy Note10 series |
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.
