A notification says an update is available, you tap "Install", the phone restarts and a few minutes later everything is as before, or nearly so. Behind this gesture lies a fairly sophisticated mechanism, designed so that a working phone does not turn into a brick if something goes wrong. Understanding it helps you decide when to update, interpret delays and judge how long a smartphone will really last.
What OTA means
OTA stands for "over the air": the update arrives over the network, without connecting the phone to a computer. The downloaded package almost never contains the entire system, only the differences from the installed version. That is why a monthly update may weigh a few hundred megabytes, while a major version upgrade is much larger.
Types of update
| Type | Content | Typical frequency |
|---|---|---|
| major version | new features, interface changes, new APIs | yearly |
| minor update | bug fixes, small features | every few weeks or months |
| security patch | vulnerability fixes | often monthly |
| component updates | system modules, browser, services | independent of the system |
On Android a growing share of system components is updated through the app store, separately from the manufacturer's firmware. On iPhone there are rapid security responses that fix urgent issues without waiting for a full update. In both cases the system version number does not tell the whole story.
A/B partitions: updating without risk
Many Android smartphones use the A/B partition scheme, also called "seamless" updates. The phone has two copies of the system partitions:
- while you use the phone normally from copy A, the update is installed in the background on copy B;
- at the next restart the phone boots from copy B;
- if booting from copy B fails, the system automatically falls back to copy A, which has remained untouched.
The result is a short restart, without the long installation screen, and a much lower risk of the phone getting stuck. Other systems use similar techniques: the shared idea is never to overwrite the working version until the new one has proved it can boot.
Why the update does not reach everyone at once
It is normal for a friend with the same model to receive the update days earlier. There are several reasons.
- Staged rollout: the manufacturer releases the update to a small percentage of devices, monitors problem reports and only then widens distribution.
- Regional and carrier variants: the same model can have different firmware depending on the market or the carrier that sold it, with different approval times.
- The Android development chain: the base code is adapted by chip makers and then by phone makers, each with their own testing.
Checking manually in settings sometimes brings the download forward, but it does not bypass the staged rollout.
Before updating
For a monthly update little is needed. For a major version upgrade a few precautions are wise:
- battery above 50% or the phone on charge;
- enough free space: installation needs temporary room beyond the package size;
- a recent backup of photos, chats and important data;
- a stable Wi-Fi connection, to avoid interrupted downloads.
People who use their phone for work can wait a few days after a major update, long enough to see whether widespread problems emerge. Security patches, on the other hand, are best installed as soon as they are available.
After the update: why the phone seems slower
In the hours after a major update the phone may run a little warm and the battery may last less. This is not necessarily a fault: the system optimises apps for the new version, re-indexes photos and files and updates apps in the background. Usually everything settles within a day or two of use with regular charging.
End of support
Each manufacturer decides for how many years a model will receive system updates and security patches. This period is a key fact at the time of purchase, often more important than a better camera. A phone that no longer receives patches keeps working, but vulnerabilities discovered afterwards stay open.
In my work I advise checking the support policy the manufacturer states for the specific model, counting the years from the phone's release date, not from the purchase date.
In short
- OTA updates usually download only the differences from the installed version.
- A/B partitions install in the background and allow a rollback if booting fails.
- Delays come from staged rollouts, regional variants and the manufacturers' chain.
- Security patches should be installed right away; major versions can wait a few days.
- The length of software support is a decisive buying criterion.
