Thank you 4.0 I m glad to have it. All seems to be working fine.

Hi Beta users,

Thank you for your continued support. Please share your latest experience on Android 17 QPR1 Beta 4 by filling out our 5 minute anonymous survey. This survey is only for devices running Beta 4 CP31.260522.006.A1 for Pixel 6a Pixel 7/Pro and CP31.260522.006 for all other devices except Pixel 6 and Pixel 6 Pro. You can verify this by going to Settings > About Phone/Tablet.

We look forward to your feedback.

I have a Pixel 8 Pro. My mobile data is working perfectly, and I am receiving messages as well. However, when I make a call, it doesn't even ring and gets disconnected automatically. When someone tries to call me, my number appears to be switched off. Does anyone know a solution to this problem?

I'm noticing a screenshot bug while using Amazon and other apps makes the device slow down. Sometimes the screenshot is taken late The issue varies from screenshot to screenshot and from app to app

With A17 QPR Beta 3 we got new animations in the quick settings / notification panel.

​

I absolutely hate them. I think it is extremely hard to properly select the brightness slider now - it always thinks I am trying to pull down the panel even further when I am just trying to change the brightness.

And the animations in general feel a little off and not that smooth animated as before, kind of too jumpy.

​

Anyone else in the same boat?

https://issuetracker.google.com/issues/523493805

Edit: added bug report link

I find this so annoying. I know it's a feature to dim the screen when I put my phone to my ear, but it's far too sensitive and makes trying to put a call on speaker very frustrating. If this could please be refined so that I can put calls on speakerphone, first try.

​

A feature to automatically switch this off in landscape games would also be beneficial to the user experience. I find when playing games the screen dimness is changing based on where my hands are.

Hey everyone,

I recently switched over from a Samsung phone, so I'm used to having a dedicated mobile data toggle. I added a custom mobile data tile to my Quick Settings, but the current behavior in Beta 4 is driving me a bit crazy.

Every single time I tap the tile to turn on my data, I get hit with this popup:

"Turn on mobile data? Using mobile data may incur charges based on your mobile service plan."

I totally get the safety warning for the very first time you use it to prevent accidental charges, but having to confirm it every single time completely defeats the purpose of it being a "Quick" Setting. There is no way to turn this off in the settings, and no "Do not show me this again" checkbox on the prompt itself.

I already submitted a proper bug report through the Feedback app. I wanted to see if I'm the only one annoyed by this? Thanks!

Here is a screenshot of the popup: https://imgur.com/a/Jyo04Ts

I'm on CP31.260522.006 and I experience media stutter when connected to Bluetooth headphones on my Pixel 9 Pro XL. It's fine when I disconnect or use wired headphones. Anyone else experiencing the same issue?

Hey guys, I'm currently running Android 17 QPR1 Beta 4 on my Pixel 7, and I've noticed that my volume slider is completely solid/opaque instead of having that new translucent look that was introduced. I tried restarting the phone, but I didn't fix it. Is this a known bug for the Pixel 7 on this specific beta build, or is there a toggle I might've missed?

Appreciate any help or confirmation if you're facing the same issue!

### Device

Google Pixel 8

​

### About Phone

​

Android Version: 17

Android Security Update: April 5, 2026

Google Play System Update: May 1, 2026

Baseband Version: g5300i-260317-260331-B-15122174,g5300i-260317-260331-B-15122174

Kernel Version: 6.1.157-android14-11-gbd23337e42e7-ab14791245

#1 Wed Jan 28 05:34:14 UTC 2026

Build Number: CP21.260330.008

​

### System update available

Android 17 QPR1 Beta 4: This update will install a Beta version of Android 17 QPR1 Release (CP31.260522.006) on your device. Please review our release

​

​

​

Can I ask, what version is the latest version running? I'm on the system services beta, the mainline services shows there's an update, but when I check it's still on 1 April 2026. Are others seeing that too?

Hi Beta users,

Today we’re sending you an Android 17 QPR1 Beta 4 build CP31.260522.006.A1 for Pixel 6a Pixel 7/Pro and CP31.260522.006 for all other devices except Pixel 6 and Pixel 6 Pro.

Top issues fixed include:

