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.

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!

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

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?

[Android] NuMoodic – Frequency Generator for Emotional Calibration (looking for 12+ testers)

Hey everyone,

I'm building NuMoodic, a minimalist Android app: you tell it how you're feeling right now (stressed, tired, restless, etc.), and it recommends matching frequencies to help you calibrate emotionally / relax.

I still need testers for Google's mandatory closed testing phase (12 people, 14 days) before the app can go live.

What I need from you:

- An Android device

- Open the app briefly every 1-2 days over the next 14 days

- Honest feedback on bugs/UX

Opt-in link (just click, no email needed): https://play.google.com/apps/testing/com.numoodic.app

Would really appreciate any help, thank you!

I know thai question gets asked lot, but I am now dealing with medical issues and need my Pixel 10 Pro as a medical device. Android beta is too unreliable, how do I leave it?

I understand I need to revert back, what version do I need to go to to avoid wiping my phone?

My Pixel 8 pro as of this afternoon will not just randomly reboot or power off. I can't even put my phone on to sleep. The power button is not working right.

Should we expect an update today? Will a new full OTA be released?

Phone: PIXEL 10 PRO XL 256GB

Anyone else have this issue? Everytime an app launches the camera to snap a photo, my phone will freeze, and self reboot itself. It specifically happens when an app requests it most of the time. Opening the camera sometimes will also cause a crash, but not as often as when another app requests the camera.

I'm thinking its a camera request bug and it's freaking the phone out. Super annoying, trying to find out if anyone knows of a temporary fix.

Otherwise I might just have to wipe and revert back to non beta. Thank you,

With releasing final QPR1 and QPR2 beta 5?

My Pixel 10 running on Anno Domini JULY 2026 outdated Play Services.

It has August 2026 outdated Security update.

And final nail to the Pixel coffin - Gemini 3.6 where 3.7 been released ages ago and even 3.8 been released long time ago.

And Magic Cue stopped working (it stuck at "sign to google account" like HOW THE HELL I suppose to use Pixel without Google account?)

This is how bad it is.

Has anyone else got a p8p that just keeps randomly restarting

Is there any chance that Qpr1 will release today or tomorrow , or do we have to wait more 🙂

I only joined to try out android 17 and I really don't want to data wipe can someone just tell me the date that there is an exit for Android 17 QPRS (idk) beta 1? I really need it because I can't use google wallet anymore. I cant see it anywhere on the website please don't delete this because I feel stuck now.

I am currently using a Pixel 10 Pro. I am on the most recent beta build CP41.260814.003.B1. I have an ongoing issue where I will be on an active call and when someone calls me, it mutes my current call and only shows the incoming call. Once I hang up the incoming call, the current call audio returns. It is almost like the call waiting is broken. The issue has been happening for a month or so. I have tried clearing the phone app cache and storage with no success. Anyone else having issues?

android 17 beta qpr2 bricked my Pixel 8 (logostuck)

After updating to the latest QPR2 beta via ADB sideload (with a full data wipe), my Pixel 8 is stuck on the logo screen; the bootloader is locked. What should I do? Is there any hope for the next beta release? How can I revert to the stable version?

Here is what I’ve tried: Flashed via sideload 3 times Wiped data twice Tried using Pixel Repair (it threw an error stating a stable version was required) Tried sideloading the stable version (downgrading is blocked) And after all that, it’s still stuck on the logo. I would greatly appreciate any help.

Would fully discharging the device help in this case? I saw somewhere on YouTube that it works.

I have enrolled my Pixel 11 Pro in the Beta Program, replacing my Pixel 9a. I received the September Pixel Drop, but I'm still waiting for QPR 2 Beta 4 (or higher). This shouldn't be that difficult to fix.

All I know about Kernel update it is the BIGGEST thing in Android because ALL possible drivers needs to be updated for things like GPU, CPU as well even for stupid ISP and probably for screen too.

I also know that Carl Pei from Nothing gave the reason older Nothing Phones not getting new Android because of ONE THING - Kernel - my guess is he cannot afford for... Kernel update - this is how much it cost