Android 17: Release Date, New Features, and Which Phones Have It

Android 17 is Google's latest major Android release: it began rolling out to Pixel phones on June 16, 2026, and its first big follow-up update, Android 17 QPR1, is landing now as part of the September 2026 Pixel Feature Drop. The headline additions are an AI layer called Gemini Intelligence, stricter App Memory Limits that decide how much RAM each app is allowed to use, Post-Quantum Cryptography to protect data against future code-breaking hardware, and a set of multitasking, gaming and social-video features built around floating "Bubbles" and simultaneous selfie-plus-screen recording. Here is what actually shipped, what's official versus reported, and which phones have it.

What is Android 17?

Android 17 is the version of Google's mobile operating system that succeeded Android 16, carrying the internal codename "Android17" and API level 37. Google's own developer documentation frames the release around three pillars: an "intelligence system" that puts AI-driven context at the center of the OS, "adaptive-first" development that makes apps behave correctly across phones, tablets and foldables by default, and a set of core improvements to privacy, security, media and performance, according to the Android 17 overview on developer.android.com.

The release was formally announced in a post titled "Android 17 is Here," written by Matthew McCullough, Google's Vice President of Product Management for Android Developer, on the official Android Developers Blog. That post is the clearest single primary source for what changed and confirms the features covered below, from the new AppFunctions API to the memory and cryptography changes.

Android 17 release date: when did it come out?

Android 17 became available on June 16, 2026, rolling out over-the-air first to supported Pixel devices, with Google noting that new devices running Android 17 from other manufacturers would follow "in the coming months." Google's own build-numbering records, maintained on source.android.com's build numbers page, list the finalized public build (tag android-17.0.0_r1, build CP2A.260605.016) as locked on June 5, 2026, roughly a week and a half before the OTA rollout began — a normal gap between Google finalizing the build and pushing it to devices.

That same source.android.com table confirms the release's formal bookkeeping: codename "Android17," version "17," API level 37, CTS version 17, and a quarterly release label of "26Q2," tying the base release to the second quarter of 2026. Google develops Android 17 on a continuous basis, publishing quarterly platform releases (QPRs) after the initial launch rather than waiting a full year for the next numbered version — which is why QPR1 exists at all and why it matters for anyone asking "is Android 17 still getting updates?" (yes, continuously).

Gemini Intelligence: the AI layer built into Android 17

The feature Google leans on hardest to describe Android 17 is Gemini Intelligence, introduced at the Android Show: I/O Edition 2026 on May 12, 2026. Google describes it as a proactive layer that turns "intention into action" across phones, watches, cars and glasses — meant to work in the background to handle tedious multi-step tasks rather than waiting for a voice command or a typed prompt.

On the developer side, this is backed by a new platform API called AppFunctions, paired with a Jetpack library (in alpha at launch). AppFunctions lets any app expose specific capabilities — for example, "create a note" or "add a calendar event" — as discrete, described "tools" that an on-device AI agent can discover and call through what Google calls Android MCP, an implementation of the Model Context Protocol running locally on the device. In practice, that's the plumbing that lets Gemini reach into third-party apps and actually do something, rather than just search or summarize. Google has been expanding this agentic approach elsewhere in its ecosystem too, as covered in Pandromeda's rundown of Gemini's connected-app integrations.

Gemini Intelligence's more demanding on-device features are gated by hardware: Google's own messaging around the announcement points to Gemini Nano v3 support, a recent flagship chipset, and at least 12GB of RAM as baseline requirements for the marquee local-AI capabilities, which is part of why the feature rolled out first on the newest Pixel and Galaxy flagships rather than older or budget devices. Chips like Qualcomm's newest flagship silicon — see Pandromeda's guide to the Snapdragon 8 Elite Gen 6 — are the kind of hardware built to clear that bar.

App Memory Limits: why background apps get killed differently

App Memory Limits is Android 17's answer to a long-standing complaint: apps getting killed in the background unpredictably, or one runaway app hogging all the RAM on a phone. According to Google's official rundown, Android 17 now enforces a strict memory budget for every app, calculated from the device's total available RAM, and the system terminates any process that exceeds its allotted limit rather than letting memory pressure degrade the whole device.

