Android Auto Error 22 means your phone doesn’t bundle Android Auto as part of the system, so the car connection won’t start until that changes.
Error 22 feels confusing because you can install Android Auto, open it, and still get blocked the moment you plug into the car. This message is not a random crash. It’s Android Auto telling you the phone-side “host” it needs isn’t present in a way the car handshake accepts.
The good news is you can diagnose the cause fast. In many cases, you fix it with the right build of Android Auto and the right Google components. In other cases, the phone’s firmware choice is the real blocker, and you’ll save time by switching plans early.
What Error 22 Means In Android Auto
Android Auto is not just a regular app that draws a screen. On a phone, it also acts as the host that talks to the car and manages the projection session. Google’s own car UI writing guidelines include the same message you’re seeing: Android Auto must be bundled with the operating system to work correctly.
When your phone shows “must be preinstalled” or “not bundled with OS,” it’s pointing to how Android Auto is packaged on that device. Some phones ship it as part of the system image. Some phones hide it as a system component you never notice. Custom ROMs, “de-Googled” builds, and some region firmware packages can ship without the right host pieces.
- Custom ROM or GSI build — Android Auto is installed like a normal app, not as a system component.
- No Google Mobile Services — the phone lacks the Google pieces Android Auto relies on for projection and account access.
- China or carrier firmware variant — some builds remove or replace Google apps, even on the same hardware.
- Work profile or device policy — a managed profile can block permissions, USB access, or required components.
If any of those match your setup, you’re close to the answer. Use the quick table below to map what you see to the most likely fix path.
| What You Notice | Most Likely Cause | First Fix To Try |
|---|---|---|
| Android Auto installs, then shows Error 22 in the car | Android Auto isn’t bundled as a system component | Install via Play, update Google Play services, then re-pair |
| No Play Store on the phone, or Google apps are missing | No Google Mobile Services on that firmware | Move to a Google-certified firmware or a phone that ships with GMS |
| It worked on stock ROM, broke after flashing | ROM choice removed required system packaging | Return to stock firmware or flash a GApps package that includes Android Auto |
| Only fails on one phone, car works with others | Phone build issue, not the car | Check Android version, device certification, and Android Auto system status |
Android Auto Must Be Preinstalled On This Device Error 22 On Android Phones
Start with one clear goal: figure out whether you’re dealing with a “false alarm” you can clear with updates, or a firmware limit that won’t budge without changing ROMs. Do these checks while parked, with the car in Park and the screen awake.
When the screen shows android auto must be preinstalled on this device error 22, treat it as a packaging signal, not a cable glitch.
- Confirm Android version — Android Auto on the car display expects Android 9 or newer on the phone, and newer builds push that baseline.
- Check whether Android Auto is a system component — on many phones with Android 10+, Android Auto won’t appear as a normal launcher app; it lives under Settings and the system app list.
- Verify Google services exist — if Play Store and Google Play services are missing, Error 22 is often a dead end on that firmware.
- Look for managed profiles — work profiles and device admin policies can block USB data, notification access, or background activity.
If you’re not sure where Android Auto lives on your phone, open Settings, go to Apps, then “See all apps,” and search for Android Auto. If you don’t find it, look for “Android Auto” under Connected devices, or search Settings for “Android Auto.” Phones running Android 10 and newer often treat it as a built-in component.
If Android Auto is present but Error 22 still appears, you’re ready for the fixes that clear the most common triggers without touching your firmware.
If you keep seeing android auto must be preinstalled on this device error 22 after each reinstall, skip the loop and move to the firmware section below.
Fast Fixes That Don’t Touch Your Firmware
These steps won’t rewrite your ROM. They target version mismatches, stale pairing state, permission blocks, and USB negotiation issues. Run them in order and test after each change so you know what worked.
- Update Android Auto from Google Play — install the official build of Android Auto, then open it once on the phone to finish setup.
- Update Google Play services — Android Auto leans on it for account and API plumbing; an outdated build can trigger strange connection behavior.
- Clear Android Auto storage — Settings → Apps → Android Auto → Storage → Clear storage, then reboot the phone.
- Forget the car pairing on both sides — remove the car from Bluetooth on the phone and remove the phone from the car’s paired list, then pair again.
- Turn off Private DNS or filtering apps — DNS filters, VPNs, and aggressive ad filtering can block the handshake or required calls.
- Allow restricted settings when prompted — on some Android builds, Android Auto needs you to allow restricted settings if it was sideloaded or restored.
After you clear storage and re-pair, connect with a known data cable. Charging-only cables are a classic trap. If your phone shows a USB notification, set it to file transfer or Android Auto mode if your device offers it. Some skins hide this behind “USB preferences.”
If you use wireless Android Auto, still do one wired setup run first. Many head units use the wired handshake to establish the initial permissions and Bluetooth pairing, then switch to wireless on later drives.
Fixing The Preinstalled Requirement When Android Auto Isn’t Bundled
If you’re on a custom ROM, a GSI, or a phone that ships without Google apps, Error 22 often reflects a packaging rule, not a bug. In that case, Android Auto must be present as a system component. Installing an APK like a normal app often won’t satisfy the check.
This is the fork in the road. You either move to a firmware that bundles Android Auto and Google services, or you do advanced changes that can wipe data and raise security risk. If that sounds like a bad trade, switching to a stock firmware phone is the clean route.
- Return to stock firmware — the safest fix when your device has an official build with Google services.
- Flash a GApps package that includes Android Auto — some custom ROM setups need Android Auto installed as part of the system image, not as a user app.
- Convert Android Auto into a system app — this often needs a bootloader opened for root access, and it can break updates if done wrong.
- Choose a different ROM — a Google-certified ROM that already bundles Android Auto removes the whole problem.
Back up your data before you change firmware. Many bootloader opening steps trigger a factory reset. Also plan for banking apps, corporate apps, and device attestation checks that may fail after bootloader changes.
Why The “System App” Detail Matters
Android Auto’s package name is commonly com.google.android.projection.gearhead. On builds that satisfy the requirement, it’s placed in a protected system location and granted privileges a normal app can’t claim. That packaging is what the Error 22 message is pointing at.
If you decide to go down the advanced route, use device-specific instructions from the ROM or device vendor. Make one change at a time, then test with a wired connection before you add more mods.
Car And Cable Checks After The Phone Side Is Clean
Once the phone is on a compatible build, the next failures come from the connection path: cable quality, port power, and head unit firmware quirks. These checks are quick and can save you from blaming the phone again.
- Use a short, high-quality USB cable — pick a data-rated cable, not a free charging lead.
- Try a different USB port — some cars have one data port and one charge-only port.
- Restart the head unit — many infotainment systems have a power button long-press restart option.
- Delete old paired devices — clear the car’s Bluetooth and Android Auto history list if your car menu offers it.
- Update the head unit firmware — car makers often ship Android Auto fixes through infotainment updates.
If your car works with both wired and wireless Android Auto, test wired first. Wired removes Wi-Fi as a variable and makes it easier to spot whether the issue is USB data or wireless pairing.
If you use an aftermarket stereo, check the vendor’s site for Android Auto firmware notes. JVC, Kenwood, and Pioneer units can behave differently across firmware revisions.
Finish setup parked, allow notifications, turn off battery saver, then test again on a drive.
When To Stop Debugging And Pick A Cleaner Path
Error 22 is one of the rare Android Auto errors where the message is often literal. If your phone’s firmware does not bundle Android Auto and the Google pieces it relies on, you can burn hours on reinstall loops with no change. In these cases, the cleanest move is a different firmware or a different phone.
- Switch to a Google-certified phone build — stock firmware with Play services has the highest success rate.
- Use a second phone for the car — keep a dedicated, compatible device for driving and navigation.
- Pick cars with Google built-in — Android Automotive OS runs apps on the car itself and reduces phone-side quirks.
If you want one quick sanity test, borrow a friend’s Android phone running Android 9+ with Play services, connect it to the same car and cable, and see if Android Auto starts. If it does, your car is fine and your phone build is the blocker.
Once Android Auto is working again, leave it alone for a day or two. Let Play services and Android Auto settle after updates, then only change one variable at a time when you tweak settings.
You can also check the official Android Auto overview and requirements page, then compare your phone to the published baseline. It’s the fastest way to avoid chasing fixes that can’t work on your current setup.
Android Auto requirements and compatibility | Android Auto on Google Play | Android for Cars writing guidelines