Pixel 10 Pro won't charge from Console USB ports

We have had no issues with pixel 9 and pixel 9 pro/xl... Other than wireless charging is fairly slow.

Another thing you could try is a worse cable that negotiates down to 20w.
 
...Another thing you could try is a worse cable that negotiates down to 20w.
Thanks, that did it! I used a USB-C to USB-A adapter, and a USB-A to USB-C cable, and now I can charge like a wild man at 10 watts.

I wish that Lucid had embedded modern 25 watt Qi 2 / Magsafe / Pixelsnap pucks in the console. They're small and thin, there's plenty of room.

1782836525037.webp
 
I have the exact same problem with my Pixel 10 Pro XL. I've had mobile look at it twice and they haven't found anything, which likely confirms a phone-specific issue. I have a power brick plugged into the back of the center console and even that occasionally has problems. I'll have to try the adapter trick.
 
I have the exact same problem with my Pixel 10 Pro XL. I've had mobile look at it twice and they haven't found anything, which likely confirms a phone-specific issue. I have a power brick plugged into the back of the center console and even that occasionally has problems. I'll have to try the adapter trick.
Looks like the solution is either a USB-A adapter and an A to C cable,, or leave a 6-foot USB cable connected to the back of a front seat.
@marqie It might be helpful to let service know that Pixel 10 Pro phones are not compatible with the USB ports in the console and will not charge. It appears to be a design issue with either the Pixel 10 Pro, or with the console USB ports. There's no need to take up service's time with this, and no need to swap out the center console.
 
Last edited:
Moderator: it might be helpful to change the title of this thread to something like "Pixel 10 Pro won't charge from Console USB ports", now that we know what's going on and how to get around it.
 
As another interesting data point, I have a baby monitor (an older version of https://mytinytraveler.com/products/tiny-traveler-classic-wireless?variant=43584846299299) that I have plugged into the center console with a micro to C cable (no adapter) and it mostly works, though if I even look at where it plugs into the center console, it will flicker off and on. I want to say I tried an adapter with that one, but now I don't remember for sure.
 
Come to think of it, Google's magnetic Qi 2 puck charges my phone at 25 watts when I plug it into the console USB port. I should just carry one of those in the console instead of a USB A-C cable, which is limited to 10 watts. And there's less risk of damaging the phone or cable if my wife leaves the car without remembering to unplug her phone first.
 
That charges it reliably? Hmm, might have to pick one up if so.
 
That charges it reliably? Hmm, might have to pick one up if so.
Yes, at up to 25 watts. It has worked great so far, and doesn't take up much more room in the console than an ordinary USB cable.

Pixelsnap charging disk in Gravity console.webp
 
Same issue here, Pixel 10 Pro XL. Will have to pick up one of those wireless chargers.
 
I was being cheap/lazy and purchased a well-rated Qi2 charger from Amazon and that did Not do the trick. Guess I'll have to buy a legit one.
 
I was being cheap/lazy and purchased a well-rated Qi2 charger from Amazon and that did Not do the trick. Guess I'll have to buy a legit one.
Unfortunate but useful to know - which one didn't work?
 

I need to do more testing, but it definitely works if I plug it into an outlet in my house.
Those are a great deal, too bad they didn't work in Gravity. There's something a little different about Gravity's console ports.
I'll bet they were well tested with iPhones, not so much with other devices.
 
I'm also experiencing the same issue w/ my Google Pixel 10 Pro XL.

I'm glad it is seemingly a phone-specific issue at its core, rather than some defective charging ports w/ the Gravity!
 
FWIW, I found that the 10-watt charging provided by a USB A-to-C cable plugged into a USB C-to-A adapter is sufficient to operate the phone and charge it while using Android Auto. You may already have these in a closet somewhere. If you don't mind the cable, it's $40 cheaper than the solution using Google's Pixelsnap / Qi 2 cable.
 
I've been struggling and I don't know what to think. I just tested:
* The official pixelsnap charger in the center console
* A well rated c-to-c cable from Anker in the center console
* The same cable plugged into the back of the front passenger seat
* The same cable plugged into a power brick into the back of the center console
* The same cable plugged into a wall outlet with a differ power brick

I didn't get above 4kw, with the pixelsnap charger getting 1.x kw or less. I guess I need to try another cable, but I'm starting to wonder if it's my phone or the car or what. I used the AccuBattery app for my numbers.

If anyone has some free time, I'd be curious what numbers you get.
 
I tried the accubattery app and didn't trust it.
I wound up buying inexpensive usb-c power meters on Amazon.
Start with a phone at a low state of charge.
I've seen up to 25 watts on my Pixel 10 pro xl.
 
Back
Top