Database Info

Android Auto

Hi, after reading a few threads about android auto compatibility with the essential phone, I have been put off purchasing as AA has become a pretty permanent fixture of my commute.
There have however been software updates I see by Essential, notably the latest firmware in the past few days. Just wondering if anyone has seen any improvement in android auto experience with any of the latest updates?
Thanks.

I havent had an issue. Im running AA on both my 2017 Audi and 2017 GMC. I had issues with my LGV20. With the LG, i would have to reboot the phone to get AA to recognize and even when it showed connected, text messages werent available. If i unplugged the phone and then tried to plug back in, i would have to reboot the phone if i wanted AA to work. With the essential, i can unplug the cable and plug back in and resume what i was doing seamlessly and all the alerts/texts come up no problem anymore

Same here no issues I use a couple of hours per day.

It works great with my modded Infotainment center in my 2016 Miata. However, it will not stay connected to my aftermarket 2016 Kenwood head unit in my other car more than 1-2 seconds constantly connecting and disconnecting. I've tried half a dozen different cables. Works fine with my Nexus 6.

elkay said:
It works great with my modded Infotainment center in my 2016 Miata. However, it will not stay connected to my aftermarket 2016 Kenwood head unit in my other car more than 1-2 seconds constantly connecting and disconnecting. I've tried half a dozen different cables. Works fine with my Nexus 6.
Click to expand...
Click to collapse
This was what I had heard of in the forums and gives me pause about purchasing. May I ask if you have tried with latest firmware which Essential says contains some bug fixes?
Thanks to the others with positive experiences. More encouraging!

Are the reported issues with the phone itself running Android Auto and just Bluetooth connecting to the car, or when the phone is linked to the head unit?

Seamonkey79 said:
Are the reported issues with the phone itself running Android Auto and just Bluetooth connecting to the car, or when the phone is linked to the head unit?
Click to expand...
Click to collapse
As I understood it, it was with the phone linked to the screen of the head unit. Mine is a 2016 vw. There was a similar issue with the Oneplus 3 which kept disconnecting for no apparent reason and Oneplus fixed this with a software update which is why I was enquiring about updates here.

No problem here, connecting to and staying connected to my wife's 2016 Ford Edge, and my 2016 Corvette.

I use AA everyday, in my 2018 Audi Q5. I've never seen it drop out once.
Sent from my PH-1 using Tapatalk

Thanks very much for the positive reports.

I had issues getting AA to work with my Essential phone, what solved the issue for me was disabling USB debugging. After that it worked like a champ.

elkay said:
It works great with my modded Infotainment center in my 2016 Miata. However, it will not stay connected to my aftermarket 2016 Kenwood head unit in my other car more than 1-2 seconds constantly connecting and disconnecting. I've tried half a dozen different cables. Works fine with my Nexus 6.
Click to expand...
Click to collapse
Exact same. My old Nexus 6 works fine but the Essential will not work with my Kenwood DDX9903. Currently I'm using my Nexus and tethering but due to Android Auto's (stupid imo) handling of calls through BT instead of USB, I can't accept calls over BT with the Essential while the N6 is in Android Auto mode.
dwj said:
This was what I had heard of in the forums and gives me pause about purchasing. May I ask if you have tried with latest firmware which Essential says contains some bug fixes?
Thanks to the others with positive experiences. More encouraging!
Click to expand...
Click to collapse
I'm all up to date and it still will connect and disconnect rapidly until my head unit restarts. It literally worked ONCE on the first night I got it. On my drive back home and up til now I only get the USB access error message.

