I have been trying to solve an issue with the top microphone while using speaker phone. The mic is working but I have to talk right into it to get it to pick up audio and then it is still very quite and distorted on the receivers end. I have verified there is nothing blocking the pin hole. I have tried full wipe, stock and custom roms with no luck. Now starting to look at the Mixer paths to see if I can boost the sensitivity, but not sure what setting to look for. I have tried changing settings in build.prop, did not help. Any suggestions or pointers in the right direction would be appreciated. Mainly trying to get this working because of Skype, (maybe change mixer-path to use bottom mic).
Issues seemed to start after android 6.
Thanks
Has the phone ever been dropped or disassembled?
Yes, I have taken it apart to verify there is nothing blocking the mic. I am sure I have dropped it as well, no physical damage.
Try the ribbon connection to see they are all seated properly
no luck, cables are good, Top mic is directly connected to main board. Thing that gets me is it is working, but it seems to not be picking up sounds very well.
mcdader said:
no luck, cables are good, Top mic is directly connected to main board. Thing that gets me is it is working, but it seems to not be picking up sounds very well.
Click to expand...
Click to collapse
Mine is the same. I think its time is just done.
Related
Not sure if I have titled the thread correctly if not please can a mod correct.
I am wondering if anyone else is having/had issues with speakers distorting then cutting out when playing any form of audio?
Asus support advised factory reset which didn't fix.
Have DOA code but figured I'd check here before I actually DOA it.
Many thanks
Rikkia
Sounds like a hardware fault and a return is in order unfortunately.
Agree with you stuntdouble,
however now the issue is raised, its in the search should anyone else have problems and need a reference to prior issues.
Interestingly I tried to do a Left/Right audio test and was getting nothing from the left. not sure if its linked in any way to the balance issue I have seen suggested as awaiting a fix.
Roll on Monday when new one should arrive!
Yeah Im one of those with the right speaker louder than the left. The left still works, it's just annoyingly low volume level. Still hoping its a software fix issue, I dont want to have to send mine back. No popping/distorting or cutting out as you describe thank goodness.
i had my first unit for 2 days and it was perfect but the right speaker crackled and then cut out completely. Tried to sort it doing the usual but ended up contacting Comet who had no problem replacing. Was disappointed with carrier as box was water damaged when it arrived but new unit is great apart from some creak. Im just a bit worried about turning the volume up now in case a speaker cuts again!
Did you guys have issues with the sound distorting and crackling all the time? Or did a reboot solve it?
I'm asking because it seems every now and then my audio will crackle and have some static and a reboot fixes it.. not sure if its software that's causing it or what
Sent from my Nexus S using XDA Premium App
I too have improper sound levels, one speaker is louder than the other.
I tried testing my the left and right channel speakers using moboplayer. My observations are that when only the right channel was on (green indication) that the sound actually cam out of the left speaker. Same if I checked only the left channel, the sound came out of the right speaker. This was also true when using headphones. Left chanel only then sound came out of headphones identified as "R" for right channel.
Is the right speaker on the TF not on the bottom right side of the TF as you look at the screen?
Anybody else notice this anomaly? or do I have things backwards?
rikkia said:
Not sure if I have titled the thread correctly if not please can a mod correct.
I am wondering if anyone else is having/had issues with speakers distorting then cutting out when playing any form of audio?
Asus support advised factory reset which didn't fix.
Have DOA code but figured I'd check here before I actually DOA it.
Many thanks
Rikkia
Click to expand...
Click to collapse
Oh~ You can contact RC (repair center) to fix this problem.
i found similar threads and posts but none with this specific problem. i have a b90 from bb, 12/11/11. yesterday out of no where, i lost sound. long story short after reboots and wipes, realized when i rotate or ecspecially shake my tf101, my speaker cut on, then off. when i press hard on the bezel in the middle, they come on briefly. sometimes they stay on.
any insight or answers to solve this so i dont have to do the rma process would be greatly appreciated. after purchase from bb for 299 ( cheaper build to reduce price maybe) i became an asus fan. now, i am really dissapointed in quality since other then this, my tablet is physically flawless and hasnt been dropped or damaged.
edit: both speakers do work when they decide to come on, and heaphones work. thnx in advance
I have cut out and removed my right speaker because it was dead, waiting on an order from asusparts.eu for a replacement speaker
It wasn't a loose wire, it was the connection to the actual cone that was bad, pressing in the middle of the speaker brought it to life for the first time since I bought it, but nothing I could do to fix it, they are more or less sealed and too tiny to fix
so you believe its the speakers? they both seem to work, they just aren't outputting sound until I shake the tablet, push, or sometimes face down they work
Why not just rma it?
dangambino said:
so you believe its the speakers? they both seem to work, they just aren't outputting sound until I shake the tablet, push, or sometimes face down they work
Click to expand...
Click to collapse
Couldn't say for sure, but it sounds like something you could fix yourself if shaking it brings it back on, if you don't mind losing warrantly opening it, but bear in mind, my speaker replacement has already taken 2 weeks and they are not expecting parts until the end of february, so RMA might be quicker, depends if you can put up being without it for a while
honestly i dont want to be without my tf. silly huh. its weird though i just discovered that like i mentioned, headphones work fine, however after i unplug the headphones the speakers immedfiately output sound and continue to do so until i change to another app. e.g.- while watching netflix, then back out and open a game with sound, it doesnt output untilni plug and unplug headphones. this seems to be the best way to get speakers to play.
they donteven seem to cut out with movement afterbthe headphones are unplugged. only when exiting out of current app, then attemptingbtonopen a new one. what is the issuer here?
im lost ast this point. rma aside, this has me curious now
id probally be willing to do it myself, if i knew exactly what i was replacing or repairing or rigging. i purchased a kit with the neccesary t5 torx, and phillips to remove bezel.
how tight should the screws be on the bottom of the tf. i dont want to overtighten. got some petty hope that tightening the screws will help. more sillyness im sure.....
this stinks though cvuz this just happened. you know? thnx in advance.
also lookimg at bluetooth speaker as an alternative
Speakers working after you remove the headphones but stopping again once you launch another app ?
You tried a factory reset in-case its a software / firmware bug ?
Screws just need nipping up, not tightened too much or you`ll either thread the holes or snap the head of the screw
Just RMA it, man.
Hi. noob here.
I have successfully flashed my mt4gs to CM 9 using the instructions here: http://forum.xda-developers.com/showthread.php?t=1508556
So my situation is-- S-ON, unlocked, CWM, and CM9
However, I now find that I have no sound on the internal speaker. Headphones work. To make matters worse, this is a used phone, and I didn't think to test the sound before I started messing about with it, so I'm not sure if it is a hardware problem since I didn't test sound under stock. Does anyone have any thoughts about a fix? Failing that, how do I return to stock to test sound there?
Failed fixes so far, based on other threads:
-just rebooting
-3rd party volume control apps
-CWM factory wipe
-Clearing dalvik cache
-re-flashing the boot.img and reinstalling CM from the .zip
Okay. Looks like it's a hardware problem. The speaker seems to be making intermittant connection. When I whack it firmly, you can hear the speaker cut in for a split second. Not sure what to do about this....
jamdis said:
Okay. Looks like it's a hardware problem. The speaker seems to be making intermittant connection. When I whack it firmly, you can hear the speaker cut in for a split second. Not sure what to do about this....
Click to expand...
Click to collapse
...and I have a sort of fix. I took off the two torx screws on the bottom back of the phone, and removed the small piece of housing down there. The speaker is held in place with adhesive and two springy clips make contact with a piece of flexible circuit material. I cut two little cardboard shims (total about 2-3 mm thick), and jammed them between the speaker and the housing to put a little more pressure on the speaker. So far works great.
Obviously not anyone's first choice for a fix, but it has the benefit of being free.
After I changed my screen on my XT1032 the ear piece doenst work. I replaced it with this but still no joy. The pins for the speaker at installed with the long pins facing the top half of the phone. Speaker phone works fine using speaker phone that how im taking call at the moment.
The connection where the speaker connect on the motherboard looks so basic its hard to imagine that got damaged.
What else can I try?
Thanks bros
cramhead said:
After I changed my screen on my XT1032 the ear piece doenst work. I replaced it with this but still no joy. The pins for the speaker at installed with the long pins facing the top half of the phone. Speaker phone works fine using speaker phone that how im taking call at the moment.
The connection where the speaker connect on the motherboard looks so basic its hard to imagine that got damaged.
What else can I try?
Thanks bros
Click to expand...
Click to collapse
The problem that the coil gets separated very easy from the rest of the earpiece.
It's very easy to replace and the orientation doesn't matter, there are pins both up and down, which are interconnected.
All I can think of is that you either got a defective replacement or you damaged it somehow.
You can test it by connecting it to some audio source at very low volume and see if it works at all.
Nexus 5, 6.0.1, rooted
When a call comes in I cannot hear what the caller says unless I turn "speaker" on. Nothing on earphones either.
Suggestions?
Have you tried using a unrooted stock ROM? Checked for loose internal connections? Clogged grill over the earpiece?
Thanks for replying.
Not yet reflashed rom. Grill holes are clean. Earpiece hole seems clear. Removed and put back the loudspeaker several times with no change.
A loose internal connection is a possibility because I recently changed its cracked screen but I'm not sure which specific connection I should check. It looks OK but I may have missed something not knowing where to check. Which connection would be involved in sending a phone call to the loudspeaker?
I don't have the Nexus in front of me so I am going from memory: is the earpiece a single module with contacts on the side? Contacts are clean and making good contact with the logic board? This happened after changing the screen?
Thank you for hanging with me. After I replaced the screen all was fine including sound. But 3-4 days later it happened. The headphone is socket is a small cylindrical piece. It is possible it was not fit in properly. I will take it apart and check.
The loudspeaker piece just seems to screw back in place. Does it have some connection I am forgetting to reconnect?
The earphone piece was fine.
I switched the speaker component from a working phone and that made no difference.
This is a spare phone and I'm leaving on a trip so I'll work more on it when I return at the end of February. Probably restore an earlier nandroid or reflash and see.
Thanks for the advice.