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!
So I got the Galaxy Nexus GSM today and it's one hell of a sexy device.
It obviously came with Ice Cream Sandwich out of the box. And errors out of the box. Right when I start the phone, Talk FCs. When I try to start the Camera, it FCs.
I though "What the heck, Jellybean probably fixes that", so I unlocked it and flashed Paranoid Android. Everything is a lot faster now, but I still have the same problems, except now Gallery just crashes, which renders the Camera unusable, because they're apparently linked together in Jellybean.
I tried 3rd party apps (Zoom Camera, Paper Camera and a few others) and none of them work.
So it seems that everything that has something to do with the Camera doesn't work.
I tried everything that I could think of;
Reflashing
returning to stock
force stop Camera
Disable and enable all network related functions in G+ and Gallery
Clearing cache - both for individual apps and the option from the recovery
Trying 3rd party apps
Googling everything I could think of
Installing G+ (that made me able to open Gallery, but Gallery still force closes when I open Camera)
Changing battery
Of course I can't see it being anything but a hardware issue, but some people who have compiled CM10 by themselves have the same errors. I don't know if that helps me.
So before I return it some time this week, does any one have any suggestions to what I could try?
I'll give this thread two days before I return it.
Thanks in advance.
You rooted? If not and you know how to root, root it, replace the app (gallery, camera, whatever is not working) with stock JB version. Hopefully it's just corrupted apps... That's easy to fix
Thanks for the reply. I've already tried the Jellybean version of Paranoid Android and it made no difference.
I though "What the heck, Jellybean probably fixes that", so I unlocked it and flashed Paranoid Android. Everything is a lot faster now, but I still have the same problems, except now Gallery just crashes, which renders the Camera unusable, because they're apparently linked together in Jellybean.
Click to expand...
Click to collapse
mrhaxx1 said:
Thanks for the reply. I've already tried the Jellybean version of Paranoid Android and it made no difference.
Click to expand...
Click to collapse
Might be a long shot, but have you tried fixing permissions in recovery?
Sent from my Galaxy Nexus using xda premium
I have, but I just tried again and it made no difference.
Also, I forgot to mention that it's not a storage issue, as I can save screenshots just fine.
mrhaxx1 said:
I have, but I just tried again and it made no difference.
Also, I forgot to mention that it's not a storage issue, as I can save screenshots just fine.
Click to expand...
Click to collapse
Any solutions for this yet? having the same problem.
Nope, nothing yet.
And to make the bad things worse, I've lost the receipt. So I can't even return it.
Bumpity bump!
mrhaxx1 said:
Bumpity bump!
Click to expand...
Click to collapse
I just went ahead and called verizon.. and they're shipping me a new phone today. I see a lot of posts about this, with no solution. It'll be quicker to do it this way. Except you call whatever your carrier is. Or samsung, if nothing else.
Well, you see, I bought the phone refurbished. There was a guarantee on it, but I lost the receipt, so I can't return it or get a new phone.
I ordered a rear- and front-facing replacement camera. It should arrive in 7-15 days because I'm ordering from the USA.
I looked into it, and disassambling and assembling it should be fairly simple. Nearly the same process as the Nexus S, which I've disassembled before.
If it doesn't work, I've only lost $22 and it's not like I have a valid guarantee on it anyway.
Oh well, replacing the cameras didn't work.
And I even managed to break the volume buttons.
Even if I got hold of the receipt, there would be no way they would repair it now.
I can as well just go buy a new phone. Next month. Maybe. At least everything else still works.
When you flash ROM, do you ensure you completely wipe previous ROM and data? Also, if you use something like Titanium Backup to restore your apps after flashing a new ROM, make sure you don't restore system apps or data. That will definitely screw things up in every ROM as incompatible files are mixed.
Try doing a full wipe of your device it could help
Sent from my Galaxy Nexus using xda app-developers app
It was like that on the stock rom.
And yes, I always ensure to wipe everything. As said in the OP, I even tried returning back to stock.
I got the same problem, I GOT IT FIXED NO HARDWARE FAILLURE!!
Hi,
this is what i did, got it fresh from the box, didn't even bother to set-up, I instantly updated to Jelly Bean..
everything worked perfectly, besides the camera, it crashed instantly.. (gallery did not respond)..
i rebooted it 2 times, then pressed the Power button + volume down.. it went to an system boot thingy.. the i connected it to my pc with an usb (usb debugging enabled).
my win7 pc said the drivers were installed, then i pressed the power button. after loading. the camera worked perfect.. thats REALY everything i DID.. i'll keep you posted if it fails again.
it also worked after unplugging the usb.. Hope I helped you a bit.
I can second this fix!
IvanGrozni87 said:
Hi,
this is what i did, got it fresh from the box, didn't even bother to set-up, I instantly updated to Jelly Bean..
everything worked perfectly, besides the camera, it crashed instantly.. (gallery did not respond)..
i rebooted it 2 times, then pressed the Power button + volume down.. it went to an system boot thingy.. the i connected it to my pc with an usb (usb debugging enabled).
my win7 pc said the drivers were installed, then i pressed the power button. after loading. the camera worked perfect.. thats REALY everything i DID.. i'll keep you posted if it fails again.
it also worked after unplugging the usb.. Hope I helped you a bit.
Click to expand...
Click to collapse
So, I was having this exact same issue and was ready to call Verizon for a replacement, when I tried this as a last resort and VOILA!! IT WORKED! I am still unsure of how this all came about, but for the purpose of hopefully helping someone with the same issue, I will second this quick fix as IT DID WORK FOR ME.
I had this same problem (camera/talk fc'ed on start, whenever opening either app), tried all the fixes I could and nothing worked. I eventually disassembled the phone and used a toothbrush and isopropyl alcohol to clean the main board and the connections for each of the camera modules. After a couple rounds of cleaning, everything started working again.
navjas73 said:
I had this same problem (camera/talk fc'ed on start, whenever opening either app), tried all the fixes I could and nothing worked. I eventually disassembled the phone and used a toothbrush and isopropyl alcohol to clean the main board and the connections for each of the camera modules. After a couple rounds of cleaning, everything started working again.
Click to expand...
Click to collapse
Thanks for this information, I'll try to do it with mine too. Any results I will post here.
This never used to happen but in the last week has.
While using it, whether I'm in GoSMS Pro, or Chrome or even in the homescreen the screen will fade to black then back one to three times. It almost feels like proximity detection but there's absolutely no obstruction nor am I in a call.
Running 4.0.4 stock unrooted, latest update from Rogers.
Has anyone had this? Getting a bit worried!
Screen blacking out randomly
I'm also having this problem. I'm also on Rogers but I'm am rooted. I am however still using the stock rom. It all started happening after I did the latest update. Any help would be appreciated.
dropzone01 said:
I'm also having this problem. I'm also on Rogers but I'm am rooted. I am however still using the stock rom. It all started happening after I did the latest update. Any help would be appreciated.
Click to expand...
Click to collapse
YES! Finally I'm not alone.
I was worried this was isolated. This confirms even more my suspicion it's a software not a hardware issue. The other reason why it would be so is because after it flashes off and on, the screen elements also do, which indicates the software is trying to refresh the display. If it were hardware it would likely not fade flash and nothing would change on the screen.
It sounds like the software update caused it as I noticed it started after installing it.
I ended up doing a hard reset yesterday after having had no responses. I am hoping it might help. I hate having to reinitialize so much crap while unrooted though. I was hoping to keep it stock and not worry about saving app data until Jelly Bean official stock is out. Oh well.
I also learned S Memo Samsung account syncing doesn't work. Good thing I made a Kies backup. Sigh...
Victorminator said:
YES! Finally I'm not alone.
I was worried this was isolated. This confirms even more my suspicion it's a software not a hardware issue. The other reason why it would be so is because after it flashes off and on, the screen elements also do, which indicates the software is trying to refresh the display. If it were hardware it would likely not fade flash and nothing would change on the screen.
It sounds like the software update caused it as I noticed it started after installing it.
I ended up doing a hard reset yesterday after having had no responses. I am hoping it might help. I hate having to reinitialize so much crap while unrooted though. I was hoping to keep it stock and not worry about saving app data until Jelly Bean official stock is out. Oh well.
I also learned S Memo Samsung account syncing doesn't work. Good thing I made a Kies backup. Sigh...
Click to expand...
Click to collapse
Update: unfortunately the hard reset did not fix it. Problem has returned as of Sunday. I hope Jelly Bean comes soon. :S
In the meantime I'm talking with Rogers about this and pointing them to this thread.
Temporary solution found
Victorminator said:
Update: unfortunately the hard reset did not fix it. Problem has returned as of Sunday. I hope Jelly Bean comes soon. :S
In the meantime I'm talking with Rogers about this and pointing them to this thread.
Click to expand...
Click to collapse
I think I've solved it, but this may not be a solution for most people experiencing this (my friend also had this issue). In my case removing the game Modern War solved it.
I remember that after I installed it, the system started doing these flashes. It now has been behaving ok for 4 days since uninstalling it.
I don't think the game itself is the cause, but rather there could be some background task from it (it does occasionally push game event updates as notifications) that doesn't like the 4.0.4 update. In this case I can't quite identify what nor do I know how to diagnose it.
Just thought I'd update people in case they still have this issue. It may be one of your apps, essentially. It sucks and it shouldn't happen, but alas unless we test with a new stock OS update, we won't have much to eliminate it without removing the offending app.
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
My external speaker stopped working, and I'm not sure if it's a hardware or software issue. The phone doesn't ring, and if I try and play anything through the external speakers no sound comes out. My headphone jack is working, and I'm able to make/hear calls.
I'm running CM 10.1.3, and I've been running this rom without any problems for a while. In trying to fix/troubleshot this issue I ran across the Galaxy S3 hardware test via the phone/dialer *#0*#, but this doesn't work in CM. Is there any way to check hardware in CM? Or does anyone know how to fix this if it is indeed a software problem?
I've checked all my volume settings and tried the following:
Rebooting
Re-installing CM, multiple versions
Pulling the Battery
Sounds like some kind of hardware failure. Flash back to stock after you do a nandroid to make sure.
metalfan78 said:
Sounds like some kind of hardware failure. Flash back to stock after you do a nandroid to make sure.
Click to expand...
Click to collapse
It seemed like a hardware issue to me too, then I did a factory reset and flashed a stock 4.3 ROM and the sound magically started working again!
Did you have the "Silent" profile on when on Cyanogenmod?
-Whiplashh
Sent from a Premium Xda app using the Flo Nexus 7.