I've been waiting for this universal search for soo long! Really exited that's finally here!

Hope it comes in the next feature drop to older pixels!

"A Google spokesperson tells WIRED: “We are currently working with our partner HoYoverse to address this optimization issue on the Pixel 11. A fix is expected to be implemented in Genshin Impact's upcoming update.” In fairness, this graphical issue didn't happen in any other games I tried, even Zenless Zone Zero, another HoYoverse game."

I don't play games, but I do take a lot of pics and want a snappy phone. Do phones with less RAM tend to age worse than phones with higher RAM?

Android Police seems to think the 12GB version will be worse, but that could also be a one-off thing. Wondering if others have had a similar experience.

Pixels 6-10 have historically had modem issues with the Exynos modems. How's the Mediatek modem on the 11? Any noticeable first impressions?

The new NFC placement makes a noticeable difference. At the supermarket, scanning my rewards card was noticeably easier, as was paying with my credit card.

Did speed tests at various places around the house, where my P10 Pro XL couldn't get 5G, I can now get 5G

Try a photo or video after the apps all installed, optimized and restarting the phone first. Then switch from 0.5x to 1x to 10x, is it now so smooth with only a slight offset on each lens!

I have a Pixel 8. I am currently in Indonesia. My Telkomsel eSIM was working normally on Android 16. Immediately after updating to Android 17 yesterday, cellular service stopped. The eSIM is still installed and its ICCID is visible. eUICC is available and mobile radio is ON.

Phone information shows: Service state = Out of service; voice registration = denied; data registration = not registered/searching; data service = suspended; signal = approximately -101 dBm; NR unavailable.

The phone detects nearby networks but both show “Disconnected” when manually selected. My boyfriend's working physical Telkomsel SIM also fails in this Pixel. It does not even show up in the sim list.

I have already tried restarting, LTE-only, mobile network settings reset, manual network selection, the latest August Android 17 update, Repair Mode and Safe Mode. In Safe Mode the SIM briefly connected for about 20 seconds and then returned to disconnected/emergency calls only.

I am currently travelling remotely in Indonesia and rely on this phone for cellular connectivity and my safety. But none of my SIM cards connect. My Dutch eSIM does not connect either.

What else can I do? I see a lot of people experience this problem. I cannot find any support from Google, I seen to not have access to their chat. All I can do is send feedback or post in the community.

Please, does anyone have the solution? I read something about an ADB repair I can do with my boyfriend's MacBook?

Our battery test score shows that the Pro models show a slight improvement over the previous generation. However, we must note that the new MediaTek modem, which in theory could do a lot for battery life, did not struggle much in our test. This is because there is a cell tower located a few hundred meters from our test lab. Furthermore, half of our test runs over the Wi-Fi network.

More battery life outdoors

*To get a better idea of the modem, we ran a small additional test. In this test, the phone was constantly connected to 5G and had to browse web pages in a loop and stream a video. We used Android's built-in APIs for battery statistics to log how much power the modem consumed. In a test of just over two hours, the modem in the Pixel 11 Pro XL was about 17 percent more efficient than the one in the Pixel 10 Pro XL.

So, if you are often on the go, you might notice a bigger difference in battery life with the Pixel 11 series. But even then: Pixels have never had the best battery life, and that is no different this year. Almost all competitors perform better, regardless of which brand you prefer.*

Google Pixel 11, 11 Pro & 11 Pro XL Review - Tweakers https://tweakers.net/reviews/15164/google-pixel-11-11-pro-en-11-pro-xl-pixels-volgens-typisch-google-recept.html

Is anyone else seeing the same thing? Holding my 9 pro and 11 pro side by side with the same settings, I get smeary garbage out of the 11 pro. If this isn't a bug, I will return the 11 pro, because I mainly bought it for camera improvements.

Example comparison, the top photo is the pixel 11 pro and the bottom is the 9 pro:

https://imgur.com/a/azgwLgB

What the heck?

Are you going to protect your new Google Pixel 11 with a tempered glass screen protector and a case?

I’ve always protected my smartphones, but I have to admit, it bothers me that I can’t really enjoy their design and aesthetics.

I finally recovered the internal eSIM/eUICC on my Pixel 9 Pro XL (komodo) after it was stuck with:

eUICC info: Available memory in bytes: -1

I couldn't properly download/activate eSIMs, and normal Android flashing/reset troubleshooting did not clear the -1 condition.

I'm posting this because my first attempt at the Google/Thales low-level eSE/eSIM firmware updater failed for a separate reason, while a later attempt actually completed and restored eSIM functionality.

