Pixel Owners Still Hit by Android Auto Wireless Disconnects Three Months In

A Pixel 9 Pro XL owner opened Google’s official Android Auto support forum on April 3 with a bug report that has now dragged on for three months. Wireless Android Auto disconnects every two to three minutes, the user wrote, and the breakage began right after the March 2026 Android 16 update. As of early July, the thread is still active, with new users piling on and one Pixel owner reporting the same fault across three different Pixel handsets and two Android versions.

The thread, titled “Pixel 9 Pro XL keeps disconnecting every 2-3 minutes,” sits in plain view on the official Google support site. It is the public ledger of a bug that Google has only obliquely addressed: a single April 4 response saying the report had been forwarded, a single June Google Play Services release note reading “Bug fixes for Device Connection related services,” and no public naming of a cause.

What the Bug Looks Like From the Driver’s Seat

The user’s original post is precise: “Every 2 – 3 minutes, my Android Auto (Wireless) keeps disconnecting. This has not been an issue until the march update for Android Auto, I thought the most recent update would fix it but apparently not.” They are on AA Version 16.5.661214 and Pixel build CP1A.260305.018, the March 2026 Android 16 release.

They went further. The disconnection tends to fire when the car is among other vehicles, which the user reads as wireless congestion. They cleared the app cache, reinstalled Android Auto, reset Bluetooth and Wi-Fi settings, disabled battery optimization, and removed the phone case. The phone is paired with the head unit only, nothing else.

“This happens every single time I’m connected without fail,” they wrote. “This issue does not occur on my head unit when using Apple Car Play, wireless as well.” The reproduction steps are simple: connect Android Auto wirelessly, drive in a fairly congested area, watch the session drop within five minutes, then reconnect. A Google Play Services update was waiting on the user’s phone when they posted the report, and they said they did not have faith in it resolving the issue.

Three Months of Reports on the Google Support Thread

The Google thread is a public timeline of the bug’s persistence. Every step on it comes from the Pixel 9 Pro XL disconnect report on Android Auto support, where the original post and replies are visible without a login.

The sequence reads like a stack of confirmations, and the latest replies describe the same fault on phones that did not exist when the thread opened.

1. April 3, 2026: Original bug report posted by a Pixel 9 Pro XL owner in the United Kingdom.
2. April 4, 2026: The Android Auto team posts a single reply saying the report has been forwarded and that the team will reach out by email for more information.
3. May 12, 2026: Two replies arrive in quick succession from another Pixel 9 Pro XL owner and a Galaxy S21 Ultra owner, both saying they see the same behavior.
4. June 8, 2026: A Google Play Services update goes live carrying the release note “Bug fixes for Device Connection related services.”
5. June 14, 2026: XDA Developers reports the fix appears to have solved the disconnection for several testers.
6. Early July 2026: New replies on the Google thread include a user who has seen the same fault on a Pixel 7 Pro, Pixel 9a, and Pixel 10 Pro XL on Android 16 and Android 17 beta.

Google’s Quiet Acknowledgment

Google’s only direct on-record statement on the broader bug came through Android Authority and was carried by Android Headlines in March. A representative told the publication: “The team is aware of this and fixes are beginning to roll out.” The company has not named a cause.

The community has a working theory. According to XDA, the common belief inside user channels is that Android’s Advanced Protection security feature is resetting USB Protection settings and blocking Android Auto from running consistently. The feature bundles Theft Detection, Offline Device Lock, Unknown App Protection, and other tools into one switch.

XDA notes that wireless users are also seeing the problem, which suggests Advanced Protection is not the full explanation. The official response on the Google thread, dated April 4, is the only acknowledgment on the affected users’ own channel. It tells the original reporter that the issue has been forwarded and asks for follow-up by email. There has been no further public reply from the Android Auto team on the thread since.

The Numbers Behind the Thread

• Apr 3, 2026: first public bug report on the Android Auto forum
• Apr 4, 2026: the only direct response from the Android Auto team
• Jun 8, 2026: Google Play Services update carries the release note “Bug fixes for Device Connection related services”
• AA Version 16.5.661214 on Pixel build CP1A.260305.018 was the original affected setup
• Galaxy S23, S24, S25, S26 series users have reported the same fault

The June 8 Fix That Might Not Be Enough

Google’s June 8 Google Play Services update is the closest thing to a resolution on the record. The release note reads, in full, “Bug fixes for Device Connection related services.” Google does not say more.

Several outlets reported partial success after the update landed. Tom’s Guide’s Scott Younker wrote that a Galaxy S26 Ultra connected to Android Auto “immediately and maintained the connection more consistently” after the update. Android Authority and Android Police also reported the fix had helped at least some of their testers.

