hi all, i have a spring samsung s3, it recently had some water damage but not full blown submerged in water. it still turns on and all buttons and functions work fine. however the speaker seems to be blown, i can hear a hiss noise from it and when i do the service menu quick test, no sounds comes out nor does the LED notification light up. pushing volume up and down buttons still work.
anyone have any idea if it may be the audio chip damaged or some sort of flex cable? i'm hoping its a part I can order and replace myself. I have opened up the phone and know how to take pieces/cables a part (aside from chips on the motherboard... may have to pass on that)
Related
So, I've replaced the phone's glass/digitizer, and after reassembly, everything but the earpiece speaker is functioning. Upon closer examination it looks like this piece:
i42.tinypic(dotcom)/2lntr49.jpg
has fallen off. It's ridiculously tiny:
i44.tinypic(dotcom)/2ykkhad.jpg
Is this piece even sure to be the reason the earpiece won't work? If so, is there any way it can be reattached, or am I totally screwed?
Did you ever find a solution to this?
I am also wondering if you figured this out.
I have an Atrix that worked fine for months but one day the speaker stopped working. We had it sent it for warranty repair and it came back only to work once. It appeared to be working but the speaker 'popped' and stopped working as soon as we turned up the volume.
I then bought a replacement speaker ribbon cable myself and after putting it in, the exact same thing happened again: On first impression the new speaker worked, but then we turned up the volume and *pop*, the speaker is broken.
Upon looking at the speaker that I pulled out during my own replacement, there is a resistor missing like in your pictures. However, it's a different one of the six. I am willing to bet that the speaker in the phone now is also missing a resistor since the pop.
Hi guys,
I have had various handsets in the past two years (HTC Desire, HTC Desire HD, Nexus S and Galaxy Nexus) and I have used all those in my car hands free via the AUX socket, i.e. successfully making phone calls and playing music whilst driving
I recently got the S2 and when I connect it to the AUX in the car, music is loud and clear but when I when in a phone call the other person is struggling to hear me even with all volume levels set at max. I can hear them clearly though.
I know when the S2 was first released there was a hoohaa about poor call quality especially the microphone volume being set too low by default etc.Could this be what I am experiencing? I am in doubt because on normal calls (no AUX) the other person can hear me clearly and I can hear them.
Is there a fix for this issue? It is important for me to be able to have calls in the car.
I am completely stock I9100 ICS 4.0.3.
I have tried with and without cases without success, currently have a barely there case on.
WIll greatly appreciate any feedback
KKH
First off, you said you have an i9000, which is the Galaxy S1. Did you actually mean an i9100?
Second, it could be a hardware issue. There is rubber housing on each mic; the lower mic is used during regular voice calls. The upper is used for noise cancellation, but also it is used for the primary microphone for speaker phone mode and car mode. I had an issue with speaker phone mode where the rubber housing on the upper mic was not seated properly, so on speaker phone, my voice was muffled. I had to open the phone up and re-seat the housing on the upper mic to get it to work properly.
ctomgee said:
First off, you said you hasn't an i9000, which is the Galaxy S1. Did you actually mean an i9100?
Second, it could be a hardware issue. There is rubber housing on each mic; the lower mic is used during regular voice calls. The upper is used for noise cancellation, but also it is used for the primary microphone for speaker phone mode and car mode. I had an issue with speaker phone mode where the rubber housing on the upper mic was not seated properly, so on speaker phone, my voice was muffled. I had to open the phone up and re-seat the housing on the upper mic to get it to work properly.
Click to expand...
Click to collapse
Sorry it was a typo, I do indeed have an I9100 aka S2 (corrected it on OP).
So the NC mic is used for car mode? The thing about the S2 is it doesnt visually show on screen when a headset/mic is connected hence I didnt think there was a car mode as such.
I may have the same issue as you, was it relatively simple to disassemble the back and relign the rubber?
Thanks
KKH
kkh786 said:
Sorry it was a typo, I do indeed have an I9100 aka S2 (corrected it on OP).
So the NC mic is used for car mode? The thing about the S2 is it doesnt visually show on screen when a headset/mic is connected hence I didnt think there was a car mode as such.
I may have the same issue as you, was it relatively simple to disassemble the back and relign the rubber?
Thanks
KKH
Click to expand...
Click to collapse
Yes, the NC mic is what picks up sound for speakerphone/car mode.
Overall, I personally found that breakdown is pretty simple. Check out this post. It details a fix for echo due to issues with the rubber housing, but it gives you an idea of what to do. Focus on the top mic; if you're not having issues with regular voice calls, don't mess with the bottom mic.
You'll need a phillips screwdriver from an eye-glasses kit, and something to pop the case apart. I used an old credit card. Be careful when popping the case apart, the power button and volume rocker can be easy to lose.
If this seems daunting to you, and you are still under warranty, just take it to an authorized Samsung repair center.
I have a Vibrant on which the sound stopped working. I would appreciate any input on diagnosing the issue.
I bought the phone for my daughter to use as an PMP with no cell service. It got it super cheap because it wasn't working. The previous owner had gotten it wet, which is confirmed by the water damage indicators. He said it worked up until he couldn't get it to turn on. I diagnosed an issue with the power button and replaced it. It powered on and worked fine all day. The one issue I noticed was that it wouldn't shut down all the way. It gets stuck on the pink square that says, "good bye" and then I have to remove the battery.
My daughter spent the evening playing Bag Piggies and Happy Street with the sound working fine. After she went to bed I loaded some music on it via a USB cable. I think the sound may have stopped after that, but am not sure. When I got up this morning no sound would come from the speaker or the headphone jack. Otherwise, it works fine. Though no sound comes out of the headphones the player stops when I remove the headphones, so it must know the headphones are in. Sound does work when I connect it to my Blue Tooth speaker. I tried a factory reset, but it didn't make any difference.
I read in another thread that someone said something about the sound, light and proximity sensors are all connected by one cable. I can't test the proximity sensor because I can't use the phone function, but it seems that the light sensor isn't working. With auto brightness on the brightness doesn't change when I cover the sensor or hold it up to light. I did disconnect this cable and re-connect it a couple of times, but nothing made any difference.
sound
What Rom are you running?
It is stock, but it is rooted.
I am pretty sure it is the part that is all connected between the earpiece, headphone jack and sensors. I ordered a replacement from e-bay which looks exactly the same, but the plug is just a tiny bit different, so it didn't work. Frustrating.
You should use Odin to flash a stock firmware first to see if it solve the issue with the shut down.
About the parts, you might have gotten the S4G (T959V) headphone jack which if I remember correctly do no fit the T959. However, the speaker, camera, slimslot and screen are exchangeable between the two.
hi guys i need some hardware infos.
my short story: i got a hox+ stuck in a boot loop it was sure that it was not a software problem so i replaced the battery, that didnt fix the problem after some testing i found out that the problem comes from the power button cable, i pulled the connection off and the bootloop was gone, i repluged it and the bootloop returned. so i thought maybe the screws are fixed to strong, after several plugs & replugs and my decision to not put the top screw back inside and dont fix the other screws so strong, for a little bit more flexibility between the mainboard and the chase the problem went away and seems fixed.
But now a other problem appears, my top ear speakers stopped working, sometimes they work and sometimes not
so my questions are:
1. has the power button flex cable anything todo with the function of the top ear speakers?
2. is it possible that the speaker didnt connect probably because the top screw is missing? did the ear speaker needs a connection to the chase for working?
3. is this w*w.ebay.com/itm/New-HTC-One-X-S720e-G23-Power-On-Off-Button-Flex-Cable-/251492842139?pt=US_Cell_Phone_Replacement_Parts_Tools&hash=item3a8e243a9b compatible with the hox+ (international)?
4. is this w*w.ebay.com/itm/HTC-One-X-Ear-Speaker-w-Adhesive-Replacement-Repair-Part-OEM-/271110152540 the same as this w*w.ebay.com/itm/HTC-One-X-Plus-Ear-Speaker-w-Adhesive-Replacement-Repair-Part-OEM-/281124922511 or are they different?
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.