Table of Contents

“Bought a phone, stopped getting updates two years later.” This complaint has existed in Android’s ecosystem for over a decade. But 2025–2026 shows genuine change: several major OEMs are taking long-term software support seriously rather than using it as marketing copy.

TL;DR

Android update landscape:

  • Google Pixel 9: 7 years OS updates + 7 years security patches (new standard from 2024)
  • Samsung Galaxy S25: 7-year update commitment, meaningfully faster One UI delivery
  • OnePlus: back to stable OxygenOS, 4 years OS + 5 years security
  • Nothing Phone: NothingOS update speed stands out in its price tier
  • Motorola Edge: among the longest update commitments in its price range (3 OS + 4 security)

What Changed: OEM Commitment Upgrades

Google Pixel’s 7-Year Commitment

Starting with Pixel 8 (2023), Google committed to 7 years of OS updates and security patches. Pixel 9 continues this standard. For a consumer buying a Pixel 9 in 2024, that’s theoretically security updates through 2031.

The technical foundation: Tensor G4’s architecture and changes to Android’s approach to older hardware support through Project Mainline, which lets many system components be updated via the Play Store rather than requiring full OTA updates.

For developers: When users may still be on an older Android version in 2031, Minimum SDK pressure to upgrade decreases. But it also means fewer users on very new API levels for a longer time.

Samsung One UI Update Speed

Samsung has historically been one of the slowest major Android OEMs for updates—sometimes 6–8 months from Google releasing a new Android version to Samsung flagships receiving it.

Galaxy S25 shows improvement: Android 16 released in June 2025; Samsung S25 received the One UI 7.x update within three months. A significant improvement.

Samsung also matched the 7-year support commitment (starting with Galaxy S24 series).

OnePlus Turnaround

OnePlus’s 2021–2022 software strategy chaos following the OPPO merger cost them heavily with core fans. OxygenOS on the OnePlus 11 era became nearly indistinguishable from ColorOS.

OnePlus 12/13 series consciously re-differentiated OxygenOS, emphasizing faster updates and closer-to-stock Android. Commitment: 4 years Android version updates + 5 years security patches.

Why This Matters

For Consumers

The TCO (total cost of ownership) calculation changes. A $700 Pixel 9 lasting 7 years = $100/year. A $400 mid-range Android with 2 years of support = $200/year. Long-term support commitments change value calculations.

For Android Developers

Longer support cycles affect the ecosystem in two ways:

API fragmentation: If users can keep 5-year-old devices and still get security updates, you may need to support Android 14 and Android 18 simultaneously. Minimum SDK upgrade pressure decreases—but so does the proportion of users who have the latest APIs.

OS updates vs. security updates: OEM “7-year” commitments usually mean OS version updates for fewer years, security patches longer. Verify what “7 years” means for a specific device—it may be 4 years of new Android versions and 7 years of security patches.

Project Mainline’s significance: Google updates system components directly via Google Play without requiring OEM OTA updates. This means some API behavior changes (like permission handling) can reach users without a full OTA. Pay attention to system behavior changes in your app even if users haven’t received an OS update.

Technical: What Determines Update Speed

  1. SoC vendor (Qualcomm/MediaTek/Google) BSP (Board Support Package): After receiving Android source, OEMs need chipmaker-specific low-level support. This is historically the biggest delay. Google Tensor builds its own chips, so Pixel has no waiting period.

  2. OEM UI customization depth: One UI is heavily customized (far more than OxygenOS), requiring longer integration time for new Android features. Nothing OS is lightly customized; updates ship faster.

  3. Carrier certification: Phones sold through carriers often need additional carrier testing and certification before updates deploy. Unlocked direct-from-manufacturer phones typically receive updates faster than carrier variants.

What to Watch

  • Whether Android 17 (expected Q4 2026) update cadence holds up for each OEM
  • Whether 7-year commitments actually deliver updates in years 5–6 or quietly only apply to flagship models
  • Whether Tensor chip architecture can genuinely sustain 7 years of performance needs (this question will be answered in future years)

References

Ask this article

Answers come from this article only. Click any prompt below or open the chat at the bottom right.

🇺🇸 English

"Bought a phone, and two years later the updates just... stopped." If you've owned an Android device, you know that complaint. It's been baked into the ecosystem for over a decade. But here's the thing — 2025 into 2026 is showing real, honest change. Several of the big phone makers are finally treating long-term software support as a promise, not just a line in a marketing deck.

Let me give you the quick lay of the land before we dig in.