Charlie_Don't_Surf said:
Exact same. My old Nexus 6 works fine but the Essential will not work with my Kenwood DDX9903. Currently I'm using my Nexus and tethering but due to Android Auto's (stupid imo) handling of calls through BT instead of USB, I can't accept calls over BT with the Essential while the N6 is in Android Auto mode.
I'm all up to date and it still will connect and disconnect rapidly until my head unit restarts. It literally worked ONCE on the first night I got it. On my drive back home and up til now I only get the USB access error message.
Click to expand...
Click to collapse
And same haha.. I'm using my Nexus 6 with hotspot thru my Essential for connectivity. And also same issue regarding calls. I was pondering cuttingthe proprietary USB cable and soldering it really close to the connector itself, thinking maybe if I get that cable as short as possible and then use a USB-C cable *just* long enough to reach the phone in front of the unit, maybe that will give the signal just enough boost to not keep failing repeatedly.

elkay said:
And same haha.. I'm using my Nexus 6 with hotspot thru my Essential for connectivity. And also same issue regarding calls. I was pondering cuttingthe proprietary USB cable and soldering it really close to the connector itself, thinking maybe if I get that cable as short as possible and then use a USB-C cable *just* long enough to reach the phone in front of the unit, maybe that will give the signal just enough boost to not keep failing repeatedly.
Click to expand...
Click to collapse
I swear I thought about doing the same thing but I think it might be a USB C issue in general. I have to test it with my mom's Nexus 5X. Worst case scenario I'll end up buying a replacement cable, cannibalizing the connector, and running a ~3ft USB C cable connected directly to the kenwood connector. That should tell me for sure if it's a cable quality/length issue. If I remember correctly, the cable from Kenwood is at least 2 ft. just by itself.
If you find any solution let me know because I have almost an hour commute and Waze's police alerts helps me big time.

My Prius was hellbent on grabbing my wife's iPhone instead of my SGS5 and the same thing happens with the Essential Phone. It always grabs her phone over mine. Otherwise, works fine.

elkay said:
And same haha.. I'm using my Nexus 6 with hotspot thru my Essential for connectivity. And also same issue regarding calls. I was pondering cuttingthe proprietary USB cable and soldering it really close to the connector itself, thinking maybe if I get that cable as short as possible and then use a USB-C cable *just* long enough to reach the phone in front of the unit, maybe that will give the signal just enough boost to not keep failing repeatedly.
Click to expand...
Click to collapse
I had it working tonight. I used a SUPER SHORT USB 2.0 Cable that came with my Anker PowerCore battery, then a samsung microusb to USB C connector.
It's so weird but I think going with the shortest cable possible, including the head unit cable might be a fix.

That sounds like a problem specific to Kenwood receivers then.
I've used my Essential with Android auto in four different cars with three different cables and I've never seen it disconnect once on any of them. But those were all Factory radios.
Sent from my PH-1 using Tapatalk

I just switched from an Xperia X and the PH-1 is significantly slower on AA. It works, but it's a slog.
This is on a 2017 Silverado

Just bought a 2017 Audi S3 and AA has been working flawlessly since day 1.

Weird, no slowdown or speed issues on AA in any of the 4 cars I've used it in. Guess I'm lucky. As long as it works in my Audi (and it does), I'm happy.
Sent from my PH-1 using Tapatalk

U11 and android auto issues w Kenwood 7704S HU

HI Guys,
Looking for some help. I have an HTC U11 on Oreo. Recently installed a Kenwood 7704S Android Auto HU.
Installed Android Auto app via google play, as well as latest version direct from Google. Phone is just not detected using the original USB C cable BUT the phone is charging, all other functions work via the Android Auto app without being cable connected. Short of installing older AA apk versions I am at a loss. I have tested unit with a iphone and Apple Car Play launches fine so it is not a a HU issue as I assumed. I had used this unit with a P10 Plus and it worked but I had intermittent issue with it as well but with the U11 it has just quit launching all together. I have reset phone to factory and tried fresh, no success. I have enabled Developer mode and enable USB debugging and selected MTP Protocol still no luck. I thought perhaps Nova Launcher may have been the culprit but not the issue once reverting to Sense as launcher. I have enabled AA permissions so thats set up correct.
Anyone experience U11 Android auto issues, super frustrating and don't want to run a custom rom just yet or possibly sell phone and find a working Android phone, last OP3 worked with previous Sony XAV-AX100 but I sold that unit wanting an extra USB port. Suggestions welcome cause I am at wits end beside trying other AA versions from earlier dates or rolling back to Nougat, that I have not yet tried. Phone has worked on Oreo and I got it with Oreo but I was experience intermitent connectivity. I can't see it being the USB C port but I did test the unit at the audio store where I bought my 7704S on their demo 9904S and same issue the phone charged but would not launch AA on the HU so it seems to be a hardware/software issue with the U11 itself