This sits alongside a handful of other performance changes Google grouped under the same "core improvements" umbrella: a generational garbage collector that runs smaller, cheaper collections on young-generation objects instead of periodic full sweeps, a lock-free MessageQueue intended to cut missed frames and speed up app startup, and R8 bytecode optimizer improvements that shrink an app's memory footprint at build time. Together, Google's stated goal is fewer dropped frames and fewer background apps getting force-closed without warning — though how noticeable that is will vary by device and how much RAM it shipped with.

Post-Quantum Cryptography: future-proofing app signatures

Android 17 is also the first version of Android to ship built-in Post-Quantum Cryptography (PQC), a response to the long-term threat that sufficiently powerful quantum computers could eventually break the cryptographic signatures Android currently relies on. Per Google's own developer documentation, compatible devices can now generate ML-DSA keys in hardware to create quantum-resistant digital signatures, and Android 17 introduces APK Signature Scheme v3.2, which combines a traditional signature with an ML-DSA signature in a hybrid scheme to protect how apps are distributed and verified.

Google paired that with several smaller security and privacy changes in the same release: a system-level contact picker that only shares the specific fields an app asks for, a customizable photo picker, a system-rendered one-time precise-location button, a new ACCESS_LOCAL_NETWORK permission for apps that want to reach devices on a user's home network, and a rule that delays a same-device app's access to an incoming SMS one-time code for three hours if it wasn't the intended recipient — closing off a common OTP-interception trick. None of these individually make headlines, but they're the kind of plumbing changes that quietly narrow how apps can misuse Android's permission model.

Multitasking, gaming and social video upgrades

Android 17's most visible day-to-day changes are less about AI or cryptography and more about how people actually use their phones. Google's own developer blog post confirms App Bubbles — the ability to collapse essentially any app into a small floating window that can be dragged, stacked and reopened with a tap — plus a dedicated Bubble Bar that docks those bubbles on tablets and foldables, a fully interactive desktop-style Picture-in-Picture mode, and "Continue On," a handoff feature for picking a task back up on a different Android device.

Alongside that, Google's rollout messaging for Android 17 highlighted two features aimed squarely at content creators: a reworked screen-recording toolbar with a mode commonly described as "Screen Reactions," which layers a selfie-camera feed over a screen recording so creators can react to their own screen without a separate camera app, and a foldable-focused gaming layout that splits the display roughly in half — game view on top, an on-screen gamepad below — while Google's performance work elsewhere in the release (the generational garbage collector and memory changes above) is aimed at reducing frame drops during graphics-heavy play. These consumer-facing features were described consistently across outlets covering Google's June 2026 Pixel Drop, though Google's own consumer-facing copy for them is spread across store listings and in-app release notes rather than a single archived developer page.

Android 17 QPR1: what's landing in September 2026

QPR1 — Quarterly Platform Release 1 — is the first scheduled update to Android 17, carrying API level 37.1. Google ran it through a public beta program starting with Beta 1 on April 22, 2026 and continuing through nine beta builds, ending with Beta 9 on August 17, 2026, according to the official Android 17 QPR1 release notes. QPR1 hit Platform Stability — meaning its APIs, app-facing behaviors and non-SDK lists were locked — at Beta 6, dated July 1, 2026, which is the point developers could safely build against its final API surface.

By Google's own description, QPRs like this one are meant to ship "bug fixes and improvements without app-impacting API changes," distributed to consumers through Pixel Feature Drops rather than as a headline OS upgrade. That lines up with what shipped: Google's own September 2026 Pixel Drop announcement centers on a visual refresh — Material 3 Expressive design language and new "Live effects" personalization — arriving on "Pixel 6 and newer, and Pixel Tablet," alongside an expansion of Scam Detection to more countries and languages, a wider rollout of the Pause Point wellbeing feature, and updated Pixel VIP contact widgets.

