Overview

Samsung releases new versions of Android firmware to provide new features, improve performance, and resolve known bugs. Each firmware version goes through comprehensive testing and certification on our extensive range of mobile devices. You might however want to wait before deploying a new firmware version to your organization's devices. Specifically, you might need to:

  • carry out your own interoperability or compatibility testing, for example, with your backend servers and in-house apps
  • comply with industry standards on approved device firmware
  • wait until known issues with a new release are patched

With Samsung's new Enterprise FOTA (Firmware Over-The-Air) feature, you can now control the deployment of new firmware. You can:

  • select the highest firmware version allowed on devices
  • force a firmware update across multiple devices at a scheduled time (coming soon)

Requirements

  • SEAP Partner account: If you are not yet a partner, click the button below to enroll as a partner.
  • Samsung Approval: If you are already a partner, click the button below to contact us about access to Enterprise FOTA.

Already a partner? Sign in


How it works

Samsung uses a secure FOTA server to provide firmware over-the-air. You use a REST API to communicate with this server, to check the firmware versions available and force firmware updates onto your devices.

  1. On this SEAP portal, contact us to apply for access to the FOTA server. You will get an API key, which you use to identify yourself in subsequent REST API calls to the FOTA server.
  2. Using the REST API, get a list of the firmware versions available for a device.
  3. Update device firmware using either of these methods:
    • Allow devices to update themselves.
      Through an app on devices, call the Knox Standard SDK v5.7 API method RestrictionPolicy.setAllowedFOTAVersion to set the highest firmware version that the device is allowed to update to. 
    • Force devices to update at a specified time. (coming soon)
      Through the REST API URI setB2bServerInit, force devices in a specified group to update their firmware at a specified time. You can test on a small group of test devices first before general deployment.
  4. The FOTA server sends the specified firmware version to the specified group of devices and initiates the update.
Key features

Through Enterprise FOTA, you can:

  • Ensure that devices do not update to a firmware version that is not yet officially supported by your organization. This prevents potential issues in new releases from affecting  the organization’s tools, data, or staff productivity.
  • Download a new firmware version to a few test devices only. This lets you run your own interoperability or compatibility tests with backend servers, in-house apps, etc. to find any corner cases that might result in performance issues.
  • Roll out new firmware on specified devices at a specified time. This way, devices are using the latest tested version and your IT staff does not need to support many different legacy versions. You can schedule updates during non-peak times, so that they don’t interfere with staff productivity.

 

Next steps ...

  • Browse the Knox Standard API call RestrictionPolicy.setAllowedFOTAVersion, if you would like to set the highest firmware version that devices are allowed to update to. 
  • Contact us if you would like REST API access to Enterprise FOTA server.
  • Read the FAQs. These provide answers to additional questions you might have.