Database Develop

Any Roms work with Android Auto?

I've tried three Roms (2 Oreo and 1 nougat) and I can't get Android Auto to work with any of them. Has anyone gotten Android Auto to work with any of the Roms available here?
Sent from my Nexus 6 using Tapatalk

It has worked well for me on the latest 7.1.2 Pure Nexus ROM. I am currently running AICP Oreo and it works great. It also worked on S.I.X. ROM Oreo and Republic of Madness Oreo ROMs for me.
What issues are you having?

Hi, I've been running Android Auto perfectly with Nitrogen OS until 2 weeks. Suddenly I can't connect my N6 correctly anymore. My car (Ford with SYNC system) tells that it can"t find Android Auto. I tried Stock version of N6 Nougat, S.I.X Oreo rom and same issue..
Could it be related to some app update (maps, google, AA,...) ?
Sometimes I get a red error screen from AA app telling me about "communication error code 17" but I can't find any reference about that anywhere.
any tip ?

imaGine00 said:
Hi, I've been running Android Auto perfectly with Nitrogen OS until 2 weeks. Suddenly I can't connect my N6 correctly anymore. My car (Ford with SYNC system) tells that it can"t find Android Auto. I tried Stock version of N6 Nougat, S.I.X Oreo rom and same issue..
Could it be related to some app update (maps, google, AA,...) ?
Sometimes I get a red error screen from AA app telling me about "communication error code 17" but I can't find any reference about that anywhere.
any tip ?
Click to expand...
Click to collapse
Have you tried a different cable? I had to try 3 of them before it worked right to start with in my F150

some premium Anker cable fromage Amazon is supposed to arrive any Time soon but I have doubts because I already tried with different cables. What is your setup? AA, Google and maps version ?? Thanks