Google's release notes don't publish a single fixed calendar date for QPR1's move to stable in the way the original Android 17 launch date was announced; multiple outlets tracking the beta program have reported the stable build arriving in mid-September 2026 bundled with that Pixel Feature Drop, so treat any specific day-of-month date for QPR1's stable rollout as reported rather than officially confirmed. What is confirmed directly from Google is that QPR1's API surface froze on July 1, 2026, and that the September Pixel Drop — which Google has confirmed rolled out in September 2026 — is the vehicle Google uses to distribute QPR-level updates to consumers.

Which phones have Android 17 and QPR1?

Pixel phones remain the first and, so far, most complete way to get Android 17. Google's own developer blog post lists the June 2026 launch as covering "most supported Pixel devices," and Google's September Pixel Drop materials specifically confirm Pixel 6 and newer, plus Pixel Tablet, as eligible for that update's features. Reporting on the September rollout has additionally listed the Pixel Fold, Pixel 6a/7a/8a/9a/10a, and the Pixel 9, 10 and 11 series (including their Pro, Pro XL and Pro Fold variants) as in scope for QPR1 specifically — consistent with Google's stated policy of supporting Pixel 6 and later across the Android 17 cycle.

Beyond Pixel, Android 17 doesn't arrive on other brands' phones on launch day, because manufacturers layer their own skins (One UI, OxygenOS, and so on) on top of the Android base and need time to adapt them. Google's own developer post names Honor, iQOO, Lenovo, OnePlus, OPPO, Realme, Sharp, vivo and Xiaomi as Android 17 beta partners — meaning their engineering teams had early access to Android 17 to prepare their own builds, not that consumer devices from those brands shipped Android 17 in June. Samsung's own rollout follows a separate timeline tied to its One UI releases; Pandromeda has covered that in detail in its look at the One UI 9 rollout schedule.

Android 17 vs. Android 16: what actually changed

Compared with Android 16, the biggest structural shift in Android 17 is that AI moved from being a feature bolted onto specific apps to a platform-level capability any app can plug into through AppFunctions and Android MCP. The second big shift is enforcement: where earlier Android versions offered guidance and opt-outs around large-screen layouts and memory usage, Android 17 removes the opt-out for large-screen resizability restrictions and actively kills processes that exceed their memory budget, rather than just recommending developers behave well. Security-wise, Post-Quantum Cryptography is a genuinely new capability rather than an iteration on an existing one — Android 16 had no equivalent hardware-backed quantum-resistant signing path.

Should you install Android 17 QPR1 now?

If your Pixel is offered the update, there's little reason to hold off: QPR releases are, by Google's own description, meant to be bug-fix and stability updates without the kind of app-breaking API changes that sometimes accompany a full numbered release, and QPR1 specifically has been through nine public betas and a platform-stability milestone before reaching consumers. The trade-off is that QPR1 is genuinely light on new features for most people — expect a visual refresh, expanded Scam Detection, and small quality-of-life changes rather than another wave of AI capabilities, which Google has generally reserved for its numbered releases and its I/O-timed announcements.

What's next for Android 17

Android's continuous release model means Android 17 doesn't stop at QPR1. Google's own build and API-level numbering already earmarks API level 37.2 for QPR2, which typically follows a few months after QPR1 on the same beta-then-stable cadence, and Google has signaled that further Gemini Intelligence capabilities will keep expanding to more device categories — watches, cars, glasses and Chromebooks — through the rest of 2026, beyond the phones that got it first. Meanwhile, non-Pixel manufacturers that received Android 17 as beta or GSI partners are expected to fold it into their own skinned updates on their own schedules over the following months, with Samsung's One UI cycle among the ones worth watching most closely given its market share. The next milestone to watch for is Android 18's developer preview, which — if Google keeps its recent cadence — would be expected in the first few months of 2027.

Written byNadia Osei

Nadia Osei covers mobile and consumer gadgets for Pandromeda: smartphones, tablets, smartwatches, earbuds and smart-home devices. She tracks launches, software updates and pricing across Apple, Google, Samsung and the rest, and builds comparisons from the manufacturers' published specifications.

More from Nadia OseiAll Mobile & Gadgets coverage