I don't have a Kenwood head unit but I have a pioneer NEX-4100 with Android Auto & Apple Carplay.
I just went out to the garage hooked up my wife's (I don't have one) HTC U11 (64GB USA Version) and successfully configured & established an Android Auto connection to the head unit. Ran through the menus and it functioned properly.
I used the USB C cable that came with my LeeCo S3 phone and it worked with the HTC U11. I did not try to use the HTC U11 cable as I don't know where the ball and chain keeps it. But I know cable(s) and Android Auto make a difference.
The U11 was on the latest Oreo 8.0 stock rom and is not rooted.
Hope that helps....
Also, on my Pioneer head unit, I have to specifically enable either Apple or Android Auto in the menu. So if it's not setup to use AA then it won't work until I enable it. This is only done once or until you need to use the Carplay side. Additionally, There are two USB connectors on my head unit with one connector specific to the iPhone and the other specific to the AA phone.

Endosmok said:
I don't have a Kenwood head unit but I have a pioneer NEX-4100 with Android Auto & Apple Carplay.
I just went out to the garage hooked up my wife's (I don't have one) HTC U11 (64GB USA Version) and successfully configured & established an Android Auto connection to the head unit. Ran through the menus and it functioned properly.
I used the USB C cable that came with my LeeCo S3 phone and it worked with the HTC U11. I did not try to use the HTC U11 cable as I don't know where the ball and chain keeps it. But I know cable(s) and Android Auto make a difference.
The U11 was on the latest Oreo 8.0 stock rom and is not rooted.
Hope that helps....
Also, on my Pioneer head unit, I have to specifically enable either Apple or Android Auto in the menu. So if it's not setup to use AA then it won't work until I enable it. This is only done once or until you need to use the Carplay side. Additionally, There are two USB connectors on my head unit with one connector specific to the iPhone and the other specific to the AA phone.
Click to expand...
Click to collapse
Thanks for your reply and taking the time to test your wifes HTC u11 on your Pio system. I am stumped still with no luck, with the Kenwood there is no selecting either the AA or Car Play in menu system will just launch automatically upon connection of device. The oddest thing is when I tested my sons 7 Plus it worked flawlessly but following I tried with my HTC U11 using the factory cable and no success. I plan to buy a better USB C cable and give it one last try because I am stumped and frustrated. Mine is USA version as well 64GB. Everything works as it should aside from the system being able to detect the phone and yet the deck rapid charges the device through either USB connection.
I tried another USB C cable and this one gives "an access error of the USB device has occurred" What makes this story even odder is my phone is not detected by my pc either so I am really starting to question if there is an issue with the USB C port, it charges fine but from my understanding data flows via different contacts within the port. This is the only sensible reason at this point. At this point as much as I like the U11 I am considering an alternative Android phone. When i looked up this access error there are lots of people with the issue and Kenwood decks as well as others... Seems it can be a hit or miss with this newest connection
https://productforums.google.com/forum/#!topic/android-auto/az_IM9QyzI4

