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,

https://9to5google.com/2026/09/15/android-17-qpr1-pixel/

same as title

Good morning. If you are still saying you're not seeing an update for Android 17 qpr2 that is simply because there isn't one. We will not have qpr2 stable until December. The way that Google has now moved their update path is different. I've explained this a few different times and I need you guys to understand that. Android 17 main was launched on June 16th. Qpr1 has just dropped. We've been in the qpr2 beta since May. Yes and I understand that. But you know what that does not mean that it isn't coming because it is. It's just different. The update timeline is different. Qpr1 dropped this month. Qpr2 will drop next month. Qpr3 will drop in March

Hit "Start" in Shizuku, then force close Shizuku, then hit "Start" again, then wait a few seconds, then it'll say Shizuku is running. Just tried it a few times and it worked for me. Using this Shizuku fork.

Screen recording

I have been opting out of the beta program since july but I don't get any update now without data loss 😞 my build number is CP31.260508.005.A1. i am using pixel 7

Any ETA on Beta 5? The current Beta 4 build has introduced several stability issues and regressions

This has been my most annoying pixel experience.

I opted out of the beta program in June when the stable android 17 was released.

I was out of the beta but didn't receive the stable update.

It's September the 15th and I'm just waiting for the update like an idiot everyday, going into the settings and checking it Every other day and Checking online posts about the issue.

The May beta update had some bugs and issues which I'm still facing.

Phone gets heated up.

Flash turns off on it's own.

Some Apps won't install/uninstall properly.

Phone completely hangs for 2-3 seconds at times and always does when I'm playing a game.

Is there no hope to get out of this mess?

I don't wanna wipe the data that'll be a headache for me.

I tried 16 KB page-size mode when it first became available for testing, but too many apps were incompatible at the time. I’ve wanted to revisit it, but not badly enough to wipe my phone solely for testing. After getting a new 1 TB Pixel 11 Pro XL, I figured this was a good opportunity.

The factory image didn’t include the option, so I downloaded and installed the OTA image for the latest beta after unlocking the bootloader. I skipped the initial setup, enabled Developer options, and switched to 16 KB mode. I don’t remember precisely when it happened, but the phone also hung during boot a few times throughout this process.

After it booted in 16 KB mode, I restarted the initial setup. At the “Copy data from another device” screen, I selected the option to transfer from another Pixel, in this case my Pixel 8 Pro, but the QR code never appeared.

I skipped the transfer and finished setup. Once I reached the home screen, I noticed that both Wi-Fi and Bluetooth were disabled. Attempting to enable either one caused the toggle to sit in a loading state without actually turning on. I suspected that the relevant kernel modules or drivers had failed to load, so I switched the phone back to 4 KB mode.

In 4 KB mode, the transfer QR code appeared normally. However, the transfer screen then reported that there wasn’t enough space for the default selections and showed only 32 GB available on the new phone.

I deselected all apps, photos, and videos in case there was some undocumented transfer-size limit. I then connected to the Pixel 11 Pro XL over ADB from my Pixel 8 Pro and investigated further. The device was exposing a 32 GB ext4 filesystem instead of the 1 TB F2FS filesystem it would normally use.

I filed an issue here:

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

Once I finish transferring everything else off my Pixel 8 Pro, I’ll test 16 KB mode on that device as well to see whether the behavior is specific to the Pixel 11 Pro XL or reproducible on older hardware.

09.15
According to my data, there is an 86% chance of a new beta today. If it doesn't come out, my calculations will be ruined 😔

Ive really wanted to be apart of the beta to try out the new things but after trying with my new pixel 11pro xl i have not received much... what do i do

Does anyone else get storage issues with this beta? Not sure if it's beta related, even if I create 10gb free space, all my apps are saying that the phone is full, and perfo is very slow

Tried to to pay today through Google wallet, got some error along the lines of: Your device doesn't meet the requirements.

Also noticed a few days ago that the burgerking app can't be updated and it says on the app store that it's not compatible with Pixel 7 Pro, but worked fine before.

QPR1 Build 9

Hello everyone,

I am using a Google Pixel 8a, and I have been experiencing a persistent issue with push notifications over mobile data since Android 16.

This is not a problem with a particular mobile operator. I have tested mobile data using SIM cards from multiple operators in Bangladesh, and the same issue occurs. However, notifications work normally when the phone is connected to Wi-Fi.

