Creating a Remap File
The administrator can create an xml configuration file and import it into any MC32N0 device. Use any text editor to
create the xml file with the filename: key-config.xml.
<?xml version="1.0" encoding="UTF-8"?>
<Button_Remap>
<trigger_1 mode="Remap Button">
<REMAP_CODE>BUTTON_L1</REMAP_CODE>
<EXTRA_SHORTCUT>MPA3_TRIGGER_1</EXTRA_SHORTCUT>
<EXTRA_TITLE/>
<EXTRA_PACKAGE_NAME/>
</trigger_1>
<trigger_2 mode="Remap Button">
<REMAP_CODE>BUTTON_R1</REMAP_CODE>
<EXTRA_SHORTCUT>MPA3_TRIGGER_2</EXTRA_SHORTCUT>
<EXTRA_TITLE/>
<EXTRA_PACKAGE_NAME/>
</trigger_2>
<trigger_3 mode="Remap Button">
<REMAP_CODE>VOLUME_UP</REMAP_CODE>
<EXTRA_SHORTCUT>MPA3_TRIGGER_3</EXTRA_SHORTCUT>
<EXTRA_TITLE/>
<EXTRA_PACKAGE_NAME/>
</trigger_3>
<trigger_4 mode="Remap Button">
<REMAP_CODE>VOLUME_DOWN</REMAP_CODE>
<EXTRA_SHORTCUT>MPA3_TRIGGER_4</EXTRA_SHORTCUT>
<EXTRA_TITLE/>
<EXTRA_PACKAGE_NAME/>
</trigger_4>
<trigger_5 mode="Shortcut">
<REMAP_CODE>BUTTON_R2</REMAP_CODE>
<EXTRA_SHORTCUT>MPA3_TRIGGER_5</EXTRA_SHORTCUT>
<EXTRA_TITLE/>
<EXTRA_PACKAGE_NAME/>
</EXTRA_PACKAGE_NAME>
</trigger_5>
<search_key mode="Remap Button">
<REMAP_CODE>NONE</REMAP_CODE>
<EXTRA_SHORTCUT>SEARCH_KEY</EXTRA_SHORTCUT>
<EXTRA_TITLE/>
<EXTRA_PACKAGE_NAME/>
</search_key>
<headset mode="Remap Button">
<REMAP_CODE>NONE</REMAP_CODE>
</headset>
</Button_Remap>
Replace the options for each trigger. See Keypad Remap Strings on page 179 for a list of available button functions.
Enterprise Reset
To ensure that the configuration persists after an Enterprise Reset:
1. Export the settings before an Enterprise Reset and then import the settings after an Enterprise Reset or
2. Push the configuration file using a MSP or a third-party MDM to the /enterprise/device/settings/
keypad/ folder before the Enterprise Reset. After the Enterprise Reset the key configuration will be automatically
applied from this file.
Two ways to persist the settings:
112 | Settings for Android Devices
April 2015 | MN000887A01-B
To Next Page
Loading...
Need help?
General