cisco kidd said:
Thanks for your reply and taking the time to test your wifes HTC u11 on your Pio system. I am stumped still with no luck, with the Kenwood there is no selecting either the AA or Car Play in menu system will just launch automatically upon connection of device. The oddest thing is when I tested my sons 7 Plus it worked flawlessly but following I tried with my HTC U11 using the factory cable and no success. I plan to buy a better USB C cable and give it one last try because I am stumped and frustrated. Mine is USA version as well 64GB. Everything works as it should aside from the system being able to detect the phone and yet the deck rapid charges the device through either USB connection.
I tried another USB C cable and this one gives "an access error of the USB device has occurred" What makes this story even odder is my phone is not detected by my pc either so I am really starting to question if there is an issue with the USB C port, it charges fine but from my understanding data flows via different contacts within the port. This is the only sensible reason at this point. At this point as much as I like the U11 I am considering an alternative Android phone. When i looked up this access error there are lots of people with the issue and Kenwood decks as well as others... Seems it can be a hit or miss with this newest connection
Click to expand...
Click to collapse
I have been fighting cables and Android Auto for a long time now and finally found my problem which is so dumb to be almost unbelievable. Had a friend suggest this and it was the problem. I keep my phone in my pocket. It picks up lint in the USB C connector. And slowly over time. I took a toothpick and cleaned out the connector. It gets packed in, so takes a while to completely clean it out. I was shocked how much came out. After doing this, all my USB errors disappeared and problems with various cables disappeared as well. Duh, the common denominator was always the phone, not the cable. But it was curious that some cables seemed to work better than others. I feel so dumb, I actually returned this model phone in the first year under warranty because it finally stopped charging by cable. Got another phone and a wireless charger, but my second phone started acting up again and finally just refused to work a few months ago with Android Auto. Now everything is working great again.
I have LG G6 and Kenwood 7704 HU.
Chris

I'm having the same problem.
I have a pioneer 4200 nex, and can't connect to android auto. Worked perfect with previous m9, but since I bought U11, nada.
I'd be curious to see if anyone can help figure this one out. I drive a lot for work so it was nice seeing Maps on the screen.

