Firmware Update

Overview

Update the devices to the target firmware before applying the Configuration. An update can be installed from a local OTA package pushed to the device by your MDM, as described on this page, or downloaded automatically by Arrow FOTA.

Firmware and Espresso updates

Espresso, the Datalogic package of device-specific drivers and APIs that runs on top of the Android firmware, is distributed and installed the same way as firmware. Every step on this page applies to both firmware and Espresso OTA packages.

Arrow FOTA

Datalogic Arrow FOTA automatically downloads and installs firmware and Espresso updates on the device, with no OTA package to host or push. It requires a Shield license and can be configured from any MDM through the Firmware Update settings of OEMConfig, including the target firmware version, polling windows, and release date delay.

Firmware packages

Firmware and Espresso OTA packages are only available from the Datalogic Shield Firmware Website. Sign in, select your device model, and download the package for the target build. Downloading firmware requires an active Datalogic Shield contract.

Monthly security updates

Datalogic releases firmware with the latest Android security patches every month. Unless the devices are updated by Arrow FOTA, plan to download each new release and deploy it through your MDM once a month. To be notified when new firmware is released, subscribe in the Notifications section of your Datalogic developer account.

Each firmware release is available as two types of OTA package:

• Full: Contains the complete firmware. It can be installed over any earlier build for the same model.
• Incremental (INCR): Contains only the changes from one specific build to the next. It is much smaller than a full package, but it must match the device model and the build currently installed on the device.

Before you begin

• Check the model and build currently installed on the devices in your MDM's device inventory, and download the matching package. Packages are specific to the device variant, such as WLAN (Wi-Fi) vs. WWAN (cellular) and ROW (rest of world) vs. US.
• Charge the devices or place them on a charger. Updates can be blocked when the battery is low.
• Make sure the devices have enough free storage for the OTA package, plus room to install it.
• Test the update on a small pilot group of devices before rolling it out to all devices.

Reset type

The firmware update can optionally reset the device after the update completes:

Reset type	Result
None	The device keeps all its data, apps, and settings. This is the recommended option.
Enterprise	Erases all user data and apps, but keeps the enterprise partition.
Factory	Erases all data on the device, including the enterprise partition.

Enterprise and factory resets remove MDM enrollment

Both the Enterprise and Factory reset types remove the device's MDM enrollment. Devices registered for zero-touch enrollment re-enroll automatically once connected to the internet after the reset; all other devices must be enrolled again manually.

Procedure

SOTI MobiControl

These steps are based on SOTI's Creating a Package guide and its Datalogic firmware upgrade guide. A SOTI package copies the firmware OTA package to the device, then runs a post-install script that starts the update.

Packages under 2 GB

Most full firmware packages are larger than 2 GB, so a SOTI package is the recommended method. If your OTA package is under 2 GB, such as an incremental (INCR) package, you can use a File Sync policy instead.

Create the package

1. Sign in to the SOTI MobiControl web console.
2. Open the main menu and select Packages.
3. Select New Package.
4. Select Create.
5. Select Android as the platform.
6. Enter a name for the package, such as Datalogic Firmware Update, and a version, such as the firmware build number.
7. Select Next.
8. On the Files tab, select Add.
9. Browse to, or drag in, the firmware OTA ZIP file.
10. Set File Destination to /sdcard/Download/.
11. Select Save.

Add the update script

1. On the Scripts tab, select Add.

2. Select Post-Install Script.

3. Enter the following command, replacing ota.zip with the actual firmware filename:

   sendintent -s "intent:#Intent;component=com.datalogic.systemupdate/com.datalogic.systemupdate.SystemUpgradeService;i.action=2;S.path=/sdcard/Download/ota.zip;i.reset=0;i.reboot=1;i.force_update=1;end"

4. Select Save.

5. Select Next.

6. Select Publish.

The script's parameters, from the Datalogic Android SDK:

Parameter	Values
action	2: Request the firmware update. Required.
path	Full path to the OTA package on the device. Must match where the file was copied.
reset	0: None (recommended), 1: Factory, 2: Enterprise. See Reset type.
reboot	1: Reboot after the update, 0: Don't reboot.
force_update	1: Install even if the same or an older build is installed, 0: Install only a newer build.
wipe_esim_profiles	Optional, SDK 1.46 and later. 1: Delete all eSIM profiles after the update, 0: Keep them.

Assign the package with a profile

These steps are based on SOTI's Creating a Profile guide.

1. Navigate to Policies > Profiles.
2. Select New Profile.
3. Select Android Enterprise as the platform.
4. Enter a name for the profile, such as Datalogic Firmware Update.
5. Open the Packages tab.
6. Select Add.
7. Select the Datalogic Firmware Update package.
8. Select Add to Profile.
9. Select Save and Assign.
10. Select the target devices or device groups.
11. Select Assign.
12. Verify that the device completes the update and reports the expected build number.

Alternative: File Sync policy (packages under 2 GB)

These steps are based on SOTI's Using File Sync Policies guide. SOTI File Sync doesn't support files larger than 2 GB.

1. Navigate to Policies > File Sync.
2. Select New File Sync Policy.
3. Select Android as the device family.
4. Enter a name for the policy, such as Datalogic Firmware Update, and select Next.
5. On the Configure tab, select Download from Server.
6. In Server File/Folder Name, select File Manager and upload the firmware OTA ZIP file.
7. In Device File/Folder Name, enter /sdcard/Download/ota.zip, using the actual firmware filename if different.
8. Select Next.
9. On the Scripts tab, turn on Enable Post-Sync Script.
10. Set Script Type to Custom and enter the same sendintent command as the package above.
11. Turn on Execute Script Only if Files Transmitted so the update command runs only when files are transferred.
12. Select Next.
13. On the Schedule tab, configure the synchronization schedule.
14. Select Save and Assign.
15. On the Devices tab, select the target devices or device groups.
16. Select Assign.
17. Verify that the firmware file is transferred and the device completes the update.

Microsoft Intune

These steps are based on Datalogic's OEMConfig Firmware Update settings and Microsoft's Azure Blob Storage documentation. OEMConfig downloads the OTA package from a URL, so the package must be hosted where the devices can download it without authentication.

One OEMConfig profile per device

Intune supports only one OEMConfig profile per device on Datalogic devices. Once the update is complete on all devices, unassign or delete the firmware update profile before assigning the profile from OEMConfig.

Create an Azure Storage Account

1. Sign in to the Azure portal.
2. Search for Storage accounts.
3. Select Create.
4. Select the subscription and resource group to use, or create a new resource group.
5. Enter a unique storage account name.
6. Select the appropriate region and leave the remaining settings at their defaults unless your organization's requirements dictate otherwise.
7. Select Review.
8. Select Create.
9. Once deployment completes, select Go to resource.

Create a public blob container

1. In the Storage Account, navigate to Settings > Configuration.
2. Set Allow Blob anonymous access to Enabled and select Save.
3. Navigate to Data storage > Containers.
4. Select + Container.
5. Enter a name, such as firmware.
6. Set the Anonymous access level to Blob (anonymous read access for blobs only).
7. Select Create.

Upload the firmware package

1. Open the firmware container.
2. Select Upload.
3. Select Browse for files and choose the downloaded firmware OTA ZIP.
4. Select Upload.
5. Select the uploaded blob and copy its URL. It should follow this format: https://<storage-account>.blob.core.windows.net/firmware/<firmware-filename>.zip.
6. Open the URL in a private browser window to verify that the file is publicly downloadable without authentication.

Create the OEMConfig firmware update profile

1. Sign in to the Microsoft Intune admin center.
2. Navigate to Devices > Manage devices > Configuration.
3. Select Create > New policy.
4. Select Android Enterprise as the platform.
5. Select OEMConfig as the profile type.
6. Enter a name, such as Datalogic Firmware Update.
7. Select Next.
8. Under Configuration settings, open Firmware Update.
9. Set OTA update file to the complete Azure Blob URL copied earlier.
10. Set Reset type to None, unless your deployment requires another reset type.
11. Select Next.

Assign the profile

1. Assign the profile to the device group containing the target Datalogic devices.
2. Select Next through the remaining configuration pages.
3. Select Create.

