Related
Hello, i need some serious help over here
What's the problem:
I own a galaxy 3 since June, a week ago i started noticing the internal mic wasn't working on some incoming calls.
Details:
First of all the problem began for no apparent reason (the phone works fine otherwise and no major updates / new apps were installed)
This started happening on the official froyo ROM which was an excuse for me to flash the Kyrillos 9.4 ROM (wiped all data / formatted sd card in the process). The problem still occurs on Kyrillos 9.4 ROM suggesting that this is not a ROM issue
I thought it was a hardware issue but the caller can hear me perfectly if i connect the headset or use the speaker Also the internal mic works fine on some incoming calls and ALL outgoing ones!
Upon further investigation i came upon 2 threads on other forums (unfortunately i can't post the urls as i am a new user, if needed pm me or search google for "Microphone not working on incoming calls") which point out that the same problem incurs on HTCs and XPERIAs. Also it happens on replacement phones (original unit shipped back after this problem), on different providers, on official and custom ROMs, on clean phones (only the stock apps installed).
This seems to happen when the phone is idle for a set period of time (unconfirmed). Fast Reboot app / manual reboot / removing battery don't fix this, however making an outgoing call seems to enable the internal mic temporarily (even if the outgoing call never connects)
When this happens apart from the mic not working on incoming calls it becomes also unresponsive for other apps (Tape-a-Talk, Skype, Soundhound etc.)
Conclusion:
It seems to me that there is bug in froyo that keeps the incoming call code from activating the microphone or perhaps there is a conflict of sorts that keeps the microphone blocked. It is highly unprobable i think that the microphone would randomly start to fail on different android phones in the exact same way, so this shouldn't be a hardware issue.
Question:
Does anyone know/guess or can produce a possible solution for this? If not, could you please suggest further testing steps to help reproduce 100% this problem in an attempt to solve it?
Any help would be greatly appreciated as this is a pain in the neck for me (and others i guess?!)
PS: Excuse the thread form, i 'm really bored of writing / reading long posts
PS 2: This is my first post, hello xda community!
samsung vibrant
I have the same problem. I flashed the phone from android 2.1 TO cyanogen 2.3 and from it TO ice cream. I had this problem even to cyanogen and only in incoming call,never in other situation.
Googling I found same information but no solution. Anyone here knows something?
Anyway I found a stupid solution....try switching to 2g( I know that it's not a solution but...). It works for me!
that's ridiculous! how can network state have anything to do with the microphone of the device? can this be related to service providers maybe a more techish member could tell us.
anyway i am on 2g already as i don't have a usim card and this happens even if data network mode is deactivated. glad you found a way out but is it really a solution? i mean you have to ditch 3g for the phone to be actually a phone...
Since we seem to be the only ones among so many to be having this problem i am seriously thinking of taking back the phone for a replacement and hope for the best...
just an update, i lost functionallity of the microphone completely earlier today. That is with outgoing / incoming calls and any app i can think of, so i thought i 'd try changing the network data setting to 3g only since i was already on 2g...
WOW!!! that had an instant effect,it works seamlessly now,didn't even have to reboot.fingers crossed it will last.
that is one nasty and very strange bug. Please any of the developers could you take a closer look at this?
much appreciated
Sent from my GT-I5800 using XDA App
Hello,
Did Samsung ever fix the low level volume fluctuation problem through the headphone connection on the 7.0+? Listening to lower level music files at lower volumes resulted in the volume jumping up and down slightly. The problem occurs regardless of whatever music player app is used. The files play fine on the Samsung Galaxy 5.0 player and other devices.
Thanks!
Update: It's not fixed.
This thread is the only reference I could find to this issue anywhere. Is it documented more fully somewhere else? Is Samsung aware of it and planning to fix it? Any references or other help would be greatly appreciated.
I've had my 7.0 Plus for about a week, and yesterday was the first time I tried listening to some classical music favorites featuring very soft choral passages. I couldn't. The volume surges every couple of seconds during soft passages. It sounds as if some demented engineer thought it would be a good idea to add an automatic volume equalizer to make sure the music never gets too soft. No. Very bad idea.
Until I found this thread, I thought I had a defective device or was losing my hearing. I'm glad that neither is the case. Again, please post links to further info about the issue. TIA.
Sun_Cat said:
Until I found this thread, I thought I had a defective device or was losing my hearing. I'm glad that neither is the case. Again, please post links to further info about the issue. TIA.
Click to expand...
Click to collapse
I've had the same problem with 6210 from day one. Other than album art being screwed up, it's the only real annoying problem I've had with the box.
The problem may be in the default player. I use poweramp and don't experience that
Sent from my DROID BIONIC using XDA
It's not just the default player. I've experienced it in the Rhapsody app too. Also see the OP, which says regardless of app and also strongly imples that the issue has been discussed before.
Sun_Cat said:
It's not just the default player. I've experienced it in the Rhapsody app too. Also see the OP, which says regardless of app and also strongly imples that the issue has been discussed before.
Click to expand...
Click to collapse
I hear it using TuneIn Radio. Hoping for a fix with ICS.
UPDATE
I've found two earlier references to the issue:
A review on Amazon from last November (reviewer says he's notified Samsung)
A post by this thread's OP, also from November (like me, he thought it sounded like Automatic Gain Control; unlike me, he remembered the right name for that feature )
Again, any more references, especially from Samsung, would be appreciated.
ETA: I found one on the Samsung support page (search for the string "How can I stop the volume" and click on the text to open the answer). It was answered, not by Samsung but by an anonymous user, who said "Sorry charlie, but you've got a headphone jack with a malfunctioning sensor. Sorry!"
I suppose that's a plausible explanation, but against it is the Amazon reviewer, who said he had the same problem with two different units. And then there's me and the OP here.
redsmear said:
The problem may be in the default player. I use poweramp and don't experience that
Click to expand...
Click to collapse
I installed Poweramp. Nice app, but it doesn't help with this problem at all.
To hear the problem you have to be playing music with sustained passages that are very soft. With most pop, rock, and jazz it won't be noticeable. That's probably why the issue isn't more widely reported.
Try this video in your YouTube app. If your Tab Plus is behaving like mine, you'll hear several volume surges during the first 20 seconds or so. ETA: Crap! I can't post outside links. Here's the last part of the YouTube URL, after the slash: watch?v=6-i1ESIRKdA.
One more clue
And I found one more indirect clue in the Samsung Troubleshooting Guide under the heading GT-P6210 Volume Drops When Headphones Are Plugged In:
The volume on your Tablet will drop 75% when you plug in your headphones. This is a preventive measure for acoustic shock to your ears. The volume can be increased after the headphones are connected.
Click to expand...
Click to collapse
Obviously this proves nothing about the issue we're discussing, but it is suggestive because it tells us that something in the firmware is deliberately designed to mess with the headphone volume.
Aha, so it's not just me who noticed this "feature" then
For anyone who is experiencing this issue and wants to let Samsung know about it in one place, I've started a public thread on their Facebook support wall. You'll have to imagine the first part of the usual Facebook URL since I can't post links. Here's the last part, after the slash: samsungsupport/posts/10150588609036213
Nothing from Samsung Support on Facebook since yesterday morning. One other person has posted there (thanks, Mark, if you're reading this). It would be nice if a few others would chime in.
I'll chime back in. I'm glad somebody else has finally noticed! The problem also exists with the Verizon SCH-i810 (Tab 7.7) but, perhaps, to a lesser degree.
I strongly suspect the (Yamaha?) driver and/or its configuration -- see the original post from November that shows the (configuration?) files. I suspect that file may hold the key to the problem. Problem is, I have no idea what the numbers actually mean and didn't find any documentation for those numbers (data sheets, etc.). I did attempt at the time to tweak a few numbers using my "best guess" by comparing the entries for rx-speaker vs. rx-headphone vs. rx-headset. but no discernible effect was heard.
No prizes for guessing who was raising such a fuss in November.
The "Sorry Charlie" answer is incorrect and I flagged it as such.
UPDATE: I found the 7.0+ /etc/audio files and I have the 7.7 /etc/audio files. There are some differences in the numbers and the 7.7 audio files (LVVEFS) have some comments (!!!) in them so maybe I can track down pertinent parameters.
Anyone else have an opinion or another idea? Is this a waste of time?
Thanks again to everyone who posted here. If you've been watching the Samsung wall on Facebook where I posted last week you've noticed that they haven't responded at all except to ask one simple question, which I answered immediately. Since then, crickets.
If you're experiencing this issue and you feel comfortable saying so in public, please add your comment to the post on Facebook. Maybe we can guilt them into responding.
Thanks.
Sun_Cat said:
Thanks again to everyone who posted here. If you've been watching the Samsung wall on Facebook where I posted last week you've noticed that they haven't responded at all except to ask one simple question, which I answered immediately. Since then, crickets.
If you're experiencing this issue and you feel comfortable saying so in public, please add your comment to the post on Facebook. Maybe we can guilt them into responding.
Thanks.
Click to expand...
Click to collapse
They just answered about 1/2 an hour ago. They provide a link and ask us to go to the Samsung Service Facebook page and fill out a support form. Might as well. Keep the pressure up on someone over there.
Agreed. I just submitted their form with full details. We'll see whether they follow through.
A hint to anyone posting there: Samsung appears to be great at stalling by asking follow-up questions. Include as many pertinent details as possible in the initial post, such as model, wi-fi or data-enabled, serial number, firmware, streaming or stored music sources, which apps, etc., etc., and so forth.
Well, at least they're responding, but I'm not sure it's helping. This morning they replied to my original Facebook post:
We can suggest checking to see if the same problem occurs in a different set of headphones or speakers. If the problem persists we will suggest servicing your Tab.
Click to expand...
Click to collapse
I've already checked with different headphones (not speakers; I've already told them several times that it's a headphones-only issue!), so I already know that the problem isn't due to one set of headphones.
This gives me zero confidence that they actually understand the issue. (Except that it's possible -- though in my view unlikely -- that it is a defective headphone jack.) I'm reluctant to send it in for service. The problem is subtle enough that someone lacking a trained musician's ear is likely to just say it's fixed and send it back. We already know that the fellow who mentioned this issue in his Amazon review got a second unit exhibiting the same defect.
Also, I have not heard from Samsung directly in response to submitting the official support form the other day, so I can't now tell whether or not this latest comment on the wall is coordinated with that other support request.
Does anyone have any advice? Has anyone here dealt successfully with Samsung support in the past, on any issue at all? How did you do it?
Sun_Cat said:
...This gives me zero confidence that they actually understand the issue. (Except that it's possible -- though in my view unlikely -- that it is a defective headphone jack.)
Click to expand...
Click to collapse
I agree. I don't believe it's a headphone jack issue either. I'm going to wait until ICS comes out and then decide what to do if it's still an issue.
I've tried adjusting some numbers in the .txt files -- no change yet. Maybe I'm adjusting the wrong file. Who knows?
I'm surprised there aren't more complaints. It's easy to identify. Headphones, earphones -- doesn't matter. The problem exists with Samsung's earphones. They can't run away from that one. Doesn't the 7.0+ come with four audio files? I can't recall if the problem could be reproduced with those files, because the problem needs periods of relative silence to get into the "AGC" mode. I think the Samsung support is in typical "denial mode". Problem? What problem? Let's go through all the permutations of user error or workaround before considering that there is a problem. It's a matter of problem ownership -- and Samsung isn't owning it.
The questions I would ask are: "Have you tried reproducing the problem?" "Do you know how to reproduce the problem?" "Who has the capability to reproduce the problem, if you can't".
Yes! Just found the Samsung music files, going to try to reproduce with all Samsung supplied software and equipment.
UPDATE: Reproduced the problem on Galaxy Tab 7.7 with all Samsung supplied files/software/equipment:
MATERIAL:
1. Samsung supplied "Music Player", no EQ
2. Samsung supplied music file "Silky whisper.mp3"
3. Samsung supplied earphones, white with button and mic (I think it's pretty generic to Samsung)
Steps:
1. Start Music Player.
2. Make certain volume is all the way down and the sound is muted (slash through speaker)
3. Press the volume up button once, twice (once to unmute and one step higher)
4. Play music file. Note how the piano cuts in and out throughout the song, especially during the opening of the instrumental.
I suspect that Samsung is going to hand this issue off to Yamaha. The constant in this matter is the Yamaha-sourced audio chip/driver/library/configuration/firmware.
Here are some files to compare from /etc/audio (I added the model to the name):
TonyBigs said:
It's a matter of problem ownership -- and Samsung isn't owning it.
Click to expand...
Click to collapse
Agreed. That's why my first question to them on Facebook was "Are you aware of the problem?" No way will I send my GT7+ to them for service until they take that step.
I'll try your steps later today and see if I get the same result. Maybe we can gang up on them.
I have one additional datum since last week. I've tried to reproduce it on Bluetooth headphones, and the problem does not show up. It's only there with plugged-in headphones.
I suppose this could be interpreted as evidence slightly inclining toward the "defective headphone jack" theory. But I still don't think so. If anything, I think it could be related to the Self Aware Volume Ghost on the Galaxy Nexus, which Samsung apparently did acknowledge. Except the Nexus bug was much more obvious since the volume control indicator actually appeared on the screen and changed.
Please help with the "hello hello bug" (2-3 secs delay when answering a call)
There are lots of old threads about this, but I can't believe this is still an issue. You know the same old problem - When I answer a call the first 2-3 seconds the other side does not hear me, then everything is fine. It is called the "hello hello" bug or "Call Delay" bug, The oldest posts I see that explain the same issue are from 2011. Now 3 years later this is still NOT fixed. Come on Google get your **** together seriously...
It seems that every android phone that I've owned had this problem. This is my 2nd nexus 5 (the first had memory problems) and I still experience the same bug.
Anyway is there a known fix for this? Does anyone had this problem and fixed it somehow? I've read that there was some "Call Delay Patch" but I cannot find a working link for this, the app is no longer in the play store also.
I am experiencing the same issue since I bought the phone, even changing the rom to CM11 did not change the situation. Does anyone have an answer to this problem?
no issues here, im using lichtis rastakat build with trinity kernel.
bump bump.. Is no one else experiencing this issue? Saying hello 2 times after answering is a bit annoying .
I've experienced this issue as well, but I've only noticed it when I'm communicating with an iphone user. It never happens when i call or receive a call from someone on landlines or android phones.
I my case this happens with litteraly any type of phone. This is a really weird bug because it doesn't seem to be device specific, i had this happen to me on my old lg optimus black, but then installing a different rom, fixed the bug, now this happens on all the roms i've installed.
Could it be baseband specific?
Hello
Since the second day since getting the smartphone have a problem with my voice / sound in telephone calls on the first day people said that my sound was very good, from the second day no one can understand what I say, I experienced the recorder voice and the sound seemed ok, so I think it can be any application that did this, an error "code" and no physical damage. I contacted the alcatel, she suggested going to the store and switch to another or send for repair since it is under warranty, but I go on holiday soon and do not want to go without the smartphone and change on the other also does not look good as lost data, who find something idea like trying to solve this? Sorry for my English, I am Portuguese, thank you
Similar problem here
Hi (greetings from Portugal too).
I'm experiencing similar problems with the mic on my new Idol 3.
At first all seemed ok, but now in every call I make people complain that they hear me very low and like I'm "inside a well".
I'm trying to assert if it has anything to do with to primary or the secondary mics, and for now I've been answering calls on the "upright position"... Next time I'll try the inverted one.
Will be on the lookout for new updates too...
IDOL 3 Mic problem
Hello,
it happens to me as well since day one. I figured out, that in my case, it has following scenario:
Sometimes SIM card disconnect and connect back (perhaps loose contact, it is little bit smaller than the frame, the sim card)
It asks for PIN
After all calls my voice to others is very low and well-like
Reset the Phone
It is OK until the SIM thing happens again
I fixed better the frame to SIM, it is ok, but generally, the voice and noise cancelation, is not the best at this phone (main feature), which on the other hand very good for the price...
Daniel.
Hi !
Got the same Problem with ALCATEL 6044D Android Version 5..1.1
Hi Guys,
well, the mic issue is not really an unknown to OPO users - I have never experienced such issue, but some time ago my mom let me know she has problems with mic for long time now (she has inherited my OPO), so there I went - looking for an intel regarding this issue.
I have come across some standard fixes for Cyanogen (the last official one by OPO themselves):
- blow out dust/debris from the microphones (done with a vacuum cleaner),
- remove TrueCaller, voice recorder, turn off "Ok google" recogniton (basically not a problem for us, we have Slovak language, thus no support anyway),
- tried other services - like Viber and it worked perfectly!
- tried speaker mode - worked!
So after this I came into the conclusion maybe a drop or something has damaged or something the rear mic for ambient noise suppression (maybe?).
But then I found some info the CnM is the problem itself, so I have just switched to the LineageOS (it is not really a change when I am thinking about it now, well is it?), but this has not helped, still the same problem.
I have found this too and applied too, but, again, no success.
Do you happen to have any other suggestion? How is it possible Viber works? Can be some app such as Viber used as the phone app too?
Thank you, in an advance...and I hope we will come to some conclusions here, I am wasted from all of this...
dropadred said:
Hi Guys,
well, the mic issue is not really an unknown to OPO users - I have never experienced such issue, but some time ago my mom let me know she has problems with mic for long time now (she has inherited my OPO), so there I went - looking for an intel regarding this issue.
I have come across some standard fixes for Cyanogen (the last official one by OPO themselves):
- blow out dust/debris from the microphones (done with a vacuum cleaner),
- remove TrueCaller, voice recorder, turn off "Ok google" recogniton (basically not a problem for us, we have Slovak language, thus no support anyway),
- tried other services - like Viber and it worked perfectly!
- tried speaker mode - worked!
So after this I came into the conclusion maybe a drop or something has damaged or something the rear mic for ambient noise suppression (maybe?).
But then I found some info the CnM is the problem itself, so I have just switched to the LineageOS (it is not really a change when I am thinking about it now, well is it?), but this has not helped, still the same problem.
I have found this too and applied too, but, again, no success.
Do you happen to have any other suggestion? How is it possible Viber works? Can be some app such as Viber used as the phone app too?
Thank you, in an advance...and I hope we will come to some conclusions here, I am wasted from all of this...
Click to expand...
Click to collapse
Just a little search,and look what I found!
https://forum.xda-developers.com/showpost.php?p=74316182&postcount=2267
Oh, I thought I will get around it without a root, thus why I did not try any of the "must be rooted" approaches. But yes, it is fixed now, however...
This is a very unwanted outcome - the phone has been used for recording band's sessions as well where the mic array was used fully, but now calls, yes, are ok, but the recording quality is horrid - basically it was recording like when you switch a call to the speaker mode, where other microphones were recording too and giving that full-bodied sound, now it is like through a gaming headset with a noise cancellation.
What is this issue caused by, anyway? Is it because of a damage of one of the microphones?
Anyone? The rear mic was really handy for the music recording (full sounding). Is it possible to make it somehow toggleable?