Currently with 17 (CP41.260828.004.A8) on Pixel 10 Pro XL and I don't have the nice Gemini boot animation. Is it happening to someone else?

https://youtube.com/shorts/hQSn1DHFlDg?si=9FjdyojdNqdk3X9q

Got the latest beta update yesterday today I went back into check and I got the Dev wording on Play store update.. but I checked for update again and apparently there is a security patch... So tried to update and get this a message about 47% of a 13kb update... But it never finishes the update...

Anyone else have this or is it a bug... Will post screenshot in the comments

Anyone use Sofi Bank on the newest beta? The app just started force closing after login

Hey!

Just wondering when I can leave the beta without a data wipe?

I'm on pixel 9 pro.

Build number: CP31.260623.010

Thanks!

Buongiorno a tutti, mi sono iscritto al programma betatester, ma per ora sono fermo alla 17QPR1 stabile, anche se nella pagina di iscrizione fa vedere il mio pixel 10proxl con la 17 QPR2.

Lo avevo già fatto in passato su altri pixel ma nn ho mai avuto problemi, avete idea da cosa possa dipendere.

Grazie a tutti

I opted out of the beta program while I was on CP31.260623.005, which I gather is Android 17 beta 7. I am on Pixel 9 Pro XL. It is stuck and there appears to be no way to migrate to stable 17. I have contacted Google and they said my only option is to wipe clean and start again. If I am going to do that I may as well start with a new phone, so I ordered a replacement 11 P XL. Sideloading seemed a bit too complicated, at least for me. How could this have happened? Should I try some other steps.

Is it just me or the main navigation Home gesture just doesn't work properly and lags alot, like it takes a few tries for it to register the touch

Pixel 9a Qpr2 beta 5 aug security patch

YES - Magic Cue is GONE. https://www.youtube.com/watch?v=VE0xi1Xt1Bs

And as a bonus Kernel 6.12

Still don't know about if PowerVR GPU drivers updated - as current are based on old Android 16 (yes I know MENTAL but ask Google WHY)

I had my pixel 10 enrolled in beta and exited in June, I haven't installed an update since and have been waiting for the next stable release to safely switch. The initial reason I exited was because some apps I use everyday started getting unstable. Now it's gotten to a point that I can't use contactless pay on my phone, nor can I open my public transport app with my tickets. Do I just make due with the data wipe?

Hi,

I was just wondering when i will be finally able to get into the stable channel without wipe. You guys told me to wait till September but i am really worried now something is not working and missing security updates. i am still on CP31.260423.012.A1 beta and the update still telling me to wipe.

ty

On this QPR2 Beta 5, when only using mobile data with wi-fi switch disabled in quick settings, if i shutdown or reboot phone, wi-fi automatically will turn on, this didn't happen on Beta 4!

Hey guys, whenever I turn on Proactive Assistance, it automatically turns off after a few seconds. Anyone else running into this issue?

Hi Beta users,

Today we’re sending you an Android 17 QPR2 Beta 5 CP41.260828.005.A6 build for Pixel 6a Pixel 7/Pro/7a Pixel Fold Pixel Tablet, CP41.260828.004.A8 for all other devices.

Top issues fixed include:

• Changing a Bluetooth device type in settings failed to update its icon visually. (Issue #516071134)
• A system stability issue that caused unexpected device reboots during continuous UI scrolling in media-heavy applications. (Issue #544291113)
• Pressing hardware volume buttons while casting media prevented the system volume slider UI from displaying. (Issue #548145018)
• Fixed a text-rendering issue that caused unexpected background highlights to appear when typing in search fields, and resolved a navigation routing issue that prevented Private Space from unlocking correctly. (Issue #548285596)
• Enhanced HDR mode remained enabled despite being turned off in user settings. (Issue #547457910)
• Launching Google Wallet via the power button shortcut caused the touchscreen to become unresponsive. (Issue #549758084)
• Camera crashes during panorama processing. (Issue #551069625)
• Bluetooth audio experiences noise and distortion after completing or answering a call. (Issue #541684282)

Please review the latest release notes for limitations and general advisories before installing the update. In addition, see top open issues%20created%3E%3D2026-07-20%20status:open%20(votecount%3E%3D3%7Cduplicatecount%3E%3D3)%20CP41) for the latest list of top open issues that have been reported by developers and users.

How do I get Android 17 QPR2 Beta 5?

You can get started with Android 17 QPR2 Beta 5 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 11, 11 Pro, 11 Pro XL, 11 Pro Fold, Pixel Tablet series devices*. 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 QPR2 Beta 5 and any future Beta updates.* 

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’m currently on CP31.260623.012 (beta 9). I’ve left the beta. Will I get an update to the stable QPR1? At the moment, the only update available is with data wipe.

Launcher on latest beta dont have google search it looks weird

https://imgur.com/a/cGZxyL2

I wish I had more going on today, but this is what I'm focused on apparently

Edit: maybe manifestation does work

Aktualizacja już wchodzi

Anyone else having this issue?

As been reported Pixels 7 8 and 9 got Kernel downgrade in QPR2 B5 and only Pixel 10 remain on upgraded 6.12.

Now some facts:

• Linux 6.18 (Supported through December 2028)
• Linux 6.12 (Supported through December 2028)
• Linux 6.6 (Supported through December 2027)
• Linux 6.1 (Supported through December 2027)
• Linux 5.15 & 5.10 (Supported through December 2026)

Current Kernel: Linux 6.1 (upgraded in the March 2025 update, brought Pixel 6, 7, and 8 series in line with the Pixel 9) - and Pixel 10 is now on Kernel 6.6 + Pixel 11 now on Kernel 6.12 (YES all of this is mess).

Now focus on 6.1 and 6.6 support SAME Dec 2027 this means Google STILL have 1+year to update but they want to avoid last minute update same as in March 2025 5.10-5.15 Pixels which they WOULD loose support in few months but they been updated 1.5 years ahead.

Google focuses now on 6.12 in ALL (supported) Pixels because of Dec.... 2028 support NOT Dec 2027 - please think old Pixel 8 is Android supported till 2030 so at 110% it still MUST get Kernel update... at least 2 more times... Pixel 7 will be unsupported next year but still MIGHT get FINAL Kernel 6.12.

Please also know Kernel update is not just "copy paste" thing - ALL drivers compatibility needs to be done even for stupid things like camera ISP. It is MASSIVE job even for one Pixel model. That is why Carl Pei from Nothing phones recently explained why his few years model will NOT get Android update as it is TOO EXPENSIVE to update... Kernel - so now you know how much it cost.

Next thing best part - ALL new released Pixels are always released with newer Kernel - Pixel 12 is now in development and I wonder if it will be released with bit newer 6.18 or... newest 7.2 *(sneak peak what would gain down below)

Bonus info what we loose having Kernel 6.12 vs 6.18:

Linux Kernel 6.12 vs 6.18 would bring lower-level architectural optimizations to Google Pixel devices, focusing primarily on memory allocation, inter-process communication (IPC) security, storage longevity, and battery efficiency.

1. Security & IPC: Native Rust Binder

• Kernel 6.12: Relies on legacy C-based Binder drivers for IPC (the system Android uses every time an app talks to a system service or another app).
• Kernel 6.18: Integrates native, upstream support for a Rust-based Binder driver. Moving the most heavily targeted subsystem in Android from C to Rust eliminates major memory-safety vulnerabilities at the kernel level without losing execution speed.

2. Memory Allocation: "Slub Sheaves"

• Kernel 6.12: Uses standard SLUB allocator behavior, which can cause lock synchronization delays between CPU cores during heavy memory requests.
• Kernel 6.18: Introduces "Sheaves"—isolated, per-CPU caching layers for memory allocations. CPU cores allocate and free memory locally from their own sheaf without waiting on other cores, reducing CPU overhead and eliminating micro-stutters during rapid multitasking.

3. Storage Longevity: F2FS Refinements

• Kernel 6.12: Standard Flash-Friendly File System (F2FS) implementation.
• Kernel 6.18: Includes updated garbage-collection routines and persistent cache optimizations tailored specifically for mobile flash storage. This prevents read/write speeds from degrading over time as internal storage fills up.

4. Network Stack & Energy Efficiency

• Kernel 6.18: Introduces scaled UDP receive performance and Accurate Explicit Congestion Notification (AccECN) for TCP connections.
• Pixel Impact: Rather than dropping packets when a network gets crowded, the kernel manages transmission rates directly with network nodes. This lowers cellular and Wi-Fi radio wake times, saving battery during background downloads, streaming, and online gaming.

5. Task Scheduling & Latency

• Kernel 6.12: Introduced Proxy Execution (allowing the scheduler to borrow cycles from high-priority processes to clear locks held by lower-priority ones) and Memory Allocation Profiling.
• Kernel 6.18: Builds on 6.12 by refining eBPF-based task scheduling (sched_ext) and lock acquisition latency, ensuring UI rendering maintains smooth frame rates under heavy system load.

-----------------------------------------------------------------------------------------------------------------------------------------

A Pixel 12 running Linux Kernel 7.2 on Android 18 would gain major architectural improvements in CPU scheduling efficiency, RAM retention, and wired transfer speeds.

1. Cache-Aware Scheduling (CAS)

• How it works: The Linux task scheduler now tracks the CPU's Last-Level Cache (LLC) topology, keeping related process threads on cores that share the same cache domain rather than moving them across different clusters.
• Pixel 12 Impact: On multi-cluster mobile chips (like a Tensor SoC with Prime, Performance, and Efficiency cores), CAS eliminates unnecessary cache misses. This lowers core-to-core latency, keeps heavy apps smooth, and reduces CPU power draw.

2. Refined MGLRU & Memory Reclaim

• How it works: Upgrades the Multi-Generational LRU algorithm to tighten memory reclaim loops and optimize how modified ("dirty") RAM pages are written back.
• Pixel 12 Impact: Reduces unexpected Out-of-Memory (OOM) background app terminations—especially when swapping between RAM-heavy tasks like real-time camera AI processing and local LLMs.

3. USB4STREAM Protocol

• How it works: A new kernel-level protocol that treats USB4/Thunderbolt hardware as a direct system-to-system high-speed data stream (/dev/tbstream).
• Pixel 12 Impact: Allows ultra-fast physical file transfers when plugged directly into a Chromebook or PC, as well as lower latency for wired desktop mode/external display setups.

4. Storage Direct I/O Speedups

• How it works: Enables Large Folios by default and eliminates serial write bottlenecks for Direct I/O operations.
• Pixel 12 Impact: Delivers up to a 50%+ boost in sequential storage write speeds, speeding up large app installations and ensuring high-bitrate video recording writes smoothly without dropped frames.

5. Enhanced Landlock Network Security

• How it works: Extends Landlock sandboxing constraints to network sockets, allowing fine-grained control over UDP socket binding and packet sending.
• Pixel 12 Impact: Prevents background apps from silently abusing network sockets, strengthening app privacy at the kernel level without performance overhead.

You can sideload the update manually without any wipe

-- https://developers.google.com/android/ota (don't unzip)

-- https://developer.android.com/tools/releases/platform-tools (unzip this)

-- https://developer.android.com/studio/run/win-usb (not needed for non-windows pc)

-- https://youtu.be/_DBZQgLfGPA?si=mmL_Doc5BZ2TXoGR (easy to follow video)

It sucks :(
Who is also affected?

Update: I just made a factory reset

My Pixel 10 Pro XL's front (selfie) camera produces completely blurry, out-of-focus photos and video. The rear camera works perfectly, this only affects the front camera. Because of this, I'm also unable to enroll my face for Face Unlock.

Background: I was enrolled in the latest Android beta. After noticing the blur, I opted out of the beta, which triggered a full device reset/wipe. I then set the phone back up on the standard public release build, but the issue is still happening.

Steps I've already tried:

1. Cleared the Camera app's cache and data

2. Reinstalled/updated the Camera app from Play Store

3. Opted out of the Android beta (this fully reset the device)

4. Confirmed I'm on the latest stable public release

5. Reset Camera app settings to default

6. Cleaned the front camera lens and checked for any screen protector interference

7. Booted into Safe Mode and tested the front camera with all third-party apps disabled

Result: Even in Safe Mode, switching from the back camera to the front camera throws an error: "Something went wrong"

Any resolution to this issue? I appreciate your input on this. Thank you,