• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Android Auto and Lineage 17.1

  • Thread starter Deleted member 10657845
  • Start date
Search This thread
D

Deleted member 10657845

Guest
I instale the ( Lineage os 17.1.20200415 and Gapps) on my S8+ . All ok ,Thanks to the developer . The only problem is with Android Auto and the usb connection in Lineage software... maybe authorities usb choice is not to file tranfer...
In S8+ with original samsung os "android 9" the application android auto with same version as above function very well.
I think the problem is the way that lineage manage the usb connection with Android Auto!!!
When Android Auto strat in the infotainment the phone usb force (goes) to "without file transfer" and the connection stops

Any help
 

Attachments

  • 20201204_080831.jpg
    20201204_080831.jpg
    3.6 MB · Views: 721

sunarowicz

Member
Jun 16, 2020
26
6
I instale the ( Lineage os 17.1.20200415 and Gapps) on my S8+ . All ok ,Thanks to the developer . The only problem is with Android Auto and the usb connection in Lineage software... maybe authorities usb choice is not to file tranfer...
In S8+ with original samsung os "android 9" the application android auto with same version as above function very well.
I think the problem is the way that lineage manage the usb connection with Android Auto!!!
When Android Auto strat in the infotainment the phone usb force (goes) to "without file transfer" and the connection stops

Any help
I observe the same behavior when connecting the old Samsung S5 Neo running LOS 17.1 to the HU. The USB connection type switches to "no data transfer" just when plugged to HU's USB port regardless of the type it was set to before. But it does not matter, it connects to HU anyway.

But I still cannot use it as it disconnects from HU some time after. I guess it is not related to the USB connection type as it keeps connection for some time (from couple of seconds to 1 or 2 minutes) before it disconnects from HU.
 

zakupy.dominik

New member
Dec 19, 2020
1
1
Me too. I have Redmi Note 7 and lineage 17.1 with gapps (nano i stock tested) and app shows that accessory is not supported and car display shows that application quit unexpectedly. Mayby some google service is broken/uninstalled? I tested also on PixelExperience ROM and it works fine.
 
Last edited:
  • Like
Reactions: d_g_m_2000

d_g_m_2000

Senior Member
Jul 6, 2015
362
90
also, have moto g6 plus and do the same behaviour... on stock rom andorid auto works great, in pixel experience also work great, just lineage send mi the "device not compatible" popup. does anyone had a work around or do i need to reflash another rom. thanks in advance for your comments.
 

McAnik

New member
Mar 14, 2021
2
0
Me too.

My wife’s stock pixel 4, no problem.
My Samsung A5 2017 when it had stock ROM, no problem.
My Samsung A5 2017 with LOS 17.1, not working with my truck’s Android Auto.

AA app on the phone installs and functions well, but when plugged into the 2018 Chevy, the phone says:
Any searching and reading shows many having this issue with 16 and 17 but not earlier versions.
 

d_g_m_2000

Senior Member
Jul 6, 2015
362
90
Me too.

My wife’s stock pixel 4, no problem.
My Samsung A5 2017 when it had stock ROM, no problem.
My Samsung A5 2017 with LOS 17.1, not working with my truck’s Android Auto.

AA app on the phone installs and functions well, but when plugged into the 2018 Chevy, the phone says:
Any searching and reading shows many having this issue with 16 and 17 but not earlier versions.
solve the same issue using an opengapps build back from december 2020, i guess is some bug from recent builds
 

McAnik

New member
Mar 14, 2021
2
0
Oooooh Yeah!

That fixed it! I re-flashed with open gapps 2020-12-01 and the truck picked it up right away.

In the truck, when I plugged it in, I pressed Android Auto on the display and it hung saying it was checking messages. Even after reconnecting the USB a few times. So on my dash I went to settings, AA, where all phones are listed and pressed mine to make it inactive, then again to make it active.
Then everything worked!

Thanks so much.
 

JohnE2

New member
Mar 6, 2021
3
0
I have just installed LOS 17.1 on my Pixel 5", but with Microg rather than OpenGapps. Not downloaded AA just yet, and wondered if others have had issues with Microg?
 

G A S T

Senior Member
Apr 20, 2018
211
97
Xiaomi Mi 4
Samsung Galaxy S6
Me too.

My wife’s stock pixel 4, no problem.
My Samsung A5 2017 when it had stock ROM, no problem.
My Samsung A5 2017 with LOS 17.1, not working with my truck’s Android Auto.

AA app on the phone installs and functions well, but when plugged into the 2018 Chevy, the phone says:
Any searching and reading shows many having this issue with 16 and 17 but not earlier versions.
I had absolutely no issues with LOS 17.1 and Android Auto together with my smart EQ, but now since April, after the Upgrade to LOS 18.1 I get exactly the same error output like you.

