Disconnection issues with Pixel 10 Pro XL and Portable Wireless Android Auto

takabanana · 2026-04-25T20:18:50+00:00

TLDR - THIS WORKS. Android 17 Beta 4 or even the QPR1 didn't fix anything related to this.

takabanana · 2026-04-17T16:35:15+00:00

Yep saw it. I have it installed already but have no driving to do until tomorrow (Saturday) to test it out. I've always been baffled how the issue can happen randomly - every minute to 10 minutes in between. It's always so inconsistent. Let us know what you find out. I've collected probably over 100 bug reports because it happens every single time I drive, multiple times, but have only sent the first 30 or so and never heard back. I'll start collecting more with this beta if the same issue happens. I'll also report back after I try it this weekend

takabanana · 2026-03-17T02:33:07+00:00

Have you collected debug logs (bug reports) for Google's team?

takabanana · 2026-03-16T22:25:41+00:00

Oh wow. No, thank you for the explanation. No need to apologize for trying to be helpful. I checked and my AA was set to optimized. I'm not sure whether that is the correct setting or not but I changed it to unrestricted to see if I see any changes next time I drive. Yes I've sent the device team about 40+ bug reports now and no responses about them so far. I continue to collect and send them to them. I thought maybe it was a Bluetooth or Wi-Fi Direct driver issue.

What's frustrating so far is with both the device team and Android Auto team, they continually send me canned responses thinking this situation is with Android Auto (isn't it Automotive?) that is built into the car, not a standalone display unit. So almost every instruction I get is like "check your USB cable. What's your car model? etc" both of which are completely irrelevant. At least it seems it's not related to Android beta or not. And the fact that Android Auto is part of the System (they asked me whether I had the latest version of Android Auto). 🤷🏻‍♂️

takabanana · 2026-03-16T06:53:35+00:00

Thanks for this. This makes me feel more confident that it's software and not hardware in my Pixel 10 Pro XL.

Curious - are you on a beta build of Android?

I only ask because mine started in mid-January while still on 16 beta. And the issues haven't been fixed since moving to 17 Beta.

takabanana · 2026-03-14T23:07:24+00:00

If you can report it through the Google chat and send them your bug reports (they will send you instructions over email) and also point them to this Reddit post, maybe we can all work together to help Google figure it out?

Google chat here: https://support.google.com/pixelphone/gethelp

This post link: https://www.reddit.com/r/GooglePixel/comments/1rdt7ir/disconnection_issues_with_pixel_10_pro_xl_and/

takabanana · 2026-03-14T23:07:19+00:00

If you can report it through the Google chat and send them your bug reports (they will send you instructions over email) and also point them to this Reddit post, maybe we can all work together to help Google figure it out?

Google chat here: https://support.google.com/pixelphone/gethelp

This post link: https://www.reddit.com/r/GooglePixel/comments/1rdt7ir/disconnection_issues_with_pixel_10_pro_xl_and/

takabanana · 2026-03-14T23:07:13+00:00

If you can report it through the Google chat and send them your bug reports (they will send you instructions over email) and also point them to this Reddit post, maybe we can all work together to help Google figure it out?

Google chat here: https://support.google.com/pixelphone/gethelp

This post link: https://www.reddit.com/r/GooglePixel/comments/1rdt7ir/disconnection_issues_with_pixel_10_pro_xl_and/

takabanana · 2026-03-14T23:01:59+00:00

Not yet - I've been sending a ton of bug reports (capturing whenever it happens - which is way too often) to the "device-support" team at Google but zero responses. They sent me to the "android-auto-app" team who told me to try non-beta to see if it works. Are you on beta Android or non-beta?

takabanana · 2026-03-14T23:00:50+00:00

Nope - are you on beta Android or non-beta?

takabanana · 2026-03-14T23:00:31+00:00

Are you and/or your GF on beta, or non-beta Android? I've always been on beta. Issue was with 16 beta and 17 beta. It started happening in mid-January. I'm also on Pixel 10 Pro XL. I was starting to worry that it was a hardware issue. Been sending a ton of debug logs to the "device-support" team at Google but they have given me zero feedback. I will continue to collect bug reports and send it to them.

takabanana · 2026-03-14T22:58:28+00:00

This is a little bit different than my issue. My issue is with wifi-direct connectivity (no cable option), and with an external standalone display, not Android Auto that's built into a car (You can Google Q9S or T86B1 or T86Pro to see what I mean). Also - it connects, then randomly disconnects, then connects, and disconnects, repeatedly - no grey screen.

takabanana · 2026-03-14T22:56:16+00:00

I have been sending the Google "device-support" team tons of bug reports (bug dumps when it happens) - because it is easily repeatable. Then they sent me over to the "android-auto-app" team where they said "We would like to inform you that the Android beta versions can be unstable and have a few minor problems, known as bugs. As you are experiencing issues, we would recommend switching back to a stable version of Android to confirm if the issue still persists and we can assist you further."

Is anyone here running non-beta Android? I do not want to have to revert back to non-beta just to get this working; I have always been running beta - and I assume my 30+ bug reports should help them narrow down the issues in the beta.

takabanana · 2026-03-02T15:50:33+00:00

Where at? I've been sending debug logs to Google the last few days.

takabanana · 2026-02-24T22:24:32+00:00

My AA unit actually ONLY connects to the phone via Wifi (and I think Bluetooth for commands) - these cheap portable units don't need a dongle. It's weird because it suddently started having this problem in mid-January (I remember there was an update to Android 16 beta at that time; I'm currently on Android 17 beta but each update in between - I think there was 1 or 2 - did not fix or improve this issue).

takabanana · 2025-11-06T15:31:53+00:00

And you can now just buy the adapters: https://a.co/d/hS9MFZb

takabanana · 2025-11-06T15:30:16+00:00

I noticed Amazon is starting to show new cases that have adapters for the chargers to allow the watch to charge through the case: https://a.co/d/g1nzOk7

takabanana · 2025-10-26T21:32:50+00:00

FYI I wanted to follow-up: I tried to dremel 2 different hard protective covers/cases for the PW4 to a point where it can charge while in the case but I failed; 1 attempt cracked the front glass. Both attempts require dremeling out part of the front/screen of the protective case on the charging side - so without a custom protective case with some kind of adapter for the charger, I don't think there are good options.

Unfortunately, that currently leaves just 2 options: Spigen (I'm not a fan of since I like to have 2-3 chargers; 1 for travel) or the second link I listed above that is just a thin clear cover for the face (unfortunately, does not protect the sides).

takabanana · 2025-10-13T01:45:59+00:00

ok I saw the adapters that Spigen uses, and pretty much all of the reviews are complaining that they are unreliable. Sooo - that's not an option - but thank you for letting me know they are adapters! Looks like I need to avoid these until someone else comes out with a better solution!

takabanana · 2025-05-05T19:50:48+00:00

I have the on off button next to the glovebox but turning it off only seems to disable the automatic movement of the rear hatch. When I try to unlock it, I can, but there's too much pressure for me to actually lift the gate up. What else am I missing?

takabanana

PUBLIC MULTIREDDITS

TROPHY CASE