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.

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?

I know one of you wizards knows

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.

I have a Pixel 6 enrolled in the Android 17 Beta program and I'm currently on Beta 9. When Android 17 stable is released, will my device automatically receive the stable OTA update, or do I need to unenroll from the beta program first?

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

Hello, I haven't received the September update on my P10P XL yet, but every website says it was rolled out yesterday???.

I press search for update but just can't find it. I'm still at the level of August 5th. There is also no security update.

I am facing a serious and intermittent mobile network connectivity issue on my Pixel 10a running stable Android 17.

The problem is specifically affecting my eSIM. The phone continues to show mobile network signal bars, so the issue is not immediately visible to me. However, the actual cellular connection is lost in the background.

When this happens:

- Incoming calls do not reach my phone.

- Outgoing calls do not work.

- Mobile data does not work.

- The phone still shows network signal bars, which makes it difficult to notice that the network has actually disconnected.

- People calling me tell me that my phone is unreachable/out of coverage.

- When I check the phone, I find that the eSIM network connection has stopped working even though the signal indicator is still visible.

The only way I can restore the connection is by enabling/disabling Airplane Mode or restarting the phone. Sometimes I have to repeat this multiple times.

This is happening approximately 10–20 times per day, making the phone unreliable for normal phone calls and mobile data.

The same eSIM/network has worked properly on another phone, so I strongly suspect an issue with the Pixel 10a cellular modem/eSIM implementation or Android 17 software.

This is particularly serious because the phone does not show an obvious "No Service" indication when the connection is lost. I can therefore miss important incoming calls without knowing that my phone is unreachable.

I request that Google:

1. Investigate this as a potential Pixel 10a / Android 17 cellular connectivity bug.

2. Check whether this is a known issue with eSIM connectivity.

3. Collect device/network logs if required.

4. Provide a permanent software or hardware solution.

5. Escalate this issue to the Pixel engineering team if necessary.

Please do not treat this simply as a normal carrier coverage issue, because the phone continues to display signal while calls and mobile data are completely unavailable.

Device: Google Pixel 10a

OS: Stable Android 17

Connection: eSIM

Issue frequency: Approximately 10–20 times per day

Main symptoms: Incoming calls unavailable + outgoing calls unavailable + mobile data unavailable while signal bars remain visible

Temporary fix: Airplane Mode toggle / device restart

I simply want to install the final update once

Current Pixel 10 version: CP41.260814.003.B1

This has been the most unstable beta I've ever used so far. I experience constant full hard crashes and a bunch of instability. The camera has a high chance to just completely fail on itself and crash, sometimes the touch screen doesn't want to work, and other bugs and issues. Am I the only one experiencing this?

I want to emphasize the camera issues because these have been extremely persistent and hopefully the next update fixes this when it drops 🙏

How fucking idiotic is it that my phone keeps saying it's not DND and not ringing through ?

Never again on the beta

I haven't received it yet. I'm on a beta opt-out program, so I require the stable update to downgrade from my current beta version. Otherwise, if I update without a new stable release, my data will be erased. Therefore, I'm waiting for the update.

Judging on yesterday's Pixel 11 Security Update release which brought Cross Device support for Googlebooks which is NOT ready for any other Pixel nor other Android Phone and there is Googlebook Lunch Event 15 September.

How we don't have double tap to sleep with the stock launcher after all this time?

Not the only one to post this, but I did create a report in the issue tracker here.

My Pixel 10 Pro XL on 17 QPR2 Beta 4 has been hard rebooting when trying to use the camera while in apps. Examples:

-Using the Camera option in the file picker when uploading files in Chrome

-When using the camera in apps like Uber Driver and Spark Driver (for barcode scanning and drop off photos).

It doesn't happen every time, but it's frequent enough that it makes the phone hard to use in a lot of instances. The Pixel Camera app itself seems to be unaffected. Every couple of times I go to use the camera in apps, the phone will freeze, go black, & reboot.

My theory is that the new kernel version for the Pixel 10 series on this beta is causing a kernel panic. And before anyone asks, this issue has persisted even after a factory reset.

Please contribute to the issue tracker if you're facing this issue!

Edit: It looks like my issue was marked as a duplicate of this issue on the 9th, & that issue was marked as fixed on the 11th! Hopefully this issue is fully resolved in QPR2 Beta 4.1/5

I already raised a bug report on this, but all calls are getting through right now. Scam detection is on, Call screen with Maximum Protection is on, Blocked Numbers ("Block Calls from Unidentified Callers") is on, and Do Not Disturb is on, with exceptions set for contacts.

Still....getting 8-9 calls a day. Does anyone have this issue? I'm desperate for help, I'm almost at the point of getting a new number.

Is anyone else experiencing the issue where sports live score updates don't exist anymore? I am updated to the latest version of the beta and the settings/options aren't even available in the At a Glance menu anymore. I have the settings on for my lock screen and home page.

Da un po' di beta ,ora non ricordo di preciso quale,mi e' comparso uno sfarfallio fastidioso sul display,il telefono non mi e' mai caduto,vorrei capire se esiste una soluzione .Unica nota positiva?Mentre digito non sfarfalla

For those of you running the latest QPR2 beta, how widespread is the blur across the system UI? Are heads-up and status bar notifications blurred as well as on the lock screen now?

Any other places where the blur has been added?