Connect with us

NEWS

Android 17 Hits 1% While Android 16 Takes a Quarter

Android 17 is on 1% of active devices in the October 19 snapshot, while Android 16 has more than tripled to 25.4% and Android 11 still holds 10.5%.

Published

on

Android 17 is on 1% of active devices in Google’s October 19 snapshot, roughly four months after it reached Pixel phones. Android 16 now leads the platform at 25.4%, more than tripling its 7.5% share from the December 1, 2025 sample. The current release still sits behind Android 8.1 Oreo, a 2017 build that holds 1.5%.

That 1% figure is the familiar early-cycle Studio dump, not a verdict on the software. The dump that actually moved is Android 16, which has locked in a quarter of the phones that check in with Play, while Android 11, shipped in 2020, still covers 10.5%.

Android 16 Holds 25.4% of Active Devices

Google no longer posts a public pie chart. The shares below are the absolute slices derived from the cumulative API-level table the company still ships inside Android Studio, covering devices that contacted the Play Store in a seven-day window. Android 16, codenamed Baklava, is the first version in this cycle to take the top slot.

THE OCTOBER 19 SNAPSHOT

Version API level Share of active devices
Android 16 36 25.4%
Android 14 34 15.3%
Android 15 35 14.7%
Android 13 33 11.8%
Android 11 30 10.5%
Android 12 31 9.6%
Android 10 29 5.7%
Android 9 28 3.1%
Android 8.1 27 1.5%
Android 17 37 1.0%

Android 14 and 15 together account for 30.0% of the sample, so the two-year-old and three-year-old releases still outweigh the leader on their own. Studio’s running total for Android 16 or newer is 26.4%, which is how the 1.0% leftover for Android 17 is inferred; the IDE does not print a separate 17 row. Devices on Android 14 or newer make up 56.4% of the check-ins. The other 43.6% are on Android 13 or older.

Android 10 still accounts for 5.7%, with Pie at 3.1% and 8.1 at 1.5%. Marshmallow is at 0.3%. Nougat 7.0 and 7.1 are at 0.2% each, matching Android 5.1 Lollipop at 0.2%. Android 5.0, which had 0.1% in the December dump, is gone from the table.

Four Months In, Android 17 Trails Oreo

Matthew McCullough, vice president of product management for Android Developer, available on most supported Pixel devices on June 16, with new hardware promised in the months after.

Today we’re releasing Android 17 and making it available on most supported Pixel devices. Look for new devices running Android 17 in the coming months.

Matthew McCullough, Vice President of Product Management, Android Developer, June 16 launch post

From that Pixel start date to the October 19 sample is roughly four months. Android 8.1 still has the larger slice at 1.5%. Combined with Android 8.0 at 0.5%, Oreo as a pair still covers 2.0% of active devices, double the current release.

That ranking is easy to mock and easy to misread. A brand-new OS always looks tiny in the first Studio dump of its life, because the sample is a Play check-in window, not a census of every phone Google has ever licensed. The fair test is the last two dumps at a similar point in the year, and those dumps do not let 17 off the hook.

How Google Counts These Shares

Google publishes these figures only inside Android Studio, as cumulative API-level totals for devices that hit Play in a seven-day span, and it updates them a few times a year rather than on a public calendar. The October set appeared around the Android Dev Summit on October 28 and 29, the first of those events in years. Phones without Google services never enter the sample.

THREE STUDIO DUMPS

  1. April 1, 2025: Android 15 is at 4.5% and Android 14 leads at 27.4%, before Samsung’s One UI 7 wave. Android 11 holds 15.9%.
  2. December 1, 2025: Android 16 is at 7.5% after Pixel, then Samsung from September, with Oppo, OnePlus, and Nothing following late in the year. Android 15 leads at 19.3%. Android 11 is at 13.7%. Android 4.4 KitKat drops off the table.
  3. October 19, 2026: Android 17 is at 1.0%. Android 16 leads at 25.4%. Android 11 is at 10.5%. Android 5.0 drops off the table.

Android 16’s jump from 7.5% to 25.4% took about ten months and a full OEM cycle. Android 15 had already reached 4.5% by April 2025, before Samsung’s One UI 7, a higher mark than 17 has now, even though that older sample sat further from Pixel day. The October 2026 window is shorter than last year’s 16 snapshot, which is the caveat Studio itself implies, and it still leaves 17 behind 15’s early curve.

One Phone in Ten Is Still on Android 11

Android 11’s 10.5% share is more than ten times Android 17’s. It also beats Android 12 at 9.6%, a reversal that has now shown up in more than one dump. In April 2025, Android 11 held 15.9% against 12’s lower slice; in December it was 13.7% against 11.4%. The 2020 release keeps declining, then keeps outranking the version that followed it.

THE STUBBORN MIDDLE OF THE PIE

  • Android 13: 11.8% of active devices, the largest slice older than 14, and past Google’s own patch window.
  • Android 11: 10.5%, still larger than Android 12 and more than ten times the current release.
  • Android 12: 9.6%, smaller than both the version before it and the version after it.
  • Android 10 and older: 11.7% once 5.7%, 3.1%, 1.5%, and the sub-1% remnants are added together.

Cheap phones that shipped with 11 and never got a major upgrade are the simplest explanation that fits the repeated ranking, and Google has not offered another. For anyone shipping an app, the practical result is the same: API 30 is not a museum exhibit. It is still one phone in ten that opens Play.

Samsung’s One UI 9 Wave Missed the Sample