Is this problem Android 11 or OpenGApps related? I'm on the latest official OpenGApps test build from january since there is nothing newer available atm. 🤔
 
Last edited:

d_g_m_2000

Senior Member
Jul 6, 2015
362
90
I had absolutely now issues with LOS 17.1 and Android Auto together with my smart EQ, but now since April, after the Upgrade to LOS 18.1 I get exactly the same error output like you.

Is this problem Android 11 or OpenGApps related? I'm on the latest official OpenGApps test build from january since there is nothing newer available atm. 🤔
i think it is a opengapps problem related. i had android 11 with pixel experience (with gapps included) on my moto g6 plus and AA worked normally... but when i flashed lineages 17.1 + opengapps newer builds it just fail.
 

SteveMKII

Member
May 3, 2021
10
13
Oooooh Yeah!

That fixed it! I re-flashed with open gapps 2020-12-01 and the truck picked it up right away.

In the truck, when I plugged it in, I pressed Android Auto on the display and it hung saying it was checking messages. Even after reconnecting the USB a few times. So on my dash I went to settings, AA, where all phones are listed and pressed mine to make it inactive, then again to make it active.
Then everything worked!

Thanks so much.
Hi, I am having the same issue with crDroid on Android 11 using gapps aroma and pico build from 2021-01-30. Are you able to provide one from December 2020 for Android 11? Or are you on Android 10? I don't see it here. Or do you know if another build works? I'm hoping to use open gapps aroma. Thanks for the help.
 
Last edited:

SteveMKII

Member
May 3, 2021
10
13
Hey guys I found a solution for those who can't get Android Auto to display on their car screen with Android 11 and gapps.

So after having issues with the gapps I tried MindTheGapps and Android Auto was working on there. I noticed that when I flashed the ROM Android Auto was installed already, but it was just a little stub app, only about 3 mb. So I decided to copy the folder containing the apk file and install it into a ROM with OpenGapps. The original file was placed in system/product/priv-app, so I copied it there using TWRP then rebooted. It did not work. So I uninstalled all the updates to AA and removed it then pasted it back in, and ended up in a bootloop. So finally I tried installing the stub app in /system/priv-app and rebooted. I then updated AA on the play store and it worked! So it seems that in order to get AA working you need this little stub app that must contain the necessary code to connect to your car. Note that AA will no longer show up in your launcher but you can download the "Android Auto for Phone Screen" app if you need to use it both on your car screen and on your phone in a car without an AA head unit. So the steps are as follows

Copy the attached apk file into a folder called AndroidAutoStubPrebuilt
Completely uninstall AA from your phone, both in user apps and system apps.
Boot into TWRP
Mount System in the "Mount" setting in TWRP
Copy the AndroidAutoStubPrebuilt folder containing the attached apk into system/priv-app/ (or your preferred folder but it needs to be in a system folder, I had a bootloop when I installed it into system/product/priv-app so if something like that happens try a different folder)
reboot your phone
install play store update for AA
set up AA on your phone
Connect to your car.
Enjoy.

Hopefully this fixes the issue for you guys as well. If it does, please let me know!

For reference I am using a US Moto G5 plus XT1687 (Potter) running CrDroid 7.5 with Open Gapps Aroma and Magisk.

This stub app comes from flashing the MindTheGapps package and is in no way my creation, I am simply sharing the apk from it for those who are using open gapps and can't get AA working. Thanks MTG, I couldn't have found this solution without it!​

 

Attachments

  • AndroidAutoStubPrebuilt.apk
    3.1 MB · Views: 341

G A S T

Senior Member
Apr 20, 2018
211
97
Xiaomi Mi 4
Samsung Galaxy S6
Hey guys I found a solution for those who can't get Android Auto to display on their car screen with Android 11 and gapps.

So after having issues with the gapps I tried MindTheGapps and Android Auto was working on there. I noticed that when I flashed the ROM Android Auto was installed already, but it was just a little stub app, only about 3 mb. So I decided to copy the folder containing the apk file and install it into a ROM with OpenGapps. The original file was placed in system/product/priv-app, so I copied it there using TWRP then rebooted. It did not work. So I uninstalled all the updates to AA and removed it then pasted it back in, and ended up in a bootloop. So finally I tried installing the stub app in /system/priv-app and rebooted. I then updated AA on the play store and it worked! So it seems that in order to get AA working you need this little stub app that must contain the necessary code to connect to your car. Note that AA will no longer show up in your launcher but you can download the "Android Auto for Phone Screen" app if you need to use it both on your car screen and on your phone in a car without an AA head unit. So the steps are as follows

