I have a Samsung S6 running unofficial Lineage 15.1 along with Super OpenGApps with a customisation file to prevent several apps getting installed. Android Auto gets installed with the Super package. If I try and launch Android Auto it starts but crashes more or less immediately. I have attached a screenshot of the error message. It worked on Lineage 14.1 and it worked on a previous version of OpenGApps with Lineage 15.1 so it might just be Google need to fix the app.
ADB100 said:
I have a Samsung S6 running unofficial Lineage 15.1 along with Super OpenGApps with a customisation file to prevent several apps getting installed. Android Auto gets installed with the Super package. If I try and launch Android Auto it starts but crashes more or less immediately. I have attached a screenshot of the error message. It worked on Lineage 14.1 and it worked on a previous version of OpenGApps with Lineage 15.1 so it might just be Google need to fix the app.
Click to expand...
Click to collapse
I have edited the OpenGApps configuration file to prevent Android Auto getting installed and have installed the .apk manually to see if this makes any difference. I downloaded and installed all AA releases (3.9, 3.7, 3.6, 3.5, 3.4, 3.3, 3.2, 3.1, 3.0 and 2.9) and the behaviour is the same with each.
I have an Android 8.0 MTCD head unit in my car (Malaysk 8.0 ROM v3.2.1) and I sideloaded the latest AA .apk and it works fine here. I also installed it on my Samsung T310 tablet running unofficial Lineage 14.1 and it works fine here also. It seems it might be an Android 8.1 or Lineage 15.1 issue?
Andy
Hi! You have to install MindTheGapps, no OpenGapps! I had the same problem, and yesterday I re-installed my rom and I installed MindTheGapps, and today android auto and some other bugs were absolutely solved!!
fenekatomico said:
Hi! You have to install MindTheGapps, no OpenGapps! I had the same problem, and yesterday I re-installed my rom and I installed MindTheGapps, and today android auto and some other bugs were absolutely solved!!
Click to expand...
Click to collapse
I installed OpenGApps yesterday and as usual thought I'd try Android Auto and bizarrely it opened... I went through the usual initial setup and now it works.
I thought it was an update to AA or Play Services. I have two phones - Samsung S6 and a S6 Edge, both running the same build of LineageOS 15.1, the S6 is my main phone and the S6 Edge has a cracked screen and I use it for testing new Lineage builds or apps before using them on my main phone. I installed the same OpenGApps to the S6 Edge and tried AA and it didn't work....
I then compared the versions of AA and Play Services. AA was the same, however my S6 showed Play Services version 15.0.90 and that this was an update from the Play Store. The S6 Edge showed version 14.8.49 and this was installed in the system as part of the OpenGApps install. There seems to be no way for you to update Play Services other than it doing it itself. So I copied the base.apk file from /data/com.google.android.gms (and then some random characters) off the S6 (via TWRP) and then installed it on the S6 Edge. Now Android Auto works on both.
Therefore the update to Play Services 15.0.90 from 14.8.49 seems to have fixed it - at least for me anyway.. I am not sure when the Play Services in OpenGApps will get updated to 15 though?
Broken again...
Installed the latest OpenGApps (1st March 2019) and Android Auto is broken again....
Google Play Services 15.1.78 gets installed and breaks it. Same error as before. Looks like I'll reinstall the previous OpenGApps I downloaded as this worked.
Do Google test things before they release them? Its like Cisco...
ADB100 said:
Installed the latest OpenGApps (1st March 2019) and Android Auto is broken again....
Google Play Services 15.1.78 gets installed and breaks it. Same error as before. Looks like I'll reinstall the previous OpenGApps I downloaded as this worked.
Do Google test things before they release them? Its like Cisco...
Click to expand...
Click to collapse
I just installed LineageOS 15.1 on my Z00T, hit the exact same error you uploaded, and decided to search XDA for info. Thanks for shedding light on this!
Hopefully AA gets fixed soon...
Would just flashing the older Google Play Services APK fix this issue???
Same problem with Nexus 6P with the latest LineageOS 15.1 and the latest OpenGapps (tried Aroma, Pico and Stock).
I had to switch back to the stock 8.1 to get AA working.
Just remembered posting in this thread... Looks like AA is fixed now!
AA from 3/19/2019, 4.1.590944-release
Google Play services 16.0.89
Related
[i9100G][LineageOS 13.0] "Unfortunately Pixel Launcher has stopped" - 2017 Gapps plz?
Hi, I just flashed the unofficial Lineage OS 13.0 ROM for the Samsung S2 i9100G. As from instructions, I have also installed TWRP 2.8.7 and Gapps (ARM, 6.0, stock) with the related .gapps-config file. Installation works well, but at boot I receive the "Unfortunately, Pixel Launcher has stopped" error loop which makes impossible to access the home screen, making the phone unusable. Recommendation is to try an older build of Gapps (from 2017 or so) but I cannot find one anywhere. Can anybody point me to a link for it? It might be useful also for people in different situations, that's why I'm opening a new thread.
Thanks in advance
gaglia83 said:
Hi, I just flashed the unofficial Lineage OS 13.0 ROM for the Samsung S2 i9100G. As from instructions, I have also installed TWRP 2.8.7 and Gapps (ARM, 6.0, stock) with the related .gapps-config file. Installation works well, but at boot I receive the "Unfortunately, Pixel Launcher has stopped" error loop which makes impossible to access the home screen, making the phone unusable. Recommendation is to try an older build of Gapps (from 2017 or so) but I cannot find one anywhere. Can anybody point me to a link for it? It might be useful also for people in different situations, that's why I'm opening a new thread.
Thanks in advance
Click to expand...
Click to collapse
Found, please close!
https://forum.xda-developers.com/showpost.php?p=76245917&postcount=89
Hello all,
I was searching trough the internet and the forum without luck on this issues.
Is there any explanation, what happened between 31.07 and 02.08? The dipper (Xiaomi Mi 8) release got ~ 300MB bigger.
Also I can't find a statement from the microG project, why they have removed the 20190805 release. I installed the latest firmware (9.6.27) and before the microG build was removed from their sources, I installed it. Since then my phone is only looping in the "MI" logo.
TWRP is working and I managed to install the regular LOS with GApps, until the microG team fixed the issue. Still would be interesting to know, if anyone would share the information.
Thanks,
Sputnik
Been getting this message with a custom ROM on the Nexus 6. I have installed all the supporting apps etc but no luck. Any help would be welcomed.
HD2FORNICK said:
Been getting this message with a custom ROM on the Nexus 6. I have installed all the supporting apps etc but no luck. Any help would be welcomed.
Click to expand...
Click to collapse
Seems to be bug in a OpenGapps. I had the same error when I was running OpenGapps dated to 20201205, 20201215 and 20201216. Than I tried OpenGapps dated to 20201201 and have this error any more since then.
Having same issue with LG v20 running LineageOS 17.1 and Open Google Apps Micro.
December 10, 2010 Nightly and
open_gapps-arm64-10.0-nano-20201216
I am going to try the 1201 gapps. Which version do you recommend?
sunarowicz said:
Seems to be bug in a OpenGapps. I had the same error when I was running OpenGapps dated to 20201205, 20201215 and 20201216. Than I tried OpenGapps dated to 20201201 and have this error any more since then.
Click to expand...
Click to collapse
Which version?
HD2FORNICK said:
Which version?
Click to expand...
Click to collapse
It depends only on what version do you need. All versions from the same daily build should behave the same. I tried pico and stock. Both worked fine with AA.
Hello, so about a week ago my phone (Mi 9) showed that my vendor is outdated and my banking app refuses to work now too. Coincidence? idk help
btw I am running lineageOS 17.1
Hello, I installed lineage 19 followed by an explanation on the XDA blog page.
So I managed to install TRWP 3.0.4 for android 12 then flashed rom lineage 19, start ok intalation nickGapps when the start smartphone message play store stops systematically.
So I'm going to try to install APK play store see other APKs, unless there is a module for magisk which fixes the problem as I downloaded magisk 23.4 it is running.
Thank you