Check the Kenwood website and see if there's a mention of unit having problems with type C connectivity.
pioneerelectronics.com/PUSA/Car/NEX/Android+Auto+not+working+for+newer+USB+Type-C+phones+(including+Pixel
While researching about me pioneer HU, this is what I found out. I suppose you can use the recommended cables as listed in the pioneer website as it sounds more of a cable problem than anything else.
I will post more once my new type A cable comes in. Sux I gotta go back in the dash to plug it in though. I still have my OEM type C so that should work.

Pixel 3XL won't connect to Android auto

As the title says all the phone does is makes the charging noise constantly. Won't charge nor load Android auto, my Bluetooth and everything is connected. I plug my old s8 in to headunit and bam works straight away. Anyone else having similar issue?
Can provide a video
Headunit is pioneer avh-z5000 and is up to date
TIA

Have you tried a different USB C cable? I (and others) had issues with Android Auto when Pie first rolled out for the Pixel 2/XL on the first one or two beta/dev releases, but it's been fine since on the Pixel 2 and 3 XL.

fury683 said:
Have you tried a different USB C cable? I (and others) had issues with Android Auto when Pie first rolled out for the Pixel 2/XL on the first one or two beta/dev releases, but it's been fine since on the Pixel 2 and 3 XL.
Click to expand...
Click to collapse
Yeah I've tried my old s8 cable and 2 other cables I have and still have issues. Going to try on a friend's car who has factory headunit and see if it does the same issue. Thing I do get is it just keeps reconnecting and doesn't get a solid connection

Have you tried changing usb connection modes? I think I may have had to do that at first...

arodey said:
Have you tried changing usb connection modes? I think I may have had to do that at first...
Click to expand...
Click to collapse
If your meaning USB debugging then yes I have enabled it.

Took a video of what is happening. Please someone help it is annoying me.

juice91 said:
If your meaning USB debugging then yes I have enabled it.
Click to expand...
Click to collapse
No I meant these options...

arodey said:
No I meant these options...
Click to expand...
Click to collapse
What should I be setting them too?

juice91 said:
What should I be setting them too?
Click to expand...
Click to collapse
I think you want This device and File Transfer

Mine do connect.. For a minute or so..and don't want to connect back until a restart the car.
I use the same cable as I used with my old Nexus 6p which was always fine

arodey said:
I think you want This device and File Transfer
Click to expand...
Click to collapse
My head unit won't even let me select as it's giving a solid connection

I am having the exact same problem. I just upgraded from a Pixel 2 to a Pixel 3XL. The Pixel 2 runs on Pie and connects just fine to the Pioneer AVH-2440NEX head unit. Pixel 3XL is running Pie as well and will not connect. The battery toggles back and forth from charging to not charging just like in the video that juice91 posted. I have put the phone into developer mode and chosen "File Transfer" and USB debugging" which did not change the problem. I updated the Pioneer head unit Firmware to v8.09, still no change. I don't know what to change next. Very Frustrated.

Solution
After battling this issue for 2 days, I finally figured it out. It's the stupid Bluetooth connection. The battery is toggling because the phone and the head unit keep bouncing back and forth trying to connect via cable then Bluetooth. The solution is very simple. Start the car, don't plug in your phone. Go to Bluetooth settings in the head unit and forget all the devices. Then plug your phone in. Android auto should pop right up and you are now connected.

Android auto keeps crashing after a few seconds

So I was all excited to get a pixel so i can use wireless Android auto, yes my stereo is compatible.
The problem is I can't even get it to work via USB cable. After a few seconds it keeps crashing and restarting. I've never had any issues with other phones and cables.
Any tricks or suggestions.

mpetruzz said:
So I was all excited to get a pixel so i can use wireless Android auto, yes my stereo is compatible.
The problem is I can't even get it to work via USB cable. After a few seconds it keeps crashing and restarting. I've never had any issues with other phones and cables.
Any tricks or suggestions.
Click to expand...
Click to collapse
Try another cable, it worked for me.

fiveplustwo1 said:
Try another cable, it worked for me.
Click to expand...
Click to collapse
Yep, I second this. I did a new head unit installation a year ago and was trying to install a nice USB flush mount cable to use with it. It was somehow causing problems and my phone connected to the head unit, the head unit saw it, but ultimately Android Auto didn't work and seemed like my phone was the problem. I removed the flush mount and just plugged in directly to the head unit and all was well. Try cables which are different brands.

Phone power issues AA not working

Hello everyone.
So I have a few issues which I am guessing are all somewhat related.
TL;DR
1) Android auto stopped working
2) if I reboot. It will just power off and needs to be plugged in to power back on
3) usb c to usb c only works one side not both sides. But usb a to usb c works both directions.
Note: my wife has the same phone and had none of these issues with the same cables and such. So it's not cables issues. We also have the same OS.
The longer detailed version.
First issue. Android auto stopped working. At first it told me that there may be an issue with the cable and that I should get another cable. I tried my wife's pixel 3 xl and it worked fine. So it's not the cable issue. I tried restarting. The phone did not. So I plugged it in and it powered on. Now the phone will only boot if it is plugged in. Plugging the phone into the car usb a to usb c it charges on both side of the cable but there's no longer any warning about the cable for Android auto. Again my wife's phone works with the same setup so it's an issue with my phone. Then when plugging my phone in using the oem cable I noticed it only chargers using one side. The other side fails. Tested my wife's phone and both sides work. I then test my wife's cable and same issue with her cable for my phone.
Pixel 3 XL
OS 11 RQ1A.210105.003
I did a factory reset but same issues remain.
I'm open to using a ROM if it will fix the issue.
I saw a few posts on google forums about this issue but not fix/solution so I was kind of wondering if a ROM would possibly fix this issue.
Thanks so much for any help.
Willing to try most items as phone is out of warranty and I really like Android auto and hate not having it.