I have a Nexus 5X running Android Oreo and after installing the latest November 5 security patch update, my car doesn't detect Android Auto on my phone at all. I get a message stating no Android Auto compatible phone is plugged in. It used to work without any issues whatsoever earlier.
I've tried my friend's phone which is a Pixel 2 and it works flawlessly with my car/cable. Even the Pixel 2 has Android Oreo and the November security patch update.
I've tried the following fixes:
1. Clearing data/cache of Android Auto app.
2. Uninstalling and reinstalling the Android Auto app.
3. Checking permissions of the app.
If there anything else I can try before I resort to Factory Data reset?
??? where you get November update? apkmirror only show oct update. can share?
Sent from my HUAWEI MT7-TL10 using Tapatalk
ahhl said:
??? where you get November update? apkmirror only show oct update. can share?
Sent from my HUAWEI MT7-TL10 using Tapatalk
Click to expand...
Click to collapse
I don't know exactly which update it is. The security patch level is shown as November 5. I got it OTA.
It's not an update to the actual Android Auto app that is causing the problem. It appears that the problem is with the November Android security update. There are a ton of threads on the "official" Android Auto support forum that are, of course, getting no responses from anyone inside Google.
Go in and activate developer mode on the 5x. Then turn on usb debugging. Fixed my wife's 5x after the update.
Fixed mine in my 2018 Honda Civic Hatch. Was working fine then just wouldn't connect at all. Tried all above fixes, new cables, reset head unit and phone, nothing worked. Last night I remembered I am on the Google Maps beta, so I deleted that apps updates. I also found in my head units menu, a setting to restore Android Auto to default. Now it is working without any issues. I don't know which thing fixed it, but maybe someone else can try one fix at a time...
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!
1) Turn off the watch and fully remove the SIM
2) Unpair the watch from the Wear OS app/factory reset
3) Clear storage/Uninstall the Wear OS app from your phone
4) Reinstall the Wear OS app
5) set the watch back up
6) Check for system updates
This worked for me today after reading a similar experience on Reddit. You will have to update to February, then May, and finally August security patches to catch up.
It may be pertinent to leave the sim card out until all of the updates are complete, using Wi-Fi during the process
Hello,
Talk you about the "H update" ?
Thanks.
Has anyone been able to get Wireless Android Auto working? I just got a used Kenwood DDX9705S and have only got my phone to connect briefly before disconnecting and then not working at all. I've cleared the data in the app multiple times, updated the firmware on the unit to the latest, installed the newest version of Android Auto, and I've tried different kernels all with no luck. When I connect via USB Android Auto works perfectly, I've gone through every setting I can think of but haven't been able to get it to work. I also haven't seen any mention of it being an issue with the February Update. I plan on trying out my friends XL 2 and my co-workers XL 4 when I can but in the mean time I wanted to look for other potential answers or if it is even the phones fault at all.
As the title says, even though this phone is not even two years old I am already finding apps that are no longer supported.
As of writing the apps that are currently showing up as no longer compatablie with this device are:
Netflix - preinstalled app asks for an update but never does, says no longer supported.
Final Fantasy XIV Compainion app - Says there was an update but says no longer supported.
Is anyone else able to confirm this happening on there device to, or is there somethign with my phone (I have even did a factory reset to wipe all data)
XQ-AT51
Build Number 58.1.A.5.530
Android 11
Security update 1 December 2021
Google Play System Update 1 January 2022
I find this really werid considering my brother has an Nokia 9 Pureview which both these apps still work on. I am guessing over the coming months more apps will start to not be supported making me start to regret buying this phone.
Netflix works great for me (current Netflix version per Play Store; and Android 12 on my phone).
JamesMiami said:
Netflix works great for me (current Netflix version per Play Store; and Android 12 on my phone).
Click to expand...
Click to collapse
Weird I wonder why google play is telling me the app is no longe supported on my device.
My phone was a XQ-AT52 which I flasehd to a XQ-AT51, but I can't imagine that causing any issues. Hell the only issue it does give me is that Xperia companion app will give me a error if I try to repair the phone.
Normally, the built-in versions are updated when there's a newer version in the Play store. It does on my phone. Maybe the rights management doesn't work anymore because the device is flashed or rooted?
Sorry for bumping this old thread, this may not be the right place to comment but I have the exact same issue on Xiaomi Redmi Note 10 Pro with the same two apps. I previously installed PixelOS on it, but decided to go back to European stock rom, and that's when I noticed the issue.
Edit: Fixed. I just had to lock the bootloader again.
no. just uninstall stock netflix then install from apkmirror if google still say incompatible. sony use spesial netfilx app that in deed no longer supported
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.