U11 and android auto issues w Kenwood 7704S HU

[cisco kidd]

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 installing 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. I thought perhaps Nova Launcher may have been the culprit but not the issue once reverting to Sense as launcher. I have enabled AA permissions so thats set up correct.

Anyone experience U11 Android auto issues, super frustrating and don't want to run a custom rom just yet or possibly sell phone and find a working Android phone, last OP3 worked with previous Sony XAV-AX100 but I sold that unit wanting an extra USB port. 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. I can't see it being the USB C port but I did test the unit at the audio store where I bought my 7704S on their demo 9904S and same issue the phone charged but would not launch AA on the HU so it seems to be a hardware/software issue with the U11 itself

 

[Endosmok]

I don't have a Kenwood head unit but I have a pioneer NEX-4100 with Android Auto & Apple Carplay.
I just went out to the garage hooked up my wife's (I don't have one) HTC U11 (64GB USA Version) and successfully configured & established an Android Auto connection to the head unit. Ran through the menus and it functioned properly.

I used the USB C cable that came with my LeeCo S3 phone and it worked with the HTC U11. I did not try to use the HTC U11 cable as I don't know where the ball and chain keeps it. But I know cable(s) and Android Auto make a difference.

The U11 was on the latest Oreo 8.0 stock rom and is not rooted.

Hope that helps....

Also, on my Pioneer head unit, I have to specifically enable either Apple or Android Auto in the menu. So if it's not setup to use AA then it won't work until I enable it. This is only done once or until you need to use the Carplay side. Additionally, There are two USB connectors on my head unit with one connector specific to the iPhone and the other specific to the AA phone.

 

[cisco kidd]

I don't have a Kenwood head unit but I have a pioneer NEX-4100 with Android Auto & Apple Carplay.
I just went out to the garage hooked up my wife's (I don't have one) HTC U11 (64GB USA Version) and successfully configured & established an Android Auto connection to the head unit. Ran through the menus and it functioned properly.

I used the USB C cable that came with my LeeCo S3 phone and it worked with the HTC U11. I did not try to use the HTC U11 cable as I don't know where the ball and chain keeps it. But I know cable(s) and Android Auto make a difference.

The U11 was on the latest Oreo 8.0 stock rom and is not rooted.

Hope that helps....

Also, on my Pioneer head unit, I have to specifically enable either Apple or Android Auto in the menu. So if it's not setup to use AA then it won't work until I enable it. This is only done once or until you need to use the Carplay side. Additionally, There are two USB connectors on my head unit with one connector specific to the iPhone and the other specific to the AA phone.

Thanks for your reply and taking the time to test your wifes HTC u11 on your Pio system. I am stumped still with no luck, with the Kenwood there is no selecting either the AA or Car Play in menu system will just launch automatically upon connection of device. The oddest thing is when I tested my sons 7 Plus it worked flawlessly but following I tried with my HTC U11 using the factory cable and no success. I plan to buy a better USB C cable and give it one last try because I am stumped and frustrated. Mine is USA version as well 64GB. Everything works as it should aside from the system being able to detect the phone and yet the deck rapid charges the device through either USB connection.

I tried another USB C cable and this one gives "an access error of the USB device has occurred" What makes this story even odder is my phone is not detected by my pc either so I am really starting to question if there is an issue with the USB C port, it charges fine but from my understanding data flows via different contacts within the port. This is the only sensible reason at this point. At this point as much as I like the U11 I am considering an alternative Android phone. When i looked up this access error there are lots of people with the issue and Kenwood decks as well as others... Seems it can be a hit or miss with this newest connection
https://productforums.google.com/forum/#!topic/android-auto/az_IM9QyzI4

 

[dcpete]

Thanks for your reply and taking the time to test your wifes HTC u11 on your Pio system. I am stumped still with no luck, with the Kenwood there is no selecting either the AA or Car Play in menu system will just launch automatically upon connection of device. The oddest thing is when I tested my sons 7 Plus it worked flawlessly but following I tried with my HTC U11 using the factory cable and no success. I plan to buy a better USB C cable and give it one last try because I am stumped and frustrated. Mine is USA version as well 64GB. Everything works as it should aside from the system being able to detect the phone and yet the deck rapid charges the device through either USB connection.

I tried another USB C cable and this one gives "an access error of the USB device has occurred" What makes this story even odder is my phone is not detected by my pc either so I am really starting to question if there is an issue with the USB C port, it charges fine but from my understanding data flows via different contacts within the port. This is the only sensible reason at this point. At this point as much as I like the U11 I am considering an alternative Android phone. When i looked up this access error there are lots of people with the issue and Kenwood decks as well as others... Seems it can be a hit or miss with this newest connection

I have been fighting cables and Android Auto for a long time now and finally found my problem which is so dumb to be almost unbelievable. Had a friend suggest this and it was the problem. I keep my phone in my pocket. It picks up lint in the USB C connector. And slowly over time. I took a toothpick and cleaned out the connector. It gets packed in, so takes a while to completely clean it out. I was shocked how much came out. After doing this, all my USB errors disappeared and problems with various cables disappeared as well. Duh, the common denominator was always the phone, not the cable. But it was curious that some cables seemed to work better than others. I feel so dumb, I actually returned this model phone in the first year under warranty because it finally stopped charging by cable. Got another phone and a wireless charger, but my second phone started acting up again and finally just refused to work a few months ago with Android Auto. Now everything is working great again.

I have LG G6 and Kenwood 7704 HU.

Chris

 

[pompanosix]

I'm having the same problem.

I have a pioneer 4200 nex, and can't connect to android auto. Worked perfect with previous m9, but since I bought U11, nada.

I'd be curious to see if anyone can help figure this one out. I drive a lot for work so it was nice seeing Maps on the screen.

 

[pompanosix]

Check the Kenwood website and see if there's a mention of unit having problems with type C connectivity.

pioneerelectronics.com/PUSA/Car/NEX/Android+Auto+not+working+for+newer+USB+Type-C+phones+(including+Pixel

While researching about me pioneer HU, this is what I found out. I suppose you can use the recommended cables as listed in the pioneer website as it sounds more of a cable problem than anything else.

I will post more once my new type A cable comes in. Sux I gotta go back in the dash to plug it in though. I still have my OEM type C so that should work.