Database Info

Stereo Headset(And other similar accesories) do not work with Cupcake/1.5?

I've been using Haykuro's builds, and now the latest JF1.5 build (So snappy. ), but in none of these builds does the Stereo Headset that came with the phone work, if you plug them in the sound keeps playing from the phone itself. Is there something special I'm supposed to do now that you didn't have to before? Or is it just something they forgot to keep on while they were busy making Bluetooth stereo work?

Mine work with JF1.5 ADP, both the stock single wired headset, and my headphones plugged into the HTC 3.5mm adapter. Music plays, can make calls, the button controls the playback... not a single problem. Have you tried adjusting the volume with them plugged in?

Well that's odd.. Yeah I have, it just changes the volume of the phone. Hmm.

update the radio
TwilitTruth said:
I've been using Haykuro's builds, and now the latest JF1.5 build (So snappy. ), but in none of these builds does the Stereo Headset that came with the phone work, if you plug them in the sound keeps playing from the phone itself. Is there something special I'm supposed to do now that you didn't have to before? Or is it just something they forgot to keep on while they were busy making Bluetooth stereo work?
Click to expand...
Click to collapse
you need to update the radio on the phone. download
ota-radio-2_22_19_26I.zip on
http://sapphire-port-dream.googlecode.com/
This fixed the same issue I was having.

Hmm, okay. I was pretty sure I already did that, but I'll try again and get back with my results tomorrow.

TwilitTruth said:
Hmm, okay. I was pretty sure I already did that, but I'll try again and get back with my results tomorrow.
Click to expand...
Click to collapse
I'm having similar issues. My HTC 3-1 adapter stopped working, but my stock adapter does work. I also flashed the radio. Please report back if re-flashing the radio fixes your issues.

Had a chance to test it out sooner than I thought. Sorry, I had ASSUMED that the 3.5mm adapter wouldn't work since my HTC 3-1 adapter didn't, but hadn't actually tried it. :x Anyways it DOES work, as per above though, the 3 in 1 does NOT.
However, I have found a workaround. With the phone unplugged, Plus your 3.5mm jack into the 3.5mm adapter that came with the phone (The one with the button), then plug the 3.5mm adapter into the 3-1's USB slot on the side, and if you're like me you'll be plugging in your car charger too, and attaching it to the back of the 3-1 adapter. Anyways, then just plug the 3-1 adapter into the phone and it WILL work. Plus you get the functionality of the little on-off button. I'm happy now.
Still, seems odd that the 3-1 doesn't work as intended (Being able to plug the 3.5mm jack directly into it.), but for my purposes this case is solved.

Well this is great for use early buyers who were treated so well and received the official adapters that are apparently the only ones that still work with the phone. /sarcasm
Seriously. What the hell.
I'm probably buying some A2DP headphones anyways, but since my original headphones' connections somehow got weakened in the little volume control nub, I'm pissed.

I have no problems with my 3 and1 adapter or stock headphone adapter with the new JF 1.50ADP....

LOL... great minds think alike. I had already discovered this workaround as well and can confirm it does work just as you said for me too. I'm okay with this solution for now, but it would be nice to eliminate some wires from my audio setup in car, rather than adding to the mess.
The new radio update must have re-mapped some function that was required for the standard headphone auxiliary outputs to work. That's the only explanation that I can think of, unless someone using a previous Cupcake build and the new radio can confirm that a 3-to-1 adapter works okay...

So, when I was using Haykuro's build I noticed a little Icon on the Notifications bar that let me know I had the 3.5mm Headphone jack plugged into the mini usb, But now on JF's 1.5, It's not there anymore. I also washed my 3.55 plug, So I don't know if something happened or if its JF's. Does anyone else know what I'm talking about?

i am also having this problem with my htc 3-in-1, i have flashed the radio. i have not tested the workaround yet.

rwbarnes67 said:
I have no problems with my 3 and1 adapter or stock headphone adapter with the new JF 1.50ADP....
Click to expand...
Click to collapse
Which 3-in-1 adapter do you have?

