Knox Customization enables Systems Integrators to transform Samsung devices into purpose-built appliances for vertical B2B markets like hospitality and retail. Example apps include hospitality...
To use the Knox Customization SDK, you need an Enterprise License Management (ELM) key and a Knox License Management (KLM) key.
Enterprise License Management (ELM)
Developers use ELM licenses...
As described in What licenses do I need to use the Knox Customization SDK, you need both an ELM and KLM license.
To activate the:
ELM license — Use the package android.app.enterprise.license...
The Knox Customization SDK v2.5 uses the term ProKiosk mode instead of the previously used term Sealed mode. ProKiosk indicates that it’s an extension of the Kiosk mode from the Knox Standard SDK.
Version 2.5 of the Knox Customization SDK introduces several enhancements to improve API names, groups, permission control, and future scalability. Although the latest v2.5 SDK provides backwards...
If you have migrated from the Eclipse IDE to Google's new Android Studio IDE, you can use an SDK packaged as an Eclipse add-on as follows:
Download the SDK.
Extract the SDK's add-on .ZIP...
Previously, all the Knox Customization API methods were provided in a single Java class called KnoxCustomManager. With v2.5, the API methods are now grouped into three new Java classes for better...
There are three types of deprecated API methods:
Replaced: This API method has been replaced by another. In the Javadocs, these are indicated as follows:
public boolean addHomeShortcut (...
Yes. Version 2.5 of the Knox Customization SDK supports the class KnoxCustomManager and existing apps that use the class will continue to run on new devices.
However, from v2.5...
