OK so this has been an issue for several months now and its gotten worse.
The ear speaker has been working intermittently and will usually not come on at all.
This seems specific to CM7 because flashing back to CM6 it works fine.
Problem is: Speaker works randomly, at first i thought it was hardware issue but every time a loud sound or voice was played through it would come on.
I would use a saved voicemail and play it a couple times and that would usually kick the speaker to work. But as of recently its doesnt come on at all, only when it wants to.
I have no idea if this would help, but using OSMonitor's log, whenever i tried to play a sound through the ear speaker it would always log audio_disable().
Sometimes reboot works, mostly it doesn't. Ive done clean wipes, fresh installs, and reverting back to previous nightlies and stables. it only has gotten worse with newer updates.
I've looked everywhere for an answer. I dont mind uploading a log, just dont no what to exactly copy for the speaker.
it happpened to me too.
Called tmobile.. pretended to run the test they told me to run.. they then agreen that it was broken internally, and sent me a replacement.
Then I un-rooted my phone, sent it to them, and life is good now
lol
do it..
any other ideas on whats causing this??any solutions besides the return?? ha
I dont know if this is a coincidence or not.. but my speaker died as soon as I flashed the Salsa Slide ROM.
I have had no issues previously.... and I am not trying to pin the blame, it just seems coincidental.
I do have a slide that I bought right at launch, so I dont know if that has anything to do with it...
Either way, I will be calling today to get it replaced because when I flashed back to NB-mod I still could not hear from the internal speaker.
Related
Having severely scratchy, distorted music audio that usually starts after a few hours of regular use of stock music player, Doubletwist and Pandora. Also happens when automatically going back to music after answering an incoming call through my BT mono. Really strange. And when it kicks in, even my notification tones begin to sound scratchy (but oddly my ringtone sounds fine). A reboot fully corrects the issue... for a while, at least... but that's a pain and drops my battery between ~2% - 8% each time.
I clean my cache automatically daily. Thought it was a rouge app and monitored for a while through SP, but still coming up empty. And of course, I've changed up my ringtones with the thought that my regular one was blowing my speakers (I'm a child of the 80's and lost my hearing to death metal concerts in my youth, so I have to have my ringer just a notch above blaring )
Tried Timat's (same issue), now back on Sav's kernal. Tried full wipe & Calks format, flashed back to Sense, a fresh download of the ROM I'm using, did all this twice. Tried to disable stagefright in the build.prop using GScript so I could re-able when necessary (didn't work either).
Has anyone come across this? Many thanks.
jedijackie said:
Having severely scratchy, distorted music audio that usually starts after a few hours of regular use of stock music player, Doubletwist and Pandora. Also happens when automatically going back to music after answering an incoming call through my BT mono. Really strange. And when it kicks in, even my notification tones begin to sound scratchy (but oddly my ringtone sounds fine). A reboot fully corrects the issue... for a while, at least... but that's a pain and drops my battery between ~2% - 8% each time.
I clean my cache automatically daily. Thought it was a rouge app and monitored for a while through SP, but still coming up empty. And of course, I've changed up my ringtones with the thought that my regular one was blowing my speakers (I'm a child of the 80's and lost my hearing to death metal concerts in my youth, so I have to have my ringer just a notch above blaring )
Tried Timat's (same issue), now back on Sav's kernal. Tried full wipe & Calks format, flashed back to Sense, a fresh download of the ROM I'm using, did all this twice. Tried to disable stagefright in the build.prop using GScript so I could re-able when necessary (didn't work either).
Has anyone come across this? Many thanks.
Click to expand...
Click to collapse
Well, you've tried everything I would've suggested...tried different kernels, flashed backed to sense, performed a full wipe, etc. I would think that flashing back to stock would've alleviated the issue if it was software related. Perhaps your speaker is starting to fail? I've seen many people reporting needing to replace the speaker. However, it is indeed odd that its intermittent, you'd think that if the speaker was failing, it'd be consistent, and a reboot wouldn't clear it up. Odd, but I don't know what else to suggest. Have you tried tweaking the settings using DSP manager at all? If all fails, and being on stock sense doesn't fix it, I'd unroot and have it looked at by Sprint probably.
Crap, I was afraid someone would say return to store (which isn't the end of the world cuz I got it through BB and they REALLY don't care if it's rooted or not. They'll just hand me a new one). Sigh... too bad too, because I got everything else running perfectly (finally) with no fc, reboots, smooth as butter save for my music.
And yeah I played around with DSP also.
Many thanks, K2. I appreciate your response.
jedijackie said:
Crap, I was afraid someone would say return to store (which isn't the end of the world cuz I got it through BB and they REALLY don't care if it's rooted or not. They'll just hand me a new one). Sigh... too bad too, because I got everything else running perfectly (finally) with no fc, reboots, smooth as butter save for my music.
And yeah I played around with DSP also.
Many thanks, K2. I appreciate your response.
Click to expand...
Click to collapse
You definitely seemed to try just about everything but did you flash a Stock RUU? I'd nandroid backup and flash it to see if the problem still exists, if you've tried that then you would only have one option left, take it to BB. Best of luck either way.
Huh... haven't tried a Stock RUU. Good call! I'll try now and report back. Thanks Blake.
jedijackie said:
Crap, I was afraid someone would say return to store (which isn't the end of the world cuz I got it through BB and they REALLY don't care if it's rooted or not. They'll just hand me a new one). Sigh... too bad too, because I got everything else running perfectly (finally) with no fc, reboots, smooth as butter save for my music.
And yeah I played around with DSP also.
Many thanks, K2. I appreciate your response.
Click to expand...
Click to collapse
You're welcome, sorry there isn't more I can suggest. As Blake said, run RUU to unroot, which I would do before you take it in anyways. (What I meant when I said "unroot and take it in). If its still out of wack then, take it in.
Sent from my PC36100 using XDA App
I attached the Stock rooted RUU but visiting HERE should return you to unrooted stock evo.
i have been having issues with no sound coming from the LG nitro , all of a sudden it cut out yesterday and have hard reset numerous times and 1 out of 4 or 5 reboots the sound comes in but if you power off then on the sound disappears .. this is a stock phone with only root , anybody have any ideas or similiar issues ?
This is not any kind of development related topic but I'd suggest that you bring it in for repair or replacement as that sounds like a hardware issue. Maybe try flashing another rom.
Sent from my LG-P930 using XDA App
moved to general
I had a similar issue and ended up returning the phone to bell for a new one.
Here is the long story just in case it helps some one. Like all good Android users I started by rooting my phone, installing ROM Manager and making a nandroid backup. Once this was done I ran rooted stock for a few days. All was well.
Then I started to debloat my phone. After which everything seamed good. Then installed and played with RAM Manager and SD Speed Increase. TBH i did not notice any particular increase in speed on my phone but that might be due to the following issue.
After all this I decided to run a few test by using the phone into the ground. Added a bluetooth headset, while using navigation and making several calls. It was all running very well until I rebooted. Once rebooted whenever I connect my bluetooth headset I was no longer able to make calls. The phone dialer would completely lag out until I de-activated bluetooth. The the 10 or so test calls I tried making would all go through at once. This wasn't the end of the word for me so I continued to use the phone as everything else was working fine. The things started degrading by which time I was on the new CM9 nightly build. The phone had started being really sluggish. I finally decided to return my phone after it would no longer play any sound and whenever it called to any sound related function would lag out and/or reboot. The same behavior happen in stock, cm9 and NO! NO! ROMs. I tried flashing a few roms in a last ditch effort.
I could be wrong by my conclusion is that the audio portion of the snapdargon chip fried and since these phone are basically just 1 chip the phone simply degraded from there.
I would like to know of anyone else has had similar issue or if I just got a lemon and also your take on the cause of the issue.
Hope this can help someone.
Thanks!
Edit: Returned my phone for a new one and I've been flashing CM9 since the first release and no issues. I'm actually really happy with the replacement and would recommend the phone as long as you don't get a lemon ;-)
I finally decided to root/s-off/ROM last week, and after following the many excellent guides around I got to a place where I liked the features and speed of the ROM I settled on (Incredible 2 HD 4.something).
Here's a breakdown of what I passed through to downgrade/s-off/root/recovery/ROM:
Friday
Downgraded from 2.3.4/Hboot0.98. Successful.
Installed CWR, su, busybox. All well.
Boot once into stock VZW GB 2.3.3.
Grab full nandroid backup of "stock" 2.3.3 as a failsafe.
Back to CWR 5.0.2.0. Installed CM7 / gapps. All still well. I wanted Sense back, so hunted for a good candidate ROM.
Settled on Incredible 2 HD from themikmik.com
Initial flash acted like I wasn't rooted (CWR .zip install said (bad) when I selected the ZIP. md5sum is perfect, so it's not a bad copy. Battery pull later and a few full wipes, install is fine.
Saturday
Inc2HD ROM is really sluggish so I decide to nuke it from orbit and start over again.
I grab the Super Wipe script and run.
Reinstall DInc2HD ROM.
Rom is very responsive, acting much better.
Start reinstalling all my apps again.
Deal with the stupid problem of sms messages from VZW (http://www.droid-life.com/2011/06/2...age-from-vzwnmn-here-is-how-to-stop-them/]fix detailed here[/URL]).
Receive and place several calls as normal throughout the day.
Gradually reinstall apps only as I need them. Keeps down the clutter
Sunday
Receive and place several calls as normal throughout the day.
Gradually reinstall more apps only as I need them.
Getting to a good state with apps re-authed and reinstalled. Decide to grab another nandroid checkpoint backup.
Backup is fine, resume normal daily use.
Monday (today)
[*]Alarm goes off as intended (yay - I have 'Clock' back after being missing on my phone since 2.3.3!)
[*]Listen to some spotify paired to my car on the drive into work
[*]Colleague calls me .. and I can't hear him. I figure it's a bad connection so I call him back. Still can't hear him through the earpiece. As a quick test I switch to speakerphone, I can now hear him.
I figured this was a one-time thing, but start test calls to DInc2 from my desk.
Damn - earpiece isn't passing any audio. Speakerphone toggle gets me audio, as does plugging in my 3.5mm earphones.
I then test other apps I know I can toggle to playback through earpiece, and no dice (Google Voice, etc). All I can hear is a very very faint buzz while a call or playback should be coming from the earpiece. When I hang up, the faint buzz in the earpiece goes dead again.
Made sure bluetooth radio was off to rule out pairing to other devices (though I haven't re-paired since wiping anyway). No wifi radio on either. All alone with the mobile network radio.
Now I know I've done a lot to the phone over the weekend, but I can't find any common cause of what might have happened between the last good call I placed on Sunday evening and today (Monday). Phone sat all night charging on my nightstand. No physical damage or anything like that.
Thinking this may be a ROM or app issue, I bounce back to my known-good snapshot of the 2.3.3 stock ROM. Problem persists - crap.
To further rule out, I full wipe and install CM7.1.0.1 from scratch just to get another baseline. Still no earpiece audio - getting frustrated!
Whatever it is, it isn't exhibiting signs of being a ROM or app issue because it persists full wipes (wipe/cache clear/dalvik wipe, and another pass even with the super-wipe script).
Yes, I've checked basics like making sure In-Call Volume is not muted. I've also installed Audio Manager to make sure there's not some lurking audio volume problem. All sliders maxed before, during and after test calls.
Uninstalled any audio-related app to attempt to remove any hold on audio output. But recall here - it's following across ROMs and wipes, so this is just busy work.
Logic says then that either
I hit some rare bug?
The process of mucking around with recoveries, ROMs, and other lower-level items has flipped a bit somewhere that will persist full user-space wipes/partitions/formats.
it's faulty hardware (which I have a hard time believing, but stranger things have happened!) This would just have to be horrible timing.
Searches on here and other sites don't bring up too much for the Incredible 2 and this kind of earpiece issue. There's a passing mention of a "silent audio bug" here, but doesn't seem relevant (nor much detail given).
I've grabbed output 'c:\> adb logcat -v time -b radio > alogcat.radio.txt' while making a call and switching between earpiece (default) and speakerphone. No really good clues there. Changes in logging verbosity didn't show too much of interest. I'll pastebin it after I scrub my phone number out if anyone's interested.
So after the wall of text ... anyone have any ideas?
I'm in it to win it with this, so I'm not unrooting and warrantying this pig I'm due for a new phone but there's nothing I want other than to just have my DInc2 back working.
I'm off to keep searching. Wondering if there are other debug-level tools/switches via adb that'd let me poke at devices, but I'm guessing those interfaces may not be as readily exposed as I'd like.
Thanks in advance all.
tl;dr - Incredible 2 earpiece randomly stopped working, but speakerphone and headphones still output phone call audio fine. Follows across wipes/ROM installs. LOLWTFBBQ?
I hate to say it, but your earpiece is probably broken... U may have smashed it with your keys in your pocket (did that on og dinc)...
Sent from my Incredible 2 using xda premium
If speakerphone and headphones work, but you cannot get sound at all from the earpiece then that would lead to me to be hardware issue... Electronics break man.. unfortunately.. and when you try to think that there is nooo way possible that you could've broken it, that's usually when you do.
Sent from my Incredible 2 using xda premium
faehsemc said:
If speakerphone and headphones work, but you cannot get sound at all from the earpiece then that would lead to me to be hardware issue... Electronics break man.. unfortunately.. and when you try to think that there is nooo way possible that you could've broken it, that's usually when you do.
Click to expand...
Click to collapse
Fair enough. I hadn't ruled out full-on hardware failure I just found it to be the least-likely of the candidates.
I had to replace the speaker in my original Incredible, so I figure it can't be too much tougher to do in this one. I'm going to exhaust some other troubleshooting first (my wife has a functional stock DInc2 that I want to compare some logcat output from, see if anything stands out when making a standard voice call).
I'm always careful to change ONE thing at a time then test to make sure my variables are where I expect them to be, so this one threw me. I'll post back with results, and hopefully get my earpiece back .
OK, I ordered a replacement earpiece and replaced it. This did not fix the audio. I tested both the original earpiece and the new earpiece before installation by using a low speaker-level source and confirmed that BOTH actually work fine and produce sound as expected.
While the phone was disassembled, I made sure all contact points were good for the earpiece. This isn't a physical problem.
So, this takes me back into the software/firmware/radio arena.
And more specifically, in order to persist all wipes and reinstalls, this has to be something below.
I'm going to use adb to flash a radio (I think there's one newer than the one I have installed, something.622? Not down at bootloader to check right now).
If this doesn't do it, anyone want to buy a DInc2 for parts and dev?
The newest radio is .1111 before that .722
Sent from my Incredible 2 using xda premium
Good call on the 1.09.01.1111 firmware. I found and flashed that instead of .722.
No effect unfortunately.
So next I'm thinking that perhaps whatever kernel I brought with me from the first ROM flash could have jacked something up in terms of audio modules or packages. It's a long shot, but I'm going to grab something like nc2_2.6.35.14#21-2.3.4.zip (non-AOSP) and flash that.
Now that I have ruled out actual hardware failure, I'm just too stubborn to give up on this .. open to productive ideas on things to check, methods to troubleshoot or rule out, etc. TIA.
What about Tue hardware connection from the speaker to phone itself? I don't know much of the board on the phone so I can't give you ideas of where to test, but if you can see where the leads go I would say follow it
Sent from my Incredible 2 using xda premium
Right. I disassembled the phone again late last night and traced back to the extent I could follow. I didn't find anything glaringly obvious or bad.
Also of note, if I'm in a super-quiet room and keep the earpiece near me with no call in progress, I hear literally nothing. As soon as a call is initiated, I hear a very faint "sputtering" sound from the earpiece (original or new earpiece), which means the symptom here clearly impacts either speaker.
So something upstream from it ... whatever pathway sends audio to this device isn't getting instantiated properly? That'd make me look to the kernel or driver to understand what pathway does work when routing audio output to the rear speaker that doesn't properly route it to the earpiece for the same call.
Recapping for my own sanity:
- Physical causes == none seen, mostly ruled out via disassembly and inspection, earpiece replacement with known-good part and known-good reassembly.
- Radio == upgrade to .722, .1111 and back to .622, no change.
- ROM == not likely culprit (problem persists any ROM replacement)
Can't fight off the nagging feeling that the act of starting down the road to S-Off + su + rooting did something here.
Given that there are guides to un-rooting (don't think you can un-S-off per se though, right) I may give that a shot since this phone is essentially a guinea pig now. Going to see how far down this rabbit hole I can go.
While I'm stewing on that does anyone have links to android filesystem reference material? I'm thinking the high-level relation between things like bootloader, recovery partition, user-space filesystem and on which levels I can address these with tools like adb. I want to try to understand if some bit could have been flipped at a layer lower than what flashing a ROM or kernel can recover, but perhaps higher than a baseband radio flash. Knowing where all these live and how they interrelate sounds interesting to me. Then I can form a better working theory on what could cause the stupid problem I'm having and if it's plausible to be in software/firmware somewhere.
There is an unrooting guide on YouTube. I find it hard to believe its software, but I work on a radar weapon system that has proven me wrong many times... But if you have flashed multiple roms then the kernel would've been reflashed atleast once and if you are doing a full boot and system wipe, whatever drivers previously installed would have been overwritten... I'm leading to believe there is a shorted componant on your board and because the voltage is so low on these, there moght not be any visual evidence. Unless u have schematics of what voltage is applied where, there isn't a way to test most of them. Especially if the gates are set to be low when applied, vice highs. I would s-on factory reset and of that doesn't work, its hardware
Sent from my Incredible 2 using xda premium
Agreed. I work with enterprise hardware/storage/cluster systems, so I'm driven by nature to root cause this silly thing - but yeah, occam's razor seems to say here that it's just a really stupid coincidence that some random component failed just at the time I began making other changes. And I can't let it go
This is even more frustrating to me because I always make a point to introduce only one change at a time then test the outcome!
After poking through the SDK/reference guide about AudioManager, I was reminded that GV has access to the earpiece audio path. While I could just make test calls in/out, this saves me from burning minutes in the process.
As a quick-and-dirty workaround (for anyone who may stumble on this in the future), you can use Google Voice to act as an internal earpiece playback test tool.
Install and then go to settings and tell it to play back via the earpiece by default and not the speaker. Then (assuming you have voicemails to play), attempt playback. You can toggle between the two audio outs in a much quicker way than I've seen in any other app. Works close enough for me to serve as a test tool as I make discrete changes as I go through troubleshooting.
Maybe there are other media playback apps that'd offer a toggle to the earpiece for playback (but why?), though I didn't look. Seems like the AudioManager reference guide implied that the earpiece was a more "protected" audio path than the speaker (but that's likely just for actual carrier network voice calls).
Cheers,
I'm really getting a kick troubleshooting.. I've been recruiting for a year and a half now.. miss working on gear.. one and a half years left and back to my ship... Can't wait
Sent from my Incredible 2 using xda premium
I actually doubt it's your ROMs --- I'm running latest unmodified vz gingerbread and all of a sudden about 5 days ago I could no longer get earpiece to function - my only guess is something shorted out because of an off-market USB charger that I got 3 of for 7 dollars off Amazon...
Anyways, I had the same sorta flutter that you seem to hear when on a call and there should be sound... and otherwise silence when silence is expected... anyways I replaced it with a brand new earpiece and EXACT same issue is happening still.
Not sure whats up but this may be the world telling me to use my Bluetooth headset more anyways... I'll post if I find anything that fixes it, but I ain't gonna hold my breath given how few ppl seem to be experiencing this issue.
Good luck
I have the Verizon Galaxy Nexus, running the 6/12/12 nightly for CM9, and everything was running great until this afternoon. I haven't dropped my phone, gotten it wet or anything like that.
Now whenever I receive a call or make one, I can't hear the other person and they can't hear me. It was working at around 11 this morning when I got a call, but not after around 5, and I hadn't done anything with it.
I tried flashing to a different ROM to see if that would fix it, so I flashed to the latest MIUI, wiped data/cache, and when I rebooted it, I noticed a headset icon in the notification bar. Curious, I plugged in my headphones, and I could hear youtube (which I also tested earlier and I couldn't hear). When I unplugged them, the headset icon remained, and I remained unable to hear anything.
I don't know why, but I restored my backup of CM9, tried everything again, and it didn't work. So I tried plugging in my headset again, and the music app that I use recognized that I plugged them in and started playing music, it stopped when I unplugged them, but I still couldn't hear anything through my normal speaker.
I looked around the forum and found temporary solutions that involve installing an app that forces the phone to use the speaker, however I am hoping to find a more permanent solution.
I'm about to reflash back to stock 4.0.2 and see if that helps, I'll post back if it does.
EDIT: Nope, didn't work. Please help.
EDIT2: Just relocked my bootloader to send it in ...and it started to work .-.
I'm going to reflash CM9 and hope that everything works out.
Do you guys think I should still have it replaced?
Had a similar experience
Headset being detected even when not connected seems to be a common bug on Gnex, have seen several posts and I myself had to go through this. It usually gets fixed by itself in a day or two.. but till then use the "toggleheadset2" from the play store, which would allow you to manually say when the headphone is connected or not.
--Vj
PhreeqQitsikk said:
I have the Verizon Galaxy Nexus, running the 6/12/12 nightly for CM9, and everything was running great until this afternoon. I haven't dropped my phone, gotten it wet or anything like that.
Now whenever I receive a call or make one, I can't hear the other person and they can't hear me. It was working at around 11 this morning when I got a call, but not after around 5, and I hadn't done anything with it.
I tried flashing to a different ROM to see if that would fix it, so I flashed to the latest MIUI, wiped data/cache, and when I rebooted it, I noticed a headset icon in the notification bar. Curious, I plugged in my headphones, and I could hear youtube (which I also tested earlier and I couldn't hear). When I unplugged them, the headset icon remained, and I remained unable to hear anything.
I don't know why, but I restored my backup of CM9, tried everything again, and it didn't work. So I tried plugging in my headset again, and the music app that I use recognized that I plugged them in and started playing music, it stopped when I unplugged them, but I still couldn't hear anything through my normal speaker.
I looked around the forum and found temporary solutions that involve installing an app that forces the phone to use the speaker, however I am hoping to find a more permanent solution.
I'm about to reflash back to stock 4.0.2 and see if that helps, I'll post back if it does.
EDIT: Nope, didn't work. Please help.
EDIT2: Just relocked my bootloader to send it in ...and it started to work .-.
I'm going to reflash CM9 and hope that everything works out.
Do you guys think I should still have it replaced?
Click to expand...
Click to collapse
---------- Post added at 10:27 AM ---------- Previous post was at 10:17 AM ----------
Only permanent solution is to change the socket. Its the switch inside which usually gets jammed.
Same exact problem
I am having this same exact problem. Its fine on stock, once I flash CM10 calls say connected and the time starts ticking but I can't hear a thing and no one on the other end can hear me.
Sometimes when I do connect, the person will hear me for a couple seconds and then it'll drop then connect again then drop...over and over again.
Google now doesn't pick up any voice searches either.
HELP, this is a relatively new issue. (2-3 months old) I've had the nexus since January and had it rooted and rom'd shortly after. Only recently has this issue cropped up.
toggleheadset2 seems to work but it sucks that I even have to use it. Any devs out there have suggestions/input? I've looked all over for a resolution.
Please don't make me go back to stock....Please!
Have AT&T Note 4 since launch. Stock, not rooted or anything like that. Not sure when this problem started because I don't regularly make calls, but I think within the last week or two, possibly after I got the update to COC6 (the update seemed to complete normally, though).
Every time I place or receive a phone call and attempt to use the phone normally (hold it to your head), the person on the other end cannot hear me at all. If I switch to speakerphone, they can hear me and it behaves normally, and if I connect to a Bluetooth device like my car, it also works fine, but if I try to use the phone normally, they cannot hear me. I can always hear them perfectly.
For what it's worth, Google won't pick up my "Ok Google" from the home screen anymore either. Also, I had previously had the option to wake the phone with "Ok Google" disabled, but when I try to enable it now, it hangs on listening to me say "OK Google" 3 times... as if it never hears me say it.
The microphone appears to be working completely normal for everything else I've tried, it's just acting like it's on mute when I'm in a call and not on speakerphone or Bluetooth, and the OK Google stuff isn't working either.
Any ideas? I'm trying not to factory reset... I've searched a lot and not found anything where anyone has solved the issue.
FWIW I had the same issue randomly with my rooted Note 2, and I believe I either fixed permissions or reinstalled the ROM to get it working (can't remember). I wish I could just reinstall the ROM or latest update (COC6) again so I don't have to factory reset. Is this an option at all?
Of course right after I post I solve it myself, but I'll share the fix for my case in the event that it helps anyone. The left hand bottom mic hole next to the USB port was plugged with some gunk (I could clearly see it plugged up completely). I used a safety pin to carefully clear it out and that fixed it. Works normally now. I had originally ruled out this kind of thing being a problem because everything was fine with speakerphone so I thought the mic was ok, but I guess maybe it only uses one mic or something? I suppose I was also swayed by the fact that my previous Note did have a software problem causing the same thing, so I figured this was probably software too. But nope, good to go after checking the mic hole!
pj_rage said:
Of course right after I post I solve it myself, but I'll share the fix for my case in the event that it helps anyone. The left hand bottom mic hole next to the USB port was plugged with some gunk (I could clearly see it plugged up completely). I used a safety pin to carefully clear it out and that fixed it. Works normally now. I had originally ruled out this kind of thing being a problem because everything was fine with speakerphone so I thought the mic was ok, but I guess maybe it only uses one mic or something? I suppose I was also swayed by the fact that my previous Note did have a software problem causing the same thing, so I figured this was probably software too. But nope, good to go after checking the mic hole!
Click to expand...
Click to collapse
Not gonna lie, I checked my mic hole as soon as I read this. XD
I tend to always put my pinky finger over that mic subconsciously. I don't mean to, but it's just how my hands want to hold the phone during a call. I constantly get people saying that they can't hear me though. Then I always notice that my stupid pinky is on the darn mic. Grrrrrr.
Sent from my SAMSUNG-SM-N910A using Tapatalk