Issues when plugging in headphones

I have some Bose over-ear headphones that I've been using for years and years with no issue. But every time I plug them into the LG V10, the Google Voice Input screen shows up (part of Google Now I believe). If my phone is locked, it starts talking to me about the things I can say into my microphone.

This is ridiculous, because this is as basic of a set of headphones as you can get, and clearly not a headset. It has 3 conductors (2 rings on the male 3.5mm connection). Headsets have 4 conductors (3 rings on the male 3.5mm connection). I cannot for the life of me figure out how to make this stop and it is driving me crazy.

03/28/2016 Edit: Marshmallow (Android 6.0) update has fixed this issue for me!
05/12/2016 Edit: No it didn't.

I'm in the same situation. I work out with the phone in my pocket and the music would stop and I hear the robot digital assistant lady start talking.

Posted via the Android Central App

It just told me how to enable wired headsets this time (weird), but it was talking too fast and I was not ready and missed the instructions.

Edit: It told me how to go enable searching through a wired headset while the device is locked. Not what I want.

Bump

Mine did that the first few times I plugged in my headphones, now it went away. I remember one of my older phones did that too.

Please post if it comes back. Mine has not stopped since I got my phone.

Sounds like what I went through with my G3. Looks like they may be using the same auxiliary ports on these devices. Thankfully, my G4 has not had these issues at all!

Originally Posted by GrooveRite

Sounds like what I went through with my G3. Looks like they may be using the same auxiliary ports on these devices. Thankfully, my G4 has not had these issues at all!

I had that issue with my G3 also

I'm curious, do you have the audio feature enabled within your accessibility options under settings?

I just checked with my Bose QC15's and no audio assist type prompts, just music (and I was using the cord with the in-line controls). Also have not experienced audio prompts with my Klipsch S4's.

Originally Posted by LuvMusic

I'm curious, do you have the audio feature enabled within your accessibility options under settings?

I just checked with my Bose QC15's and no audio assist type prompts, just music (and I was using the cord with the in-line controls). Also have not experienced audio prompts with my Klipsch S4's.

I've checked every setting on my phone and I simply cannot get this to stop happening.

I'm re-bumping this to the top now that more people have this phone and have hopefully discovered this thread. I turned off my HiFi DAC, and the "headset" icon showed up in my notification bar. I am obviously not using a headset.

Attachment 206898

Edit: I found these two links to reddit posts regarding the G3 having the same issue. I've tried the app they suggest (SoundAbout) and it doesn't seem to work for me. I don't want another app having to run constantly in the background in order to do the simple task of correctly detecting my headphones. The one thing that I did get out of these posts is if I quickly and forcefully cram my headphones in, it detects them as headphones. So there's that.

https://www.reddit.com/r/LGG3/commen...dentifying_my/

https://www.reddit.com/r/LGG3/commen...er_headphones/

Originally Posted by Andrew Bonner

I'm re-bumping this to the top now that more people have this phone and have hopefully discovered this thread. I turned off my HiFi DAC, and the "headset" icon showed up in my notification bar. I am obviously not using a headset.

Attachment 206898

Edit: I found these two links to reddit posts regarding the G3 having the same issue. I've tried the app they suggest (SoundAbout) and it doesn't seem to work for me. I don't want another app having to run constantly in the background in order to do the simple task of correctly detecting my headphones. The one thing that I did get out of these posts is if I quickly and forcefully cram my headphones in, it detects them as headphones. So there's that.

https://www.reddit.com/r/LGG3/commen...dentifying_my/

https://www.reddit.com/r/LGG3/commen...er_headphones/

I did have the same issue briefly on my V10. Funny part is, I have yet to figure out how to trigger the voice assistant on purpose (aside from "OK Google"). Anyways, After I adjust the settings you mentioned earlier, to allow headphone controls while the device is locked (my headphone had no such controls), the problem went away. If that doesn't fix the problem, try a full factory reset ( I know, that sucks). If it still doesn't go away, warranty it out. Perhaps there is a real problem with your phone.

I just noticed this the other day. I had only used bluetooth for music streaming until last night. I plugged my phone into my car stereo, and I heard a woman's voice but I had no idea what it was. It only lasted a couple of seconds and the music played fine. Seemed like a minor annoyance in the grand scheme of things, but it would be nice if it didn't do it. I'll keep my eyes on this post tho, to see if a solution pops up or if I run across a solution.

Now that this phone has been out there for another month, has anyone experienced this? It has still been happening to me. Every time I plug in my headphones, the google app launches and listens for my command. Then when I say nothing, it says "If you just said something, I didn't hear what it was."

This must be frustrating for you. I have not experienced the problem. What music player are you using?

Originally Posted by LuvMusic

This must be frustrating for you. I have not experienced the problem. What music player are you using?

Google Play Music, Amazon Music

I was having the exact same issue with my LG G4 and it was driving me nuts! I think I've eventually found the setting that stops it. No doubt there'll be a difference on your phone, but it might give you an idea where to look.

Go to: General settings > Language & Input > Speech - Voice Search > Hands Free then make sure "Wired Headsets" is disabled.

Hope that helps, I know how irritating that robot is!