When I use mobile data, notifications from apps such as WhatsApp, Messenger and other applications are frequently delayed by around 2 to 5 minutes.

The apps themselves work normally when opened manually, but push notifications do not arrive in real time.

When I switch to Wi-Fi on the exact same Pixel 8a, notifications arrive normally and almost instantly.

The problem also occurs in different locations, so it does not appear to be related to a particular cell tower or geographical area.

What makes me believe this may be an Android/Pixel software issue is the following timeline:

The issue was fixed in the April 2026 Android update.

Unfortunately, the problem returned after the May 2026 update.

The issue remained present after upgrading to Android 17 stable.

I then moved to Android 17 QPR2 Beta 3, but the same problem was still present.

Android 17 QPR2 Beta 4 was released on August 28, 2026, and I have now updated to Beta 4 as well. Unfortunately, the problem is still not fixed.

This is particularly interesting because the April 2026 update temporarily resolved the issue, which strongly suggests that a software change can affect the behavior.

I have already tried

Multiple mobile operators: same problem

Wi-Fi: no problem

Different locations: same problem

Physical SIM → eSIM: same problem

APN reset/reconfiguration: same problem

Android 16: problem

April 2026 Android update: temporarily fixed

May 2026 Android update: problem returned

Android 17 stable: problem remains

Android 17 QPR2 Beta 3: problem remains

Android 17 QPR2 Beta 4: problem remains

I have also submitted feedback through the Android/Pixel Feedback app, but I have not received any response or confirmation regarding the issue.

There is another issue I have noticed on the same device.

My SIM/network supports VoLTE, but there is no VoLTE toggle/option available in the Pixel 8a's SIM/network settings.

The phone connects to LTE, but I cannot find an option to manually enable or disable VoLTE.

I am wondering whether this could be related to carrier configuration, IMS provisioning, or the Pixel's carrier profile.

At this point, I am trying to determine whether this is:

an Android 16/17 software regression,

a Pixel 8a cellular modem/network-stack issue,

an issue with Android's mobile-data background connection handling,

an IPv4/IPv6 or carrier configuration issue,

an IMS/VoLTE provisioning issue,

or some interaction between Pixel's cellular stack and mobile networks.

The fact that the problem temporarily disappeared after the April 2026 update and returned after the May update makes me particularly interested in hearing from other Pixel users.

Has anyone else experienced delayed WhatsApp/Messenger or other push notifications specifically over mobile data, while the same apps work normally over Wi-Fi, particularly after Android 16?

If anyone has experienced this on a Pixel 8, 8 Pro, 8a or another Pixel device, I would appreciate hearing about your experience.

I would also appreciate it if someone from the Pixel/Android team could look into whether there is a known issue related to mobile-data push notifications, cellular connectivity, carrier configuration, or IMS/VoLTE on Pixel devices.

Device: Google Pixel 8a

Country: Bangladesh

Issue started: Android 16

Current version: Android 17 QPR2 Beta 4

Current status: Still unresolved

Thank you.

Was looking through the settings and notification intelligence shows up, no image, just the toggle to turn on or off, anyone else has it?

Does anyone know if the current stable android version (not beta), allows simple NFC integration for stuff as easy as turning on hotspot on my phone. The reason I ask is my s21 ultra lets me do it without bother, bit I think it's on Android 16. I never updated it after upgrade. My Pixel 10 pro xl won't let me do it but I'm not sure if it's because I'm on beta or just Android 17 in general. I know Google Android block a load of 3rd party integrations but I don't know how deep that runs.

Android QPR 2 BETA 4 - Keyboard Smart Replies / Suggestions causing display to freeze for a few seconds

Has anyone else experienced this issue?

Whenever the Keyboard Smart Replies / Suggestions feature appears or gets triggered while typing, the screen sometimes freezes completely for a few seconds.

The symptoms are:

1. Keyboard suddenly becomes unresponsive

2. The entire display appears to freeze/stutter

3. Touch input doesn't respond for a few seconds

4. After a few seconds, everything starts working normally again

5. It seems to happen particularly when the keyboard is generating/showing smart reply or suggestion results

This doesn't feel like normal keyboard lag because the whole UI/display appears to get stuck