Finished reading? Continue your journey in Tech with these hand-picked guides and tutorials.
Boost your workflow with our browser-based tools
Share your expertise with our readers. TrueSolvers accepts in-depth, independently researched articles on technology, AI, and software development from qualified contributors.
TrueSolvers is an independent technology publisher with a professional editorial team. Every article is independently researched, sourced from primary documentation, and cross-checked before publication.
Android 17 arrives in June 2026 with its longest eligible device list yet. But the phones being dropped from the update, including the Galaxy S22 and OnePlus 10 Pro, expose a two-tier reality in manufacturer support. Here is who makes the cut, why the cutoffs fall where they do, and what it means for your next phone decision.
Android 17, codenamed Cinnamon Bun, is on track for a stable release in June 2026. The Android Developer release notes confirm that Beta 3 reached the Platform Stability milestone, with the technical foundation frozen so app developers can finalize submissions targeting the new OS. For users, that milestone is the clearest signal yet that the June timeline is firm.
The feature list is substantial. Google is introducing floating "Bubbles" windows, which let users open any app in a resizable overlay that persists above whatever else is on screen. Unlike earlier implementations limited to messaging apps, Bubbles in Android 17 extend to every application, making it a platform-wide multitasking change. Our full breakdown of Android 17's Bubble mode covers what the feature delivers in practice, where it falls short of Samsung's long-running implementation, and which devices benefit most from the June 2026 stable release. On foldables and tablets, a dedicated bubble bar anchors these windows to the taskbar, bringing the experience closer to desktop multitasking than anything Android has offered natively before.
Other additions include native App Lock, which secures individual apps behind biometric authentication via a long-press on the icon. Separate Wi-Fi and mobile data toggles return to Quick Settings, reversing a decision from Android 14 that combined them into a single Internet tile. Lock screen widgets arrive with paginated support. For external display users, Desktop Interactive Picture-in-Picture keeps video call controls accessible while navigating other apps. Camera apps gain support for RAW14 images, a 14-bit per pixel format that was previously available only through third-party workarounds.
Beta 1 shipped in February 2026 for Pixel 6 and later devices, with two subsequent betas following before Platform Stability. Beyond Pixel devices, the OnePlus 15, Oppo Find X9 Pro, and Realme GT 8 Pro are running Android 17 betas as partner hardware. After Pixel devices receive the stable release, OEM rollouts will follow, with the broader Android 17 ecosystem expected to complete its initial wave of updates by approximately October 2026.
As of April 2026, Samsung has not yet published an official One UI 9 eligibility list, so the Samsung figures we reference are based on the company's published update policies applied to its device portfolio.
The Galaxy S22 launched in February 2022 as an $800 flagship; the OnePlus 10 Pro arrived the same month at a similar price; and the Sony Xperia 1 V shipped in 2023 with only four years of OS support promised. Three different brands, three different design philosophies, one shared outcome: all are being cut from Android 17 because they were sold under the update regime that predates both the EU regulation and the industry shift to seven-year commitments.
That pattern makes the Android 17 exclusion list more meaningful than a routine feature-gap notice. The devices losing access are not budget phones that ran out of steam on a short cycle. They are former flagships, sold at premium prices, whose update windows simply expired on schedule under the terms their buyers accepted.
The brand-by-brand breakdown below reflects the current state of manufacturer update commitments. Where official eligibility lists have not yet been published, we note it explicitly.
Google's official support page specifies that Pixel 8 and later devices receive seven years of OS and security updates from the date they first became available on the Google Store in the US. Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, and the original Pixel Fold receive five years under the same measurement.
That policy puts the entire current Pixel lineup inside the Android 17 window: the Pixel 6 series, Pixel 7 series, Pixel 8 series, Pixel 9 series, and the new Pixel 10 series are all supported. Google subsequently extended five years of full OS coverage to the Pixel 6 and 7 generations, meaning devices that many expected to max out at Android 15 will now receive Android 17. Pixel devices benefit from a structural advantage: because Google engineers both the hardware and the OS, its update pipeline has no manufacturer integration step, and updates ship on the same day as the platform release itself.
Devices fully outside Google's support window, the Pixel 5a and earlier, will not receive Android 17 and have already exited security patch coverage entirely.
Samsung's eligible list for Android 17 is the largest across any single manufacturer. Based on its published update commitments, the following devices are expected to receive One UI 9, Samsung's Android 17 skin:
Galaxy S series: S23, S23+, S23 Ultra, S24, S24+, S24 Ultra, S24 FE, S25, S25+, S25 Ultra, S25 Edge, S25 FE, and the upcoming S26 series.
Galaxy Z series: Z Fold 5, Z Fold 6, Z Fold 7, Z Flip 5, Z Flip 6, Z Flip 7.
Galaxy A series: A16, A17, A25, A26, A34, A35, A36, A54, A55, A56.
Galaxy M series: M35, M54.
SammyGuru, citing Samsung's February 2026 software roadmap, confirmed that the Galaxy S22, S22+, and S22 Ultra have been placed on a quarterly security patch schedule and that One UI 9 is explicitly outside their update scope. The Galaxy Z Fold 4, Z Flip 4, Galaxy A53, A73, and XCover 6 Pro are also excluded. The Galaxy S21 series was removed from Samsung's support roster entirely as of February 2026.
OnePlus has one of the cleaner update communication records among Android manufacturers, and its Android 17 list reflects the company's published policy directly.
The OnePlus 11, 11R, 12, 12R, 13, 13R, 15, 15R, Open, and Nord 4 are all expected to receive OxygenOS 17, built on Android 17.
The OnePlus 13 and 13R follow a four-OS-update plus six-years-of-security policy, meaning Android 17 represents one of their middle updates rather than a final one.
Excluded from Android 17: the OnePlus 10 Pro, 10T, 10R, Nord 3 5G, Nord CE 3 Lite 5G, and Nord CE4 Lite 5G. The OnePlus 10 Pro received an unexpected extension that carried it to Android 16, but Android 17 is beyond its committed window.
Xiaomi's update policy is less explicit than Samsung's or Google's, so the following list reflects expected coverage based on the company's historical pattern and known commitments rather than a formally published eligibility document.
The Xiaomi 14, 14T, 14T Pro, 15, 15T, 17, and their Pro variants are expected to receive Android 17 delivered as HyperOS 4.0.
From the Redmi line, the Note 14 and Note 15 series are expected to make the cut. From Poco: the X6 5G, X6 Pro, X7, X7 Pro, F6, F6 Pro, M7, and M7 Pro.
Devices expected to miss the update include the Xiaomi 13 series, Redmi K60 Ultra, Redmi K70 Ultra, Poco X6, Poco M6 Plus, and Mix Fold 3.
Honor provides up to seven years of updates for flagship Magic series devices. Expected to receive Android 17: Honor Magic 6, Magic 7, Magic 8 in all variants, Magic V5, Magic V6, Magic V Flip, Honor 200 series, and Honor 400 series.
Excluded: Magic 5, Magic 5 Pro, Magic V2, Magic V3, Magic VS, X50 Pro, X60 Pro, Honor 90, and Honor 90 Lite.
Oppo's Find X9, Find X9 Pro, and Find N6 are expected to receive Android 17, along with the Reno 13, Reno 14, and Reno 15 series.
Excluded are the Find X5 series, Find X6 series, Find N2, Find N2 Flip, and the Reno 11 and Reno 12 families.
From Realme: the GT 6, GT 7, GT 8 and their Pro variants are expected to make the cut. The GT Neo 5 and GT Neo 3 are not.
Motorola's situation is more nuanced. Expected to receive Android 17: the Motorola Signature, Edge 50 series including Ultra, Pro, Fusion, and Neo variants, Edge 60 series, Razr 50, Razr 50 Ultra, Razr 60, Razr 60 Ultra, Moto G56, G75, G86, and the Lenovo ThinkPhone 25.
Excluded: Edge 40 family, Razr 40 family, Moto G35, G45, G55, G85, and the original Lenovo ThinkPhone.
Nothing commits to at least three major Android updates per device. The Phone (2), Phone (2a), Phone (2a Plus), Phone (3a), Phone (3a Pro), Phone (4a), Phone (4a Pro), and CMF Phone 2 Pro are all expected to receive Android 17.
The original Nothing Phone (1) and CMF Phone 1 are not.
Sony is among the more transparent manufacturers regarding update timelines.
The Xperia 1 VI, Xperia 1 VII, Xperia 10 VI, and Xperia 10 VII will receive Android 17.
The Xperia 1 IV, Xperia 1 V, Xperia 5 IV, Xperia 5 V, and Xperia 10 V will not.
Asus announced a pause on new smartphone production in early 2026, but existing devices remain eligible for updates under the company's support commitments.
The ROG Phone 8, ROG Phone 8 Pro, ROG Phone 9 Pro, Zenfone 11 Ultra, and Zenfone 12 Ultra are expected to receive Android 17.
The ROG Phone 7 and ROG Phone 7 Ultimate are not.
There is nothing technically wrong with the Galaxy S22 or the OnePlus 10 Pro. Both remain capable hardware in 2026. The reason they are exiting the Android 17 update cycle is simpler and more structural: they were purchased when manufacturers promised shorter update windows, and those windows have now closed exactly on schedule.
The Galaxy S22 series launched in February 2022 under Samsung's then-standard policy: four major OS updates plus five years of security patches. It received Android 12 through Android 16 as its four promised OS versions. That source confirms Android 16, delivered via One UI 8, as the final major OS update for the S22 series, with One UI 8.5 arriving as a last feature refinement before the device transitions to security-only maintenance.
The OnePlus 10 Pro followed the identical trajectory. Launching in January 2022 on Android 12, it received four OS updates through Android 16 in early 2026. That fulfilled OnePlus's committed window for that device tier. Android 17 sits outside the promised boundary.
The manufacturers covered here fulfilled their original commitments on schedule, as far as our review of current documentation confirms. The problem is not that manufacturers broke their promises. The problem is that promises from 2022 were structurally shorter than what those same manufacturers now advertise for new devices.
Samsung moved to seven-year update commitments starting with the Galaxy S24 series. Google extended Pixel 6 and 7 coverage to five full OS years, meaning devices many expected to stop at Android 15 will now receive Android 17 as well. OnePlus raised its flagship policy to four OS updates plus six years of security patches beginning with the OnePlus 13. A consumer who buys a Galaxy S24 today holds hardware promised updates through roughly a decade after launch. A consumer who bought a Galaxy S22 in 2022 received the four updates their device was sold with — and that cycle is now complete.
That is the generational split the Android 17 exclusion list makes visible. The cutoff is not a failure of quality control or early abandonment. It is the exact line where the old update regime meets the new one, and the 2022 flagship cohort is the last group to experience the shorter window.
Whether that counts as a problem depends on what the buyer was told at the time of purchase. For buyers in 2026 considering a new device, the question is whether manufacturers will follow through on today's longer commitments. That requires examining the regulatory framework that was supposed to guarantee them.
The EU Ecodesign Regulation that came into force on June 20, 2025 requires manufacturers to provide software updates for at least five years after the date the last unit of a given model is sold. This "end of sales" timing matters: a phone released in September 2025 and discontinued in August 2026 must receive updates until at least August 2031.
That five-year floor was widely covered as a win for consumers. Most manufacturers responded by advertising six or seven years of support for new devices. The regulation does not cover phones already on sale before June 20, 2025, which is why it offers no protection for Galaxy S22 owners today.
The timing gap between manufacturer launch-date counting and the EU's end-of-sale measurement creates meaningful differences. Brands like Xiaomi and Honor, which have advertised five years of support from launch date, face the most direct compliance pressure. If they sell a device for a year before discontinuing it, the EU effectively requires six years of coverage counted from launch, not five. Brands claiming seven years from launch have built-in buffer. Brands claiming exactly five years from launch may need to extend that window to comply.
The European Commission has not yet issued a formal ruling on Motorola's interpretation of this regulation, and the outcome of that challenge remains unresolved as of April 2026.
The EU Ecodesign Regulation's five-year requirement took effect June 20, 2025. Its legal text in Commission Regulation 2023/1670, Annex 2, title 1.2, paragraph 6(a) specifies that manufacturers must provide updates "if they provide" them at all, and Motorola's lawyers have since argued that single conditional word means no minimum support period exists.
Gizmochina, citing ITdaily's reporting on Motorola's internal position, documented that Motorola interprets the regulation as requiring only that updates, if offered, must be provided at no charge. Since no manufacturer has ever charged for software patches, Motorola's reading would reduce the regulation to a provision that changes nothing about its current practices. Under this interpretation, Motorola could continue shipping phones with two to three years of OS support and argue full regulatory compliance.
Motorola has launched phones in Europe since June 2025 with limited security patch windows and no OS upgrade commitment. The Motorola Edge 70 in some European configurations offers more generous terms, showing the company is capable of longer commitments when market positioning demands it. The gap is not a technical limitation but a strategic choice.
This interpretation, if accepted by regulators, would hollow out the regulation for any manufacturer inclined to follow Motorola's lead. What remains unclear is whether the European Commission will formally challenge it, and on what timeline that resolution arrives.
Android updates are not primarily about features. Every monthly security bulletin that Google publishes addresses real vulnerabilities in active use against real devices. The March 2026 Android Security Bulletin flagged CVE-2026-21385 as potentially under "limited, targeted exploitation." That phrase carries specific weight in Google's terminology: it is used only when evidence exists of the vulnerability being exploited in actual attacks, not merely in research environments.
The March 2026 Android Security Bulletin we examined specifies that CVE-2026-21385 is a memory corruption flaw in a Qualcomm Graphics subcomponent. It was first reported to Qualcomm by Google's Android Security team in December 2025, patched in March 2026, and subsequently added to CISA's Known Exploited Vulnerabilities catalog. It affects well over 200 Qualcomm chipsets in widespread use across Android devices. The gap between when Google issues a patch and when it reaches an actual user device can stretch from days to months, depending on the OEM and carrier. For devices that have exited OS update coverage, that patch never arrives at all.
The scale of this monthly exposure is larger than most users realize. Each Android security bulletin patches dozens of active vulnerabilities across system, kernel, and hardware components, month after month. Android malware rose 151% in the first half of 2025, according to Malwarebytes data, as attackers targeted a growing population of devices running older, unpatched software. A device on Android 16 that receives no further OS updates does not have a fixed attack surface. That surface widens month by month as new vulnerabilities are discovered, published, and left unaddressed.
The distinction matters most at the OS architecture level. Each new Android version includes security framework changes that patches cannot fully retrofit onto older base versions. A device running Android 16 without Android 17 can receive some security patches for its existing version, but it cannot receive the architectural improvements built into Android 17's security layer. Those improvements are not features. They are structural defenses built into the OS foundation that older versions simply cannot absorb through patch delivery alone.
For most users on excluded devices, the practical risk remains context-dependent. A device used primarily for media streaming and email carries different exposure than one used for mobile banking, two-factor authentication, or work email. The risk is not theoretical, but neither is it evenly distributed. What the monthly bulletin cadence establishes is that the exposure is not static. It compounds.
A phone excluded from Android 17 does not stop working. Calls, apps, camera functions, and core features continue operating exactly as before. The change is at the security layer, and it is gradual rather than immediate.
For most devices being cut from Android 17, security patches will continue for some time after the final OS update. Samsung's pattern is to maintain security patches for approximately one year after a device receives its last major OS version. A Galaxy S22 excluded from Android 17 is not immediately unprotected. Its security window extends into 2027 before those quarterly patches wind down. During that window, using the device for lower-risk tasks while keeping a newer device for banking or authentication work is a reasonable intermediate strategy.
If the device is approaching the end of its security patch window entirely, the practical checklist is straightforward: verify the current security patch level in Settings under About Phone, check whether the manufacturer still lists the device on its security update page, and confirm whether banking or financial apps still accept the device's security certification. Many financial institutions check Android's security patch level at login and may refuse access to devices more than 90 days behind on patches.
For those evaluating a next device purchase, the update policy question requires more than reading the headline years-of-support number. Based on the update policies we documented across brands, the only transparent approach to evaluating a manufacturer's commitment is to verify the specific end-date, not just the years promised, before purchase.
Several considerations now matter at point of sale that most buyers skip. First, the headline number counts from launch date, not from when you buy the phone. A device with a stated seven-year policy sold 18 months after launch has about five and a half years remaining when it reaches your hands. Second, update delivery speed varies considerably: Pixel devices receive updates on the same day Google releases them, Samsung flagships typically receive them within 30 to 60 days, and Chinese-brand flagship devices routinely arrive three to six months behind Google's public release. A seven-year commitment delivered three months late every year covers the same calendar period but with shorter actual coverage per patch cycle. Third, verify whether the manufacturer has formally committed to the specific model or whether the policy is stated at a product-line level that may not apply uniformly.
Google's Pixel lineup and Samsung's current flagship range currently offer the clearest policy documentation and the most consistent delivery track record among major Android manufacturers. OnePlus carries a strong update history on its flagship tier, particularly since moving to the four-OS-plus-six-security framework. Brands with less transparent commitment language, or brands like Motorola whose compliance with regulatory minimums remains actively disputed, require closer scrutiny before purchase, regardless of the hardware quality they otherwise offer.
The Android 17 list will not be the last eligibility list that matters. Android 18 will draw another cutoff line, and the devices that land on the wrong side of it will be the ones purchased today with shorter-than-seven-year commitments. Checking that window before purchase is more reliable than checking it after.
In most cases, yes, but for a limited additional period. Manufacturers typically continue delivering security patches for approximately one year after a device receives its final major OS version. For Samsung devices excluded from Android 17, the Galaxy S22 series is expected to receive security patches through approximately early 2027 before those stop as well.
The critical distinction is between security patches and OS-level security architecture. Patches address specific known vulnerabilities within the existing OS framework. They cannot add the architectural security improvements that come with a new Android version. A device on Android 16 receiving security patches is better protected than one receiving nothing, but it accumulates exposure to OS-level threats that patches cannot address. Once security patch delivery ends entirely, the device is operating on a fixed and increasingly exposed software foundation with no further manufacturer support.
The EU Ecodesign Regulation that took effect June 20, 2025 applies only to phones sold on the EU market from that date forward. It offers no protection for devices purchased before June 20, 2025, regardless of where the buyer lives, and it has no jurisdiction over devices sold outside the EU.
For buyers outside Europe, update coverage depends entirely on the manufacturer's voluntary commitments and, in some jurisdictions, local consumer protection frameworks. The EU regulation has historically created spillover effects in global policy, as the USB-C mandate demonstrated when it drove Apple to standardize globally, but those effects are not guaranteed and typically lag years behind the EU implementation. Manufacturers like Motorola, whose interpretation of the EU regulation's requirements is currently contested, are under even less pressure to extend voluntary commitments to non-EU markets. Verifying the manufacturer's update policy for your specific region at the time of purchase remains the only reliable method.
The gap varies significantly by manufacturer. Pixel devices receive Android 17 on the same day Google publishes the stable release, because Google controls both the OS and the hardware without intermediary steps. Samsung's current flagships have been delivering major Android updates within approximately 30 to 60 days of Google's release, a meaningful improvement from the 90-plus-day windows common a few years ago.
Chinese manufacturers including Xiaomi, Oppo, and Realme typically deliver major Android updates three to six months after Google's stable release on their flagship devices, and the delay is longer for mid-range and budget tiers. The broader OEM ecosystem for Android 17 is expected to complete its initial rollout wave by approximately October 2026. For specific devices, checking whether your manufacturer runs a beta program and whether your model is enrolled in it is the earliest indicator of how quickly the stable update will arrive.
Android 17 eligibility information is based on manufacturer-published update policies and publicly available roadmaps as of April 2026. Official confirmation lists for Samsung One UI 9 and some other brands had not been published as of this writing. Update schedules are subject to change.