I am using my Nexus 5X with Android Auto (on a 2016 VW Golf) and I am finding that the initial connection between the phone and the vehicle is unreliable. I am using a Google OEM USB C to USB A cable and of course I have Android Auto app installed. Sometimes the vehicle finds and connects automatically and more often it tries to connect and fails. When it initially fails I disconnect the cable from the phone, wait a minute and reconnect. Sometimes it works, sometimes it requires a third or fourth reconnection. Occasionally (!) I will get a notification on the phone that USB is connected to a power source and I have switched to USB as PTP.
It's all a bit random and I haven't done a good job yet on weeding out what works and what doesn't. I have wondered whether it is to do with Marshmallow and permissions, but I have granted Android Auto pretty much every permission in the book and it is still fussy.
Anyone else with Android Auto found this? Any advice on how to get a consistent experience?
I haven't been able to get Android Auto working at all on my 2016 GTI, though I haven't tried with Google's USB C to USB A cable.
I was bummed because it worked most of the time with my LG G3.
Related
Hello everyone,
has anyone else run into the issue that if you connect your pixel xl via usb to a computer that your connection of a wireless mouse or keyboard is disrupted?
Every time I plug it in, it is nearly impossible to write something (lost key types and delays) and the mouse also reacts very delayed from time to time. It also happens when I set my pixel to airplane mode. When I unplug it, everything works fine again.
Do you have the same issue? Or do you have a suggestion what it can be?
PS:
this computer is a dell xps 27 with dell's wireless keyboard and mouse, running windows 10
I had the Nexus 6P (with Android 7) and plugging it into the USB worked with my 2011 Camaro (it is not Android Auto, the Head-unit basically will see the phone as a USB Storage device, mount it, index the files, and I could then use my car's controls to search, change tracks, etc).
I broke my phone and turn it in on warranty, and end up getting the Pixel XL as replacement, and upgrade it to Android 8.
Now when I plug it into my car, I get a "No supported media found" message on my car's display. I have tried with and without USB Debugging, going into the the developer options and changing the "Select USB Configuration" to MTP, Audio Source and still the same. I would also have this issue with Samsung phones, and could never get them to work.
I am not sure if this is an issue with Pixel's, or with the Android 8 update, since my Nexus 6P with Android 7 worked fine
you need to use the otg adapter that came with it
So I have to get a standard USB-USB cable to connect the adapter to my car?
I thought this adapter added functionality, so my phone can mount drives, not the other way around? Doesn't make since that something that has worked so well on the past 3 phones (except for Samsung for whatever reason) now no longer works without another piece of hardware. Not what I would call progress
So I ordered another cable and am using my OTG adapter, and it still does not work.
I have a brand new 2017 Ford Raptor with Sync 3, version 3.0. I can easily connect my Samsung Note8 to it via Android Auto and it sees it immediately, connects just fine. If I unplug that device from the two USB connections, I try to connect another Android 7.0 Nougat device that is WiFi only to it, using a OBDII WiFi hotspot attached, and it connects to the internet just fine, but will not connect to the truck via Android Auto. The device is a DOOGEE BL5000, a Chinese Android device that does not have any US LTE bands, and I wanted to use a hotspot in the car to connect other devices to it on long trips anyways, so I paid $145 for an Android phone that I would use only with WiFi.
I've connected it with Bluetooth, done all the setup, and the screen shows BL5000 detected when plugging in, but absolutely will not connect to have THAT device use the Android Auto instead of my phone. My goal is to disable AA on the Note8 and have the BL5000 dedicated to AA duty while in the truck. I have tried FIVE different USB cables, two of which were factory Samsung cables, so they aren't the cheap ones, tried unplugging, plugging in, changing which USB connection type (charging / file transfer, PTP, etc), and nothing changes. The Note8 it set to just charging, so I can't imagine the setting is that important when it connects instantly. I have done a master reset on the Sync 3, had to start all over again with connections, trying the BL5000 again first without setting up the Note8, turning the truck on and off multiple times, it just won't connect.
It was said that Huawei devices for some reason won't connect to AA, don't know why or what the logic is behind that, but am I screwed with this DOOGEE BL5000? I wanted something with at least 4GB of RAM and wiping / disabling everything else but AA, Maps, Music off of it in order for it to work solely as a processor for AA that I can remove and replace, but this is becoming a headache all in and of itself.
Any thoughts or suggestions? Thanks in advance!
Hello
I'm in the UK experiencing the same problem with my new Doogee and Sync 3.
Did you get any where with this issue please
Thank you
Richard
rwalton159 said:
Hello
I'm in the UK experiencing the same problem with my new Doogee and Sync 3.
Did you get any where with this issue please
Thank you
Richard
Click to expand...
Click to collapse
Yes and no. The Doogee would never connect, so I was refunded the purchase on PayPal because this was all I needed the device for, the seller did not respond so I got to keep the device. I since purchased a Moto G4 unlocked and it connects perfectly, immediately, and put a SIM card in it to run directly from the device instead of through WiFi only, makes Android Auto boot time much faster this way. Hope that helps!
Thanks for your very prompt reply. Glad you managed to get a solution in the end.
I previously tried a Cubot Cheetah 2 with my car to no avail. What's interesting is that my old Samsung J5 works with AA. You'd think a phone with android 7.0 would work.
Thank you again
Richard
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 instalkling 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.
Anyone experience U11 Android auto issues, super frustrating and dont want to run a custom rom just yet. 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
Greetings. I have a T-Mobile G7 and 2017 Honda Pilot.
Connecting to Android Auto is very flakey. No matter what when I plug in the phone to the car a message shows up on the car display that says "unknown device." Still, sometimes the connection works and sometimes it doesn't. Clearing cache does not seem to help.
I have tried using different cables with no improvement. The connection works fine with other phones.