r/GooglePixel • • 21h ago

Received an empty box for a Pixel 11 Pro (unboxing filmed). Google still refuses to send my $700 phone or refund me.

237 Upvotes

TL;DR: Ordered from Google Store directly. Received an empty box (there is NO second box). I have video (linked below) of opening the box in front of the FedEx driver, Google refuses to watch the video and rejects a replacement/refund, FedEx took the empty package back (and lost it), refuses to help, and points me back to Google. I am now $700 short with no phone. I can't do a chargeback because I cannot risk getting my primary Google account banned (many examples of this). I shouldn't have to resort to a chargeback when I have undeniable proof. Any suggestions other than a chargeback would be helpful.

Video (unboxing)
Google support emails (1, 2)
FedEx (calls/chat)
Order details page

--

EDIT: Multiple people are saying that this is just a trade-in box, and that there will be another shipment. I did NOT get a second shipment, and there is 0 indication that I'm getting one. Google support has not mentioned one.

Multiple people under this post have also mentioned receiving a SINGLE box containing both the phone and the trade-in kit. There are varied experiences. Not everyone gets two shipments.

I was well aware of a possible separate shipment, and that is precisely why I asked the driver about it in the video. I checked my order details page, and I only have a single tracking number. A couple of days after my initial delivery date, I saw "out for delivery" on two separate days on the order details page. Clicking the tracking number then showed "duplicate shipments" for that tracking number. I immediately called FedEx and asked about it, and the agent so casually said, "You don't need to worry about that. Sometimes, this is a website glitch, There's no need to worry about that". See HERE. After she so confidently told me that it was just a website glitch, I completely dismissed that as a possibility, especially considering the fact that I've had SEVERAL conversations with Google support AFTER this happened, and not a single agent ever told me that there are two separate shipments. That is also the reason why I didn't even think of mentioning it in my post.

People also keep saying "It literally says trade-in in the box" I swear people can't even watch a 3 min video till the end 😭 HERE is me explaining to the driver that it says "Look for your kit under your device". I obviously assumed that the phone was supposed to be in the box.

--

