i got nex 4100 my galaxy 5 now i get red screen saying my phone not  compable  with  android  auto nice google or pioneer

   i got nex 4100 my galaxy 5 now i get red screen saying my phone not  compable  with  android  auto nice google or pioneer

I get that as well. Which carrier do you have?

I think the main culprit here is Samsung with an assist from the carrier. The Galaxy S5 has so much CRUD and variation between them that Google has not yet developed the workaround to get it working with Android Auto. They fixed it real quick with the S6. But other manufacturers, like LG for example, don't have their flagship phones already on Lollipop working with AA. I don't get why the G3 doesn't work.

Make sure you have usb debugging turned off!  i left mine on and android auto wouldnt connect.  i turned off usb debugging while it was pluggedd in, and it came right up one debugging was turned off

i have sprint guys   and debugging is on

i try uncheck  debugging when plug in  no luck  still get red screen saying s5 is not compable

The only way I was able to get my Sprint S5 to work with Android Auto was to flash a CM rom to the device. I'm running CM 12.1 which is Android 5.1.1 and everything is working great.

rbrown email me  on how you did this [email protected]  i have sprint i only have 5.0 ;lollipop 

Okay I got android auto to work......I opened up and looked at my wiring and realized that I actually did not ground my parking brake wire....

After I did it worked just fine with no warnings.....however it seems like I'm running into the issue that mostly everyone else is running into....I can't get voice controls to work at all.

I'm having the same issue. I am sure that the parking brake wire is grounded. Because I have the software bypass activated (I even shut it to SET OFF and tested a DVD just to make sure it was working). But Android Auto is trying to get me to "park" the car still to start the process.

Sorry for cross posting, but this thread seems to be getting a lot of replies. So I am hoping to get some help here.

I installed avic-8100-nex in my 07 ford expedition xlt using the  Metra XSVI-5520-NAV harness. I used a CCAUSB 2.0 (http://goo.gl/lu7FGQ)  pass through cable connected to port 2.   

I *do not* have any brake bypass, hardware or software, I have the parking wire connected to the light green wire on the metra harness. I upgraded firmware from 1.01 to 1.03. I have a nexus 5 that recently got the 5.1.1 OTA, I connected the nexus5 using the LG USB cable that came with the phone.

The HU recognized the phone, initiated the download of Android Auto and showed me the "accept" screen on the phone and then disconnected. I depressed the parking brake, head the break pedal down, unlocked the phone, and reconnected the phone. Android auto icon appears on the head unit, I when click on the icon or mode button I see the following message: "Android Auto cannot connect right now. When it is safe to do so, please check your Android phone."

I have tried couple of different USB cables, even connected the cable directly without a pass through. I also  uninstalled the android auto app several times and reconnected, and each time I get the same behavior. I have also tried connecting the parking brake wire to the electrical ground on the harness. One thing I have not tried is a different phone. 

Should I ground the parking brake to the vehicle chassis? Do you folks have better results getting Android Auto working that way?

Should I try a different USB cable? What cable do you recommend? 

Should I factory reset the phone? Or Head unit ? 

Any other suggestions ? 

Sorry for cross posting, but this thread seems to be getting a lot of replies. So I am hoping to get some help here.

 

I installed avic-8100-nex in my 07 ford expedition xlt using the  Metra XSVI-5520-NAV harness. I used a CCAUSB 2.0 (http://goo.gl/lu7FGQ)  pass through cable connected to port 2.   

 

I *do not* have any brake bypass, hardware or software, I have the parking wire connected to the light green wire on the metra harness. I upgraded firmware from 1.01 to 1.03. I have a nexus 5 that recently got the 5.1.1 OTA, I connected the nexus5 using the LG USB cable that came with the phone.

 

The HU recognized the phone, initiated the download of Android Auto and showed me the "accept" screen on the phone and then disconnected. I depressed the parking brake, head the break pedal down, unlocked the phone, and reconnected the phone. Android auto icon appears on the head unit, I when click on the icon or mode button I see the following message: "Android Auto cannot connect right now. When it is safe to do so, please check your Android phone."

 

I have tried couple of different USB cables, even connected the cable directly without a pass through. I also  uninstalled the android auto app several times and reconnected, and each time I get the same behavior. I have also tried connecting the parking brake wire to the electrical ground on the harness. One thing I have not tried is a different phone. 

 

Should I ground the parking brake to the vehicle chassis? Do you folks have better results getting Android Auto working that way?

Should I try a different USB cable? What cable do you recommend? 

Should I factory reset the phone? Or Head unit ? 

Any other suggestions ? 

I don't think a factory reset of the phone is necessary. I don't know what the heck happened with my set up, but all of a sudden the "parking" situation resolved itself and I was able to start the set up. Someone kicked around the idea on another forum that Android Auto doesn't even tap in to the head unit to figure out whether the car is parked. Which makes me wonder what is the trigger to keep it from locking you out of the app and connecting the phone. They need to scrap that ASAP.... all it does is cause problems.

Do Apple users have to deal with this with CarPlay?!

I contacted Pioneer customer/Tech support regarding this issue. I am told that  "Android Auto cannot connect right now. When it is safe to do so, please check your Android phone."  means that my phone is not supported. Tech support tells me that they get this same question all the time and they say it could mean one of the following 1) my provider (T-Moble) in my area does not support Android auto 2) My device is not supported by Android Auto. Which is crazy I think because I have a Nexus 5, google's flagship phone and Tmobile ("the uncarrier") and I am based on central Texas. I somehow can't believe pioneer tech-support's explanation.  

