Has anyone been able to connect wirelessly to the Android Auto in their car? I have a Honda CR-V 2017 and it connects with the USB cable, but not wirelessly. I have tried all settings multiple times but cannot figure out why it won't connect. I was under the impression that Pixel 3 XL phones had this capability. Can anyone share if they have it working, particularly on a Honda CR-V 2017. If so can you share your settings?
Sent from my Pixel 3 XL using XDA-Developers Legacy app
I have a 2018 crv and 2018 accord and I didn't think that could be done. I connect with usb on both.
Eudeferrer said:
Has anyone been able to connect wirelessly to the Android Auto in their car? I have a Honda CR-V 2017 and it connects with the USB cable, but not wirelessly. I have tried all settings multiple times but cannot figure out why it won't connect. I was under the impression that Pixel 3 XL phones had this capability. Can anyone share if they have it working, particularly on a Honda CR-V 2017. If so can you share your settings?
Sent from my Pixel 3 XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Sent from my Pixel 3 XL using Tapatalk
The wireless connection is a car feature not a phone feature. Very few makes support at the moment
micks_address said:
The wireless connection is a car feature not a phone feature. Very few makes support at the moment
Click to expand...
Click to collapse
I guess I thought most new cars which have Android Auto would be able to connect wirelessly. I thought it depended on the phone model instead.
Sent from my Pixel 3 XL using XDA-Developers Legacy app
Eudeferrer said:
I guess I thought most new cars which have Android Auto would be able to connect wirelessly. I thought it depended on the phone model instead.
Sent from my Pixel 3 XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
It depends on both, really. The phone and car both have to support it. Phones (like the Pixel 3/XL) have the ability now, but very few head units (especially OEM from car manufacturers) support it. A few aftermarket units are starting to get it, but it's still very few.
I bought a Kenwood HU that has wireless AA and to be honest I'm disappointed. It works half the time and usually I end up just plugging it in cause it's quicker than messing around with my phone trying to get it too work
I have a pioneer 4400nex and wifi Android auto works flawlessly. Love it.
MoeDaddy said:
I have a pioneer 4400nex and wifi Android auto works flawlessly. Love it.
Click to expand...
Click to collapse
I have the 8400nex and it works well too and I used the cars speed signal to control the volume and the screen works well. The Kenwood screen was not sensitive enough and had dust under the screen and had trouble connecting but it did auto switch between the front and back camera when backing up and then driving forward. Not a big deal but cool. Both the new ones got rid of the camera mirroring and backup lines that the pervious units had. Can't win but overall the Pioneer is better.
Related
Hey all I've had my 360 for a few months now and just started noticing a problem. When I have my watch connected to my phone my phone has a hard time connecting to my Chrysler Uconnect in my stereo. I can't tell if it's a phone problem, Uconnect problem or the watch. It'll drop connection from the car on and off and sometimes not connect at all. I'm pretty sure the watch stays connected the whole time. Once I disconnect the watch, the car connection works just fine.
Anyone else run across this?
These issues are seen with lollipop on phone....
or some people whose phone is moto x or one plus one
Sent from my SM-N910C using Tapatalk 2
It's a Bluetooth low energy issue. Same exact problems with my nexus 5 and my pebble, also exists with my nexus 6 and moto 360. It's very very annoying as it appears to be an issue with android itself somehow. I'm hoping with more Google engineers using wear and a nexus they'll get annoyed and finally fix it...
Sent from my Nexus 6 using XDA Free mobile app
i have no such issues with pairing a nexus 6 connected to a moto 360 in the ride.
i mainly use poweramp and the connection to the HU is a few seconds SLOWER than i noticed on the htc one max i used prior, but it connects and displays the music data on the ride with no issue. steering wheel buttons also work normally.
stock and not rooted. both devices.
It seems to be select car kid or a2dp devices. My car has the issue but not my Bluetooth speaker. So the Bluetooth device also matters somehow
Sent from my Nexus 6 using XDA Free mobile app
Never had the issue on my Samsung Galaxy note 2 even on any custom ROM... But had this issue when I flashed CM12 lollipop
Sent from my SM-N910C using Tapatalk 2
pakure said:
Never had the issue on my Samsung Galaxy note 2 even on any custom ROM... But had this issue when I flashed CM12 lollipop
Sent from my SM-N910C using Tapatalk 2
Click to expand...
Click to collapse
Were the other Roms aosp or TW? Maybe it's an aosp specific issue
Sent from my Nexus 6 using XDA Free mobile app
Just got a Moto 360 this week-end and in the car on the way home, my phone calls over bt to my BMW dropped repeatedly. Would connect and disconnect. Rebooted my phone, same issue. Did not happen with original galaxy gear. This is a deal breaker from me. My phone is a stock Samsung Note 4. No car phone issues with a Striiv Touch.
mjposner said:
Just got a Moto 360 this week-end and in the car on the way home, my phone calls over bt to my BMW dropped repeatedly. Would connect and disconnect. Rebooted my phone, same issue. Did not happen with original galaxy gear. This is a deal breaker from me. My phone is a stock Samsung Note 4. No car phone issues with a Striiv Touch.
Click to expand...
Click to collapse
Unpair them and pair again.
Sent from my SM-N910C using Tapatalk 2
I have an older TomTom Toyota Head-Unit on my Toyota Yaris, and it doesn't support Bluetooth Audio. But bluetooth phonecalls are working exactly as before pairing the Moto 360 to my HTC One.
I just disconnect my watch when I get in the car. Annoying that I have to do that.
Anyone had any luck or tried their new Oneplus 3 with Android Auto yet? I have been unable to get mine to connect with the factory USB type C cable on my Pioneer AVH-4100NEX. My Oneplus One running Sultans CAF 13.0 ROM runs no problem. This could be enough to make me return this new OnePlus 3 honestly. I really rely and love Android Auto.
unlock bootload and flash cm13, since sultans rom runs off of CM13 and see if that works
Sultan has not made a ROM for Oneplus 3, or else I would definitely do that. I am watching the threads with other CM 13 authors but seems a little too early to jump in on any of those.
OK I have tried Resurrection Remix Official which is a CM based ROM, still no luck (Very nice ROM with a ton of features BTW) Have some Type C cables and adapters on the way from Amazon, maybe it is the factory cable?? If anyone has had success or issues would love to hear from you, I can't be the only one
Come on guys, Android Auto is a must these days....how can we make it work ?
Glad I saw this thread before I bought. If Android Auto will not work on it then I'll gonna pass on it. Hope they get it working in time as I do want this phone.
I did have similar issues with ROM's when I first got my AVH-4100NEX and my Oneplus One, luckily I just kept trying a few different ROM's until one worked. Never figured out what the issue was but now most I have tried have worked with the One. Just being so new there are only so many to try with the Oneplus 3 at this point.
I have contacted Oneplus about it, they don't even know what I am talking about, they just keep replying that they can't guarantee the phone to work with all bluetooth devices. I have told them twice now it is not the Bluetooth, in fact my Bluetooth has been fine. It is only when the cable is plugged in. I have made some progress on the latest ROM I have tried, it now says Android Auto is connected on the phone, notification, BUT...it isn't because I do not get the 2nd notification I am used to saying the phone is in car mode AND the Android Auto button on the head unit is not lighting up.
Tried multiple cables now, and known working micro USB cables with type C adapters now. Same results. It's either the phone or the ROM. Next thing I am going to try is a different version if GAPPS specifically play services, since everything uses it it would appear.
I was able to get my OnePlus 3 connected to my Seat Leon with Android Auto a few times after I plugged it in and out dozens of times, did some restarts of the OPO3 and the media unit, plus some tinkering with the USB MTP and notification access settings. But it was never stable, longest lasting connection was about 15 minutes long, than it crashed again. The overall success rate for connecting is about 1 of 10 times. So altogether not usable...
The question is on the official 1+ forums also and they are ignoring it.
I'm guessing there will be no AA support.
Oh well, The Axon 7 is being released soon and hopefully it will work there.
Lythandra said:
The question is on the official 1+ forums also and they are ignoring it.
I'm guessing there will be no AA support.
Oh well, The Axon 7 is being released soon and hopefully it will work there.
Click to expand...
Click to collapse
See here some updates.
http://forum.xda-developers.com/oneplus-3/help/android-auto-issues-t3406352/page2
My OnePlus 3 is stock and it's working flawlessly with Android auto.
Sent from my ONEPLUS A3000 using Tapatalk
I tried it on my golf 7 and it was working fine then a couple minutes later it started freaking out. Kept connecting and disconnecting in a loop. Seemed like an issue android auto had when I first got the car with my Nexus 6 but was eventually fixed with an update to AA.
Sent from my ONEPLUS A3000 using Tapatalk
riotburn said:
I tried it on my golf 7 and it was working fine then a couple minutes later it started freaking out. Kept connecting and disconnecting in a loop. Seemed like an issue android auto had when I first got the car with my Nexus 6 but was eventually fixed with an update to AA.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Mines working great on my mk7R. Did u enable USB debugging in developer options?
Sent from my ONEPLUS A3000 using Tapatalk
robstunner said:
Mines working great on my mk7R. Did u enable USB debugging in developer options?
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Forgot to mention that I was using it with a micro USB cable with an adapter on it. Also I should try it again because a lot of things seem to have some issues on first use with this phone. If not I'll try one plus cable.
Sent from my ONEPLUS A3000 using Tapatalk
riotburn said:
Forgot to mention that I was using it with a micro USB cable with an adapter on it. Also I should try it again because a lot of things seem to have some issues on first use with this phone. If not I'll try one plus cable.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
I'm using the original cable and had no issues.
Sent from my ONEPLUS A3000 using Tapatalk
robstunner said:
I'm using the original cable and had no issues.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
I tried today with the original cable. I just plugged it in and connected to android auto. I didn't play music or us maps. After about 10mins it just freaked out and disconnected.
Sent from my ONEPLUS A3000 using Tapatalk
riotburn said:
I tried today with the original cable. I just plugged it in and connected to android auto. I didn't play music or us maps. After about 10mins it just freaked out and disconnected.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
So with an adapter, it didn't do this? Only when you used the original cable?
blacknet101 said:
So with an adapter, it didn't do this? Only when you used the original cable?
Click to expand...
Click to collapse
It did it with both.
Sent from my ONEPLUS A3000 using Tapatalk
Work around accord 2016
I had a tough time getting Android Auto working with my Honda accord 2016. All other phones worked fine except the op3.
Finally was able to get it to work. Here is what i did:
1. Enable developers options
2. Connect the phone to the car while the car is on
3. Go to developers options and under "select USB configuration" pick "MIDI"
Then Android Auto connects to the car. It is really disappointing to see the bugginess of the phone. I really like the hardware. But the software is s**t. If I wasn't past the return date I would have gotten a different phone. Oh well at least I got it to work for now. Hopefully op will release an update to fix the glitches.
Had connected to support and asked them about Android Auto support before i figured out the work around. They flatly stated that Android Auto is not a supported feature. Support was supposed to be added in "a few weeks". Don't know how long weeks are in OP land
Cheers and hope this helps someone
Ah you used midi? I tried mtp but that didn't work. The latest release fixed the issue of it not saving the selected USB mode. It always reverted to charging
Sent from my ONEPLUS A3000 using Tapatalk
Well, never knew that Google was having issues with Bluetooth. My pixel xl was fine. Just got the 2 xl and here is what happens : I can pair my LG hbs-760 headphones but they don't connect. Shows them in the Bluetooth devices but that's as far as I can go. Same with my Bluetooth Panasonic headsets we have in the house. Will pair but will not connect. My pioneer car stereo will not connect either. Shows it paired and that's it.
Now I do have 2 devices which seem to be fine. I have Jaybird bluebuds x and a garmin approach x40. Both pair and connect.
Searching, but not finding any solutions except to wait for the November or December updates... My pixel 2 xl is still on the September update.
Any ideas?
Sent from my Pixel 2 XL using Tapatalk
Have paired to 4 devices without any issues
No issues with pairing here either.
Recently I just read an article from Lifehacker about Bluetooth issues. Maybe it will help you: How to Fix Bluetooth Audio Stuttering
If the issue is still there, you should contact with support asking for a replacement.
TBarb169 said:
Well, never knew that Google was having issues with Bluetooth. My pixel xl was fine. Just got the 2 xl and here is what happens : I can pair my LG hbs-760 headphones but they don't connect. Shows them in the Bluetooth devices but that's as far as I can go. Same with my Bluetooth Panasonic headsets we have in the house. Will pair but will not connect. My pioneer car stereo will not connect either. Shows it paired and that's it.
Now I do have 2 devices which seem to be fine. I have Jaybird bluebuds x and a garmin approach x40. Both pair and connect.
Searching, but not finding any solutions except to wait for the November or December updates... My pixel 2 xl is still on the September update.
Any ideas?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I've had a few issues with connecting my 2XL. Pairing went find, but then wouldn't connect. I did a restart on the phone and all was well. This happened with a bluetooth speaker and then in my car (accord).
ame29 said:
I've had a few issues with connecting my 2XL. Pairing went find, but then wouldn't connect. I did a restart on the phone and all was well. This happened with a bluetooth speaker and then in my car (accord).
Click to expand...
Click to collapse
Well that worked! I feel ashamed that I didn't try rebooting...
Sent from my Pixel 2 XL using Tapatalk
TBarb169 said:
Well, never knew that Google was having issues with Bluetooth. My pixel xl was fine. Just got the 2 xl and here is what happens : I can pair my LG hbs-760 headphones but they don't connect. Shows them in the Bluetooth devices but that's as far as I can go. Same with my Bluetooth Panasonic headsets we have in the house. Will pair but will not connect. My pioneer car stereo will not connect either. Shows it paired and that's it.
Now I do have 2 devices which seem to be fine. I have Jaybird bluebuds x and a garmin approach x40. Both pair and connect.
Searching, but not finding any solutions except to wait for the November or December updates... My pixel 2 xl is still on the September update.
Any ideas?
Click to expand...
Click to collapse
This thread is a joke no problems here
evocalante said:
This thread is a joke no problems here
Click to expand...
Click to collapse
Thanks Captain Obvious! Please move along and troll some where else.
Sent from my Pixel 2 XL using Tapatalk
I've had Bluetooth issues with only one of my cars. The phone pairs, but then stutters on and off playing any audio. Eventually the bluetooth stack crashes. I had similar, though not exactly the same issues, with my Nexus 6p. Those were resolved by the October security update, which the Pixel XL 2 hasn't received yet. Hoping that resolves the problem again when it arrives.
Headphones/Truck have been fine for me but I have a gamegolf device which connects via bluetooth and every time I get a text or call while playing golf the gamegolf device disconnects. I'm still testing and don't know if it's a gamegolf issue or phone issue but it's annoying.
Just curious why Bluetooth on this phone doesn't display the streaming information across the radio (Uconnect if it matters). My sons s8+ does it as well as my previous Note 8. Just curious if theirs something I'm not doing right.
MHB1638 said:
Just curious why Bluetooth on this phone doesn't display the streaming information across the radio (Uconnect if it matters). My sons s8+ does it as well as my previous Note 8. Just curious if theirs something I'm not doing right.
Click to expand...
Click to collapse
I've got the same issue. Its not just you.
I'm connecting to a Honda bluetooth system, if that makes a difference.
After 8.1, it works better with my BMW at showing the data, but it's hit or miss. It also stops working if you switch music apps, so only the first one works.
Sent from my Pixel 2 XL using Tapatalk
It's because everyone implements Bluetooth items differently and there isn't a "standard" that everyone uses for even basic stuff. Since phone manufacturers implement things differently, device & car manufacturers also need to try and accommodate all the various implementations.
Sent from my Pixel 2 XL using Tapatalk
Well I'm still waiting on the Verizon OTA. But i definitely don't like the lack of info on the screen. I have the note sorting beside me... Test driving both... And send like such a simple thing.
imnuts said:
It's because everyone implements Bluetooth items differently and there isn't a "standard" that everyone uses for even basic stuff. Since phone manufacturers implement things differently, device & car manufacturers also need to try and accommodate all the various implementations.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Actually, for this kind of thing there is a standard called AVCRP, and the Pixel should support 1.4, but it seems to be the buggiest implementation ever since Android 7
Sent from my Pixel 2 XL using Tapatalk
I've noticed in developer options there are numerous settings for Bluetooth... Should i change these for display information?
MHB1638 said:
I've noticed in developer options there are numerous settings for Bluetooth... Should i change these for display information?
Click to expand...
Click to collapse
Try adjusting the AVRCP version.
Sent from my Pixel 2 XL using Tapatalk
I have the same issue connecting to a Honda. For what it's worth, it never worked with my 6P, either.
Devhux said:
Try adjusting the AVRCP version.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Nothing worked. Just don't understand this, everyone else does it, why can't Google!
Hi guys, i'm using my Note 10+ connect to my Honda CRV 2018 to use Android Auto, look like everything so slow, especialy transition effect between screens or app.
The Android Auto version is: 4.6.593324-release
Cable is USB A to C.
What's my problem? My phone or my car?
m_dht said:
Hi guys, i'm using my Note 10+ connect to my Honda CRV 2018 to use Android Auto, look like everything so slow, especialy transition effect between screens or app.
The Android Auto version is: 4.6.593324-release
Cable is USB A to C.
What's my problem? My phone or my car?
Click to expand...
Click to collapse
This may be on your car side because my head unit is just fine with with Android auto
Sent from my SM-N975U using Tapatalk
antawnm26 said:
This may be on your car side because my head unit is just fine with with Android auto
Sent from my SM-N975U using Tapatalk
Click to expand...
Click to collapse
Which car do you using? CRV 2018?
m_dht said:
Which car do you using? CRV 2018?
Click to expand...
Click to collapse
I'm using Kenwood DNX876S IN MY SILVERADO
Sent from my SM-N975U using Tapatalk
m_dht said:
Hi guys, i'm using my Note 10+ connect to my Honda CRV 2018 to use Android Auto, look like everything so slow, especialy transition effect between screens or app.
The Android Auto version is: 4.6.593324-release
Cable is USB A to C.
What's my problem? My phone or my car?
Click to expand...
Click to collapse
It's the car. I'm a technician at a honda dealership and honda head units are the slowest. It actually irritates me with how slow they are. Something as simple as resetting the oil life on the unit isn't a smooth experience. It's a common complaint with all our customers. Unfortunately there is no fix it's a hardware thing.
Loads up amazingly quick on my wife's car. 2019 Audi A6.