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
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.
Endosmok said:
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.
Click to expand...
Click to collapse
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
cisco kidd said:
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
Click to expand...
Click to collapse
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
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.
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.
Related
Hello.
I recently came into possession of an LG G5 Android phone, T-Mobile variant H830. I was planning to use it for software development, and I was wondering if there's a way to get it to connect to the internet using my ADSL connection. I'm fairly new to the wonderful world of Android, so please bear with me.
I realize Wi-Fi is the path of least resistance... but it's not the best option in this particular house and I have a fine Ethernet network just sitting there waiting to be used. Also, my old Windows Phone (ducks) is able to use it just fine.
I have a USB type C hub (a Microsoft HD-500 display dock) and a small collection of USB to Ethernet adapters (Realtek RTL8153, ASIX AX8872B). Unfortunately, the LG G5 has no interest in recognizing any of them.
I've also played around with reverse tethering to my PC, but apparently it requires root access to even work, and even after that it doesn't even work very well.
Does anyone have any suggestions on how to make this work? Should I be looking into flashing LineageOS? Or maybe I just have the wrong phone?
Thanks.
Today's progress: I played with an app called ReverseTethering, which works by establishing a VPN connection to its host PC over an ADB-controlled USB pipe. Most apps seem fine with it. However, the Google Play Store insists on using Wi-Fi to download apps and won't recognize a reverse-tethered connection. It does resume in-process downloads over the connection, but won't initiate new ones. My conclusion is that this is an app bug, and that it is checking for Wi-Fi when it really should simply be checking for a valid connection.
There's an app called Fake Wifi that will apparently hack apps into thinking their connection is over Wi-Fi when it's not. However, this app needs a framework that requires a rooted device. So, back to square one.
(NB: I'd prefer not to root my device for security reasons.)
Today's progress: connecting a Sharkk UH-SKRJ11 (RealTek RTL8153 chipset) directly to the phone using a USB C-to-A adapter works. A couple of apps seem iffy about it, including the Google Maps offline downloader, but the Google Play Store and the LG updater work. So this is probably as good as it gets without major surgery.
This suggests that the problem was in fact the Microsoft HD-500 display dock. It would charge the phone, but the phone didn't seem to recognize it as a USB hub.
Does anyone have a suggestion for a USB Type C hub that works with this phone? Ideally I'd like to use Ethernet and charge at the same time.
Hello,
I work on the desktop team at a company and we started using Dell's DW-15 USB-C docks since Dell is phasing out the E-port. Out of curiosity, I plugged my phone into one a couple of months ago and everything but the display output works. We also have Dell 96NPS USB-C to Ethernet adapters that work fine with the G5.
I have this here.
Bought from eBay. Works on both G5 and V20. Should work on any phone that supports SlimPort.
I have connected it to the phone with display and various peripherals. Did not try ethernet dongle though.
I'm a bit puzzled that the Microsoft dock did not function right. I though that too was simply a display/slim-port design. Or maybe it's only the hub/otg functionality that's unavailable?
@askermk2000: thanks for the note. Any idea what the model number is on that device?
The Microsoft dock situation is quite odd. Before fully patching the OS (the phone arrived with the March security patch, I think) it wouldn't see anything at all on the dock (which has a Surface Ethernet Adapter aka RTL8153 plugged in). After patching, it suddenly started working, and working fine. Then after patching up to latest, it sort of half-works. It connects and data flows, but the phone pops a "Connecting" message for a minute every so often, as if it were pulling a new DHCP address or something. When connected directly to the Ethernet adapter, things work fine.
(And when I say fine, I mean mostly fine. Every now and then I plug in the adapter and nothing works. Disconnecting and reconnecting sometimes works. Changing USB connection settings sometimes works. Sometimes rebooting works. <shrug>)
@Keynesian
I'm sorry but there is not a single marking on that thing. A truly generic device.
That exact one seems to have become rare now. This looks like the successor, though it has one less usb port than mine.
Here's a listing of mine.
There are many generic types, with or without hdmi, one or more usb etc
One option with aluminum housing, 1 usb 1 hdmi and usb-c power input should cost no more than about $10
I think I got mine for around that (which is a more expensive model), but I got lucky and found a lonely expiring auction. Saved maybe $20
Weird about that dock of yours. Hopefully you'll have better experience with another one.
If I had an ethernet dongle I'd try to confirm if it works with or without the dock on my H850, but that could also depend on the type of chipset and driver used (and LG's flavor of the month it seems).
Just ordered one of these off Ebay. We'll see how it goes in a month:
https://www.ebay.com/itm/UBS-3-1-Ty...-Charging-Port-OTG-Adapter-Cable/162309246619
Hi, after reading a few threads about android auto compatibility with the essential phone, I have been put off purchasing as AA has become a pretty permanent fixture of my commute.
There have however been software updates I see by Essential, notably the latest firmware in the past few days. Just wondering if anyone has seen any improvement in android auto experience with any of the latest updates?
Thanks.
I havent had an issue. Im running AA on both my 2017 Audi and 2017 GMC. I had issues with my LGV20. With the LG, i would have to reboot the phone to get AA to recognize and even when it showed connected, text messages werent available. If i unplugged the phone and then tried to plug back in, i would have to reboot the phone if i wanted AA to work. With the essential, i can unplug the cable and plug back in and resume what i was doing seamlessly and all the alerts/texts come up no problem anymore
Same here no issues I use a couple of hours per day.
It works great with my modded Infotainment center in my 2016 Miata. However, it will not stay connected to my aftermarket 2016 Kenwood head unit in my other car more than 1-2 seconds constantly connecting and disconnecting. I've tried half a dozen different cables. Works fine with my Nexus 6.
elkay said:
It works great with my modded Infotainment center in my 2016 Miata. However, it will not stay connected to my aftermarket 2016 Kenwood head unit in my other car more than 1-2 seconds constantly connecting and disconnecting. I've tried half a dozen different cables. Works fine with my Nexus 6.
Click to expand...
Click to collapse
This was what I had heard of in the forums and gives me pause about purchasing. May I ask if you have tried with latest firmware which Essential says contains some bug fixes?
Thanks to the others with positive experiences. More encouraging!
Are the reported issues with the phone itself running Android Auto and just Bluetooth connecting to the car, or when the phone is linked to the head unit?
Seamonkey79 said:
Are the reported issues with the phone itself running Android Auto and just Bluetooth connecting to the car, or when the phone is linked to the head unit?
Click to expand...
Click to collapse
As I understood it, it was with the phone linked to the screen of the head unit. Mine is a 2016 vw. There was a similar issue with the Oneplus 3 which kept disconnecting for no apparent reason and Oneplus fixed this with a software update which is why I was enquiring about updates here.
No problem here, connecting to and staying connected to my wife's 2016 Ford Edge, and my 2016 Corvette.
I use AA everyday, in my 2018 Audi Q5. I've never seen it drop out once.
Sent from my PH-1 using Tapatalk
Thanks very much for the positive reports.
I had issues getting AA to work with my Essential phone, what solved the issue for me was disabling USB debugging. After that it worked like a champ.
elkay said:
It works great with my modded Infotainment center in my 2016 Miata. However, it will not stay connected to my aftermarket 2016 Kenwood head unit in my other car more than 1-2 seconds constantly connecting and disconnecting. I've tried half a dozen different cables. Works fine with my Nexus 6.
Click to expand...
Click to collapse
Exact same. My old Nexus 6 works fine but the Essential will not work with my Kenwood DDX9903. Currently I'm using my Nexus and tethering but due to Android Auto's (stupid imo) handling of calls through BT instead of USB, I can't accept calls over BT with the Essential while the N6 is in Android Auto mode.
dwj said:
This was what I had heard of in the forums and gives me pause about purchasing. May I ask if you have tried with latest firmware which Essential says contains some bug fixes?
Thanks to the others with positive experiences. More encouraging!
Click to expand...
Click to collapse
I'm all up to date and it still will connect and disconnect rapidly until my head unit restarts. It literally worked ONCE on the first night I got it. On my drive back home and up til now I only get the USB access error message.
Charlie_Don't_Surf said:
Exact same. My old Nexus 6 works fine but the Essential will not work with my Kenwood DDX9903. Currently I'm using my Nexus and tethering but due to Android Auto's (stupid imo) handling of calls through BT instead of USB, I can't accept calls over BT with the Essential while the N6 is in Android Auto mode.
I'm all up to date and it still will connect and disconnect rapidly until my head unit restarts. It literally worked ONCE on the first night I got it. On my drive back home and up til now I only get the USB access error message.
Click to expand...
Click to collapse
And same haha.. I'm using my Nexus 6 with hotspot thru my Essential for connectivity. And also same issue regarding calls. I was pondering cuttingthe proprietary USB cable and soldering it really close to the connector itself, thinking maybe if I get that cable as short as possible and then use a USB-C cable *just* long enough to reach the phone in front of the unit, maybe that will give the signal just enough boost to not keep failing repeatedly.
elkay said:
And same haha.. I'm using my Nexus 6 with hotspot thru my Essential for connectivity. And also same issue regarding calls. I was pondering cuttingthe proprietary USB cable and soldering it really close to the connector itself, thinking maybe if I get that cable as short as possible and then use a USB-C cable *just* long enough to reach the phone in front of the unit, maybe that will give the signal just enough boost to not keep failing repeatedly.
Click to expand...
Click to collapse
I swear I thought about doing the same thing but I think it might be a USB C issue in general. I have to test it with my mom's Nexus 5X. Worst case scenario I'll end up buying a replacement cable, cannibalizing the connector, and running a ~3ft USB C cable connected directly to the kenwood connector. That should tell me for sure if it's a cable quality/length issue. If I remember correctly, the cable from Kenwood is at least 2 ft. just by itself.
If you find any solution let me know because I have almost an hour commute and Waze's police alerts helps me big time.
My Prius was hellbent on grabbing my wife's iPhone instead of my SGS5 and the same thing happens with the Essential Phone. It always grabs her phone over mine. Otherwise, works fine.
elkay said:
And same haha.. I'm using my Nexus 6 with hotspot thru my Essential for connectivity. And also same issue regarding calls. I was pondering cuttingthe proprietary USB cable and soldering it really close to the connector itself, thinking maybe if I get that cable as short as possible and then use a USB-C cable *just* long enough to reach the phone in front of the unit, maybe that will give the signal just enough boost to not keep failing repeatedly.
Click to expand...
Click to collapse
I had it working tonight. I used a SUPER SHORT USB 2.0 Cable that came with my Anker PowerCore battery, then a samsung microusb to USB C connector.
It's so weird but I think going with the shortest cable possible, including the head unit cable might be a fix.
That sounds like a problem specific to Kenwood receivers then.
I've used my Essential with Android auto in four different cars with three different cables and I've never seen it disconnect once on any of them. But those were all Factory radios.
Sent from my PH-1 using Tapatalk
I just switched from an Xperia X and the PH-1 is significantly slower on AA. It works, but it's a slog.
This is on a 2017 Silverado
Just bought a 2017 Audi S3 and AA has been working flawlessly since day 1.
Weird, no slowdown or speed issues on AA in any of the 4 cars I've used it in. Guess I'm lucky. As long as it works in my Audi (and it does), I'm happy.
Sent from my PH-1 using Tapatalk
Once the USB cable is connected to OP6 first and then car ignition is turned on, Android Auto is not coming up on head unit screen. If the ignition is turned on first, and if I insert the USB, it gets recognized properly and AA comes up. It seems OP6 with Pie relies on USB connection broadcast for kicking off AA. I verified that this is not an issue with car's head unit because my Samsung phone running Android Oreo behaves properly with the same head unit. This is either an OP/OxigenOs-specific or Pie-specific issue. The expected behavior is that AA should appear on head unit screen when car is turned on even if the USB cable is already connected. Also, this is a safety concern as well. Right now, you can't expect me to insert USB cable after I have started driving. Even if a I manage to do it initially, if I stop the car somewhere and turn it off and on again, I have to unplug and plug the USB cable back again now to make it work. Any help is appreciated. Device details are given below
Head unit: Alpine stock unit on Honda Jazz VX 2018.
Phone: OP6 with latest Pie, not rooted, USB debugging off
AA: 3.5
Already tried AA cache/storage reset, uninstall, etc.
Likely an issue with your phone or cable. I've never had any issues getting AA to activate no matter how I connect.
Try using a different cable, or a factory reset.
iElvis said:
Likely an issue with your phone or cable. I've never had any issues getting AA to activate no matter how I connect.
Try using a different cable, or a factory reset.
Click to expand...
Click to collapse
Thanks. Already tried 3 different cables including original OnePlus cable. Only thing remaining is factory reset, which I will try today. If that doesn't work, thinking of downgrading to Oreo. Then that doesn't work, thinking of switching to Samsung. Already have had a couple of bitter experiences with OP6 despite its other great features.
iElvis said:
Likely an issue with your phone or cable. I've never had any issues getting AA to activate no matter how I connect.
Try using a different cable, or a factory reset.
Click to expand...
Click to collapse
Tried factory reset and downgrade to Oreo today, but the issue persists. Samsung J7 Max works beautifully
negie said:
Tried factory reset and downgrade to Oreo today, but the issue persists. Samsung J7 Max works beautifully
Click to expand...
Click to collapse
May just be a conflict between your phone and head unit. AA can be weird. My HTC M9 was a huge pita with my VW, but when I switched to OP all the issues went away. ¯\_(ツ)_/¯
Hi everyone i'm facing this problem since july now, the issue is that the pixel 3 usb-c port works only with charge and nothing else, that means it doesn't work with pixel buds, doesn't work with other headphones with jack adapter, no OTG devices work, and finally PC connection wont work either.
I've tried everything possible from cleaning the port to factory resetting the phone, with no results.
Online there are few google forum threads about the problem but without any fix, so i've tried to RMA from google but even if i have still warranty, i should have paid 106€ cause my back glass cover is broken. Since i didn't want to pay that much to fix the back i bought the usb-c port replacement and i fixed it myself, i thought it would have fix it but surprisingly it didn't and i have still the same issue so working charge but no any other usb-c connection.
At this far i'm thinking it's a software problem but even Android 11 with last october patch didn't solved it , still the same: usb preferences greyed out when connecting to a PC ( tried different PC: Windows 10, Windows 7 and even Linux) same result.
Update:
I have more evidences which lead to this point, a few days ago i tried to connect my Pixel C to the laptop to transfer some files and it is suddenly showing the same problem of the Pixel 3, i have to state that the Pixel C was running an Android 9 ROM so it fits perfectly in all the reported issues about it precisely that the problem pops out since Android 9 and there seems not to be any fix for this even in the last Android 11 patch.
I also started getting the same issue. Maybe I didn't notice for a long time because I was using a Bluetooth headset for a long time. And today when I checked, it was not working for me. Charging works and pc connection is also okay for the moment. Surprised to see no one has responded to this.
This happened to me every now and then. I was able to clear it by turning USB debugging on (under developer options) then connecting it to my laptop. Unplugged it and turned USB debugging back off.
Hello everyone.
So I have a few issues which I am guessing are all somewhat related.
TL;DR
1) Android auto stopped working
2) if I reboot. It will just power off and needs to be plugged in to power back on
3) usb c to usb c only works one side not both sides. But usb a to usb c works both directions.
Note: my wife has the same phone and had none of these issues with the same cables and such. So it's not cables issues. We also have the same OS.
The longer detailed version.
First issue. Android auto stopped working. At first it told me that there may be an issue with the cable and that I should get another cable. I tried my wife's pixel 3 xl and it worked fine. So it's not the cable issue. I tried restarting. The phone did not. So I plugged it in and it powered on. Now the phone will only boot if it is plugged in. Plugging the phone into the car usb a to usb c it charges on both side of the cable but there's no longer any warning about the cable for Android auto. Again my wife's phone works with the same setup so it's an issue with my phone. Then when plugging my phone in using the oem cable I noticed it only chargers using one side. The other side fails. Tested my wife's phone and both sides work. I then test my wife's cable and same issue with her cable for my phone.
Pixel 3 XL
OS 11 RQ1A.210105.003
I did a factory reset but same issues remain.
I'm open to using a ROM if it will fix the issue.
I saw a few posts on google forums about this issue but not fix/solution so I was kind of wondering if a ROM would possibly fix this issue.
Thanks so much for any help.
Willing to try most items as phone is out of warranty and I really like Android auto and hate not having it.