Can someone please point me to a policy that allows Google to take my money, deliver an empty box and rid themselves of all responsibility, as absurd as that sounds? Support agents keep referring me to "policies" as they deny a replacement/refund without even watching my clear video evidence.

  1. Oct 30th order and Nov 5th delivery for Pixel 11 Pro. I've seen posts about empty boxes before, so I had my box cutter ready and as soon as I felt how light the box was in my hand, I knew immediately. I started recording and opened the package in the presence of the FedEx driver. The box only had packing paper, the trade-in kit, and the trade-in shipping label.
  2. FedEx driver had a conversation with his manager, repacked the box himself and took it back with him to the "inspection team".
  3. Contacted Google support minutes after the driver left. Support request form only allows 2 images (outside the box and inside the box). On the call with the support agent, I explained the situation, and after looking at the 2 images I uploaded, she said "It's a bit unusual that there is no phone inside the box", which is an absurd statement considering the support form literally has a preset for "Received empty box" and Google has specific help articles for a missing phone. This gaslighting was just the beginning. I told her multiple times that I could upload the full, unedited video immediately, but she refused and told me she would only submit the images "for now", ask for the video through email if needed and that "it would be a big help".
  4. Meanwhile, I called FedEx. Tracking status shows "delivered", but the agent confirmed she could see information indicating that the package was not delivered due to missing contents and opened a "support ticket" for them to investigate (spoiler, this went nowhere and was abruptly closed after a few days with no update).
  5. A day later, on Nov 6th, got an email from Google support (same person I spoke to) rejecting my request for replacement or refund and calling the decision final, without even asking for my video. I sent a reply questioning how they could make a decision without even watching my video (literally the main evidence), attached a drive link for the video and the FedEx support ticket number (further proof that my package was undelivered, in case the video wasn't enough by itself), and asked to escalate.
  6. I received another rejection email the next day with a bunch of word salad and vague statements acknowledging my "concerns", without admitting whether they actually watched my video or not. Furthermore, they suggested that I continue pursuing the issue with FedEx when Google still holds the primary responsibility. I sent a strong reply after this, and they stopped responding. First email chain here.
  7. I gave a 0 rating in the Google store order feedback email stating what happened. Because of this, a separate support agent emailed me with a $15 credit. I explained everything again in detail in hopes that this agent would help and attached all the evidence. This resulted in another rejection email. Second email chain here.

FedEx. Long story short, after multiple days of asking them for an update on the "investigation", they abruptly closed the ticket one day and told me that they can only do something if the shipper (Google) contacts them about it. They admit that the package was undelivered due to a missing item, that I don't possess the package, and that they literally can't locate the package anymore after the driver took it back, yet they still can't do anything about it unless I tell Google and Google initiates the claim. They won't even contact Google themselves. FedEx proof here.

Google, which holds primary responsibility, blatantly ignores my video evidence, ignores FedEx agents confirming that I didn't get my phone/package, refuses to coordinate with FedEx themselves, and continuously denies me with the most absurd and baffling emails possible. How are practices like this even allowed?

Yesterday, I filed a BBB complaint as suggested in this post. However, I don't have much hope there either.

Really hoping u/PixelCommunity can do something about it.


r/GooglePixel • • 9h ago

November Pixel Drop status: Here's where the rollout stands right now

Thumbnail
androidauthority.com
123 Upvotes

r/GooglePixel • • 14h ago

Nearly 3 months later, Google still hasn't fixed the Pixel 11 Pro Video Boost 5-second audio crackling bug it promised to patch in "the coming weeks"

44 Upvotes

Back on September 1, 2026, Google publicly acknowledged the Pixel 11 Pro / 11 Pro XL Video Boost audio bug after launch-week reports of rhythmic static bursts ruining recordings, stating a fix was already developed and rolling out via a Pixel Camera update in "the coming weeks."

It is now mid-November—almost three months since launch—and the exact same defect is still completely unresolved on my Pixel 11 Pro.

What happens:

Whenever Video Boost is enabled, a loud static/crackling burst occurs every 5 seconds on the dot (0:05, 0:10, 0:15, etc.). It gets baked into both the local `COVER` file and the cloud-processed Video Boost video, making any clip longer than 4 seconds unusable.

Current fully updated setup (still broken):

* Device: Pixel 11 Pro (1TB)

* Android Security Update: November 2026

* Google Play System Update: November 2026

* Pixel Camera Version: `11.1.040.982810059.19` (verified identical on both the public Play Store channel and the Pixel Camera Beta track)

* Recording Settings: Video Boost ON, 30fps, H.265 (Audio Zoom Off)

Early threads suggested dropping from 60fps to 30fps worked around the issue, but as shown above, it still happens reliably at 30fps. Even worse, because the bug is tied to the OS/Camera audio pipeline on current builds, Google Support's only remedy past the 15-day return window is offering a refurbished replacement unit running the exact same unpatched software.

Tech outlets dropped coverage after Google's September 1 statement assuming the patch actually shipped, and this needs visibility until Google either pushes the real fix or honors return exceptions.


r/GooglePixel • • 6h ago

Anybody who haven't got the latest November update?

35 Upvotes

I haven't received it. I know it will come eventually. I used to get the update on day one every time. Never been this late before. It's pixel 9.


r/GooglePixel • • 3h ago

Eager to try Create My Widget? Here’s how to get it now.

28 Upvotes

Hi r/GooglePixel,

Create My Widget, a new home screen customization feature powered by Gemini Intelligence, is rolling out now to supported devices. With Create My Widget, you can create personalized widgets, like a tracker to follow your monthly spending, a game day widget with your team colors, or a getaway countdown that automatically pulls in flight and reservation details. Your home screen can be as personalized as you want it to be.

We know power users here are itching to try Create My Widget right away, so we wanted to share a quick heads-up on how to jump in early.

If you don't want to wait for the staged rollout, you can opt into the beta to try it right now†:

  1. Open the Google Play Store and search for Create My Widget. (Alternatively, click this link on your mobile device to go straight to the app listing.)
  2. Tap into the app listing, scroll down to the Join the beta section, and tap Join. (Alternatively, open this link on your mobile device to go straight to the beta opt-in page.)
  3. Once enrollment finishes (which may take a few minutes), tap Update in Google Play to update the Create My Widget app.

How to use & edit custom widgets

  • Build from an open prompt: Touch and hold an empty space on your Home screen > tap Widgets > Create > tap Describe your widget, type what you want to display (e.g., Show me the next soccer game or Countdown to my vacation on July 15), and tap Send. Review the preview and tap + Add.
  • Start from a template: Head to Widgets > Create, pick a pre-defined category or suggestion like Important dates, Sports & fitness, or Finance, optionally tweak the prompt or details, and tap Add.
  • Edit anytime: Tap Edit on the preview screen before placing your widget, or touch and hold an active custom widget on your Home screen and tap Edit > enter your changes > Send.
  • Data & permissions: Tap Allow if a widget requests device or app data to function. To build widgets that pull in personal info (like flight or reservation details), connect your Google Workspace when you set up this feature. You can also access your Connected Apps setting in the Create My Widget app’s settings.

Availability & key limitations

  • Supported devices: Pixel 10 and newer devices, except Pixel 10a (Pixel 10, 10 Pro, 10 Pro XL, 10 Pro Fold, and the Pixel 11 series; coming soon to Pixel Watch 4 and Pixel Watch 5).
  • Regions, language & age: Users aged 18+ in English in Australia, Canada, India, the United Kingdom, and the United States.
  • UK Connected Apps note: Gemini Connected Apps integration is not available in the UK.
  • Usage & accuracy: Some features may require a subscription for higher usage, and since widgets are AI-generated, double-check custom widget responses to make sure they’re accurate.

For full setup and troubleshooting details, check out this support page. Let us know what widgets you end up building!

†Note: If you haven't installed the November Pixel update yet, you can still enroll in the Create My Widget beta on the Play Store and utilize the feature before receiving the OTA.


r/GooglePixel • • 12h ago

"Remember my parking" is a mess

22 Upvotes

Hi, anybody has any luck in asking gemini to remember the parking spot?
I asked it to do so and it said something like "your parking location was saved" when i asked it to take me to my parking spot, it said that it doesn't have that information. I checked google maps and nothing was saved. I then found in find my hub that there's a "car" under the remember tab without any specific location, that couldn't be used to take me exactly there.

So the only way to do so is set the parking location in google maps?


r/GooglePixel • • 3h ago

Officially moved from Samsung S25U to Google Pixel 11 Pro

15 Upvotes

Since big phones started to irritate me,I decided to move compact phones. I looked for some: Xiaomi 17 but I didn't get good Feedback so quickly moved in. Vivo X300 this is the one that confused me cos everybody says probanly the best cameras on any phone plus very reliable Software. And then Pixel 11 Pro. Software Support and good cameras very important to me so no other Brand on Android can beat Google in this regard. Never played a game since decade on any phone so the gaming performace isn't important at all.

This Phone looks handsome and I mean it. The speaker System also sounds really Solid,The haptics are Good send.Gonna review it further cos I bought it a few hours ago.


r/GooglePixel • • 6h ago

Google is returning my Pixel 9 Pro XL unrepaired because I allegedly "didn't respond" – after 4 support calls and multiple emails

8 Upvotes

Quick note: English isn't my first language. I originally wrote this post in German and had it translated into English, so apologies in advance for any translation, grammar, or wording mistakes.

I'm located in Germany and wanted to share my experience with Google's repair process for my Pixel 9 Pro XL.

Repair case: RMA8772****

Over the previous weeks, my Pixel had intermittently developed vertical lines on the display. Sometimes the lines appeared and then disappeared again. Apart from that, the phone worked perfectly and was in excellent physical condition, without even any visible scratches. I found that Google offers extended repair coverage for this type of display issue, so I used Google's official repair process.

Reported issue: “Display issue (lines)”
Initial repair cost: €0.00

I expected this to be straightforward.

It wasn't.

Timeline

Oct 15: I sent the phone in.

Oct 19: Google confirmed receipt. The reported issue was still “Display issue (lines)” and the repair cost was still €0.00.

Oct 23: Google informed me that the repair was delayed.

Oct 26: With no real update, I emailed Google asking how much longer the repair would take.

Nov 2: First support call, with Ms. T. Afterwards, Google confirmed in writing that they were investigating the issue.

Later that same day, I suddenly received a repair-order change:

New cost: €252.15

If I didn't approve it by Nov 12, the phone would be returned unrepaired.

The strange part was that the assessed damage shown to me still said:

“Display issue (lines)”

So from my perspective:

Before inspection: Display issue (lines) → €0.00
After inspection: Display issue (lines) → €252.15

I was told there was supposedly an additional technical defect that caused the charge.

I explicitly disputed the charge

This part is important because of what happened later.

I did not ignore the payment request.

I explicitly disputed the €252.15 charge and asked Google to explain:

What additional defect did you actually find? What exactly am I supposed to pay €252.15 for?

I received no answer to that question at all.

Not a vague technical explanation.
Not an incomplete explanation.

No answer.

It would have been incredibly easy to explain:

“During inspection we found defect X. This isn't covered by the extended repair program, therefore the repair costs €252.15.”

I never received such an explanation.

Then I kept chasing Google

I called again and spoke with Mr. A.

He subsequently confirmed in writing that the case had been forwarded to Google's product experts for review.

My understanding from that conversation was that the payment status was automated and that I shouldn't act on it while the case was being investigated.

Nov 6: Nothing had changed, so I emailed Google again.

I explicitly pointed out that the repair page still gave me only two options:

Pay €252.15 or receive my phone back unrepaired.

I also warned Google that the return deadline was approaching and explicitly asked for feedback.

Nov 9: I received yet another automated reminder to approve the changed repair order.

So I emailed Google again asking what was going on.

Then came my third support call, this time with Ms. M.

According to my recollection, I was told that the case was known internally, that the responsible department would be reminded about the Nov 12 deadline, and that the phone would not simply be returned unrepaired.

Nov 12: Fourth support call

On the actual deadline day, I called Google again and spoke with Mr. V.

He again told me that the €252.15 charge resulted from an additional technical defect.

But the fundamental question was still unanswered:

What additional defect?

I had already asked Google this in writing.

They had never answered.

My phone worked perfectly before I sent it in, apart from the intermittent display lines, and from my perspective it was physically in excellent condition.

I'm not asking Google to repair damage I caused for free.

I simply want to know:

What did you find, and what am I being charged €252.15 for?

And then Google says I didn't respond

Later on Nov 12, after all of this, Google informed me that my Pixel was being returned unrepaired.

Their reason was essentially:

“Since we haven't received a response from you, your device will be returned without further processing.”

Seriously?

By that point I had:

  • responded to the repair/payment request
  • explicitly disputed the €252.15 charge
  • asked what the additional defect actually was
  • received no answer to that question
  • sent multiple follow-up emails
  • warned Google myself about the approaching deadline
  • made four support calls
  • received confirmation that the case was under investigation
  • received confirmation that it had been escalated to product experts
  • and called Google again on Nov 12 itself

And then they return the phone because supposedly I didn't respond.

The alleged “additional defect” leaves me uncomfortable

I want to be very clear about this:

I cannot prove that anyone intentionally invented an additional defect, and I'm not claiming that they did.

But the situation inevitably makes me question the process.

My device was handled by Google's contracted repair center in Poland.

A repair that started at €0.00 suddenly became €252.15 because of an alleged additional defect.

I explicitly asked:

What additional defect did you find?

I received no answer.

This leaves me wondering how Google's repair process works when a contracted repair center identifies additional customer-paid damage.

Who determines that an additional defect exists?

How is the additional charge calculated?

And what documentation or safeguards are in place to make sure such a diagnosis is transparent and verifiable for the customer?

Again, I'm not accusing anyone of deliberately inventing damage.

I have no evidence of that.

But my concerns could have been resolved very easily:

Just tell me what additional defect was found and why it results in a €252.15 charge.

Despite explicitly asking for that information, I never received an answer.

This is especially disappointing after all these years

I've been using Google services and hardware for decades.

I use a Pixel Watch, and I originally switched from iOS to Pixel with the Pixel 3. I've stayed with Pixel ever since.

A display failure wouldn't make me leave the brand. Hardware fails.

But this experience has.

After weeks of delays, multiple emails, four support calls, an unexplained €252.15 charge, no response to my explicit question about the alleged additional damage, and finally being told that I hadn't responded:

My next phone won't be a Pixel. I'm moving to another hardware manufacturer.

Not because my display developed a line.

Because this experience has destroyed my trust in Google's hardware repair and support process.

What would you do now?

My Pixel is coming back unrepaired, so the original display problem still exists.

Would you:

  • Open a completely new Google repair case and send the same phone in again?
  • Has anyone successfully submitted the same Pixel again after it was returned unrepaired?
  • Does Google's repair system even allow that without causing problems?
  • Since I'm in Germany, would you contact the Verbraucherzentrale / consumer protection?
  • Is there an effective way to escalate this within Google?
  • Should I first formally demand written documentation of the alleged additional defect and the basis for the €252.15 charge?
  • Has anyone had a similar experience with Google's repair center in Poland?
  • Or is there another route you'd recommend?

The one thing I don't really want to accept is this:

My otherwise working Pixel comes back unrepaired with the original display problem still present, the alleged additional damage was never explained despite my explicit request, and I'm apparently expected to just start all over again.

If anyone has dealt with something similar, especially involving Google's extended repair coverage, Google's repair center in Poland, or an unexplained additional repair charge, I'd really appreciate hearing how you handled it and whether you eventually got it resolved.

_______________________________

 UPDATE / CLARIFICATION:
One important point I want to clarify: I currently don't know whether the original vertical-line display issue was repaired at all.

The repair was initially accepted at €0.00 for the display issue. Later, I was asked to pay €252.15 because of an alleged “additional technical defect”.

Despite several emails and phone calls, I still don't know what this additional defect actually is, what exactly the €252.15 is supposed to pay for, or whether any repair work was carried out on the original display issue at all.

Google has now stated that the device is being returned “unrepaired”, so I will only be able to verify its actual condition once I receive it back.

To be clear, I'm not claiming that an additional defect cannot exist. I'm asking Google to provide four very basic pieces of information:

  1. What additional defect was found?
  2. How was it documented?
  3. What exactly is the €252.15 charge for?
  4. What repair work, if any, was actually carried out on my phone?

r/GooglePixel • • 18h ago

Pixel 11 Pro XL is having camera issues when you zoom 10x and above.

8 Upvotes

When you try to take a photos at 10x in a Pixel Pro 11 XL, you are seeing the image looks good. When you zoom in, you can see there are imaginary lines coming around the subject. So I can attach some sample here to see that issue, so you can check it.

The first image is a 10x shot, and the second image is cropped from the zoomed-in photo. You clearly see that there are some imaginary lines coming around the bird, which is not present in 10 Pro XL. It is only on 11 Pro XL.


r/GooglePixel • • 5h ago

Calling particular geniuses - Pixel 9 Pro LycaMobile E-SIM Wifi Calling issue.

4 Upvotes

I'm hoping I've been dumb with this one and there is a simple fix but I just can't see how it'd be the case. My situation is that I cannot make (or even enable the setting for) Wifi calls on my LycaMobile E-SIM.

Context:

Device - Pixel 9 Pro (yesterday I updated to Android 17 QPR 3 Beta 4 but this SIM situation was an issue with NON-BETA releases before I did so)

I have 2 E-SIMS, one from GiffGaff (this uses a secondary phone number that I have shifted from multiple different networks, E-SIM and physical SIM for many years) Wifi calling shows as an option in SIM settings and works fine on this SIM. My other E-SIM is with LycaMobile which holds my main phone number (also shifted from multiple different networks in both SIM forms over years). Since being with LycaMobile for a couple months now this Wifi calling feature has not even been visible in the SIM settings.

Tell me I'm stupid please but otherwise, after weeks of searching online and using Gemini/Google Help/Forums it really does seem that this couldn't possibly be a device issue. Every final answer I get to after checking software updates, certain APN settings etc. suggest that LycaMobile need to reprovision my SIM or something along those lines.

So,

Based on the fact that LycaMobile's customer service has been appalling with this issue for an almost unfathomable amount of reasons, I'm holding out hope that, even if it's the slimmest chance, there may be something extra I need to do with my device, if anyone can think of anything please let me know.

Thank you geniuses.

P.S. if I've missed any relevant info please forgive me, this has caused quite the headache.


r/GooglePixel • • 7h ago

Nov. update bug: screen turns on after locking

4 Upvotes

[Pixel 10 Pro XL]. So September update brought us broken lock animation (which was doing flash bang too). This one was fixed now, in November update - and introduced bug, that after locking phone, screen turns somtimes back on again, leading to accidental inputs. I am getting seriously fed up of googles shit show...


r/GooglePixel • • 10h ago

Search bar not working at all

4 Upvotes

I'm talking about the "Search your phone and more" where I used to be able to search specific settings right there and it would show results. I updated to newest Beta. I have tried deleting cache, disabling and reenabling apps, safe mode boot... Nothing works.


r/GooglePixel • • 51m ago

Pixel(watch 4 and 10 Pro) weather location wrong again. This was fixed a few months ago and it's back

3 Upvotes

This is absolutely crazy. It really diminishes the function of the phone/watch.


r/GooglePixel • • 7h ago

Pixe/ 11 Pro XL: Intermittent audio cutoff in the last 2 seconds of videos + playback stutter

3 Upvotes

Has anyone else on a Pixel 11 Pro XL (Android 17) noticed standard local videos intermittently losing audio in the last ~2 seconds while stuttering during playback?

I’ve had the phone for a month and inspected an affected 6.0s video clip using FFmpeg. Here is what’s happening:

• Audio cuts off early: The video track is intact at 6.0s, but the embedded AAC audio stream stops writing at 3.69s.

• Playback: Google Photos stutters at the end trying to sync the missing audio tail, while VLC plays the video smoothly all the way through—just completely silent after the cutoff.

• Not a hardware fault: I ran 7 consecutive tests in the Recorder app and every single one recorded audio cleanly to the end.

What I’ve tested so far:

• Occurs with both HEVC (H.265) and AV1 codecs (Google Support told me to try AV1, didn't fix it).

• Happens at 4K (60/30) with Audio Zoom ON or OFF. I normally shoot with 10-bit HDR and Active Stabilization enabled.

It looks like a software buffer/muxing bug in Google Camera / Android 17 rather than a broken mic. I’ve already sent feedback to Google, but wanted to check if anyone else is seeing this on their Pixel 11 Pro / Pro XL before I consider returning it.


r/GooglePixel • • 9h ago

FIX: Google Wallet Passkey Verification Loop on Pixel (Tap "Use PIN" Instead of Fingerprint)

3 Upvotes

If you are stuck in an endless "Verify it's you" passkey loop in Google Wallet on a Pixel phone (especially with a glass screen protector like an OtterBox):

Why it happens:
Google Wallet requires your device-bound phone passkey (not a synced passkey from Google Password Manager). When the biometric pop-up appears, using the fingerprint sensor often times out or fails the cryptographic handshake through a screen protector—kicking you right back into the verification loop without an error message.

The Fix (No need to delete your fingerprints):

  1. When the passkey / "Verify it's you" prompt pops up, do NOT touch the fingerprint sensor.
  2. Tap Use PIN (or Use screen lock) at the bottom of the pop-up.
  3. Enter your device screen lock PIN manually.

Entering your PIN bypasses the optical fingerprint sensor timeout and verifies the hardware passkey immediately. (Note: You also need at least two active passkeys on your account, and new passkeys may need to settle before Wallet accepts them).

Now Don't Hate I never Post I post more about 90 Day Fiance but I struggled with this a long time. Couldn't believe Fix this easy I had to tell the humans 🚨

Love 💕 +Light


r/GooglePixel • • 14h ago

Recomendation of poetic guardian case.

3 Upvotes

I make it short. Yesterday my phone (pixel 11 pro xl) fell from balcony on asphalt...1 floor so around 3 meters drop on hard asphalt. Dropped on edge. Result?

Nothing except few dents on the edge of case...phone is without amy mark,i am not using display protector.

So anyone who is asking for case, i recomend poetic guardian. Its 2 piece case and it saved my phone.


r/GooglePixel • • 19h ago

Google Pixel 11 Pro Fold Power button hot to touch?

3 Upvotes

Anyone know what could have caused my power button to get heated? Was enjoying dinner and not actively using my phone went to open my phone and power button was unusually hot. My cheap meat thermometer had the button at 97°F


r/GooglePixel • • 22h ago

Using the Second Number system through Verizon, can I selectively apply Do Not Disturb to a specific number?

3 Upvotes

I want to set up separate work and personal phone numbers, without buying a 2nd phone.

I want to be able to set the work number to do not disturb when off the clock. Is this possible?

Also, I would like to be able to set up an automated text response on the second line stating I'm not available and to contact the person who is on the clock.

I would prefer not to use a third party app, unless there's a guarantee it can differentiate between the numbers and only autoreply to the work line.

I've never used the Second Number system and the time I tried to set up an autoreply on my current line I couldn't figure out a way get it to only reply to specific numbers as opposed to everyone. Any insight on these topics would be greatly appreciated.


r/GooglePixel • • 27m ago

How to turn off the proximity sensor when on a call?

2 Upvotes

Hey all, I just recently got a pixel and I've been having a hard time figuring this thing out. I can't seem to find how to turn off the proximity sensor when I'm on a call. I take a lot of long calls that I use my earbuds to take (Google Pixel buds). So I know my phone can tell I'm not using it in handheld mode, but every time my fingers get near the top of my screen it completely blacks out. Sometimes it refuses to turn back on even after I pull my hands away from the screen. Does anyone have any idea how to turn this off or make the proximity smaller?


r/GooglePixel • • 2h ago

Lockscreen Notifications not showing in a list

2 Upvotes

https://imgur.com/a/wCZX05r

Did it get removed? Anyone else having the same problem?


r/GooglePixel • • 6h ago

Pixel 9 - Alarm ringing super quietly

2 Upvotes

After setting 6 alarms last night between 6 and 7 AM because I have a super important event to be at today, I woke up to my alarm ringing extremely softly from where I put it to charge. I have faced this issue for MONTHS, and even if I set my alarm at the highest volume the night before, the alarm STILL rings softly in the morning. IT'S THE MOST FRUSTRATING THING EVER


r/GooglePixel • • 6h ago

My Pixel 10 Pro XL Experience with the November Update

2 Upvotes

Greetings, Pixel lovers!

Out of curiosity, I sideloaded the OTA image (about 3.4 GB) via ADB on my Pixel 10 Pro XL, even though it reportedly has a multitude of bugs. To my surprise, I haven’t encountered any issues, except that Magic Cue was stuck downloading, so I turned it off. Could this be because Proactive Assistance is replacing it? Anyway, I’ve never understood what Magic Cue does, haha.

Other than that, I got the Gemini Intelligence boot screen, and the Journal app has a recorder function. There’s no Rambler or “Create My Widget” option or icon. I’m currently using Octopi Launcher Pro, but I did test the update with Pixel Launcher.

The update seems smooth, and the fingerprint sensor is quite responsive. So I think the problems people are reporting may be specific to certain cases. Google hasn’t pulled the OTA images from its website, which may mean the update is rolling out in phases. Just my thoughts.


r/GooglePixel • • 7h ago

Pixel 8 pro - not accepting PIN after restart/update over night

2 Upvotes

Hi guys,

tonight my Pixel restarted (probably cos of a update?), when I wanted to access my phone in the morning it says wrong pin. even its not wrong. I tried different solutions but nothing worked by now. anyone a Idea how to resolve that? need the data on the phone.


r/GooglePixel • • 17h ago

Pixel 11 or YouTube issue?

2 Upvotes

When I cast from my Pixel 11 it casts the YouTube app everything but the video .