The last half year have riddled various forums with the now infamous Samsung HW/SW bug that is most often causing an extremely unpleasant echo in the other end of a conversation. However, this bug appears in many variants due to the multiple causes of many interacting smaller problems.
In my own quest of finding the root of the problem and scanning the web for a potential solution (not involving send my phone off), I decided to share my findings, very well aware of the shortcomings of my limited research. So please let me know of any current (or future) solution to this, or if I have missed anything important.
Internally there are 2 microphones and 2 speakers. Unfortunately the way these are situated, aligned and and isolated, together with the sound transmission throughout the phone chassis and the complicated sound and digital noise reduction (NR) settings, are the cause of these problems.
All this can best be seen in the iFixit's teardown guide:
http://www.ifixit.com/Teardown/Samsung-Galaxy-S-II-Teardown/5861/1
or in the "S2 screen replacement photo tutorial":
http://forum.xda-developers.com/showthread.php?t=1253969
or in the schematic blow-apart diagram in the official "Samsung-GT-i9100-service-manual". (Google that!)
My Conclusion:
After performing a limited number of tests, on my own, I have concluded that this problem should in ANY case be resolvable by a fix in the phone firmware/software. Obviously the phone is working without a case, and (usually) perfectly when turning off NR (noise reduction) and/or turning down the volume. Others report fiddling with the internal rubber enclosure of the microphones and/or speakers. In either case, it would be very interesting to know the details of your phone's SW and HW configuration as many reports differences in behavior after flashing new/old phone software. It is very likely the problem occurs as a combination of "PHONE/PDA" software, the lower USB charge-port HW and the upper speaker/microphone insulation. In other words the NR algorithm need to be changed or better tuned for various environments. We can only hope Samsung fixes this in their next updates... But very unlikely as they are much more interested in making new phones and selling more of them. And if they did fix it, they probably wouldn't tell anyone since if they ever did admit to any wrong doing, they'd have to replace/repair probably at least tens of thousands of phones!
Problem (Simple Description):
A number of small assembly line variations is causing the internal noise reduction software to misbehave. (Remember the "butterfly effect"!)
Problem (Technical Description):
The problem consists of (at least) 3 smaller problems working together.
1. The lower playback speaker is always on (!) and is causing feedback to the lower microphone when using a protective cover. Thus explaining the greater echo at higher volumes and less external noise, when using a rubber cover.
2. The SGS2 plastic casing transmits sound around the entire phone. Thus both speakers (lower and upper) are transmitting sound to both the lower normal microphone and the upper noise cancelling microphone. These need to be isolated.
So when covering the upper noise reduction microphone you are getting better feedback (more "noise") from both upper AND lower speakers, than from outside and thus (usually) improving call quality by reducing the echo effect, but when there is no case-cover and a noisy environment, you may end up increasing the echo, by covering it up!
3. BUT not all phones have echo, thus there is also a NR settings or algorithm problem that should or may be resolved by a firmware/phone/PDA update. In addition, and making things even more complicated, different phones have slightly different hardware on the PCB of the USB charge-port...
Who to Blame?
1. Samsung Hardware engineers who must have been sleeping in their "Acoustics and Wave Propagation" classes.
2. Samsung (?) Software engineers who never took a course in "Feedback and Control Theory".
3. Samsung HW design director(s) who
a) didn't make (1) and (2) work closely enough together on the SGS-2.
b) never though of putting a rubber case on the phone! 4. Samsung Assembly line Quality Control manager(s) who didn't check for minor design flaws.
- check (open up) every 100 or so phones, if problem check ALL previous 100 and estimate problem!
- stop assembly line and talk to the management about solution ..
..
oo. The casual SGS2 owner who just wanted to protect his new investment with a rubber/plastic cover.
Some Known Solutions:
Service Center Solutions:
1. Improperly placed internal speaker cushion:
http://androidforums.com/samsung-ga...ice-echo-anyone-else-getting.html#post3000051
2. Replace the UI Board; Part No: GH59-10949A
http://androidforums.com/samsung-ga...ice-echo-anyone-else-getting.html#post3269199
http://www.scribd.com/doc/56542824/5/Cellular-phone-Exploded-View
http://giga-tel.com/item-10095-samsung-i9100-ui-board.html
3. Attach layers of soft electrically and noise insulating tape (e.g. medical-tape) over the back-side of the upper speaker, earphone jack and microphone. On the inside of you phone. See instructions in Hebrew (!) below:
http://iandroid.co.il/forum/topic56552.html
DIY Home Fixes (various success):
4. Put some tape over the top NR hole, which is next to the 3.5mm head-phone jack. (This fix messes up the speakerphone functionality!)
5. Put some tape over the hole just above volume-rocker
6. Lower volume
7. Manually disable NR during call: ("HOME" button)
8. Factory Reset (This will wipe your data/contacts and probably only lasts until next reboot!)
9. Try to flash a different phone ROM/Firmware/Kernel/Baseband etc. (Seem like it's mostly Gingerbread 2.3.4 phones being affected.)
10. Perhaps by changing some settings in the hidden "Service Mode" menus (???)
11. Open your phone and
a) make the bottom small microphone hole in the case bigger and
b) cut some of the rubber from the lower microphone cover.
See: "Fix for low microphone volume":
http://forum.xda-developers.com/showthread.php?t=1127103
http://forum.xda-developers.com/showpost.php?p=20022525&postcount=10312. Attempt the above Service Center operations by yourself!
NOTE: It's highly recommended to do only ONE AT THE TIME!
Currently Recommended Solution:
A) WITH stock phone/firmware AND warranty; ask for a new phone and test it!
B) WITHOUT stock phone/firmware OR WITHOUT warranty; Try 11b!
List of Firmwares WITHOUT echo: (PDA/Phone/CSC)
"Polish Stock ROM"
"Many Indian firmwares don't have DNR (KE8 or KF3) activated"
I9100XWKE7 (2.3.3)
KI4/KI1/KH2 (XEU) Echo with DNR OFF (default) NO ech with DNR ON!
KD6/KE7/KD1 (XEU) 'same'
[ If you have/find other firmware solutions, please add them to this thread! ]
Service Mode Settings
Entering Service Mode: *#197328640# OR *#*#197328640#*#* [dial]
See: http://forum.xda-developers.com/showpost.php?p=14692752&postcount=30
These settings are probably ending up in the various audio setting files in: /system/etc/audio (which are only accessible in a rooted phone.)
Potential (Rooted) System Hacks
Tweak/check the files present in: /system/etc/audio
OR perhaps write some Tasker script; see:
http://forum.xda-developers.com/showpost.php?p=19339706&postcount=125
Some custom ROMs come with NR tweaks that allow you to permanently turn ON/OFF DNR:
VillainROM (VRTweaks)
DarkyROM
Revolution 2.7.1
[Could someone confirm & provide a links to these?]
Apparently there are other ways in which you can directly hack the Phone.apk package, under certain conditions. Thus at least in theory it should be possible to directly toggle NR in memory, which could indeed be useful. Here is one variation of the APK hack:
In the Phone.apk package, find the ../res/values/bools.xml file. Edit and recompile after changing the line: "<bool name="has_in_call_noise_suppression">true</bool>".
See: "[HOWTO] disable NoiseSuppression by default, to enlarge mic volume":
http://forum.xda-developers.com/showthread.php?t=1251922&highlight=volume
and start reading from this post:
http://forum.xda-developers.com/showpost.php?p=18932990&postcount=107
Some additional info for hacking Phone.apk:
http://forum.xda-developers.com/showthread.php?t=1332137&page=3
Do you have a contribution or solution?
So if you want to contribute to the solution and permanent fix of this (or any other comments), please post the following info, as well.
1. Baseband (aka. "Phone") version
2. Kernel version
3. Build number
4. The USB-charge-port PCB version (if known)
5. Your particulars when it works and when it doesn't
6. Details on how you fixed the problem, if you did!
To find info use these codes on the dial pad:
Firmware Version: *#1234#
Hardware Version: *#2222#
Both Versions: *#8999*8376263#
That way we may hope to find and fix the problem ourselves!
Some of this I already mentioned here:
http://forum.xda-developers.com/showpost.php?p=20142257&postcount=99
http://forum.xda-developers.com/showpost.php?p=20143129&postcount=28
http://androidforums.com/samsung-galaxy-s2-international/357910-voice-echo-anyone-else-getting.html
Also try to search the "Samsung Galaxy S2 Q&A" forum for "Echo Noise Reduction".
http://forum.xda-developers.com/search.php?searchid=104855328&pp=25
Thanks and I hope this helps!
...
UPDATE: 2012-01-30
Apparently there have been many reports of very happy people doing their own SGS2 surgery following the thread:
http://forum.xda-developers.com/showthread.php?t=1441510
This is essentially equivalent to the solution in number #3 above!
+1 for the effort, about time someone did an all-in-one topic about this rather common issue.
I've had the same problem and noticed it the day I bought my phone, a friend called and immediately complained about the echo. I did a quick Google search and found out that it's a rather common problem and caused by most case types, removing the case or disabling NR did indeed fix my problem.
Anyway, I have tried many fixes, including VillianTweaks/LeoMar's fix, turns out those only remove the ability to turn NR on/off, but it was still turned on by default. This fix however was the only one that actually worked:
http://forum.xda-developers.com/showthread.php?t=1332137
The fix above had a minor drawback though, the first call after reboot always had NR enabled by default. I wanted a set and forget solution to permanently disable NR so I learned a bit about deodexing/decompiling and managed to get rid of it for good, you can check the fix in here:
http://forum.xda-developers.com/showthread.php?t=1372718
Wow
E:V:A said:
After performing a limited number of tests, on my own, I have concluded that this problem should in ANY case be resolvable by a fix in the phone firmware/software. Obviously the phone is working without a case, and (usually) perfectly when turning off NR (noise reduction) and/or turning down the volume.
Click to expand...
Click to collapse
I'd disagree. I heard a slight echo also without the case (I called from a land phone to hear it myself). Lots of SGS2s work fine with cases, with NR on. Killing NR should not be considered the solution.
I've opened the phone and inserted two thin layers of white medical tape over the ear speaker (much less tape than in that hebrew sample). The original echo gone completely, with and without case. But now the other party hears a very slight echo of me. I don't consider tape a solution either. Perhaps the speaker is not mounted properly (sticks out too much)?
I was wondering about the position of the cushion, don't understand what that guy meant precisely. Mine looked a bit squashed by the case, maybe too firm contact?
> 1. The lower playback speaker is always on (!)
Are you sure? It could be transmission via the case? I guess the add-on cases increase the transmission.
> 3. BUT not all phones have echo, thus there is also a NR settings or algorithm problem that should or may be resolved by a firmware/phone/PDA update.
I'm not sure the NR algorithm can be fixed so that it can work with a faulty phone.
> Service Center Solutions:
Add 4. Replace old SIM card
I'm using stock 2.3.4 I9100XXKI1
2.6.35.7-I9100XWKI4-CL575468
[email protected] #2
FTA HW REV1.5
Baseband: KI4
ROM: MIUI 1.12.2
Kernel: Siyah 2.4.2
Everybody I talked to used to tell me that my voice echoed pretty bad. Then I switched to the KI4 modem and the issue was resolved. Maybe someone with this echo problem could try the KI4 modem and report back.
Sent from my GT-I9100
@bazzag: Thanks for VillainTweaks info, I'll scratch that until further notice.
@_sem_: Essentially I agree that killing NR is not a proper solution, as it is just a remedy for a sickness, which would return in a very noisy environment when NR may be needed. But given that this will probably never get properly fixed, it seem to be the best option we have for now. ALSO:
a) In the 1st § you say you called your own phone and found echo, then in the 2nd § you said: "But now the other party hears a very slight echo of me." these seem the same to me, or did you mean that now you hear echo when using your mobile to call someone else?
b) > 1. The lower playback speaker is always on (!)
Actually I am not sure about this as I live in very noisy environment, but everyone standing next to me, during phone calls, say then can hear everything the other person is saying!
c) > Service Center Solutions: Add 4. Replace old SIM card
Now THIS is a shocker! Why on earth would upgrading the SIM card have anything to do with this? Where did you see and hear about this solution?
d) We have the exact same stock SW/HW!@iHoneyBadger: Yes! Could someone provide a link for (easy/noob) instructions on: (1) where to find/download the KI4 Baseband files and (2) how to easily install only Baseband?
@E:V:A
> Essentially I agree that killing NR is not a proper solution, as it is just a remedy for a sickness, which would return in a very noisy environment when NR may be needed. But given that this will probably never get properly fixed, it seem to be the best option we have for now.
I think the best option is the service center if you have stock ROM. You may need to convince them first, best by showing another SGS2 that works fine with your case. But that'd take much more time for me than inserting that tape did.
It really isn't difficult. Except that I'd feel a bit better knowing the exact problem better. It may be possible that the change was just due to taking the phone apart and back, not the due to the tape. I'm too lazy to do it five times trying this and that I'd ask the next one who tries this to check if the speaker can perhaps be pushed a fraction of a mm deeper into its seat, so that the speaker would have less or no contact with the (removed) back of the case. I think this could be better than tape.
> a) In the 1st § you say you called your own phone and found echo, then in the 2nd § you said: "But now the other party hears a very slight echo of me." these seem the same to me, or did you mean that now you hear echo when using your mobile to call someone else?
This echo is on the level of the previous echo without case - barely noticable if you're listening carefully, but no longer an issue really. And, those phones that do not have the problem don't have any tape inside
b) > 1. The lower playback speaker is always on (!)
> Actually I am not sure about this as I live in very noisy environment, but everyone standing next to me, during phone calls, say then can hear everything the other person is saying!
I think this could also be caused by the case conducting the sound. It must also be emitting some around. I've also read some folks got improvements by cutting ugly large holes in gel cases at the back - that'd probably decrease conduction.
> c) > Service Center Solutions: Add 4. Replace old SIM card
Now THIS is a shocker! Why on earth would upgrading the SIM card have anything to do with this? Where did you see and hear about this solution?
I think it was a german forum android-hilfe
/samsung-galaxy-s2-i9100-forum/144551-probleme-beim-anrufen-echo.html
/samsung-galaxy-s2-i9100-forum/174469-echo-problem-sgs2.html
@E:V:A
It's in the modem thread in the original development section.
Here's a link to the CWM flashable zip...
http://www.multiupload.com/0FTG1P9MK4
Edit: It's just the modem. Let us know if it helped.
Sent from my GT-i9100
Your modem did NOT work for me :-(
put k14 modem on my phone
so i just added the modem as of now doesnt seem to be any noticeable echos. I will use it for a day with a case and see what happens.
Just tried to install the zip on power up of the phone....it starts but I just get a signature verification failed error. The progress bar hangs and when I go back to the root menu in recovery the error message is present in red.
Am I doing something wrong?
I had also the echo problem and also the other person could not hear me well... After changing my modem firmware to BOKJ1. This is a custom made firmware for Greece Cosmote... My voice is now loud and clear.
But I have also made a change to the stock dialer at KK5 deodexed ROM (Omega v9) so that the phone starts with noise reduction off.. but you can enable it from the menu during call.
Please see my post..
http://forum.xda-developers.com/showthread.php?t=1388058
iHoneyBadger said:
It's in the modem thread in the original development section.
Here's a link to...
Edit: It's just the modem. Let us know if it helped.
Click to expand...
Click to collapse
Thanks! I will flash a complete new ROM (with a different Modem) in few days, when I get some more time off. I'll get back to you on the results.
talexop said:
...
After changing my modem firmware to BOKJ1. This is a custom made firmware for Greece Cosmote... My voice is now loud and clear.
But I have also made a change to the stock dialer at KK5 deodexed ROM (Omega v9)
...
Click to expand...
Click to collapse
Please see my response at:
http://forum.xda-developers.com/showpost.php?p=20306528&postcount=11
This does not seem like stock...
a) Where did your Phone.apk come from?
b) What did you do?
c) How does it compare (diff) to a real stock,lets say the 2.3.4 (XWKI4 / XXKI1)?
Could someone test this?
E:V:A said:
Please see my response at:
http://forum.xda-developers.com/showpost.php?p=20306528&postcount=11
This does not seem like stock...
a) Where did your Phone.apk come from?
b) What did you do?
c) How does it compare (diff) to a real stock,lets say the 2.3.4 (XWKI4 / XXKI1)?
Could someone test this?
Click to expand...
Click to collapse
Please see my responce. I hope I made it clear for you. I have tried a patch nobody else did and to tell you the truth I cannot uderstant why they did not! My patch is way to easy and leaves the user choise to reenable noise reduction.
Also all the other patches did not work for me. The one I made worka fine.
http://forum.xda-developers.com/showthread.php?p=20320415
Sent from my GT-I9100 using Tapatalk
I don't know for u guys but with last KK5 Roms my sound is terrible.
When i speak with people sounds as i call out of the box
Can't find f'in solution....
BuzzFuzz said:
I don't know for u guys but with last KK5 Roms my sound is terrible.
When i speak with people sounds as i call out of the box
Can't find f'in solution....
Click to expand...
Click to collapse
First of you should try to change your modem firmware... This did the best work for me. You should try the one you had before... If that one was ok... Also you can try my dialer which works for KK5..
Sent from my GT-I9100 using Tapatalk
Used my phone without my tough mate case and have worried about dropping my phone all day! Really wish i could sort this myself, why can i not install this modem zip?! Echo def gone without case no complaints at all. It doesn't feel right without a case! If someone could help me install this modem id be eternally grateful!
sent from t'internet
Dear all, i was testing the loud speaker (you know, speaking with speaker on) and unfortunately no one can hear me. When i disable it everything is ok. I made a hard reset, but nothing changed. Do you have any alternatives??
Thanx
Hmmmmphh....back to a service centre for my phone then! This is a fundamental flaw with the phone. Problem still occurs without a case if the top of the phone moves too close to my head!
Related
I just bought my wife a used Eris and it turns out that it has the silent bug. It is a non-rooted phone running 2.1. What would you try to fix it?
1) update the radio (if so, to what)?
2) update the ROM (if so, to what)?
Any other ideas?
Thanks in advance.
Whenever I had the silent bug, I would fix it by slamming my phone against the palm of my hand, it really works. At least for me.
Thanks. Any other ideas out there?
Anyone? Any information is appreciated.
depends on if its hardware or software... software just a reboot or supposedly upgrade will help but if your already running the july ota 2.1....
Eris has a usb-trackball-mic combo port that has a notorious 'bad ground' (other physical trackball-equipped htc devices with similar designed usb-mic ports have the same issue as well) i cant even use the mic or trackball down and left without having the usb plugged in and slightly pulled forward, and barely then will the mic work. also have an issue where incoming bluetooth calls(only way i can use my phone as a phone aside from a wired headset) are rerouted back to my phone immediately upon answer have this problem with numerous roms and headsets
symptoms of this 'bad ground' problem and eventual complete mic failure etc are:
do u have phantom cursor movement whenever you plug in your usb cable into your device? ie. green selector jumping or tracking around the screen even when your device is not handled in any way...(makes it impossible to use the device while its doing this as well as it selects what it wants..lol)
callers asking hello hello hello? then hanging up even when your trying your best to wiggle the usb port or smack your phones microphone on your palm....
attempting to repair this problem (as im on cricket and obviously have no verizon 'warranty' anyways) i followed a write up on here about how to change your trackball and replaced with a new one as well as tried to clean dirty trackball contacts.. my microphone worked ok for like 3 days then went back to broken had no effect on trackball
on the other hand when i have had the silent call bug back when the mic worked, i usually couldnt hear the other person and they could not hear me and usually a restart worked..
hope some of this jibberish helps...
I contacted HTC support about the silent bug and this is what I got in response...
"Thank you for contacting HTC Technical Support. I’ve had to do a bit of research concerning the “silent bug”. Based on what I’ve read, do you mean that the audio goes silent on some calls, where you can’t hear the other party and they can’t hear you? Is rebooting your phone the only way to recover from it?
I can definitely understand your frustration if this is going on. I mean, you basically can’t use your phone sometimes. The latest update for the Eris addresses this issue. Please go to MENU > SETTINGS > ABOUT PHONE > SOFTWARE, and check the software number. The new software is number 2.37.605.4"
Her software number was lower than that, so I rooted her phone and installed xtrsense 4.6.5. She had one issue this morning but she isn't sure if that was because her volume was all the way down or if it was really the problem.
I also downloaded the Sprint radio update ending in 27, because her radio version is stale as well. I found that in the hidden menus using ##778. I am a little bit reluctant to flash that as I can't verify the CD5 #.
I haven't noticed the jumping around cursor and her trackball works OK. So I guess we are in wait and see mode now while I try to figure out what the next fix would be.
Thanks for the responses so far.
Yep
Sent from my Eris using XDA Premium App
My eris just got hit with both the trackball and the mic problem the other day. At first a swift hit on my palm fixed it for a day. And now the mic doesn't work at all unless my charger is plugged in and pulled toward me as well.
I haven't found any easy, or viable option of replacing the entire charge-trackball-mic block.
I am experiencing a problem with the speakerphone. The buzzing noise that is known to happen on GSM devises when u r close to speakers, TV's, radios etc is happening when I turn on the speakerphone. Is this a known problem for GSM TP2 devices running android? Is there a fix or will I just have to deal with it till it gets worked out?
EDIT
I have done some testing and lots of reading. Its seems that the "GSM BUZZ" only happens on the 2G network. I will explain exactly what I am experiencing, when I am on the phone if I turn on the speakerphone the speaker starts buzzing, also if I am on the phone and recieve an alert/notification or press a button the same buzz comes through the speaker and to stop it I have to turn the speakerphone on then off. This is a real problem and it is happening on both GSM devices I have access to. I need people with GSM devices to do test so we can see if this is happening on all GSM devices. All I need is for u to make a call with 3G turned off or if u do not have 3G access simply turn the speakerphone on and report what happens. Also make a call and press a key, I belive that if keytones are enabled the buzz will happen and if not it will be buzz free. Somehow sounds are turning on the speaker while on the phone. Lets get this fixed!
You have a giant WinMo6.5 logo in your sig... Why don't you stick to WinMo?
Does it happen in WinMo? I don't have any speakerphone issues, but I'm on CDMA.
I asked for help not a smartass comment. stop being condescending towards people just cause u have a little knowledge. if all ur gonna do is talk down to others than y even post anything? u can go ahead and come back with another post trying to put me down but all it will do is make me laugh. please do not post unless u are willing to help me understand my problem. I know u think ur routine of accusing people off not reading before posting makes u feel like a man but to other u come of as a douche bag.
Now to answer ur question, CDMA devices so not genrerate the buzz through TVs and speakers that GSM devices do. My question was asking y the known buzz comes through the speakerphone. its almost like android thinks the speaketphone is part of another device.
now ur other question, I don't stick to WM for the same reason everyone else doesn't, my device allows me to do things like boot android and Ubuntu so I have the freedom to choose my OS.
porkenhimer said:
I asked for help not a smartass comment. stop being condescending towards people just cause u have a little knowledge. if all ur gonna do is talk down to others than y even post anything? u can go ahead and come back with another post trying to put me down but all it will do is make me laugh. please do not post unless u are willing to help me understand my problem. I know u think ur routine of accusing people off not reading before posting makes u feel like a man but to other u come of as a douche bag.
Now to answer ur question, CDMA devices so not genrerate the buzz through TVs and speakers that GSM devices do. My question was asking y the known buzz comes through the speakerphone. its almost like android thinks the speaketphone is part of another device.
now ur other question, I don't stick to WM for the same reason everyone else doesn't, my device allows me to do things like boot android and Ubuntu so I have the freedom to choose my OS.
Click to expand...
Click to collapse
You obviously do not what you're talking about.
Plus, I asked a simple question and you failed to answer it in your long drawn out whining post. Meh.
FYI, CDMA devices produce a similar noise in other devices, not sure why you think that's isolated to GSM. iDEN does the same thing - perhaps the frequency is different, never really looked into it.
Your sig just makes me think you prefer WinMo, and kinda makes me giggle as it is comically large.
Well, I've got a bit of the same problem. But it only occurs when I'm either ending the call or when i have to touch the touchscreen during the call. Then it just goes haywire and give the bzzzz noise..
Running Froyo Red..
arrrghhh said:
You obviously do not what you're talking about.
Plus, I asked a simple question and you failed to answer it in your long drawn out whining post. Meh.
FYI, CDMA devices produce a similar noise in other devices, not sure why you think that's isolated to GSM. iDEN does the same thing - perhaps the frequency is different, never really looked into it.
Your sig just makes me think you prefer WinMo, and kinda makes me giggle as it is comically large.
Click to expand...
Click to collapse
i do know what i am talkin about. its called "THE GSM BUZZ" cause it happens on gsm devices.
i am so sorry i did not get ur approval before postin my sig. u remind me of one of those kids that feel bad about ther self so they try to insult other to make themselves feel better. u picked the wrong one. i ain't puttin up with ur ****. u may get a pass from other cause u helped a few people but u r constantly being rude to anyone that ask a simple question. ur way is not always right.
i asked for help not for comments on my sig or to be told to stick with a certain OS. this is America and i can like two things at once. yes i love WM but if i wanna use android on my device i will and do not need u to make up my mind for me. if u wanna help me get to the bottom of this buzzing noise fix this problem then cool but i do not need ur condecending remarks.
arrrghhh said:
You obviously do not what you're talking about.
Plus, I asked a simple question and you failed to answer it in your long drawn out whining post. Meh.
FYI, CDMA devices produce a similar noise in other devices, not sure why you think that's isolated to GSM. iDEN does the same thing - perhaps the frequency is different, never really looked into it.
Your sig just makes me think you prefer WinMo, and kinda makes me giggle as it is comically large.
Click to expand...
Click to collapse
Actually, I'd be shocked if a CDMA device actually caused the "GSM buzz" in other devices - Interference maybe, but not the distinctive buzz. It's due to differences in the channel access schemes between CDMA (To be specific, ANY form of CDMA, whether it is Qualcomm CDMA2000 or UMTS) and GSM (iDEN is similar to GSM)
CDMA systems a channel access scheme that has all devices transmitting continuously when active, but using special coding so that the receiver at the cell tower is able to "pick out" the individual handset signals. Since the device is transmitting continuously, the RF power envelope is fairly constant.
2G GSM/EDGE (not UMTS), iDEN, and the long obsolete D-AMPS use a different channel access scheme, time division multiple access. Each handset is assigned a time slot (or slots for EDGE) to transmit in. On a given channel, a set of slots is contained within a frame. Each time a phone's assigned spot in a frame comes up, it transmits. The end result is that the RF envelope pulses on for a short period every frame. Many other devices will rectify and filter the RF (unintentionally) resulting in a signal that follows the RF envelope - a low duty cycle square wave with a frequency equal to the frame repetition rate.
I have no clue why a device would cause such interference to itself in only one OS. It's not an issue anyone else has encountered to my knowledge. Original poster has a pretty poor attitude and atrocious grammar that is difficult to read. (People who can't be bothered to type out the word "you" really bother me for some reason...)
Entropy512 said:
Actually, I'd be shocked if a CDMA device actually caused the "GSM buzz" in other devices - Interference maybe, but not the distinctive buzz. It's due to differences in the channel access schemes between CDMA (To be specific, ANY form of CDMA, whether it is Qualcomm CDMA2000 or UMTS) and GSM (iDEN is similar to GSM)
CDMA systems a channel access scheme that has all devices transmitting continuously when active, but using special coding so that the receiver at the cell tower is able to "pick out" the individual handset signals. Since the device is transmitting continuously, the RF power envelope is fairly constant.
2G GSM/EDGE (not UMTS), iDEN, and the long obsolete D-AMPS use a different channel access scheme, time division multiple access. Each handset is assigned a time slot (or slots for EDGE) to transmit in. On a given channel, a set of slots is contained within a frame. Each time a phone's assigned spot in a frame comes up, it transmits. The end result is that the RF envelope pulses on for a short period every frame. Many other devices will rectify and filter the RF (unintentionally) resulting in a signal that follows the RF envelope - a low duty cycle square wave with a frequency equal to the frame repetition rate.
I have no clue why a device would cause such interference to itself in only one OS. It's not an issue anyone else has encountered to my knowledge. Original poster has a pretty poor attitude and atrocious grammar that is difficult to read. (People who can't be bothered to type out the word "you" really bother me for some reason...)
Click to expand...
Click to collapse
but its not just my device. my friend also has a tilt 2 and she lives in another part of the state and her speakerphone makes the same buzing noise on android. its kinda weird cause i have not seen other people askin about this problem. its just a buzzing noise that makes u not wanna use the speakerphone. also it happens if there is alerts while using the phone and then the only way to stop it is to turn the speakerphone on then off. it has to be affecting others too. it could not just be happening on two devices.
I see exactly the same thing on my rhod100 (de).
I also have another problem which existed for a long time: On some occasions, after booting to android, audio is completely gone. I test it by placing a call and checking if there is any in-call audio. Plus, on such an occasion, media files also do not make any sound, and rebooting the phone is the only solution. Enabling speakerphone does not help, even if I hear the mentioned buzzing sound.
I remember seeing something about audmgr_enable and that the arm9 did not respond to an rpc in the logs. I can post them if that happens again.
I think there are a fair number of known issues with the speakerphone.
I haven't bothered to try it myself, the only speakerphones I have ever used with acceptable audio quality are Polycoms.
edited first post.
well... i have the same problem and i've tried all the android variants out there...
finally someone else that has this problem. it is a big problem for me cause it makes the speakerphone unusable. I wish someone with some knowledge would recognize this is a real problem and try to fix it. I think somehow android thinks the speaker is part of another device.
are ALL the users with this problem ONLY experiencing this issue on Android or WinMo as well?
ryannathans said:
are ALL the users with this problem ONLY experiencing this issue on Android or WinMo as well?
Click to expand...
Click to collapse
From his description, it seems to only happen in Android.
I talked to stine briefly, and he hasn't tested it - is there a bug open on it? If you really want dev attention to a problem, and there isn't already a bug, file a bug. If there is a bug, post to it and add some logs - there might be something funny going on that's easily spotted.
Also, you haven't done any triage from what I can tell - does this not happen on a certain combination of rootfs, kernel, or system image? If you can recreate a scenario of where it doesn't happen, that'll help narrow it down. If it's always been happening... it'll be more difficult, but also good to know.
One of our top kernel devs has a GSM device, he's never mentioned this issue. If I talk to him today, I'll mention it to him.
arrrghhh said:
From his description, it seems to only happen in Android.
I talked to stine briefly, and he hasn't tested it - is there a bug open on it? If you really want dev attention to a problem, and there isn't already a bug, file a bug. If there is a bug, post to it and add some logs - there might be something funny going on that's easily spotted.
Also, you haven't done any triage from what I can tell - does this not happen on a certain combination of rootfs, kernel, or system image? If you can recreate a scenario of where it doesn't happen, that'll help narrow it down. If it's always been happening... it'll be more difficult, but also good to know.
One of our top kernel devs has a GSM device, he's never mentioned this issue. If I talk to him today, I'll mention it to him.
Click to expand...
Click to collapse
it happens no matter what build or combination of parts. it only happens on android anytime the speaker is on and if the speaker isn't on and any kids of alert or noise such as a button press happens the speaker comes on and buzzez till u manually turn the speakerphone on then off. basically the same noise that comes through any audio device when a GSM cell is near is comin through the speaker. i am pretty sure it only happens on 2G cause the "GSM BUZZ" does not happen with a 3G signal. if ur guy test he'll for sure hear it.
I just managed to confirm the issue on a Tilt2 - needed to force 2G.
(I almost never use speakerphone and am almost always in 3G areas so never noticed this before.)
Apparently there are some audio routing patches in the pipeline already that might fix this.
Problem gone in Android 2.3.3... works like a charm
eu0741924381 said:
Problem gone in Android 2.3.3... works like a charm
Click to expand...
Click to collapse
Interesting - did you ONLY change system.ext2 build, or did you also use a different kernel?
had this problem a few times (froyo) but never occurred in my last call.
I think it may have something to do with a data connection before or during the call? There are a few problems originating from data connections. Perhaps it was latest kernel that fixed it for me? Will have to wait and find out.
Hello everyone. We got 5 phones during the holidays from Microsoft retail store in LA. Right after we put our sim cards and start using our phones all of us realized that other party can't hear us clearly (as an example when I use my AT&T Tilt 2 other party can hear me way better). Looks like the microphone cuts all high-frequency sounds. Either it's a microphone problem (could be defected batch) or some other settings. We've already checked all possible settings with no success. Does anybody else having the same problem?
Other than that phone is really awesome!
OS version: 7.10.7720.68
Hardware version: 0002
Radio: 16.23.02.26_A_16.27.00.23U
Any suggestions?
Nobody else experiencing this problem?
Is it possible that something is wrong with this particular batch?
TITAN - Lousy Sound Quality - Other Party Can't Hear . . .
I also have most people I call tell me I sound all distorted, (Or occasionally worse.) When I have someone call from my phone to a land line, to me the receiving sound has a buzz, almost tinitus, frequency shifts, & sometimes pulsing of the signal. Don't know if this might be the microphone, transmission, or what, although it seems consistent to my Titan, Occurrs in many places . . .
I'm surprised that no one else (except you) seem bothered. I tried unchecking the signal boost / loudness check, but to no avail.
Any suggestions? How is the sound quality you others are getting? Hope it is just a bad unit that I can swap Friday, or else I'll go back to my HTC AT&T Tilt-2, (the titl-2 is a much inferior phone, but with decent sound.)
My gilfriend constantly complains that she cant hear me too well. I think its because the phone is pretty long and the mic is right on the bottom. She can hear me better when i put the bottom part closer to my mouth. Its quiet annoying. I dont think its call quality but just bad positioning of the mic by htc.
@artzznyzz Where did you buy your phone?
UPDATE on bad / inferior Titan Sound Recepton:
Following a suggestion, I un-set (TURNED OFF) my attentive phone 'flip for speaker' option, so as to NOT automaticially go to speaker only when turning phone over & setting it down for hand free use during a call. This seemed to help some. (But a drag as this was a very nice touch - Most of my usage is in office / for business)
Per 'Cubanaso', above, I am also being more attentive to not holding the phone at the top where the antena may be, and also holding it lower so as to speak nearer the microphone on the bottom edge of the phone. (Why the heck did HTC place the main voice microphone so far out of the line of normal user speach? Maybe an attempt to save $ & go with only one microphone for both normal handheld usage, and also for face down on the table hands free usage? It would seem better to have two good mics, and via software use one for main speach, and the other for noise cancelling input, depending upon orientation.)
(This specialized custom grip is a pain because of aviding so much 'verbotten' contact with the phone - Can't touch the top off/on switch, nor the camera button, nor cover the microphone, nor where the micro-USB charger is attached. Too many restrictions, until new habits are learned . . .)
Anyhow, some more minor improvement, but still inferior sound quality for the person being called (whether they are on their own other cell or landline.)
BALMADOR: I bought mine at the AT&T corporate store on Main St. in White Plains NY. The sales kid, and contract, both promised a 30 day return period.
I am surprised that, of the (presumably) thousands of Titans out there, there are so few complaints about sound quality. Maybe I / we just have the rare problem ? ? ?
Any other insight from HTC, Google, or other web sites, etc.??? (I already checked WPCentral.com, and nothing more there . . .)
There are a few other problems, although not as major as this:
- Some phone numbers within given contacts (entered in outlook 10/ exchange 10) do not display on the the Titan. Seems to be 'Car', and others . . .
- Want access to the file storage space to set up directory structure for downloaded files (like the windows subdirectory structure & access), rather than just dump them into a single place managed by the system, without any identifiers other than the file name.
- The sync & skydrive of files seems random &/or flakey - We do not have the time to debug this.
- The HTC / AT&T issue standard documentation is superficial. (Also there is no WIKI, or no easy to access WIKI yet on XDA Developers, or I can't find it . . . Suggestions ? ? ?)
- Finally, Office Mobile seems generally flakey. For example, - Seems impossible to read & edit any file formats prior to office 2010, - Very difficult in Excel to highlight and drag a several cells, - can't figure out how to copy & paste reliably, etc., etc. . . .
Summary - I want to like & keep the Titan (another unit) so I am still inclined to try an exchange, or return the phone. Does anyone else have any further suggetions? (Maybe wait & try the Lumina 800 some day - What system will that be on, Verizon or AT&T ? ? ?)
Thanks, Art
not a rare problem
I was constantly told that I sounded "muffled" or "like I was underwater".
....I took my phone to be replaced for a new device....I guess I'll see how it goes.
smokeyb111 said:
I was constantly told that I sounded "muffled" or "like I was underwater".
....I took my phone to be replaced for a new device....I guess I'll see how it goes.
Click to expand...
Click to collapse
smokeyb111, could you tell where did you buy your phone?
If you have already exchanged it, can you tell if your new phone doesn't have this problem?
smokeyb111 said:
I was constantly told that I sounded "muffled" or "like I was underwater".
Click to expand...
Click to collapse
Same here!
Actually, my phone's earpiece also sounds muffled
smokeyb111 said:
I was constantly told that I sounded "muffled" or "like I was underwater".
....I took my phone to be replaced for a new device....I guess I'll see how it goes.
Click to expand...
Click to collapse
I'm considering this as well as my titan is muffled on caller's end on about half of the calls to an unacceptable level.
Please update us on the results of a swap
Update re Sound Issue - Exchanged Unit : - )
Total fustration, so yesterday I went back to the AT&T corporate store (where I had upgraded from the Titl-2 to the Titan) and traded the Titan in for a new unit.
The trade in transaction took an hour ++, because the staff, although very friendly, cooperative and sincere, had no experience with the Titan (and I have a lot on my phone.) The store did not have or was missing the bluetooth dongle needed for content transfer, etc, etc, etc . . . But we got it done, thanks to my Exchange for Outlook, and e-mail for a few business photos, etc.
Anyhow, after 24 hours, it seems to be night and day on the sound issue - Extremely good, (except in very noisy environments); very loud both ends, better / tolerable connections in a few fringe areas where I had trouble with old Titl-2, No complaints on early test calls, etc, etc. I'll update y'all after several more days of experience . . .
So, Status Quo:
- My Titan is a very good phone (only) and decent electronic rolodex, with pretty good mapping / traffic / gps.
But:
- Lots of nagging ??software?? issues, some mentioned in prior post above. These problems seem like quality control programming bugs which should not have gotten through, and should be easy to fix. (Hope so as I really like this phone for my heavy business use!) More to follow.
HELP:
- How about a WIKI page for the Titan P139100 to organize the list of defects needing improvement, and most important, to supplement the superficial HTC / AT&T documentation, user guides? (lots of these problems may be mere lack of information & training for us users . . .)
I've tried to set up the WIKI page, with no luck. Maybe one of you with more experience can either get it started, or private message me with a little guidance . . .
Thanks
Arthur
Anyhow, after 24 hours, it seems to be night and day on the sound issue - Extremely good,
Click to expand...
Click to collapse
I appreciate your feedback and it is encouraging to know that another handset might fix my issue (call quality) with the device. thanks! Think I might try to swap out for another unit when my local store gets more in
OTOH, I don't understand your transfer issues. Do you not have all of your photos and music synced with Zune? also do you have a live account where all of your contacts and calendar is saved?
I don't use Exchange server so maybe it's different but I walked into a store and swapped devices last week (Focus S) and stood there and reset (wiped out) my phone, typed my live account on the new device and walked out of there with all of my contacts calendars and email on the new phone instantly. plugged it into Zune when I got home and had photos and music back as well.
Went online to Windowsphone.com and clicked on all the apps I had previously installed and they too were put back on the phone
For everybody who having problem with the microphone.. I just spoke to HTC Hardware Department. They even not aware of this problem. Please call them and let them know. So at lease they will add this to the known issue list. Their phone # is: (866) 449-8358
For what it's worth, I just got my phone this past weekend. I've only had a few calls so far and no complaints from anyone. I have asked everyone I talked to if they could hear me okay and there was no problem.
I bought mine from a large retailer which hopefully means they go through a lot of Titans and I got a good one.
I did play a video from GoPro today and when I max'd the volume, it was distorted and had static. Haven't had the problem with other vid's so I am assuming it was the vid and not the speaker on the phone.
Decent phone. I was about to blow up when I realized that Outlook Sync was gone but after playing with it for a few hours, I was able to get the Windows Live connector to do it's thing for me. Not 100% happy but pretty close.
Same problem here
I have the same problem. I love the titan, but I have to fix this issue (or return the phone) for the sake of my relationship and work.
It seems as if the noise cancellation software is dumbing down the highs of my voice (it sounds like I am underwater). I haven't experience this problem when using Tango to video chat. I've also read that the problem doesn't exist while recording a video. Just a heads up, people have been posting about this issue in the wpcentral forums. I'm new to the forum, so I can't post links.
Here are the links to WPCentral forum:
http://forums.wpcentral.com/titan/184444.htm
http://forums.wpcentral.com/titan/184445.htm
I've also posted in this HTC forum:
http://community.htc.com/na/htc-forums/windows-phone/f/174/t/14751.aspx
Please put your comments as well. We need HTC's attention to this problem. Now we almost sure that it's not a mic problem (thanks to TANGO). Somehow dialer/phone software (noise cancellation or coding or any other filtering) and may be camera's part are not performing as needed on some units. And it should be fixed or patched.
Just a thought that might help with diagnosing the problem. I have a wired hands free headset (don't like any of the bluetooth devices from inexpensive to way over priced) and if you think it's the microphone or software for noise reduction is the problem, I bet you could try a wired headset and see it the trouble persists. If so, I would go get a replacement phone.
Just a thought.
Can someone who doesn't experiencing a "muffled" effect send me a private message with his phone # so we can make a couple test calls? That way we can really compare and make a better statement.
I've bought a titan for my wife, and had these same mic issues, she sounds muffled, recessed, underwater, got her a plantronics 975, and call quality went from bad, to terific.
Something is definately up with the mic/software on these things. I got the UK version from Clove.
I've since bought a second device for myself, and call quality is horrible, lots of chopping out, bad signal, bad reception. I was later told by my service provider, its a problem with their HSPA network, and the TITAN was not tested on it and may not be properly supported, i swithced off the 3g radio and sure enough all my problems went away, perfect call quality and reception, but no 4g? Sucks. They say they need to do patches on their network before the phone will work properly. But that seems to be a spereate issues, the mic stuff defiantely needs to be addressed. or we all use bluetooth!
matthewhypolite said:
I've since bought a second device for myself, and call quality is horrible, lots of chopping out, bad signal, bad reception. I was later told by my service provider, its a problem with their HSPA network, and the TITAN was not tested on it and may not be properly supported, i swithced off the 3g radio and sure enough all my problems went away, perfect call quality and reception, but no 4g? Sucks. They say they need to do patches on their network before the phone will work properly. But that seems to be a spereate issues, the mic stuff defiantely needs to be addressed. or we all use bluetooth!
Click to expand...
Click to collapse
Maybe I should factor in my location to the lack of problems with my phones audio quality. I live in the Dallas area, home of AT&T, and it's possible the network has been upgraded here and when I travel outside of this area, the quality will suffer as many of you have reported. This could be why some are not having troubles and others are.
Hello dear friends,
I've been running my I9300 for about 1 1/2 years now. Yesterday, after weeks and weeks of not changing anything (PA3.99RC2), the speakers AND microphone stopped working. So now sound when playing music, no sound during calls and no functionallity of the microphone (Google Voice and Calls). The only thing, which can be related to this issue was a testing of an old external speaker, which i connected to the phones audio jack (and which did not work but did crackling sounds).
I am sure its not a software issue, as I allready reflashed PA3.99 and also returned to 4.1.2 and 4.3 stock rom. What I can say is, that the phone is running quietly well and fast, WiFi, internet, all. But: If I run something with a sound, e.g. tapping on the loudness controll or even starting mp3 or youtube it becomes laggy and stuttering, even rebooting sometimes.
My last workaround was to connect a bluetooth headset to have an "external soundcard" but i still get no sound at all and it becomes to lag.
In my opinion, the soundchip of the device was grilled by using the damaged external speakers and so it responds weirdly to signals -> generating lags on use. Do you have other ideas what could be wrong?
Now for a solution: I think, buying a new (old) mainboard on ebay and changing that part might be the best possibility. Or do you think, the damaged module is in the upper part with the audiojack and the antenna?
Thanks a lot in advance,
cmoe
cmoe said:
Hello dear friends,
I've been running my I9300 for about 1 1/2 years now. Yesterday, after weeks and weeks of not changing anything (PA3.99RC2), the speakers AND microphone stopped working. So now sound when playing music, no sound during calls and no functionallity of the microphone (Google Voice and Calls). The only thing, which can be related to this issue was a testing of an old external speaker, which i connected to the phones audio jack (and which did not work but did crackling sounds).
I am sure its not a software issue, as I allready reflashed PA3.99 and also returned to 4.1.2 and 4.3 stock rom. What I can say is, that the phone is running quietly well and fast, WiFi, internet, all. But: If I run something with a sound, e.g. tapping on the loudness controll or even starting mp3 or youtube it becomes laggy and stuttering, even rebooting sometimes.
My last workaround was to connect a bluetooth headset to have an "external soundcard" but i still get no sound at all and it becomes to lag.
In my opinion, the soundchip of the device was grilled by using the damaged external speakers and so it responds weirdly to signals -> generating lags on use. Do you have other ideas what could be wrong?
Now for a solution: I think, buying a new (old) mainboard on ebay and changing that part might be the best possibility. Or do you think, the damaged module is in the upper part with the audiojack and the antenna?
Thanks a lot in advance,
cmoe
Click to expand...
Click to collapse
I would suggest to consult a mechanic, rather than trying by yourself.
KSKHH said:
I would suggest to consult a mechanic, rather than trying by yourself.
Click to expand...
Click to collapse
Ah, almoust forgot this:
The mechanic told me that changing one of the audio chips would cost 89€. Changing both chips would cost 130€.
I got a new (used) mainboard for 50€, changed it and everything is working well (including all those reidculous data not wiped on the new chip ;P)
Greetings!
CallSoundRepair.apk - Work as well
Hello folks.
As a little hint, 'cause I had the same problem about the sound where I fixed it, with apk, check the link below, I hope that it can might work for you too.
Topic Forum = http://forum.xda-developers.com/showpost.php?p=50065763&postcount=154
Directly apk = http://forum.xda-developers.com/attachment.php?attachmentid=2560477&d=1391607726
sergioseiva said:
Hello folks.
As a little hint, 'cause I had the same problem about the sound where I fixed it, with apk, check the link below, I hope that it can might work for you too.
Topic Forum = http://forum.xda-developers.com/showpost.php?p=50065763&postcount=154
Directly apk = http://forum.xda-developers.com/attachment.php?attachmentid=2560477&d=1391607726
Click to expand...
Click to collapse
Will you stop posting this around. I have yet to see one where you have read and understood the OP Then posting something that is actually useful for the OP and the problem.
EDIT: Read the other comments in this thread to see what I've tried and what hasn't worked. Thank you!
I love my Galaxy S5 so far, but currently it's sucking at being an actual phone. On the other end of the phone line, the people I've talked to have complained of the audio sort of cutting in and out like someone is interrupting me. This happens when I'm in quiet rooms alone, so I'm confused. At first I though it was the case on my phone (Supcase), but after replicating the problem for myself, that doesn't seem to be the case. So at this point I'm not really sure if my phone is possessed or if it's a hardware problem. For reference, I'm running XtreSoLite rom and I have a few Viper4Android audio things running. I'm not sure if that could be the problem. Anyway, if someone could help me solve this issue, I'd really appreciate it. Thank you!
jtc276 said:
I love my Galaxy S5 so far, but currently it's sucking at being an actual phone. On the other end of the phone line, the people I've talked to have complained of the audio sort of cutting in and out like someone is interrupting me. This happens when I'm in quiet rooms alone, so I'm confused. At first I though it was the case on my phone (Supcase), but after replicating the problem for myself, that doesn't seem to be the case. So at this point I'm not really sure if my phone is possessed or if it's a hardware problem. For reference, I'm running XtreSoLite rom and I have a few Viper4Android audio things running. I'm not sure if that could be the problem. Anyway, if someone could help me solve this issue, I'd really appreciate it. Thank you!
Click to expand...
Click to collapse
It's certainly not normal. Not with stock firmware or custom ROMs like Phoenix. I have no idea if your custom ROM is a factor, bit it seems unlikely.
Possibly your problems are reflective of being in a location with a weak and tenuous signal strength. Generally speaking dropouts and feedback are data latency issues seen more with Voip and VoLTE calls. You don't have nearly enough information to do more than guess yet.. but I would make your audio app (Viper) to be the prime suspect.
See if you can exempt voice calls from Viper or temporarily uninstall it. Also find out if any background apps are using high CPU and in particular if any audio apps are set to high priority. Find out if you arwe using VoLTE. CPU (power saving) apps?
If you can't narrow it down, make a backup and then revert to 100% stock to rule out hardware issues. Then install apps one at a time, watching for the issue to return. You could also open a carrier support ticket to see if your account is misconfigured, using a low grade codec, etc.
.
fffft said:
It's certainly not normal. Not with stock firmware or custom ROMs like Phoenix. I have no idea if your custom ROM is a factor, bit it seems unlikely.
Possibly your problems are reflective of being in a location with a weak and tenuous signal strength. Generally speaking dropouts and feedback are data latency issues seen more with Voip and VoLTE calls. You don't have nearly enough information to do more than guess yet.. but I would make your audio app (Viper) to be the prime suspect.
See if you can exempt voice calls from Viper or temporarily uninstall it. Also find out if any background apps are using high CPU and in particular if any audio apps are set to high priority. Find out if you arwe using VoLTE. CPU (power saving) apps?
If you can't narrow it down, make a backup and then revert to 100% stock to rule out hardware issues. Then install apps one at a time, watching for the issue to return. You could also open a carrier support ticket to see if your account is misconfigured, using a low grade codec, etc.
.
Click to expand...
Click to collapse
Thank you for all of this! I'm having an unfortunate week because I'm actually away from home and have very limited internet access, so factory resetting my phone isn't currently an option. However, I did turn VoLTE off and I'll be wiping my cache because I read somewhere that might work. I'll also be watching my apps, but I'm not sure that's the problem. I generally have the same apps on all of the phones I use and this is the only phone people have said I sound bad on. And I don't think Viper is the culprit either because I've disabled it and nothing has changed. So hopefully turning off VoLTE works or simply wiping the cache does the trick. If not, I'll definitely do everything that you recommended because I want to avoid RMAing this device at all costs.
It seems that a factory reset solved the problem. I still have no idea what the problem was, though, but I'm happy it seems to be gone.
So the problem has returned. I factory reset once again and it hasn't done the trick. Everyone is describing it as an echo and telling me they can hear themselves echoing when they speak, although it sounds fine on my end. I don't know what else to do. I have:
Factory reset
Taken the sim out and put it back in
Changed APNs
I don't know what else I can do. Really hoping I don't have to RMA this device. Does anyone know how Samsung is with RMAs?
Bump
Still having this problem. I hope there's someone out there who knows how to fix it.
you ain't alone mine was fine for a while then after the new update it came back i call t-mobile.they put in a open repair tickets as others around my town also complain.my signal is always -114 to -119.they have heard it it when i call them.i get the echo or it brakes up or call turns into noise and then calls drop and they have to call me back on house phone they claim it is a tower/signal issue.??
jtc276 said:
Still having this problem. I hope there's someone out there who knows how to fix it.
Click to expand...
Click to collapse
i had this on my first two handsets it happened in the first 14 days so i had no trouble going into tmo store and exchanging it twice. people could not hear me and the echo was really bad. third s5 call quality super clear now.
been you had exchange the phone and new one working fine what software is it on NF6 or the new NG3 that would tell us a lot???before i downgrade back to the nf6
420soljah808 said:
i had this on my first two handsets it happened in the first 14 days so i had no trouble going into tmo store and exchanging it twice. people could not hear me and the echo was really bad. third s5 call quality super clear now.
Click to expand...
Click to collapse
I had this same issue as well. I could hear people jsut fine, but when they tried to talk to me, be it over tmo network or through wifi calling, they heard bad echoes and noise. I even did as you did; factory reset and it sorta worked. When it happened again, I cleared caches (the official fix from tmo 611) and that worked for a couple hours. Eventually, they told me to take it back to the store and get a replacement.
I believe it's a hardware issue related to the mic; here's why:
When I'm in my car and on bluetooth people on other end hear me just fine and crystal clear. When I used a bluetooth headset, same thing. As soon as I disconnect from BT and go to just the normal mic, echo pops in.
One thing you can do is call 611 and use the voice prompts. It was so bad on my end that the voice prompts picked up itself (well the echoes from the voice prompts). If you do and the voice prompt system routs you even when you don't say anything (it routes your call because of the echoes) then you definitely have a bad handset.
I was rooted, custom recovery, knox tripped and mailed my phone in. Nothing happened. But they did charge me $20 for a return/replacement fee. The new phone I got works no problem.