FAMOCO OS 2.0 Firmware upgrade
The FAMOCO OS 2.0 is a major release that packages multiple updates and new functionalities. A Beta testing phase is currently underway with a selection of clients whose feedback will help shape the final release. The final release will be mandatory for all future improvements.
The upgrade applies to all devices and to simplify the OS upgrade process we have created a Device Updater application.
The “Device updater” is an application that will allow you to remotely upgrade the firmware of your devices by downloading new firmware and installing it on the devices.
The Firmware is quite large, around 200 MB, and means the process is data hungry (and relatively long - approximately 7 minutes with standard 512K ADSL).
We recommend turning off the Mobile Data Connection for the Firmware update when using SIM with little data allowance and doing the update through WiFi connection.
The following steps are recommended for the FAMOCO OS 2.0 Firmware upgrade:
- Test fleet - dedicated app only (Section 1 + 2)
- Dry run - dedicated app on clone of existing fleet (Section 3)
- Full rollout (Section 4)
The Device Updater application will be easily identifiable from the list of your FMS applications, thanks to its name and logo, that look like like:
However, please feel free to revert to your sales account manager for any clarification.
Setting up the Device Updater in your FMS : Test fleet
To get used to the procedure, we suggest you first try it with a few test devices. We advise to use stock devices, if any available, that do not contain any data.
Please create a new profile called Test profile with the following configuration:
- Device updater application within the applications list
- Developer mode ON
- Screen timeout 30 mins
- Sync interval 5 mins
- Volume level to 1
Then create a fleet called Test fleet and apply Test profile to it, before choosing a device you have with you and that does not contain any sensitive information, to be drag and dropped to the newly created fleet from the FMS Devices tab.
You can now test the Firmware Update procedure for the test device in the Test fleet by following the step-by-step process described in Section 2 below.
Please repeat the same process with multiple devices simultaneously (five for example) to test batch upgrade.
If any issue is faced in the process, please contact support (firstname.lastname@example.org) with [OS 2 Beta Tester] in the email Subject. In the body of the mail, please include the FAMOCO ID and image build number (can be found on device dashboard). A support agent will reply within 48 hours.
Once the Device Updater has been set up in your FMS, you can update the devices
a) Connect device to Internet. Please note that natively all FAMOCO devices can connect to SSID “FAMOCO” with password “famocoaccess”. You can set-up a local router / hotspot with this configuration for convenience.
b) Synchronize device by pressing the volume-up button for 2 seconds.
c) The Device Updater app will be installed on the device, initialize and either display the update available pop-up described in step d); or display an error message as described in Section 5.
d) Click “OK” on the download popup that appears on screen. This will start the download of the firmware from the server.
e) Wait for the firmware to download (tracked with a progress bar).
Click “OK” on the install pop-up that appears on screen. It will then reboot the device to trigger the firmware installation.
f) After reboot the Android installer page will appear, indicating that the firmware upgrade is in progress (The installation lasts around 1 minute, please do not remove the battery during this process). The FAMOCO Dashboard will appear once the upgrade is complete.
g) Verify that the new firmware has been installed successfully. You can do this on the device through the dashboard, or through the FMS in “device details”. You can also contact the FAMOCO support team for them to export a Firmware upgrade status report.
Now that you are familiar with the process, you are ready to apply it to an existing fleet. The firmware upgrade application has been designed to not corrupt any data on the devices, so both the existing applications and their data will remain untouched.
It is therefore possible to simply add the OTA application to the fleet, but in order to monitor the fleet upgrade in the best possible way, we recommend a dry run on a clone fleet first.
To clone a fleet:
Please select a fleet F accordingly, which contains devices that you physically have access to.
Duplicate the profile P attached to fleet F, name it P clone and add the device updater to its list of applications.
Create a new fleet F clone and attach P clone to it
Drag and drop one device from fleet F to fleet F clone
Follow steps described in Section 2 to update the device and double check that all applications are available and the data has not been affected.
Re-do the same process with few more devices if desired.
After the Dry Run is complete, you are ready to upgrade rest of the fleet using the same process (recommended for better monitoring), or by adding the application to the original fleet.
Please note however, if devices are physically in the same place, the download can be subject to Wi-Fi limitations when upgrading large batches of devices simultaneously. If this occurs, please proceed with small batches of 5 to 10 devices.
Once devices have been updated, you can move them back to their original fleet as the Device Updater is of no further use.
Errors that can occur during the process:
The error messages will be clear and descriptive, such as warning that download requirements are not fulfilled (not enough battery or not connected to Wi-Fi), but if you face any message you don’t understand, please feel free to contact support.