Frequently asked questions for Foundation Software Updates.
In this article:
About
What are Foundation Software Updates?
Foundation Software Updates help users manage updates for devices that run Esper Foundation.
What is Foundation?
Foundation is Esper software that runs on ARM and x86 devices. If you're interested in Foundation, contact Esper Sales.
How do I know if my devices run Esper Foundation?
You can check if a device is running Foundation by checking the Device Details > Software section.
Requirements
What do I need to use Foundation Software Updates?
- Devices need to be on Esper Agent 7.17 or later. How to check Esper Agent version.
- A device’s OTA Manager version should 2.2 or later. How to check OTA Manager version.
When a new software update is available:
- Esper Agent will update within an hour
- OTA Manager will update within six hours
Pipelines
I'm able to set auto-updates and download builds, but I can't use Pipelines.
You'll need an admin to update your role to include Piplines.
I didn’t approve a build, but it’s still an option for a pipeline. Why is that?
You only need to approve builds for auto-updates. Since pipelines are manually deployed, you can choose which build is deployed.
I’m not seeing my device in the device list for this pipeline.
Ensure the device meets the software requirements: Esper Agetn 7.17+ and OTA Manager 2.2+.
Can I use Auto-Update with Pipelines?
Yes. We designed this feature to give you the option to deploy with both update methods.
Here’s one way you can utilize both methods:
When a new build comes out, deploy that build in a pipeline to your test devices. After testing out those devices, approve the new build for auto-updates.
When working with thousands of devices, selecting all the devices you need is sometimes hard. With auto-updates, you no longer need to target every device. Once approved and set, auto-updates will update those devices over a 24 hour period.
Can I use Pipelines to downgrade builds?
No. Android systems don’t support downgrades.
Auto Updates
I’ve set Foundation to auto-update. Why haven’t my devices received the update yet?
The time devices receive auto-updates depend on their model, version, and so on. For example, If I set an auto-update at 9 am, and my device’s schedule timer is at 4 pm, my device will get that auto-update at 4 pm.
If a device hasn’t received an update, check back in 24 hours.
If it’s been more than 24 hours, check the following:
- That the device is communicating with Esper. Sending a ping is one way to check.
- That applicable FQDNs are allow-listed in your firewall.
- That the device has a reliable internet connection.
How will auto-updates affect devices newly added to Esper?
Once the device boots up, it will receive the update.
A device didn’t communicate with Esper during the whole time the previous auto-update version was available. Now there’s a new build. What happens when that device starts communicating with Esper again?
Devices that aren’t communicating with Esper won’t receive any updates. Once they communicate with Esper again, these devices will receive the latest approved update.
However, you may want to update devices to each build at a time. In that case, you can deploy updates through a pipeline.
You may need to disable auto-updates during this period so that devices don’t get an update you aren’t expecting.
I’m trying out Foundation Updates for the first time. Why isn’t my device updated to the latest build?
The first time you use Foundation Software Updates, devices may take 15 minutes to a couple of hours to update to the latest build. If it’s been an hour or two and the device still hasn’t updated, try rebooting it.
Why don’t I see any builds in the dropdown menu for auto-updates?
Approve a build to see it in auto-updates.
Do updates install automatically once auto-update is enabled?
Builds must be user-approved to install. Once approved, the system will install based on its blueprint update settings:
- Automatic - the build updates immediately.
- Windowed - the build installs during the window.
- Postpone - the device user will be prompted to install the build after 30 days.
Learn more about Android System Update Policies.
Full and Delta Builds
What types of builds are displayed in Foundation Sofware Updates?
Only full builds are available.
Can I use delta builds to save on bandwidth for auto-updates?
Reach out to Esper to request delta builds for auto-updates.
Troubleshooting
I get an error message that I need to update the OTA Manager. What is it and how do I update it?
The OTA Manager allows devices to receive updates. Version 2.2+ is required for Foundation Software Updates.
Most devices should automatically update their OTA Manager version to the latest version within six hours.
To check a device’s OTA Manager version, go to Settings > Apps > Esper OTA Manager. The version number will appear at the bottom of the App info screen.
Common issues for why an OTA Manager may not be updated are:
- A firewall interfered with the update. Ensure your Esper general and Foundation rules are on the allowed list.
- The device stopped communicating with Esper during the update period. Ensure the device has a stable network connection.
What happens if a build installation fails?
An error message will appear in the device Event Feed. The device will revert to its previous build.
For delta builds, devices may use the full build version for the update.