One UI 9, Samsung’s Android 17 build, started reaching existing Galaxy phones in late September, first on the S26 line. In the United States, the S25 series, Galaxy Z Fold 7, and Z Flip 7 were in the stable wave around October 5, and the Fold 6 and Flip 6 followed around October 13, so those flagships could sit inside a sample dated October 19. The S24 series landed on October 20, one day after the cutoff. The S23 series landed on October 23.

Samsung told a German inquiry it had already updated 29 Galaxy models in that market, a count taken on October 29, ten days after Studio’s window. The Japan roster runs through October and November, with the Galaxy S23 FE listed for January 2027. Xiaomi, Oppo, OnePlus, Nothing, and Sony have builds in the field; Nothing OS 5.0 began landing on the Phone 3a and 4a lines at the end of October, after the snapshot.

Put those dates against the 1% slice and the picture is Pixel phones plus the first Galaxy flagships, not the A-series volume that still has to move. Last year’s 16 dump at 7.5% already included Samsung’s September start plus late Oppo and Nothing traffic. This year’s 17 dump does not. The next Studio refresh, whenever it comes, is the first one that can show the Galaxy wave as a share rather than a shipping list.

The API 36 Rule Meets a 1% OS

Play’s store rule and Play’s device sample are now a year apart. Since August 31, 2026, new apps and app updates must target Android 16, API level 36 to be submitted. Existing apps must target Android 15, API level 35, to stay offered to new users on newer phones. An extension to November 1, 2026 sits in Play Console for teams that missed the August date.

PLAY’S 2026 TARGET RULES

  • New uploads: Phone and tablet apps have to target API 36, Android 16, or the Console rejects the package.
  • Existing listings: Apps below API 35 stay on phones at that level or lower and drop out of view for people on newer builds.
  • What it does not change: Raising targetSdk does not raise minSdk, so the same binary can still run on the 10.5% still on Android 11.

Developers are compiling against Baklava while Cinnamon Bun, Android 17’s dessert name, is on 1% of the phones that show up in Studio. The store is pushing the toolchain forward on a clock Google controls. The install base moves on a clock Samsung, Xiaomi, and carriers control. Those clocks have not matched in any of the last three dumps, and the October sample makes the gap visible as a 1% row under an API 36 upload rule.

Why 43.6% of Phones Are off Google’s Patch List

Android 13 reached the end of AOSP security support in March 2026, about three and a half years after it shipped to Pixel. The March 2026 Android security bulletin is the first monthly note that no longer lists the 2022 release among patched branches. At 11.8%, that unsupported version is still the fourth-largest slice in the October sample, larger than Android 12 and larger than 17 and 8.1 combined.

Add 13 to 11, 12, 10, and everything older, and 43.6% of the devices that checked in with Play are on software Google itself has stopped patching at the platform level, or on versions that lost that support even earlier. Project Mainline and Play services still refresh some components on those phones. The kernel and the rest of the OS do not. Makers can keep shipping their own fixes after Google stops, and some do; the Studio table does not say which 11.8% of Android 13 devices still get a vendor blob.

Android 16’s rise to 25.4% is the first time in this three-dump stretch that a single recent release has taken a true quarter of the fleet. Android 17’s 1% is what the same process looks like before that OEM year has run. Google has not named a date for the next Studio dump. Until it does, the working picture is a platform whose current release is a 1% slice, whose year-old release finally leads, and whose 2020 release still covers more than one phone in ten.

Frequently Asked Questions

How Does Google Measure Android Version Share?

Android Studio shows cumulative API-level totals, not a labeled pie, for devices that contacted Google Play during one seven-day window, and the October set surfaced around the Android Dev Summit on October 28 and 29. Phones without Google Play services, including many AOSP forks and some regional models, never appear, so the 1% and 25.4% figures describe the Play-active fleet rather than every Android device ever sold.

When Did Android 17 Ship, and What Came Before the Pixel Launch?

The first public beta landed on February 13, 2026, platform stability locked with Beta 3 on March 26, and the stable build went to supported Pixel phones on June 16. Google has said Android 17 will keep getting quarterly releases, with the Q2 drop as the one that carries planned app-breaking behavior changes and a minor SDK planned for Q4.

Do Wear OS, TV, and Car Apps Have to Target Android 16 Too?

No. Wear OS and Android Automotive OS apps must target Android 15, API level 35, for new submissions, while Android TV and Android XR apps must target Android 14, API level 34. Permanently private apps restricted to one organization are exempt from the public-store rule, and the November 1, 2026 extension in Play Console applies to teams that missed the August 31 date.

When Did Android 13 Stop Getting Google Security Patches?

Google stopped listing Android 13 in the March 2026 security bulletin, after moving platform bulletins to a quarterly cadence in July 2025, which means the December 2025 patch may have been the last AOSP fix that branch received. Makers can still ship their own updates, and Mainline modules plus Play services keep moving on those devices, but new holes in the core OS are no longer closed by Google for that version.

Studio will replace this table the next time Google refreshes the IDE totals. The October 19 sample is the full public picture until that happens.

Harry is the editor of BUDGY APP, an independent title he owns and runs after ten years in journalism that began on a reporter's desk and ended up at the editor's. Numbers get particular attention here. A percentage in a business story is recomputed from the underlying figures before it goes live, a benchmark in a technology or gaming review is quoted with the conditions it was measured under, and a transfer fee or a lap time in the sports and auto pages is traced back to the club, the league or the timing sheet that published it. The same rule covers news, science, entertainment, lifestyle and travel: if a figure cannot be tied to a filing, a dataset, a transcript or a test Harry ran himself, it does not appear. Readers around the world see prices in the original currency with a conversion alongside. Errors are corrected in the open under a published corrections policy, with the change noted on the article. Questions about any figure reach him at support@budgyapp.com.

Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

Trending