Tagged ota
3 pieces
- · 10 min read
Ninety Percent Is Not Success: Update Telemetry That Measures The Wrong Stage
On at least one major connected-device platform, a firmware update progress figure reaching 90 percent means the download completed, not that the install completed. Teams read it as near-success when it is the moment just before the risky part begins. Telemetry that measures the wrong stage is worse than no telemetry, because it manufactures confidence. The fix is to report download, install, reboot and version confirmation as four separate stages.
- · 10 min read
Rolling Back On A Platform That Forbids Downgrades
Platforms that enforce a strictly-higher-version rule make conventional rollback impossible, because the device will refuse any image numbered below what it is running. The technique that works is forward-versioned rollback: take the known-good older binary, relabel it with a higher version number, and the device installs it as a normal upgrade while running the old safe code. It works, it creates a bookkeeping hazard, and it does not extend your recovery boundary past devices that still check in.
- · 10 min read
A Staged Rollout Of A Bad Build Is Still A Bad Build
A rollout ladder controls how many devices a build reaches, and that is the entire extent of what it does. It cannot make the build safe. A one percent rollout of firmware that bricks on power loss bricks one percent of the fleet, permanently. The gate that asks whether the build survives an interrupted update runs before device one, and missing evidence counts as a fail rather than as a reason to proceed carefully.