Launcher Configuration for Samsungs

Samsung-specific parameters within the Launcher.JSON configuration file

For Samsung devices managed in Knox, the launcher.json configuration will be sent to devices as a Managed App Config through your MDM. Beyond the standard configuration settings and layouts, which you can choose from our Launcher Technical Guide, add the following knoxSettings section to your launcher.json configuration file.

"knoxSettings": {
    "knoxLicenseKey": "XXXXX-YYYYY-ZZZZZ-11111-22222-33333", // Request the test key from BlueFletch
    "knoxProKioskMode": true,
    "knoxAllowWifi": true,
    "knoxAllowBluetooth": true,
    "disableSamsungComponents": [
      "com.android.systemui/.controls.ui.CustomControlsActivity",
      "com.google.android.googlequicksearchbox",
      "com.google.android.gms/.nearby.sharing.DeviceVisibilityActivity"
    ]
}

These values in the disableSamsungComponents array are just examples. BlueFletch disables a number of the components by default, but you can add components to the disableSamsungComponents block based on what you would like to have disabled.

If you would like to enable the Recents button, you can also add the following to the knoxSettings object in your configuration:

"knoxSettings": {
    ...
    "knoxEnableRecentsButton": true
}

Please note that the above only works on some Samsung devices with a physical Recents button. If the device you’re using does not have a physical Recents button, you can use the following to enable BlueFletch’s task switcher service. Add the following to the settings section of your configuration:

"settings" : {
    ...
    "recentsActivityEnabled": true
}