Android Auto On TCL Flip 2

I am using a rooted TCL Flip 2 which I loaded g-apps with magisk. When trying to download android auto from the play store it says my device doesn’t support it. When downloading the apk with adb I get an error message. If anyone has experience or thoughts on this, please let me know here.

I successfully was able to get the app on my TCL phone by following this guide.
I got stuck by 2 steps though. The guide says to go to play store and update the AA app. When I go to the app on the play store there isn’t an option to update it rather it says this app isn’t compatible
Screenshot_20241007-130638
The second place I get stuck is on this step: * Open Activity Launcher**,** Find Android Auto then create a shortcut and launch by tapping on ”.companion.AndroidAutoActivity”.
There isn’t an option called “companion.AndroidAutoActivity”.
If anyone has any help please reply.

Here is the actual error I get when connecting it to a car
Screenshot_20241010-154517

You could try using hideprops to spoof your phone as an Android Auto supported device and then updating it through play store though you should probably sign out of play store and clear its data/cache before you use hideprops

Thank you. Can you elaborate on what hideprops is and how to do it.

You have to take the right gapps package. For Android Auto, you should take the full package.
Here’s a list of gapps package levels and what they do.

  1. Pico

Includes: Only the essential Google Play services needed to run apps dependent on Google services.

Purpose: For users who want the absolute minimum Google services for app compatibility without additional Google apps.

Size: Smallest.

  1. Nano

Includes: Core Google services and minimal essential apps (e.g., Google Play Services, Google Play Store, and Google Search).

Purpose: Offers slightly more functionality than Pico while still being lightweight. Great for users who want only the basics.

Size: Slightly larger than Pico.

  1. Micro

Includes: Adds a few more apps like Gmail, Google Calendar, and Google Text-to-Speech.

Purpose: Provides a bit more Google functionality, including some communication and productivity tools.

Size: Medium.

  1. Mini

Includes: Adds even more apps, such as Google Maps, Google Photos, and Google Keyboard (Gboard).

Purpose: A good balance for users who want essential Google apps without the full set of Google apps.

Size: Moderate.

  1. Full

Includes: All the Google apps typically found on a new device (e.g., Google Drive, Google Chrome, Google Duo).

Purpose: For users who want a close-to-stock Google experience with most of the major apps.

Size: Large.

  1. Stock

Includes: Everything found in the Full package plus additional system apps that are commonly pre-installed on Google-certified Android devices.

Purpose: Mimics the Google app setup on Pixel or stock Android devices. Best for users who want a full Google experience.

Size: Very large.

  1. Super

Includes: Everything in the Stock package plus optional apps like Google Books, Google News, and other lesser-used apps.

Purpose: Provides every possible Google app and service in the GApps suite. Ideal for users who want every Google app available.

Size: Largest.


So when you look for gapps packages, try to find the one with the right surname.
(I only use Pico and stock)

Well I believe getting the smaller package and than adding an app by downloading it whether through play store or apk is the same.
I think the phone is missing something that it needs, to handle android auto.

a regular app is the same, as chatgpt created the list…
but each package comes with different backround requirements.

And the one of the packages will give me everything I need for android auto?

technically

Its a magisk module that can spoof the devices fingerprint and some build properties to make your phone seem like another device (that would support Android Auto) here is some info on how it works

2 Likes

Once you install hideprops reboot your phone and run adb shell su props and in the shell follow the steps to edit the fingerprint and choosing a device (choose one that runs the same android version)

That’s also how you can certify your device.

Build props module and BusyBox module are from the best modules out there

Just to clarify did anyone end up getting android auto on the TCL Flip 2 there is alot of information here not sure what finally happened?

don’t have one

I as the OP never figured it out. But your welcome to test things and keep us updated.
I never tried anything more than downloading a magisk module that gave me the AA app, but it didn’t help me.

This guy seems to have gotten AA working on the TCL with MicroG and a magisk module. Prerequesites · HSBERG/TCL-FLIP-2-GUIDE Wiki · GitHub (scroll to the bottom of the page).

Being that I have Gapps and not MicroG, is that a reason why the module shouldn’t work for me?