Patrick O’Rourke, News Editor at XDA Developers, framed the update on June 14 as the fix for “the Android Auto disconnection problem plaguing Samsung and Pixel users.” He wrote: “I’d test the update myself, but I haven’t experienced Android Auto disconnection problems with my Pixel 10 Pro or my Galaxy S26 Ultra.” The same article notes that the update is rolling out in stages, which means some users will see it before others.

The article also flags a technical wrinkle: a GitHub bug report on the wgtunnel Android app documents a residual failure on the March 2026 Pixel build CP1A.260305.018, where Android Auto Wireless drops its local Wi-Fi Direct route when a VPN service is detected in the background. On the support thread, the picture is more mixed. The early-July replies include a user who has cycled through three Pixel phones and two Android versions without a working connection, calling the situation “embarrassing.” Google has not said when the fix rollout will be complete.

What Pixel Owners Have Already Tried

The Google forum thread reads like a checklist of fixes users have already burned through, none of which closed the case. The list below reflects the moves named across the thread and the supporting technical reports.

• App cache and data reset for Android Auto, followed by a full uninstall and reinstall.
• Bluetooth and Wi-Fi settings reset on the phone, with the head unit kept as the only paired Bluetooth device.
• Battery optimization disabled for Android Auto and Google Play Services.
• Phone case removed and the handset repositioned in the car to rule out antenna obstruction.
• Full factory reset on the phone, then a from-scratch setup, which one user reports did not stop the disconnects.
• Hardware swap: one user bought a new Android Auto and Apple CarPlay head unit only to see the same fault on a Pixel 7 Pro, Pixel 9a, and Pixel 10 Pro XL running Android 16 and Android 17 beta.

One user spelled out the failure in plain language: “I have already performed a full factory reset / operating system reset on the phone, configured everything again from scratch, and the problem still happened again. Because of this, it does not seem to be caused by a simple app cache issue or a wrong setting on the phone.” Another user on the same thread added: “This usually occurs if there’s some battery saving option enabled on the phone, or battery restriction on android auto app,” which is the kind of community guess that has not, in the reported cases, actually fixed the disconnection.

The pattern matters because the workaround catalogue has been exhausted without changing the outcome. The thread has stayed open for three months without a patch note that names Android Auto, which leaves affected users without a target to wait on.

Where the Affected Pixel Owners Stand

Three months in, the picture is uneven. Google says a fix is rolling out. At least one outlet’s tester reports the fix worked. The Google Play Services release note does not name Android Auto. On the user-facing Google thread, a user who has cycled through multiple Pixel phones and Android versions says nothing has worked, and calls the situation “embarrassing.”

Samsung Galaxy S23, S24, S25, and S26 owners have reported the same fault, and the issue spans both wireless and wired Android Auto. Google has not named a cause or given a date for when the rollout will be complete, and has not committed publicly to a follow-up fix if the June 8 patch does not close every case. A separate three-month Android Auto bug, this time in Waze’s cancel-route button, has followed the same pattern of forwarded tickets and unanswered threads, and is documented in a three-month Waze cancel button bug on Android Auto report.

Frequently Asked Questions

Which Pixel phones are affected by the Android Auto wireless disconnect?

The first report came from a Pixel 9 Pro XL on Android 16 build CP1A.260305.018. The thread has since collected the same complaint from Pixel 7 Pro, Pixel 9a, and Pixel 10 Pro XL owners on Android 16 and Android 17 beta.

Has Google fixed the Android Auto wireless disconnect yet?

Google released a Google Play Services update on June 8, 2026 with the release note “Bug fixes for Device Connection related services.” Several outlets reported the patch helped at least some testers. The original poster and other users on the support thread say the issue persists.

Is the problem limited to wireless Android Auto?

No. Android Headlines, citing Android Authority, reported that Samsung Galaxy S23, S24, S25, and S26 owners saw the same fault on both wireless and wired connections, and Pixel users on the March 2026 update reported wired failures too.

What is causing the Android Auto wireless disconnect?

Google has not publicly named a cause. The strongest user theory, carried by XDA, points to Android’s Advanced Protection security feature resetting USB Protection settings, though XDA notes wireless users are also affected, which means the theory does not explain every case.

What should affected Pixel owners do right now?

Update Google Play Services through the Play Store. If on a wired connection, swap the USB cable. If on wireless and the issue continues, file the AA version, Pixel build, and exact symptoms on the official Android Auto support thread so Google can correlate the case.