Google has deployed a targeted fix for a messy Android Auto bug that caused wireless connections to crash and burn following last week’s 17.2 update. The corrected builds—17.2.662638 on the stable channel and 17.3.662813 for beta testers—stop the app from repeatedly dropping or refusing to launch, a problem that left drivers scrambling to revert to wired mode or older versions.

The Glitch That Left Drivers Disconnected

The trouble began as Google pushed Android Auto 17.2 to phones worldwide. Almost immediately, users flooded Reddit and support forums with reports of connection failures. Wireless setups were hit hardest: the app would launch, connect to the car’s head unit, then drop within seconds, or fail to start at all. Some wired users also described similar instability, but the bulk of complaints pointed to wireless dongles and built-in wireless receivers. The issue wasn’t limited to one phone brand or car model; drivers with Samsung, Pixel, and OnePlus devices all chimed in, alongside head units from Pioneer, Kenwood, and even factory systems in vehicles from Ford, Honda, and Hyundai.

Google’s initial diagnosis pinned the blame on “uncertified aftermarket head units.” In a post on Reddit, a Google community representative stated that the 17.2 rollout introduced a compatibility hiccup with these non-OEM systems. But that explanation doesn’t cover every case. As first reported by Autoevolution, and echoed in countless Reddit threads, drivers with completely stock, factory-installed head units also saw their connections collapse. Google has not confirmed whether those cases share the same root cause, leaving some uncertainty for the affected minority.

The bug persisted even in early Android Auto 17.3 beta builds, which were supposed to iron out kinks before a wider release. That meant beta testers—who opt in to get new features early—found themselves equally stuck. The twin patches now tackle both channels, with the stable fix carrying version 17.2.662638 and the beta fix arriving as 17.3.662813.

Who’s Affected and Why It Matters

If your phone updated to any Android Auto build between the initial 17.2 release and before the patched versions, you’re likely in the danger zone. Specifically:

  • Stable channel users: Any 17.2.x build prior to 17.2.662638 may be buggy. The patch jumps straight to the corrected version number; there’s no intermediate hotfix.
  • Beta channel users: Early 17.3 builds (before 17.3.662813) contain the same flaw. The fix is baked into the latest beta.

For drivers who depend on wireless Android Auto, the impact was more than annoying. A navigation app that cuts out mid-turn or a music stream that stutters and dies isn’t just inconvenient—it’s a distraction that can lead to missed exits or fumbling with the phone. Many resorted to plugging in via USB as a workaround, but that defeats the purpose of a wireless setup. Others disabled automatic updates in the Play Store and rolled back to the 17.1 branch, which remains stable. Now that the patch is out, those users can safely update again.

How to Grab the Fix Right Now

Android Auto updates are delivered through the Google Play Store via a staged rollout, meaning not every device sees the new build at the same time. If you’re stuck on a buggy version, here’s how to get patched:

  1. Check your current version: Open the Play Store, tap your profile icon, and go to “Manage apps & device.” Find Android Auto in the list of installed apps and look at the version number. Alternatively, go to Settings > Apps > Android Auto on your phone.
  2. Compare to the fixed builds:
    - Stable: you want 17.2.662638 or higher.
    - Beta: you want 17.3.662813 or higher.
  3. If an update is available: Hit “Update” in the Play Store. The download is small—typically under 50 MB—and installs in seconds.
  4. If no update is showing: You’re likely in the early stage of the rollout. Try manually refreshing the Play Store listing (search for Android Auto, open its page, and see if an “Update” button appears). If not, wait a day or two; Google usually completes staged rollouts within a week.
  5. For beta users: Double-check that you’re enrolled in the beta program via the Play Store’s Android Auto beta page. If you’re stuck on an older beta, you can opt out of the beta (which uninstalls the beta and reverts to stable; you may lose data), then install the patched stable version. Only do this if you’re comfortable with a fresh setup.

Once the update is installed, test a short drive—wireless first, then wired—before relying on Android Auto for a long trip. Most users in the Reddit threads report that the patch resolves the disconnections immediately; no phone reboots or head‑unit resets are needed.

A Timeline of the Dropout Drama