SureMDM

These steps are based on SureMDM's Firmware Upgrade guide.

Create the firmware File Transfer job

1. Rename the downloaded firmware OTA package to firmware.zip.
2. Sign in to the SureMDM console.
3. Navigate to Jobs.
4. Select New Job.
5. Select Android.
6. Select File Transfer.
7. Select Add, then select the upload icon.
8. Upload firmware.zip, set the device path to /sdcard/, and select OK.
9. Enter a job name, such as Datalogic_Firmware.
10. Save the job.

Create the Run Script job to start the firmware update

1. Navigate to Jobs > New Job.

2. Select Android.

3. Select Run Script.

4. Enter a job name, such as Upgrade Datalogic firmware.

5. Enter the following script:

   am startservice -n com.datalogic.systemupdate/com.datalogic.systemupdate.SystemUpgradeService --ei action 2 -e path /sdcard/firmware.zip --ei reset 0 --ei reboot 1 --ei force_update 1

6. Save the job.

The script's parameters, from the Datalogic Android SDK:

Parameter	Values
action	2: Request the firmware update. Required.
path	Full path to the OTA package on the device. Must match where the file was copied.
reset	0: None (recommended), 1: Factory, 2: Enterprise. See Reset type.
reboot	1: Reboot after the update, 0: Don't reboot.
force_update	1: Install even if the same or an older build is installed, 0: Install only a newer build.
wipe_esim_profiles	Optional, SDK 1.46 and later. 1: Delete all eSIM profiles after the update, 0: Keep them.

Create and apply a Composite Job

1. Navigate to Jobs > New Job.
2. Select Android.
3. Select Composite Job and select Add.
4. Add the two jobs in this order:
   1. Datalogic_Firmware (File Transfer).
   2. Upgrade Datalogic firmware (Run Script).
5. Save the Composite Job.
6. Return to the SureMDM Home page and select the enrolled device or target devices.
7. Select Apply.
8. Select the Composite Job and apply it.
9. Verify that the firmware update completes successfully.

Workspace ONEWorkspace ONE (formerly AirWatch)

These steps are based on Omnissa's Managing Android OS Upgrades with Workspace ONE UEM guide.

Create the OS Upgrade File/Actions component

1. Sign in to the Workspace ONE UEM console.
2. Navigate to Devices > Provisioning > Components > Files/Actions.
3. Select Add Files/Actions.
4. Select Android.
5. Enter a name, such as Datalogic Firmware Update.
6. Select the Files tab.
7. Select Add Files.
8. Select Choose Files and upload the firmware OTA ZIP.
9. Set the Download Path to $osupdate$/ota.zip, replacing ota.zip with the actual firmware filename.
10. Select Save.
11. Select the Manifest tab.
12. Under Install Manifest, select Add Action.
13. Select OS Upgrade.
14. Select the uploaded firmware ZIP file.
15. Select Save to save the Files/Actions component.

Create and assign the product

1. Navigate to Devices > Provisioning > Product List View.
2. Select Add Product.
3. Select Android.
4. On the General tab, enter a Name, such as Datalogic Firmware Update.
5. In Assigned Groups, select the Smart Groups that should receive the update.
6. Select the Manifest tab.
7. Select Add.
8. Select File/Action - Install from the Action(s) To Perform list.
9. In Files/Actions, select the Files/Actions component created earlier.
10. Select Save.
11. Select Activate to preview the devices that will receive the update.
12. Select Activate again to start the deployment.
13. Monitor the product deployment status in Workspace ONE UEM.
14. Verify that the device installs the update, reboots if required, and reports the expected build number.

If the update fails

If a device doesn't report the new build in your MDM's device inventory after the update:

• Check that the package matches the device model. For incremental packages, also check that it matches the build installed on the device.
• Check that the OTA package reached the device, at the expected path, and is not truncated.
• Check the battery level and free storage on the device.
• Download the package again from the Shield Firmware Website and retry the update, or use the full package instead of an incremental one.
• If the update still fails, contact Datalogic support with the device model, serial number, current build, and the package filename.