I've had this Mytouch 4g slide for about 9 months now. It has been good so far, except for the fact that no matter what ROM I'm running on it, and no matter what the T-mobile signal quality on it is, I get poor microphone performance.
What I mean by that is that every few seconds, the microphone becomes completely muffled, and then restores clarity a few seconds later....
Is this something on my side with settings, t-mobiles side, or a faulty phone? It seems odd that the mic would work 100% for a minute, and then die for a few seconds later.
Perhaps I need to update a Kernal or something? I'm running what seems to be 2.6.35.14-cyanogenmod [email protected] #10
The Rom itself is Virtuous Inquisition v4.0.2, but I've tried CM and other ones as well.
Baseband is 10.48.9007.00U_10.12.9007.07_2M
Thanks for any help y'all can provide!
If it goes ROM to ROM and is constant from the same device my bet is hardware.
I had nearly the same thing happen with a GS4G I got on warranty replacement for my original MT4G.
Hastily spouted for your befuddlement
I actually just had this start happening to my phone. I've had it for just about a year now and had 0 problems with the mic. I was swapping some roms around 2 days ago. I made some phone calls and people kept asking if they were on speaker phone. I decided it may be the new ROM I was testing so I restored my backup and called them back. They said it sounded better but still not right. In fact one thought they were on speaker phone immediately before I could ask.
I use an Aegis case and have only dropped the phone a few times. If it's a hardware issue I'd say it failed on its own. Although since it traveled with the ROM change I can only conclude that it is indeed hardware.
xzuhto said:
I actually just had this start happening to my phone. I've had it for just about a year now and had 0 problems with the mic. I was swapping some roms around 2 days ago. I made some phone calls and people kept asking if they were on speaker phone. I decided it may be the new ROM I was testing so I restored my backup and called them back. They said it sounded better but still not right. In fact one thought they were on speaker phone immediately before I could ask.
I use an Aegis case and have only dropped the phone a few times. If it's a hardware issue I'd say it failed on its own. Although since it traveled with the ROM change I can only conclude that it is indeed hardware.
Click to expand...
Click to collapse
prob you have dust clogged the mic (happens freq where i work) try carefully cleaning it out
crimedave1987 said:
prob you have dust clogged the mic (happens freq where i work) try carefully cleaning it out
Click to expand...
Click to collapse
Any suggestions on how to do this? I'm worried something like compressed air would push dirt farther in. If I use something to actually push in the hole I'm concerned I'd cause damage to the Mic.
Related
The phone has such a ground issue that its causing all this, screen issue seems ground issue, wifi, ground, unlock screen, ground.
There is something completely wrong with the way this is grounded causing all the issues, hell even the charger issues could be because of that. I think they need to redesign this thing. I know some claim to have good ones, but Ive had 3 so far with the same issues. I just dont know what to do anymore. Damn g2x wasnt so bad after all.
Any more mad cap theories??
No issues here. Maybe there is a problem with the batch you have been replacing your devices from. No need to redesign the phone.
Sent from my HTC Sensation 4G using XDA App
Not seen any issues with mine, 100% fine.. must be a bad batch or certain firmware revision. O2 UK firmware and phone fine.
Sent from my HTC Sensation Z710e using XDA App
smashpunks said:
The phone has such a ground issue that its causing all this, screen issue seems ground issue, wifi, ground, unlock screen, ground.
There is something completely wrong with the way this is grounded causing all the issues, hell even the charger issues could be because of that. I think they need to redesign this thing. I know some claim to have good ones, but Ive had 3 so far with the same issues. I just dont know what to do anymore. Damn g2x wasnt so bad after all.
Click to expand...
Click to collapse
Any issues I've had were down to the ZDBox app. After I've uninstalled that I've no issues really
Sent From My HTC Sensation using Xda premium App
smashpunks said:
The phone has such a ground issue that its causing all this, screen issue seems ground issue, wifi, ground, unlock screen, ground.
There is something completely wrong with the way this is grounded causing all the issues, hell even the charger issues could be because of that. I think they need to redesign this thing. I know some claim to have good ones, but Ive had 3 so far with the same issues. I just dont know what to do anymore. Damn g2x wasnt so bad after all.
Click to expand...
Click to collapse
Hello guys,new guy here.
There may be a ground issue with the user,not the phone.
Bear with me:
I used to have a good buddy that could never wear a wrist watch for mare than a week.
After that,they died.
It didn't matter how expensive a watch he bought...they all died.
In this case,there could very well be a static buildup coming from the user's body.
Clothes,diet,etc. can affect body chemistry.
If it acts up again,try touching the backside of the phone to a water faucet for a few seconds.
See if grounding out the case helps.
smashpunks said:
The phone has such a ground issue that its causing all this, screen issue seems ground issue, wifi, ground, unlock screen, ground.
There is something completely wrong with the way this is grounded causing all the issues, hell even the charger issues could be because of that. I think they need to redesign this thing. I know some claim to have good ones, but Ive had 3 so far with the same issues. I just dont know what to do anymore. Damn g2x wasnt so bad after all.
Click to expand...
Click to collapse
No issues with mine whatsoever.....
Keep in mind before these blanket statements are made, that most owners do not have all the issues you might have. It's by no means the norm. As others mentioned, you may simply have a bad device....or bad app, SD card.
The vast MAJORITY of owners have no such problems....it gets WAY blown out of scale on these and other forums. It would be better to title your thread "I have grounding issues"...
Also, as always, anyone with major issues needs to make sure they still have said issues after a factory reset with nothing installed, no 3rd party apps, no SD card etc. If ya still have issues after that....ya got a defective device.
The vast majority of Sensations are fine....let's keep it real.
We get it....you're having problems with your device....You don't need to start a new thread everyday....I'm sure this could have went into one of your MANY OTHER THREADS YOU'VE ALREADY MADE. As for your "grounding issue", the same thing was said about the nexus one and the EVO....and in the end NEITHER OF THEM HAD A GROUNDING PROBLEM. Just as this phone DOES NOT have a grounding issue either. That being said, if you're having so many problems, return your phone, and go back to your G2X. There really is no reason for a grown man to be whining so incessantly. You have already started several threads about your many problems...post in those....No need to keep creating new threads every time you feel like complaining.
PS
As the previous posters have stated, no I don't have a problem either.
Cass67 said:
Not seen any issues with mine, 100% fine.. must be a bad batch or certain firmware revision. O2 UK firmware and phone fine.
Click to expand...
Click to collapse
I've got a TMo US Sensation, and it's great. The only "problems" i've noticed is the rare sense lag, but it always clears up in a matter of seconds. And the battery life is amazing compared to my Evo (i can go 2-2.5 days on a charge, same usage level would drain my evo in 10ish hours). While I eagerly await s-off and persistent root, I think this is a very good phone especially so recent after release.
This is your 2nd or 3rd thread that you have made to complain about something. Thread closed, start another thread complaining and I am going to consider infractions.
Hi there,
So I'm relatively new to Android, having moved from an iPhone 3GS to the Galaxy S2 less than a month ago, and I've been looking at custom ROMs and settled on Lite'ning.
I flashed it, upgraded to 2.2 and got it going no worries, and everything was going well until I recieved a phone call. Initially, the other person couldn't hear me, and then when they could they said it was muffled. This happened on calls with 3 different people. I tried reflashing to 2.0 and tested it, and it still has the same problem. Has anyone experienced anything similar, or have any clues as to where I should be looking to fix it??
In the meantime, I'm planning on going back to the stock firmware, just to double check it isn't hardware related (which would be an odd coincidence!)
Thanks!
Right. I went back to the stock ROM last night and still had the issue. Decided to investigate a bit futher, and it turns out I managed to get a pretty solid piece of pocket lint in that tiny little microphone hole. Bit embarrassing ;P
N.M.E. said:
Right. I went back to the stock ROM last night and still had the issue. Decided to investigate a bit futher, and it turns out I managed to get a pretty solid piece of pocket lint in that tiny little microphone hole. Bit embarrassing ;P
Click to expand...
Click to collapse
This seems to be too simple. I am happy for you. However, my case is different. The speaker is clean and the volume is still low.
It was the Microphone mate, not the speaker. And it wasn't quiet, it was muffled. I suppose it was the equivalent to talking through a pillow
How does your volume go via a headset though?
It's just as the title states my nexus s sound isn't working! There isn't any sound at all. Ringtone/notification/media.
When i receive a phone call my phone vibrates but it doesn't ring and when i pick up the phone i can't hear the person i'm speaking to and they can't hear me either.
Had my phone since mid-october,and the first time i encountered this issue is when i put ICS on my phone at the end of december and its been an on and off thing since then but it would last for like 2-3 mins, and it used to be fixed by putting my phone on vibrate, lock it, unlock, turn the volume back up and it would work but that doesn't work anymore i even reverted back to GB and it didn't solve anything
so WHAT CAN I DO TO FIX THIS ? also, do you think it's a hardware or software issue ?
forgot to add whenever i try to use google voice search it crashes
If you plug in headphones, can you hear music? Were you using custom ROM or Stock? Have you tried installing a custom ROM with a complete wipe (factory reset)?
I'd put my money on software. Full wipe (data/factory reset, format /system, format /boot) and then flash your preferred ROM. See if it works after this.
Oogway13 said:
If you plug in headphones, can you hear music? Were you using custom ROM or Stock? Have you tried installing a custom ROM with a complete wipe (factory reset)?
Click to expand...
Click to collapse
Yup, even with headphones there isn't any sound and it first occurred on a custom ICS rom and yesterday I flashed 2 more custom roms with a complete wipe still no progress
Harbb said:
I'd put my money on software. Full wipe (data/factory reset, format /system, format /boot) and then flash your preferred ROM. See if it works after this.
Click to expand...
Click to collapse
just did that and unfortunately it still didn't fix the problem
skillz398 said:
just did that and unfortunately it still didn't fix the problem
Click to expand...
Click to collapse
That's not good
You may be the very unlucky owner of a dead Wolfson chip in the phone. Is the phone still under 1 year old? Might be time to give samsung a ring and hope for the best. If you do decide to take it in, remember to flash a stock ROM and lock the bootloader.
Maybe someone else on the forum has an idea to help you though, but so far i'm afraid chances look slim. You could possibly try heating behind the battery a little with a hairdryer (not too much) and see if it would work afterward, it could just be a dry solder joint on the audio chip, but you'd still want it fixed.
Harbb said:
That's not good
You may be the very unlucky owner of a dead Wolfson chip in the phone. Is the phone still under 1 year old? Might be time to give samsung a ring and hope for the best. If you do decide to take it in, remember to flash a stock ROM and lock the bootloader.
Maybe someone else on the forum has an idea to help you though, but so far i'm afraid chances look slim. You could possibly try heating behind the battery a little with a hairdryer (not too much) and see if it would work afterward, it could just be a dry solder joint on the audio chip, but you'd still want it fixed.
Click to expand...
Click to collapse
*sigh* I feared that its a hardware issue and as far as warranty goes I bought it in 11/2011 and it was bought used so how much would it cost to get that fixed ? Also I restored my phone on a custom 2.3.6 from then rebooted my phone and the sound was working, then after a hour of inactivity, then I rebooted my phone and it started working and got greedy and flashed another rom then the sound was cut off again so should I have hope and try your method of drying ?
I have the same problem. Samsung Infuse 4g. I'm back to stock. Tried everything including GTG and Heimdall. (sigh) Sux. I hope u get urs working again, as I do mine. Saw another post where somebody dropped theirs and it starting working again. Better start praying... Good luck to u!
^^^^^^ i'm about to drop mine for an experiment lol
Hard to say how much. Might be easier to replace the whole board or just one chip, or just because it's too much trouble to find the problem. Also depends on shipping as you'd have to pay to send it to samsung, unless they have some kind of repair centre nearby where you can drop it off - and you'd likely be left without your phone for a couple weeks.
I'd be ringing samsung and asking all of this first. Afterward you may be able to get some quotes from a phone repairer if they can find the problem. These days it's often "throw it away and get a new one", and i'm afraid it's largely the same with phones despite what would be only minor problems/fixes.
OK, y'all. I've got news and info on this issue. First, i have the Samsung Infuse 4g. After trying everything possible short of throwing it into the river, I figured it was def hardware related. I, of course prayed & am convinced that is the real reason it started working, bit jic here is what I did. I checked online just to see (I'm not an idiot, I wasn't going to take it apart. Well, probably not). But I was still all for slapping and twisting and flicking the heck out of it. Then, I decided to look at the other side of it. So I removed the battery and there is a tiny little slit-like hole there. I got out a safety pin and just kinda wiggled of a bit mostly toward the inside of phone. Lo and behold sound was working when I turned it back on. I can't believe it! I'm so happy!
Sent from my SAMSUNG-SGH-I997 using XDA
OK, y'all. I've got news and info on this issue. First, i have the Samsung Infuse 4g. After trying everything possible short of throwing it into the river, I figured it was def hardware related. I, of course prayed & am convinced that is the real reason it started working, bit jic here is what I did. I checked online just to see (I'm not an idiot, I wasn't going to take it apart. Well, probably not). But I was still all for slapping and twisting and flicking the heck out of it. Then, I decided to look at the other side of it. So I removed the battery and there is a tiny little slit-like hole there. I got out a safety pin and just kinda wiggled of a bit mostly toward the inside of phone. Lo and behold sound was working when I turned it back on. I can't believe it! I'm so happy!
Sent from my SAMSUNG-SGH-I997 using XDA
Click to expand...
Click to collapse
Glad to hear that
Sent from my Nexus S using Tapatalk
So I rooted my Skyrocket last week and I screwed something up and since than I've had problems with the audio on the phone part. So I'm running Odin and even after double and triple checking I managed to screw it up by not having Auto Reboot checked. In a panic (and after waiting a long time) I unplugged the phone and powered it down. I booted into Recovery and did a wipe and installed CM 10.1.2 and I swear it worked fine for a week but all of a sudden I started having this weird issue with the phone audio. I'll call a number up and I won't be able to hear anything but I can put it on Speaker and it comes through fine or if I use my Bluetooth Headset it works fine.
I reloaded CM 10.1.2 and still nothing. I tried a nightly, I tried 10.1, I tried Beanstalk, and I now I'm back to stock and no luck on the phone audio. I have no idea what to do. I've tried Google searching and I'm coming up with a bunch of things but not what I'm looking for. I've even found some people having similar problems but they got no answer as well and I'm waiting to hear back from them (I found at least three people reporting the problem over on Cyanogenmod's Skyrocket Forum). I found some reference to it possibly being a Kernel problem. Thoughts?? I'll do some reading up on that tonight.
As a last resort I'm looking into buying a used Skyrocket to replace this one because I'm still 6 or 7 months till I'm eligible for an upgrade. HELP!
Edit, sounds like a hardware problem.
Have you tried to odin back to stock?
jd1639 said:
Edit, sounds like a hardware problem.
Have you tried to odin back to stock?
Click to expand...
Click to collapse
Well I wondered about the hardware problem myself but it was working fine before I flashed everything and was working fine for a while afterwards. But I do have an issue with hardware. A few months ago I ran over the tip of my headphones at work with my chair and broke it off. Without thinking about it I put the tip back and reinserted it back on the phone again. I immediately realized what I had done and when I pulled the headphone jack out the tip remained inside the phone. I'm pretty sure it's caused some odd issues with my phone when trying to play audio using the speaker as sometimes it would play and other times I would hear anything unless I played it through Bluetooth. I took the phone apart thinking I could get to the tip that's inserted in there but it really can't be reached.
With the new phone audio problem I didn't think it was related because it was working fine before and for a little while afterwards. Plus I've seen other people post on the Cyanogenmod Forum about having the same problem so I'm not sure.
So no thoughts on it being a Kernel issue or some other software problem?
jd1639 said:
Edit, sounds like a hardware problem.
Have you tried to odin back to stock?
Click to expand...
Click to collapse
Oh and yes I've tried back to stock with no luck.
dfwjose said:
Oh and yes I've tried back to stock with no luck.
Click to expand...
Click to collapse
Seems like you have your answer then. If the problem persists regardless of which ROM or kernel you're using then logically it would seem that it can't really be software related, right?
Brought to you but time and relative dimensions in space.
dfwjose said:
Well I wondered about the hardware problem myself but it was working fine before I flashed everything and was working fine for a while afterwards. But I do have an issue with hardware. A few months ago I ran over the tip of my headphones at work with my chair and broke it off. Without thinking about it I put the tip back and reinserted it back on the phone again. I immediately realized what I had done and when I pulled the headphone jack out the tip remained inside the phone. I'm pretty sure it's caused some odd issues with my phone when trying to play audio using the speaker as sometimes it would play and other times I would hear anything unless I played it through Bluetooth. I took the phone apart thinking I could get to the tip that's inserted in there but it really can't be reached.
With the new phone audio problem I didn't think it was related because it was working fine before and for a little while afterwards. Plus I've seen other people post on the Cyanogenmod Forum about having the same problem so I'm not sure.
So no thoughts on it being a Kernel issue or some other software problem?
Click to expand...
Click to collapse
You have to get the piece out dude. It's making contact intermittently and killing the audio.
Sent from my HTC One using Tapatalk 4
And just like that I'm up and running again and my phone works. I had given up and was having problems with a CM nightly so I did another wipe and loaded a stockish AT&T ROM that I've installed before and no my phone is working fine. I'm going to leave this thing alone until I pick up a spare phone!!
xcrazydx said:
You have to get the piece out dude. It's making contact intermittently and killing the audio.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
I'm sure it is and that's why I took the phone apart to see if I could get to it. I tried all kinds of things to get that tip out before tearing the phone down and I had no luck. I should have taken some pictures but I've tried tweezers (everything I had was to big or to weak to pull it out) and even glue before resorting to taking the phone apart. Unfortunately with the design it's enclosed all the way around with no way to really get to it. I even thought about replacing it but that piece looks to be soldered on.
In the end, I might just send it back to Samsung and see if they will fix it. Not sure if it's worth it but I never got serious about it because I didn't have a spare smart phone other than my work iPhone.
I shouldn't have spoken so soon. Rebooted the phone and it's locking up now. I give up. I can't find anything that will work. I either have sound with a phone that locks up or have to live with Speakerphone/Bluetooth and be able to reboot.
Well I have been a owner of a LG Nexus 5 for the past (almost) 2 years now, in fact I am coming to the end of my contract very soon and will be able to either goto another company or get a new phone.
Anyways, sometime ago I experienced a problem with my microphone and external speakers not working, or at at least some of the time... After a bit of research online I found out my problem was related to a connection inside the phone that connected the bottom assembly to the main board at the top of the phone. It required me to remove the back panel and a few screws to remove the plastic cover, but the poster suggested putting some tape on top of that connection to hold it down more firmly to the socket it connected too. So I did this. I put some black tap (electrical tape cut to fit.) on top and then assembled the phone again. Viola, It worked!
Well, a short time after I decided that I wanted to update my phone from stock kitkat (4.4.4). Always been curious about custom ROMs and gave Cyanogenmod a try. Not only that I got bold and tried the nightly releases of the new marshmellow update. After some time I started experiencing things not working, like the camera, and a lot of freezing, hang ups and random reboots (not so much the reboots as the constant freezing). Often I couldn't get anything on the screen or the phone to respond from a locked state and when I did, often the phone would lag so much, that doing anything would take a long time and proved to be impossible.
I started thinking it was the nightly releases as the source of my problem and just kind of shrugged it off and figured "they will eventually fix the problem". I kept this thinking for quite some time. But it occurred too me one day that something else was causing the issue I was facing for the simple fact that the lag started showing up in the recovery mode (also custom) and a lot of times would continue to show up after I rebooted my phone. Hence, would rule out any 'software' issues I was facing.
I began to think that my problem was hardware. Maybe it was just time for a new phone. But still months away from the end of my contract, this meant I would have to pay off the 'problematic' phone first before getting a new one. I really didn't like that idea. So while looking into this problem, in a last ditch effort, I opened my phone again. Dunno why but I also decided to get rid of the tap on the connection I tried to fix before... I popped off the connection there and had a look at it. It didn't seem damaged in any way nor did the socket. Strange as it was I put that connect back in the socket and put the cover plate back on making sure not to torque the screws and assembled everything back up....
Now the mic and ext speakers work just fine and the phone is working like I just opened the box and took it out for the first time. And I have not once seen any problems... I understand what's happening here... still just wanted to share that for it was definitely weird or what?
https://drive.google.com/open?id=0B0pUNVcVRCJ7MThMc0NHLUNkSEU
Sorry about the link, only way I can upload an image.
Just so there is no confusion... an image of the effected area, inside the phone. The arrow points to the connector and more importantly the area of the connector that seems damaged. If I press lightly where the arrow is pointing on this image, the assemable at the bottom (speaker/mic) will work, indicating a loose connection. Although after visual inspection, I cannot see any damage to connector or the socket. I suppose the only way to really "fix" the issue is to order a new part. As stated previously, already tried tape on the socket to help hold it down, but that seem to cause just as many issues with the phone performance. Any other suggestions?
When ordering a replacement part, you need to be careful because there was another XDA member replaced the same part with a cheap 3rd party solution and the phone would not charge until he replaced it with an oem part.
http://forum.xda-developers.com/google-nexus-5/help/to-buy-usb-charging-port-flex-cable-t3314357
Does anyone else have issues with there ext. speaker and mic not working?
An update on the phone;
back to square one. My ext speaker and mic will not work. And that socket has something to do with the LCD connection on the screen as it will black out if just the right area on the back of the phone is pressed. Only way to revive the phone is to long-press the power button for a reboot. Then will come up fine but speaker and mic still do not work.
audit13 said:
When ordering a replacement part, you need to be careful because there was another XDA member replaced the same part with a cheap 3rd party solution and the phone would not charge until he replaced it with an oem part.
http://forum.xda-developers.com/google-nexus-5/help/to-buy-usb-charging-port-flex-cable-t3314357
Click to expand...
Click to collapse
Wow, that sounds pretty low level tactics of LG... just shameful really, but not hard to believe these days...
Quite honestly, I am just going to replace the phone. Think I got a pretty good run out of it and think its pretty well time for an upgrade. Anyway, for the reason I got the phone, it wont matter the speaker and mic don't work. Just going to use it for development and it will be a good test device.
Oh an this post is related to this thread so I thought I would link it for it may help someone else facing similar problems....
https://forum.cyanogenmod.org/topic/125227-nightly-cm13-releases-make-my-nexus-5-very-slow/
I'm not sure that LG had anything to do with the low-quality replacement parts.
If I were you, look for a n5 with a smashed screen that is suitable for parts.
audit13 said:
I'm not sure that LG had anything to do with the low-quality replacement parts.
If I were you, look for a n5 with a smashed screen that is suitable for parts.
Click to expand...
Click to collapse
Good idea, except the iphone is the most popular phone around here ... find it pretty hard to find one, been looking. But thanks.
I have seen quite a few busted n5 phones in Toronto. I have managed to get working phones with a smashed screen for as little as $30 which is rare for Toronto. Average I pay is $40 to $50. For this price, I either use the phone for parts in several phones or I get third part screen from Aliexpress for around $40 CAD.
I just want to update this as well...
I am fairly certain (now thinking about causes) its not really a design flaw, but more so because I frequently sat on my phone when it was in my back pocket...
audit13 said:
When ordering a replacement part, you need to be careful because there was another XDA member replaced the same part with a cheap 3rd party solution and the phone would not charge until he replaced it with an oem part.
http://forum.xda-developers.com/google-nexus-5/help/to-buy-usb-charging-port-flex-cable-t3314357
Click to expand...
Click to collapse
It was not me but I had that same experience. Replaced with a cheap oem and it didn't charge after that.
I found out why. The charger usb socket was not connected to anything ! Unbelievable! It lacked the black plastic backing for that part of the cable to connect to.