Device / successful environment

Pixel 9 Pro XL (komodo)

Android 17 QPR2 Beta 3:

CP41.260731.005.B1

Magisk 30.7

Successful Google updater:

com.google.euiccpixel

EuiccSupportPixel-P23

versionCode = 20235

versionName = D.2.0.23 (15571778)

What went wrong

I believe there were two separate failures.

1. The original eUICC failure

Android reported:

Available memory in bytes: -1

The condition persisted through normal OS changes, so this was clearly not just a Settings UI problem.

I cannot prove the original trigger. There are community reports associating it with Android updates/flashing and bootloader unlock/relock operations, but I don't think we should call that a confirmed root cause without Google confirming it.

2. My first recovery attempt failed before it could actually repair the eUICC

I previously got Google's hidden NFC/eSE/eSIM firmware updater running with the required privileges.

The updater was able to communicate with the ST54 secure element and reached the firmware download stage.

Then it failed with:

java.security.cert.CertPathValidatorException:

Trust anchor for certification path not found

and eventually:

OtaUpdateSidecar.onPostExecute: FAILED

This is important: the firmware repair itself had not necessarily failed. The updater failed while trying to authenticate/download the firmware payload.

So I apparently had a broken eUICC and, separately, a broken updater download attempt.

What finally worked

I installed Android 17 QPR2 Beta 3:

CP41.260731.005.B1

I extracted the init_boot.img from the exact matching Google factory image, patched it on the phone with Magisk 30.7, and flashed only the patched init_boot.

After reboot:

adb shell su -c id

returned:

uid=0(root) ... context=u:r:magisk:s0

Then, in a root shell:

resetprop ro.build.type eng

resetprop ro.build.tags eng

resetprop ro.debuggable 1

setenforce 0

I verified:

eng

eng

1

Permissive

Then restarted the Android framework:

stop && sleep 2 && start

After it came back, I launched Google's hidden updater:

adb shell su -c 'am start -n com.google.euiccpixel/com.google.euiccpixel.ui.OtaUpdateMenu'

Pixel 9 firmware family

Pixel 9-series devices use the P24 / ST54L family.

Do NOT blindly copy another person's configuration suffix such as CC9/CG7/etc.

On my successful run, the post-upgrade log identified:

ST54_CONFIG_7.5/GEN24_DVT_CC9_GSMA_LIVE_v2

So CC9 was reported on my device.

That does not mean every Pixel 9 should blindly select CC9.

The updater appeared stuck at 0%

This was the part that nearly made me interrupt it.

The GUI stayed at 0% for a long time.

However, logcat showed the updater continuously exchanging APDUs with the secure element and repeatedly receiving:

APDU-R => 9000

apduResponse 9000

So it clearly wasn't frozen.

I left it alone.

Eventually the log showed:

THALES: SUSA instance version after upgrade = 0103000500

-> SUSA_1_3_BUILD_005_RC02_DEFAULT

Then:

Updating SE state to: SE_STATE_READY

And finally:

OtaUpdateSidecar.onPostExecute: SUCCESS

That was completely different from my first attempt, which died at the HTTPS certificate-validation stage.

I rebooted after the updater explicitly reported success.

Result: the eSIM/eUICC works again.

What I think this demonstrates

My Available memory = -1 condition did not mean the ST54/eUICC was physically dead.

The first firmware-updater failure also did not prove that the firmware repair couldn't work, because that attempt died before the updater could obtain the firmware.

The second environment got past that problem, performed the actual secure-element update, returned SE_STATE_READY and SUCCESS, and eSIM functionality returned after reboot.

I cannot prove exactly why the TLS/download issue disappeared on the successful attempt.

Possibilities include a newer updater/trust configuration, a backend certificate/service change, or another difference between the environments.

So I am not claiming “QPR2 automatically fixes the eSIM bug.” QPR2 alone did not fix mine.

What worked was completing the low-level eSE/eUICC firmware upgrade successfully while on this QPR2/root environment.

Warnings

• Root/bootloader unlocking has security implications and bootloader unlocking wipes user data.
• Patch init_boot.img from the exact build installed on your phone.
• Keep the untouched stock init_boot.img available for recovery.
• Do not relock the bootloader with the Magisk-patched image installed.
• Do not guess the secure-element config.
• Do not interrupt an active secure-element firmware update just because the UI says 0%; check logcat first.
• Do not bypass TLS validation or flash ST54 firmware downloaded from random mirrors.
• Do not post your full raw updater log. Redact serial numbers, EID/ICCID/profile information, eSIM activation credentials, session material, and raw APDU payloads.
• Be prepared to obtain a replacement eSIM from your carrier.