Copy the attached apk file into a folder called AndroidAutoStubPrebuilt
Completely uninstall AA from your phone, both in user apps and system apps.
Boot into TWRP
Mount System in the "Mount" setting in TWRP
Copy the AndroidAutoStubPrebuilt folder containing the attached apk into system/priv-app/ (or your preferred folder but it needs to be in a system folder, I had a bootloop when I installed it into system/product/priv-app so if something like that happens try a different folder)
reboot your phone
install play store update for AA
set up AA on your phone
Connect to your car.
Enjoy.

Hopefully this fixes the issue for you guys as well. If it does, please let me know!

For reference I am using a US Moto G5 plus XT1687 (Potter) running CrDroid 7.5 with Open Gapps Aroma and Magisk.

This stub app comes from flashing the MindTheGapps package and is in no way my creation, I am simply sharing the apk from it for those who are using open gapps and can't get AA working. Thanks MTG, I couldn't have found this solution without it!​


Very Interesting! I hope that the OGApps team will take account of your important hint and that we'll find a fix in the next builds.👌
 

hannesz

Member
Apr 13, 2020
7
4
Hey guys I found a solution for those who can't get Android Auto to display on their car screen with Android 11 and gapps.

So after having issues with the gapps I tried MindTheGapps and Android Auto was working on there. I noticed that when I flashed the ROM Android Auto was installed already, but it was just a little stub app, only about 3 mb. So I decided to copy the folder containing the apk file and install it into a ROM with OpenGapps. The original file was placed in system/product/priv-app, so I copied it there using TWRP then rebooted. It did not work. So I uninstalled all the updates to AA and removed it then pasted it back in, and ended up in a bootloop. So finally I tried installing the stub app in /system/priv-app and rebooted. I then updated AA on the play store and it worked! So it seems that in order to get AA working you need this little stub app that must contain the necessary code to connect to your car. Note that AA will no longer show up in your launcher but you can download the "Android Auto for Phone Screen" app if you need to use it both on your car screen and on your phone in a car without an AA head unit. So the steps are as follows

Copy the attached apk file into a folder called AndroidAutoStubPrebuilt
Completely uninstall AA from your phone, both in user apps and system apps.
Boot into TWRP
Mount System in the "Mount" setting in TWRP
Copy the AndroidAutoStubPrebuilt folder containing the attached apk into system/priv-app/ (or your preferred folder but it needs to be in a system folder, I had a bootloop when I installed it into system/product/priv-app so if something like that happens try a different folder)
reboot your phone
install play store update for AA
set up AA on your phone
Connect to your car.
Enjoy.

Hopefully this fixes the issue for you guys as well. If it does, please let me know!

For reference I am using a US Moto G5 plus XT1687 (Potter) running CrDroid 7.5 with Open Gapps Aroma and Magisk.

This stub app comes from flashing the MindTheGapps package and is in no way my creation, I am simply sharing the apk from it for those who are using open gapps and can't get AA working. Thanks MTG, I couldn't have found this solution without it!​


Brilliant!! This just did the trick with LOS 18.1 and opengapps 11 beta 20210130 on my XZ1 compact. I've been holding off on the update because of this. Thank you!!!
 
  • Like
Reactions: ChriMo

aaron.castro1990

New member
May 14, 2021
1
0
Hey guys I found a solution for those who can't get Android Auto to display on their car screen with Android 11 and gapps.

So after having issues with the gapps I tried MindTheGapps and Android Auto was working on there. I noticed that when I flashed the ROM Android Auto was installed already, but it was just a little stub app, only about 3 mb. So I decided to copy the folder containing the apk file and install it into a ROM with OpenGapps. The original file was placed in system/product/priv-app, so I copied it there using TWRP then rebooted. It did not work. So I uninstalled all the updates to AA and removed it then pasted it back in, and ended up in a bootloop. So finally I tried installing the stub app in /system/priv-app and rebooted. I then updated AA on the play store and it worked! So it seems that in order to get AA working you need this little stub app that must contain the necessary code to connect to your car. Note that AA will no longer show up in your launcher but you can download the "Android Auto for Phone Screen" app if you need to use it both on your car screen and on your phone in a car without an AA head unit. So the steps are as follows

Copy the attached apk file into a folder called AndroidAutoStubPrebuilt
Completely uninstall AA from your phone, both in user apps and system apps.
Boot into TWRP
Mount System in the "Mount" setting in TWRP
Copy the AndroidAutoStubPrebuilt folder containing the attached apk into system/priv-app/ (or your preferred folder but it needs to be in a system folder, I had a bootloop when I installed it into system/product/priv-app so if something like that happens try a different folder)
reboot your phone
install play store update for AA
set up AA on your phone
Connect to your car.
Enjoy.

Hopefully this fixes the issue for you guys as well. If it does, please let me know!

For reference I am using a US Moto G5 plus XT1687 (Potter) running CrDroid 7.5 with Open Gapps Aroma and Magisk.

