JigenKing Posted April 11, 2015 Report Share Posted April 11, 2015 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. Quote Link to post Share on other sites
kenny36 Posted April 12, 2015 Report Share Posted April 12, 2015 my galaxy 5 was workin half way no voice.i had to do hard reset on phone now it wont come up at all on pioneer nex 4100 any ideas Quote Link to post Share on other sites
JigenKing Posted April 13, 2015 Report Share Posted April 13, 2015 It won't detect your phone at all? or you see it boot and then crash? You might just try uninstalling auto and reinstalling it...maybe something got corrupt when you did the hard reset Quote Link to post Share on other sites
kenny36 Posted April 16, 2015 Report Share Posted April 16, 2015 when you plug your phone in it shows the android auto app for 2 second then goes off i delete the app and install no luck i also check my usb setting it charges the phone just no android auto any ideas i can try Quote Link to post Share on other sites
slaakker Posted April 18, 2015 Report Share Posted April 18, 2015 Mine worked for a minute then froze. Now it doesn't recognize the phone other than a usb connection. Sprint note 3 nex4100. Quote Link to post Share on other sites
kenny36 Posted April 27, 2015 Report Share Posted April 27, 2015 i got nex 4100 my galaxy 5 now i get red screen saying my phone not compable with android auto nice google or pioneer Quote Link to post Share on other sites
Dr. Claw Posted April 27, 2015 Report Share Posted April 27, 2015 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. Quote Link to post Share on other sites
PaisanNYC Posted April 28, 2015 Report Share Posted April 28, 2015 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 Quote Link to post Share on other sites
kenny36 Posted April 28, 2015 Report Share Posted April 28, 2015 i have sprint guys and debugging is on Quote Link to post Share on other sites
kenny36 Posted April 29, 2015 Report Share Posted April 29, 2015 i try uncheck debugging when plug in no luck still get red screen saying s5 is not compable Quote Link to post Share on other sites
rbrown863 Posted April 29, 2015 Report Share Posted April 29, 2015 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. Quote Link to post Share on other sites
kenny36 Posted April 29, 2015 Report Share Posted April 29, 2015 rbrown email me on how you did this rkcoop9@aol.com i have sprint i only have 5.0 ;lollipop Quote Link to post Share on other sites
Dr. Claw Posted May 30, 2015 Report Share Posted May 30, 2015 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. Quote Link to post Share on other sites
manjo Posted May 31, 2015 Report Share Posted May 31, 2015 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 ? Quote Link to post Share on other sites
Dr. Claw Posted June 1, 2015 Report Share Posted June 1, 2015 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?! Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.