Originally Posted by Geordieclare

I was having the exact same issue with my LG G4 and it was driving me nuts! I think I've eventually found the setting that stops it. No doubt there'll be a difference on your phone, but it might give you an idea where to look.

Go to: General settings > Language & Input > Speech - Voice Search > Hands Free then make sure "Wired Headsets" is disabled.

Hope that helps, I know how irritating that robot is!

I tried that ages ago, unfortunately. It's been disabled (unchecked) for weeks and weeks now. Still does it every time I plug in headphones.

Just tried it again.

Open Google Noise
Unsuccessful Google Noise
"If you just said something, I didn't hear what it was"

When you are listening to music, does it cut out from time to time. Like just stops play all on its own??

Posted via the Android Central App

Happens to me too. Highly aggravating.

Posted via the Android Central App

Me, also.

I have a pair of Sennheiser HD 650s that I sometimes try to wear while taking the dog for a walk, and my phone will start/stop over and over and over again until I get mad and unplug it just to stop the annoyance (hitting "stop" in the music app doesn't do any good). The Google Voice screen will also pop up randomly, even if I'm trying very hard to keep from moving the phone (like when watching something on Hulu while laying in bed).

The only thing I can figure is that the headphone plug is making intermittent connection with the ground or mic contact in the headphone jack of the phone. The way you can cause the play/pause feature to work is by shorting the mic contact to ground for a short period of time, then returning to an open state. When you are using headphones that don't have a mic or remote (that is, they use a 3-conductor, or TRS plug) the mic contact is always shorted to ground. So in order for this to happen, the headphone has to lose contact with either ground or mic, then make contact again for a short period, then lose contact again, which fools the phone into believing that you just hit the play/pause button (then possibly causing it to think that you are continually holding the button down again after having let go or making the phone think that you quickly plugged in a different set of headphones that don't have a mic).

In order for the Google Voice search screen to pop up, the only difference is that the period of time that the mic and ground contacts were shorted -- in between the losses of contact -- lasts a little longer. You can hold the play/pause button for a couple of seconds (maybe less) on a headset with a remote to cause Google Voice to pop up normally.

Edit: sorry, didn't realize this one got posted... I meant to not post it and finish a more comprehensive post later (which you can see below), so if someone could delete this one for me, that would be great. Otherwise, I hope you all can forgive my double-post) :(

Originally Posted by rfmike

When you are listening to music, does it cut out from time to time. Like just stops play all on its own??

Posted via the Android Central App

It's usually fine after I dismiss the original Google Voice interruption. Doesn't happen again.

I did notice in the car the other day while hooked up to AUX that when I moved my phone the wrong way that it would interrupt, but it doesn't do that when I'm listening to music at work.

Me, also.

