Google started the stable Android 17 rollout on June 16, 2026, beginning with supported Pixel devices. Your update date depends on your manufacturer, not on Google. This guide covers the new features, the developer-facing behavior changes, the brand-by-brand eligibility picture, and the terminal commands to verify your build.
Quick Takeaways
- Release: Android 17 (codename Cinnamon Bun) went stable on June 16, 2026. Pixel 6 and newer receive it first.
- Headline features: App Bubbles, real-time location indicators, RAM-based app memory limits, and stronger theft protection.
- Samsung: One UI 9 is built on Android 17. It shipped on the Galaxy Z Fold 8 and Flip 8, with older Galaxy models staggered.
- Rule of thumb: Most flagships launched in 2023 or later are eligible. Budget phones and older models are the ones to verify.
| Brand | Android 17 Skin | Status (as of Oct 2026) |
|---|---|---|
| Google Pixel | Stock Android | Stable, Pixel 6 and newer |
| Samsung | One UI 9 | Shipping on new foldables, S-series rolling out |
| Xiaomi / Redmi / POCO | HyperOS | Flagships first, rest staggered (reports conflict) |
| OnePlus | OxygenOS | Expected late 2026 |
| Others | Vendor skins | Flagships first, mid-range later |
What Is New in Android 17
Android 17 uses a different release model from earlier versions. Traditional Developer Previews are gone, replaced by continuously updated Android Canary builds. The platform also takes a major release in Q2 and a minor SDK release in Q4, with QPRs in between.
One detail matters for OEM phones. Many features that went live on Pixels through the Android 16 QPR releases reach other manufacturers’ phones as part of the Android 17 platform update. A “new” feature on your Galaxy or OnePlus may already have been on Pixels for months.
App Bubbles and Multitasking
App Bubbles turns any app into a floating window on top of other apps. Foldables and large-screen devices also get a bubble bar at the bottom of the screen to manage them. Foldables get a 50/50 game layout with the game on one side and a dynamic gamepad on the other. Google says it will roll out in the coming months.
Privacy and Permissions
- Location indicators: Android 17 adds a real-time location icon to the status bar. It appears when a non-system app accesses location in the foreground, then settles into a persistent dot. Tapping it shows which apps are tracking you.
- Contact picker: You can share only selected contacts with an app instead of your entire contact list.
- Local network protections: Apps targeting Android 17 or higher have local network access blocked by default.
Security and Theft Protection
Android 17 hardens Factory Reset Protection, making it harder for thieves to wipe and resell a stolen phone. Other safeguards carried over from the 16 QPR cycle include Identity Check (now extended to apps and watches), Secure Lock Device, and updated Advanced Protection Mode safeguards. Find Hub also gets new security and safety features.
Performance: App Memory Limits
Google is introducing app memory limits based on a device’s total RAM, aiming for a more stable, deterministic environment. A single leaking app can no longer starve the rest of the system. Expect more predictable behavior on 6 GB and 8 GB devices.
Interface Changes
- Separate toggles: Wi-Fi and Mobile Data are now two separate Quick Settings tiles.
- Force Dark Mode: Applies dark mode to all apps, with a per-app opt-out.
- Blur effects: Heavier frosted-glass blur in the notification shade, volume panel, and power menu. Carried-over settings let you disable background blur.
- Enhanced HDR brightness: Better SDR/HDR blending in feeds.
- Lock screen widgets and Material 3 Expressive carry over from the Android 16 QPRs.
- Screen Reactions: Screen recording can capture your reaction through the selfie camera.
- Android Switch: A rebuilt iOS-to-Android migration flow.
Features Still in Testing
Google is testing Android 17 QPR2 with native App Lock, expanded Dynamic Color, customizable Quick Settings, lock-screen blur, and status-bar customization. Treat these as unconfirmed for any stable build until your vendor’s changelog lists them.
Android 17 Developer and SysAdmin Changes
Fleet admins and app developers should check these behavior changes before rolling out to managed devices.
| Change | Impact | Who It Affects |
|---|---|---|
| Local network blocked by default | Apps targeting 17+ lose LAN access unless granted | IoT, casting, printing, and discovery apps |
| Native library DCL protection | Native files loaded with System.load() must be read-only first when targeting 17+ |
Apps that unpack .so files at runtime |
| Per-display desktop windowing | Desktop windowing can be enabled per display | External display and tablet workflows |
| OTT call autorouting | Voice and video calls from OTT apps can route to premium network connections | VoIP and conferencing apps |
| Hardware-wrapped keys | Simplified implementation | OEMs and security teams |
| OpenJDK 21 and 25 features | Newer language APIs and TLS group support | Developers |
Which Phones Get Android 17?
Eligibility follows each manufacturer’s update policy. The lists below combine official announcements with reported policy-based estimates, so confirm your exact model with your vendor.
Google Pixel (Stable Now)
Android 17 is officially available for Pixel 6 and newer, including the Pixel Fold and Pixel Tablet. The Pixel 10 series is included. Pixel 5 and older are not.
Samsung Galaxy (One UI 9)
One UI 9.0 is based on Android 17 and launched on the Galaxy Z Fold 8 and Z Flip 8. The Galaxy S26 series has begun receiving the update, with the S25 series and the A57, A34, and A17 lines expected soon.
| Series | Likely Eligible | Notes |
|---|---|---|
| Galaxy S | S26, S25 (incl. Edge, FE), S24, S23 | Flagships first |
| Galaxy Z | Fold/Flip 8, 7, 6, 5 | Fold 8 and Flip 8 ship with it |
| Galaxy A | A57, A56, A55, A54, A37, A36, A35, A34 and newer budget A-series | Staggered rollout |
| Galaxy M / F | Recent M and F models | Typically last |
| Galaxy Tab | Tab S11, S10, S9 series and others | Verify per model |
Sources disagree on older hardware. One tracker lists the Galaxy S22 series as receiving a final major OS update under its 4-year guarantee, while another estimate excludes the S22 and older. Check Settings > Software update or Samsung’s support page for your model.
Xiaomi, Redmi, and POCO
Eligible Xiaomi flagships include the Xiaomi 17, 17 Ultra, 17T, 17T Pro, the 15 and 14 families, and the 13T and 13T Pro. Redmi and POCO models follow. Skin naming differs between sources (HyperOS 3.3 versus HyperOS 4), so rely on Xiaomi’s own update announcements.
OnePlus
The expected list includes the OnePlus Open, 15, 15R, 13, 13R, 13s, 13T, 12, 12R, and 11, plus recent Nord models. OnePlus usually follows Pixel and Samsung by a few months.
Motorola, Nothing, Vivo, OPPO, Realme, Sony, and Asus
Recent flagships from OnePlus, Oppo, Vivo, iQOO, Nothing, Motorola, Realme, Xiaomi, and Poco are expected to be eligible, and most phones launched in 2023 or later qualify. Mid-range models are the least predictable.
Phones Unlikely to Get It
| Brand | Likely Excluded |
|---|---|
| Pixel 5 and older | |
| Samsung | Galaxy S21 and older (S22 disputed), early foldables |
| Xiaomi | Xiaomi 13 and older, Redmi Note 13 and older |
| OnePlus | OnePlus 10 series and older |
Step-by-Step: Check and Install Android 17
Step 1: Verify Your Current Build
On the device, open Settings > About phone > Android version. Over USB with debugging enabled, run:
adb shell getprop ro.build.version.release
adb shell getprop ro.build.version.sdk
adb shell getprop ro.build.version.security_patch
ro.build.version.releasereturns the Android version string.ro.build.version.sdkreturns the API level. Android 17 should report 37.ro.build.version.security_patchreturns the patch date.
Step 2: Check for OTA Updates
Go to Settings > System > Software updates > System update on Pixels. On Samsung, use Settings > Software update > Download and install. Staged rollouts mean your device may show nothing for days or weeks.
Step 3: Back Up Before Updating
adb backup -apk -shared -all -f backup.ab
adb backup is deprecated and unreliable on modern builds. Prefer Google One backup or Samsung Smart Switch. Copy /sdcard/DCIM and /sdcard/Documents to a computer before any major OS jump.
Step 4: Sideload the OTA (Pixels, Advanced)
If the staged rollout skips you, download the official OTA package for your exact model, then boot to recovery and select Apply update from ADB:
adb sideload your-ota-package.zip
Match the build ID and device codename exactly. A wrong package fails signature verification and does no harm. A wrong factory image flash can wipe data.
Step 5: Verify After Install
adb shell getprop ro.build.version.release
adb shell dumpsys package com.example.app | grep targetSdk
The second command shows the targetSdk of an installed app. Use it to find apps that now fall under the new local network and native-loading rules.
Troubleshooting Android 17 Problems
Fixing a Bootloop After the Update
- Hold Power + Volume Down to reach the bootloader or recovery.
- Select Reboot to recovery, then try Wipe cache partition where available (not offered on all devices).
- If it still loops, use Factory data reset. Back-up-first applies, because this erases user data.
- On Pixels, reflash the factory image as a last resort:
fastboot flash bootloader bootloader.img
fastboot reboot bootloader
./flash-all.sh
flash-all.sh wipes the device unless you remove the -w flag from the script.
Fixing Battery Drain After Updating
Heavy post-update indexing is normal for 24 to 48 hours. If drain continues, inspect per-app usage:
adb shell dumpsys batterystats --reset
# use the phone normally for a day, then:
adb shell dumpsys batterystats > batterystats.txt
--reset clears old counters so the new capture reflects only post-update behavior.
Apps Crashing or Closing in the Background
RAM-based memory limits can terminate apps that previously ran unchecked. Check an app’s footprint:
adb shell dumpsys meminfo com.example.app
Look at TOTAL PSS. Update the app first. If the crash persists, report it to the developer with this output attached.
Smart Home or Casting Apps Cannot Find Devices
Apps targeting Android 17 lose local network access by default. Open Settings > Apps > [App] > Permissions and grant the local network permission if it appears. Admins managing a fleet should test discovery apps before pushing the update.
Feature Missing After Updating
Google lists features per release, and OEMs implement them on their own schedule. A missing App Bubbles option on a third-party skin usually means the vendor has not enabled it yet, not that the update failed.
FAQ
When did Android 17 come out?
Android 17 stable was released on June 16, 2026. Pixels received it first, and other manufacturers follow with their own timelines.
Will my Samsung Galaxy get Android 17?
Most Galaxy S, Z, A, M, F, and Tab models from 2023 onward are expected to receive it through One UI 9. The Galaxy S26 series has started receiving it. Check your model in Settings > Software update.
Is Android 17 worth updating to?
Yes, for most users. The update brings stronger theft protection, location indicators, RAM-based app limits, and better multitasking. If you rely on smart home or casting apps, wait a few days and confirm that your apps have updated first.
Which Pixel phones support Android 17?
Pixel 6 and later devices receive it. That covers the Pixel 6 through Pixel 10 series, the Pixel Fold, and the Pixel Tablet. Pixel 5 and older do not receive it.
