ssmcd

The same exact thing happens on my 4100 NEX when using Android Auto. Phone (Moto Z) gets really hot, voice recognition goes to crap and AA glitches and lags. Im pretty sure the issue is the phone thermally throttling though, not the NEX, because the rest of the sources (iPod, HD Radio, etc) function perfectly fine and the phone still misbehaves after disconnecting from the radio. I think the combination of the battery charging, GPS, and ambient temperature in the summer cause the phone to overheat and lag. Best bet is to keep the phone out of the sun and/or in front of a vent with the A/C on.

You could always install a switch on the ACC power wire.

Are you plugged into USB1? The device won't recognize the update on USB2 or the SD card.

damn thats sweet, im stuck with a avh 4100 though

hopefully someone can fix that in near future

x100 (AVH-X8700BT) has no love in this forum...

 

Was so excited until I read X8700BT is not part of the x000 series.

There is a solution for x100 devices on the AVIC Hacking slack. It's​ somewhat less sophisticated than this but it gets the job done.

Android Auto currently appears to only support streaming music apps like Spotify, Pandora, Google Play Music, etc..

If you want to listen to music over USB I would suggest loading your music onto a USB thumb drive or an iPod where you can make playlists and better sort through your collection.

I don't think the pioneer units were designed to read music from your phone directly. There is Bluetooth streaming for that.

My current setup is AA with an iPod and it works perfectly.

Make sure the folder â€AVICAVH16" is at the root of your fat32 formatted USB stick plugged into USB1. When you open up the USB drive on your computer you should only see one folder.

Just upgraded my 4100 from 1.05 to 1.09. The first time I switch to my iPod after turning on the head unit I get tons of popping and static. If I switch to any other input then back to iPod the static is completely gone. Happens on both USB 1 and 2. Tried multiple cables with the same result. I have no idea what would cause it to go away after the input is switched. Any ideas? Never had this issue on 1.05.

Just use a normal USB cable for Android Auto

Firmware Version 1.09 for x100 devices is now available as well.

Were you able to get a fullscreen boot animation to work? I tried 480x800 and 800x480 and it's still distorted and laggy at 20fps on my 4100.

Good find for the bootlogo in framework-res btw. I had found the same image in jcommonlib-res and changed it but it didn't work.. now I know why lol

Thanks for the replies...tried a number of cables and given that another phone works using the exact same cables I am 'assuming' that it's the combination of the Moto X 2nd Gen and Verizon.  Hopefully someone else on Verizon has the same phone and can post.  I also tried a friend's Samsung Galaxy S5 on Verizon and it did NOT work (running Lollipop 5.0 flat).  Verizon, as usual, seems to have done something with their custom ROM that prevents phones from working with Android Auto.

I have a 4100NEX and MotoX 2nd Gen on Verizon and ran into similar problems at first.  Ended up wiping data for Android Auto, Google Play Services, and Google App and tried at least three different cables.  Probably a little overkill but I finally got it working after a frustrating 30 minutes, but now it works flawlessly.

Also noticed my phone needs to be unlocked before it connects.  I tried setting up the NEX as a "trusted device" but the way Pioneer pairs the device messes it up.  Hopefully this gets fixed eventually.