I have a pair of Sennheiser HD 650s that I sometimes try to wear while taking the dog for a walk, and my phone will start/stop over and over and over again until I get mad and unplug it just to stop the annoyance (hitting "stop" in the music app doesn't do any good). The Google Voice screen will also pop up randomly, even if I'm trying very hard to keep from moving the phone (like when watching something on Hulu while laying in bed).

The only thing I can figure is that the headphone plug is making intermittent connection with the ground or mic contact in the headphone jack of the phone. The headphone plug can be laid out in two different ways: Tip, ring, sleeve; or tip, ring, ring, sleeve. A normal headphone plug (with no mic or remote) uses the tip for the left speaker, the ring for the right, and the sleeve for common ground of both speakers. A headset uses the tip for left audio, the first ring for right audio, and the second ring and sleeve for the mic and a common ground for both speakers and the mic (there are two different standards for whether the second ring or the sleeve is the mic or ground, but no matter which way these are laid out, shorting the two of them together produces the same result). The way you can cause the play/pause feature to work is by shorting the mic contact to ground for a short period of time, then returning to an open state. When you are using headphones that don't have a mic or remote (that is, they use a 3-conductor, or TRS plug) the mic contact is always shorted to ground. So in order for this to happen, the headphone has to lose contact with ground and/or mic, then make contact between the two again for a short period, then lose contact again, which fools the phone into believing that you just hit the play/pause button. In order for the Google Voice search screen to pop up, the only difference is that the period of time that the mic and ground contacts were shorted -- in between the losses of contact -- lasts a little longer. You can hold the play/pause button for a couple of seconds (maybe less) on a headset with a remote to cause Google Voice to pop up normally.

I have noticed, at least with my phone, that the amount of play in the headphone jack is pretty extreme. That means that just stressing the headphone plug from one angle to the opposing angle could cause this open-short-open circuit to happen. Imagine a pair of pencils on a desk with a ruler laid across them. If the plug is at an angle, only one is making contact (imagine for the sake of argument that the underscore is "making contact" and the hyphen "isn't"):
_____---------
.....O......O.....

Then, as the plug starts moving, they both make contact:
___________
.....O......O.....

This is where the phone says "Hey, they are pressing the play/pause button!" Now, the plug finally gets pushed all the way to the opposite side:
--------______
.....O......O.....

And once again you have an open circuit and this tells the phone that you "pressed and released the play/pause button." If the amount of time that the middle position was held lasted longer than a normal short click, the phone reads that as meaning that you wanted to bring up the Google Voice app. This what I believe is happening in some of our phones. When I plug in a pair of Bose in-ear headphones, I don't have any issues, because the mic and ground contacts never get shorted together unless the play/pause button is pressed AND the headphone plug is making contact with all four jack contacts, so no matter how I wiggle the plug, nothing happens.

One possible fix would be to create a short cable with a TRS jack and a TRRS plug, and never connect the second ring or the sleeve (pick one) of the jack to the sleeve of the plug (normal adapters would connect both the second ring and the sleeve of the jack to the sleeve of the plug). I'll have to order some parts to see if I can make this work, and will try to remember to get back here to report whether it works. My only worry is that not connecting the mic and ground together will cause the phone to be confused as to whether or not a TRS or TRRS jack has been plugged in. Apple devices do a series of checks to figure out what has been plugged in, and this could cause an Apple device to not output any sound to the headphone jack. I'm not sure if Android phones do a similar check, or if they simply believe the "jack sense" output of modern headphone jacks (most 1/8" [3.5mm] headphones jacks have a separate pin that gets shorted to ground [I believe] when a headphone plug is inserted into the jack to notify to the device that it should reroute sound output from the internal speaker to the headphone jack).

Edit: Please reply if you know any of what I just said to be false. I haven't gone looking for datasheets on anything, and only did a cursory glance at what the internet claims to be true about the layout of TRRS plugs via Google image search. Most of what I have said is just "the way I understand things to be", and I have been proven wrong on my assumptions about other things before. :p

Originally Posted by N0BOX

Me, also.

I have a pair of Sennheiser HD 650s that I sometimes try to wear while taking the dog for a walk, and my phone will start/stop over and over and over again until I get mad and unplug it just to stop the annoyance (hitting "stop" in the music app doesn't do any good). The Google Voice screen will also pop up randomly, even if I'm trying very hard to keep from moving the phone (like when watching something on Hulu while laying in bed).

The only thing I can figure is that the headphone plug is making intermittent connection with the ground or mic contact in the headphone jack of the phone. The headphone plug can be laid out in two different ways: Tip, ring, sleeve; or tip, ring, ring, sleeve. A normal headphone plug (with no mic or remote) uses the tip for the left speaker, the ring for the right, and the sleeve for common ground of both speakers. A headset uses the tip for left audio, the first ring for right audio, and the second ring and sleeve for the mic and a common ground for both speakers and the mic (there are two different standards for whether the second ring or the sleeve is the mic or ground, but no matter which way these are laid out, shorting the two of them together produces the same result). The way you can cause the play/pause feature to work is by shorting the mic contact to ground for a short period of time, then returning to an open state. When you are using headphones that don't have a mic or remote (that is, they use a 3-conductor, or TRS plug) the mic contact is always shorted to ground. So in order for this to happen, the headphone has to lose contact with ground and/or mic, then make contact between the two again for a short period, then lose contact again, which fools the phone into believing that you just hit the play/pause button. In order for the Google Voice search screen to pop up, the only difference is that the period of time that the mic and ground contacts were shorted -- in between the losses of contact -- lasts a little longer. You can hold the play/pause button for a couple of seconds (maybe less) on a headset with a remote to cause Google Voice to pop up normally.

I have noticed, at least with my phone, that the amount of play in the headphone jack is pretty extreme. That means that just stressing the headphone plug from one angle to the opposing angle could cause this open-short-open circuit to happen. Imagine a pair of pencils on a desk with a ruler laid across them. If the plug is at an angle, only one is making contact (imagine for the sake of argument that the underscore is "making contact" and the hyphen "isn't"):
_____---------
.....O......O.....

Then, as the plug starts moving, they both make contact:
___________
.....O......O.....

This is where the phone says "Hey, they are pressing the play/pause button!" Now, the plug finally gets pushed all the way to the opposite side:
--------______
.....O......O.....

And once again you have an open circuit and this tells the phone that you "pressed and released the play/pause button." If the amount of time that the middle position was held lasted longer than a normal short click, the phone reads that as meaning that you wanted to bring up the Google Voice app. This what I believe is happening in some of our phones. When I plug in a pair of Bose in-ear headphones, I don't have any issues, because the mic and ground contacts never get shorted together unless the play/pause button is pressed AND the headphone plug is making contact with all four jack contacts, so no matter how I wiggle the plug, nothing happens.

One possible fix would be to create a short cable with a TRS jack and a TRRS plug, and never connect the second ring or the sleeve (pick one) of the jack to the sleeve of the plug (normal adapters would connect both the second ring and the sleeve of the jack to the sleeve of the plug). I'll have to order some parts to see if I can make this work, and will try to remember to get back here to report whether it works. My only worry is that not connecting the mic and ground together will cause the phone to be confused as to whether or not a TRS or TRRS jack has been plugged in. Apple devices do a series of checks to figure out what has been plugged in, and this could cause an Apple device to not output any sound to the headphone jack. I'm not sure if Android phones do a similar check, or if they simply believe the "jack sense" output of modern headphone jacks (most 1/8" [3.5mm] headphones jacks have a separate pin that gets shorted to ground [I believe] when a headphone plug is inserted into the jack to notify to the device that it should reroute sound output from the internal speaker to the headphone jack).

Edit: Please reply if you know any of what I just said to be false. I haven't gone looking for datasheets on anything, and only did a cursory glance at what the internet claims to be true about the layout of TRRS plugs via Google image search. Most of what I have said is just "the way I understand things to be", and I have been proven wrong on my assumptions about other things before. :p

I read a little bit about this in the Reddit posts I linked WAAAAY ABOVE. I bet that is the issue. Is the TRS male to TRRS female not something that exists already?

Yes, there already exist adapters to go from TRS to TRRS, but they connect the "RS" of the TRRS plug to the "S" of the TRS jack, and if the issue involves contacts of the TRRS jack of the phone losing contact with the "S" of the TRS or the "RS" of the TRRS plug, then the same issue will continue. If you were to make sure that either the second "R" or the "S" of the TRRS plug is NOT connected to the "S" of the TRS jack, then that would prevent the issue. My only fear is that the phone checks whether there is a TRS or TRRS plug inserted, and if it does, then this might confuse the phone.

I have the same issue with my hd 700's. Every time I plug my headphones in I get that google prompt. My guess is the Jack is touching something inside the phone is causing this. This is my second v10 as my first one the headphone jack got messed up because I didn't buy the adapter for the 1/4 to 3.5mm and the weight of the jacks completely messed up the phone. I couldn't move a centimeter without that google prompt showing up. I still have this issue with my second v10 but it has drastically reduced the prompt now that I use this adapter.

Posted via the Android Central App

Maybe this will help. Going to give it a try.

Posted via the Android Central App

Sorry if you tried this. Only way I could replicate was saying "ok google" after enabling it for wired headsets in google now . I'm coming from a Nexus 6 and that "ok google" voice command is very sensitive. On the Nexus you can have the phone always listening for it even while the screen is locked and off. I've had it triggered listening to music, podcasts, talking to people without ever saying "Ok Google". You can turn this off by holding down the home button and swiping up, then hit the hamburger menu in the upper left corner, settings, voice, hands free it will give you an option to toggle detection over blue tooth and or wired headsets. Or just turn the detection completely off.

I've had everything even remotely related to "Ok Google" or "Google Now" turned off since I bought the phone, but it still pops up whenever my headphones are plugged in. Not only is there a hardware issue with the headphone jack, but there is a software issue whereby the Google voice search CANNOT BE DISABLED. You can prevent it from popping up when the phone is locked, but you can't turn it off for when the phone screen is on. There is simply no option to disable Google voice search completely.

So, our only hope is that some inline adapter can be used to prevent this issue in hardware. I have a Digi-key order on the way, so I might be able to get something put together over the weekend.

That "OK Google" thing never worked right for me. No matter how clearly or loudly I spoke/yelled at my phone. People would stare at me like I was some lunatic yelling at my phone. Mine too did pop up a couple times when I plugged in my headphones, not every time though... so that was the last straw. It was one of the first things I defeated when I got my phone.

Settings => Language & Input => Google voice typing => "OK Google" detection

From there, slide the "From the Google app" toggle to the OFF position.

It hasn't bothered me in almost 2 months now.

Originally Posted by kramer5150

Settings => Language & Input => Google voice typing => "OK Google" detection

From there, slide the "From the Google app" toggle to the OFF position.

That doesn't turn it off for me, unfortunately.

I have nothing new to add to this thread, only that I have this same problem every time I plug in headphones. Bought mine less than a month ago.

Success!! (as far as I can tell, anyway)

I ordered some parts from Digi-key (an online electronics supplier):
Tensility International Corp 10-00341
Switchcraft Inc. 35LJNS (There is also a gold-plated part, P/N 35LJNAUS, but it was almost $4.50 more)

I would have posted the links to the actual web pages on Digikey's site, but I don't have enough posts, so you can search for those part numbers if you choose to do this yourself. You can also look for similar parts or build the cable assembly yourself from scratch. I went for "decent quality" and "easy".

I found through experimentation that the LG V10 utilizes the CTIA pinout order for 4-conductor headsets (there is also an OMTP standard that transposes the Ground and Microphone contacts that is used by some other phones/companies). This means that the V10 expects the Tip to be Left+, the first Ring to be Right+, the second Ring to be Ground (Left-, Right-, and Mic-), and the Sleeve to be Mic+. So, I connected the cable assembly's red wire to the tip contact, the white wire to the ring contact, and the green wire to the shield/ground/sleeve contact. The black wire I just cut off and didn't use, and the shielding from the cable was also just cut off so that it wouldn't make contact with anything (I made sure that the shielding wasn't connected to any of the plug's contacts before I did this... I did some reading online that told me not to connect the shielding to signal ground in audio cables).

So, with a little hair pulling, a flux pen, some solder, and a soldering iron you can make your own hardware fix for this issue. Or LG could buy some headphone jacks that aren't crap.

Attachment 216199

I also bought a second set of cable assembly/3.5mm jack so that I can play with building my own custom cable that has an Android-compatible remote on a short wire (that way I can add a remote to a normal pair of headphones, and the short wire would allow me to run a line for the remote from my pocket (where my phone generally lives) up to a lapel clip. The remotes that Android phones use introduce a specific resistance across the Mic and Ground contacts, so adding a couple of resistors (one for Vol+ and one for Vol-) and a button for play/pause/next/prev on a small circuit board should give me all the control I am used to getting from my Bose in-ear sport headphones that I use with my iPod Touch at the gym.

Originally Posted by N0BOX

That doesn't turn it off for me, unfortunately.

You re CORRECT sir... the steps I outlined above most definitely do not work. I think I am tricking my V10 into working because the mic/volume-cabled headphones I own are for iOS (being a recent convert). So I think the V10 sees an iOS cable just like a simple TRS connector headphone without vol module although the mic still works fine which for me is really the important part. I am willing to bet proper android cabled headphones will have this problem for me as well. I was at Frys yesterday and I plugged in the Sennheiser momentum headphone demo board and the annoying "OK Google" thing kept popping up at random.

Originally Posted by N0BOX

Success!! (as far as I can tell, anyway)

I ordered some parts from Digi-key (an online electronics supplier):
Tensility International Corp 10-00341
Switchcraft Inc. 35LJNS (There is also a gold-plated part, P/N 35LJNAUS, but it was almost $4.50 more)

I would have posted the links to the actual web pages on Digikey's site, but I don't have enough posts, so you can search for those part numbers if you choose to do this yourself. You can also look for similar parts or build the cable assembly yourself from scratch. I went for "decent quality" and "easy".

I found through experimentation that the LG V10 utilizes the CTIA pinout order for 4-conductor headsets (there is also an OMTP standard that transposes the Ground and Microphone contacts that is used by some other phones/companies). This means that the V10 expects the Tip to be Left+, the first Ring to be Right+, the second Ring to be Ground (Left-, Right-, and Mic-), and the Sleeve to be Mic+. So, I connected the cable assembly's red wire to the tip contact, the white wire to the ring contact, and the green wire to the shield/ground/sleeve contact. The black wire I just cut off and didn't use, and the shielding from the cable was also just cut off so that it wouldn't make contact with anything (I made sure that the shielding wasn't connected to any of the plug's contacts before I did this... I did some reading online that told me not to connect the shielding to signal ground in audio cables).

So, with a little hair pulling, a flux pen, some solder, and a soldering iron you can make your own hardware fix for this issue. Or LG could buy some headphone jacks that aren't crap.

Attachment 216199

I also bought a second set of cable assembly/3.5mm jack so that I can play with building my own custom cable that has an Android-compatible remote on a short wire (that way I can add a remote to a normal pair of headphones, and the short wire would allow me to run a line for the remote from my pocket (where my phone generally lives) up to a lapel clip. The remotes that Android phones use introduce a specific resistance across the Mic and Ground contacts, so adding a couple of resistors (one for Vol+ and one for Vol-) and a button for play/pause/next/prev on a small circuit board should give me all the control I am used to getting from my Bose in-ear sport headphones that I use with my iPod Touch at the gym.

So, could I purchase this item and get the same results? It seems all that needs accomplished is the reversal of the GND and MIC wires.

Amazon.com: Honsky Universal CTIA to OMTP 3.5mm Male to 3.5mm Female Earphone Adapter Cable - Red: Cell Phones & Accessories

Thanks for your post!!!!!

Edit, it seems that this is a bad product, based on the reviews. However, if it does what it says is that what we need?

Unfortunately, that wouldn't solve the problem. What our problem is is that the headphones we are using cause the GND and MIC wires to be shorted together (this is normal, and a phone should be able to deal with this without any trouble) and that the headphone jack allows the plug to wiggle, causing the GND or MIC (or both) contacts to lose contact with the headphone plug. This causes the phone to think that we are using a headset (instead of plain old headphones) and that we have been pressing the play/pause button intermittently. The "adapter" I created only does one thing: it prevents the MIC contact from ever being connected to anything. That is why I didn't attach the black wire in the photo to anything.

If you could somehow open that adapter up and snip the correct wire, it may work, but it would ONLY work with a standard pair of headphones, not a phone headset with the mic and remote. You could also snip the correct wire in a standard 3.5mm stereo headphone (3 conductor) to 3.5mm stereo headset (4 conductor) adapter, but trying to open up one of those short cables, identifying the correct wire, and snipping it so that it doesn't ever make contact without messing up the other tiny wires inside would be more work than building a new cable from scratch.

What that product you linked to does is adapt a phone headset for, say, an international model Nokia phone so that it would work with the LG V10. It wasn't built to adapt a normal pair of headphones to a cell phone. I have seen products that do add a remote and microphone to a regular pair of headphones, but the remote ends up too close to the phone to be useful and to use the mic, you have to clip a wad of the 3' to 6' of cable your headphones came with to your lapel where the mic is. That is why I would like to put a short adapter cable next to the phone, then run a separate wire up to the lapel for a remote and possibly a mic. I'm going to see if I can design a little board with three buttons , some resistors, and a mic on it that could be put inside a 3D printed case. Then I could attach that to my current version of this LG V10 "fix" and it would also be useful for other people who have perfectly working set of phone/headphones to which they would like to add a mic/remote. Even though those remote/mic adapter cables aren't designed to be useful, they would actually fix the problems many here are having with normal pairs of headphones.

You could look for these search terms on Amazon:
Scosche control adapter for ipod
Griffin control headphone adapter for ipod
Monster iSoniTalk Microphone Headphone Adapter for iPhone

They are all listed to work for iPod Touch or iPhone, but they would at least work to fix this issue with the LG V10. The only issue you would have with their 'features' would be that the volume control buttons won't work with any Android phones (Apple uses some proprietary digital communications protocol for their volume controls, where Android shorts the MIC and GND contacts through different values of resistors to change the volume or 0 ohms to signal play/pause/voice search). If you can find one that is built for Android phones, that would be a better choice, but it was hard for me to even find these adapters for use with the iPhone.

So, with a little it of testing and prototyping, I managed to put together a neat Headphones-to-Headset adapter that is compatible with most Android phones. I put another cable together basically the same way, but instead of leaving the black wire disconnected, I ran it and another wire from the GND terminal to a breadboard. On the breadboard I placed a small condenser mic, a few resistors, and three momentary pushbuttons. This gave me the ability to hit play/pause/next track/prev track/Google Voice Assist, Vol+, and Vol-, and I was able to voice dial my phone, have a conversation using the mic on the breadboard and my Sennheiser HD 650s, and listen to and control music using the Tidal streaming music app.

Unfortunately, when I tried to create a soldered version of the remote/mic I ended up shaving a bit of insulator off the wire and by the time I had tried to fix it everything was completely trashed. So, I have ordered a few sets of new parts so I can try to put together a working prototype. If I can I'll have a really nice, high-quality headset adapter for my Sennheiser HD 650 headphones that I might be able to get worked into a small product run. A side effect of using this type of adapter would be that the problems we have all been having would also be fixed. I'd just have to figure out how to design a small PCB and a plastic case for it to live in.

It seems like ill have days that go by without the Google voice search thing popping up, and then days where every time i plug headphones or my cars aux cable in the Google voice search thing will pop up. It seems very hit or miss.

The only real solution I can see is sticking with audio hardware whose male plug connectors use 4 conductors instead of 3 sadly. Kinda interesting really how this was present as far as I know since the G3 but was never really fixed.

Posted via the Android Central App

Originally Posted by HNNNNNGHHH

The only real solution I can see is sticking with audio hardware whose male plug connectors use 4 conductors instead of 3 sadly. Kinda interesting really how this was present as far as I know since the G3 but was never really fixed.

Posted via the Android Central App

Yeah, and it's sad because at the moment this phone is one of the favorites in a thread labelled "Best smartphone for audiophile" on the Head-Fi forums. It looks like there are several new phones in the works that are going the way of the G3, G4, and V10 that are pairing a quality DAC with the necessary amplifiers to drive high-impedance studio-quality headphones (which was my main reason for choosing the V10). I'm lucky that I treat electronics as a hobby, so I had the tools I needed to diagnose and build a fix for my phone, but most people don't.

That said, would people here be interested in buying an adapter if I were to put some together? I couldn't find any forum rules other than the ToS for the site, so I'm not sure if it is against the rules to offer something like that for sale. I wouldn't know how much it would cost, and I'd have to find some parts that are less expensive (the parts I used for mine were bought out of convenience... I already had an account at Digi-key, and those were the only parts that came up that didn't look like cheap plastic Radioshack style connectors). If there is some interest, I will see if I can find a source of decent-quality connectors and wire that doesn't cost too much and try to come up with a price.

I wonder if this is carrier dependent?
I only have gotten the OK google thing 2-3 times ever. FWIW I use a 1/8M-1/4F Grado adapter with my traditional headphones. The only 1/8TRS phones I directly plug in to my V10 are various Jays in-ears and Bose sound true. Both of which have mic/vol cables intended for use on iOS-Apple... could this be the difference?

I have been considering upgrading my senn HD558 cable to one with a microphone. Should I buy one intended for iOS or Android?

One age old drawback to the TRS connector is it will briefly short the ring and sleeve when its inserted into the jack. Headphone amp designers (single ended variety) need to account for this when they are designing the circuit. The circuit needs to be robust and stable enough to handle the brief shorting. Doesn't seem like LG or the android OS has taken this into account. You would think deactivating "OK Google" detection under Language and input settings SHOULD kill it outright.

Originally Posted by N0BOX

Yeah, and it's sad because at the moment this phone is one of the favorites in a thread labelled "Best smartphone for audiophile" on the Head-Fi forums. It looks like there are several new phones in the works that are going the way of the G3, G4, and V10 that are pairing a quality DAC with the necessary amplifiers to drive high-impedance studio-quality headphones (which was my main reason for choosing the V10). I'm lucky that I treat electronics as a hobby, so I had the tools I needed to diagnose and build a fix for my phone, but most people don't.

That said, would people here be interested in buying an adapter if I were to put some together? I couldn't find any forum rules other than the ToS for the site, so I'm not sure if it is against the rules to offer something like that for sale. I wouldn't know how much it would cost, and I'd have to find some parts that are less expensive (the parts I used for mine were bought out of convenience... I already had an account at Digi-key, and those were the only parts that came up that didn't look like cheap plastic Radioshack style connectors). If there is some interest, I will see if I can find a source of decent-quality connectors and wire that doesn't cost too much and try to come up with a price.

I'd probably pay ~$7-8 for it, but no more. I now listen to my music through my computer at work, and listen on bluetooth in both cars.

Originally Posted by N0BOX

Yeah, and it's sad because at the moment this phone is one of the favorites in a thread labelled "Best smartphone for audiophile" on the Head-Fi forums. It looks like there are several new phones in the works that are going the way of the G3, G4, and V10 that are pairing a quality DAC with the necessary amplifiers to drive high-impedance studio-quality headphones (which was my main reason for choosing the V10). I'm lucky that I treat electronics as a hobby, so I had the tools I needed to diagnose and build a fix for my phone, but most people don't.

That said, would people here be interested in buying an adapter if I were to put some together? I couldn't find any forum rules other than the ToS for the site, so I'm not sure if it is against the rules to offer something like that for sale. I wouldn't know how much it would cost, and I'd have to find some parts that are less expensive (the parts I used for mine were bought out of convenience... I already had an account at Digi-key, and those were the only parts that came up that didn't look like cheap plastic Radioshack style connectors). If there is some interest, I will see if I can find a source of decent-quality connectors and wire that doesn't cost too much and try to come up with a price.

Is this an issue that can be fixed over a software update???

Originally Posted by N0BOX

Yeah, and it's sad because at the moment this phone is one of the favorites in a thread labelled "Best smartphone for audiophile" on the Head-Fi forums. It looks like there are several new phones in the works that are going the way of the G3, G4, and V10 that are pairing a quality DAC with the necessary amplifiers to drive high-impedance studio-quality headphones (which was my main reason for choosing the V10). I'm lucky that I treat electronics as a hobby, so I had the tools I needed to diagnose and build a fix for my phone, but most people don't.

That said, would people here be interested in buying an adapter if I were to put some together? I couldn't find any forum rules other than the ToS for the site, so I'm not sure if it is against the rules to offer something like that for sale. I wouldn't know how much it would cost, and I'd have to find some parts that are less expensive (the parts I used for mine were bought out of convenience... I already had an account at Digi-key, and those were the only parts that came up that didn't look like cheap plastic Radioshack style connectors). If there is some interest, I will see if I can find a source of decent-quality connectors and wire that doesn't cost too much and try to come up with a price.

Is this an issue that can be fixed over a software update???

Originally Posted by Andrew Bonner

Is this an issue that can be fixed over a software update???

I was wondering this too... I installed a Verizon update mid January FWIW. Not exactly certain what was done in the update. The general consensus is it fixed the fingerprint scanner bug among other things. Its still a version of lollipop though.

Originally Posted by Andrew Bonner

Is this an issue that can be fixed over a software update???

This is a hardware issue with the headset jack of the phone, but a software fix appears to be possible. It looks to me like a daemon (background program) that monitors the jack and tries to detect what type of plug has been inserted could be created.

Detection should be possible, since an electret condenser microphone element will appear as a resistive load across the MIC and GND terminals of at least 1Kohm (a short of the terminals would appear as less than 1ohm, usually, and the Android specs require that the mic element have at least 1Kohm of DC resistance). Anything that is plugged in that provides an open or short circuit, which you would expect from a normal TRS stereo or TS mono plug, should cause the jack daemon to turn off remote control detection in software.

I don't know why such a daemon isn't already part of the stock ROM from LG. The Android documentation clearly sets out what headset manufacturers must do to comply with Android's specs, and it is fairly obvious that the mic DC resistance was chosen for the purpose of allowing for automatic detection of the type of device that has been plugged in. If Android doesn't have a jack detection daemon in its stock AOSP build, then it would still be simple for a hardware manufacturer to provide their own. Android might not include one by default because the device running Android may not always have a headset jack. It's possible that it might be a set top box with only HDMI or an optical output, or a tiny computer with separate headphone/line out and microphone/line in jacks. That would mean that manufacturers who provide TRRS jacks for headset use should create their own jack daemon that is tailored to work with their hardware.

Hope this helps. Maybe we should be beating down LG's door to get a jack daemon included. They already have the hardware in the phone to precisely detect resistive loads, because the phone can detect Vol+, play/pause, and Vol- signals, which are resistive loads of 240ohms, 0ohms, and 470ohms respectively.

Originally Posted by kramer5150

I was wondering this too... I installed a Verizon update mid January FWIW. Not exactly certain what was done in the update. The general consensus is it fixed the fingerprint scanner bug among other things. Its still a version of lollipop though.

I think the Marshmallow update fixed this issue!

Originally Posted by Andrew Bonner

I think the Marshmallow update fixed this issue!

I haven't had the issue since marshmallow yet either. I've plugged into the headphone jack at least a dozen times since too, and no Google voice search pop-up yet.

BUMP

Still good, not one time has it popped up since marshmallow.

Originally Posted by jasonb

Still good, not one time has it popped up since marshmallow.

Me either. I listened to music with my suspect headphones the other day and sat there for 10 minutes plugging and unplugging to be sure.

I'm glad that Marshmallow fixed this for some of you, but it didn't for my v10.

I have the same problem - my Koss PortaPros, Phillips earbuds, and any Aux cord is recognized as a headset, and toggles Google Now or playback controls when the cord is slightly bumped. Without fail.

I've sent my phone in to the LG repair center TWICE now.
The first time, they replaced the headphone jack and it didn't fix the problem at all.
Second time around, they replaced the whole motherboard. The problem disappeared for about 4 weeks before returning in full force - about a week after updating to Marshmallow.
The suggested actions in this thread do not work, neither does running a full factory restore.
I've had it with LG. I paid nearly $800 for this phone and I can't even listen to music on it.

Originally Posted by Anthony Siracuse

I'm glad that Marshmallow fixed this for some of you, but it didn't for my v10.

I have the same problem - my Koss PortaPros, Phillips earbuds, and any Aux cord is recognized as a headset, and toggles Google Now or playback controls when the cord is slightly bumped. Without fail.

I've sent my phone in to the LG repair center TWICE now.
The first time, they replaced the headphone jack and it didn't fix the problem at all.
Second time around, they replaced the whole motherboard. The problem disappeared for about 4 weeks before returning in full force - about a week after updating to Marshmallow.
The suggested actions in this thread do not work, neither does running a full factory restore.
I've had it with LG. I paid nearly $800 for this phone and I can't even listen to music on it.

Mine has popped up the Google Prompt a few times since I posted my message. So, I guess it isn't fixed? I'll edit the thread title.

haven't seen it on mine since marshmallow and I plug things into mine every single day.

settings/language and keyboard/google voice typing/"ok google" detection. Enabled "from any screen". Did the voice training (say ok google 3x).

fixed this issue. for 10 min so far

I also have this issue and it's driving me crazy. This is a $800 phone for God's sake. How could they buy such a cheap audio port??

Especially since they tout the phone's audio DAC. If any one knows a fix please help.

Not even apps are able to block the headset commands. Believe me, I tried.

I dunno if it's helpful but the most common interruption actually even causes the hi-fi DAC to turn off. This suggests there's a full disconnect going on. Not just the headset commands.

Using Android 5.1

Originally Posted by whoskubi

settings/language and keyboard/google voice typing/"ok google" detection. Enabled "from any screen". Did the voice training (say ok google 3x).

fixed this issue. for 10 min so far

Does not work for me

I have had the issue with the google voice thing. One kind of a fix is to only use a pair of headphones that comes with a mic. Everytime I use headphones with a mic I never have this problem. I hope this helps someone.

Anyone who's interested should star this issue with Google maybe they can do something about it, eh?

https://code.google.com/p/android/is...orter%20Opened

So i fixed it on my end by simply disabling the Google App completely.

So... thats an option.

Awful. Awful system whose Idea was this? I searched everywhere for the answer they all told me to do the same thing so I went to Google settings already and did all that crap and it's still happening. This is what usually happens: I'm watching a YouTube video and suddenly I slightly move my earbud wire and Google Voice starts and when I back out it starts playing something I was previously listening to on Google play. This happens so often and it has gotten so frustrating to the point that I'm thinking of ditching Android all together and just getting an iPhone just because of how annoying this feature is. If it's also on IPhone then fml. I've had this issue on other Android phones but this one does it ten times more often. Atrocious feature. If this continues to happen, they're gonna be losing a customer.

Originally Posted by Andrew Bonner

I have some Bose over-ear headphones that I've been using for years and years with no issue. But every time I plug them into the LG V10, the Google Voice Input screen shows up (part of Google Now I believe). If my phone is locked, it starts talking to me about the things I can say into my microphone.

This is ridiculous, because this is as basic of a set of headphones as you can get, and clearly not a headset. It has 3 conductors (2 rings on the male 3.5mm connection). Headsets have 4 conductors (3 rings on the male 3.5mm connection). I cannot for the life of me figure out how to make this stop and it is driving me crazy.

03/28/2016 Edit: Marshmallow (Android 6.0) update has fixed this issue for me!
05/12/2016 Edit: No it didn't.

This issue is one of the main reasons I decided to switch to a Galaxy S8. It may not sound quite as good or power hard to power headphones but for on the go with in ear headphones it sounds just fine and the headphone jack seems to have no issues. No Google pop ups and no songs skipping while the phone is in my pocket.

Ridiculous that the phone has such a good DAC and amp yet it has such a dumb issue that makes it so inconvenient to use.

I've been using standard apple earbuds on my Samsung Galaxy S7 for the past few months but within the last few days every time they're plugged in my phone will turn the volume up and down by itself, close apps, ghost tap and take me to google voice control. Would getting new headphones fix it? Or is it a problem with the phone itself?

Your Android phone is just protesting the Apple technology. LOL

Don't hear anything back from the headphones

I did what you stated here and it worked for me. I will still act up if I don't plug in headphones properly. I noticed that the little headphone symbol at the top of my phone, if plugged in correctly, will show just headphones but if not, than it will show it with a microphone as well.