Hi
The sound has stopped working on my wallaby, and I wonder if anyone can help me fix it. I have cleaned the headphone jack with a toothbrush and IPA solvent and this has made no difference. I have also checked the resistance across the contacts with a multimeter and measured zero ohms across pins 2-3 and 4-5 after cleaning.
However, I have found that the sound does work if the device is really cold. For example - if I put the wallaby in the fridge, the sound will work for a few minutes until it warms up again.
Can anyone sugest what might be the problem?
Cheers
Ben
I have also tried the playback test from the bootloader meny and this works fine.
any luck with "no sound" so far? i am having same problem with jasjar. tried to screw around with headphone jack socket like threads state but no luck. thought maybe you might have some advice on how yours is going?
Hi
No progress whatsoever. It's almost impossible to fault find without a circuit diagram / schematic. I can't get my head around why it works fine from the diagnostics menu, but not at all once I boot it up into Windows (unless I put it in the fridge).
Cheers
Ben
wallabyuser said:
Hi
No progress whatsoever. It's almost impossible to fault find without a circuit diagram / schematic. I can't get my head around why it works fine from the diagnostics menu, but not at all once I boot it up into Windows (unless I put it in the fridge).
Cheers
Ben
Click to expand...
Click to collapse
Perhaps the failing componant is near another that emits a lot of heat when the phone is booted, but doesn't startup in diagnostic mode? Charging circuit overheating / shorting maybe? Or maybe the resistance of something in the speaker circuit is changing as it warms?
Any access to a thermal camera / image software?
Richard
just got my jasjar back after having cracked lcd and headphone jack replaced. sent to http://www.pocketpctechs.com out of california as suggested by very helpful user on this site. cost me around $20 dollars and took only a day to fix. works fine now!
more of this problem in ear peace ( audio jack ) problem ... just use some contact
Related
Hi all,
to my great frustration, I've discovered that my SGS2 line-out / headphones jack seems to have a slack joint, i.e. if you turn a connected plug around its long axis, a crackling sound is heared in the speakers and at some angular positions the stereo signal will be reduced to mono (i.e. one speaker gos silent). With one device (mobile outdoor speaker) I even had no sound at all at when inserting the plug with the wrong "orientation".
Did anybody experience the same problem or am I just out of luck here?
I am wondering whether sending back the device to the retailer (Amazon) or directly to Samsung (I'm situated in Germany) will yield the faster round-trip time, any experiences here?
Thanks!
PS: I know this may be a stupid question but can somebody PLEASE tell me how to search for multiple keywords with AND logic in this forum? Tried "+word +word" and "word AND word" (without the quotes) but nothing seems to work.
Are you using the headphones that came with it? My better half went through 4 sets of the stock samsung headphones with her original Galaxy S and all produced the same issue of losing one channel after a matter of days/weeks. having the jack inserted to about 2/3rds is a workaround but not ideal as you still lose some frequencies and it's insecure... They're just a bit pony.
No, I used different kind of headphones, including Sennheiser in-ear headphones and a standard male-male audio jack connected to some bigger hifi system. With some jacks I did not encounter the problem, but most of them lost some part of the signal with some orientations: I persume that the manufacturing tolerance of the jacks also plays a role...
Anyway, it's definitely not a problem of the jacks but of the device since I tried it with the SGS2 of a friend yesterday and it worked with the same jack that made problems with my device.
I will proceed sending my phone to Samsung for repair, I hope that won't take to long *sad looking*, I am so used to it now, it's card to survive to weeks without it.
I had the same problem, all I had to do was insert headphones cable "HARDER" into the audio jack until I herd a "click" sound.
I was way to over protective of this phone when i first had it, and wanted to handle too much with care, forced the dam cable in, and "click", sounded like it snapped into place, the audio worked correctly without cracking noise or without the need to wiggle to cable get clearer sound.
Perhaps your friends SGS2 is already used to headphone being inserted, but yours not. Just add a little pressure until you hear clip into place.
If this doesnt help, then repair or return.
Thanks for the hint, but unfortunately I had the jack inserted to the very end, so this was not the problem... sent in for repair now, let's see what happens.
I have a fix for you i think!!!!!!!!
ok . when i got my s2 like 4 days ago (at&t usa version) i noticed that when i plugged into my aux cable in my car that it was low sound cracking more volume on the left side , very annoying . NOW FOR A SIMPLE FIX FOR SOME TO TRY! PLUG IT IN ALL THE WAY! i noticed when plugging it in i wasnt fully plugging it in . it should go all the way down FULLY! the sound is perfect once this is done . I HOPE THIS HELPS YOU !!!!!! good luck
I have an issue with my headphone Jack constantly switching on and off when nothing is plugged in so the volume control keeps popping up and nothing plaslys through the speaker. Does anyone know how to completely disable the headphone port? I already removed the Jack itself and it did nothing. Anyone have any ideas? O also tried all the Widgets and none of them worked.
Have you tried fixing permissions, or wiping the phone? See if that helps the problem at all.
Sent from my MB860 using xda premium
I've tried hard resets, custom roms, custom recovery's, clearing cache and everything else. nothing has helped it so far.
Anyone else got ideas?
Your headphone jack might be dirty.
-Take a cue tip.
-Cut in in half lengthwise (So it is thinner, not shorter)
-Dip the cue tip in rubbing alcohol,
-Stick cue tip in headphone jack and twist around and thrust in and out (Haha)
-Let dry for an hour
-??????
-Profit!
I already said i took it apart and cleaned it, even went so far as removing the headphone port completely but the phone still switches back and fourth into headphone mode. I'm looking for a way to completely disable the headphone port in the software of the phone, I've got a custom ROM on it so it's open for tweaking.
I don't ever use the headphone port so I just want it disabled and turned off in the software.
I think i disabled it on a hardware level. I got fed up with it and disabled it by disassembling the phone and back tracing the electronics finding two resistors in path to the rest of the electronics for the headphone port and removed them. Headphone port seems disabled now
My sgs2 has apparently been water damaged while skiing and now i get this weird error, whenever my earphone isnt inside the jack port it freezes. If i restart it wont boot untill the jack is inserted, only the download mode works. Recovery freezes also. I flashed to official firmware i still get the same error, i replaced the jack piece with a new one and the problem persists. It seems like a short circuit somewhere, and for some reason the earphone piece stops it from taking place. So what could the reason be if it isnt the jack piece what else could it be?? does it have a solution that can be fixed without sending it to samsung??
thx
anyone?
Anyone?
It looks like the jack acts like a bridge to complete the circuit.
I suggest you need to look at the back of the motherboard, it looks the water damage could have broken a solider path connection or sensor, normally the phone by passes the headphone jack until the circuit is complete by the metal of the headphone jack.
Other cause which neds a JTAG is that one of the instructions on the chip has been corrupted so that it can not tell the phone to by pass the jack when it does not sense it.
Cosmic Blue said:
It looks like the jack acts like a bridge to complete the circuit.
I suggest you need to look at the back of the motherboard, it looks the water damage could have broken a solider path connection or sensor, normally the phone by passes the headphone jack until the circuit is complete by the metal of the headphone jack.
Other cause which neds a JTAG is that one of the instructions on the chip has been corrupted so that it can not tell the phone to by pass the jack when it does not sense it.
Click to expand...
Click to collapse
I took appart and took a photo of the backside, apparently there's plenty of humidity marks all around the motherboard so i really cant tell where the problem might be... if it were a corrupt instruction woould i be able to substitute the chip or is there some alternative solution?? how can i identify the problem with the jtag???
thx
Hi guys.
I have had this issue for awhile and have put it off thinking it was a headphone cable issue but it's not.
I have already tried cleaning with contact cleaner and rubbing alcohol.
My issue is that my phone will trigger "Google voice" search just by slight movement at the cable /jack junction. This is insanely annoying considering I bought this phone due to its audio prowess.
It will also automatically pause or change tracks with the same jack/cable movement.
I am Canadian and bought this from HK via ebay. I am one of those who almost never bother with warranties but obviously would seeing as I spend near a grand on this thing. How would I begin on a warranty claim?
Thanks.
Seems to be a common issue, unfortunately. I haven't really found a way to fix it yet.
How new is your device?
What type of finish is on the end of the cables ends?
I use this cable with almost no issue. Once in a while it will trigger voice when I plug in. But that's all.
https://www.amazon.com/gp/aw/d/B00F9KUF7O/ref=yo_ii_img?ie=UTF8&psc=1
I've also got a phone from HK prior to release in my country and have been struggling with this.
It looks to me that this is because of the way the phone detects your device. I've that the headphones that comes with the device and other earbuds works with no problems, but my bigger M40X for example have this.
The best solution I've found so far is this: plug it and leave it (not moving it at all) for about 10 seconds. After this the problem seems solved most of the time.
Unplugging and re plugging it several times also worked sometimes at the begging, but it was very frustrating and probably not so good for the longevity of the jack.
I'm actually about to make a factory reset for other reasons, but I'll post here if it makes any difference.
UPDATE: The factory reset did not fix the issue, but I have the impression it's triggering the high gain with my m40x as now I've noticed increased volume and no difference to when doing that trick of plugging the detachable cable first to the phone and then to the headset. Don't ask...
I had this issue a few times on my previous phone (Droid Maxx) when in the car, as I was plugging it in (usually when there was turbulence). I thought it was due to the tip of the plug contacting one of the other contacts in the jack. See this link for what the different parts of a headphone/mic combo plug or jack are. I'm not sure if your cable has all of those, but if the wrong ones touch maybe it triggers the mic to listen. Or internally your cable may be shorting between the different signals. Just spitballing ideas.
You know what guys, a friend of mine really liked my phone and got one as well. So when he got it I asked to him to test the jack problem with my headphones and it was simply not there. I do suspect this is a problem with the device. I'll try to get in touch with LG a second time for support (as the first time they asked me to get back to the country where I got it, the Philippines, and this is not really an option).
MrCogito said:
I've also got a phone from HK prior to release in my country and have been struggling with this.
It looks to me that this is because of the way the phone detects your device. I've that the headphones that comes with the device and other earbuds works with no problems, but my bigger M40X for example have this.
The best solution I've found so far is this: plug it and leave it (not moving it at all) for about 10 seconds. After this the problem seems solved most of the time.
Unplugging and re plugging it several times also worked sometimes at the begging, but it was very frustrating and probably not so good for the longevity of the jack.
I'm actually about to make a factory reset for other reasons, but I'll post here if it makes any difference.
UPDATE: The factory reset did not fix the issue, but I have the impression it's triggering the high gain with my m40x as now I've noticed increased volume and no difference to when doing that trick of plugging the detachable cable first to the phone and then to the headset. Don't ask...
Click to expand...
Click to collapse
Funny you mentioned the volume increase. That is a trick I learned from someone in another thread as the standard gain setting for low impedance headphones was too weak. That made a vast improvement in volume and was a life saver because I bought this phone specifically for its audio abilities.
As for the Google voice thing the only thing I found that worked was going under apps and disabling the Google app which is ridiculous considering it kills Google on tap which is a big feature of android.
I am pretty sure this is being trigggered by the jack somehow engaging a contact. Explains why it's triggered when I move.
Drives me nuts. Read somewhere that MM fixed this but not for me. I will try enabling Google app and uncheck all the voice options and see if this helps.
You know what, after struggling long with this I've finally gathered the balls to buy a headphone jack part and replace it myself. I've done it with my old Nexus 4 (the jack actually broke there).
It takes a while to arrive, but I'll perform the change and post the result here.
Where I got it from:
http://www.ebay.com/itm/122034019463
I sometimes have the voice recognition and volume issue, but for me it appears to be an issue with my headphones (Bose MIE2i). I don't have the issue with any other headphone or cable. I have this issue when I fiddle with the in-line controls of the Bose (both this and the 1st pair of Bose). My belief was that it was due to poor shielding of conductors in the controller or shoddy wiring connections.
Did u ever solve the problem with replacement? Im having issues with left and right volume. Like a shorted cable, but bought new phones & still doing that.
Just in case anyone is still suffering from this problem, I made a discovery today. I've replaced the headphone jack in my v10 3 times thinking that they're just ****ty headphone jacks that break all the time, but in my case at least the fault wasn't the contacts inside the jack itself. I found that my problem was actually related to the push-down connector that clips to the motherboard. I had a hunch that keeping the phone in my pocket with headphones connected was slowly rocking it back and forth and would eventually disconnect it. In order to add more clamping pressure to the connector, I put 3 small slices of electrical tape on top of it before screwing the back down. On my walk home today, the left earphone would disconnect with literally every step that I made. After putting the electrical tape in the problem was solved.
So i checked dozens times if the jack socket is ok and it is, also the motherboard pads looks ok, but i can't make any headphones to work anyway.
They don't get detected, ones or twice they worked for 1 second, and then it's only rugg noise.
no idea anymore. No any garbage inside. Everything look clean and cool.
I also flashed and rooted it with 2 different roms. Didn't help.
Pls help.
Fox_Murderer said:
So i checked dozens times if the jack socket is ok and it is, also the motherboard pads looks ok, but i can't make any headphones to work anyway.
They don't get detected, ones or twice they worked for 1 second, and then it's only rugg noise.
no idea anymore. No any garbage inside. Everything look clean and cool.
I also flashed and rooted it with 2 different roms. Didn't help.
Pls help.
Click to expand...
Click to collapse
hardware issue, you must need a technician
Could the IC get wrecked? It should not cause the speaker works normal. I can hear all voices and music.
Fox_Murderer said:
Could the IC get wrecked? It should not cause the speaker works normal. I can hear all voices and music.
Click to expand...
Click to collapse
Maybe the headphone jack sensor got damaged. Does the headphone icon appear on the status bar when plugged? If not, then this is likely the issue.
Where is jack sensor?? How does it looks like?
Fox_Murderer said:
Where is jack sensor?? How does it looks like?
Click to expand...
Click to collapse
The jack it's attached to the upper part of the board. You'll have to open the phone. And it is covered in plastic. If it's damaged then you'll probably have to replace it.
With EdwinMoqs and Artas' roms volume output can be high enough to cause clipping, which is often accompanied by false headset removal event. You have to carefully adjust the maximum safe volume level, but in the end it's still louder than stock rom which is crippled by EU and probably US regulations.
I can adjust volume via headset button, with the Headset Button Controller app. Setting max volume to 80-90% should do. The clipping protection in poweramp wasn't effective, it did the job with Artas' rom.
Problem can also be caused by a switch, which should be under one of the contacts in the jack, and can be reached with a needle(i never checked how it looks inside the jack). Also the plug should fit in to the hilt. Something might block the plug, the spindle with the contacts be too short. If you get the plug fully in and still see the spindle you're safe.
Socket looks like connecting, i can see pins moving. And i was shorting some last pins and it didn't said headphones is on.
There's a new feature in Android from 5.x or 6.x up, called Pressy Mode. It does exactly what the problem is here, and it can be controlled by Headset Button Controller app.
Probably intended for using the headset as antenna for a built-in tuner solely.
Ok, thank you all to trying to help me. I fixed this, it is working for now, i don't know for how long.
I connected for couple of seconds left channel and/or right channel by wire to the grounded Metal shield on board, and it started to detect headphones every time for now. The wire is not needed for constant working. I don't know how it worked. Also, motherboard was just a little moving over socket, so it was needed to make it hold still. I puted some little plastik on board so it pressed to the back. Works for now. I just dont know for how long. But there are still some little scrathes noises so it must be faulty IC or something in way from controller to the socket. The speaker has no scratch noises, works normal. but elements looks normal no green rust or anything.