Android 17 QPR1 goes stable, One UI 9 lands on the S26, and the Pixel 6 says goodbye

Version check first, because this changes constantly and half the roundups you will read get it wrong. As of today, September 18, 2026, the current shipping Android version is Android 17, API level 37, originally released June 16, 2026. The current stable build on Pixel is Android 17 QPR1, which went stable September 15. The current beta is Android 17 QPR2 Beta 5, released September 16. I found no evidence of an Android 18 developer preview existing yet, though I cannot prove a negative there.

Android 17 QPR1 goes stable

On September 15, Google pushed Android 17 QPR1 to stable, build CP3A.260905.009. The security side is substantial: it carries the September 2026 patch at levels 2026-09-01, covering 115 Android issues, and 2026-09-05, covering 85 more, plus 110 additional fixes specific to Google devices. If you have been putting off an update, this is the one to take. The device list is unusually long, running from the Pixel 6 through the Pixel 11 Pro Fold, including the 6a, 7a, 8a, 9a, 10a, the Pixel Tablet, and the original Fold (Source).

On top of 20 Pixel specific bug fixes, eight of them in the UI layer alone, QPR1 brings visible changes: expanded blur effects throughout the system, a redesigned volume panel with Dynamic Color theming, a refreshed power menu, a carousel style media player, a bouncier Quick Settings animation, a Mobile Data tile toggle, a new Keyboard tile in Quick Settings, and expanded Health Connect tracking. If you build Android apps, the volume panel, power menu, and media player changes are the ones to pay attention to. Those are system surfaces, and system surface changes have a way of turning up as layout bugs in third party apps that nobody tested against them.

QPR2 Beta 5 arrived one day later

On September 16, one day after QPR1 went stable, Google shipped Android 17 QPR2 Beta 5, builds CP41.260828.005.A6 for the Pixel 6a, 7 series, Fold, and Tablet, and CP41.260828.004.A8 for everything else supported. This one is purely bug fixes, eight of them: Bluetooth device icons displaying wrong, system stability while scrolling in media apps, volume button behavior during casting, text rendering in search fields, HDR mode sticking when it should not, a Google Wallet power button shortcut that left the touchscreen unresponsive, camera crashes during panorama processing, and Bluetooth audio distortion after calls (Source).

That Wallet one is rough. A power button shortcut that freezes your touchscreen is the kind of bug that makes a phone feel broken rather than buggy. The Pixel 11 series only joined the QPR2 beta program on September 1, so it is newly in scope, and the Android Emulator is supported, which matters if you want to test QPR2 behavior without dedicating a physical device to a beta channel. Running a stable release and a beta of the next quarter within two days tells you Google is holding a tight cadence.

Samsung ships stable One UI 9.0 to the Galaxy S26 line

On September 16, Samsung began the stable One UI 9.0 rollout to the Galaxy S26, S26+, and S26 Ultra, based on Android 17 and carrying the September 2026 security patch. The build reported by beta testers is S94xNKSU4BZ16, around 550MB, and the rollout started in South Korea with other regions expected within days. One UI 9 was not brand new here, it had already shipped in stable form on the Galaxy Z Fold 8 and Z Fold 8 Ultra back in July 2026, but the S26 line is the volume seller and this is where Android 17 starts reaching large numbers of people outside the Pixel bubble (Source).

• My FanCam, auto tracking that locks onto a specific person in recorded footage and reframes around them
• Customizable Now Brief cards and Now Nudge, contextual shortcuts surfaced inside messages
• Interpreter thread view with lower translation latency
• Document scanning that corrects curved pages
• AI structured voice recorder summaries with headings and tables
• Security Brief, AI privacy alerts for suspicious apps, and Warranty and Care built into Settings

Worth noticing how much of that is Samsung's stack rather than Google's. Now Brief, Now Nudge, and Interpreter are Samsung features, not Android features. The gap between what an Android phone can do and what a Samsung Android phone can do keeps widening, and it makes "works on Android" a less meaningful statement every year.

The Pixel 6 gets its last major update

The QPR1 rollout doubles as the final major OS update for the Pixel 6 and Pixel 6 Pro. Software support ends in October 2026, and there will likely be at least one more security patch before the cutoff, which would put these phones at five years of security patches total. The context is better than it sounds: Google originally scheduled the Pixel 6 for end of life in 2024, then extended OS support by two more years, so the actual lifespan exceeded the original commitment by a fair margin. That is a genuinely useful data point when you are evaluating the newer seven year support promises (Source). Practically, this retires the entire first generation Tensor lineup, which sets a floor on the minimum Android version you will realistically find in the active Pixel install base going forward.

Play Store 53.x makes your listing copy matter more

Google's September system updates went out in two waves, September 7 and September 14. Google Play services hit v26.36 on the 14th and v26.35 on the 7th, Google Play Store hit v53.2 and v53.1 on the same dates, and Android WebView v154 shipped September 10. The Play Store changes are the ones developers should read twice. v53.2 adds a Contribution Hub cluster on the "You" tab for submitting ratings and tracking social impact. v53.1 adds key feature descriptions in "similar apps" sections, device installation visibility for app recommendations, and a new navigation bar for exploring interests on Play home pages (Source).

That "similar apps" change is the real one. If Play now surfaces key feature descriptions there, your store listing feature copy is doing organic discovery work it was not doing before. It is no longer just something a person reads after they have already found you, it is now part of how they find you at all. Worth a pass through your listings this weekend. Play services v26.36 also added real time cart price adjustment in Wallet when a user switches payment method, and v26.35 added NFC support for adding physical transit cards to Wallet.

The deadline that is not this week's news but should be on your calendar

There were no Play Store policy announcements between September 12 and 18. The most recent policy entry on the Play Console announcements page is still July 15, 2026. But the developer verification and sideloading timeline is the single most consequential near term item for Android developers, and it is close. September 30, 2026 is when user facing enforcement activates in Brazil, Indonesia, Singapore, and Thailand, expanding globally to certified Android devices in 2027. Apps from unverified developers will require the advanced sideloading flow or ADB, including a 24 hour lock period (Source). Google did launch limited distribution accounts in August 2026 for hobbyists and students, up to 20 devices, no government ID and no fee. If you distribute anything outside the Play Store, even to a handful of testers, that deadline is twelve days out.

Everything here reflects Google's own release notes and Pixel Drop post plus same-week reporting from 9to5Google, Droid Life, SamMobile, and Android Authority, linked inline. Verified September 18, 2026. If you want apps that keep your data on your device, the studio's full lineup is at jcmobileappstudio.com/apps.