This stub app comes from flashing the MindTheGapps package and is in no way my creation, I am simply sharing the apk from it for those who are using open gapps and can't get AA working. Thanks MTG, I couldn't have found this solution without it!​

How can I uninstall the Android Auto from user apps and system apps?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 9
    Hey guys I found a solution for those who can't get Android Auto to display on their car screen with Android 11 and gapps.

    So after having issues with the gapps I tried MindTheGapps and Android Auto was working on there. I noticed that when I flashed the ROM Android Auto was installed already, but it was just a little stub app, only about 3 mb. So I decided to copy the folder containing the apk file and install it into a ROM with OpenGapps. The original file was placed in system/product/priv-app, so I copied it there using TWRP then rebooted. It did not work. So I uninstalled all the updates to AA and removed it then pasted it back in, and ended up in a bootloop. So finally I tried installing the stub app in /system/priv-app and rebooted. I then updated AA on the play store and it worked! So it seems that in order to get AA working you need this little stub app that must contain the necessary code to connect to your car. Note that AA will no longer show up in your launcher but you can download the "Android Auto for Phone Screen" app if you need to use it both on your car screen and on your phone in a car without an AA head unit. So the steps are as follows

    Copy the attached apk file into a folder called AndroidAutoStubPrebuilt
    Completely uninstall AA from your phone, both in user apps and system apps.
    Boot into TWRP
    Mount System in the "Mount" setting in TWRP
    Copy the AndroidAutoStubPrebuilt folder containing the attached apk into system/priv-app/ (or your preferred folder but it needs to be in a system folder, I had a bootloop when I installed it into system/product/priv-app so if something like that happens try a different folder)
    reboot your phone
    install play store update for AA
    set up AA on your phone
    Connect to your car.
    Enjoy.

    Hopefully this fixes the issue for you guys as well. If it does, please let me know!

    For reference I am using a US Moto G5 plus XT1687 (Potter) running CrDroid 7.5 with Open Gapps Aroma and Magisk.

    This stub app comes from flashing the MindTheGapps package and is in no way my creation, I am simply sharing the apk from it for those who are using open gapps and can't get AA working. Thanks MTG, I couldn't have found this solution without it!​

    4
    Thanks for sharing, we'll definitely include this (or something similar) in our next builds.
    1
    Me too. I have Redmi Note 7 and lineage 17.1 with gapps (nano i stock tested) and app shows that accessory is not supported and car display shows that application quit unexpectedly. Mayby some google service is broken/uninstalled? I tested also on PixelExperience ROM and it works fine.
    1
    I have just installed LOS 17.1 on my Pixel 5", but with Microg rather than OpenGapps. Not downloaded AA just yet, and wondered if others have had issues with Microg?
    Go to microg thread for more info.. I think AA is not supported by microg.
    1
    Hey guys I found a solution for those who can't get Android Auto to display on their car screen with Android 11 and gapps.

    So after having issues with the gapps I tried MindTheGapps and Android Auto was working on there. I noticed that when I flashed the ROM Android Auto was installed already, but it was just a little stub app, only about 3 mb. So I decided to copy the folder containing the apk file and install it into a ROM with OpenGapps. The original file was placed in system/product/priv-app, so I copied it there using TWRP then rebooted. It did not work. So I uninstalled all the updates to AA and removed it then pasted it back in, and ended up in a bootloop. So finally I tried installing the stub app in /system/priv-app and rebooted. I then updated AA on the play store and it worked! So it seems that in order to get AA working you need this little stub app that must contain the necessary code to connect to your car. Note that AA will no longer show up in your launcher but you can download the "Android Auto for Phone Screen" app if you need to use it both on your car screen and on your phone in a car without an AA head unit. So the steps are as follows

    Copy the attached apk file into a folder called AndroidAutoStubPrebuilt
    Completely uninstall AA from your phone, both in user apps and system apps.
    Boot into TWRP
    Mount System in the "Mount" setting in TWRP
    Copy the AndroidAutoStubPrebuilt folder containing the attached apk into system/priv-app/ (or your preferred folder but it needs to be in a system folder, I had a bootloop when I installed it into system/product/priv-app so if something like that happens try a different folder)
    reboot your phone
    install play store update for AA
    set up AA on your phone
    Connect to your car.
    Enjoy.

    Hopefully this fixes the issue for you guys as well. If it does, please let me know!

    For reference I am using a US Moto G5 plus XT1687 (Potter) running CrDroid 7.5 with Open Gapps Aroma and Magisk.

    This stub app comes from flashing the MindTheGapps package and is in no way my creation, I am simply sharing the apk from it for those who are using open gapps and can't get AA working. Thanks MTG, I couldn't have found this solution without it!​


    Brilliant!! This just did the trick with LOS 18.1 and opengapps 11 beta 20210130 on my XZ1 compact. I've been holding off on the update because of this. Thank you!!!