Related
I'm hoping someone can help me with this.
I woke up yesturday morning looked at my phone and noticed that the little icon you see when you plug in a headset was appearing.
I thought that it was quite strange condering i never use a headset so i did the obvious thing and plugged a headset in and removed it, yet it stayed there.
I've tried everything, cleaning it, moving the jack around, i even installed a new rom and it's still stuck in headset mode.
I'm guessing it must be hardware related due to the fact that i did reinstall the rom.
If i slowly insert the jack of my headset into the 3.5mm port, there is a point where the icon changes to display just headphones.
Anyone have any ideas because it's really bugging me having to use a headset to make calls all the time?
Unfortunately, it may mean that your Hero is soon for repair.
I had this problem - instead of using the headset, you can also use it set to speakerphone as a work around for now.
For me, a week later the mini USB port only allowed charging, not USB disk or sync and was told it was a circuit problem. Sent it away and all problems have disappeared with change of the mini-usb "flex" inside the handset.
The first tech support guy said this indicated that there was an electrical contact inside the 3.5mm jack which may have got some dirt or water that was completing the circuit and making the phone think there was a jack in there the whole time. Try visually inspecting it and ?remove any dirt with high pressure air? Just an idea.
Good luck.
Did you try one of the toggleheadset apps yet? (http://code.google.com/p/toggleheadset2/ or http://code.google.com/p/toggleheadset/)
It's a far shot, as you already changed your ROM, but you might want to try it nevertheless.
I have contacted HTC but haven't heard anything yet.
The second app you posted allows me to turn it off, however for it to work properly during phone calls i have to make sure i answer the call and then turn headset mode off.
Thanks for showing me the that app as it will help me use the phone whilst wating for HTC to reply haha.
Thank you very much elmicha. Toggleheadset is a life saver app.
My HTC Hero always stucked up in headset mode if I ever plug in the headset unless it is restarted. For a long time I had been scared to plug in the headset to ever listen music coz I'll have to restart it to bring it out of headset mode.
I tried the toggleheadset2 which is available in market but it didn't work for HTC hero. Fortunately, the toggleheadset widget worked.
Thank you very much guys. XDA rocks!!!
elmicha said:
Did you try one of the toggleheadset apps yet?
It's a far shot, as you already changed your ROM, but you might want to try it nevertheless.
Click to expand...
Click to collapse
Is there anything for a more recent build? Having a similar issue on DLEV 2.3.4 on an Infuse...
Reinstall with RUU should fix this
Hi,
I had similar issue, headset not working and device not recognised by usb. The installation of ice cream sandwich had screwed my phones drivers such that even older roms that used to work never worked again. Please install an original HTC RUU after a complete wipe, solves all problems.
http://forum.xda-developers.com/showthread.php?t=559622
Regards,
Kiran
Music plays fine out of the wired headset...it always has. The headset has functioned properly until about two weeks ago. At that time, my Atrix began to think that I was pressing the headset button. Constantly. Over and over. Any time the screen is on with the headset in, it redials automatically. When the screen is off, it does it too, because when I turn the screen on, it gives me the vlingo vs. voice command box. Also, when I make a call with the headset plugged in, the other person can somehow not hear me at all, until they call me back, and it's fine. The phone thinks the headset button is being pressed once every few seconds. THIS IS INCREDIBLY ANNOYING.
I know it's not the headset, because I've tried three different headsets (two by Motorola, both the 'official' wired headsets of the Atrix, and one third-party), all with the same result. Also, it's not just my phone! Oddly enough, I replaced my Atrix with AT&T's warranty, and THE NEW PHONE HAD THE SAME PROBLEM.
Has anyone else experienced this, or have the slightest clue what is going on? I've looked around the internet for weeks now and I haven't seen a single instance of it. Pleeeeease. This is brutal.
My headset with mic and button does not have any issues. Its the bose MIE2 mobile phone headset.
Yes I have experienced this as well and it is super annoying I will prob swap it out and hope I don't get another messed up one. Sometimes when I am in my car and connected to my bluetooth handsfree it'll do the same thing and start a song playing and I don't even push anything!!! Hope someone figures this one out.
theres defo something funny about the atrix headphone jack and remote controls.
At first my nexus one remote worked fine with it, but it started doing funny things, then flat out would go crazy (issuing commands without me touching it etc.)
Gave up and went wireless, now I only use wired @ the gyma dn they're just dumb headphones w/out remote
ME TOO!!
Yes, yes, and yes on having this problem. I use my headphones (SkullCandy FMJ) sometimes when riding my bike and yesterday all I kept hearing was "please say a command...did you say...I'm sorry please try again" over and over...hard to deal with at 70MPH!!! Hope this gets fixed, I thought it was my headphones, but it sounds like another GB issue. I don't have any problems when using my SENA SMH10 Bluetooth inside the helmet.
I had this same problem, mine got randomly solved. You could find how the wiring world for the Atrix and block that connection or cut off the controller on the headphone and solder your headphones back together.
Sent from my MB860 using XDA App
Thanks for the feedback, but a)I'm not looking to do any soldering or rewiring (I'm good with software mods, but not hardware mods), and b) it never happened until recently, then I swapped out the phone for a new Atrix, and it happened right off the bat - again with all three headsets. Tried a bluetooth, worked fine, no problem.
I tried a new headset (skull candy something-or-other) and it's been working so far, inexplicably.
I made a voodoo doll of my Atrix and poked it a bunch of times in its little voodoo headphone jack. Seems to have done the trick. I'd recommend that method.
I have this problem too with my headphones from my Sony x1, or x10. I cant remember which one. But as soon as I plug them in the phone goes nuts!
Which really sucks because they are they best headset/ headphones I have ever used for my funny shaped ears.
I think mine fixed after I dropped it and the headphones came out Anyways as long as its resolved that's awesome.
Sent from my MB860 using XDA App
Anyone having the problem using the pure music widget, by any chance? Uninstalled that and hasn't happened since with any headset.
Sent from my MB860 using XDA Premium App
i also started to experience this issues.At first i thought it is kernel or ROM issue but then after multiple test and experiment it is the Atrix 3.5mm headset jack is the culprit.If im not mistaken it is due to pressure contact sensor inside headphone jack.Please anyone know how to rectify this kind of problem do post your solutions for us.TQ
rknight68 said:
Yes, yes, and yes on having this problem. I use my headphones (SkullCandy FMJ) sometimes when riding my bike and yesterday all I kept hearing was "please say a command...did you say...I'm sorry please try again" over and over...hard to deal with at 70MPH!!! Hope this gets fixed, I thought it was my headphones, but it sounds like another GB issue. I don't have any problems when using my SENA SMH10 Bluetooth inside the helmet.
Click to expand...
Click to collapse
You bike at 70MPH? Holy.
so no one found a real fix or solution for this problem? Maybe we need to make a petition and submit to motorola
I had the same problem with a BB9700. It ended up being a damaged headphone jack. I figure some crap from my pocket had been in the jack when I plugged in the head set. Which jammed everything into it wrecking the receiving end of things.
Luckily I had a spare housing which came with a new jack. I'm not sure if it's as easy to replace on the Atrix since I haven't had the opportunity to tear it apart yet.
Power amp has settings that fix my controls and it works great.
Sent from my MB860 using XDA Premium App
Still no one ever face this kind of problem?
Can anyone confirm that this could fix our problem? http://forum.xda-developers.com/showthread.php?t=1301998
I have same problem too. But I have this problem on stock ROM and CM10.1 (with 3.1 kernel) ROM. I don't have this problem with any other ROM.
While watching youtube or playing video via SD card from my Nook Tablet (rooted indirect method, 1.4.0) I get a very annoying static/popping noise before the audio plays at the start of a video or when resuming from a pause. This is only present when headphones are attached. Almost like the device mutes the headphones while no sound is present then clicks/pops/buzzes for a split second when audio is detected before playing. This is happening with three different pairs of headphones and multiple browsers/players. The noise is in relation to the volume set on the device... If I turn the device up to max the static is louder then if the volume is set at half. I see this problem while the device is charging and also when it is not.
Is this problem common and people are dealing with it or am I alone? I did a forum search but didn't see any posts relating to my question.
thanks for any comments.
I have the same issue, and it is rather annoying. I am hoping it is a software issue with the rom, where the ramp between dc and audio is not being handled correctly. It would suck if we had broken hardware
Did you happen to try headphones before rooting?
Maybe related to my "clicking" I get when my NT is sleeping with WiFi on... hopefully a software bug and not shoddy design/materials.
seanchronnery said:
Did you happen to try headphones before rooting?
Click to expand...
Click to collapse
Nope, seems unlikely that would screw with it though.
seanchronnery said:
While watching youtube or playing video via SD card from my Nook Tablet (rooted indirect method, 1.4.0) I get a very annoying static/popping noise before the audio plays at the start of a video or when resuming from a pause. This is only present when headphones are attached. Almost like the device mutes the headphones while no sound is present then clicks/pops/buzzes for a split second when audio is detected before playing. This is happening with three different pairs of headphones and multiple browsers/players. The noise is in relation to the volume set on the device... If I turn the device up to max the static is louder then if the volume is set at half. I see this problem while the device is charging and also when it is not.
Is this problem common and people are dealing with it or am I alone? I did a forum search but didn't see any posts relating to my question.
thanks for any comments.
Click to expand...
Click to collapse
I think it's a software issue. We all have noticed it at some poont.
thin wired headphones
I've noticed this before with thin wired headphones, especially when around a computer. Thick wired headphones with more insulation / protection are a bit less likely to have this problem.
... just a thought... might not work in this case.
Nook Color was just like that. cm7 make it perfect.
Sent from my Nexus S using xda premium
Yup! It happened for a long time. I realized that it cause by the sleep mode of sound chip but it is a software bug... -_-
Last time I use it for the song picker for the annual dinner event and it keeps pop pop pop before start playing. I solve the problem by minimizing the volume but not stop playing.
Finally someone makes a thread about it! I noticed it very early on when I bought my Nook Tablet in last December. It bugged me a lot. I couldn't find much about this problem; all I could find was a similar problem reported with Nook Color. The description of the problem looked so similar that I assumed Nook Tablet has inherited it... I hadn't registered on XDA forums then and decided to live with my assumption.
It has nothing to do with root. I discovered it after rooting it, reverted back in hopes of curing it, it stayed. It persisted when it auto-updated to 14.1. I was hoping this was one of the bugs B&N fixed with the update, but apparently their only motive for the update was to block users from side-loading apps.
This annoying audio issue manifests in at least two different ways. With some headphones, NT emits bursts of hisses before starting the playback. With others, there's no hiss but there's a pop. The hiss is more bothersome than the pop. I have tried with a few different headphones, and only on one I hear the hiss. On the rest, I hear the pop. I don't know why it behaves differently with different headphones. Maybe it's something to do with impedance.
My take is that NT turns off the audio at the hardware level whenever it doesn't detect any audio playback. It comes back on with a prelude of a pop or hiss. The idle period needed shut off audio is very little (maybe 1 second or so). Maybe it was done to conserve battery. This makes playing any musical instrument app very frustrating. Once you pause before playing another note, you automatically get a prelude of a pop or a hiss.
Speaking of musical instrument apps, another thing that makes NT quite unsuitable for enjoying those is a lag/latency between hitting the touchscreen and hearing a sound.
Is there any other way to fix it as we wait for a stable version of Cyanogen ROM? I'm not sure. I have seen some lines dealing with audio on build.prop. I don't know editing which parameter to what value would help things, so I didn't mess with them. Maybe someone more knowledgeable would like to try? I will try myself if I can learn more about it.
So figured I'd go ahead and add a thread about this here for us Sprint users that are experiencing the problem with the Aux cable. Its a known issue and I'd link to a couple other posts, but I'm still a "noob"
I was a little upset to find that I wasn't able to use my phone to Pandora in the car.
However....
Today I got it to work, and here is how: I had the stereo set to the CD player when i plugged the AUX cable in and the icon stayed in the notification bar. Then I launched Pandora and let it start playing. THEN I switched the stereo to AUX mode, and it played fine my entire trip to work. Still experienced the "hot plug" sound between tracks, but I think I can deal with it.
geetee360 said:
So figured I'd go ahead and add a thread about this here for us Sprint users that are experiencing the problem with the Aux cable. Its a known issue and I'd link to a couple other posts, but I'm still a "noob"
I was a little upset to find that I wasn't able to use my phone to Pandora in the car.
However....
Today I got it to work, and here is how: I had the stereo set to the CD player when i plugged the AUX cable in and the icon stayed in the notification bar. Then I launched Pandora and let it start playing. THEN I switched the stereo to AUX mode, and it played fine my entire trip to work. Still experienced the "hot plug" sound between tracks, but I think I can deal with it.
Click to expand...
Click to collapse
I recall having an issue with my samsung headphones. They didn't work at one point, I rebooted and they were fine. The phone didn't even detect them for some reason. I've had no issues with aux in my car (aside from needing a new cable), however I thought it would be worth mentioning that my Note 2 had an issue with aux when it is on any AOSP ROMs. Selecting any app, even swiping the notification window down, sometimes even just leaving the music app and going back will stop the music from playing. The only solution for this was to go to the home screen unplug the aux start music playing and plug the cable back in and touch no other app. Again, it never did this with stock. I even went back to stock briefly because of this. AOSP seems to throw a fit with the aux cables.
I had issues with AUX today as well. Thought it was my specific phone but I'm relieved to know it's common....and perhaps a software issue.
infernosoft said:
I had issues with AUX today as well. Thought it was my specific phone but I'm relieved to know it's common....and perhaps a software issue.
Click to expand...
Click to collapse
Yeah I have it as well...I've found if I start Spotify, then plug in the AUX cord from my car, it works fine.
So I think I know the answer to this one.
It seems to have to do with how cars and some other devices treat aux inputs. For the most part it appears (at least in the case of my Prius) that with the input switched to aux the phone would not consistantly stay aux mode. What it seems like was happening is that the car doesnt actually 'activate' the aux port unless it senses a completed circuit (ie: audio playing). I have to believe this has to do with preventing feedback.
Unfortunately it seems the phone does the exact same thing. The headphone or aux symbol appears on insert of the cable because the phone senses the initial connection but then finds no load on the circuit thus assuming it is not connected and disables the port. You end up with basically an electronic stalemate. Neither one engaging cause they sense nothing from the other side. No load on the circuit.
Bear in mind this is completely dependent on the device you are connecting to your phone, as to whether it does what I'm talking about. Likewise, those experiencing popping or similar during song or track changes would basically be experiencing the same issue as during the song change the phone stops playing audio and your car kills the port. When the car kills the port, the phone kills the port, or is in the process of it when the next song starts.
To counteract this I bought an audio cable with a ground loop circuit built in. It is designed to remove the buzz from car aux audio due to the phone or other device being charged through the car's power system. But the added benefit is that it creates an artificial load on the line that the phone senses. Same idea as plugging in headphones as the earphone on the headphones creates a load on the line in the same way.
This is the audio cable I bought. Works like a charm every time, although one warning. I did experience one case of very loud static when unplugging it through the speakers in my car because of the fact that the car and the phone believe the circuit constantly is active and thus do not kill the connection to save your hearing. So be careful to only plug or unplug it when the input is not active or the car is off.
http://www.amazon.com/Kensington-Reducing-SmartPhone-including-iPhone/dp/B0031U1ATQ/
It does appear that Amazon has put the item under review for now, though I'm not sure why as mine works flawlessly, but any similar car aux noise reducing cable would work, assuming its decent quality.
An aux cable with an in-line volume control should peform similarly due to the load created by the potentiometer, although it wouldnt remove the charger buzz.
Something like this:
http://www.amazon.com/Apollo23-3-3-Volume-Control-Samsung-Smartphones/dp/B00COXA8Y4
wolfhelm said:
So I think I know the answer to this one.
It seems to have to do with how cars and some other devices treat aux inputs. For the most part it appears (at least in the case of my Prius) that with the input switched to aux the phone would not consistantly stay aux mode. What it seems like was happening is that the car doesnt actually 'activate' the aux port unless it senses a completed circuit (ie: audio playing). I have to believe this has to do with preventing feedback.
Unfortunately it seems the phone does the exact same thing. The headphone or aux symbol appears on insert of the cable because the phone senses the initial connection but then finds no load on the circuit thus assuming it is not connected and disables the port. You end up with basically an electronic stalemate. Neither one engaging cause they sense nothing from the other side. No load on the circuit.
Bear in mind this is completely dependent on the device you are connecting to your phone, as to whether it does what I'm talking about. Likewise, those experiencing popping or similar during song or track changes would basically be experiencing the same issue as during the song change the phone stops playing audio and your car kills the port. When the car kills the port, the phone kills the port, or is in the process of it when the next song starts.
To counteract this I bought an audio cable with a ground loop circuit built in. It is designed to remove the buzz from car aux audio due to the phone or other device being charged through the car's power system. But the added benefit is that it creates an artificial load on the line that the phone senses. Same idea as plugging in headphones as the earphone on the headphones creates a load on the line in the same way.
This is the audio cable I bought. Works like a charm every time, although one warning. I did experience one case of very loud static when unplugging it through the speakers in my car because of the fact that the car and the phone believe the circuit constantly is active and thus do not kill the connection to save your hearing. So be careful to only plug or unplug it when the input is not active or the car is off.
http://www.amazon.com/Kensington-Reducing-SmartPhone-including-iPhone/dp/B0031U1ATQ/
It does appear that Amazon has put the item under review for now, though I'm not sure why as mine works flawlessly, but any similar car aux noise reducing cable would work, assuming its decent quality.
An aux cable with an in-line volume control should peform similarly due to the load created by the potentiometer, although it wouldnt remove the charger buzz.
Click to expand...
Click to collapse
I just want my G3 to work as it should for such a simple function as the headphone jack/aux port.
I want to listen to music in my car without fannying around with different cables etc etc.
I had a Galaxy Note and S4, both played fine in the same car with the same cabling.
Shame on LG for releasing us a substandard product that cannot perform the most basic of tasks correctly.
I will say, i was extremely dissapointed when i plugged my shinny new phone into my stereo and the audio continued to come through the phone speakers. All other phones/devices work just fine in my car and there is no reason why my G3 shouldn't either.
R2DeeTard said:
I will say, i was extremely dissapointed when i plugged my shinny new phone into my stereo and the audio continued to come through the phone speakers. All other phones/devices work just fine in my car and there is no reason why my G3 shouldn't either.
Click to expand...
Click to collapse
My first feeling was confusion. I was also worried my headphones wouldn't work. But I was able to watch a beautiful high def video on my phone last night with my headphones on
Sent from my LGLS990
I just got this phone too, and although I love it, I was very sad to have this issue! I haven't had it on any other phone I have owned, so I certainly hope it is fixed in a future update. That and the video force close bug, but that is for another thread!
Guys, there is nothing wrong with the AUX port on your cars -- and they don't trigger via sound. They trigger via either conductive circuitry or via ohm load. Can you test if you are still seeing these problems when *not* charging? This issue is typically related to bad grounds. This happens to me at work when my phone is charging and I plug my headphones directly into my G3. If I pass the audio to my PC first (to the line-in,) and THEN to my headphones, the static is mostly gone.
So try unplugging the power source, and using different aux cables. Another factor is try plugging the power source into the same feed as the stereo. Sometimes this isn't that easy though.
What's happening on the back end with the sound changing between songs, etc, is that the audio codec, (the chipset,) is turning off to conserve battery. For me, when the chip turns on, it grounds the 3.5mm port just fine, and when it's off, AND I have power connected with headphones, I can get that whine -- depending on the scenario. So basically, this is by design -- an energy conservation tactic. I would be okay with them leaving the audio chip on the entire time headphones are connected.
Had this problem too and found that as long as I was charging the phone it would play like it should.
Yep, grounding issue. At work, routing the aux signal through my PC works just fine WHILE charging -- if I unplug, then I get all the machine noise.
In general, though, the headphone output is pretty crappy on this device. Even when it's "working great," there is still a faint amount of white noise that can be heard. Much higher than my HTC M7. The S5 had similar performance as the G3 though.
I just bought:
http://www.amazon.com/gp/product/B00ANDHBNS/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1
And plugged it into:
http://www.amazon.com/gp/product/B00F474DVG/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1
So when I get in my car, it connects to the dongle for music and the car's blue tooth for phone.
It's not perfect, but gets the job done.
wolfhelm said:
So I think I know the answer to this one.
It seems to have to do with how cars and some other devices treat aux inputs. For the most part it appears (at least in the case of my Prius) that with the input switched to aux the phone would not consistantly stay aux mode. What it seems like was happening is that the car doesnt actually 'activate' the aux port unless it senses a completed circuit (ie: audio playing). I have to believe this has to do with preventing feedback.
Unfortunately it seems the phone does the exact same thing. The headphone or aux symbol appears on insert of the cable because the phone senses the initial connection but then finds no load on the circuit thus assuming it is not connected and disables the port. You end up with basically an electronic stalemate. Neither one engaging cause they sense nothing from the other side. No load on the circuit.
Bear in mind this is completely dependent on the device you are connecting to your phone, as to whether it does what I'm talking about. Likewise, those experiencing popping or similar during song or track changes would basically be experiencing the same issue as during the song change the phone stops playing audio and your car kills the port. When the car kills the port, the phone kills the port, or is in the process of it when the next song starts.
To counteract this I bought an audio cable with a ground loop circuit built in. It is designed to remove the buzz from car aux audio due to the phone or other device being charged through the car's power system. But the added benefit is that it creates an artificial load on the line that the phone senses. Same idea as plugging in headphones as the earphone on the headphones creates a load on the line in the same way.
This is the audio cable I bought. Works like a charm every time, although one warning. I did experience one case of very loud static when unplugging it through the speakers in my car because of the fact that the car and the phone believe the circuit constantly is active and thus do not kill the connection to save your hearing. So be careful to only plug or unplug it when the input is not active or the car is off.
http://www.amazon.com/Kensington-Reducing-SmartPhone-including-iPhone/dp/B0031U1ATQ/
It does appear that Amazon has put the item under review for now, though I'm not sure why as mine works flawlessly, but any similar car aux noise reducing cable would work, assuming its decent quality.
An aux cable with an in-line volume control should peform similarly due to the load created by the potentiometer, although it wouldnt remove the charger buzz.
Something like this:
http://www.amazon.com/Apollo23-3-3-Volume-Control-Samsung-Smartphones/dp/B00COXA8Y4
Click to expand...
Click to collapse
I just purchased this:
http://www.amazon.com/Kensington-Reducing-SmartPhone-including-iPhone/dp/B0031U1ATQ/ref=sr_1_1?ie=UTF8&qid=1406313911&sr=8-1&keywords=kensington+noise+reducing+car+audio+aux+cable
Working pretty well. Mainly solves the connectivity issues.
Still have the pop between tracks but it's much better.
Still have the "computer talk" garbage noise related to the display coming through the left channel.
I can live with this until LG or Android comes up with a fix.
aux problem
I guess I lucked out with my phone but then again maybe not. First off I will describe my setup, I have a 05 Subaru WRX with stock 6cd changer head unit ( no aux port ) I installed a Harmon Kardon Drive + Play iPod dock. This allows me to remote control my iPod and comes with a display that shows tracks and such. It works by FM transmitter but has an optional wire which I have that connects directly between the antenna and the stereo so you get little to no loss of signal. Between the AUX and my phone I connected a PAC SNI-1/3.5 3.5-mm Ground Loop Noise device. My previous phone was an LG Optimus G which I loved, when I hooked this phone up I could listen to Pandora/TuneinRadio through my car speakers and upon making/receiving a call I would hear the call through the car speakers and when I talked the phone mic. would pick up my voice. When I attempt this with the G3 I get no popping between tracks but the phone mutes the mic and when I say mute I don't mean the mute button comes on I mean the other person can't hear me. I found if I unplug and plug the phone in during the call eventually the mic works again, but to do this while driving defeats the purpose of hands free calling. Does anyone else have this problem? (or a solution).
Click to open expanded view
gorillaz1 said:
Yeah I have it as well...I've found if I start Spotify, then plug in the AUX cord from my car, it works fine.
Click to expand...
Click to collapse
Works for me, thank you.
Mines does not work at all, with headphones or aux Jack, now I have to get Bluetooth headphones and bluetooth radio for car
Sent from my LGLS990 using XDA Free mobile app
Do we know if LG is working on this issue? Or if it is something that can even be fixed with an update? I'm getting tired of messing with the cable just to play music in my car, and I don't want to have to buy extra accessories to get the job done.
Sent from my LGLS990 using XDA Free mobile app
Bumping this thread because I just started having issues. Last night I was listen to music with headphones and my device kept turning itself down. I thought it was Tasker at first but it kept happening. Today at work I wanted to listen to music on headphones again and the sound would only come through my device. I'm going to try an aux and other headphones when I get off work, but does anyone know if a system restore will fix this? I'm rooted with TWRP, I just don't want to wipe it for nothing.
Srambo217 said:
Bumping this thread because I just started having issues. Last night I was listen to music with headphones and my device kept turning itself down. I thought it was Tasker at first but it kept happening. Today at work I wanted to listen to music on headphones again and the sound would only come through my device. I'm going to try an aux and other headphones when I get off work, but does anyone know if a system restore will fix this? I'm rooted with TWRP, I just don't want to wipe it for nothing.
Click to expand...
Click to collapse
They fixed it with ZV6. If you're already on ZV6 then I have no idea.
Sent from my LGLS990 using XDA Free mobile app
Hellllllllllllllllllllllllllllllllllo XDA peeps.
so ages ago we all got the marshmallow update and i must say, issues have been a real thing. I did consider ROMS but too risky as i use this phone daily for business's and such.
Anyway so one problem I can not find across the whole internet is the AUX cord problem, now when i drive, I plus in the cord and this notification appears saying "Headset is connected" then disappears, then repeats almost 8 times and lags my phone which after this, goes to normal and finally works. However!
I found that in lollipop I had never had this issue, I just plug in and it works perfectly. As well as this, I found its not a hardware issue, reason being is that other headphones work, every set of headphones i plug in work like a charm.
I have cleared data and cache from smart connect, even disabled it and nothing. Ive booted in safe mode, nothing.
I really just want this sorted as I love this phone, I do. Im not sure if this is a Marshmallow update bug or something but if any fix can be found or advised to me; Id love you forever, because i miss being able to just plug in and play and not waiting for this bug to simply calm itself from this spasm.
Lag is an issue, I have no clue why but it seems the newest update caused things to get hot, lose alot of battery quick and just plain ol' lag. Any fixes on this to is perfect, at the moment though I iwsh to get the AUX cord fixed as a priority to lag.
Anyway, thanks guys and hope to hear something soon! After all, this is a 007 phone, bond never had these issues
Are you sure its not the physical connection on your phone? May it happened to get damaged when you upgraded MM.
Headphones work fine for me. I recently got a rental car with no bluetooth and bought a cheapo stereo cord to hook to the car's speakers and I saw this occur. No lag though. The major annoyance was that goggle play music would stop thinking the headset was unplugged. After some dangerous debugging while driving, it seemed like one end of the chord was defective. When I swapped the problem went away.
eng3 said:
Are you sure its not the physical connection on your phone? May it happened to get damaged when you upgraded MM.
Headphones work fine for me. I recently got a rental car with no bluetooth and bought a cheapo stereo cord to hook to the car's speakers and I saw this occur. No lag though. The major annoyance was that goggle play music would stop thinking the headset was unplugged. After some dangerous debugging while driving, it seemed like one end of the chord was defective. When I swapped the problem went away.
Click to expand...
Click to collapse
Literally nothing hardware related, the cord in my car works fine with other devices. It's very weird and as I say, I did a short test and found that lollipop on this device actually creates no problem, I then updated tonight and found it happens again.
I think it's more software related and I hope android N is just a pure wave ?
I have the same issue.
So so many problems with this phone ?
I have the same problem as well. What I do is plug the jack, wait for it to finally recognize it and then launch the app I need