Bluetooth Stereo not working here
I can use a regular headset fine.
but when i pair up my bt stereo a2dp headset I get no call sound. Regular sound tops at this point. Then I have to reset my phone to get sound back.
Anyone experiencing this ??
it seemed to be in the official ADP 1.5 so I guess It may be an unfixed Android bug.

same issue here =(
I ALWAYS used to use my G1 as a music player in my car, but now that doesn't work =/ I'm stuck using CDs! =( lol
I have an HTC adapter I actually bought at a Tmobile store so I can't bealieve it doesn't work now with these new builds. Mine only has the male end that goes to the G1 and 1 female where I plug an aux cable into so I can;t do the trick you guys talked about above.
If ANYONE can help out, it would be very appreciated.

The htc 3-in-1 adapter was reported not to work as intended pretty soon after the HTC version of 1.5 was released. It doesn't register on the phone. I suspect all derivatives of the HTC version (like JF's) will behave the same. I also suspect this will be fixed in an upcoming service release.
/Mats

So there's no current fix for this?

shadixt said:
So there's no current fix for this?
Click to expand...
Click to collapse
Nothing beyond using some other adapter, as far as I know. Ironically, only the original HTC 3in1 adapter seems to cause this behaviour.
/Mats

shadixt said:
So there's no current fix for this?
Click to expand...
Click to collapse
As noted previously, you CAN continue to use the HTC 3-in-1 adapter, but only in combination with a second USB to headphone jack adapter (such as the original one that came packaged with the G1 for the past few months). Not a fix, but the workaround does work fine.

this is almost crazy
So what you are trying to say is.. We wanted Bluetooth, so we got Bluetooth, but we lost Headset feature??? Other than the iPhone, there is not a phone out there that acts like this? Dont get me wrong I love the G1 and I'm not really sure how I got along with out it.. but really guys, Fixing one thing only to break another is not a good business practice. My guess is that the iPhone will work the first time.. but only time will tell... Has anyone heard anything about the Beam files feature?
//j

USB audio on the Moto G?

I already found out, that the Moto G supports USB OTG, but would it support USB DAC's (digital-analog audio converter) ? If any Moto G owner owns a USB Dac or atleast something compareable like a USB headset or USB headphones, I'd be really thankfull if you could try it out.
The dac/headset needs to be plugged into the phone using a USB OTG cable.
Thanks!
Sent from my GT-I8160 using xda app-developers app

Works!! BUT:
I hooked an USB-OTG to Moto G, in there a Creative USB Soundcard with analog/digital output. Analog didn't work (must be the soundcard), but digital. I connected the digital out with a light cable to my RME environment and I could hear the music but with wrong frequency and crackled - but it works
Moto G has enough power to let the soundcard work.
[edit]
Hooked another soundcard in, this time analog works but wrong sample frequency and oversaturated, no option to control the volume.

Wow! This phone seems to be even more incredible value than I ever thought.
The problems that you mention sound pretty weird, though. The first thing that I'd suspect is the lack of special drivers for the soundcards on the Moto g. Maybe a simple DAC that doesn't need any special drivers would work better.
In fact, stock androids rarely work with any USB audio devices. But there's a app that includes special drivers and makes most USB-OTG enabled droids work with USB audio devices. You can the trial version (link in the description of the app) of it if you like:
https://play.google.com/store/apps/...=organic&utm_term=usb+audio+recorder+pro+demo
Be aware that the trial only works for 15 minutes and it doesn't play the usual audio formats. ( .flac works) If you try it, you should put a flac on the phone before installing the app.
Oh, and who knows how well this might work when CM and KitKat arrive!
Thanks a lot for your help.
Sent from my GT-I8160 using xda app-developers app

With the app it works, without stuttering and you can control the output volume, although there was an error warning at startup regarding main volume
I tried to record something, but hadn't enough time. First try was unsuccessful unfortunately.

shaftenberg said:
With the app it works, without stuttering and you can control the output volume, although there was an error warning at startup regarding main volume
I tried to record something, but hadn't enough time. First try was unsuccessful unfortunately.
Click to expand...
Click to collapse
Well, that's nice to hear. Maybe some Custom ROMs (Cyanogenmod in particular) will have better support for this without the app.
Anyway, I think I'm going to get this phone (Christmas is coming ). Usb audio support (atleast with the app) is crucial for me, so thanks for reporting that it works.:good:
One last thing though, what make and model were the two soundcards that you used for testing?

UnknownAX said:
One last thing though, what make and model were the two soundcards that you used for testing?
Click to expand...
Click to collapse
First a cheap Creative USB Soundcard, second a DJ-Audio-Player from EKS (www.eks.fi) which has its own soundcard per player.

Could you test this on the faux kernel that your running atm, Shaftenberg?
Most people who have tried it on the stock ROM have experienced the same glitches that you mentioned in your first post. On the other hand, there's also one report of it working fine, with the Google music player. The DAC is probably the biggest factor.
Anyway, I'm just waiting for the 16gb version to be available....

I tried 2 DACs. One was a CEntrance DACport LX flashed with the iPad firmware, and the other was a cheap off-brand thing (ELE EL-D01 on eBay). Both of them "worked", but I encountered the same issue with each: I tested both by playing a Youtube video, and the audio was not playing back at the proper sampling rate. The audio was slightly slowed down... as a result, pitches were slightly lower, and the audio lagged behind the video pretty significantly. If I had to guess, the audio was 48kHz, and Android was trying to play it back at 44.1kHz without resampling it first.
Why it was doing this, I have no idea: on a Nexus 4 running stock Jellybean with jacknorris' patch (which, AFAIK, doesn't pay attention to sampling rates but just assumes Android will handle that properly elsewhere), this works perfectly. However, it was fascinating/encouraging to see this work at all on the Moto G: it means that with stock firmware, not only does OTG/USB host mode work, and not only does the kernel have the stock Linux USB DAC driver compiled in, but the Android framework itself attempts to use the DAC, which is *definitely* not true with plain-jane AOSP.
One thing I was sad to see (which also seems to be true of a LOT of other Android phones that support OTG out-of-the-box) is that if I injected 5V from an external source into the USB power lines, the phone would NOT charge as long as OTG mode was engaged. Which means that, at least with the stock Moto G firmware, you can't both be in USB host most *and* be charging the battery at the same time. (Interestingly, the very first time you plug the power in, the phone says "charging", but it's quickly obvious it isn't. If you unplug and re-plug the power in after that, it will not show the lightning symbol on the battery any longer until you reboot the phone. Normal USB chargers continue to work without the OTG cable without requiring a reboot.)
-- Nathan

