How long will your phone receive updates? A source-versioned support register

Direct answer: do not estimate a phone's safe support life from its age or brand reputation. Use the exact model, the manufacturer's written promise, the promise's start point, the latest delivered update, and any regional or carrier condition.

This guide includes a source-versioned sample register for Google Pixel, Samsung Galaxy, Apple iPhone, Fairphone and Xiaomi models. It is a verification method, not a permanent guarantee. The register snapshot is dated 7 August 2026 and must be refreshed before publication or purchase.

The five records people often confuse

1. Promised OS upgrades: how many major operating-system generations the vendor says it plans or commits to deliver.
2. Promised security period: how long security maintenance is promised.
3. Support anchor: the date the clock starts—global launch, first US store availability, first shipment, last sale or another event.
4. Delivered update: an update actually released for the exact model or supported model group.
5. Estimated end date: a calculation from a promise and an anchor. It is not itself a manufacturer promise.

“Seven years of updates” is incomplete unless the source says which updates, for which model, starting when and in which market.

Current sample register

The machine-readable companion register preserves the source IDs, snapshot date, scope and calculation status.

Why this is not a simple countdown

“Years” and “generations” are different

Seven OS generations is a count of major upgrades. Seven years is a time period. A phone could receive a major release late, skip a feature because of hardware, or receive security maintenance without the newest OS. Keep the fields separate.

The start date changes the answer

Google explicitly starts Pixel 8-and-later support from first availability on the Google Store in the US. It separately publishes those availability months.

Samsung says the Galaxy S25 policy runs from the global launch date and warns that timing can vary by device model, network provider and market.

If a vendor says only “six years” but the source does not give the anchor for the exact regional model, do not invent an end date.

“Up to” is not the same as an unconditional minimum

Samsung's cited regional Galaxy A16 page uses “up to” language for six OS generations and six years of security maintenance. It does not establish the exact Galaxy A16 5G promise, so that separate model remains UNKNOWN. The register preserves “up to” and does not turn it into “guaranteed until [date]”.

A delivered update does not prove the future

Apple's security-release page is strong evidence that a named model group received a named release on a date. It is not a model-specific promise about how many future years remain.

As of the 7 August 2026 snapshot, Apple lists iOS 26.6 for iPhone 11 and later, released 27 July 2026. The same history shows separate security releases for older device groups. That supports a delivered-state record, not a forecast.

How to check your exact phone

Step 1: identify the model, region and carrier

Record:

• marketing name;
• exact model number;
• country or sales region;
• carrier variant;
• current OS version;
• current security-patch level;
• purchase date and first-sale date if known.

Two phones sold under similar names can have different chips, carrier certification or regional support paths.

Step 2: find the vendor's model-level policy

Prefer, in order:

1. exact model support page;
2. official product announcement with scope footnote;
3. official security-update scope list;
4. official release notes;
5. official EOL list.

Do not substitute a retailer, search snippet or another model in the same brand.

Step 3: capture the exact wording

Copy only the material phrase and label it:

• MINIMUM COMMITMENT
• UP TO
• PLANNED
• GOAL
• DELIVERED
• UNKNOWN

Fairphone, for example, says Fairphone 5 is planned for five Android version upgrades and at least eight years of security updates, with a goal of ten years. “At least eight” and “goal of ten” must not become one ten-year guarantee.

Step 4: identify the anchor

For Pixel, Google publishes both the rule and the US Store availability month. Pixel 10 became available in August 2025 and Pixel 8 in October 2023.

For other models, use the exact source's specified global launch, regional launch, first shipment or last-sale event. If the source is silent, set the estimated end to UNKNOWN.

Step 5: separate promise from delivery

Check the current release notes or security bulletin:

• Is the exact model listed?
• Is the update a major OS upgrade or a security-only release?
• What patch date is shown on the device?
• Has the update reached the reader's carrier and region?

Google says Pixel rollouts are phased and depend on carrier and device. Fairphone says updates can be delayed by country and network operator. Samsung also attaches model, provider and market variation to its S25 policy.

Step 6: calculate only when the inputs are clear

Use:

estimated support end = documented anchor + documented period

Then label the result DERIVED ESTIMATE, not manufacturer text. Use month-level precision when the source gives only a month.

Step 7: apply a safety margin

For a purchase, do not plan to use the phone until the exact final day. Allow time for:

• staged rollout;
• carrier validation;
• data migration;
• battery or hardware failure;
• app-support changes;
• an unclear final security-release cadence.

This is Nerd Mango planning guidance, not a vendor guarantee.

Brand examples and their evidence shape

Google Pixel: clear rule plus clear anchor

Google's current policy says Pixel 8 and later receive seven years of OS and security updates from first US Google Store availability. The page lists exact included models and notes phased, carrier-dependent rollout. A second Google page publishes the availability month for each model.

That combination supports a derived month. It still does not promise that every feature reaches every device.

Samsung Galaxy: strong series promises with scope footnotes

Samsung's Galaxy S25 announcement says seven generations of OS upgrades and seven years of security updates from global launch. It also says timing can vary by model, network provider and market.

Samsung's cited Galaxy A16 (SM-A165F) product material says “up to” six OS generations and six years of security maintenance and notes that policies are subject to change. No exact Galaxy A16 5G source is active in this snapshot, so the 5G model is not assigned the same promise.

These records should not be normalised into the same certainty label.

Apple iPhone: delivered support is easier to prove than a future end

The cited Apple pages list compatible models and released security updates. They do not provide a fixed future end date for each current iPhone model.

The honest register therefore records a delivered state and leaves the future endpoint UNKNOWN. Historical longevity may inform editorial context, but it is not a substitute for a current model-specific commitment.

Fairphone: distinguish minimum, plan and goal

Fairphone says the Fairphone 5 launched with Android 13, is planned for five Android version upgrades and at least eight years of security updates, with a goal of ten. A separate end-of-sales page says software releases continue until 2031 at the earliest.

Release notes are the delivered-state check: the cited February 2026 entry shows Android 15 and a February 2026 security patch.

Xiaomi: brand-level language is not enough for a model promise

Xiaomi's security centre says it typically maintains smartphone and tablet security updates for at least two years after first shipment and publishes an EOL list. That general statement does not establish the exact Xiaomi 15 OS-upgrade count, security end date, region or carrier path. The register keeps those fields UNKNOWN until a model-specific official source is captured.

Buyer decision framework

Before buying, answer:

Stop condition: if the phone will handle banking, authentication, health or sensitive work and the security-support endpoint is UNKNOWN or already passed, do not assume continued safety. Seek a current manufacturer or enterprise-management statement, or choose a model with a clear supported window.

Maintenance and versioning

This register is useful only if every row carries:

• snapshot date;
• source URL and retrieval date;
• exact model and market;
• promise wording;
• anchor;
• calculation method;
• delivered update;
• confidence;
• change history.

Refresh monthly and immediately after a vendor policy change, major OS release, EOL-list change or correction. Never silently overwrite an old promise: add a new version and preserve what changed.

Sources

• CT-S01 — Google Pixel update policy
• CT-S02 — Google Pixel first-availability dates
• CT-S03 — Samsung Galaxy S25 support promise
• CT-S04 — Samsung Galaxy A16 support wording
• CT-S05 — Apple security releases
• CT-S06 — iPhone models compatible with iOS 26
• CT-S07 — Fairphone software-support timelines
• CT-S08 — Fairphone 5 release notes
• CT-S09 — Fairphone 5 end-of-sales support statement
• CT-S10 — Xiaomi Security Center update policy and EOL list