Menu

Hardware key re-mapping

Refer to this section to integrate a hardware key re-mapping configuration using the Samsung Knox SDK.

PTT key re-mapping considerations

If a PTT app vendor decides to use an intent defined by Samsung, an IT Admin can either leave the intent pre-populated, or enter an intent as provided by their PTT app vendor.

List a generic intent to a PTT vendor app

Vendors can also use the following intents for PTT key press and release actions:

  • For key press -> com.samsung.android.knox.intent.action.PTT_PRESS
  • For key release -> com.samsung.android.knox.intent.action.PTT_RELEASE

The following optional timestamp can also be considered:

  • Extra -> com.samsung.android.knox.intent.extra.EVENT_TIMESTAMP (with type long which will hold the Epoch timestamp of the event)

Secure PTT intents

The Samsung Knox team recommends registering an intent in manifest statically so KSP can wake the app if in a stopped state. Consider the following:

<receiver

android:name=".PTTKeyReceiver"

android:permission="com.samsung.android.knox.permission.KNOX_CUSTOM_SETTING"

android:exported="true" >

<intent-filter>

<action android:name="com.samsung.android.knox.intent.action.PTT_PRESS" />

<action android:name="com.samsung.android.knox.intent.action.PTT_RELEASE"/>

</intent-filter>

</receiver>

Optional Security: To ensure a PTT vendor app is listening to intent actions only from KSP, an app can add the above permission in the receiver, which is platform signature protected.