Google's Pixel 9 now comes with seven years of OS updates and seven years of security patches — that became the new bar back in 2024. Samsung's Galaxy S25 matched that seven-year commitment, and just as importantly, it's pushing out One UI updates dramatically faster than it used to. OnePlus has pulled itself back from the brink with a stable OxygenOS again — four years of OS updates, five years of security. And then there are the value picks: Nothing Phone punches way above its price tier on update speed, and Motorola's Edge offers some of the longest support in its price range — three years of OS, four of security.

So what actually changed? Let's start with Google.

Beginning with the Pixel 8 back in 2023, Google committed to seven years of both OS updates and security patches, and the Pixel 9 carries that forward. Think about what that means for someone who bought a Pixel 9 in 2024 — in theory, they're covered on security straight through 2031. That's not a phone, that's a long-term relationship.

How do they pull it off? Two pieces. First, the Tensor G4 chip — because Google designs its own silicon, there's no waiting on an outside vendor. Second, something called Project Mainline. This is the clever part. Instead of every little system component needing a full over-the-air update, Google can push updates to a lot of those components directly through the Play Store. So core pieces of the system get patched almost like updating an app.

Now, if you're a developer, this cuts both ways. When people are still running an older Android version out in 2031, there's less pressure to raise your minimum SDK. But the flip side — fewer users sitting on the very newest API levels, and for a lot longer. You've got to plan for that spread.

Next up, Samsung — and this is genuinely the redemption arc of the bunch. Historically, Samsung was one of the slowest big names out there. Google would drop a new Android version, and Galaxy flagships might not see it for six to eight months. Painful. But look at the Galaxy S25: Android 16 landed in June 2025, and Samsung had the One UI update out within about three months. That's a real leap. And they matched that seven-year support pledge too, starting with the S24 line.

Then there's OnePlus, which had a rough stretch. Back in 2021 and 2022, after the OPPO merger, their software strategy kind of fell apart. OxygenOS — the thing fans loved for being clean and fast — started looking nearly identical to OPPO's ColorOS. The core fanbase was not happy. But with the OnePlus 12 and 13, they consciously walked it back. They re-differentiated OxygenOS, leaned back into faster updates and that closer-to-stock Android feel. The commitment now: four years of Android version updates, five years of security patches.

Okay — so why does any of this actually matter? Let's talk money first, because it's simpler than people think.

It comes down to total cost of ownership. A seven-hundred-dollar Pixel 9 that lasts seven years works out to about a hundred dollars a year. Now compare a four-hundred-dollar mid-ranger that only gets two years of support — that's two hundred a year. The cheaper phone is actually the more expensive phone. Long support windows completely rewrite the value math.

For developers, the ripple effects are bigger. One is fragmentation. If people can hang onto a five-year-old device and still get security updates, you might find yourself supporting Android 14 and Android 18 at the same time. Less pressure to bump your minimum SDK — but also fewer users on the shiny latest APIs.

And here's a crucial catch: read the fine print on these "seven-year" claims. Usually seven years means seven years of security patches, but fewer years of actual new Android versions. It might really be four years of new OS versions and seven years of security. So verify what "seven years" means for the specific device — don't assume.

Also, keep that Project Mainline idea in mind. Because Google can change system behavior — things like how permissions are handled — through Play services without a full OS update, your app's environment can shift even when the user hasn't "updated" anything. Watch for behavior changes regardless.

Now let's get technical for a minute — what actually determines whether an update ships fast or slow? Three big factors.

First, the chip vendor. After Google releases the Android source, phone makers need low-level support from their chipmaker — Qualcomm, MediaTek, whoever — the so-called board support package. Historically, that's the single biggest source of delay. And this is exactly why Pixel is quick: Google builds its own Tensor chips, so there's no vendor to wait on.

Second, how heavily the maker skins Android. Samsung's One UI is deeply, deeply customized — far more than OxygenOS — so integrating each new Android release takes longer. Nothing OS, by contrast, is a light touch, so it ships fast.

Third, carriers. If you bought your phone through a carrier, that update often has to pass extra carrier testing and certification before it goes out. Unlocked phones bought straight from the manufacturer usually get updates noticeably sooner than the carrier versions.

So what should we keep an eye on going forward? Android 17 is expected in the fourth quarter of 2026 — the real test is whether each maker's update cadence actually holds up when it lands. We'll also find out whether these seven-year promises truly deliver in years five and six, or whether they quietly apply to flagships only. And there's a genuinely open question about whether the Tensor chips can sustain seven years of real-world performance. Time will answer that one.