The Android Auto bug didn’t appear in isolation. Google’s update cadence for the app is relentless, with new versions landing every few weeks. Here’s how the past two weeks unfolded:

  • Early July 2026: Android Auto 17.2 begins its staged rollout via the Play Store. The update includes under‑the‑hood improvements, but Google’s changelog mentions nothing about connectivity changes—making the subsequent bug a surprise.
  • Within 48 hours: Reports surface on r/AndroidAuto and Google’s own support forums. The pattern is clear: wireless connections drop, often immediately after startup, on phones that never had issues before.
  • July 15 (approx.): A Google community representative acknowledges the problem on Reddit, stating it’s due to “uncertified aftermarket head units” and affects a “small number” of users. The post advises those affected to wait for a fix.
  • July 16–17: Tipsters and tech blogs, including Autoevolution, note that the bug also hits factory‑installed head units. Beta testers on 17.3 report the same issue, indicating the fix wasn’t included in the early beta channel.
  • July 17: Google releases the patched builds: 17.2.662638 (stable) and 17.3.662813 (beta). A Reddit post confirms the rollout, asking users to update and report back.

This isn’t the first time an Android Auto update has caused connection headaches. In early 2025, version 13.9 broke wireless for some OnePlus and Motorola phones, and Google took three weeks to patch it. This time, the turnaround was much faster—under a week from initial reports to a released fix—likely because the regression was narrow and easily reproducible.

If You’re Still Stuck After Updating

For the vast majority, the patch should be the end of the story. But if you install the correct version and still see dropouts, here’s a methodical checklist before you blame the hardware:

  1. Force‑stop Android Auto and clear its cache (Settings > Apps > Android Auto > Storage > Clear Cache). Do not clear data unless you’re willing to set up the app from scratch—this erases paired cars and preferences.
  2. Reboot your phone and your car’s head unit. A full power cycle (turn the ignition off, open the driver’s door to kill accessory power, wait 30 seconds, then restart) can re‑initialize the USB and Bluetooth stacks.
  3. Check for conflicting apps. Battery‑optimization settings on Samsung and OnePlus devices can aggressively kill background apps; make sure Android Auto is excluded from any power‑saving features.
  4. Try a different cable for wired testing. Even if you primarily use wireless, a bad USB cable can cause the initial setup (which often requires a wired handshake) to fail.

If the problem persists across multiple drives and devices, gather these details:

  • Exact Android Auto version (e.g., 17.2.662638)
  • Phone model and Android version
  • Connection type (wireless dongle model, built‑in wireless, or wired)
  • Head‑unit make and model
  • A brief description of when the disconnection occurs

Then submit feedback through the Android Auto app: open it on your phone, go to Settings, and tap “Send feedback.” Google’s team actually reads these, and detailed reports help narrow down edge cases.

A Word for Fleet Managers and Professional Drivers

For businesses that depend on Android Auto for delivery routing or field service, the bug was a productivity hit. If you manage a fleet of company phones, now is the time to push the update to all devices via your MDM console. Because Google’s rollout is staged, individually checking each phone may be faster than waiting for the update to arrive automatically. Ensure that automatic updates remain enabled going forward to avoid similar gaps.

For drivers using rental cars or unfamiliar vehicles, the patch should restore reliability. If you’re picking up a rental with an unknown head unit, a quick wired test before you leave the lot can confirm everything works—saving you from mid‑trip frustration.

The Outlook: Android Auto’s Stability Cycle

Google is likely keeping a close eye on telemetry data from the patched builds. Look for a possible 17.3 general release in the coming weeks that folds this fix into the main release channel for all users. The current beta (17.3.662813) may graduate to stable once it’s proven with a wider audience.

What about the “uncertified aftermarket head units” that Google blamed? Expect the company to quietly refine its compatibility checks in future updates. The reality is that Android Auto’s open ecosystem—it works with thousands of car models and dozens of phone brands—makes regression bugs inevitable. The good news: this one was squashed quickly, and the app’s fundamental architecture remains robust.

For now, the message is simple: update, test, and get back to hands‑free driving. If you’ve been holding off on the 17.2 branch, it’s safe to move forward. The patch doesn’t add new features, but it brings back what matters most—a connection that stays put.