I used to be able to connect the USB cable to my phone on Android O and it'd launch the AA in my head unit, but now nothing happens. I unplug/plug several times to no avail. Is this a common issue or isolated to me?
I have made sure that all of my devices are up to date and even made sure to test on an older phone. It works on an older device just fine.
I'm having the same problem
Me too, will try a different cable but thinking there must be a problem.
Just tried different cable, still not working. Was working prior to updating to android 9. Car is only just over a month old. Using original pixel XL. Missing sat Nov Google maps already.
Same here.
I am also having this issue. My Pioneer head unit is not recognizing my phone for Android Auto. Although I did fix that buzzing noise that people were discussing. I turned off the charging now sound in sounds. At least that is gone. I use Android Auto every day and I've spent a lot of $ to have it. I hope this gets resolved quickly. I'm becoming disenchanted.
I also can't connect to my Pioneer head unit (MVH-2300NEX) after Android 9 P (Pie) update. Everything was fine using Oreo.
I replaced USB cable.
I re-paired phone to car.
I re-installed AA on my phone.
I tried different auto-launch settings in AA.
All to no avail.
Sounds like we're all in the same boat until Google gets this fixed.It's painful to live without AA on head unit since I ditched all devices for mounting phone to dash.
I also heard the alarm (not a buzz) which I was able to turn off in the Sounds menu under "Advanced", "Charging sounds".
Google Play Services - 12.8.74 (100400-204998136)
Android Auto - 3.4.582534
Android 9 Build PPR1.180610.009
Sorry to cross post. Android Auto crashes every 5 to 10 minutes on Android Pie.
Error message: The phone is not responding
Car / head unit make & model: 2016 Hyundai Tucson
Phone make & model: Google Pixel
Android OS version: 9
Android Auto app version: 3.4.582534-release
Google Play services version: 12.8.74 (100400-204998136)
We did all the same things. I have the AVH-2330NEX. Just to make sure it wasn't my head unit, I put my wife's Note 8 on it with Oreo on it. It popped right up. Hopefully they are fixing this deal. We spent a lot of $ on this to have AA, which I use daily. Good luck!
Hey everyone,
Thanks for the feedback. Could you please fill out the information below?
Car / head unit make & model: if you use Android Auto on your car display
Android Auto app version:
Google Play services version:
@Noah Swint: the issue appears to be related to this thread here.
For known Android Pie issues that you’re experiencing, please visit:
@Don - Android Auto Team:
Is there a way to capture a bug report if the phone never connects? It's seems like nothing is happening.
Google Play Services - 12.8.74 (100400-204998136)Android Auto - 3.4.582534Android 9 Build PPR1.180610.009
Pioneer MVH-2300NEX
Yes, you still can. After pressing on the Android Auto icon, if it doesn’t launch or it crashes, then you can capture the bug report. It should contain some information for our engineers.
For those who are having the black screen issue, it seems that on AA 3.5 it works fine (you can download it from APK Mirror while it is not on the Play Store for everyone).
After upgrading my Pixel 2 to Android Pie AA doesn't even get recognized in my head unit.
If I look at the charging sign on the phone, it goes from battery to charging many times as it seems it is trying to understand what is connected to it (the same way it happens with the Type C to 3,5mm dongle)
Same exact problem here. Phone won't connect at plug in and start AA. Charges intermittently. All worked perfectly yesterday. Please fix.
I upgraded to 3.5 and the issue still persists. I was able to finally get a connection on my Pioneer by upgrading the Head unit firmware but the blackouts and drops keep happening
You have to be kidding us for asking to give a bug report. There are thousands of complaints on the same issue after Android 8.0 update that people cannot,connect their phone to the car the USB connection option just keeps popping back and you want a bug report from us??
Car companies and consumers should file a class action lawsuit against Android and Google only they will they fix this issue.
Hello,
App won't load after downloading onto my Galaxy S9. States "Something went wrong, Google Play services doesn't seem to be working right now"
App won't load after downloading onto my Galaxy S9. States "Something went wrong, Google Play services doesn't seem to be working right now"
Car / head unit make & model: 2018 Chevy Malibu
Android Auto app version:3.3.583024
Google Play services version:11.1.15-all[0][PR]206859054
Ever since the Android 9 Pie update was applied to my Pixel 2 XL two days ago, the screen on my Kia Forte 2017 Hatchback goes black intermittently, to then reappear on the same app before going black, either Waze, Google Maps, Google Play Music, Spotify, etc.; This didn't happen at all while having Android 8.1 Oreo installed.
Google Play Services: 12.8.74 (100400-204998136)Android Auto: 3.5.583024-releaseAndroid 9 Build: PPR1.180610.009
Please fix this issue as it's distracting while driving.
Hey Paul, I installed the Pioneer July firmware V8.35. My Pioneer AVH-2330NEX is now working now with android auto. Just a tip during the install either turn phone off or at least turn off bluetooth. I went to Pioneer looked for my radio scrolled all the way bottum you'll find the Download. Also the instructions are pretty easy,
Good luck!
Scott
Hi @Don,
It has nothing to do with the other thread.
They were able to connect Android Auto to their head unit, it the screen was getting black from times to times.
In our case, the smartphone doesn't even recognize the head unit and goes charging-battery-charging-battery-charging forever and ever =\
Having the same issue connecting to a pioneer headunit with a Pixel 2 (not xl). Connection was rock solid with Android 8.1, no longer working once upgraded to 9.0. Have tried a few different cables. The first which was working with 8.1 now just alternates the phone between charging and nothing. Have tried a newer one and the phone says it's charging, but it doesn't connect to the headunit (ie android auto doesn't launch, can't find the headunit as a device under AA).
I am running the most recent firmware for the pioneer, have tried resetting it to factory settings, uninstalling and reinstalling the AA versions from play store.
I'm not sure how to capture a log, sorry.
Car / head unit make & model: Headunit = Pioneer AVH-Z5150BT (FW 8.07)
Android Auto app version: 3.5.583024
Google Play services version : 12.8.74 (100400-204998136)
A fix would be ace!
thx
Same problem with my pixel XL 2 and pioneer mvh 2300. The phone shows connected thend disconnected over and over and over. Worked this morning before the update and not anything afterwards. Bluetooth is ok.
Thanks Scott Dabson, never thought about the Pioneer firmware update. Works great now!! Much appreciated.
Same problem here!
Pixel 2 XL Android 9.0 Pie (stable build)
Volkswagen Polo 2018, Android Auto updated to last version
Good call @Scott Dabson!
I updated the firmware on my Pioneer head unit and now my Pixel 2 XL running Android 9 P (Pie) launches AA on the head unit when I connect via USB.
Thanks for the suggestion bro' !
Paul
I'm having the same problem
Same problem with my Mitsubishi Outlander PHEV.
Here is what worked for me.
Enable Developer Mode. (Settings - System - About Phone - Tap the Build Number at least 7 times)
After developer mode is enabled, change the default USB configuration to USB terhering. (System - Advanced - Developer options - Default USB configuration - USB tethering)
After that reconnect to Android Auto infotainment unit.
@Eric Piech
The options I have when going into this are:
Charging
MTP (Media Transfer Protocol)
PTP (Picture Transfer Protocol)
RNDIS (USB Ethernet)
Audio Source
MIDI
I don't have a USB Tethering option.
I just did that with a Pixel 2 XL in a 2018 Honda Civic and it worked like like a charm. Something in the security settings with Android Pie updated is blocking the USB tethering with the head unit in the cars. Thank you Eric
Did it this morning but I still cannot skip songs on Spotify (ONLY WHEN USING AA) with my steering controller .......
Same issue. Ford Escape 2017. Worked fine before Pie update. Now, cable will charge but head unit says that "USB unit is not responding." Have tried all fixes discussed in this thread and nothing has worked. This is infuriating as a Pixel user.
So I managed to get it working this morning, but it is not a permanent fix.
The primary issue is that since updating to pie, my pixel 2 no longer connects to my pioneer head unit to use Android auto. Phone alternates between charging and not charging. Can launch AA on phone, but it is not transmitted to headunit.
The primary issue is that since updating to pie, my pixel 2 no longer connects to my pioneer head unit to use Android auto. Phone alternates between charging and not charging. Can launch AA on phone, but it is not transmitted to headunit.
Phone : Pixel 2 (not xl)
Car / head unit make & model: Headunit = Pioneer AVH-Z5150BT (FW 8.07)
Android Auto app version: 3.5.583024
Google Play services version : 12.8.74 (100400-204998136)
Go to settings and search for 'usb preferences'.
The should be 2 parts to this
-USB controlled by
and
-use USB for
Keep this screen up and plug USB in phone.
The options under 'use USB for' should at some point change from greyed out to active (but this only happens for about 0.25 seconds). Just keep tapping the usb tethering option when this happens.
If you time it right, you can select the tethering option and the phone should be recognised by the headunit and AA should auto launch.
If you don't time it correctly, unplug USB from phone for 10 seconds and try again.
If it starts working, great! But the moment you unplug your phone/switch car off, you'll lose the connection.
Hopefully someone much smarter than me can figure out an easy, permanent fix for this...
FMN
I'm having the same issue with a Pioneer AVH-Z7100DAB head unit. I've tried the USB tethering fix but that doesn't work. Any word on a proper fix?
I had issues with my Pioneer AVH-2330 NEX and my Pixel 2xl. What fixed my issue was actually a July Pioneer update. Go to the Pioneer website find your radio, scroll all the way to the bottom and you will see if there is an update. Good luck!
Tried changing USB tethering setting, but that' didn't fix my issue. My Google Pixel 2 XL, when plugged into my car's Pioneer AVH-2400NEX, wouldn't launch AA and would cycle between charging and not charging. I went to Pioneer website and downloaded firmware update, which fixed the problem. AA works flawlessly now. My mistake was not putting the parking brake on when installing firmware update, so make sure to do that.
Unfortunately there's no firmware update available for the Pioneer AVH-Z7100DAB yet so I'm relying on Google fixing this at the moment
I updated my Android auto app on my Moto Z2 yesterday and now the app will not not connect to my Kenwood head unit in my truck anymore. It was working perfect right before I updated and now it won't connect at all.
have a same problem, i use galaxy s9+ and AA cant lauch " something whent wrong" everything is on the lastest version. pls helpp me
kenwood ddx9704s with latest firmware
Everything was working great before I updated to Pie...now it connects and disconnects every 10 seconds - maps, phone calls etc. So frustrating!!!!
Pixel 2 XL updated to Pie
Everything was working great before I updated to Pie...now it connects and disconnects every 10 seconds - maps, phone calls etc. So frustrating!!!!
I have the exact same issue. Android Auto won't start period. I'll add that the "charging sound" chime is accompanied by a flashing battery charging icon on the phone itself. Also wondering if ANYONE has been able to get a Google brand USB A to C cable to use when connecting a phone to Android Auto. My has been suspiciously on order since June 11. Google stopped updating staus on this ored a month ago. I think there is a USB bug in the Pixel 2 XL.
I'm having the same problem on a Pixel 2XL with Android auto in my car.
Car / head unit make & model: Acura TLX 2018
Android Auto app version: 3.5.583024-release
Google Play services version: 12.8.74 (100400-204998136)
Google Maps version: 9.85.0 (#985004244)
Come on man. You have everyone s rewed. You know the problem. YOU FIX IT GOOGLE GENIUSES!!!!!!
Had the same issue. Updated my Pixel from 8.x.x to 9.x and Android Auto immediately stopped working on my Pioneer MVH-2300nex. Still receiving power over USB C. Will update Pioneer firmware asap.
No further updates on this from Google? I've contacted Pioneer but they have no firmware update for my head unit so at present I have no Android auto on it at all, not even the black screen some people mentioned
I was able to fix my Android Auto issue. When I updated to Android Pie on my Pioneer AVH-2440NEX, I found I was unable to get Android Auto to start. Instead my Pixel 2 XL just made the recharging battery chime over and over.
I went to the Pioneer site and updated the firmware for my Pioneer head unit from version 8.06 to version 8.09. Now everything works. One tip. Make sure you unzip and take the upgrade .avh file out of the folder it comes in which has the same name BEFORE you try to upgrade your head unit...
Pixel 2 XL, Build PPR1.180610.009
Pioneer AVH-2440NEX, version 8.09
Android Auto version 3.5.583024-release
Don, please call me. I'd like to discuss this with you buddy.
Same problem here after pie upgrade
@Yurim:
My Pixel 2 XL has *always* had disconnects after around 30 minutes of being plugged into Android Auto. Since updating to Android 9 (Pie), the disconnect frequency has increased to about every 2 minutes. So, Android Auto has become unusable.
Error message: None
Car / head unit make & model: Chevy Cruze 2017
Phone make & model: Android Pixel 2 XL
Android OS version: 9
Android Auto app version: 3.5.583024-release
Google Play services version: 12.8.74 (100400-204998136)
Android Auto connection after 9.0 upgrade to Pioneer 2330 - FIXED!
As a few other users have noted, upgrading the firmware on the Pioneer head unit solves the problem. I updated to the latest available firmware, V8.35 and Android Auto immediately connects when plugged in. The Pioneer firmware I was running before the upgrade was V8.26. Upgrading to Pie broke the connectivity. I changed nothing else, simply upgrading the firmware solved the problem. Didn't change the cable on the Pioneer or any settings on the phone.
Looking at the Pioneer this same version (V8.35) should work with the AVH-1300NEX, 1330NEX, 2300NEX and 2330NEX.
Phone: Pixel2, Android 9.0
As a few other users have noted, upgrading the firmware on the Pioneer head unit solves the problem. I updated to the latest available firmware, V8.35 and Android Auto immediately connects when plugged in. The Pioneer firmware I was running before the upgrade was V8.26. Upgrading to Pie broke the connectivity. I changed nothing else, simply upgrading the firmware solved the problem. Didn't change the cable on the Pioneer or any settings on the phone.
Looking at the Pioneer this same version (V8.35) should work with the AVH-1300NEX, 1330NEX, 2300NEX and 2330NEX.
Phone: Pixel2, Android 9.0
Android Auto V3.5.583024
Now why hasn't there been any response from Google telling us the fix for the problem instead of making us figure it out for ourselves? Amazing :( I didn't see anything about it on the Pioneer website either. We spend hundreds of $$$ on phones and radios but neither vendor cares whether or not they work once you own them!
Hope this helps someone else from buying new cables, playing with phone settings, etc.
Jim
Now why hasn't there been any response from Google telling us the fix for the problem instead of making us figure it out for ourselves? Amazing :( I didn't see anything about it on the Pioneer website either. We spend hundreds of $$$ on phones and radios but neither vendor cares whether or not they work once you own them!
Hope this helps someone else from buying new cables, playing with phone settings, etc.
Jim
Unfortunately there is no update on the Pioneer site for my AVH-Z7100DAB.
Neither Google or Pioneer have responded with anything useful to me yet.
2017 Silverado and google Pixel 2. Same thing, worked yesterday, updated to android 9.0, won't work today. Real bummer.
same prob connecting to 2018 Volvo XC90. Has anyone been able to connect to a Volvo after updating to Android P? Suspect Volvo will need to update their system.
@FMN,
I'm having the exact same issue are you are with the exact same Pioneer Head unit: Pioneer AVH-Z5150BT (Firmware 8.07)
Google Pixel 2 (non-XL) Android Auto was working fine with Android version 8.1, ever since the upgrade to Android P, connecting the usb-C cable causes the phone to constantly switch between charging and non-charging every second or so. Android Auto never detects the USB connection.
I've tried switching to other various USB-C cables before i found this forum. Changing the cables doesn't make any difference
I can confirm that plugging in another Google Pixel running 8.1 still works just fine. Other older phones (samsung, motorola, apple) also all seem to be doing AndroidAuto/Carplay just fine.
Android Auto App version: 3.5.583024
Car Headunit: Pioneer AVH-Z5150BT (Firmware 8.07)
It looks like Pioneer might be releasing firmware updates for other headunits that are having issues with the charging non-charging issue. I've reached out to them but I would like to see if google is going to address this in any way.
I really don't want to have to downgrade my phone back to Android 8.1.
I'm having the same problem. Android Auto won't launch on my Pioneer AVH-4200NEX car stereo. I've been using it every day for the last year just fine, and it just stopped working today. My Google Play store says AA was updated yesterday. The phone charges when I plug in the USB cable, but it doesn't launch AA anymore. If I launch it manually from my phone, it comes up on the phone screen but doesn't cast to the car stereo screen like it used to.
I'm having similar issues with wireless android auto and connecting. I love beta testing a retail product.
I just updated to pie the other day, and I also am now unable to get Android Auto to pull up when I plug my phone into my Pioneer head unit. For the poster who suggested going into USB settings and turning tethering on, that worked for me but only temporarily as every time I plug my phone in I'd have to sit there and wait for it to let me change the settings. I updated the firmware, but as I have a 4100NEX the only firmware update available was iPhone specific and didn't solve my problem.
There's a firmware update for the AVH-Z7000DAB. I'm going to give that one a go. I can't see the difference between AVH-Z7000DAB and AVH-Z7100DAB.
I've tried the firmware update to v8.35 and my google pixel 2 is still not connecting to my Pioneer AVH-Z7000DAB :(
@don
Car / head unit make & model: Pioneer avh-z7000dab - Firmware version 8.35
Android Auto app version: 3.5.583024-release
Google Play services version: 12.8.74
Phone: Google Pixel 2 - Android version 9 patch level 5 August 2018
When I plug my phone into my stereo it shows as charging, but does not connect to the AA. It worked prior to my upgrade to Android 9.
The stereo does connect successfully to my wife's Google Pixel 1 running Android version 9, so the stereo and cable are ok.
On Wednesday, 8 August 2018 22:41:35 UTC+1, Don - Android Auto Team wrote:
Hey everyone,
Thanks for the feedback. Could you please fill out the information below?
Car / head unit make & model: if you use Android Auto on your car display
Android Auto app version:
Google Play services version:
@Noah Swint: the issue appears to be related to this thread here.For known Android Pie issues that you’re experiencing, please visit:
On Wednesday, 8 August 2018 22:41:35 UTC+1, Don - Android Auto Team wrote:
Hey everyone,
Thanks for the feedback. Could you please fill out the information below?
Car / head unit make & model: if you use Android Auto on your car display
Android Auto app version:
Google Play services version:
@Noah Swint: the issue appears to be related to this thread here.For known Android Pie issues that you’re experiencing, please visit:
Same exact problem. Funny thing is it worked okay for a little while after the Android P update. I was getting the black screen reboots, then the next AA version fixed that for a few days. Then, out of nowhere, with no updates done on my part, my P2XL just would not be recognized. Two other phones (Pixel 2 (non XL) and Motorola Nexus 6) work fine.
I tried all 3 phones in two different cars (listed below), and the P2XL is not recognized, while the other two phones work fine. Please get this fixed and don't forget about us! Part of why I buy Pixel phones is because I figure they should be the best supported phones from Google, and that hasn't really been my experience as of late. The cars are:
2016 Kia Optima
2018 Hyundai Tuscon
Android Auto App Version: 3.5.583024 (had the same problem on the immediate prior version as well)
Google Play Services Version: 12.8.74 (100400-204998136)
Car / head unit make & model: brand new Pioneer AVH-2330NEX
Android Auto app version: 3.5.583024
Google Play services version: 11.4.16
When I plug in, it connects and disconnects over and over (I can see the charge signal go on and off while also hearing the sound made when connected/disconnected. It seems to be a fairly steady pulse). Android auto is never able to launch on the head unit, but I am able to use it from my phone to control the head unit via Bluetooth. Sadly, I purchased this unit ONLY because I wanted to put my phone away and use GPS on the head units screen.
I spent a good hour pulling my hair out over this before looking in the forums and finding out that I am NOT a clueless moron (well...not because of this at least. Up for debate elsewhere), and it shouldn't be this difficult.
I feel just like you. I'm relieved to see I'm not alone with this frustration, but am also incredibly annoyed with Google right now.
Still no way for making my MVH-2300NEX work with Android Auto.
Audio head unit make & model: MVH-2300NEX (firmware v8.02, can't get it to recognize the fat32 USB stick with firmware update to v8.21, might need to pull it out to directly access the USB port vs using my extension cable...)
Android Auto app version: 3.5.583024-release
Google Play services version: 12.8.74 ((100400-204998136)
Same problem w/Pixel 2 XL after P update.
I noticed it also wasn't showing the notification to enable USB file transfer when connected to laptop or car.
My Pixel 1 running P has no issues plugged into my laptop or car. It displays the USB notification like it's supposed to and launches AA.
I thought I fixed the issue by blowing into the USB C port in the bottom of the Pixel 2 XL (like an old NES game cartridge) but it turns out no.
I have the AVH-2330 and did the Pioneer July update. My Pixel 2 XL works perfectly now with Android Auto. I hope there is an update for your unit. Go the the pioneer website find your unit scroll all the way to the bottom to see the latest firmwear for your unit. follow the instructions. It's pretty easy. Good Luck!!
Hi Don,
I have the same issues with my Pixel XL 2. Headunit is Pioneer AVH-Z5150BT Firmware Update 8.07, My Android Auto App Version is 3.5.583024, Google Play Services Version 11.4.16. it works on older Pixel Devices even with the Pie Update, with the same cable I've used prior to upgrading to Pie.
Aldrich
I am having the same issue: https://buganizer.corp.google.com/issues/113637927 with a Pioneer Aviv F77DAB, Firmware update to 1.11 did not help.
Mine has started working now. I think it might have been the firmware update that fixed it. It didn't seem to work when I first tested it, but maybe I had a loose connection: -
Car / head unit make & model: Pioneer avh-z7000dab - Firmware version 8.35
Android Auto app version: 3.5.583024-release
Google Play services version: 12.8.74
Phone: Google Pixel 2 - Android version 9 patch level 5 August 2018
After the Android Pie update my phone is not responding to being plugged into my 2018 Ford F-150 running Sync 3. my Phone will connect, and it runs on Sync 3, but Android no longer runs on the head unit with my phone plugged in.
2018 Ford F-150 with Sync 3 software version 2.3, build 17109_PRODUCT
Android Auto Version 3.5.583024-release
Google Play version 11.4.16-all [0] [PR] 209796717
Hope it helps
Car / head unit make & model: Seat Ibiza 2018, car display
Android Auto app version: 3.5.583024
Google Play services version: 12.8.80(100400-209656296)
Phone: Google Pixel 2 XL with Android Pie august patch (PPR1.180610.009
I use AA, but without a reason, it disappear from my car screen, and my phone starts the phone AA mode...
Also experiencing the same issues as everyone above. Phone seemed to connect for awhile after the update (usually had to unplug and re-plug it in a few times but it would eventually connect) but after this past weekend it won't recognize the phone at all.
Vehicle: 2017 Honda CRV w/ Android Auto & Car Play
Android Auto Version: 3.5.583024-release
Google Play Services: 12.8.74 (100400-204998136)
Android Version 9 - Aug 5th Security Patch
Troubleshoot steps:
Unplugged and re-plugged multiple times
Rebooted phone
Unpaired and re-paired phone
Uninstalled Android Auto and Re-installed
Tried multiple cables
Rebooted head unit multiple times
Was concerned it could be my head unit so I fired up my old Nexus 6P, ran all the updates and updated to all of the latest app versions and it connects to my vehicle immediately without issue and fires up Android Auto on my head unit like it should. Disconnected it from the usb cord multiple times, shut the vehicle off a few times and re-started and the 6P connects immediately without issue each time (Of course the Nexus 6P does not have the Android Pie update so this seems to be the culprit either Pie or Pixel Specific).
Android Auto is core functionality, it seems like users here have had this issue for awhile. Not sure why it is taking so long to fix, we bought a premium device for a reason. Why do I get more functionality out of a device that is two generations old than my next gen premium google device?
I'm having the same problem but it's on a standard 2018 Jeep Wrangler, no aftermarket head unit or anything. It worked 2 days ago even after Android 9 upgrade then plugged it in today and the phone wouldn't recognize at all. Same cable, same car, same phone. Bluetooth would recognize and connect to the car, charging worked fine, and AA would open on the phone but wouldn't transfer to the car at all. The only change was that I placed the phone in Battery Saver mode and the battery died the day before so I needed to recharge and restart the phone. Even after several restarts and verifying all Google updates I've had no luck. Here are my changes so far:
- Developer mode unlocked
- USB debugging on
- Default USB to USB Tethering
AA App Version:3.5.583024-release
Google Play Services version: 12.8.74 (100400-204998136)
Please help! Any recommendations would be appreciated.
Unfortunately I don't think there's much we can do other than wait for Google to (hopefully) fix this in a timely manner. With each day that passes by without a fix or further comment from a Google rep here here, I'm having my doubts that will happen.
As another poster recently said, this is a core feature and this problem should be addressed accordingly, yet that doesn't appear to be the case. So much for choosing the Pixel over other phones because of the expectation that Google would provide quality support for it.
This experience, along with that ugly notch on the P3XL, has me thinking this will be my last pixel phone for a while. Might as well save some money and go with the upcoming One Plus, since I don't seem to be getting the only real differentiator (quality support directly from Google) that I thought I'd get by staying with pixel devices.
My AA with my Pixel 2 XL will connect most of the time but sometimes it doesn't. Seems real finicky with the cord. I have a nice Belkin one (high data rate). It will charge my phone but not launch AA. Then other times it's just fine. Anyone have more luck with an actual Google cord?
I don't think the cord is an issue, I tried using multiple cables with my Pixel XL 2 that are approved by Benson (https://bensonapproved.com/) who is a Google engineer that tests USB C cords for comparability and none of them work. However, the same cords all work with my Nexus 6P (which is also a USB C phone).
Clearly this is a Pixel and/or Android Pie issue. I also had the same experience as you, AA would connect most of the time and I would have to unplug and replug a few times with the cord but it would always trigger. Unfortunately last week it just stopped working completely and will no longer connect. I wouldn't be surprised if sometime down the line you run into the same issue unless they get this resolved soon.
That's good to know. Thanks. Almost bought a Google cord.
It's a mystery. Last night I drove somewhere and was marveling at AA. It had read my calendar and offered directions to my event and got me there early. Then on the way home it wouldn't connect. Ahh, the frustrations of technology.
It's a mystery. Last night I drove somewhere and was marveling at AA. It had read my calendar and offered directions to my event and got me there early. Then on the way home it wouldn't connect. Ahh, the frustrations of technology.
What's so frustrating is this was working relatively fine since the phone came out, Google screwed it up with the release of Pie, and now they're not prioritizing fixing this.
I gave up playing around with beta versions recently because I currently don't have the time for troubleshooting, bugs, and having features that I paid for not work. This is unacceptable for a flagship phone that cost this much money.
I've had a Pixel 2 XL since it's release and had awful bluetooth issues with my old car since day one (couldn't talk on the phone on bluetooth but could listen to music and podcasts). Just got a new car with AA and was hoping the wire would solve all of my problems. Apparently not. There's so much I love about the phone, but my wife has an iPhone 6S that's never had any problem with either (bluetooth or Apple Play). So frustrating.
I have a 2018 VW Alltrack Sportswagon and cannot connect my Pixel 2XL to the stock stereo unit. Whenever I connect the UBS cord to the Android Auto App, through the stero unit, no USB device registers. I have tried going through developer mode, and changed the USB Debugging setting, but to no success. Does anyone have a solution out there!?
Hey John. It seems like there's no solution. We're at the mercy of Google, and they're not exactly showing that this is a priority for them. It's wrong.
Has anyone tried using AA again after the latest patch?
The most recent patch I have is as of Aug 5, certainly not very recent. Did an update come out for you more recently?
I got a security patch today. I guess I should probably just walk my lazy legs out to the truck to try it.
I had the ota update yesterday for the September security patch. Still not working.
Fyi,
I have also raised an issue on the issue tracker. Still no response after 2 weeks.
**Has anyone tried downgrading to 8.1 Oreo to verify this isn't a USB hardware issue?**
Because:
1. I read a report of a Pixel 2 XL on Android 9 working normally with Android Auto on their car (Mazda; same setup that is failing for me).
2. I read a report of a Pixel 2 XL running Android 8.1 that was experiencing this same USB issue.
3. This USB issue appears to be greater than just Android Auto. I have been seeing some inconsistent behavior when connecting to a laptop USB for file transfer. Keep plugging in and unplugging USB to replicate. Haven't tested if wired USB headphones are affected.
Problem is not only with the PIxel or Android Auto, it is with any phone that has the Android 8.0 or above software, especially with the OTA upgrade.
This is for any phone, any car.
Google could care less. It is time for a class action law suit against them.
Please lets all file a class action suit against Android and Google.
Even car manufcaturers seem to be just giving up and offering Apple Play as standard software, want nothing to do with Android anymore.
This is incorrect, I have a Nexus 6P updated to Android 8.1 that works without issue in my 2017 Honda CRV. (tested 2 days ago, removed all apps from device aside from stock google apps, everything updated to latest version, 8.1 Aug. Security Patch)
This doesn't change the fact that it doesn't work for Pixel's and Android Pie which I agree is unacceptable, but the above is definitely misleading that AA will not work with version 8+. Not trying to detract from your frustrations (also very frustrated) but don't want to mislead someone reading this post.
One point to clarity is that there are a lot of advanced setting in Pie that could effect things. Autolaunch (connecting to AA when your bluetooth connects to your car) and "Display Over Other Apps" are two obvious ones. Anything else I'm missing (I'm new to AA)? It's been working most of the time with my new Subaru Crosstrek and Pixel 2 XL but other times it does not. So I don't think we can make a blanket statement that it doesn't work with at all for anyone.
More evidence of a hardware (or firmware flash) issue:
From https://support.google.com/androidauto/forum/AAAA6SY52nIs-gUJ-NaewI/?hl=en
"8/11/18
Honesto V - Pixel 2XL, 9.0 Pie, Kenwood 9902S
I had similar problems on a 2XL with 8.0 and 8.1. It was intermittent and AA would launch but soon crash and repeat frequently. Soon my phone failed to make any data connection by cable and AA stopped launching altogether. Do you have access to other Android phones and other cables? Some were able to solve their similar problem by using a new cable rated with higher speed for data transfer. I don't have a LG6. I did a lot of testing to get to the root cause (including a factory reset). My problem was hardware and specifically data was not passing thru the cable (I could charge) to AA with a failed Type C port on the phone or the data path from the system board to C port and data was no longer going to AA. Can you connect and transfer data files to/from your computer? I could not. I swapped out my phone with a Nexus 6P, a Pixel, and a Pixel 2XL and they all worked with all four of my cables with AA and with my computers."
"8/20/18
Honesto V - Pixel 2XL, 9.0 Pie, Kenwood 9902S
I believe the root cause of the problem being experienced by so many in AA is the firmware update with Oreo to the system board or the USB port. I first experienced AA failing to launch after the Oreo OTA. I tested connecting to my Win10 PC and that failed to be a recognized device and could not connect. I could charge at both head unit and PC but others in other Android forums report charging has failed as well. I also no longer had connection with USB Type C headphone adapter and headphone function. I discussed the test and all solution tries results, which included a factory reset, with Google Pixel 2XL service and they agreed to send a replacement phone. It came with 8.0 and all AA/PC/headphone launch/connect testing was successful. With each OTA update (8.1, Security monthly, 9.0) I repeated the tests. All successful. This means the board and/or the C port hardware is compatible with current OTA code or Android's system board and port manufacturers also updated the firmware code to be able to work with current/legacy hardware. For me and others, the root cause was not AA. Good luck and test to isolate for your root cause."
From https://support.google.com/androidauto/forum/AAAA6SY52nIs-gUJ-NaewI/?hl=en
"8/11/18
Honesto V - Pixel 2XL, 9.0 Pie, Kenwood 9902S
I had similar problems on a 2XL with 8.0 and 8.1. It was intermittent and AA would launch but soon crash and repeat frequently. Soon my phone failed to make any data connection by cable and AA stopped launching altogether. Do you have access to other Android phones and other cables? Some were able to solve their similar problem by using a new cable rated with higher speed for data transfer. I don't have a LG6. I did a lot of testing to get to the root cause (including a factory reset). My problem was hardware and specifically data was not passing thru the cable (I could charge) to AA with a failed Type C port on the phone or the data path from the system board to C port and data was no longer going to AA. Can you connect and transfer data files to/from your computer? I could not. I swapped out my phone with a Nexus 6P, a Pixel, and a Pixel 2XL and they all worked with all four of my cables with AA and with my computers."
"8/20/18
Honesto V - Pixel 2XL, 9.0 Pie, Kenwood 9902S
I believe the root cause of the problem being experienced by so many in AA is the firmware update with Oreo to the system board or the USB port. I first experienced AA failing to launch after the Oreo OTA. I tested connecting to my Win10 PC and that failed to be a recognized device and could not connect. I could charge at both head unit and PC but others in other Android forums report charging has failed as well. I also no longer had connection with USB Type C headphone adapter and headphone function. I discussed the test and all solution tries results, which included a factory reset, with Google Pixel 2XL service and they agreed to send a replacement phone. It came with 8.0 and all AA/PC/headphone launch/connect testing was successful. With each OTA update (8.1, Security monthly, 9.0) I repeated the tests. All successful. This means the board and/or the C port hardware is compatible with current OTA code or Android's system board and port manufacturers also updated the firmware code to be able to work with current/legacy hardware. For me and others, the root cause was not AA. Good luck and test to isolate for your root cause."
And one other thing... I do need a high data cable to use my AA (a non high data Belkin doesn't work). I use this Belkin one.
Posting here because another thread was marked duplicate.
How do I collect a bug log on my pixel2xl?
How soon after the issue occurs do I have to collect it?
Do I have to increase the verbosity of the log first?
I'm trying to use android auto on a Ford Focus RS with the premium Sony head unit running sync 3, v3.0, not sure of exact version beyond that.
My pixel2xl is fully up to date on pie.
Thanks.
My issue is just that Android Auto does not start when I plug it into my car and is not recognized if I manually start Android Auto. My Nexus 7 (Unsupported device) works fine and so does my wife's iPhone so I know the car is fine. I have tried multiple cables and still nothing. Worked @ 1 week ago and for no reason just stopped.
Car / head unit make & model: Ford Escape with Sync 3
Android Auto app version: 3.5.583024
Google Play services version: 13.2.78 (100400-210410490)
Desperately need to get this working again. Use it daily for my work.
I am more than willing to try beta's or test builds if possible to get this working.
Thanks,
Jason
2017 Ford Focus RS / Sony Premium Stereo (model # unknown) running Sync3, 3.0
Android Auto version = 3.5.583024-release
Google Play Services = 12.8.74(100400-204998136)
AA fails to launch when plugged in
I recommend we all take our phones to the Google authorized repair shop UBreakIFix for a FREE diagnosis of the USB-C port.
Jason, Install this on your Nexus 7: https://labs.xda-developers.com/store/app/uk.co.borconi.emil.aagateway
Then you can leave the Nexus 7 in the car and use a Wifi connection. How to is here: https://forum.xda-developers.com/general/paid-software/android-3-0-proxy-gateway-android-auto-t3813163 reported to be working for many users.
Not ideal but it will get you going for sure.
@Don,
Everyone here has had nearly the same experience, bug reports have been provided at length. Many troubleshooting steps have been recommended and tried without any resolution. I don't understand why you and the Android Auto team refuse to communicate to everyone aside from asking for more bug reports of which you already have. Based on the response from the Pixel Support associates it already sounds like you know whats wrong, so tell us.
You marked the other thread as a duplicate but you didn't respond to anything in my lengthy post (created a separate topic).
TWO Pixel support specialists acknowledged the issue when I spoke to them yesterday, they said the Android Auto Team of which you are a part of I assume is aware of the issue and is working on a fix expected in the next update of Android Auto. Your Pixel support specialists are telling me and I assume others who inquire about it this.
So if you are aware of the issue and are working on it then why can't you simply communicate to us who have been waiting for AA to resume working on our devices for a long time now your progress with the issue, what steps are left before the issue is resolved, what the ETA is, and why is it taking so long?
We bough the flagship Google phone. Again this isn't a Samsung, LG, HTC etc... this is a Google branded Pixel Phone touted as the flagship model. You have a core piece of functionality broke, for many users. Functionality that many depend on on a daily basis and have been without for a month now.
Everyone here has had nearly the same experience, bug reports have been provided at length. Many troubleshooting steps have been recommended and tried without any resolution. I don't understand why you and the Android Auto team refuse to communicate to everyone aside from asking for more bug reports of which you already have. Based on the response from the Pixel Support associates it already sounds like you know whats wrong, so tell us.
Class action suit!!!!!
I am using a Sony Sync 3 Version 3.0 system in a 2018 Ford Explorer, Android Auto App version 3.5.583024-release, Google Play services 11.4.16-all [0] [PR] 209796717 and Android Auto works fine on my phone but just stopped working on my head unit. I plug it in and it just charges but acts as if there is no signal to the head unit saying I am plugged in. On bluetooth I can use Iheart radio and other apps that are bluetooth compatible but Android Auto will not engage on the head unit. I tried master reset, deleted and installed app, verified all apps are up to date but it still wont work.
Everyone please contact the law firm of Mafliaccio & Rathod LLP 202-470-3520 www.classlawdc.com to start class action suit!!!
Head-Unit: Pioneer AVH-2330NEX
Android Auto App Version: not installed
Google Play Services Version: 12.8.74
I've upgraded the HE firmware to 8.35 but that did not help.
My symptom is that when I plug into the HU, the phone tries to launch App Radio. The HU does not recognize the phone nor does it try to launch the installation of AA. This happens when AA is installed from the Play Store as well.
This was a perfectly functioning setup since January 2018 that stopped working after the last OS update. There were no other changes....same phone, cables, etc.
This is a Samsung Galaxy S9 on Verizon.
Yup - join it now! ------> Mafliaccio & Rathod LLP 202-470-3520 www.classlawdc.com to start class action suit!!!
Hi All,
I have the same issue. Even tried to install old version of android auto. No luck at all. I think its issue with App or Pie security.
Car / head unit make & model: Maruri Suzuki S-cross May 2018 .
Android Auto app version: v 3.5.583024
Google Play services version: v 12.8.74 (100400-204998136)
phone: google pixel 2
os: 9
Please do the needful at the earliest.
Wow. Look at this. And it appears that AA just crawled back into their hole. Come on AA. The emails are flowing into the law firm. AA team needs to step it up!!! ... Everyone, please. I urge you to contact that law firm. It's the only way we're going to be able to get some satisfaction
Are these issues happening with Apple as well or just Android?
Any updates on this issue? Not able to use AA for more than a month now.
@Roel,
Can you try the method from this thread:
I like most of the others in this thread was having the same issue and using the method a fellow user found was able to get it running for me as a workaround. Worth a shot, it looks like another Pixel user didn't have the same luck though so not sure why that is.
I just tried this with no success.....I had very high hopes too. No luck for me.
The September security update for Pie fixed all my Android Auto and Bluetooth issues.
I was having the same problem and was able to convince Verizon I was having a charging issue. A replacement phone fixed the problem immediately but I haven't done the update to Pie or any security updates. I'll install those today and hope for the same result, otherwise, for me at least, it seems like data rate issues we're the problem. Hoping for the best!
@Daniel
Will be curious to see what happens after the updates. I know my device worked for awhile after the Pie update but just all of a sudden stopped, I will say that prior to it stopping I would have to frequently unplug and re-plug in the device or restart the device multiple times to get it to register but I could always get it to eventually recognize it. Eventually it just quit.
I wonder if we are seeing both Hardware and Software issues... Honestly both are concerning but the hardware more so. I know if you were an early adopter like myself your warranty is going to be up soon. So we could potentially have a scenario where we are still left in the dark with this and our warranties expire then it comes out it's hardware... what do we do then?
Noticed that my headphone dongle doesn't work after update either. If the phone doesn't connect to the head phone adapter how can it connect to my car. What ever this update did it killed my headphones and my AA
@Alan,
I don't know for sure if AA was the culprit of this but it seemed to always happen after I left my vehicle (always had AA connected). I even argued with Pixel support and had a brand new replacement device (After they sent me a new dongle that didn't fix it) sent to me. It didn't resolve the issue so I just gave up trying to fix it and basically resigned to restarting my phone every time I wanted to use the headphone dongle.
I wonder if these are related Pixel issues.
The dongle never really worked for me. I noticed that if I used AA and then took my phone and plugged in the dongle to use my headphones they would not work. However, if I restarted my device after having AA connected the dongle would then work.
I don't know for sure if AA was the culprit of this but it seemed to always happen after I left my vehicle (always had AA connected). I even argued with Pixel support and had a brand new replacement device (After they sent me a new dongle that didn't fix it) sent to me. It didn't resolve the issue so I just gave up trying to fix it and basically resigned to restarting my phone every time I wanted to use the headphone dongle.
I tried the unknown device workaround in AA, no fix here.
@Andrew
Did you enable USB Debugging in the general Developer Mode settings?
Which device? Pixel XL 2?
Pixel2xl. No, I hadn't enabled debugging mode.i just did now, and will try again in about an hour and report back.
Tried debugging mode as well, same issue.
@Andrew,
Can you confirm that your versions are the same as mine?
PPR2.180905.005 (Sept. 5th Security patch)
My AA version is 3.5.583024-release
My Google Play Services is 12.8.74 (100400-204998136)
And I am using an Anker Powerline + cable.
Just curious, this entire issue is just odd. Why does one fix work for some devices but not others, why does this work for my Pixel XL 2 but not yours...
I received an OTA Android 9 update on my Pixel 2 last week and now it works with my 2018 CR-V. The update must have fixed my connection issue, at least with Pixel 2. I hasn't worked with my car since Pie upgrade.
Using the Google cable from Google store. My versions are noted above
@David,
I have a 2017 CRV though so that is a difference as I assume our head unit's aren't likely slightly different at least in firmware, unfortunately Honda does not offer firmware updates for Models prior to 2018 and I don't believe the CRV 2018 or 2019 will receive downloadable firmware updates (currently only available for the Accord, Oddessy, Pilot). I should clarify firmware updates are available but it is a royal pain to get them, you can't download them yourself and you need to take your vehicle into a dealer and depending on the dealer they will either be nice and update it for you or force you to give them a compelling reason for the update.
Can you compare your versions with my devices:
PPR2.180905.005 (Sept. 5th Security patch)My AA version is 3.5.583024-releaseMy Google Play Services is 12.8.74 (100400-204998136)
I have a Pixel XL 2 and the OTA security update from last week did nothing to fix my issues. It's just odd that the update works for one device but not the other when they are the same device... especially since we both have the same Vehicle make/model.
I have a 2017 CRV though so that is a difference as I assume our head unit's aren't likely slightly different at least in firmware, unfortunately Honda does not offer firmware updates for Models prior to 2018 and I don't believe the CRV 2018 or 2019 will receive downloadable firmware updates (currently only available for the Accord, Oddessy, Pilot). I should clarify firmware updates are available but it is a royal pain to get them, you can't download them yourself and you need to take your vehicle into a dealer and depending on the dealer they will either be nice and update it for you or force you to give them a compelling reason for the update.
I'll echo your concern about the USB port and dongles. My Pixel 2 XL purchased in June often needs to be restarted to use the dongle. Also, this is just an unverified conspiracy. I ordered 2 new dongles and 2 new USB A to C cables from Google on June 11. Still waiting for them to be delivered. Google has no response to why it's taking so long. Just gives me the option to cancel the order. I ordered everything because prior to the Pie upgrade, AA was working only intermittently for me, so to trouble shoot, I thought it would be best to use a Google cable, not the Amazon cable i use to connect my pixel to my Pioneer head unit. (Note: Google does not provide a USB A to C for use with the phone to head unit connection for AA -but offers it on the Google store). Maybe a supply chain issue, but three months for a cable sounds like they know they have some issues with the port. I've since gone to a Bluetooth headset and found that updating my Pioneer head unit with the latest PIONEER update fixed OS 9 Pie issues that made my phone (as posted here a few weeks ago). All that said I feel for folks who don;t have the time or gumption to unscrew the Google update. This is a consumer device, not custom code. I'd be happy to be proven wrong as I'm totally invested in the Google Smart home with over 20 Google branded devices or compatible devices including my washer and dryer, wifi, safety and smart speakers, sprinkler and soon garage door.
Ah sorry missed those, so they are the same.
I have no idea, it doesn't really make sense and the AA team isn't really helping either.
I have no idea, it doesn't really make sense and the AA team isn't really helping either.
If I get a chance this evening I will try to mess around with my settings some to see if I can figure out if there is something else that may have made it work for me and not you. But I don't see why we both had the same issue on the same device but the workaround works for one and not the other...
tried the work around with AA developer mode no fix for my Pixel 2xl
Exact same versions of all of those as yours James. The only difference is I have Pixel 2 and not XL, if that makes a difference. I would assume it's the same head unit in 2017 CR-V as the 2018, maybe you can call Honda to find out? It has to be the update because I got it at night and the next morning I was able to do everything in my car, back to normal. As soon as I got the Pie upgrade, phone stopped working in my car and Android Auto. When I received Android 9 update, it went back to normal. I know how frustrating it is, hope this helps.
It's just odd that the update fixed issues for your device but broke so many others. It's so frustrating that they can't figure this out and we have heard nothing from them on what their progress is with this issue.
The workaround presented in the other thread unfortunately stopped working for me this afternoon. Not sure why but everyone else that tried it today wasn't able to get it to work so I am not surprised that when I got into my vehicle this afternoon it also wasn't working even after working this morning. It's odd because no apps updated today for me, the last app updates were last evening.
I am going to attempt to get a replacement device from support tomorrow, I rely on AA too much to be without it.
James, so far everything has worked perfectly. I completed all the normal app installations and upgrades after setting up the phone. The only AA settings I changed were as follows:
-prevent auto launch
-enable bluetooth recognition
-disable wireless projection
After 10 successful startups of AA when plugged into the car I completed the Pie update and Sept. 5 security update. After 10 more pairings, I've no further problems.
I'm not sure if this means my issue was hardware only or if so other issue has been cleared. I'm hoping this problem holds off and that it was purely hardware related but I certainly hope this helps other people as well!
The whole thing is extremely odd. Is this affecting ALL Pixel 2/Pixel 2 XL phones with Android 9 or just random ones? I know it affected mine and now it's fine after security update. I didn't have to change any settings or do any workarounds like other people have posted. It just went back to working. I assume every Pixel 2 phone is the same, so they should all react the same way to an update. Same with Pixel 2 XL, as I know Pixel 2 is manufactured by HTC and XL is manufactured by LG. Just glancing through the forum it seems that majority of the complaints are for Pixel 2 XL, however, mine is a Pixel 2 and some other posts are Pixel 2. I too can't figure out why nothing has been said from Google on this issue. Again, this can't be affecting every single Pixel phone or I would think is would be making headlines. One option I guess would be to go to verizon (or another place that sells Pixels) and see if another phone has the same issue, or try to get a replacement straight from Google as you mentioned. One reason we all chose to purchase Pixel 2's because of being pure Android and having the latest OS. Google is making it difficult to continue to make the same decision in the future. Good luck and I hope you find a solution soon!
Is it only pixel2 phones ? I know that a few weeks ago, android auto voice commands stopped working to play all media, and it was not a pixel exclusive thing, for a lot of people. Google fixed that without any explanation or patch.
This is the second time in a month this shit is broken for me :(
Not only pixel2. I’m on a Galaxy S9 with the same issue.
@Daniel @David,
I echo your confusion as to why it seems to be happening to some devices and not others. Why the update fixed everything for some users and not others and why the workaround works for some users and not others.
I would think this is something the AA team could help us with... but they seem to have disappeared again. I know @Don is still responding to new threads as you can tell based on the comments but all that is typically given is a copy pasted troubleshooting messages and then direct links to other forum threads where users have found workarounds.
I have yet to see an AA team member or Don actually address what is going on with this issue other than asking us to continue to post our make/model and android versions or to try a new USB cable.
Anyway, for a quick update. Last evening I was actually able to get the workaround to work for me again, I sat in my vehicle and tested a few things out and from what I gather I think it may be a partial hardware issue... at least for me. I was able to get my device to register again with the workaround by plugging in the USB cable at an angle before seating it completely in the device. For some reason this caused the device to register, why I have no clue. If I just plug it straight in it will charge but not register but initially inserting it at a slight angle must be creating a more secure connection or something and allowing for the device to register. It honestly makes no sense to me but it has worked for multiple tries. I know it will be suggested again that it is the cable but I don't believe that is the case, I am using a anker powerline + which is google recommended, I swapped multiple cables, I also tested the same cable with my nexus 6p and I don't need to do this to get the device to register with my 6P. My assumption here is that the usb port has some sort of issue. This doesn't change the fact that I still need to use the workaround to get it to work with my device, so their likely is also a software issue in addition to partial hardware issues.
I am going to test this out a few more days but will likely be calling to try and make my case for a replacement device. Will keep the threads updated with anything else I can find out.
You guys are way more dedicated than myself. I spent a good two hours screwing with this and wasted a bit of cash on cables and splitters trying to get it to work. I'm not wasting more time or money on it. I shouldn't have to. It should work and I hope they can get it working eventually.
Ball is in your court AA.
Got mine to work with the walk around today. This is the 1st time since the update that my AA has seen my phone. Hope it's still working for the ride home today.
Fyi, thus issue has been fixed for me. Pioneer have just released a fw update for my avh-z5150bt and the pixel connection to my hu is fully functional again and AA is disputing on my cars screen.
Hopefully everyone else will get a firmware update for their units soon.
fmn
Glad the firmware update has fixed your issue.
What's annoying me is that everything worked fine for me for the last 1 1/2 years, and then this pie update hits and nothing works. Google obviously caused this problem, at least for a lot of us.
So this worked for a week for me on Pie and then stopped . Anyone go back to Oreo and test?
There was a 'security update' for Android today for me, it did not resolve the issue.
I think everyone should start a warranty claim and maybe google will start to pay attention more. Maybe the forums mean nothing to them....here is the link.
I am on the phone with them now.
Any luck with the warranty claim? I'm glad we got that extra year warranty due to the screen issues. I'm giving them another week or two, and if there's still no progress, I'll keep warrantying my phone until they offer to give me my money back (or cause me to look into legal options if they refuse), and I'll put that towards the One Plus 6T when it comes out. I've been trying to cut them some slack and be calm about this, but it's been about 6 weeks now without a feature I paid for, and the frustration is building.
I called and was on the phone for 30 minutes. Was told someone would call me back tonight....still no call. I will call back in tomorrow and get them to escalate my case. This is rediculous and needs a fix.
I finally had a chance to do the firmware upgrade (I can never find a flash drive when I need one) and so far it works. I was able to connect for the first time ever. I'm using a Pixel 2 and avh2330nex. Seems to be working so far.
I have the same head unit but the firmware upgrade did not help me at all.
I'll go through the exact process I used in case it helps anyone else. I only do this because it may be some tiny alteration in how you do it.
I used a brand new 16gb flash drive (cheapest one at Best Buy). I downloaded the zip to my MacBook pro. Transferred the unzipped exe to my drive and then proceeded to my car.
First thing I did before starting my car was I turned off my Bluetooth and completely shut my phone off. I plugged in the drive and went through the steps in the directions. I did not start my phone until my head unit was finished updating and I had run through setup to the main screen. Then I turned on my phone and my Bluetooth. Once I was able to connect via Bluetooth, I plugged in and started AA on my phone. It immediately popped into the head unit and worked just as it's supposed to with GPS and my podcast republic app.
We'll see how long it lasts, but this is the first time in a few weeks that it's even TRIED to start
Google hardware support is telling me it is a "known" software issue and they are working on a fix and "hope" to have it out in a few weeks. Would not confirm if it would be part of the October Security update or not.
Thanks for the update, Jason. I suppose we should be hopeful in light of that response (assuming the rep wasn't b.s.'ing you). Fingers crossed.
@Don - Android Auto Team:
I get a USB connection error message displayed on the indash display.
Google Pixel 2 XL
Kenwood DMX7704S
Google Play Store: 11.6.18-all [0] [PR] 211882939
Waze: 4.43.0.3
Google Play services: 13.2.80 (100400-211705629)
Messages: 3.5.053 (Zither_RC22_xxxhdpi.arm64-v8a.phone)
Android Auto: 3.5.583024-release
Android 9 Build number PPR2.180905.005
Permissions:
phone: on
contacts: on
location: on
sms: on
microphone: on
calendar: on
call_log: on
Hi everyone,
You can get the most updated information from this community. For Android Pie connectivity issues with Pioneer head unit, please check this update thread here. For other cars/head units, we're still investigating.
Your frontline support is telling people that the issue has been identified, and they hope to patch sometime in future. in my case, they asked for my car make/model (2017 Ford focus RS) and then told me the above.
Have you guys reached out to Ford sync team on this? Or is it wholly device-side?
In regards to whether this issue is wholly device-side, I want to note that my 2XL worked perfectly fine in 3 different cars before the Pie update, and now does not work in any of these same 3 cars. The cars are a 2016 Kia Optima, a 2018 Hyundai Tuscon, and a 2017 Hyundai Elantra.
Can you guys also try plugging your Pixel2XL into your computer a few times?
Even with Android 9 in safe mode I get an unknown device on win10 and sometimes can't transfer files. Also sometimes can't transfer files connected to Chromebook.
The more symptoms we can agree on, the more likely we will find a solution.
Mine works fine everytime. Win10 64 bit
I can't connect to my Pioneer head unit (AVIC-EVO1-G72), it doesn't work since Android 8 Oreo and still not workin on Android 9 Pie.
I tried tree Samsung's phone ( Galaxy S4, A3 (2015), A3 (2017) ) and a Huawei P8, AA starts everytime.
I try a different cable, still not working.
USB Debug is enable on Pixel
Sometimes, the USB Debug notification appears but nothing happening.
Error message: no response
Car / head unit make & model: Pioneer AVIC-EVO1-G72 (firmware v. 1.06) (July 2018 update)
Phone make & model: Google Pixel XL
Android OS version: 9
Android Auto app version: 3.5.583024-release
I tried tree Samsung's phone ( Galaxy S4, A3 (2015), A3 (2017) ) and a Huawei P8, AA starts everytime.
I try a different cable, still not working.
USB Debug is enable on Pixel
Sometimes, the USB Debug notification appears but nothing happening.
Error message: no response
Car / head unit make & model: Pioneer AVIC-EVO1-G72 (firmware v. 1.06) (July 2018 update)
Phone make & model: Google Pixel XL
Android OS version: 9
Android Auto app version: 3.5.583024-release
I just wanted to tell everyone that AA has been working on my head unit since I updated to the newest firmware. If you have not already done that, you should we least try. Prior to updating the firmware, my phone would not charge and AA would not launch on the head unit. AT LEAST TRY the firmware update.
I have a Pixel 2 XL, it worked fine for months before the upgrade to Pie. Now it just says: "No response. Please disconnect then reconnect USB device." I checked for an Alpine firmware update, nothing is newer than what I have installed.
Car / head unit make & model: Alpine ilx-207
Android Auto app version: 3.5.583024-release
Google Play services version: 13.2.80 (100400-211705629)
AA version - 3.5.583024-release
Playstore version - 13.2.80 (040408-211705629)
OS - 8.0.0 opr1.170623.032
Phone MI5 (MIUI global 9.61. stable)
frequent disconnection
I have tried stock cable which came with the phone and also a usb cable with a type c connector. with stock cable it never connects - just keeps on popping message if i need to connect to android Auto. With the connector at least it connects for some time and then disconnects.
@ Don
Running a Pixel XL2
On a Sony XAV-AX100
Running a Pixel XL2
On a Sony XAV-AX100
Android Build PPR2.180905.005
AA version 3.5.583024-release
Play version 11.6.18-all [0] [PR] 211882939
If I plug in my wifes Pixel XL it runs AA on the head unit.
Plug in my and phone shows that it is charging but will not launch AA on the device or the head unit. It was working as of last weekend but I had not installed the latest security patch yet. Now with the patch it appears to be down.
Side issue - When it was "working" I could not get it to connect to the head unit via bluetooth. That limited calls to speaker from the phone (meaning i could not take calls through the car stereo). Now that AA is not working the it suddenly is connected to the head unit via Bluetooth??
I had that same issue when AA actually worked.
If my phone was plugged in for AA I could not take BT calls. If it was unplugged it worked fine.
I got excited when I saw an Android Auto update today (9/19), but of course, it still doesn't work. My 2XL simply will not launch AA when plugged in.
Google.....this is unacceptable. I've been a Google "fanboy" since the G1 on T-Mobile (for real), and never would imagine I'd be tempted to jump ship to an iPhone, but I can't imagine Apple treating their customers that spent top dollar on their flagship phone in this manner. We're closing in on 2 months now without a fix for a feature that is super important to many users. With Apple CarPlay finally supporting Google Maps, it may be time to see what it's like on the "other side."
I remember talk in these discussions about a class action lawsuit a few weeks ago. Did anyone actually follow up with that? I'm coming very close to the point where I call Google, ask for a refund, get predictably shot down, and then am forced to start looking at legal options.
Eric, if you're thinking about jumping to Apple because "they won't treat their customers like this", don't forget about the time they literally were slowing down phones in their updates to force people to buy the newer versions. We're talking about 2 of the biggest companies in the world, I'm sure they're not too worried.
Daniel -ugh. I know, I know. You have a good point. I'm increasingly feeling like the two only real options nowadays both have such big shortcomings. It's frustrating.
However, I will say this. Whenever there's a problem with iPhones, the problems typically get a lot of press coverage, which then seems to force Apple to provide a fix quickly. Is it because they care so much about their customers? Of course not. But issues with iPhones typically garner more widespread media attention, and thus, they're forced to act quickly. Google seems to neeeeever provide quick fixes, if they provide a fix at all.
I'm in exactly the same boat. Pixel 2Xl prior to Android 9 was working flawlessly with AA on a Kenwood headunit. After Android 9 update the head unit doesn't even recognise it's plugged in. No error message just nothing. Everything has been updated and reset including the headunit firmware, the phone and all apps. Official USB cable that was working before.
It's such an embarrassment for Google that their flagship phone doesn't work with AA.
Like for everything else this phone is a dream and I love it. I would choose it over anything any rival manufacturer is putting out hands down. That kind of makes it worse because I really feel let down by this particular issue and I'm sorry to hear that other people are affected by it.
Please please please fix it!
2017 Cadillac xt5 - worked almost flawlessly for 2 years, since the 9.0 update doesn't even recognize AA and can't even stream audio through the head unit. Calls work fine thru Bluetooth. Worked with support for almost an hour last week to no avail.
I have been using the patch described in this thread for a week now. My pixel 2xl is working with AA and has not failed to connect. I don't like changing settings on my phone. But everything else seems to be my fine. I hope they fix this soon before the patch settings causes something else to break.
Hello? Anyone? Google?
You folks should be ashamed of yourselves for the lack of transparency on this issue.
What a complete and utter joke.
The odds of me going with a vanilla android device, by google, next time around are about zero at this point.
Before you complain, be sure you've updated the firmware on your head unit. I had all the issues described, but installed the firmware update (pioneer avh-2330nex) this weekend and have not had an issue since.
Someone from the AA team did reach out to me for some bug reports about 2 weeks ago, which I appreciated. I sent them, and was hoping to at least see some kind of update by now. So frustrating.
For those of you that are about to throw in the towel with Google's "flagship" devices, what would you consider? I love Samsung hardware, but don't want their skin and bloatware. The Oneplus 6T is coming out soon. Anyone here have any experiences with their phones and how they compare to the overpriced and undersupported pixel phones?
Unfortunately there are no updates for the head unit in my car. I checked. I also tried on 2 other cars where AA works fine with the non-XL pixel, and no dice. Google screwed something up bad, and they either aren't prioritizing fixing it or are stumped.
I'm glad some people's issues were resolved by head unit updates, but that's not the case for a lot of us.
Theyve been asking for bug reports and logs and all sorts of shit for 2 years. Clearly they dont care. Probably are ignoring anyone with AA problems to focus entirely on their Android based car headunits they want to implement as factory radios in new cars in 2020...What a terrible time to be alive that will be. "Sorry car wont start right now i cant seem to connect to Play music" or "Please connect phone to turn on wipers".
I haven't had a chance to check in on these threads for a couple days now but a few observations since last week...
1. The workaround of enabling "unknown sources" in the developer options of the AA App (not just the general developer settings but the app developer settings) seems to have somewhat addressed the issues with my Pixel XL 2 and head unit.
2. When I say somewhat I mean that it does not always work when I first connect my cable. When I plug in the cable it always triggers the device to charge but it does not always initiate AA. Unplugging and re-plugging in the device does not always fix it either. I almost always need to move the cable around and forcefully push the cable in various directions to get it to trigger. Now this is going to trigger a replace the cable response. Before anyone says that, I have tried it with multiple cables, always the same issue. Also, when I use the same cables on my Nexus 6P it connects without having to do this. My hunch is it is both a hardware (faulty usb port or the usb port has not held up to the wear of constantly plugging in the device for AA plus charging plus headphones) and a software issue.
3. I am also glad that firmware updates are solving the issue for some, but a firmware update for a head unit is absolutely not acceptable. It is just another workaround. AA should absolutely not require manufacture head unit firmware updates to work. They should not be breaking backward compatibility with head unit versions. Not every auto manufacturer provides or allows for you to update head unit firmware. A user should not have to have their car serviced to fix AA. If the AA team is actually reading this, this is not acceptable. I'm glad it's working for some but it's a workaround NOT a fix.
Honestly I doubt we are going to get any resolution from the AA team here. A future update may or may not fix your device because honestly I believe their are both faulty Pixel XL 2's (most likely worn out usb ports) and faulty software. An update is only going to fix one issue. A class action lawsuit is not going to do anything, I keep up with the major blogs and I also linked all of these forum threads to each blog as a potential story and none have run it. This leads me to believe this isn't that widespread, with so many android devices a small minority of users having an issue isn't going to be enough for a lawsuit or really enough to garner any attention from Google as you can see is evident with the response from the team in these threads. They simply do not care to do anything beyond the absolute minimum in customer service which is copy and pasting generic trouble shooting messages in each thread.
My advice and thoughts are that anyone with a Pixel, Pixel XL, Pixel 2, or Pixel XL 2 should contact Pixel support continuously, link them to these threads and do everything you can to get a new device. At least that allows you to rule out a potential hardware issue. Someone above noted that support said there was a fix coming and they knew of this issue. This is absolutely not the case. They told me the same thing, I posted what they said and @Don from the AA team responded. He said they were referring to the black screen issue and NOT the issue we all are describing. Again the fix that is coming is for the black screen issue. I can search through my posts to find his direct response to this as proof if you need it.
Go through Google support as they are sending me a replacement phone.
Jason, yes, you're right. Seems like it's about time to start the exchanges. Please post here again once you get the new phone and let us know if it works for you.
"but a firmware update for a head unit is absolutely not acceptable. It is just another workaround."
Is this a joke? You realize the head units are engineered to work with AA, and not the other way around. Google cannot possibly keep up with all the variations in head units. Thus, it's up to manufacturers of head units to keep their products up to spec so they will work with AA. If you did the firmware update (in my case, the update was out well ahead of Pie) and there's still an issue, then you a have every reason to be angry, but you aren't martyr just because you have to do an update on your unit.
If you are THIS fragile, I suggest you go purchase an iPhone and retrieve your security blanket.
Al, the issue is that things were working perfectly fine for many of us for a year with our current head units, then Google updates the os on our phones, and things stopped working. Are you suggesting that it's reasonable that every time Google updates the os, we may have to update our head units? That doesn't sound reasonable to me.
Besides, some of us have fully updated head units anyway - I checked and my car manufacturer hasn't offered a firmware update since my car was released 2 years ago.
No, that would not be reasonable, but is that the case? Have you, in fact, had to update your head unit everytime Android updates or was it just on this one major update?
It's one thing if you've updated and it's still not working, or if you have no update. I can understand being mad but it's completely snowflake to make a fuss about having to update your firmware and thinking they should NEVER be necessary.
My S8 just started working again today thankfully. Wouldn't connect to AA or a computer previously
@Al R
The issue is a lot of us have indeed already updated the head unit firmware with no resolution of the issues.
Also I understand that sometimes a firmware update may be needed after a particularly big Android update, but if that's the case there should be an on screen prompt saying 'head unit firmware out of date please install latest version to continue AA compatibility', especially for the folk who aren't even aware that the head unit has firmware.
Regardless as I already mentioned, updating the firmware has made no difference for me or many others. If there's no fix with the next update I will be returning my phone under warranty as it is clearly not working as intended.
@Al R
It absolutely is unacceptable for a firmware update to be require, and yes they should maintain backward compatibility with head unit firmware. If an existing head unit was advertised to work with AA it should not be broken by software.
1. Not every auto manufacturer allows for head unit firmware to be updated. Some require you take your vehicle in, some do not allow it at all. So for those consumers whom AA may have been a significant factor in the purchase of their vehicle be out of luck? Should they just have to go in and buy a new vehicle? Are we cool with the AA team making updates to AA that break compatibility with head units, so do we now need Google to advertise a list of head units that were and are no longer compatible so when you buy a vehicle you can go look up to see if it no longer works? What about head unit manufacturers that don't make firmware updates, or the head unit is at end of life cycle and is no longer supported but is used in a newer vehicle, AA breaks compatibility and now that new vehicle is AA incompatible when it was advertised as compatible. Do you not see the issue with this? You clearly don't see the bigger picture with this.
2. AA in vehicles has been advertised and promoted as an alternative to vehicle navigation. Many people purchased vehicles without factory navigation in order to take advantage of this. AA can't just break the app for certain head units / firmware and say oh sorry now you are out of luck? A vehicle is significantly more expensive than a cell phone. You can't just buy a new one if AA decides to break it's software for your vehicle.
3. I completely understand if the AA team wants to put in new features (a la wireless use of AA) that require a new firmware update etc.. but they absolutely should not break the function of the core app on existing firmware.
4. This has nothing to do with consumer fragility, this has everything to do with keeping a company accountable. If you purchased a vehicle that was advertised as being AA compatible and it's worked for months or years and suddenly breaks, that is on the AA team. You shouldn't need to purchase a new vehicle or update your vehicle for it to work, new features sure but core functionality should always function.
@James,
Bravo. I could not have said it any better myself. I bought my car 2 years ago and I specifically made a point of buying a car with Android Auto. I skipped out on other cars that I potentially liked better than the one I bought because of Android Auto. It's now been 2 months without being able to use AA, and Google is making me feel like a schmuck for making AA a top priority when buying my car.
Bravo. I could not have said it any better myself. I bought my car 2 years ago and I specifically made a point of buying a car with Android Auto. I skipped out on other cars that I potentially liked better than the one I bought because of Android Auto. It's now been 2 months without being able to use AA, and Google is making me feel like a schmuck for making AA a top priority when buying my car.
I also have the exact issue:
Car: 2018 Kia Stinger GT2
Android Auto app version: 3.6.583534-release
Google Play services version: 11.6.18-all
Pixel 2 XL, Android version 9.
@ James - excellently explained.
We bought cars because AA was a key feature being offered.
We bought cars because AA was a key feature being offered.
Its time for everyone to get together and file a suit against Android, Google and AA
Their lack of response is pathetic.
Their lack of response is pathetic.
Car: 2018 Subaru Impreza Premium
Android Auto App Version: 3.6.583534-releaseSame here with Elantra 2018, I talked with google support and they told me that they are working on a fix, but they do not have an ETA..
In other words - n0, no they arent working on it.
It's funny. One poster calls support, and they're sending him a replacement phone. Another calls and is told they're "working on a fix." what a complete s**t show.
Someone from the AA team proactively reached out to me 2 weeks ago asking for bug reports, and I obliged. I emailed that same email address 2 days ago asking for an update and I got no response.
This is a disgrace.
I don't believe it. They do not tell everyone that calls this, and they will not saywhatthe issue is. They told me that.... Two weeks ago? There has been an AA and Google Play Services industry since then.
At least the acknowledge then issue...
Yea just like non pixel owners texting, navigation, and connectivity issues have been acknowledged for 2 damn years YES YEARS! They say they are aware of the problems and are working on a fix - they will update the thread when more info is available. They have been collecting logs for 2 YEARS and absolutely zero updates. Every damn update they release an update only causes more people to get pissed off at them for breaking thier setups.
Fire the damn AA developers as they are incompetent already.
@Don
Just an update. My issues with AA continue. When I jumped in the car on Saturday morning it would not work. I unplugged and re-plugged 10-15 times with no go. I also tried turning off the head unit and back on again, restarting the phone, clearing the cache for the AA app. Nothing made a difference. Then that afternoon I plugged in and it worked?? I did nothing to the phone that whole day and it did not power down or anything. Sunday morning I was back in the car and AA was working. I was in and out of the car a few times and after my 3rd stop I plugged in and it would not connect to the head unit yet again. To be clear the phone always shows charging once I plug in and Bluetooth calls only work if AA is not working. I am going to call Google this week because this is just absurd.
@Don It has been a month+ now, i think. AA still will not launch at all. I've supplied extensive logs of the event happening to your team. What is the issue, in my case? I know you can't answer for everyone. Maybe if someone, or an AI, analyzed my logs there's an answer for my issue specifically. I'm not even asking for a fix. I'd just like some transparency about what is happening.
@Don, @Andrew,
I am in the same position as Andrew. Your AA team reached out to me on 9/6 and asked me to provide extensive bug reports. I did that on 9/9. I was then contacted again by the AA team on 9/14 asking for more information, which I provided. I emailed that same contact back on 9/20 asking if there was any update, and so far I've been ignored.
Like Andrew said, just give us some kind of update. The lack of transparency isn't right. This isn't a budget phone from some 3rd party manufacturer that we bought. Many of us spent close to $1,000 on Google's "flagship" Pixel 2 XL, and to be treated this way disgraceful.
@andrew and others above,
I submitted logs as well, @Don just commented on one of the other threads:
"Some of the connectivity issues described in this thread is similar to when a USB’s shielding is damaged. When it’s damaged, slight movements can disrupt the signal and interrupt the connection between the phone and the car. Another thing is to check the USB ports on the phone and in the car/headunit to see if there’s debris (dust, lint, etc)."
If you read through some of my posts on this thread and the above, based on my troubleshooting I suspected this was both a possible hardware and software issue. His above comment seems to be finally acknowledging that our actual devices may be the issue as well in addition to a possible software issue in some cases.
My device generally does not work but with the USB debugging but I have at least been able to get it to trigger occasionally but with no real pattern or method to getting it to trigger. I know for a fact it is not the USB port in my vehicle because the port is housed in the covered center console so there is no dirt/grime in that area (I don't keep anything in there so I am never opening it aside from when I have tested new cables with my device). I regularly clean my vehicle and that area of dust, I'm sure there has been a little dust because it's impossible to keep an area dust free but the cable is always plugged in so unless dust is finding it's way in while it's plugged in then not sure how that is the issue. Plus, lets be honest here if a little dust is causing such connectivity issues then our devices would fail with more than just AA. They would fail at charging as well and many users report their devices are still charging.
What I am getting at is that I believe some of us at least may have defective usb ports on our devices or hardware issues and we should be working to try and get replacements. I spent a good amount of time talking with support over the weekend (after they initially brushed me away) and I am working on getting a new device. I will keep up to date on these threads, but assuming I can get a replacement and that solves the issue then I will report back and we should all be pushing for new devices.
I ordered a pair of micro USB to type c adapters. They're useful to have, and am curious as to whether they change things.
I'm not concerned about my cat or cable, they work fine with other android phones. If this is a hardware issue, it is in my phone's USB c port itself. Unlikely, as every time I plug it in, it charges and tries to launch AA, but fails ro get past "unlock to get started" or "get started" if already unlocked.
@James - thank you for the info. I just tried plugging in my 2XL into two Windows 10 computers, and while it charges fine, I get no USB options pop-up to let me switch to file transfer mode. I could have sworn I've done this since the AA problems started and it connected fine, but I've done so much troubleshooting over the last 2 months that I can't be sure.
Now, letting it sit there connected, I keep getting "device malfunctioned" errors on the computers. Son of a gun....is the issue really a bad USB connector? If so, talk about a bad coincidence where the problem started happening after upgrading to Pie. I guess it's time to do a warranty exchange and see what happens.
That was my assumption as well, but after working with support again this weekend they openly acknowledged they have no idea what is wrong. (I have emails to back this up). I assume that if it was software related it would be pretty easy to figure out by the logs we have all submitted as to what the potential causes are.
I really think it could be an issue with both software and hardware, at least for some of us. We have Pixel users and I have seen Samsung users comment about it not working, I find it hard to believe that AA is broke on both Samsung and Pixel devices and there has been no acknowledgement from Google or mention in any Android blog. This just leads me to believe that a subset of devices is having the issue and it could be a hardware issue at least for some of us, and possibly software who knows. I doubt it is just software at this point though. Perhaps an issue with the port where it is seated enough to charge but not transfer data, I know with previous phones and other devices I can sometimes have a USB port partially plugged in and it will still charge but it won't register as a device etc...
And here's the predictable runaround I'm currently getting trying to do the warranty exchange. Friggin' Google. Maybe my Apple sheep friends have a point when they talk about buying Apple for the customer service they provide.
@Eric what are they saying?
I got the same run around the past few weeks, they basically said the team was looking into it and they had no update. The last time I spoke to them I wouldn't take that as an answer, I basically told the rep that wasn't acceptable and that I needed to speak to someone else who had the authority to issue a replacement or to speak to an AA specialist directly. He finally said he would put me in contact with someone within 24 hours and asked me to submit more bug reports. I did this and someone contacted me, they essentially said they didn't know what the issue was and where investigating it but had no update for me at this time.
I sent them a lengthy email saying this was unacceptable and that I clearly have a defective device and they should replace it because it is not functioning as advertised and that is covered under warranty, I said I would file a chargeback with my CC company stating it wasn't working and forwarding the emails where they acknowledged they didn't know what was wrong. After that they started to work with me...
I haven't confirmed a replacement yet, but they asked me for my IMEI number, purchase location, country etc... The last time I got a replacement they asked for all of that info first. So I assume they are at least beginning the process but will keep this thread updated.
Even if you get a replacement, first of all could be a refurbished one, and second you will still have the same error.. so I do not think it make sense to ask for a replacement.
Mine was working correctly but Google messed up with the latest update. Actually they added some features to control the usb by the external device or with the pixel and I think there they had some bugs..
It is bad that they do not say an ETA to fix it. the only thing left is right now either refund it if possible or wait for the next update and the fix.
@James. I figured I'd give the online support a shot first. I've been transferred 6 times now because I was in "the wrong department." One guy went so far as to ask for my IMEI #, but then ended up having to transfer me to a different "specialist" for some reason. I figured the online support might work since I could paste my email correspondence with the AA team and forward them to this link, and at least have a ticket # I could refer to if I had to call instead, but I guess that was wishful thinking.
Looks like I'll have to spend the time making the phone calls. Thank you for explaining what you've been through so far. At least I know what I'm in for.
@Octavio, I was thinking the same thing, until I realized just now that my P2XL won't make a data connection with my Windows 10 PCs either.
Are you (or anyone else reading this) unable to connect to AA, but are able to get a data connection established with a computer?
@Eric I have not tried, but I believe the USB is completely messed up.. My wired headphones are not working neither..
Currently I think the USB is only working for charging.. maybe I am wrong.
I have the same issue as well, my windows PC does not detect my phone. I even tried connecting the "dongle" (USB-C to 3.5mm Jack) and music does not play either through the headphone..
I noticed all of this happening when the most recent update happened (September security patch?).
@Octavio,
That isn't necessarily the case. If what you said where true then everyone with the same device would be having the issue and they are not.
There are Pixel XL 2 users on this board that report there phones are working, if the Pixel XL 2 (and all Pixel devices) have been broken by Pie we would have seen some acknowledgement from Google on top of the fact that the blogs and android news sites would have run with the story. I mean there was an uproar because people saw a faint tint of blue on their screens vs a core app being broken.
This leads me to believe it may at least be partly issues with our devices. It doesn't make sense that AA will work on one Pixel XL 2 and not the other. If it was entirely software then both devices would not work.
@James, well Google already acknowledge the issue (I talked to support and they did, also someone on this thread did).
And yes I might be wrong, I do not work there so I do not know what is the problem, but my guess is that it is affecting only some of them and it is related to an update issue (software not hardware)
and what you are saying it is possible also that a third party or something is messing this up.
On Monday, September 24, 2018 at 3:10:31 PM UTC-4, Octavio Limon wrote:
@James, well Google already acknowledge the issue (I talked to support and they did, also someone on this thread did). --Correct, but publicly they haven't acknowledged anything. If this is an issue on all devices that would be a significant issue, not only would consumers be upset but they would be facing backlash from auto makers who now need to explain to customers that their devices won't work as advertised with their vehicle.And yes I might be wrong, I do not work there so I do not know what is the problem, but my guess is that it is affecting only some of them and it is related to an update issue (software not hardware) --If its only a subset that supports a possible hardware issue, why would only some Pixel's be effected but others not. There are really only two ways, something hardware related is different between the devices or as you said below a third party app is causing the issue. I suppose we all could delete everything off of our phones to rule that out but I believe someone at some point did a factory reset and had the same issue. I would rather get a new device and rule out hardware while I am still under warranty rather than wait for an answer that we have no timetable on arriving. Not to mention if you get a warranty replacement Pixel and you still have the issue then you can send the phone back for a refund and at least purchase one of the phones that is working. I love my Pixel (aside from this) but I would rather have a working phone from another manufacturer than a Pixel that doesn't work.
and what you are saying it is possible also that a third party or something is messing this up.
that is up to you, if you get a replacement might be a refurbished one.. I would prefer to wait a little bit. if they do not fix it I will replace it, also remember that we have 2 years warranty.
Octavio has a great point about the extra year warranty. That's huge for us right now.
After being transferred and speaking with 7 different online chat support "specialists" (no exaggeration), the last person said that he was escalating my issue, and that I'd get an email within 24 hours, which I believe is what happened to someone else. I'll see if I actually get that email and what they say.
I'm fine giving them my credit card for advance replacement, so I figure I'll let them send me a new one, see if it works, keep it if it does, and send it back if it doesn't. I clumsily shattered my screen back in January and am already on a refurbished unit, so that's not an issue for me personally, although I can understand others not wanting to roll the dice in that regard.
Can other Pixel 2XL owners that are having this problem with Android Auto connect your P2XL to your computer and see if you're able to establish a data connection to transfer files?
I just learned yesterday that in addition to my P2XL not launching AA when plugged in to my head unit, when I plug it into my computers, I get "USB device malfunctioned" errors.
I'm wondering if there are any P2XL owners that (1) cannot get AA to launch when plugging in to the head unit, but (2) are able to get a data connection when plugging the P2XL into their computers.
I just did my first factory reset since discovering my P2XL no longer gives me a data connection when connected to computers. Still nothing. My port is obviously defective. I've been talking to Google Support for 45 friggin' minutes right now. I've been transferred twice and they're still giving me problems about "it could be software" and not wanting to send me a replacement.
Between being transferred to 7 different people over the course of an hour and 15 minutes yesterday via online support, being told my issue was escalated and never getting my promised call-back/email within 24 hours, and now this, I can honestly say that this is the second worst customer service experience I've ever had in my life (Verizon FIOS being #1 - congrats Google for joining their ranks).
I feel for those of you that are going to have to go through this process too. Word of advice - don't even mention Android Auto. They keep trying to deflect to a "software" issue, even though I can't get a data connection on my computers. If you are in the same boat as me, just tell them it won't connect to your computers and don't mention AA.
So frustrated right now. If I don't get the replacement sent before hanging up, I might rage walk into an Apple store and buy a friggin' iPhone.
Let me know how that goes.
Just tested on my PC with my USB A to C cable, says the usb device has malfunctioned. I pulled out my USB C to C stock cable from Google and I get the same error (my PC has a USB C port).
Just tested on my PC with my USB A to C cable, says the usb device has malfunctioned. I pulled out my USB C to C stock cable from Google and I get the same error (my PC has a USB C port).
Sounds like that should be enough evidence it is the port. Calling again now.
Just to add to this, I left both cables connected to my PC. Booted up my Nexus 6P and it connects with both cables immediately without issue. Just like it does with AA in my vehicle.
Either Pie messed up all data transfer via USB for Android devices or we clearly have defective devices.
@James - one would think it should be enough evidence. But not in my case. However, I may have screwed myself by first having them escalate the issue as an Android Auto issue first before I realized the data connection won't work on my computers either. My escalated ticket was never closed, and I think that's part of the hold-up in my case.
My friend's P2XL with Pie works perfectly fine on his computers (he doesn't have AA to test it with, and I haven't seen him in person lately). So I think we just have bad hardware.
Good luck with your call. I hope you have more luck than me. George, one of their supervisors, emailed me a ticket number, and PROMISES me he'll call me back by 9:30pm EST tonight after checking with the escalation team. I hope he wasn't lying to me.
Interesting that the USB C port may be to blame. Does anyone have any idea why this is temporally linked to the Android 9 update? It seems strange that we all got the same issue at the same time after the same update.
With everyone having the same problem and the problem starting since the recent update I would have to disagree with those that believe it's a hardware issue.
@Peter, I felt the same way. Until I tried to connect my phone to 3 different computers and couldn't establish a data connection with any of them, using 3 different cables, even after a factory reset. Have you checked to see if your phone is able to do file transfers on a PC? Mine gives me a "USB device malfunction" error and I never get my file transfer dropdown. My friend's P2XL works fine with computers. Both phones are fully updated.
@Eric, I have the same issue, I already tested and there is not data connection with the pc, this sucks hehe, but I still believe is a software issue.
if you can wait for the next update.
I will contact google to see what they say.
@Octavio,
Iiiiiinteresting. So far no one has said that their phone works when plugged into their computer, but doesn't work when plugged into Android Auto.
I also really thought (think?) it's software. But then why would some P2XL's, like my friends, work fine? My P2XL and his are both fully updated. I even factory reset mine and booted it up into safe mode, and it still won't be recognized on a computer.
I think it's also worth noting that in my case, the problem didn't start immediately after updating to Pie. Shortly after updating to Pie, AA worked fine, but with that random black screen. Then the next AA update fixed the black screen. Then shortly thereafter, these problems began.
I'm totally spitballing here, but could Pie have done something software wise that affected the voltage draw in the port, and that damaged some of our devices? I don't know. What I do know is I'm super frustrated, especially after factory resetting for nothing!
@Eric, your last point about Pie illuminating a potential hardware issue is something I was always thinking could be the case because my issues did not start immediately after the update either. I posted this same thing in my other thread.
I just got off the phone, the support specialist opened a separate case for the PC issue. He said the reason they won't issue a replacement for AA is basically that the engineering team has not ruled out that software is the issue. They are still trying to determine a root cause and thus have not authorized anyone to give a replacement for AA specific issues. So until the support team hears from them that hardware is a potential issue we won't get replacements and are stuck waiting for a resolution.
I just got off the phone, the support specialist opened a separate case for the PC issue. He said the reason they won't issue a replacement for AA is basically that the engineering team has not ruled out that software is the issue. They are still trying to determine a root cause and thus have not authorized anyone to give a replacement for AA specific issues. So until the support team hears from them that hardware is a potential issue we won't get replacements and are stuck waiting for a resolution.
Now, if you can get them to open a separate ticket for the PC issue then a replacement is a possibility. I was emailed a list of troubleshooting steps that I have to cross off before they can issue a replacement. So going to work through that list tonight. Unfortunately one of them is factory reset so it's going to be awhile before I can get it done.
@James,
Thanks for the additional info. It wasn't explained to me very clearly, but I think that's exactly what happened to me. I believe they've opened another ticket for the PC connection issue and that's what they're going to (allegedly) follow up with me about.
Just went through the troubleshooting steps and provided pictures and screenshots of me completing each step. The only thing left to try is a factory reset.
The device is clearly malfunctioning when it's connected and not being recognized. Not sure what a factory reset will do at this point but will give it a shot.
So I went to support again, and we followed a lot of steps, after trying to troubleshoot the issue, we ended up with a factory reset, but the issue was there, they guy said that it was a hardware issue related to the port so I am having a replacement.
I guess I was wrong about thinking it was a software issue.
I'm glad the process was relatively painless for you, Octavio - minus the factory reset. I guess I won the unlucky lottery with the support reps that I'm working with. Let us know how things work out with your replacement device. I'll do the same - if I ever get them to ship mine.
And another thing. I just plugged wired headphones into my USB C port with Google's dongle. Guess what? Yup - it's not recognized, and audio just plays through the phone's speakers. I can't believe I didn't think of trying these things until now. What a waste of 2 months of no Android Auto and misplaced troubleshooting. My apologies to the Android Auto team. As for the rest of Google support.....
Google finally just put through my replacement order. It took about hours total and about 12 different reps if you count online support reps and phone reps, but a supervisor named George finally took ownership and helped me out. I'll post back here once the replacement arrives. Good luck to those of you that have to order replacements still. Don't focus on Android Auto when calling. Test connecting to your computers and headphones with the dongle, and tell them that nothing works.
@Eric
Glad they finally issued you a replacement. Hopefully I get the same good news tomorrow.
Glad they finally issued you a replacement. Hopefully I get the same good news tomorrow.
I took screenshots and pictures of each troubleshooting step and also performed the factory reset this evening. I documented that as well and as expected the device would still not connect to my PC.
Since you mentioned the headphone dongle, I actually have already had this phone replaced (got a new device before they were sending out refurbs because it was early in the life cycle) due to the USB dongle not working with my device. I could not get it to transmit audio through to my headphones without having to restart multiple times and unplug / replug in the dongle multiple times. Honestly the replacement never fixed the issue but I wasn't going to continue arguing with them. I just re-tested the headphones and dongle after the factory reset and as expected they still do not work. I then plugged the dongle/headphones into my Nexus 6P and it connected immediately and I could play music through the headphones without issue.
There is clearly some kind of issue with the USB C port on the Pixel XL 2's and transmitting data through USB. I'm not sure if it is really hardware or if something in the software is causing the issue but there is an issue nonetheless.
I hope I get a replacement and it actually fixes the AA issue. But I am concerned how that will affect trade in values. I am hesitant to get a Pixel 3 but assuming I get a replacement I will be on my 3rd Pixel XL 2 all with the same recurring issue. I don't want to go through this again a few months down the line. I would rather just get a new device entirely. If a refund was an option I would gladly take it over a replacement.
Verified earlier, I can connect my phone to PC no problem with Ian C cable
It may still be a combo of software and hardware issues but who knows at this point.
I know I initially could use AA after the update, it didn't just immediately stop working. It degraded and then just stopped working completely. I would continually check if I were you that it will connect to your PC as it could still be in the process of completely failing if it is the hardware issue.
Do you have any issues with wired headphones and the adapter?
It's possible you don't have the same defect as some of us even though it's similar symptoms. Overall there just seems to be a ton of instability around AA which is a shame.
Error message: None
Car / head unit make & model: Ford Fusion / Sync 3
Phone make & model: Google Pixel 2 XL
Android OS version: Pie (9)
Android Auto app version: 3.6.583534-release
Google Play services version: 13.2.80 (100400-211705629)
Android
Auto was working perfectly fine up until this afternoon (it even worked
this morning). Nothing was changed on my end in my car, or my phone.
Was working perfectly before on my Sync 3 system with Android 9.0 up
until today.
I tried a Master Reset on my
car unit and also cleared App Cache / App Data for the Android Auto app
on my phone. Considering I have two USB ports in my car, I tried both
ports. Car detects phone with no problem (it even says when I connect
it via USB) but doesn't even attempt to launch Android Auto.
I
also tried multiple USB A to C cables, including approved Anker ones.
Phone connects to computer with no issue and am able to transfer files.
Please assist.
I guess my topic was merged with this one? (the post above) I'm not sure if it's really PIE related because I've been on PIE for over a month with no issues.
What does it take for us to understand? www.classlaw.com
Having the same issue now.
Honda Civic LX 2017
Android pie 9
Google pixel
Android auto updated to latest version.
The phone will stay on the screen saying you can click on the icon on your car to start it, and on my cars head up display it says stuck at loading.
My Pixel 2 AA stopped working correctly with my 2018 Kia Forte after updating to P. I have found that a short 1ft cable works fine but nothing longer. I've tried multiple 3ft cables including ones that used to work. Sometimes with a 3ft cable it will connect and last up to 5 minutes before it starts flashing between connected/connecting/disconnected. My Pixel 2 does work on my 2017 Kia Sorento without issue though.
Here's a new kicker. Tried my friend's Pixel 2 XL on Pie w/latest security patch. His works with no problem. Tried mine again, no go.
I still do not believe it's a hardware issue. I'm able to plug into a PC and transfer data without issue. Maybe some Pixels need some firmware/software tweaking for their USB?
I will wait until next patch in October or when the next OS launches with the new Pixel before RMA'ing my phone.
I have both a 2018 MB E300 and a Chrysler Pacifica with uConnect 8.4.
Phone Pixel 2 XL with Android 9, AA version 3.6.583534
Using genuine Pixel USB A to C cable (2 different cables)
Neither car will accept AA anymore.
I plug in my Note 5 with marshmallow works fine.
Steps:
Deleted Phones from car and repaired
Deleted cars from Bluetooth and repaired
Forget all cars in AA (Will not add new cars to AA now)
Help. Expensive cars/Expensive phones - not working is not good.
I want to buy Pixel 3 but not if it is not going to work in my cars.
Thanks
Well, the MIDI tip didn't work, so I played with the settings in the Default USB Setting under developer options. After changing it to "File Transfer," my Android Auto has been flawless. 4 trips of 30 minutes + without a single disconnect. Perhaps the September Update changed the way the phone appropriated the Android Auto USB mode, and then it freaks out?
Hopefully this workaround works for everyone here, obviously YMMV.
If you need to access Developer Options to check for yourself, Settings > System > About phone and tap the "Build Number" until it says "You're now a developer." Go back a menu to System, tap "Advanced," then tap on "Developer Options." Scroll down and tap on Default USB Configuration and change it to File Transfer. Close out of the developer options, disconnect and reconnect your phone.
@ James Duke
This makes sense, but it would be interesting to note what the USB setting was BEFORE the update to Android 9 Pie. I have Pie 9 and Default USB Configuration was set to "No data transfer." Was that the same setting on Android 8? I have no way of telling. Anyone out there that did NOT upgrade to Android 9 able to check that out?
I guess how do each of those USB modes work, and what "files" are we transferring by selecting "File Transfer." Also, on the actual Android Auto app in the options for connecting to Bluetooth does it matter if that is ON or OFF? When Android Auto is connected to my head unit is it streaming music via Android Auto and USB or is it streaming via Bluetooth?
@Jason Miller
I know on with my Pixel 2 XL on Oreo, it prompted me to change when I would plug it in to a computer. Since Pie, it has not. However, I was using Android Auto with Pie with a Rental Car on the August Update and it worked flawlessly. It just so happens when I arrived back from my business trip that the September update happened. I did not have AA in a car until Saturday, when I bought my new Subaru. AA worked for about 5 minutes after adding the car, then disconnected and went to the "Simplified Display" on the phone. Uninstalled/Reinstalled, set up AA, it would work for 5-10 minutes, then disconnect. I swapped cables with no change until discovering someone talking about the MIDI change in the developer options and then checking the cable on a Windows computer, where it had worked, also before the September update. It didn't work like it had previously in the rental car until I turned on the File Transfer.
@James Duke,
If you read back through the posts on this and some of the other longer threads, users have tried this. It worked for some but not others, which is in line with almost every workaround we have tried.
I personally tried those settings and switching between all of the USB modes and none of them made a difference. When I called in this week after testing my phone via PC & headphones after another user mentioned his device not working one of the troubleshooting steps was to manually set the USB Mode to File Transfer to test. This did not work for me and I documented this.
I originally bought a launch device and had my Pixel XL 2 replaced in Feb. because of a similar issue (phone would not transmit audio via the adapter with wired headphones). This was before the Pie update, so I am still sticking with it being hardware related, could it be that changes in the last update brought to light the hardware issues possibly but it seems like some of us have some sort of combination of hardware/software issue that others with the same device do not.
I finally got the RMA issued. I know we are getting refurb devices but the purchase price for the refurb is the same as the original device. I am hoping this is a sign the refurbs will get full trade in value. Hoping to jump on a Pixel 3 as it launches and trade this in, 2 warranty claims on one device is enough for me not to trust it. I have a hard time trusting the Pixel 3 but at least I know they will be more willing to work with support wise on a brand new launch device rather the previous device.
Wtf, you are buying a Pixel3, after this bullshit? Wow.
That's nuts. Google pixel is garbage. Support is by idiot robots.
The 3XL is a hard no for me because of that ridiculously deep and ugly notch, so I'm glad I don't have to decide whether to leave the Pixel line just yet. I'm planning on sticking with the 2XL for another year, or maybe the OnePlus 6T if it really wows me.
However, I have to kind of agree with James Clapper regarding Google's support. Back in the Nexus days, the support was wonderful! Now it's mostly a bunch of people who don't know what they're doing, don't really give a crap about the customer, and are just going through their troubleshooting flowcharts with no real understanding of what they're talking about.
And I say this out of experience, after dealing with 7 online chat "specialists" and 5 or 6 phone reps over the last few days regarding this issue. Absolutely atrocious and dreadful experience.
Don't get me wrong I have been extremely unhappy with the service but would it have been any different if we had any other device? As a few us have demonstrated in the past few days the entire reason we have gotten such a run around is because we called in and reported this as an AA issue. I guarantee if you have a Samsung, Essential Phone, LG, Huawei, Motorola etc... and called into support reporting an AA issue you would have had the same problem. I also doubt you would be getting a replacement device from any of those manufacturers for AA not working.
Had we called in and reported our devices as not working with our PC's / Headphones we likely would have gotten a replacement without a hassle. While all but one of the reps I spoke to were unhelpful I did manage to speak with one rep that actually took the time to explain why they couldn't issue a replacement for just an AA defect. Essentially the engineering team or some team identified an issue and at the time was still determining if it was hardware or software, the support teams have a set of rules to follow as far as replacements based on the specific issue you have. Basically any AA issues were determined to not warrant a replacement and thus forced us to have to wait for the update. Do I agree with this? Absolutely not, but it explains why we had to find other issues with our device in order to get replacements and why we had such a difficult time.
My Pixel XL 2 has largely been a fantastic device, except for this one critical issue. This leaves me two options:
1. Jump to another manufacturer - As I said above our AA issues have been reported across a multitude of devices not just Pixel's and I am fairly confident that Google wasn't going to do anything special for you if you had a Samsung, LG etc... Those manufacturers have no control over AA so you would be just as handcuffed. If you call into Samsung and report AA as not working with your device I'm not sure they send you a replacement.
2. Jump to Apple - This is a personal no go for me. While the new Apple devices are great devices I am fully ingrained in the Google eco system. I don't want to switch out all of the current devices and services I use. I also frankly don't like the Apple UI / look and feel of the UI.
While it was a absolute pain I still have managed to get two replacement devices from Google during the life of my device. Any issues with AA would have gotten the same response from Google / Manufacturer as I already received. So for me id rather roll the dice on a new device and warranty. At least I know now when I call into support I won't even mention software as an issue and immediately report it as a hardware defect so I don't run into this again. I still have my Nexus 6P that functions fine to fall back on if the Pixel XL 3 has the same AA issues and if it does then I can make the hard decision of if I want to uproot myself from the Google ecosystem once and for all and convert to Apple or not.
I will keep up with the threads here and see what happens when my replacement arrives / Oct. Security update to see how AA performs. There will still be time before launch to make a decision.
So it is true that from the beginning pixel had some manufacture defects, however google by giving 2 years warranty shows how Google believed in its device.
For me the google support was fine, they tried to fix it, after that factory reset and then replacement, it would have been the same in apple.(I had apple before this pixel)
Maybe the phone is not the best but beside this defect with the usb port, it has been great
Project fi, and google services are the best, so sticking with a pixel I think is a good choice for me.
I was having all the issues described in here, both AA not working at all (even before P) as well as windows not recognizing my device. This all worked fine on my Nexus 6P. Talked to both Google and Fi support I'm getting a replacement under warranty. I had originally tried making a claim describing only my AA issues and they just wanted me to send logs. Once I realized I had the USB issue with Windows 10 as well I contacted them again about it. We went through all the trouble shooting steps on a screen share session and we're unable to resolve it, so they are sending me a new phone.
Similar issue for me as well......
My Pixel 2 XL used to work fine with my 2018 Silverado HD. Now it will not connect.
I get the error on my dash: Projection device not connected
Phone:Pixel 2 XL with Android 9,AA version 3.6.583534
tried 3 cables of which at least two worked before.. probably all 3 did.
Bluetooth works fine
cable will charge phone
tried various things, power reset, enabled dev options and USB debug, disabled, re-enabled, uninstalled and reinstalled AA.
What gives?
I received my replacement Pixel 2 XL and updated it to Android Pie and restored from Google.
AA WORKS PERFECT NOW.
The USB-C connector seems much tighter than my old one.
But even with all the updates it seems to be a hardware issue (And possibly software)
Not
sure if everyone else who had this issue was an early adopter of the
Pixel 2 XL but i ordered it the day it was released and had one of the
early units.
I would recommend going through support and don't take no for an answer until they say the will replace it.
Hope everyone gets fixed.
Replacement phone is out for delivery right now, unfortunately my car is at the body shop right now until Monday or Tuesday. I'll post an update once I get my car back.
Just set up my replacement P2XL. Updated to Pie. AA and PC connections are working flawlessly so far.
Glad to see everyone that ordered a replacement is reporting back that AA is working again. So much for it solely being a software issue with Pie. I really wish @Don would comment on this, where is the AA team? Maybe the canned response of checking cables etc.. should be changed to call Pixel Support and get yourself a replacement.
Will have my replacement next week, hoping that I can report back the same as you guys and have working AA (and PC / wired headphones)
Eh? i thought that the few that have had replacements sent clearly had an issue with their device (no data connectivity to any device) and not just AA failing to load in-car.
That's why I said solely software, it can still be a combo of the two but it clearly wasn't just Pie.
True there are plenty of users that still can get successful connections to other devices but that still doesn't explain why one Pixel XL 2 user has working AA with Pie and why another Pixel XL 2 user does not. Is there a bug in the software causing issue in certain devices? If that's the case it still leads back to the device, mine es well issue replacements for those devices so users can get back to running AA, rather than have to wait for a software fix that may or may not fix the compatibility with the device. AA is clearly not broken for everyone with Pie.
Supposedly a fix is coming in the Oct. Security patch, I suppose well see if everyone's device just starts working again.
So I got the replacement and it is working with the AA without problems, however the mobile network is not getting signal.. I called support twice and it works only around an hour and then it stops working :S
Ugh. That stinks, Octavio. Sounds like you may have gotten a defective replacement. Let us know if it was something else.
After setting up the new device I'm now able to successfully connect to my laptop to transfer files where before I got "Unknown USB Device". Will update again once I can test AA when I get my car back from the body shop. Going to keep a look out for issues on the replacement device like Octavio has.
Car / head unit make & model: 2018 Mercedes E300, 2018 Mercedes GLE, 2018 Chrysler Pacifica w/ uConnect 8.4
Android Auto app version: 3.6.583534-release
Google Play services version:13.2.80 (100400-211705629)
Phone - Pixel XL 2 - Android Version 9
Steps that I have taken -
tried 2 different genuine google USB A to USB C cables
usb debugging on then off
usb set to file transfer
usb set to usb tethering
uninstalled AA,
Cleared AA Cache
uninstalled bluetooth from phone
uninstalled phones from car
factory reset phone
verified that it also would not connect with Win 10 PC
verified AA worked in car by connecting Note 5 running Oreo
Pulled all of my hair out!!!
Please at least reply that this has been read.
Thank You, I can see that you are being attacked swamped on this issue, and am grateful for your continued efforts.
@Sam,
Try the headphones dongle and see if it works. If not, I bet your USB port is defective and you need a replacement. That's what happened to me. No AA, no PC connection, and no dongle audio. Replacement works perfectly.
I don't think all of us suddenly have a USB failure. This seems more related to pie. Getting a replacement that works does not completely indicate that the USB was failing.. it may just be that Pie works fine with the recent hardware, but not with the first ones.
Count me as another one who's AA connection stopped working today (after an apparent server-side update to AA if Reddit is to be believed). I will say that my audio dongle isn't working either although the phone charges fine. I find the timing of it all to be odd.
Pixel 2XL
2017 Chevy Camaro SS factory head unit (Chevy MyLink)
Android Auto: v3.6.583534-release
Google Play Services: v13.2.81 (100408-212283828)
I just wanted to say thank you. This worked for me with my pixel 2 xl. Its funny because prior to the pie update I was enabled. The update must have disabled the developer mode.
Thank you again! Google support wasn't able to figure this out, but you were!
It's not rocket science. If AA doesn't work, AND PC data connections don't work, AND wired audio doesn't work with the dongle, there's obviously a problem with the USB port.
If just AA doesn't work but the other things do, then it's a different story.
Hi all, I want to pass along something that worked:
I've had all the same symptoms as many/most of you, but I'm running a Samsung Galaxy S8. My HU is a Pioneer AVH-2330 NEX.
I tried everything that everyone has tried; firmware update in the HU, developer mode, usb debugging, various settings in AA and USB modes, etc etc. Nothing worked even though my phone worked fine for 6 months.
Pioneer has a tech bulletin on their site that says something about how some users of newer phones with type C usb are having trouble, and you need to use a certified cable. It then listed some cables. I didn't buy that since my AA worked great for months and since this same cable worked for PC data xfer, tethering for mobile data, etc etc.
To make this a bit shorter, I eventually bought one of the cables they recommended and the effing thing worked! I was shocked.
So, in case it helps, here is a link to that bulletin that lists the recommended cables:
I hope this helps.
@James
Have an LG G6, the phone worked seamlessly with AA & 2018 Acura MDX until the oreo update.
LG and Verizon both said they cannot do anything as they do not control the Android software problems.
My wife was smart and did not update her phone from nogart and all works fine on her phone still.
Surely a problem with the update to 8.0 or above but Android seems to care less about this issue.
Surely a problem with the update to 8.0 or above but Android seems to care less about this issue.
Luckly if Pixel phones work after replacements.
You are correct LG said they cannot do anything for this till Android fixes the software issue.
I even have the same problem on my oneplus6 ,while connecting to my VW Tiguan Car. the issue is related to call log history not getting refreshed properly, Whatsapp messages no longer gets display when there is a new message , checked with One Plus team ,they informed me to check with app development team.
After reading Selius's post (Sept 7), I bought the 3ft Cable Matters cable (https://www.amazon.com/gp/product/B00S8GU2OC/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1), and Android Auto now works with my car. Not sure what the issue was. The cables I was using does not work with my car, but work with my computer. Wierdd.
YES!!! Exactly the same for me. Very very weird. Something changed and I don't think it's the cable. Some signal thresholds in the software? I just don't know.
And now today everything works again. Headphone dongle, AA, connecting to PC... Google has already shipped a replacement device. I'm not sure if it's an intermittent USB port issue or if they fixed something in the background.
It wasn't a server side update, check your phone to see if it auto updated to the October Security patch. Apparently the patch included a fix for AA and for the fast charging issue.
While the fast charging issue never mentioned anything about a PC or Headphone not communicating with your device apparently they were related to the same issue. Whatever fix they implemented for the fast charging fixed the inability of devices communicating to PC / Wired Headphones via adapter. After the security update my Pixel was finally recognized by my PC and AA seems to be stable.
I am not sure what I am going to do with the replacement device yet, I am going to test my device out a few more days before I make any decisions to determine that everything was in fact fixed by the patch and isn't just intermittently working.
So it seems to point to it not being a hardware issue despite the inability to communicate to PC/headphones. Google never mentioned that as a side effect of the fast charging issue. Again, all of this could have been avoided by the AA AND Google teams working on fast charging issues communicating with the user base, letting us know they have in fact found the issue and have been working on it rather than dodging the questions and re-directing people to buying new cables and trying all of these random settings in developer mode.
You just wasted our time and your time. And on top of that you have replacement devices that went out to people that likely never needed to be sent out. You caused a ton of ill will within the community when if they had just been up front from the beginning it could have all been avoided. If you know what the issue is then say it, I have no idea why you aren't able to do that. It's clear both teams at Google knew what the issues where and what symptoms they were causing, seeing as how they are remedied in the security update.
Except all of my functionality was restored before I downloaded the October security patch so... ¯\_(ツ)_/¯
How do we check to see if we have been pushed the update?
settings -> system -> advanced -> system update -> check for update
"The October update also includes improvements to Android Auto stability" - https://www.theverge.com/2018/10/1/17924792/google-patch-pixel-xl-phone-fast-charging-security-issues-bugs-fix
For what it's worth, I haven't sent back my defective P2XL yet. On the defective unit, AA, PC connections, and USB dongle/headphone connections all didn't work. I just did the October security patch in conjunction with another factory reset, and these things are all still broken. So at least in my case, the USB port is indeed defective.
Final update on my replacement device. Got my car from the body shop. First thing I did was plug in my phone to the head unit and it instantly all worked. This was the first time I've ever seen it work! So my new device is connecting properly now to my Windows 10 machine and my Alpine ILX-207 head unit. If this wasn't already great, this new replacement device doesn't have the horrible blue tint from the screen when looking at the device from an angle!
Great! by the way did you test your previous phone with the latest update?
I got also a replacement but the replacement was not working fine.. so I after 7 hours with support I am getting another replacement.
I did the October security update today. AA still does not work. I am just completing a reset on the phone, and will try again in a few minutes.
I am getting my replacement later this week. 7 hours on the phone!?!?! Wow.. that sucks. I spent right at an hour to get my replacement... Hopefully all good... and bonus if no blue tint... I just hope it ALL works. I hate refurbs. I also got the Oct update and no change. My dongle does not work, nor can I see my phone on win10.
I did a factory reset, reinstalled all my apps, and AA works now. Whatever.
Yes Octavio, I updated my device and still had all the same issues.
Chevy Mylink in my traverse and volt. Will not launch after pie update and recent patch
And no good with 10/5 update that was specifically supposed to fix AA connectivity to head unit. Ssdd
I have a 2017 ford flex and starting having problems connecting my Samsung S6 to Android auto on my vehicle display screen. Then all of a sudden it stopped connecting at all to my vehicle. Very frustrated. Tried new high quality usb cord. Tried uninstalling app and reinstalling. I've talked to ford, and my cellular provider AT&T for hours and nothing helps. Does Google have a customer support phone number?
Some solution ontheway??
Same problem, both the pixel XL, and the pixel 2 not recognized by head unit.
Kenwood- DMX7705S
Android 9
Kenwood- DMX7705S
Android 9
"USB device not recognized"
Occasionally it will connect, for about a minute, then the same message
Andriod auto stopped launching to the headunit after update. Phone still charges. Very frustrating.
PXL 2 XL
VW golf 2016
Play store: 11.9.14
Andriod auto: 3.6.583534
Is it working perfectly now?
Same here on Pixel 2Xl latest versions of all, on an Audi A5 (Germany) made this July.
Hey Don,
Have we figured this out yet? Obviously this isn't a unique situation as everyone is commenting on it saying they're experiencing the same thing with their pixel phones.
Hey everyone, with the new update that was pushed to my phone today, it seems to be finally fixed!!
Who pushed it to your phone? Can anyone push this to my phone?
I spoke to support about 4 weeks ago about the Android auto issue, figured I would call back today to see if there was a resolution. The support agent has informed me that an update will be released within the next week that will specifically fix this problem. Let's hope it works
ClaudioPerez42, which version of AA now have?
Hi Peter Cosmoglos,
You’ll get the most updated information from this community when we have news to share such as a fix
You’ll get the most updated information from this community when we have news to share such as a fix
Really Don that answer is beyond unacceptable from Google & AA but why would either Google or AA care of the cosumer getting screwed
Vehicle: 2018 Honda Fit w/ Android Auto & Car Play
Android Auto Version: 3.6.583534-release
Google Play Services: 14.3.66 (100400-213742215)
Android version 9 - October 5th Security Patch
Phone: Pixel 2 XL
Troubleshooting steps:
Uninstalled and reinstalled the app.
Forgot the Car
Had the car forget the phone and readded the phone to the car
Car works with my Pixel XL