Let me leave you with the three things worth remembering. One: the seven-year commitment is real and it's spreading — Pixel started it, Samsung matched it, and that fundamentally changes how long a phone stays worth owning. Two: always check what "seven years" actually covers, because security patches and new OS versions are not the same promise. And three: update speed isn't magic — it comes down to who makes the chip, how heavy the software skin is, and whether a carrier is standing in the middle. Google wins on speed mostly because it controls the whole stack.

The bottom line? For the first time in a long time, buying Android with the long game in mind is a real, defensible choice.

🇹🇼 中文

這集直播的標題叫「phone updates」,其實藏了兩件事:一是手機相關的更新消息,二是一場 giveaway 的後續說明。而這場一次送出二十五支手機的活動,才剛結束沒多久,網路上就冒出一個很直接的質疑——這該不會是假的吧?

事情是這樣的:有人在 Reddit 發了一篇貼文,標題就是「為什麼我覺得這場 giveaway 是假的」,還把影片裡的畫面一格一格截下來分析。創作者乾脆在直播裡把這些疑點攤開來,一個一個回。結論先說:不是假的,每一個所謂的破綻,背後其實都有很直白的解釋。

先講第一個疑點:盒子上都沒有原廠封膜。質疑者發現,影片裡一大堆手機盒,沒有任何一個還包著那層收縮膜。乍看確實可疑——全新手機不是應該還封著膜嗎?但真正的原因是,dbrand 幫每一支手機都貼了皮。你想這個流程:原廠封膜的盒子,得先把膜撕掉,開盒、把手機拿出來,貼上皮,再裝回盒子闔上。手機都被拆出來過一輪了,那層封膜自然就回不去了。所以「沒有封膜」根本不是造假的證據,反而是貼皮這道工序留下的必然痕跡。

第二個疑點更主觀:有人說某些盒子敲起來空空的,好像裡面根本沒放手機。創作者對這點的回應也很乾脆——他說他實在不知道要怎麼去「量化」聲音空不空這種感覺,但他非常肯定,每一個盒子裡都確實有手機,而且全部都被拿出來貼過皮。他也在直播裡秀出當時拍的二十五支手機照片當佐證。

第三個疑點是外觀:這些盒子看起來一片空白,完全沒有印刷資訊。質疑者還特別注意到,某台 Note 8 的盒子有個外套式的 sleeve,就更好奇了,為什麼所有盒子看起來都是空的?答案其實跟隱私有關——創作者是刻意把印有 IMEI 貼紙的那一面藏起來。手機盒底部通常會貼 IMEI 標籤,而 IMEI 是每台機器的唯一識別碼,要是在影片裡公開,等於把未來得獎者手機的識別碼白白送給有心人。做法很單純:那個 sleeve 可以整個抽出來,轉個方向再套回去,把有 IMEI 的那一面轉到鏡頭拍不到的位置,於是每個盒子正面看起來就都空白了。這不是造假,是保護得獎者。

三個疑點還原完,事情就很單純了:這場 giveaway 就是二十五支手機,全部編上紅黑相間的號碼,每一支都真實存在,也都拆出來貼過皮。至於有人問「幹嘛花這麼多錢買手機來送」——創作者的態度很簡單,就是想盡量多送一點獎品,這就是他們做事的風格。

不過,比起「giveaway 是真是假」,這集真正值得你記住的,是創作者在尾聲的那個提醒:這是一場在 Twitter 跟 Instagram 上辦的活動,一定會有人冒充官方,私訊你說「恭喜你中獎了」來行騙。這幾乎是社群平台 giveaway 躲不掉的副作用。實務上你可以記幾條原則:官方帳號通常不會主動私訊、叫你點連結、付運費、或先提供個資才能領獎;收到「你中獎了」的訊息,先回到原始貼文、跟官方本人比對,別急著點對方丟給你的連結;任何要你先付一筆錢、或跟你要信用卡、要驗證碼的「領獎流程」,基本上都是詐騙。

所以總結一下今天的重點。第一,那些看起來像破綻的細節——沒封膜、敲起來空心、盒子空白——全都是貼皮工序跟保護 IMEI 隱私的結果,二十五支手機是真的都在。第二,真正該提防的不是這場活動,而是冒充官方的得獎詐騙。第三,記住那條底線:只要對方要你先付錢、或索取信用卡跟驗證碼,那就是詐騙,別讓一場真的送獎活動,變成有心人下手的藉口。

Tags