Is there anyone on this forum who got Android Auto working with Nexus 5, T-Mobile in the central Texas area? 

Well I recently installed the 8100NEX and had no issues getting Android Auto up and running on my GS6 but I am having an issue with the audio - google play music works but on the left side of the car, the audio crackles/pops/hisses/cuts in and out/etc.  I am wondering if anyone else has had this issue?

Bluetooth/radio/etc all works great.  Going to test a different USB cable and see where that gets me.

Frustrating...

Going to test a different USB cable and see where that gets me.

I would also recommend trying a different Android Auto compatible player app from the play store.

I would also recommend trying a different Android Auto compatible player app from the play store.

I tested both Spotify and Google Play Music on two different galaxy S6's - exact same result.

What's amusing is you can literally tap the side of the center stack next to the 8100 and get the cracking/pops/hisses to change/stop/etc.

Sounds like a bad solder joint or loose connector. 

I had encryption enabled, and I had 3 google accounts on my phone. I had to reformat and factory reset my phone to fix all the problems I was having. But was it worth it? after a few weeks of using Android Auto, I don't think so. The stock 8100 features are nice and works better than Android Auto, I like the stock navigation better than Google maps on Android Auto, the voice commands are a mess, also the BT works better on the stock phone app and people complain of static on the line when I use it with Android Auto. The only thing so far that I liked in Android Auto is Google Music. I know Android Auto in its current form is just a teaser, but they are giving their users such a horrible experience on launch, once you screw up on user experience ... you have lost them for ever... Although I am not an Apple user, I am sure apple CarPlay is not the POS that Android Auto is. 

1-The stock 8100 features are nice and works better than Android Auto,

2-I like the stock navigation better than Google maps on Android Auto.

3-The voice commands are a mess.

4-The BT works better on the stock phone app and people complain of static on the line when I use it with Android Auto.

1 - You cannot reply to a text via the stock 8100. I like that in Android Auto. Push the button on the HU to listen, then push it again to reply. No trying to fumble with phone while driving.

     A)Illegal very dangerous.

2 - I will have to agree with you on this.

3 - The voice commands have worked fine in AA so far, for me.

4 - The stock BT on the 8100 just plain sucks. People think I always have my windows rolled down when I'm talking. I have moved the mic to a few different locations.

the POS that Android Auto is. 

Hmmm... Here, Android Auto works exactly as intended. Folks say the audio quality on calls is near perfect. And the voice commands have been almost a hundred percent. Is it perfect? No... I have a number of little quibbles regarding interface issues, but everything it is supposed to do it does well.

I am going to go out on a limb and guess you have a phone from an OEM that has heavily modified Android.

Android Auto does suck for me. It freezes every 15 minutes. Useless.

During the short period of time it DOES work, it is very nice.

i have galaxy s4 on sprint running lolipop, had android auto come up once but then froze up ,tried everything from uninstalling aa and still no luck, what is cm 12.1 and  how do i get it on my phone ,

I spent a day trying to get my Samsung Note 4 to connect to my 4100nex, either android auto or mirrorlink, no dice.  Problem was the cable.  i had gone on ebay and bought an "aftermarket' CD-MU200 cable, which is just a 3ft usb extension and a 3ft microusb cable.  well long story short after pulling my hair out I swapped the microusb with one I had laying around and guess what, worked right away.  so not sure what the difference is but bottom line is try a different cable if you are having problems, may need larger gauge wire, shielding, who knows. 

I spent a day trying to get my Samsung Note 4 to connect to my 4100nex, either android auto or mirrorlink, no dice.  Problem was the cable.  i had gone on ebay and bought an "aftermarket' CD-MU200 cable, which is just a 3ft usb extension and a 3ft microusb cable.  well long story short after pulling my hair out I swapped the microusb with one I had laying around and guess what, worked right away.  so not sure what the difference is but bottom line is try a different cable if you are having problems, may need larger gauge wire, shielding, who knows. 

The cable you purchased might have just been a charging cable, regardless of what they advertised in the eBay auction.   You need a data/charge USB cable, which is what the second cable you used is.     Complain to eBay and get your money back for item not as described.

You need a data/charge USB cable

Add me to the list of users that cannot get Android Auto to launch {HTC One M9, by the way).  Weird part is that it did a couple of times, but has not since.  I'm going through all the iterations of things that have been changed trying to land back on the "magic" set that actually works.  I'm fairly sure every cable I own is the combo type, but I'm wondering how to confirm.  If I plug the USB cable into a desktop PC and it allows me to transfer files to & from the phone, that would pretty much guarantee it is the correct cable.  Is that assumption correct??  Also, I have all the smartphone settings correct for Android Auto mode in the head unit and USB is running to USB2 input . . . . . straight connection with none of the MHL adapters or anything like that.

Like others, I have literally spent a couple of hours tinkering with this silly thing, so I'm definitely open to ideas.  Thanks in advance!

~Vol

P.S.  This is my first post here.  Is it politically correct to discuss AVH units in an AVIC forum?  

I have Android Auto working well on my Galaxy S6 and 4100NEX.  I had a few issues with the initial connection.  What I noticed is that if the bluetooth connection on the phone showed that it was connected for phone only Android Auto would not work.  If it showed phone and media then android auto works.