The message “Android Auto must be preinstalled”, sometimes shown as Communication Error 22, points toward the phone’s Android Auto integration. Installing an APK may put the app on the phone without supplying the operating-system configuration that car projection expects.
The most useful question is whether Android Auto has ever worked on this exact phone and firmware. A device that never supported it needs a compatibility check. A previously working phone that fails after an update needs a different investigation.
Read the message before troubleshooting the connection
Record the complete error, not just “22.” This article concerns the Android Auto message about preinstallation or operating-system integration. A similarly numbered error in another app is a separate problem.
Google’s current Android Auto requirements describe it as integrated into compatible phones. They specify Android 9 or later for wired use, additional requirements for wireless projection, and no support for Android Go edition. Meeting the Android version requirement alone does not establish that a particular regional firmware supports the feature.
Search Settings for Android Auto. Also check Settings > Apps, enabling the option to show system apps if available. An app-drawer icon is not required. Conversely, seeing an installed Android Auto package does not prove that all necessary integration is present.
A phone that has never connected successfully
Start with the exact model and software build. Under Settings > About phone, record the model number, Android version, build number, and software region. Check whether the phone uses manufacturer firmware, a retailer-modified build, or a custom ROM.
Imported phones deserve model-specific checking. Two phones sold under similar names can have different regional firmware and Google-service integration. Do not assume that every device using HyperOS, ColorOS, or another manufacturer interface has the same limitation.
Ask the manufacturer whether Android Auto car projection is supported on your exact model and build. If the answer is no, repeatedly reinstalling Android Auto, clearing Bluetooth settings, or changing USB cables will not add missing firmware support.
A factory reset returns the phone to its installed firmware configuration. It does not install the system components absent from that firmware. Only consider a firmware change when the manufacturer provides a supported path for the precise hardware variant.
A phone that worked before an update or software change
A previously successful connection is valuable evidence. Identify what changed: a system update, a ROM installation, a debloating tool, or disabling a system app.
- Install available official phone updates and any Android Auto update offered through Google Play.
- Check that Android Auto is enabled in App info. If a system-modification tool removed or disabled it, use that tool’s documented reversal procedure for your device.
- Restart the phone and test again while parked.
- If the component is present and enabled, open Android Auto > Storage & cache > Clear cache. Menu labels vary by manufacturer.
Cache clearing can address temporary app state; it cannot repair absent operating-system integration. If Error 22 remains after an official update on an otherwise supported phone, check the manufacturer’s support notices for the same build and report the regression.
When several apps also began failing after the update, Apps Keep Crashing After an Android Update can help with that separate symptom. Do not treat unrelated app crashes as proof of the cause of Error 22.
Use another phone to distinguish the phone from the car
Connect a known-compatible phone to the same car using the same connection method. If it works while your phone consistently displays the preinstallation message, concentrate on your phone’s firmware and Android Auto configuration.
If neither phone connects, check the vehicle’s Android Auto setting and head-unit firmware. Cable replacement is useful for interrupted wired communication, but a cable cannot change which system components the phone includes.
Once the explicit Error 22 message is gone, ordinary setup troubleshooting may become appropriate. Google documents forgetting previously connected cars in Android Auto settings > Previously connected cars. You can then reconnect and complete the prompts. For general pairing failures or disconnects, use Android Auto Not Working.
Custom ROMs require ROM-specific support
A custom ROM can run Google apps while still lacking the integration Android Auto requires. Ask the ROM maintainer whether car projection is supported and which installation configuration is required.
A random APK, root module, or system-partition modification is not a dependable general fix. Bootloader changes and firmware flashing can erase data or leave the phone unable to boot. An unofficial “global ROM” download is not proof that a conversion is supported for your device.
Give support a report they can act on
Send the manufacturer or Android Auto support the full error message, phone model, firmware region and build, Android Auto version, vehicle or receiver model, connection method, and whether another phone works in the car. State clearly whether the feature worked before and which update or change preceded the failure.
That information helps distinguish unsupported firmware from a regression on a supported device. If the manufacturer confirms that your build lacks Android Auto support and offers no supported update, stop spending time on app resets. The practical option is a supported phone or an officially supported firmware configuration.
