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.
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!
After updating AW 2.0 to my watch, I am having trouble trying to set up google account on my watch. I have factory resetted the watch a several times, and I have cleared the cache of Android wear and Google service app.
Put the button on the watch. Go to the parameter, then go to personnalisation and enter your google account. Voil
I have the same issue. Did you manage to get a resolution?
or anyone have any ideas.
Running on Android wear 2.0 and Lenovo P2 on 7.0
Can anyone offer any advice on things to check or steps to try.
Basically when i try and add an account on either the initial set up or later, it never finds my Google Account. Just get the loading circle spinning and spinning.
I am pretty sure the problem is actually either the Android Wear app or the Lenovo ROM, as i can connect it fine with my LG G4.
Also have posts on the Lenovo forum and Android wear forum.
Mark
I am having the same problem. If you check google product forums, there are more people with various watches and phones having the same problem. I think its something on google's side. I wonder if downgrading to an older version of the wear phone app will work.
ahalol said:
After updating AW 2.0 to my watch, I am having trouble trying to set up google account on my watch. I have factory resetted the watch a several times, and I have cleared the cache of Android wear and Google service app.
Click to expand...
Click to collapse
hashish16 said:
I am having the same problem. If you check google product forums, there are more people with various watches and phones having the same problem. I think its something on google's side. I wonder if downgrading to an older version of the wear phone app will work.
Click to expand...
Click to collapse
I was having this issue until today. I uninstalled the Android Wear app, Wiped Google Play services cache and data, downloaded and installed a Wear APK from february off of apkmirror, installed it, wiped cache and data for the app, reset my watch, and it worked! Rather than sitting at the loading animation forever, I was instantly brought to the copy accounts screen.
I tried going back to an old version, but I didn't go back to Feb. Thanks.
hashish16 said:
I tried going back to an old version, but I didn't go back to Feb. Thanks.
Click to expand...
Click to collapse
I went back to the feb version, followed all the steps, still no dice. Anyone else still stuck?
Try copy the account to your watch using your cell data not wifi
ahalol said:
Try copy the account to your watch using your cell data not wifi
Click to expand...
Click to collapse
Thanks but no dice. Does this on both wifi and cell data.
solution is create a second google accout on the phone, disconnect and reset the watch, when you re-pair it to the phone both the old and new google accounts should show up, add the account you want and once the set up is complete go to accounts on the phone and delete the account you don't want.......worked for me on Sony z5 and moto 360
I just got the same problem, but found the solutions now. here's what the solutions i found from someone in the internet and it did work on mine. First, Remove your secondary or more google accounts in your mobile phone (make sure there's one left only), you can add it again later. And then you can try again to add account/ copy account from your watch.
The point is, the watch somehow can only copy account if there's only one google account on mobile phone.
Hope this help.
devilsadvocatenu said:
Thanks but no dice. Does this on both wifi and cell data.
Click to expand...
Click to collapse
I tried everything and realized it was either downgrade to 1.5 or suck it up. I said forget this and bought a Samsung Gear S3.
Anyway, Google (and I say Google because this has happened across numerous brands on AW2) messed up on this one. I would have stuck with AW but for this, but their response has been totally unacceptable.
hashish16 said:
I tried going back to an old version, but I didn't go back to Feb. Thanks.
Click to expand...
Click to collapse
This has worked for me twice now. Such a simple fix. Geez, Google... Wtf? Thank you!
Installed Apple Music and it has been working fine since launch until recently. At launch it will just crash in about a second. I've tried clearing cache and data, reinstalled, and rebooted the phone to no success.
Anyone else has/had any issues with this?
neolionhart said:
Installed Apple Music and it has been working fine since launch until recently. At launch it will just crash in about a second. I've tried clearing cache and data, reinstalled, and rebooted the phone to no success.
Anyone else has/had any issues with this?
Click to expand...
Click to collapse
It's working ok for me so might be a firmware issue on the phone
lisnalee said:
It's working ok for me so might be a firmware issue on the phone
Click to expand...
Click to collapse
Thanks for the reply. My device is CLT-L09 UK model on EE and it's been the same firmware since launch with no updates. Like I said, it was working fine up until recently.
neolionhart said:
Thanks for the reply. My device is CLT-L09 UK model on EE and it's been the same firmware since launch with no updates. Like I said, it was working fine up until recently.
Click to expand...
Click to collapse
Exact same setup for me so that's not much help for you unfortunately!
neolionhart said:
Installed Apple Music and it has been working fine since launch until recently. At launch it will just crash in about a second. I've tried clearing cache and data, reinstalled, and rebooted the phone to no success.
Anyone else has/had any issues with this?
Click to expand...
Click to collapse
I have the exact same problem. Switched from an iPhone to Huawei P20 Pro. Apple Music was fine for a week and since yesterday it keeps crashing. Installed old version APKs, tried cleaning everything, even resetting the phone to factory settings although there were no firmware updates. Literally tried everything and no luck.
And that's just one of the issues I am having. Some SMS messages won't show up in the default messaging app, notifications won't show on lockscreen. Some strange OS hiccups happening all the time. The whole office here tried to enable the notification content on the lockscreen - we know where the option is - but it just doesn't work. The SMS isssue is beyond Huawei support and carrier support. And hey, we are phone reviewers, we know stuff FFS...
Anyway, joining the wagon with Apple Music crashing and hoping for some resolution.
Me too, signed up to a free 3 months a few days ago. Working well yesterday, since this morning I can't open the app.
I've uninstalled/reinstalled, cleared cache/data and nothing. EE handset too. Although didn't use the 6 months free offer from EE. I'll use that when my 3 month one expires.
Sent from my CLT-L09 using Tapatalk
Out of interest, if your having the apple music crash, do you also have the issue with Google maps? I have both! Starting to wonder if the problems are linked and I need to go for a replacement handset.
Sent from my CLT-L09 using Tapatalk
I don't have other apps crashing, just Apple Music. Used Google Maps this morning.
Also I used AM on lots of Android devices, this is the first one where it completely stopped working.
I'm using the EE 6 MTH trial and both apple music and Google maps are still working fine for me.
It could be a simple phone setting or another app conflicting with it.
lisnalee said:
I'm using the EE 6 MTH trial and both apple music and Google maps are still working fine for me.
It could be a simple phone setting or another app conflicting with it.
Click to expand...
Click to collapse
It could, but nothing is fixed even after factory reset. It just happened in a slow day with no new installed apps or updates (I have just 8 apps anyway). Tried everything already. It's like it's an hardware issue...
eomero said:
It could, but nothing is fixed even after factory reset. It just happened in a slow day with no new installed apps or updates (I have just 8 apps anyway). Tried everything already. It's like it's an hardware issue...
Click to expand...
Click to collapse
Be worth checking with others and compare apps to see if it's that.
I installed an app similar to geekbench and it's stopped my pixel XL from switching on with the power button, i had to hard reset it to bootloader menu every time to get it going. Took some head scratching to narrow it down. Once app removed the phone was as good as new again
lisnalee said:
Be worth checking with others and compare apps to see if it's that.
I installed an app similar to geekbench and it's stopped my pixel XL from switching on with the power button, i had to hard reset it to bootloader menu every time to get it going. Took some head scratching to narrow it down. Once app removed the phone was as good as new again
Click to expand...
Click to collapse
Yes. Although on a fresh install - I just download AM and that's it - it keeps doing it. I am now thinking of some carrier+phone related issue and will try by downgrading the carrier services, or switching SIMs...
eomero said:
Yes. Although on a fresh install - I just download AM and that's it - it keeps doing it. I am now thinking of some carrier+phone related issue and will try by downgrading the carrier services, or switching SIMs...
Click to expand...
Click to collapse
Try going to settings, battery, app launch and set am to manual. Clear the cache etc and see if it helps. That's what mine is set to
It's a problem with Google play services. If you uninstall, then update again it will work again.
You're right, thank you. Just cleared data from Google play services and it's working again!
Sent from my CLT-L09 using Tapatalk
Kerchant said:
It's a problem with Google play services. If you uninstall, then update again it will work again.
Click to expand...
Click to collapse
Thanks!!! Fixed it.
Happened again yesterday. Google play services issue again but wiping data means I have to set up Google pay from scratch every time. Quite annoying.
Sent from my CLT-L09 using Tapatalk
I've started having this problem now as well, so somethings not right.
Had the same issue. Deleted Google Play Services data and cache and it worked again.
hkoornhof said:
Had the same issue. Deleted Google Play Services data and cache and it worked again.
Click to expand...
Click to collapse
Yea, that fixed it for me yesterday. It's only temporary though - started crashing again today.
Hello everyone,
first I'm sorry for my english and hope you understand everything.
I'm using Android Auto since two years with the same smartphone a galaxy s8+ (Android 9) in my opel corsa e on an Intellilink R4.0 and most of the time it worked without any problems.
But since one week it didn't starts on the Intellilink.
The last systemupdate from my galaxy was something about four weeks ago and in the mean time everything worked fine.
Each time i connect my Smartphone as usual with the car the Android Auto App shuts down and in the smartphone notification it says that Android Auto is connectet but the Intellilink didn't starts Android Auto. It only offers me to change to my Galaxy s8+ but without any result. If i try to start the Android Auto App (while the smartphone is connected to the car and i tryed it once to change to the galaxy) the "Android Auto" app shuts down immediately.
I deleted the bluetooth-connection in my smartphone and in the car and reconnected both.
I deleted the cache & AppData from "AndroidAuto", "Google Play Service" and from the "Google App".
i deleted and reinstalled the Apps.
I also tryed to use two older versions from those Apps because i thought i updated them recently before it didn't worked anymore but without any success.
I tryed three different USB-cabels...
The data-transfer to my pc works so the USB-Port from the galaxy is okay. no one in my circle of friends has a Android Auto compatible car so i can't test it there.
Somewhere i could read that it could help to enable and disable the usb-debuggin in the devolopmentmode in the galaxy but it didn't helped.
Then i disconnected the Car Battery to make a Hardrest in the Intellilink and again no success.
Confusing was that last thursday on the way home, past 20min of connection and driving it suddenly started in my car and i could use everything as usually (Voice, Maps, Spotify).
But when i arrived home and disconnected the smartphone to try it once more it didn't started.
Till Today i didn't get it to work and i dont know what problem it could be or what else i can do.
The galaxy isn't rooted i don't want to root it.
Once i had a similar problem and some App updates fixed the problem so i'll wait for an update from "Android Auto", "Google-Play-Service" and the "Google App" to try it this way before resetting the galaxy to factory settings.
But I hope that someone can help me and has another idea what i can try to do.
with best regards
xman1985
I have the same issue with my s9 on my astra. I might have a solution. Every time u connect your phone to your car and the after the notification in your phone comes saying android auto is connected go to photo gallery, search for any random video if u have in your app. Play it n hit back/return key on your phone. Yes its a bit of a struggle but mine one works every time i do this . Looks like a bug
samuhang said:
I have the same issue with my s9 on my astra. I might have a solution. Every time u connect your phone to your car and the after the notification in your phone comes saying android auto is connected go to photo gallery, search for any random video if u have in your app. Play it n hit back/return key on your phone. Yes its a bit of a struggle but mine one works every time i do this . Looks like a bug
Click to expand...
Click to collapse
Thanks,
I'm not sure if its just a coincidence but i tried it and it realy works that way.
xman1985 said:
Thanks,
I'm not sure if its just a coincidence but i tried it and it realy works that way.
Click to expand...
Click to collapse
Hi ive found out today that downgrading your aa to
4.6.593334-release (arm64-v8a works without going to gallary app n playing a video. But first just clear data of your aa before unintalling it than intall the above mentioned ver from apkmirror . Com. Have a nice day
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...