I have been using the Carlinkit in my '16 Pilot (w Honda Hack) for two years. It's a bit buggy, but works.
Yesterday, when I plugged every thing in, my phone immediately rebooted. If I left it connected, it would continue to reboot.
This happens on my Pixel 3xl and a Samsung A10E, so I'm doubting it's the phone.
Any suggestions?
I am running Google ver 12.1.9.23.arm64, which was updated on 1/22 and I believe the problems started after that. I am also on AA 5.9.6.4634, which was updated on 12/2, and Google Play Services ver 20.47.14, which was updated on 1/5.
EDIT: SOLVED --> Uninstall updates to Chrome
I got the same issues, and rollback of AA to older version doesn't help
Disable chrome on phone
Related
I have been using android auto for the past 3-4 weeks flawlessly. However in the last day when I plug my phone in I now get the red page stating this device cannot work with android auto on the phone. I have tried everything from reinstalling the android auto app/clearing cache/data and the same for google play services to factory resetting the phone. Has anyone else encountered this? does anyone have any ideas?
Phone: Nexus 6, stock, never rooted, never unlocked
Headunit: Pioneer AVIC8100NEX
Edit: I've been messing around with this, I am starting to suspect the 7.3.29 update to google play services is the culprit. downgrading to 7.0.99 seems to make it work up until the google play service updates itself automatically. I've tried connecting the phone in airplane mode to prevent this but android auto doesn't launch at all when the phone is in airplane mode.
Send a bug report.
ma2885 said:
I have been using android auto for the past 3-4 weeks flawlessly. However in the last day when I plug my phone in I now get the red page stating this device cannot work with android auto on the phone. I have tried everything from reinstalling the android auto app/clearing cache/data and the same for google play services to factory resetting the phone. Has anyone else encountered this? does anyone have any ideas?
Phone: Nexus 6, stock, never rooted, never unlocked
Headunit: Pioneer AVIC8100NEX
Edit: I've been messing around with this, I am starting to suspect the 7.3.29 update to google play services is the culprit. downgrading to 7.0.99 seems to make it work up until the google play service updates itself automatically. I've tried connecting the phone in airplane mode to prevent this but android auto doesn't launch at all when the phone is in airplane mode.
Click to expand...
Click to collapse
Better send a bug report to Google and the Android Auto support team. After I took that update I had some problems with other devices, not sure where but there is a list of devices and applications that have switches to allow/not allow them and all of them were switched to off. Had to turn many of them back on for me to get any information from them. Don't know about the AA application. I have not used it much because there is no Pandora Radio support yet and I have not had to go on any long trips so all I've needed was the voice navigation from Google maps on my phone. Hoping Pandora gets added soon, then it will be all I ever use.
ma2885 said:
Edit: I've been messing around with this, I am starting to suspect the 7.3.29 update to google play services is the culprit. downgrading to 7.0.99 seems to make it work up until the google play service updates itself automatically.
Click to expand...
Click to collapse
7.3.29 is installed on my Nexus6, with the same HU, and I have no problems. Have you updated the avic8100NEX's firmware to 1.0.3?
Yea, I updated to 1.03 the first day I got it installed. There seems to be some people with a similar issue, and others dont experience it at all.
I started a post over at androidcentral http://forums.androidcentral.com/an...y-states-device-cannot-work-android-auto.html
Two others chimed in with the same problem. Started about the same time google play servivce update rolled out. But if that is the problem then I am at a loss why only a few of us are having this problem.
Yeah, I think the update caused issues on some devices. I tested with 6 different phones the other day. HTC One M8 w/ CM12 seems OK, as does MotoG stock or CM12, and I think GS2 w/ 5.1 ROM. GS3 was among the problem devices.
I see a permissions problem in the logcat; Google's own Android Auto app can't get the permissions it needs.
I'm not positive this is all directly related though.
What build of Android?
ma2885 said:
Yea, I updated to 1.03 the first day I got it installed. There seems to be some people with a similar issue, and others dont experience it at all.
I started a post over at androidcentral http://forums.androidcentral.com/an...y-states-device-cannot-work-android-auto.html
Two others chimed in with the same problem. Started about the same time google play servivce update rolled out. But if that is the problem then I am at a loss why only a few of us are having this problem.
Click to expand...
Click to collapse
Could be a combination of things, i.e. build version I,E,M,D,etc.
vvveith said:
Could be a combination of things, i.e. build version I,E,M,D,etc.
Click to expand...
Click to collapse
You nailed the nail on the head...
I think I've figured it out. It definitely is the google play services update 7.3.29 on a N6 running Android 5.0.1. I can out my SIM and block google play through my home firewalls then downgrade to 7.0.99 and it works flawlessly. I then manually updated to Android 5.1.0 with google play services 7.3.29 and it also works flawlessly. So my recommendation is to manually apply the 5.1 update. I just tried to go back to 5.0.1 and once 7.3.29 services come down it no longer works. And went back to 5.1 and it works again. Definitely an issue with 5.0.1 and google play services 7.3.29 combination.
All of this testing was done with factory images, the only non factory application installed was android auto. all partitions on the device were formatted prior to applying system images.
ma2885 said:
You nailed the nail on the head...
I think I've figured it out. It definitely is the google play services update 7.3.29 on a N6 running Android 5.0.1. I can out my SIM and block google play through my home firewalls then downgrade to 7.0.99 and it works flawlessly. I then manually updated to Android 5.1.0 with google play services 7.3.29 and it also works flawlessly. So my recommendation is to manually apply the 5.1 update. I just tried to go back to 5.0.1 and once 7.3.29 services come down it no longer works. And went back to 5.1 and it works again. Definitely an issue with 5.0.1 and google play services 7.3.29 combination.
All of this testing was done with factory images, the only non factory application installed was android auto. all partitions on the device were formatted prior to applying system images.
Click to expand...
Click to collapse
This also worked for me. I was so confused as to why my Nexus 6 all of a sudden didn't work with Android Auto... I was running 5.0.1 with the updated Google Play Services 7.3.29 (auto updated). Switched to a ROM with 5.1 and it works again. Thanks!
Recently purchased a 2016 Honda Accord, and wanted to give AA a shot. My phone was initially running android 5.0.1., and while I was able to establish a connection with my vehicle, I would get disconnected frequently.
I decided to do a system reset on my phone, and the OS automatically updated itself to 5.1.1. After performing the update, android auto can't establish a connection at all! Instead every time i plug in my phone after starting my car, Android Auto will open and then immediately force close, followed by an error message stating, "Unfortunately, Google Play Services has stopped".
Anyone have this happen to them/know a fix? Thanks in advance!
What phone ?
Make sure you have a GOOD cable.
If you can change USB modes in Settings or from Notifications, try that.
mikereidis said:
What phone ?
Make sure you have a GOOD cable.
If you can change USB modes in Settings or from Notifications, try that.
Click to expand...
Click to collapse
oneplus one with a CM12.1 snapshot
i'm using a 22 AWG cable that i purchased from my local Fry's. Do you have any suggestions for cables? The only research I did into micro-usb cables was in regards to charging speed, so I don't know much about connection/stability or other stuff like that.
I'm having the same damn issue! Have tried the following:
1) signing out and back in to google account
2) clearing cache/data in both google play services/google system framwwork
3) uninstall/reinstall android auto
4) factory reset
I'm on a Note 4 running CM13.
On the 2016 Civic, you can reboot the head unit by holding down the Audio power button until the reboot dialog appears.
This fixes a LOT of AA issues.
colbyrainey said:
I'm having the same damn issue! Have tried the following:
1) signing out and back in to google account
2) clearing cache/data in both google play services/google system framwwork
3) uninstall/reinstall android auto
4) factory reset
I'm on a Note 4 running CM13.
Click to expand...
Click to collapse
did you ever figure this out? I get the same error anytime play services updates itself and it's annoying. I've disabled layers and xposed, cleared play services data, restored play services data, uninstalled and reinstalled play services, logged in and out of account.
Hello All,
I am a 'Non Developer' user and its my first post on forum, so please pardon my ignorance whatsoever.
I am using an ROG P3 Tencent edition (I003DD) running Android 10 Build QKQ1.200419.002.WW_Phone-17.0823.2008.78. Over last few weeks, I am facing several issues which I will try to explain below.
1. Bluetooth: When connecting a bluetooth headset, the device connects successfully, but gets no sound. Disconnecting and reconnecting, even removing and re-adding the device doesn't help. Strangely, on connecting a device, there is a few seconds lag/ freeze before I can play a video on youtube, no sound still. Restarting the device solves the issue for the moment, but the issue remains when I reconnect after a few hours.
2. Settings keeps stopping: I am using Whatsapp Twin Apps. When trying to link a Whatsapp web device on my secondary whatsapp App, I am unable to go past 'Link a device' icon and after a few taps, get 'Settings keeps stopping' error.
I haven't faced this exact error on other apps, but have had few other apps crashing too recently in a random fashion.
3. Fingerprint: It takes several attempts to unlock the screen using fingerprint. That's despite using clean fingers screen.
I have already tried resetting/ wipe the device through Settings but that didn't fix the problem. There are no Updates available in System Update.
Questions:
1. Has anyone else faced similar issues ? If so, were you able to fix it?
2. WIll retting the phone through Bios make any difference than resetting through setting (which I already did).
3. Since the phone is originally a Chinese version and it came pre-installed with Global OS, will Bios reset put it back into Chinese?
4. Should I update to 17.0823.2102.143 manually?
I have a Note 20 Ultra which has been working great since last September on my Hyundai I20N with the same cable and no automatic updates.
Last week it worked great one morning and later on that day it started throwing an error saying the phone is not recognised.
I have updated the car's head unit software, tries several versions of AA, cleared cache and data, switched cables, used a Samsung cable, uninstall and reinstalled, cleared Play Services cache, all short of a phone reset.
Meanwhile, my wife's S20 FE works fine on my car, and mine doesn't work on any car.
Ideas?
Try to delete cache and data of Google Play Services app.
SOFO888 said:
Try to delete cache and data of Google Play Services app.
Click to expand...
Click to collapse
Already tried it. Also removed all updates to Play Services. Still no go...
I'm seriously baffled by this one.
Also tried connecting my Galaxy Tab S6 LTE to my car and it worked flawlessly. Same AA version, same updates, same options on AA... and still my Note won't connect. Reproduce me sideways....
Android auto was working for me less than 24 hours ago. I factory reset my phone and boom my android auto no longer works. Did the whole uninstalling and cache thing and nothing. I am able to get to the welcome to android auto and then when I click it on my head unit, it crashes
jollijm1207 said:
Android auto was working for me less than 24 hours ago. I factory reset my phone and boom my android auto no longer works. Did the whole uninstalling and cache thing and nothing. I am able to get to the welcome to android auto and then when I click it on my head unit, it crashes
Click to expand...
Click to collapse
Exactly the same as with my Note 20, although I did not do a factory reset. As a matter os fact, between AA working and no longer working, I did nothing on my phone.
But my Tab S6 has all the same software, versions and updates, and it works just fine...
I'm losing my crap, here
Luis33Boxer said:
Exactly the same as with my Note 20, although I did not do a factory reset. As a matter os fact, between AA working and no longer working, I did nothing on my phone.
But my Tab S6 has all the same software, versions and updates, and it works just fine...
I'm losing my crap, here
Click to expand...
Click to collapse
Android Auto stopped working on my car screen after the Android software update on 12th August 2022 - Android Auto Community
jollijm1207 said:
Android Auto stopped working on my car screen after the Android software update on 12th August 2022 - Android Auto Community
Click to expand...
Click to collapse
I posted my issue on the Google android auto help forum and they sent me to another post similar to our issue. Look like the issue started about a week ago
jollijm1207 said:
I posted my issue on the Google android auto help forum and they sent me to another post similar to our issue. Look like the issue started about a week ago
Click to expand...
Click to collapse
I saw some stuff about that.
What's weird, though, is that in my case it was working in the morning and stopped on the afternoon of the same day, and I didn't update anything in the meantime. Weird.
Following that previous tip regarding the Google Android Auto help forum, someone suggested something that I tried and actually worked: download and install AA version 8.0.623314 and that's it, it seems to solve the issues.
I have an Alpine iLX-W650 and a OnePlus 7 Pro. Android Auto has been working perfectly for well over 4 years now, even through OS upgrades (currently on Android 12).
Suddenly, about a week ago I got the "Device is not supported." message. A reboot of the phone while in the car fixed it.
Then it happened again the next day, nothing I do resolves it including a new or different cable. There was an Android update this morning and I also saw a new version of Android Auto. I did both of these hoping one would fix the issue. Nothing. Multiple reboots later, including telling Android Auto to forget me unit, still nothing.
I had my wife plug in her phone and the head unit works perfectly with Android Auto, so something with my phone changed or a setting is corrupted. I'm not sure how to get things working again.
As mentioned, I tried:
another cable (several now)
"Forgetting all cars" in the settings
Forgetting connected cars in the Head Unit.
Factory resetting the Head Unit.
Double-checking the Head Unit is the latest firmware (it is).
Deleting the AA app and clearing data and cache for it and then updating to the latest.
Deleting the AA app and clearing data and cache for it and then trying to connect to let it pull down AA.
As noted above, my wife's phone works no problem with my head unit and since thing my daughter tried her phone which works too. Clearly, something on my phone got corrupted or something to cause it to not work anymore.
Rule #1 - if a OS is fast, stable and fulfilling its mission let it be! Upgrades and updates can and do break devices.
Once you sort that mess out disable auto updates.
For anyone that might stumble on this, I considered that maybe my phone's data port was at fault and causing issues. Otherwise, my OnePlus 7 Pro works great and still charges. Not really ready to let it go.
Since I've always wanted AA to be wireless, I ordered the AAwireless device and it works flawlessly. In fact, it is more responsive than when my phone was cabled. Wish I had done this years ago.
stevemajor said:
For anyone that might stumble on this, I considered that maybe my phone's data port was at fault and causing issues. Otherwise, my OnePlus 7 Pro works great and still charges. Not really ready to let it go.
Since I've always wanted AA to be wireless, I ordered the AAwireless device and it works flawlessly. In fact, it is more responsive than when my phone was cabled. Wish I had done this years ago.
Click to expand...
Click to collapse
A port pcb failure can cause data and phone service loss at least on Samsung's.
If it happens after a firmware upgrades/update it's not a hardware failure...