Hello xda members! I have been experiencing a strange problem with my "T-Mobile G2"'s microphone and would like to share it with you in case you had any insight on it:
My phone's microphone is not working - I cannot use voice input, music recognition services, etc. all it picks up is silence. What makes it a "strange" problem? Well, the microphone will work during calls, but ONLY IF I first snap out the keyboard and then snap it back in! Sometimes the microphone will fade out and then go silent again, at which point I'll open/close the keyboard again so that the other party can hear me again.
I thought it was software at first, but then I flashed it to stock and still had the same issue. Now I'm worried it might be a problem with the ribbon cable that connects the two halves. Have any of you ever heard of a similar problem? Any suggestions as to how I might fix it?
If it is intermittent and you reflashed then my guess would be hardware like you suggested.
Most likely you mic is loose. Does it behave the same as opening and closing if you just hit it or shake it?
Sent from my ghdudsjihfr using dhhcdfhuf.
Thanks for the replies, I honestly didn't expect any! Interesting thing.. I flashed MIUI yesterday and now it feels like the problem is fixed. I've noticed a slight lag before the mic responds the first few times but now it's spot on. I don't see why flashing to stock didn't fix it while flashing to MIUI did so I think it's just a coincidence and that this is still a hardware issue.
I'll try and poke around explore this more when I get more time.
jervill said:
Thanks for the replies, I honestly didn't expect any! Interesting thing.. I flashed MIUI yesterday and now it feels like the problem is fixed. I've noticed a slight lag before the mic responds the first few times but now it's spot on. I don't see why flashing to stock didn't fix it while flashing to MIUI did so I think it's just a coincidence and that this is still a hardware issue.
I'll try and poke around explore this more when I get more time.
Click to expand...
Click to collapse
Do you superwipe?
killj0y said:
Do you superwipe?
Click to expand...
Click to collapse
Yup I did use superwipe.
Incidentally, the issue returned after 2 days of working perfectly. Doing a wipe and then installing that same ROM fresh (not a backup) did not fix it so that new most likely ROM had nothing to do with it. I'm giving up then and calling this a hardware issue, period. I guess it's a good thing that the HTC One phones are are coming out soon!
Related
Good Morning,
Unfortunately my HTC Touch Pro2 has stopped working properly.
Everything works fine except microphone and speaker when I answer a call (or call someone). I can still communicate via speakerphone, but that's rather inconvenient.
Is there anyway I can fix my phone?
(it's out of warranty)
Thanks for all suggestions,
Alec Taylor
Isn't this the answer to your problems?
http://forum.xda-developers.com/showthread.php?t=826396
Thanks JackOS (I use your ROMs BTW), but that didn't fix the problem...
The other caller/call-receiver can hear me, but I can't hear them.
Please tell me what I can do to fix the problem (I tried the .cab, and when that didn't work, I tried the manual Phone->Advanced setting change)
Thanks,
Alec Taylor
If you use my roms there is no need for the fix I provided.
Looks like you have a hardware failure. There is nothing I can do about it.
Did you ever find a fix? My phone started having this issue yesterday.
wizardknight said:
Did you ever find a fix? My phone started having this issue yesterday.
Click to expand...
Click to collapse
If it's a hardware issue, there isn't much to be done software-wise... as Jackos clearly states.
Good luck.
wizardknight said:
Did you ever find a fix? My phone started having this issue yesterday.
Click to expand...
Click to collapse
Most probably your Flex ribbon cable is going bad.
I am having a problem where all vibration/haptic feedback will just randomly stop working completely. Then a few hours (and sometimes days) later it will randomly start working again. It will keep working again for a few hours or maybe days, and then randomly stop again. There seems to be no pattern to it.
I have no idea what is causing this. Has anyone else experienced this, or does anyone have any idea how to fix it?
This is extremely frustrating as I am someone who never uses the ringer; I just always have my phone on vibrate.
I'm running the latest stable release of CM 7.1 for the Evo 4G, but I had this happen before on stock Sense as well.
mredmond2012 said:
I am having a problem where all vibration/haptic feedback will just randomly stop working completely. Then a few hours (and sometimes days) later it will randomly start working again. It will keep working again for a few hours or maybe days, and then randomly stop again. There seems to be no pattern to it.
I have no idea what is causing this. Has anyone else experienced this, or does anyone have any idea how to fix it?
This is extremely frustrating as I am someone who never uses the ringer; I just always have my phone on vibrate.
I'm running the latest stable release of CM 7.1 for the Evo 4G, but I had this happen before on stock Sense as well.
Click to expand...
Click to collapse
I am having this same issue as well. It must be software related because the vibrate function works just fine when the phone rings. I am running CM 7.1 stable on an Evo 4G. I noticed the issue as well on CM 7.0.3.1 or whatever the latest stable build was on CM.
Does the phone ever always (or never) vibrate under a certain circumstance? i.e. incoming text, email, incoming/outgoing call, typing, etc.? Also, do you have any toggle widgets that could affect vibrate/ringer status?
I ask this because, and this may sound silly, it may be that you are modifying settings unknowingly. I've had that happen where I have my hands in my pockets and next thing I know I've accidentally got my Facebook up and running and typed half a book in the status field.
Again, I know that sounds silly but I ask because it's happened to me before.
Concordium said:
Does the phone ever always (or never) vibrate under a certain circumstance? i.e. incoming text, email, incoming/outgoing call, typing, etc.? Also, do you have any toggle widgets that could affect vibrate/ringer status?
I ask this because, and this may sound silly, it may be that you are modifying settings unknowingly.
Click to expand...
Click to collapse
That's fine, its an important clarification to make. But no, I am absolutely sure I have not changed any of the options unknowingly. As I said in the OP, ALL vibration/haptic feedback will cease to function entirely. I've often had it happen that in the middle of typing something, the haptic feedback for the keyboard will just go away. Immediately after this if I check the soft key buttons or test the vibration for notifications, none of these will produce any sort of vibration response either. Then randomly a few minutes, hours, or days later, all haptic feedback will just return. Its been an extremely strange and frustrating issue.
4nth0ny said:
It must be software related because the vibrate function works just fine when the phone rings. I am running CM 7.1 stable on an Evo 4G. I noticed the issue as well on CM 7.0.3.1 or whatever the latest stable build was on CM.
Click to expand...
Click to collapse
For me, when the vibration stops working, it stops working for everything, even when the phone rings. But that's what I can't figure out: if it is a software or hardware related issue. I was having this problem on stock Sense, and I figured if it was software related, perhaps flashing a new ROM (in my case, CM7), would fix it. However it hasn't, so I'm beginning to think if it is indeed a software issue, it must be a bug somewhere very deep within the code, otherwise it has to be a hardware issue. But if its a hardware issue, I can't figure out why it would randomly stop/start working like it does, and the thing is, most (75%) of the time, it is working. Its just the other 25% that annoys the hell out of me. That's why I thought I'd ask and see if anyone else had experienced it or found any solutions.
Its a CM7 thing I've noticed it on Xplod, Decks, and CM7 I don't really mind it cuz my ringers are loud as hell but yeah its pretty weird :shrugs:
Usually AOSP ROMs for some reason have that problem cuz on sense ROMs it never happens
infamousteeboy said:
Its a CM7 thing...Usually AOSP ROMs for some reason have that problem cuz on sense ROMs it never happens
Click to expand...
Click to collapse
Well like I said before, I was having this problem on my stock Sense ROM.....
infamousteeboy said:
Its a CM7 thing I've noticed it on Xplod, Decks, and CM7 I don't really mind it cuz my ringers are loud as hell but yeah its pretty weird :shrugs:
Usually AOSP ROMs for some reason have that problem cuz on sense ROMs it never happens
Click to expand...
Click to collapse
I've never had that problem on CM and I've been using many different versions of it for a long time. I don't know if I am lucky or what but people complain about a lot of issues that are claimed to be CM issues....yet I've never had a single one of them.
Concordium said:
I've never had that problem on CM and I've been using many different versions of it for a long time. I don't know if I am lucky or what but people complain about a lot of issues that are claimed to be CM issues....yet I've never had a single one of them.
Click to expand...
Click to collapse
Well I kinda had the same problem that he's run into on CM but I figured it out but I figured since he's had the problem on a sense ROM also then maybe its not the ROM but I jus went into everything that had the option to vibrate and turned them all on cuz I've flashed a couple ROMs and the vibration would be off I try not complain about anything about any ROM its a person hard work they've done for free I try to figure things out on my own as much as possible before I create a thread not bad talkin the OP but jus sayin you know?
I don't think that it's rom related. I've been having issues with my haptic feedback since I got the phone, even before rooting it. I think it's just a crappy vibrator. (If there's a better name than "vibrator", please someone tell me.)
I had vibration problems on my first Evo as well, it was never rooted. My second Evo was a HW004 and the haptic feedback was perfect - it was softer instead of the shock-like haptic feedback I've experienced with my 003s. My current and third Evo is also a 003, so I assumed it had something to do with the motor used in 003s.
I've just turned haptic feedback off. I thought I'd miss it, but I've gotten used to it. I still use have my phone set to vibrate for notifications and calls and I've seen fewer issues.
If you think you can go without, I'd suggest turning haptic feedback off. Otherwise, unroot and take it into Sprint. You may have more luck calling, because if you can't replicate the issue in front of them then they can't do much.
Sent from my Evo + MIUI using Tapatalk!
plainjane said:
I don't think that it's rom related. I've been having issues with my haptic feedback since I got the phone, even before rooting it...
...Otherwise, unroot and take it into Sprint. You may have more luck calling, because if you can't replicate the issue in front of them then they can't do much.
Click to expand...
Click to collapse
Yeah, its definitely not ROM related...I don't know if people aren't reading the posts, but I've said several times that this occasionally happened on stock Sense, both before and after rooting.
Dang. I didn't want to have to bring it in to get it fixed, but I guess that's what I'm gonna have to do if its a hardware problem...I was really hoping it was software related or if someone would know of a way to fix it so that I could avoid dealing with warranty services...I got suckered into the Best Buy warranty, and it turns out that even though they either give you a new or refurbished model, they make you turn yours in and wait 5-7 days for the replacement to come in instead of ordering the replacement and then doing a trade with you when it comes in. I already experienced it once before when my USB port broke... :/
Not being able to replicate the issue is my main concern since sometimes it works and sometimes it doesn't. Trying to get it to stop working at a time when I can actually run out to the store is gonna be a pain...And I really don't want to waste a trip to the Best Buy store only to have it start working again with me trying to tell the GeekSquad Agent, "I promise, I promise! It was broken just 5 minutes ago!!" I can't imagine how many of those they have to deal with....
Hi guys, I have a strange problem and I couldn't find any Qs and As to it in the forum so I thought I'd post it up and see if someone can help me figure this problem out.
I was running EliteMod and out of nowhere this problem arose.
Whenever I put in my headset the phone would become unresponsive/frozen, and on the odd occasion it would work, but after a few minutes would randomly restart.
I thought it may have been the rom so I flashed another.
I'm now running Cyanogenmod 9 ICS beta 10 and the problem is still apparent.
I'm at a loss of what it could be.
Any help would be great.
Cheers
Edit:
I should add that when I reflashed Cyanogenmod 9, I put the headphones right at the start when setting up a fresh google account on startup, still the same result. Which is why it has me so confused. It came up at random, and a fresh flash won't get rid of it.
kozij said:
Hi guys, I have a strange problem and I couldn't find any Qs and As to it in the forum so I thought I'd post it up and see if someone can help me figure this problem out.
I was running EliteMod and out of nowhere this problem arose.
Whenever I put in my headset the phone would become unresponsive/frozen, and on the odd occasion it would work, but after a few minutes would randomly restart.
I thought it may have been the rom so I flashed another.
I'm now running Cyanogenmod 9 ICS beta 10 and the problem is still apparent.
I'm at a loss of what it could be.
Any help would be great.
Cheers
Edit:
I should add that when I reflashed Cyanogenmod 9, I put the headphones right at the start when setting up a fresh google account on startup, still the same result. Which is why it has me so confused. It came up at random, and a fresh flash won't get rid of it.
Click to expand...
Click to collapse
I had this same problem for two different reasons with two different phones.
The first time, which seems unlikely for you, was a problem with DSP Manager that comes with CM9 causing my phone to crash and restart.
The second is manufacturer error. The phone has a titanium case, and due to some errors in assembly, when I would plug in headphones, the system would freeze and restart. Because I still had warranty, I had it replaced and the problem disappeared.
If you have a multimeter there are ways to check for a short, but I'm not sure if you are familiar with this.
Hope this helps!
Ahh I see.
I guess that would make the most sense... a hardware fault.
I'm out of warranty so I guess no more music via this phone.
Thanks for the advice
blutooth
Sent from my HTC Vision using xda premium
kozij said:
Ahh I see.
I guess that would make the most sense... a hardware fault.
I'm out of warranty so I guess no more music via this phone.
Thanks for the advice
Click to expand...
Click to collapse
If you still want to try and find a solution, get some electrical tape (or another strong insulating tape) and cut off a thin strip lengthwise (about 0.8-1cm width x 3-4 cm length) and tape it to the top of the headphone plug on your headphones so that it blocks any contact with the titanium.
demkantor said:
blutooth
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I use a pair of Bluetooth headphones and a Bluetooth-enabled car radio. But alas, if you care a lot about your sound quality, then Bluetooth certainly is *not* the way to go.
But if you care that much about audio quality, you would have a dedicated device which uses all it's processing power for playback, right?
Hi everybody, for about a week I experience the following annoying problem. When I call someone or receive a call I don't hear the person on the other side of the line through the normal speaker. When I switch to loudspeaker I can hear them loud and clear. The strange thing is that it does not always happen. It is definately not a hardware problem, the speaker sometimes works fine. When I can't hear the person on the other side pressing the volume-up button several times sometimes solves the problem and suddenly the audio works...
I noticed the problem earlier this week after I flashed CM 7.1 again. Before I had an Andromous rom with ICS installed, but I didn't like that one so I flashed my good ol' CM 7.1 again. When I noticed the problem I upgraded to CM 7.2 (with full-wipe) and also flashed another radio. Unfortunately all these things did not work...
Does someone have any idea how I can fix this annoying problem?
Right now the call function of my phone is pretty useless
Ps. the person on the other side of the line can always hear me.
full wipe, multiple rom flashes, even with it being intermidete it sounds like hardware, slight chance the flex is going bad, more likely the speaker needs to be replace or at least fiddled with. any recent drops?
Sent from my HTC Vision using xda premium
It is certainly not a hardware issue. When I install Skype and dial the Echo / Sound Test Service I can hear the everything just fine through the earpiece.
then you aren't wiping properly, fastboot -w or superwipe or both. the stock dialer doesn't have sound issues that I'm aware of and there must be curroption somewhere. change the radio will not change this, flash a vinilla rom after a full wipe and see what happens, don't restore anything
Sent from my HTC Vision using xda premium
*kick*
Still having this problem...Back on CM 9 (RC2) after wiping everything and again flashing a new radio. Matched RIL and everything. Nothing seems to work. Microscope is still working sometimes, but most of the times it doesn't. Does anyone have any ideas how to fix this?
I have seen that others have had this issue and not found a solution as to how they fixed it.
I just bought this phone from ebay and it was working fine then one day I was using Voxer and the mic wasnt working. I tried talking on the phone to a friend and they could not hear me as well. If I reboot the phone the mic works again. Others have said there are 2 mics in the phone and one is malfunctioning at times. Has anyone had this problem? If so how did you repair it?
I have tied installing CM10 (JellyBean) and it seems to work but I didnt test very long to make sure. Jellybean seemed to have issued with the screen and I couldnt install google apps with Clockworkmod and had to install manually. I ended up flashin back to the Normal Sprint 2.3.6 ROM (My Wife like it better). The problem is still there though. Any Help would be appreciated. Thank you in advance.
osxuser001 said:
I have seen that others have had this issue and not found a solution as to how they fixed it.
I just bought this phone from ebay and it was working fine then one day I was using Voxer and the mic wasnt working. I tried talking on the phone to a friend and they could not hear me as well. If I reboot the phone the mic works again. Others have said there are 2 mics in the phone and one is malfunctioning at times. Has anyone had this problem? If so how did you repair it?
I have tied installing CM10 (JellyBean) and it seems to work but I didnt test very long to make sure. Jellybean seemed to have issued with the screen and I couldnt install google apps with Clockworkmod and had to install manually. I ended up flashin back to the Normal Sprint 2.3.6 ROM (My Wife like it better). The problem is still there though. Any Help would be appreciated. Thank you in advance.
Click to expand...
Click to collapse
I'm pretty sure the issue is the connection for the mic inside the phone is loose.
jeffreyjicha said:
I'm pretty sure the issue is the connection for the mic inside the phone is loose.
Click to expand...
Click to collapse
the mic appears to be directly soldered from pics I have seen. I am not sure if it is a surface mount solder or not. The mic works after restarting the phone.
**EDIT** Looks like I was wrong on that. I must have been looking at some other phone. I found this break down of the phone here: h ttp://ww w.youtube.c om/watch?v=g6npRaFm0d4 looks pretty straight forward. I may tear it all down then put it back to gether and see if that corrects it. Thank you