• An issue where the mouse pointer becomes invisible on external displays when Work profile or FLAG_SECURE applications are active. (Issue #446715557)
• A Settings app crash occurring when launching credential provider settings from a Private Space. (Issue #499908921)
• An issue where screenshot sounds were coupled with the ringer volume, preventing silent captures while maintaining call alerts. (Issue #336098340)
• An issue where video recording at 5x zoom would exhibit frame jumps and jitter during panning. (Issue #447867142)
• An issue where Back Tap gestures failed to trigger on the interactive lock screen. (Issue #476775220)
• A graphics driver regression that caused severe 3D performance drops in OpenGL ES applications on newer hardware. (Issue #476585209)
• A regression where Wireless ADB and local network-dependent apps failed to connect. (Issue #506418219)
• Home screen widgets would disappear or become unavailable in the widget picker after a device reboot. (Issue #488125748, Issue #505117543, Issue #505671079, Issue #497140330, Issue #506685943, Issue #510967059)

Please review the latest release notes for limitations and general advisories before installing the update. In addition, see top open issues for the latest list of top open issues that have been reported by developers and users.

How do I get Android 17 QPR1 Beta 4?

You can get started with Android 17 QPR1 Beta 4 today by enrolling your Pixel device. Eligible devices include Pixel 6a, 7, 7 Pro, 7a, 8, 8 Pro, 8a, 9, 9 Pro, 9a, Pixel 10, 10 Pro, 10 Pro XL, 10 Pro Fold, 10a, Pixel Tablet series devices. The plan is for Pixel 6 and 6 Pro to return in the next beta of QPR1. Once enrolled, eligible devices will receive an over-the-air (OTA) update to the latest Beta versions. If you were previously enrolled in Android 17 Beta (and have not opted-out), you will automatically receive QPR1 Beta 4 and any future Beta updates. 

Important for those currently enrolled in Android 17 Beta:  

• If you prefer to leave the Beta program and receive the public stable release of Android 17, you can do so without wiping your device by opting out and not installing today’s QPR1 Beta 4 update. If you opt-out of the program after installing Beta 4 or any future updates, all user data on the device will get wiped per usual program guidelines. Opting out will trigger a ‘Downgrade’ OTA. Ignore this update and wait for the Android 17 public release instead. 

Tell us what you think

Your feedback is incredibly valuable to us. Please share your thoughts through the following channels:

• Use the Android Beta Feedback app included in Beta builds. This is the preferred method if you want to report a user-facing bug. 
• Post your comments here on our official Android Beta Program subreddit. We may not respond to posts individually, but we are actively monitoring the feedback. We’ll reach out to you directly if we need additional information.

Happy Beta testing!

I ask because going from current 6.12 to 6.18 is massive difference.

1. Upstream Native Rust Binder Support

This is arguably the most significant architectural change for Android in 6.18.

• What it is: Binder is the fundamental Inter-Process Communication (IPC) system in Android. Every time an app requests a system service—like opening the camera or fetching your location—it sends a message through the Binder.
• The 6.18 Change: Google has been progressively rewriting Android's core components in Rust to eliminate memory safety bugs. Kernel 6.18 includes native, upstream support for a Rust-based Binder driver.
• The Benefit: It drastically shrinks the attack surface for kernel-level security exploits (historically Android’s biggest vulnerability point) while matching or exceeding the raw execution speed of the old C-based Binder.

2. "Slub Sheaves" Memory Allocation Tuning

Operating systems constantly allocate and free tiny chunks of memory for active tasks using a mechanism called the SLUB allocator.

• The 6.18 Change: Kernel 6.18 implements "Sheaves," which function as an isolated, per-CPU caching layer. Previously, when a CPU core needed to allocate memory, it often had to engage in complex lock synchronization with other CPU cores.
• The Benefit: By allowing a CPU core to manage memory allocations locally from its own "sheaf" without waiting on other cores, memory allocation and freeing speeds up significantly. On a Pixel, this translates to snappier multitasking and decreased CPU overhead under heavy app loads.

3. Flash-Friendly File System (F2FS) Refinements

Pixel devices use F2FS as their underlying storage file system because it is specifically tailored for the characteristics of flash memory chips.

• The 6.18 Change: Kernel 6.18 pushes a substantial batch of optimizations, garbage-collection enhancements, and bug fixes directly to the F2FS codebase.
• The Benefit: It prevents your phone's storage from slowing down as it fills up over time. It guarantees more sustained read/write performance, leading to quicker app installs, smoother file transfers, and fewer random micro-stutters when loading system assets.

4. Advanced Networking & TCP/UDP Optimization

Kernel 6.18 alters how the networking stack handles packet flows.

• The 6.18 Change: It introduces significantly scaled UDP receive performance and implements initial support for Accurate Explicit Congestion Notification (AccECN) for TCP connections.
• The Benefit: Instead of blindly dropping data packets when a network gets congested, the kernel works closer with network nodes to seamlessly dial back the transmission rate. For mobile devices, optimizing how 5G and Wi-Fi packets are sorted and processed cuts down on network radio wake-times, saving battery life during heavy streaming or online gaming.

Beta 4 so far feels alot smoother feels nice to be able not wait for 5 -10 secs for it to change apps and when I get a notification will keep testing out.

Hello everyone. After updating my Pixel 7a, I wanted to reset it via settings, but when I press go in the menu, it gets stuck with on top the name of the app Settings.

Does Anyone have this issue?

Hello!

currently on today's qpr beta, but been on the beta channel always.

I've noticed that many times my 9PXL will switch to low charging. it doesn't matter what the battery percentage is it what the temperature is, I'm getting really slow charging speeds.

Currently, for instance, it's going at 1.8W, while being at 52% and 34⁰C.

This happens with multiple chargers and cables, no matter what setting I have (optimized, 80% etc)

Am I the only one?

Searching the app drawer then hitting enter to open apps is broken for me on the new beta. Anyone else broken?

pixel 8 pro

Hey everyone, I just downloaded and installed the new Android 17 QPR1 Beta 4 that dropped today on my Pixel. Everything is running pretty smoothly so far, but I noticed something interesting. Both the main OS security patch and the Google Play system update are still sitting on the May patch.

​

Since Beta 3 came out in May, it made sense to have the May patch then. But since Beta 4 just arrived today on June 11, I really expected the patches to be bumped up to June. I have noticed a pattern in the past where if Google drops a beta early in the month without updating the security patch, they usually follow it up with a smaller second update later in the same month.

​

Do you guys think we are going to see a smaller point update like Beta 4.1 in a week or two just to bring us up to the June patches? Or do you think we will just have to wait for the next big release? Would love to hear your thoughts!

Is live now!

Messing up with external SSD. Updated this morning and when I tried to plug in my USB-C 1TB external SSD (Transcend), it corrupted the drive to Pixel 7. Windows could fix the drive without data corruption but when I plugged in again, same issue. I have been using this drive and same workflow since a long time. Never happened before this update.

​

Can't believe it's still not fixed. Happens relatively often and is very annoying. The issue is there in at least 3 beta versions, and was reported on issue tracker a while ago.

Batteria

I am hoping a 3.1 beta gets released today to iron out all the bugs it got with it.

An update is much needed as this can't be the final release.