nlra said:
If I had to guess, the audio was 48kHz, and Android was trying to play it back at 44.1kHz without resampling it first.
Click to expand...
Click to collapse
That makes sense to me. But what would happen if we played a 44.1kHz track? It wouldn't have to resample then, would it?
Maybe that's why there is a report of it working with google music player...maybe he just happened to try it with a 44.1kHz track?
I'm pretty sure this will/can be fixed with a ROM / Kernel. Like USB OTG charging, it's just a matter of time (I hope). Both things have already been successfully enabled on many different devices.
Thanks for the info, luckily I'm not the only one showing interest in this.

It most definitely works with my Moto G and my FiiO E17 (connected via a generic OTG cable)
Trouble is, although it ALMOST worked, I got sporadic but impossible to listen to skipping/stuttering when using Poweramp or the native Google player app.
I finally found an app made by the same people who do the USB Audio Recorder Pro as mentioned by the poster, called USB Audio Player Pro (can't post the link, being a new poster, but a quick search for "USB audio player" gets to it)
...it costs over 5 pounds, and to be frank it is not the world's prettiest or richly featured player, but it certainly works and the output sound is great.
Anyway, just posting to let you know that it works, at least with my Fiio E17.

So here's some good news: after applying the official KitKat 4.4.2 OTA, OTG still works, USB DAC support still exists, and now it even works properly, at least for me! No more strange audio sampling issues: I could attach either one of my DACs and play the same Youtube clip without any difficulty! Audio was perfectly in-sync with the video.
-- Nathan

Did anyone manage to get USB audio to work with the Moto G play edition?

Has anybody found a way to enable OTG and charging at the same time? I genuinely enjoy listening to Moto G + FiiO E17 but it leaves me with low battery on the way home which is rather frustrating and makes me to swap charger/DAC during the day.
I don't mind putting unofficial ROM in as long as it doesn't require hardware mods.

jjacks said:
Has anybody found a way to enable OTG and charging at the same time? I genuinely enjoy listening to Moto G + FiiO E17 but it leaves me with low battery on the way home which is rather frustrating and makes me to swap charger/DAC during the day.
I don't mind putting unofficial ROM in as long as it doesn't require hardware mods.
Click to expand...
Click to collapse
I have taken ziddey's USB OTG kernel patch for the Nexus 4, which allows both for charging as well as USB OTG mode without an actual OTG cable, and I have compiled a new kernel for the stock Moto G 4.4.2 ROM, and it works great! The only thing is that you have to use a non-OTG cable...if it detects the OTG cable it will shut off the charging. So you will need a USB Y cable to inject a 5V power source to both your DAC and phone, and plug the phone into the Y cable using a standard micro-USB cable instead of an OTG cable.
If people are interested in this kernel, I can post it. You will need to unlock your bootloader to flash it.
-- Nathan

That is interesting. I would be happy to flash it. Is it safe operation? I flashed multiple windows mobile / windows phone devices but no experience with Android mods yet. Any downsides of custom kernel?

jjacks said:
That is interesting. I would be happy to flash it. Is it safe operation? I flashed multiple windows mobile / windows phone devices but no experience with Android mods yet. Any downsides of custom kernel?
Click to expand...
Click to collapse
You should read some of the other threads on how to unlock your Moto G bootloader and how to flash stock ROMs back, at the very least, before applying mine. I can't educate you on these matters here and there are other threads more appropriate for those discussions. Then take that knowledge and apply it to this. In this case, as long as you are using a stock Motorola ROM already (and not a GPE ROM!), you only need to flash one component: the kernel.
This kernel is completely identical to the stock Motorola kernel in every way except that it has ziddey's patch applied. So the only downsides would be:
1) because you have to unlock the bootloader, if you live in the U.S. at least, Motorola can legally void your hardware warranty, even if you have a hardware failure that cannot be linked to your unlocking of the bootloader. (Other countries' laws are different and Motorola may not be legally allowed to void warranties for bootloader unlocks where you are at.)
2) If an OTA update is pushed to your phone, I believe the kernel will be replaced with a stock one again, and this will stop working. Either that, or because you are running a custom kernel or an unlocked bootloader, perhaps OTAs won't be pushed to your phone, or if they are, they might not install. I have not tested this or read up on this myself as I generally detest OTA updates outside of my control, and prefer to flash my devices myself on my terms when I'm ready to do so.
You can read about ziddey's USB OTG patches that he developed (with the help/inspiration of CaptainMuon) here: http://forum.xda-developers.com/nexus-4/orig-development/usb-otg-externally-powered-usb-otg-t2181820
The only real difference between how this works on the Nexus 4 and how this works on the Moto G is that, as I explained previously, on the Moto G, there is something in hardware that prevents the phone from accepting a charge if it detects that you are using an OTG micro-USB cable, whereas the Nexus 4 doesn't care if you use an OTG cable or not because pin 5 on the Nexus 4 is not actually wired to anything internally. On the Moto G, there is even a slight cosmetic quirk: if you try to inject 5V power to the phone through an OTG cable, the first time that you plug it in after a fresh reboot, it will say that it is charging after you plug the cable in, but it actually isn't (battery will continue to deplete). And if you unplug the cable and plug it back in, it will no longer show the "charging" symbol, until you reboot the phone again. If you plug in a regular micro-USB cable, though, it will both show charging as well as actually take a charge.
Another thing to be aware of is that there are two different releases of KitKat 4.4.2 that Motorola has released for the G (they released an updated 4.4.2 ROM that fixed a couple of bugs after its initial release), but as far as I can tell, they have so far only released the kernel sources for the original 4.4.2 ROM and not the updated one. So I have only managed to build a kernel for the original 4.4.2 update for the Moto G. I have not tested this, but it's *possible* that this kernel will work just fine with the later 4.4.2 ROM. You are welcome to try it; you won't harm your phone by doing so and can always flash the factory kernel back if it doesn't work or has problems. This kernel likely won't work with any 3rd-party ROMs or with the Google Play Edition ROM (which doesn't support USB DACs anyway, sooo no point in using that one, at least if you care about USB audio which you obviously do). Motorola has not released any kernel sources for 4.4.3 or 4.4.4 yet either, so you should stick with 4.4.2 for now. If this kernel does not work with the later 4.4.2 release, then you should be able to downgrade your system image to the older 4.4.2 ROM and use this kernel with that.
The two 4.4.2 releases on the Moto G (excluding the GPE ROM) are marked by their kernel versions. The first 4.4.2 kernel is versioned as KXB20.9-1.8-1.4, and corresponds to the U.S. retail 172.44.4 ROM version, among others internationally. The second 4.4.2 kernel is versioned as KXB20.9-1.10-1.24-1.1, and corresponds to the U.S. retail 174.44.1 ROM version, among others internationally. It is the source for the first kernel that I have access to.
You may download my kernel from here: http://www.nconx.com/~nathan/motog/boot_motog_KXB20.9-1.8-1.4_OTG_charge.img
After you have unlocked the bootloader via Motorola's site and mfastboot, enter Fastboot mode on your phone again, and then flash the kernel to the phone with mfastboot (the Motorola version of fastboot) the same way that you would flash a stock Motorola kernel (see this post, step 3b: http://forum.xda-developers.com/showthread.php?t=2542219), but substituting in the file name of my kernel instead:
Code:
mfastboot flash boot boot_motog_KXB20.9-1.8-1.4_OTG_charge.img
Reboot your phone, plug it into your DAC + 5V power source (again, using a normal micro-USB cable), and enjoy battery charging while simultaneously connected up to your external DAC.
Good luck,
-- Nathan

Great. Thanks a lot. I will give it a try when I find some spare time

My Moto G works with Creative X-FI DAC
My Moto G runs Kitkat.
OTG cable is connected between Creative X-FI Dac and Moto G. Then Creative device's optical output is fed to the Logitech speaker with optical input. Sound with this setup is much better and awesome.

My Moto G Works w/ Fiio E07K
Running Android 4.4.4
Moto G (LTE) > USB OTG cable > Fiio E07K USB Cable > Fiio E07K > headphones
:victory:

nlra said:
I have taken ziddey's USB OTG kernel patch for the Nexus 4, which allows both for charging as well as USB OTG mode without an actual OTG cable, and I have compiled a new kernel for the stock Moto G 4.4.2 ROM, and it works great! The only thing is that you have to use a non-OTG cable...if it detects the OTG cable it will shut off the charging. So you will need a USB Y cable to inject a 5V power source to both your DAC and phone, and plug the phone into the Y cable using a standard micro-USB cable instead of an OTG cable.
If people are interested in this kernel, I can post it. You will need to unlock your bootloader to flash it.
-- Nathan
Click to expand...
Click to collapse
Would you be interested in building a compatible kernel for 4.4.4? Is the source available? My Moto G is brand new pre-installed with 4.4.4. so no option to use your 4.4.2 kernel. I would really appreciate the help - I have a project that requires me to be able to charge and host simultaneously.
Also, I'm fine with flashing an alternate ROM with source available, such as CyanogenMod -- anything to get OTG + Charging working. Any advice is appreciated.
Thanks,
samwathegreat

U11 and android auto issues w Kenwood 7704S HU

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.

Pixel USB-C Earbuds not working on OP6

Curious if anyone else has procured the new Pixel USB-C earbuds and tried them on a OP6 and/or OP5/5T. They are suppose to work on ANY PHONE running Android P....I am running the Android P Beta 5 on my OP6 and the phone doesn't seem to recognize that the headphone are plugged in AT ALL.... nada, nothing.

jerrywmilton said:
Curious if anyone else has procured the new Pixel USB-C earbuds and tried them on a OP6 and/or OP5/5T. They are suppose to work on ANY PHONE running Android P....I am running the Android P Beta 5 on my OP6 and the phone doesn't seem to recognize that the headphone are plugged in AT ALL.... nada, nothing.
Click to expand...
Click to collapse
what do you see checked in Developer options under Default USB configuration?

jerrywmilton said:
Curious if anyone else has procured the new Pixel USB-C earbuds and tried them on a OP6 and/or OP5/5T. They are suppose to work on ANY PHONE running Android P....I am running the Android P Beta 5 on my OP6 and the phone doesn't seem to recognize that the headphone are plugged in AT ALL.... nada, nothing.
Click to expand...
Click to collapse
Someone on the OP forum just hipped me to turn on OTG setting....and now they work like a charm....though maybe I'll have to reactive this setting each time as it supposedly turns off after 10 minutes which will be a pain.
And pleasantly surprised to find out the BASS kicks on these things...as all the other reviews I have seen out there say they lacked such.

You need to activate OTG in the settings get them working.

Hey,
I also got these buds for my OP6. They work fine and I also enabled always on for the OTG option. But the music control (pause, start, skip, google assistant) are not working at all.
Volume UP and DOWN are working fine.
Any suggestions?

Nummer35 said:
Hey,
I also got these buds for my OP6. They work fine and I also enabled always on for the OTG option. But the music control (pause, start, skip, google assistant) are not working at all.
Volume UP and DOWN are working fine.
Any suggestions?
Click to expand...
Click to collapse
The middle button for Google Assistant / pause / Play / Answer Call work fine for me.

jerrywmilton said:
The middle button for Google Assistant / pause / Play / Answer Call work fine for me.
Click to expand...
Click to collapse
Did you enable anything specific?

Nummer35 said:
Did you enable anything specific?
Click to expand...
Click to collapse
Nope. But when I activated OTG for the 1st time it did step me through a set up menu for the headphone. And again I am on Beta 5.

Maybe because the op6 have usb 2 and pixel have 3.1?

Sh0X31 said:
Maybe because the op6 have usb 2 and pixel have 3.1?
Click to expand...
Click to collapse
Naw. It is suppose to work on all phones with USB C and Android P regardless of port version. Hopefully OP will get rid of the need to activate the OTG setting since the OP6T won't even have a headphone jack.

jerrywmilton said:
Nope. But when I activated OTG for the 1st time it did step me through a set up menu for the headphone. And again I am on Beta 5.
Click to expand...
Click to collapse
Theory:
The OP6T gets Usb-C headphones and maybe the handling of Usb-C headphones is already shipped to user within the beta versions.
I can't imagine OP lets its users always reenable the otg option when they remove the headphone jack and develop their own usb-c headphones.
I can#t verify this at the moment maybe someone else can?

So today I tried the OP6T USB-C adapter on my OP6 and nothing. Wasn't even detected. I didn't try turning on OTG but come on, I can't believe this isn't supported with Android 9 out of the box. Of course it works on the OP6T fine.

adrianblack said:
So today I tried the OP6T USB-C adapter on my OP6 and nothing. Wasn't even detected. I didn't try turning on OTG but come on, I can't believe this isn't supported with Android 9 out of the box. Of course it works on the OP6T fine.
Click to expand...
Click to collapse
You will have to turn on the OTG until they update the firmware.

Hi guys, I'm on op6 with oxygen 9.0.2 and I would like to use USB c port because jack output is not that good at quality, in my opinion. I tried with enabling otg in the notification bar, but I really can't make my USB c headphones work! Is there anything else I have to do? Thanks

daddu97 said:
Hi guys, I'm on op6 with oxygen 9.0.2 and I would like to use USB c port because jack output is not that good at quality, in my opinion. I tried with enabling otg in the notification bar, but I really can't make my USB c headphones work! Is there anything else I have to do? Thanks
Click to expand...
Click to collapse
I assume out mean the OTG Storage setting under "System" menu ? That should do the trick.

jerrywmilton said:
I assume out mean the OTG Storage setting under "System" menu ? That should do the trick.
Click to expand...
Click to collapse
Yeah right that. But that didn't do the trick...headphones still not detected I'm using Sony Wh-Ch700n with USB c adapter. They work fine on mi Mix 2 (and there audio quality looks far better to me) than on OP6 using 3,5mm jack. That's why I would like to try USB c port...

daddu97 said:
Yeah right that. But that didn't do the trick...headphones still not detected I'm using Sony Wh-Ch700n with USB c adapter. They work fine on mi Mix 2 (and there audio quality looks far better to me)
Click to expand...
Click to collapse
Hmmm. I never tried an adapter on my OP6. Just the Pixel Buds. My daughter has my old OP6 now...otherwise I would try the adapter I just got for a friend as it works on my OP6T. I do know some adapters only work on certain phones. This is the adapter I bought (it list OnePlus)
Pixel 2 USB C to 3.5mm Headphone Jack Adapter，Stouchi Nylon Braided DAC Chipset Type C to 3.5mm Audio Adapter USB C to 3.5mm with Realtek Noise Reduction Chip for Pixel 2/ XL, HTC U11, Essential ph-1 https://www.amazon.com/dp/B07BQQHV64/ref=cm_sw_r_cp_apa_i_NmW.BbZ7356W8

jerrywmilton said:
Hmmm. I never tried an adapter on my OP6. Just the Pixel Buds. My daughter has my old OP6 now...otherwise I would try the adapter I just got for a friend as it works on my OP6T. I do know some adapters only work on certain phones. This is the adapter I bought (it list OnePlus)
Pixel 2 USB C to 3.5mm Headphone Jack Adapter，Stouchi Nylon Braided DAC Chipset Type C to 3.5mm Audio Adapter USB C to 3.5mm with Realtek Noise Reduction Chip for Pixel 2/ XL, HTC U11, Essential ph-1 https://www.amazon.com/dp/B07BQQHV64/ref=cm_sw_r_cp_apa_i_NmW.BbZ7356W8
Click to expand...
Click to collapse
Thank you, please let me know if you can make it work in USB C. I'm really curious., If it is going to work, I will definitely buy a better adapter.

USB Type C to 3.5mm jack are not supported

Is there a possibility with Root, 3.5 mm jack adapters that are not supported by the u12 + anyway to operate on the device? I wanted to test one of Huawei, there came the message "this is not a htc adapter"

I got two generic ones and they work fine. Maybe it is the Huawei adaptor that is not working?
Not sure if I can post links so moderators can remove if so...
This is the one I usually use - https://www.amazon.com/gp/product/B076B2MJKV/ref=oh_aui_search_asin_title?ie=UTF8&psc=1

I do not know what it is. I have now ordered the adapter from the Razer phone. I hope that this is recognized. It would be interesting to know if you can change that on the software side, that other adapters will be recognized as well.
what irritated me is that the original HTC adapter is required.

you can only use an USB dongle with a DAC inside. the razer one will work fine, huawei one doesn't has a DAC inside, so this will never work

DeeZZ_NuuZZ said:
you can only use an USB dongle with a DAC inside. the razer one will work fine, huawei one doesn't has a DAC inside, so this will never work
Click to expand...
Click to collapse
Not true. You can use the ones without DAC (passive) but you need to use app like "Lesser AudioSwitch" to route sound through adapter. Sound quality is very bad.
Apple USBC audio adapter works with nice sound quality but it hangs phone when inserted, at least my phone. Solution is to reboot phone with adapter inserted.