Need help!
I just factory reset my Nexus 6, root it and found in About phone - System update - "System update downloaded and... (restart now)".
I am definitely not want to update from 6.0.1 to 7.1.1, so I am going to Google play service and clean all data. And found that System update start downloading immediately again with only options "Pause downloading", so I pause it for now. I am also found this topic https://forum.xda-developers.com/nexus-6/help/how-to-stop-update-downloaded-t3157232 , but it about 5.1.1 and the answer is wrong, because there is no "Automatic System Updates toggle" in 6.0.1 Nexus 6 (this option came in 7.0). I am also installed Disable services app, and disable SystemUpdateService in Google Play Services and Google Services Framework, but it not work.
I am also try another method - Rename /system/etc/security/otacerts.zip to otacerts_bak.zip , but its also didnt work for me
So, how to prevent it, cos I am afraid to reboot my phone?
It's been forever long since MM. I think things were different then, but some ideas;
Long press the notification and a settings gear/cog should be available. From Settings select "Turn off notifications update"
Go to settings -> apps -> Google Play services (not store - you may need to "show system apps") then uncheck the notification box.
Settings -> about device -> software update -> check for updates
There might be an toggle in developer options (tap on build number 7 times to enable developer options)
I try most of those ideas in start topic. Notification not a problem, I am already blocked it - problem with downloading.
And, as I said, Developer options didnt have it in 6.0, only from 7.0
Hmm, maybe I found solution for my question:
Not enough to kill SystemUpdateService, but when I killed SystemUpdateService Activity receiver, System Update options just disappear from menu "About".
Can somebody confirm it?
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
Deleted member 10657845 said:
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
Click to expand...
Click to collapse
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.
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.
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.
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:
No installed apps work with this USB accessory.
Learn more at www.android.com/auto/.
Any searching and reading shows many having this issue with 16 and 17 but not earlier versions.
McAnik said:
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:
No installed apps work with this USB accessory.
Learn more at www.android.com/auto/.
Any searching and reading shows many having this issue with 16 and 17 but not earlier versions.
Click to expand...
Click to collapse
solve the same issue using an opengapps build back from december 2020, i guess is some bug from recent builds
d_g_m_2000 said:
solve the same issue using an opengapps build back from december 2020, i guess is some bug from recent builds
Click to expand...
Click to collapse
Yes, I can confirm that. The latest GApps that works to me with AA on LOS 17.1 is the 20201201 one. All the newest versions I tried so far have the "No installed apps work with this USB accessory." issue.
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.
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?
JohnE2 said:
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?
Click to expand...
Click to collapse
Go to microg thread for more info.. I think AA is not supported by microg.
sunarowicz said:
Yes, I can confirm that. The latest GApps that works to me with AA on LOS 17.1 is the 20201201 one. All the newest versions I tried so far have the "No installed apps work with this USB accessory." issue.
Click to expand...
Click to collapse
Do you have a link please:? Here https://sourceforge.net/projects/opengapps/files/arm64/ the versions jump from 2020-07-05 to 2020-12-11. Thanks
jo mateix said:
Do you have a link please:? Here https://sourceforge.net/projects/opengapps/files/arm64/ the versions jump from 2020-07-05 to 2020-12-11. Thanks
Click to expand...
Click to collapse
Ah, nevermind; 2020-07-05 worked
McAnik said:
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:
No installed apps work with this USB accessory.
Learn more at www.android.com/auto/.
Any searching and reading shows many having this issue with 16 and 17 but not earlier versions.
Click to expand...
Click to collapse
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.
G A S T said:
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.
Click to expand...
Click to collapse
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.
McAnik said:
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.
Click to expand...
Click to collapse
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.
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!
SteveMKII said:
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!
Click to expand...
Click to collapse
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.
Thanks for sharing, we'll definitely include this (or something similar) in our next builds.
SteveMKII said:
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!
Click to expand...
Click to collapse
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!!!
SteveMKII said:
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!
Click to expand...
Click to collapse
How can I uninstall the Android Auto from user apps and system apps?
Hello guy i managed to get gms semi working, I dont know what to do next
Tried everything i dont have any ideas anymore hope somebody can use this and make it working
Playstore gets data but u cant download it crashes
Play services is version 7.3.29
Services framework is version 4.4.4(newer doesnt work)
Account manager version 7.1
Youtube works with account but sometimes crashes
Perhaps if you share the steps someone can use that info and make it happen.
Okay
1. Installed lzplay
2. Installed googlefier
3.installed only microg gms from googlefier and logged in with my account
4.I disabled microg gms trough adb so that account stays loged in while uninstalling(there is tutorial how to disable apps)
5. Installed Services framework version 4.4.4
6. Installed google account manager version 7.1
7. Installed google play services version 7.3.29
8. Instaled Playstore
9. If playstore wont open just go airplaine mode and delete data of playstore and services framework
Playstore opens and gets all data u can search everything but when u click download it crashes if u want working youtube u need to update google play services to this one i put here but when u install this apk i get error that this device is not play certified
Edit: uploaded all apks that i used,except play services 7.3.29 you will have to download it from apkmirror(i doesnt want to upload)
Please specify: China only device with Harmony, not with EMUI.
On Chinese models, GMS should be fully functional, as far as I know.
Well, as i've searched on youtube it's complicated to sideload GMS on HarmonyOS for chinese devices, no matter if it's Mate 40 Pro or P50 Pro, it's complicated...
robi101012981 said:
Please specify: China only device with Harmony, not with EMUI.
Click to expand...
Click to collapse
But in the video says EMUI 12 and NOH-NX9, the Chinese model it's not the same as far as I know.
dizeL69 said:
Hello guy i managed to get gms semi working, I dont know what to do next
Tried everything i dont have any ideas anymore hope somebody can use this and make it working
Playstore gets data but u cant download it crashes
Play services is version 7.3.29
Services framework is version 4.4.4(newer doesnt work)
Account manager version 7.1
Youtube works with account but sometimes crashes
Click to expand...
Click to collapse
it is a big step ahead, hope someone will find out the complete solution. how about downgrade to EMUI 11 and try the steps one more time?
Hi!
I'm using Mate 40 Pro (C432 - HW-EU => NOH-N29).
It's rather easy to downgrade using the HiSuite from EMUI 12 down to 11.
In my case I'm setting up the Hi Suite Proxy (3.3) downloaded from it's official page:
Releases · ProfessorJTJ/HISuite-Proxy
Modifying HiSuite and manipulating it's connection data to install Roms before they officially get released. - ProfessorJTJ/HISuite-Proxy
github.com
Just install HiSuite, Hi Suite Proxy, patch the HiSuite, start up the phone and connect.
I additionally turned on the Programmer Mode in the phone.
Once connected via HiSuite, in the UPDATE section, except the UPGRADE (if available) it allows to install another variant -> in my case it's allowing to DOWNGRADE (Roll-back) down to EUMI 11 (in my case: 11.0.0.253).
IMPORTANT - it's deleting/erasing all the data, so before ANY actions it's wise to backup the files on the phone.
After downgrading I was trying many methods:
- LZPlay / G-Play,
- Googlefier,
- MicroG (several variants, including the one where it allows to use different 'ID's' -> i.e. Nexus X5 (which worked partially in opposite to other sollutions).
- LightHouse -> variant available on AppStore (Huwaei) isn't working, but the one downloaded from this forum did allow me to create the Google account.
Unfortunately any mixes/fixes of GPS, GFS, Account Managers, Google Play Store - are recognizing and forgeting the accounts, while attempting to remove the MicroG or LightHouse.
Perhaps you can help by explaining how to freeze the MicroG (by ADB?) and I'll be able to move-on.
My goals are:
- make the Android Auto to run;
- make the GApps -> Google Assistant, Chrome (with sync), Google Calendar to work;