imaGine00 said:
some premium Anker cable fromage Amazon is supposed to arrive any Time soon but I have doubts because I already tried with different cables. What is your setup? AA, Google and maps version ?? Thanks
Click to expand...
Click to collapse
AA - 2.7.573953-release
Google - 7.15.19.21.arm
Waze - 4.32.0.2
I don't use google maps anymore now that Waze is available for AA.
One thing that may work is to delete your phone out of Sync and delete Sync out of your phone both under bluetooth and AA. Once you have them removed. Just plug the phone into sync and let it re-setup everything (I don't even pair bluetooth separately, I let AA do the bluetooth pairing).
What version # of Sync3 do you have?

AAuto works great on my N6 with LineageOS on my Kia Sportage. It's a brand new 2018 Kia purchased two days ago. One of the main reasons for that purchase was AAuto in the electronics package.

bfmetcalf said:
AA - 2.7.573953-release
Google - 7.15.19.21.arm
Waze - 4.32.0.2
I don't use google maps anymore now that Waze is available for AA.
One thing that may work is to delete your phone out of Sync and delete Sync out of your phone both under bluetooth and AA. Once you have them removed. Just plug the phone into sync and let it re-setup everything (I don't even pair bluetooth separately, I let AA do the bluetooth pairing).
What version # of Sync3 do you have?
Click to expand...
Click to collapse
pairing bluetooth with AA didn't work after deleting Sync and phone config :/
Sync continue to say it can't reach AA.. still waiting for the new anker microUSB cable
And I got same app version installed too
here 's my sync version

imaGine00 said:
pairing bluetooth with AA didn't work after deleting Sync and phone config :/
Sync continue to say it can't reach AA.. still waiting for the new anker microUSB cable
And I got same app version installed too
here 's my sync version
Click to expand...
Click to collapse
Try clearing data for AA and see if that helps.

Still can't get it to work in a 2017 Chevy Tahoe. I have now tried 4 different cords and I am currently on Six Oreo Rom. I know the head unit is compatible since I had it working with the pixel 2 xl during the brief time I had that phone.
Do I need to change any settings such as USB debugging? What setting should I set it to when I connect the cord (i.e. Transfer Files, etc)?
Sent from my Nexus 6 using Tapatalk

Negotiator50 said:
Still can't get it to work in a 2017 Chevy Tahoe. I have now tried 4 different cords and I am currently on Six Oreo Rom. I know the head unit is compatible since I had it working with the pixel 2 xl during the brief time I had that phone.
Do I need to change any settings such as USB debugging? What setting should I set it to when I connect the cord (i.e. Transfer Files, etc)?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Try going into settings > six settings > Other > look for Enable MTP instead charging when connect to PC
Make sure that is UN-ticked. That will block AA from working for some reason.

bfmetcalf said:
Try going into settings > six settings > Other > look for Enable MTP instead charging when connect to PC
Make sure that is UN-ticked. That will block AA from working for some reason.
Click to expand...
Click to collapse
This did the trick!! Thank you so much!
Sent from my Nexus 6 using Tapatalk

bfmetcalf said:
Try going into settings > six settings > Other > look for Enable MTP instead charging when connect to PC
Make sure that is UN-ticked. That will block AA from working for some reason.
Click to expand...
Click to collapse
woooooh that did the trick ! Thank you !!

I use it with crDroid 4.0 Beta 6 and everything work ...

android auto and android 10

I have a Galaxy S9+ using a sony head unit. Since the android 10 update most things dont work anymore. Samsung doesnt respond to questions and either does google. I would roll back to 9 but my bootloader is locked. Is there anyway around this ?

I ran into 2 problems after upgrading to Android 10 on my S10e.
1. I had second AA app installed (I think it was the one for phone display)
2. Adb debug has to be off
Also app settings are accessible only through Settings -> Apps -> AA -> In-app notifications settings

mrdlejzr said:
I ran into 2 problems after upgrading to Android 10 on my S10e.
1. I had second AA app installed (I think it was the one for phone display)
2. Adb debug has to be off
Also app settings are accessible only through Settings -> Apps -> AA -> In-app notifications settings
Click to expand...
Click to collapse
This is because AA is built-in into Android 10, it is part of the operating system, so there is no need for the AA app. Upgrading to Android 10 should automatically remove the AA apk used on Android 9.
Sent from my SM-N975F using Tapatalk

uhi711 said:
This is because AA is built-in into Android 10, it is part of the operating system, so there is no need for the AA app. Upgrading to Android 10 should automatically remove the AA apk used on Android 9.
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
I uninstalled the old aa app on my phone because i thought it was part of the os, restarted the phone and plugged it in my truck and it would not connect. The only way aa almost works is if you install the app on your phone.

As I said before, AA is built-in in Android 10, so there is no need for the apk. But you are right, there are still a lot of problems with AA on car's screen and Android 10. The fact that your phone does not connect to your car's infotainment system or that you are able to sometimes use AA after installing the apk, does not mean that it should be like this. I am sure that you sideloaded the apk because it shouldn't appear on your Play store after upgrading to Android 10.
I, for example, I refused to upgrade because of the many bugs I read about when using AA. I suffered enough (repeated connection problems), in the beginning, after upgrading my phone from the Note 8 with Android 8 to the Note 10+ with Android 9. I'm afraid that it is not possible to go back to Android 9, as far as I know. You'll have to stick with what you have and dig the internet to find possible solutions, because I'm sure there isn't yet a straight forward fix for your AA problem.
Sent from my SM-N975F using Tapatalk

uhi711 said:
As I said before, AA is built-in in Android 10, so there is no need for the apk. But you are right, there are still a lot of problems with AA on car's screen and Android 10. The fact that your phone does not connect to your car's infotainment system or that you are able to sometimes use AA after installing the apk, does not mean that it should be like this. I am sure that you sideloaded the apk because it shouldn't appear on your Play store after upgrading to Android 10.
I, for example, I refused to upgrade because of the many bugs I read about when using AA. I suffered enough (repeated connection problems), in the beginning, after upgrading my phone from the Note 8 with Android 8 to the Note 10+ with Android 9. I'm afraid that it is not possible to go back to Android 9, as far as I know. You'll have to stick with what you have and dig the internet to find possible solutions, because I'm sure there isn't yet a straight forward fix for your AA problem.
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
So i uninstalled AA from my phone and then restarted it. Then i backed it up with smart switch, i then did a factory reset. Then i did a clean install of 10 from Chimera. I restored my phone and plugged it into my truck. It proceeded to install AA and still not worth a damn lol. That was a good 3 hours not well spent. So now i will play no more until if ever a fix comes out. Thanks

dinosaurus1 said:
So i uninstalled AA from my phone and then restarted it. Then i backed it up with smart switch, i then did a factory reset. Then i did a clean install of 10 from Chimera. I restored my phone and plugged it into my truck. It proceeded to install AA and still not worth a damn lol. That was a good 3 hours not well spent. So now i will play no more until if ever a fix comes out. Thanks
Click to expand...
Click to collapse
Sorry to hear about all the trouble. Just keep searching the internet about your specific problem and configuration. If you still have your previous phone and if it still has a working AA, you could use it just in your car connected to your wifi hotspot from your Note 10. Also try a different cable, a shorter one (I use a 1 foot only cable), all my connection problems went away with this shorter cable bought on Aliexpress. Wish you luck!
Sent from my SM-N975F using Tapatalk
---------- Post added at 07:59 PM ---------- Previous post was at 07:50 PM ----------
I forgot to ask, did you try using AA with a wireless connection? If you have a new car, chances are that you could use wireless connection between your phone and the car. There is a setting in AA to enable this. Just set this switch on before trying to connect to the car's infotainment system.
Sent from my SM-N975F using Tapatalk

@uhi711 what did you do to resolve the issues on note 10+
Since Samsung updated to android 10, my AA has not worked.
Cables are same that used to work on Android 9
Keeps disconnecting and reconnecting
Tried clear cache and data on AA
Reset the cars head unit
Used new cables, old cables, OEM cables same issues
Haven't tried a small cable, will try the charger cable that comes with Sony xm3 head phones

deepudips said:
@uhi711 what did you do to resolve the issues on note 10+
Since Samsung updated to android 10, my AA has not worked.
Cables are same that used to work on Android 9
Keeps disconnecting and reconnecting
Tried clear cache and data on AA
Reset the cars head unit
Used new cables, old cables, OEM cables same issues
Haven't tried a small cable, will try the charger cable that comes with Sony xm3 head phones
Click to expand...
Click to collapse
Unfortunately, I do not have a satisfactory answer for you. I just didn't upgrade my phone to Android 10, because of the many bug reports I read about. A long time ago, when I was using the Note 8 and Android 8, I had the same connection problems for a few months. Then, the only thing that helped me was using short (20-25 cm) quality cables, bought on Aliexpress. It might also be a coincidence, I'm not sure, because in the same time I changed cable after cable, Google also updated AA. As of now, I'm using the Note 10+ with Android 9 and the same short cable that I think it fixed my connection problem then, and I still don't have any problem. You'll just have to wait patiently for Google to fix the bugs.
Sent from my SM-N975F using Tapatalk

Hi
I have Lineage OS 17.1 which is Android 10.
Should I install just "AA for phone" instead of normal AA ?
With "normal" AA installed is working, except for notifications that I don't get for any apps (Whatsapp, Telegram,...)
Thanks

woody4165 said:
Hi
I have Lineage OS 17.1 which is Android 10.
Should I install just "AA for phone" instead of normal AA ?
With "normal" AA installed is working, except for notifications that I don't get for any apps (Whatsapp, Telegram,...)
Thanks
Click to expand...
Click to collapse
I'm sorry, I'm afraid I can't help you. I don't know what is Lineage OS and how it works. What I do know is that there is no such a thing as different AA versions. There is only one kind of AA app downloadable from the Play store if you have Android 9 or less on your phone. If you have Android 10 installed on your phone, then you do not need the AA app and you won't be able to download it from the Play store, because it is already built-in in the OS (Android 10).
Sent from my SM-N975F using Tapatalk

I had the same problem with my Note 9 with Android 10, it kept connecting and disconnecting. Restarting the phone worked for me.

The couple AA and Android 10 is known for a lot of bugs and connection problems.
Sent from my SM-N975F using Tapatalk

Any way to get android auto as a host on a tablet?

I have an android auto capable vehicle. I also have a tablet that I use for offroading. the tablet is not compatible with android auto. When plugged in to the car, the tablet recognizes that AA is there, and asks me to update, but the play store tells me it is not compatible. AA is now baked into Android, so the only store app that is available is AA for phone screens, which is now being updated to the new version which is like, AA lite. This is on a rooted Lenovo M10 FHD Plus, so roms are kinda out of the question as theyre not available and I wouldnt know where to start writing my own; but Magisk is installed along with busybox and xposed framework. Does anyone know how to either trick the tablet into running AA the same way that my phone does (natively, included in android) or have a solution for this?

Have your tried to use titanium backup (or some other apk extractor) to copy the AA apk from your phone to the tablet and see if it runs?

JohnC said:
Have your tried to use titanium backup (or some other apk extractor) to copy the AA apk from your phone to the tablet and see if it runs?
Click to expand...
Click to collapse
Not possible, I have no plans to root my phone. I sideloaded the apk though, and it does work as intended as "android auto for phone screens" what I'm trying to do is get it fully integrated as if it were a phone. My s21 ultra for example, doesn't even have an icon for android auto it's installed as a service (afaik) and is only found in my system settings.

What other differences are there between how the tablet runs AA and how it runs on your phone (besides that the tablet has an icon for AA)?

Im trying to make it so that the tablet, hooks up to the car and runs android auto on the cars screen. I don't think AA for phone screens supports host, though I could be wrong?

evilsway said:
Im trying to make it so that the tablet, hooks up to the car and runs android auto on the cars screen. I don't think AA for phone screens supports host, though I could be wrong?
Click to expand...
Click to collapse
What do you mean by "host"?
If you can get the AA APK running on the tablet then it should work as expected (show on the car's screen).
So, what exactly is not happening?

Yeah, I didn't realize it would work that way. I ended up taking the harder route, rooted the tablet and installed a gsi rom. Works beautifully now.

Even with APK AA doesn't work in vehicle the same way it does with a phone. I made sure APK is the same version as car. No matter what I try, android auto will load on tablet but the vehicle will not recognize it and launch it on car screen. There must be a way to do this with a rooted tablet and AA APK. Anyone tinkered with this? I have a 2021 f-150 which even supports wireless AA from my phone.
@evilsway were you able to get this to work?

I guess Android Auto requires a device which is capable to make phone calls...

CoolWalk based UI is rolling out

Coolwalk AA UI is rolling out as a public beta right now ​Seems that beta channel is full, but APK should soon be available at ApkMirror
Android Auto's long-awaited redesign is nearly here — here's how you can take it for a test drive​

Which version are you in ?
I think it's still a server side thing sadly for non beta members

It's a server-side switch, so even if you have the latest beta apk, it won't help.

RaZor83 said:
Which version are you in ?
I think it's still a server side thing sadly for non beta members
Click to expand...
Click to collapse
Yes, you have the point here, it's a server side.
I'm at latest beta, and I've tried rebooting phone and clearing AA cache, but still no coolwalk interface on both wired and wireless AA.
Anyhow, this is last phase of testing, and we should soon have it

Still hope to get it public before 2023

If you set the flags with root now. Will they reset?

cammykool said:
If you set the flags with root now. Will they reset?
Click to expand...
Click to collapse
I have set them on saturday.... still works!

HofaTheRipper said:
I have set them on saturday.... still works!
Click to expand...
Click to collapse
What all did you enable to get it working? Just following OP and it doesn't reset?

cammykool said:
What all did you enable to get it working? Just following OP and it doesn't reset?
Click to expand...
Click to collapse
did the termux commands and it still works.
Thread 'Google Cast & "Coolwalk"' https://forum.xda-developers.com/t/google-cast-coolwalk.4396533/
before google released it to beta, it reseted after 1 day... now it works since 3 days

unfortunately, it got reseted today :-(

Become a beta tester, go to settings, apps, android auto: click on the three dots upper right side of the screen en select 'uninstall updates'. Reboot the phone and update android auto to the latest available version. Connect to the car, setup android auto and disconnect from the car/headunit again. Reboot your phone once more and android auto is 'Coolwalk" when connected again.
Worked for me on a Oneplus 10 Pro with the latest Oxygen 13 OS, headunit in the car is an aftermarket Kenwood DMX8019DABS,

Works for a day then just reverts back, can't seem to make it stick.

[email protected] said:
Become a beta tester, go to settings, apps, android auto: click on the three dots upper right side of the screen en select 'uninstall updates'. Reboot the phone and update android auto to the latest available version. Connect to the car, setup android auto and disconnect from the car/headunit again. Reboot your phone once more and android auto is 'Coolwalk" when connected again.
Worked for me on a Oneplus 10 Pro with the latest Oxygen 13 OS, headunit in the car is an aftermarket Kenwood DMX8019DABS,
Click to expand...
Click to collapse
That did not work for me. Probably because I'm not a beta tester and I've been trying to become one for years. That's with the latest daily build on 11.21.2022

I'm an Android Auto beta tester and my issue is that if I reboot my phone then connect to my car, Coolwalk UI will load, then if I connect to my car again a few hours later it loads back the old AA UI.
Any ideas why?

Same problem here, this beta coolwalk rollout is a complete disaster!

Cyclops1055 said:
I'm an Android Auto beta tester and my issue is that if I reboot my phone then connect to my car, Coolwalk UI will load, then if I connect to my car again a few hours later it loads back the old AA UI.
Any ideas why?
Click to expand...
Click to collapse
For me as beta tester Coolwalk keeps working, also after multiple reboots. I'm also beta tester for the Google app, Waze and Maps. I'm on Oxygen 13 (Android 13). Not sure what makes the difference compared to your situation.

[email protected] said:
For me as beta tester Coolwalk keeps working, also after multiple reboots. I'm also beta tester for the Google app, Waze and Maps. I'm on Oxygen 13 (Android 13). Not sure what makes the difference compared to your situation.
Click to expand...
Click to collapse
Here is what I have done to get Coolwalk working again, do note that I am an Android Auto beta tester.
I went into Settings>apps>Android Auto
Force stop Android Auto
Cleared data
Uninstalled updates
Installed latest Android Auto beta version (8.6.1246) from Apk Mirror
Reboot phone
Installed latest Android Auto beta version (8.6.1246) again
Connected to car and AA Coolwalk UI has loaded
Disconnected from car
Waited 30 minutes and reconnected to car
Coolwalk UI still loaded
I will see in about 2-3 hours if it sticks
**So I tried AA after 2.5 hours and AA loaded the old UI

Cyclops1055 said:
Here is what I have done to get Coolwalk working again, do note that I am an Android Auto beta tester.
I went into Settings>apps>Android Auto
Force stop Android Auto
Cleared data
Uninstalled updates
Installed latest Android Auto beta version (8.6.1246) from Apk Mirror
Reboot phone
Installed latest Android Auto beta version (8.6.1246) again
Connected to car and AA Coolwalk UI has loaded
Disconnected from car
Waited 30 minutes and reconnected to car
Coolwalk UI still loaded
I will see in about 2-3 hours if it sticks
**So I tried AA after 2.5 hours and AA loaded the old UI
Click to expand...
Click to collapse
same happened to me... also beta tester.... but:
-- clear cache of AA
-- reboot phone
-- start headunit server in AA settings (dev has to be activated)
-- keep headunit server running
As long as i connect to my car with headunit server running, coolwalk keeps enabled for me since 4 days now.
I didnt notice any additional battery drain.

I
HofaTheRipper said:
same happened to me... also beta tester.... but:
-- clear cache of AA
-- reboot phone
-- start headunit server in AA settings (dev has to be activated)
-- keep headunit server running
As long as i connect to my car with headunit server running, coolwalk keeps enabled for me since 4 days now.
I didnt notice any additional battery drain.
Click to expand...
Click to collapse
I tried your suggestion and Coolwalk UI loaded, I will see if it will still load again tomorrow.

I've experienced this AA UI roll back to the old one. But after cleared the cache and rebooting the phone it turns back to cool walk UI until now.
This problem appears when I'm using the wireless AA adapter/dongle (Carlinkit CCPA), finally I'm installed a Head Unit Reloader on my HU (it's a Pioneer Android) and works perfecly without adapter.
Also it still showed cool walk UI when I connect my phone to my other car that use an OEM Toyota Head unit with wireless AA adapter (Carlinkit CP2A).
Maybe its a adapter/dongle firmware compatibility issue triggered the AA to roll back to the old one...

installing android auto on an lte tablet.

Found a lot of info on this for rooted devices. but not to much for non rooted devices
i want to install AA on a LTE tablet that will stay in my car. the tablet will run other car related apps.
but im tired of having my phone tied up playing music draining my battery. specially on long trip.
also i cant record videos or talk on the phone and still have music lol i know things i shouldnt be doing anyway..
is there anyway to make it work. i tried to sideload it. but got an error 22 that android auto needed to be installed on my os.
any help would be appreciated

maybe try AA emulator on this tablet?

Android Auto app is not targeted to tablets, only phones. And since Android 10, Android Auto is a system app, not a user app. So, if your current Android version is 10 or higher and you sideloaded the Android Auto apk, it will not work. To make it work you'll need to root the tablet and install Android Auto as a system app.
[GSI] Fix 'Communication error 22' on Android Auto
If you've installed a custom ROM that doesn't come with Android Auto pre-installed, you'll get the following error when connecting your phone to your car (the Android Auto app opens correctly, the error is only shown when you connect to the car)...
forum.xda-developers.com
The easiest alternative is to use your tablet as an Android Auto receiver using Hedunit Reloaded Emulator. It's available on the Play Store and is very cheap. It has even a free trial app with a 5 minute limit if you want to test it.
When installed, this apps acts as an Android Auto receiver. This way if you connect your phone to your tablet using an OTG cable (or a USB-C to USB-C cable if both devices have this port) your phone will detect the tablet as an Android Auto compatible headunit and show stuff on it.
You can use this app in Android headunits if they don't have Android auto compatibility, as long as they support USB OTG mode.