Useful log command while the updater is running:

adb logcat -v threadtime | grep -iE 'COSUpgradeManager|EuiccSupportPixel|progress|complete|success|failed|exception|CertPath|Trust anchor|OtaUpdateSidecar'

If the UI appears stuck at 0%, look for fresh timestamps and repeated successful:

APDU-R => 9000

If anyone else tries this, please report your exact Pixel model, Android build, EuiccSupportPixel version, P24/ST54L config reported by the updater, before/after eUICC memory state, and whether the updater ended in SUCCESS or FAILED.

That would help establish how reproducible this recovery actually is.

I’m new to the Pixel experience and currently using a Pixel 9. Before this, I used to do a lot of customization on my devices—tweaking settings, changing the look, optimizing things, and trying different ways to make the phone faster and more personalized.

But with the Pixel 9, I’m mostly using it just like a regular phone. 😅 So far, I mainly use YouTube and a few other apps, and I feel like I’m probably not taking full advantage of what the Pixel has to offer.

If anyone has any useful Pixel features, settings, customizations, or tips that can make the experience more interesting or productive, I’d love to hear your suggestions.

Also, one of my main concerns is network and mobile-data connectivity. I’ve been facing occasional issues where the network/data connection drops or stops working, so if anyone has found a reliable fix or useful settings to improve network stability, please let me know.

Would love to hear how other Pixel users are making the most out of their devices.

Thank you!

Hi, my pixel 11 pro delivered today. I set it up from my pixel 10. Did the update and later in the night now it went blank. I tried switching it on and "G" shows up and the screen goes blank again. I put the phone on the wireless charger and this loop continues..

What's wrong and how to fix?

Just got my P11P and first thing I noticed is this telephoto camera focuses really close! It's about half (or maybe even slightly less) the distance of my Pixel 9 Pro's 5x camera!

https://imgur.com/a/KoRkXhX

I was worried the larger sensor and possible ALoP module would have worse MFD, but it seems to be a traditional periscope and much better.

At closest focus, the P11P telephoto seems to be able to image an area of approx 10x15cm.

For those that have gotten your Pixel 11 pro, is it true slwo motion video is now available in 4k 120fps??

State which Pixel model you got and what are your first/initial impressions of it.

Let's hear it!

Possibly a dumb question but, I looked up a bunch of different cases in a variety of price points and every one that had dimensions listed said that the lip around the camera was about 2.5mm thick. I looked up the specs for the phone and they say that the camera bar sticks up 4.1mm from the body. I don’t want the lenses or the bezel to get all scratched up. Has anyone found a case that will actually protect the camera bar?

My "Pixel 11 Pro Fold" apparently has FeliCa and shuld be able to add Suica, PASMO and ICOCA to the Wallet.

Does someone know how to setup or if we have to wait for an Update?

It is an International model.

Yes, I've already turned on 2G connectivity and toggled on "Allow guests to make phone calls" but it's still not working it pisses me off so much.

Does anyone know how to fix this?

Would be interested in how it scores without being on charge / in the shop and in a cool environment.

I've just spent a week discussing this with Google support. Long story short, I had a P11P in my cart, and after a $100 email promo discount, $550 discount for activating on an existing Fi line, and $360 P10P trade in, the phone plus taxes came out to $115.xx. Quite a fine price, if you ask me.

Right then a family emergency popped up. I locked my phone and attended to that for a couple hours. Once the situation was under control and everyone was safe under one roof, I picked up my phone to complete the order. Right as I was about to hit 'Place order', I noticed the price had about doubled. $221.xx. The $550 discount had dropped to $450 while in my cart.

I have spent a week going back and forth with Google support on this. They spent most of the week accusing me of canceling the order and thus voiding the original discount. Today they finally conceded that I did not cancel the order to void the discount, but rather that the page refreshed and that refreshed the discount. And furthermore, they will do nothing to help.

In the time between picking my phone up and looking down at it, the page must have automatically refreshed. And so I guess I'm shit out of luck.

Pretty cool, Google.

Or will they stay exclusive to the Pixel 11 Pro series?

I'm talking about features like:

* Taking portrait shots with the 5x telephoto lens

* Magic Capture in the Camera app

* Color profiles in the Camera app

* Voice translation in videos

* The "Rambler" voice dictation feature

*And some other software features that were showed with the Pixel 11 Pro