Hi, i have an unusual echo problem on my defy. When i call somebody they claim hearing themselves back. their voice and mine too. If i lover the volume not that much but still...
Tried different builds always the same.. today i tried to remove the battery cover and make a phone call and it's gone, without the cover it works completely normal no echo. Well it's ok but i don't wanna use the phone without the battery cover, besides my battery falls out with a little hit on the phone so i NEED my battery cover! anyone have any suggestions????
possible fix for echo problem
If you are brave, you could try this to fix your echo problem.
http://www.youtube.com/watch?v=FkcxzmCPFWw
bradxray said:
If you are brave, you could try this to fix your echo problem.
http://www.youtube.com/watch?v=FkcxzmCPFWw
Click to expand...
Click to collapse
Anyone tried this?
Is it Working?
Related
I have a problem with my elf: people that talk to me on the phone hear me (pretty badly) and themselves (like an echo). I tried talking from another phone and it really sucks from the other end..
I switched between a number of ROMs, installed the latest radio, but the problem persists.
Anyone had this problem? Any idea what’s wrong?
Oh.. Had a problem with it once and had to dissasemble it.. Think that may have screwed it up?
Did a search on this and didn't see anything about it, but after flashing to the 2+ ROMs, I've had a pretty bad echo on my end whenever my voice gets much above a whisper. I didn't have this issue on 1.5 and it disappears when I go back to 1.5. Anyone else have this issue or have any idea how to fix it? - other than the obvious 'go back to 1.5' fix
I had this also. If you update to Damage's new rom 2.05 based on the Sprint leak, it is no longer there.
bernard_photography said:
I had this also. If you update to Damage's new rom 2.05 based on the Sprint leak, it is no longer there.
Click to expand...
Click to collapse
have you tried fresh's new ROM? does it have the echo for you also? i'm using it right now and still have the problem. will check out damage's. thanks!
LOL Echo has nothing to do with what rom you're using.
obannvi said:
LOL Echo has nothing to do with what rom you're using.
Click to expand...
Click to collapse
Then why does it reliably disappear when I switch back to any of the 1.5 ROMs and reappear when I go back to 2.1?
p.s. went to damage's most recent ROM and echo disappeared!
jadambpharm said:
Then why does it reliably disappear when I switch back to any of the 1.5 ROMs and reappear when I go back to 2.1?
p.s. went to damage's most recent ROM and echo disappeared!
Click to expand...
Click to collapse
Its called a placebo affect.
obannvi said:
Its called a placebo affect.
Click to expand...
Click to collapse
You're right, obviously, because you're some kind of scientist, right? Point is, it works now.
And it would be placebo effect. You should come take my research methods class
jadambpharm said:
You're right, obviously, because you're some kind of scientist, right? Point is, it works now.
And it would be placebo effect. You should come take my research methods class
Click to expand...
Click to collapse
Actually, no im not a scientist. I worked for a large wireless telecom company for many many years and I know the ins and outs of how a call is made and how echos work and react when they aren't echo cancelled via the echo canceller in the central office.
obannvi said:
Actually, no im not a scientist. I worked for a large wireless telecom company for many many years and I know the ins and outs of how a call is made and how echos work and react when they aren't echo cancelled via the echo canceller in the central office.
Click to expand...
Click to collapse
So you're telling me that it's entirely impossible for something --completely-- on my end that causes me to hear myself a split second after I say something?
jadambpharm said:
So you're telling me that it's entirely impossible for something --completely-- on my end that causes me to hear myself a split second after I say something?
Click to expand...
Click to collapse
Yes. What happens is the call goes through the switching center then goes through an echo canceller to cancel out any echo. Unfortunately, this doesnt happen all the time. When an echo happens that means there are too many calls setup on the switch thats is switching that particular cell site you're connected too. usually it will go away after a few, but sometimes the echo stays and the only way to get rid of it is too start the call over...
obannvi said:
Yes. What happens is the call goes through the switching center then goes through an echo canceller to cancel out any echo. Unfortunately, this doesnt happen all the time. When an echo happens that means there are too many calls setup on the switch thats is switching that particular cell site you're connected too. usually it will go away after a few, but sometimes the echo stays and the only way to get rid of it is too start the call over...
Click to expand...
Click to collapse
Dude... i CURRENTLY work for AT&T and IBM (I know right?) and i can tell you that after being with a telecom company for so long you don't know what you're talking about... Thank you, come again!
Hi,
many people still claim there isn't such a problem but there IS:
After ending a call the screen stays off and can't be turned on again. Hardwarekeys don' t do anything.
Only option: Hold the phone in bright light or take battery out -.-
I tried the most popular roms here (NAND&SD)
In WinMo everything works fine.
So here i want to show that not only i but many others suffer by this issue.
Hopefully some real CHEFS/Devs realize this.
Making tons of senseless customisations and graphics tweaks isn't enough to be a real Dev...
Here are some of the threads concerning this issue so far:
http://forum.xda-developers.com/showthread.php?t=1061481
http://forum.xda-developers.com/showthread.php?t=965123&highlight=call+screen
http://forum.xda-developers.com/showthread.php?t=1097531&highlight=call+screen
http://forum.xda-developers.com/showthread.php?t=1097531&highlight=call+screen
http://forum.xda-developers.com/showthread.php?t=735906
http://forum.xda-developers.com/showthread.php?t=946012
http://forum.xda-developers.com/archive/index.php/t-946012.html
srmemnoch2 said:
gsm.proximity.enable=false
you can include this in your build.prop file, locate in /system and reboot.
this never turn off screnn during calls..
but i think only run in froyo
im desperate i want update to gingerbread but this code do not run on ginger.
ragards
Click to expand...
Click to collapse
this really helps! But now the screen stys on all the time, must be careful not to end the call by touching the screen XD... But it's better than having a blocked phone.
But still the issue itself isn't solved ...
You could try http://www.xda-developers.com/android/proximity-sensor-re-calibrator-for-desire-hd/ this?
yes tried this already before, thanks, but didn't work.
I know this problem sounds weird to those who don't have this issue but it's real (i'm not crazy XD) The hardware is also working correctly as on WinMo everythiong's fine
I'm been having this problem since my first rom. I actually thought it was just my phone. It drives me crazy, as I found that plugging it in gets the screen to return. Very annoying!
Sent from my HD2 using XDA App
First I would like to thank Maniac for all his hard work getting the kineto wifi calling working with CM7 on the Defy.
It seems to be working fine except for one issue. The caller on the other end is getting a nasty echo of their own voice. I restored my phone back to the Moto Froyo 2.2 rom and it does not seem to have this problem. If anyone has any ideas how to fix this I am certainly willing to give it a try.
Thanks again.
This might be related to the second (noice cancellation) microphone. Does that also happen if you're using a headset (wired/BT)? In any case, about the only idea I have at the moment would be replacing the audio libraries to the ones in the stock t-mobile ROM. I've attached them; please copy libaudiopolicy.so to /system/lib, reboot and retry; if the problem is still there, please do the same with libaudio.so. Then give feedback about the outcome
Thanks for replying.
I copied the libaudiopolicy.so to /system/lib using es file explorer, but upon rebooting the phone it hangs at the moto logo screen.
Is there anything else I need to do?
Oh, that's bad. You normally don't need to do anything additionally. As I don't have time to investigate this at the moment, I suggest to reinstall the nightly you're using in order to get your phone into a working state again for now.
EDIT: But do you get the same kind of echo when calling with headset or speakerphone?
Sent from my Defy
Yes, the echo is still there with a wired or bluetooth headset or speakerphone mode. But oddly enough if I enable mute the echo goes away.
I was able to get my phone working again by restoring a backup.
Hi i can confirm that this is indeed a problem that happens consistently (tho the kineto app works perfectly with Voice and text messages).
When you copy the two proposed files to the file system using Root explorer, it causes the phone to hang upon reboot.
Anything i can do to aid in the fixing of this issue? i would love to have this very annoying echo gone.
Thanks in advance.
Did you set the permissions the same as the previous?
Hi, the permissions appeared to be the same according to root explorer.
Can anyone confirm that swapping in these libs has fixed the echo problem? I tried replacing libaudiopolicy.so first and got stuck at the Google/Moto bootup screen just as Mr. Cool did, and had to do a restore on my phone. I guess it would make sense to copy both files, but I'd at least like to hear that it worked for someone else first.
I also had trouble with callers complaining of a bad echo. I tried replacing both libaudio.so and libaudiopolicy.so, but replacing those files resulted in the phone getting stuck at the boot screen.
wifi calling echo
just installed the latest "CyanogenMod-7-20120628-unofficial-jordan." confirmed when talking to my wife that there is a huge echo on her end and not on my end.
capntang said:
I also had trouble with callers complaining of a bad echo. I tried replacing both libaudio.so and libaudiopolicy.so, but replacing those files resulted in the phone getting stuck at the boot screen.
Click to expand...
Click to collapse
I did this to clear up my stock ROM wifi-calling quality but others have mentioned also doing this to clear up quality issues on alternative ROMs with wifi-calling: go into your router setup and if default is "mixed mode" change to either straight G or N. May help.
scrannel said:
I did this to clear up my stock ROM wifi-calling quality but others have mentioned also doing this to clear up quality issues on alternative ROMs with wifi-calling: go into your router setup and if default is "mixed mode" change to either straight G or N. May help.
Click to expand...
Click to collapse
Thanks for the idea. I changed my router from "mixed mode" to G only, but the echo persists.
Hi,
in the last days with my S3 on every call I had which went for more than 1 minute the other person suddenly couldn't hear me anymore. Sometimes it happened after a minute, sometimes after 3 minutes, but in the last 4 calls it happened every time!
Reception came back after some seconds and from then on it was really bad, the other person had hard problems understanding me.
I searched around and found this thread of GNex owners having the same problem:
http://androidforums.com/samsung-galaxy-nexus/472451-vzw-other-person-cant-hear-me.html
Then I found it in the Issues DB too
http://code.google.com/p/android/issues/detail?id=24019
Do you guys know more? it is really bad, since this is my business phone so nearly every call is an important one and it really bugs me out.
Anyone having same problems?
I hope someone can help me out.
Yes I have the exact problem. It's driving me nuts and I've tried different roms and kernels.
Sent from my GT-I9300
Have you tried to DISable the noise canceling feature?
No but I will try it and report back.
By the way I'm on stock LF6 4.0.4 in Germany (with o2 as my carrier. Unbranded. )
Is the noise canceletion buggy?
Sent from my GT-I9300 using xda app-developers app
I've read that some kernels cause issues like this.
Also, in UK, in Birmingham on Orange, I have been having issues like this, and it usually occurs when the Signal Switches over from Orange to T-Mobile, mid call, and once onto T-Mobile signal, the call breaks up or goes quiet.
Maybe an issue switching from 2G to 3G or back mid call also?
BobFL said:
Have you tried to DISable the noise canceling feature?
Click to expand...
Click to collapse
Will try also. The only reason I haven't got rid of this phone is it mostly happens on o2 calls, I am on giffgaff which is run by o2, The op is o2! Hmmm
Sent from my GT-I9300 using xda app-developers app
just yesterday I again had the issue....and my noice cancelling was off...so this is not causing it....
I'm bumping this in hope someone has a cure.
The new rom LFB is not yet published for Germany but for UK. Perhaps it makes a difference? Can somebody in UK with LFB who previously had the issue please check?
Same problem, no solution
I'm facing the same issue. Tried searching for any possible explanations, but haven't found anything conclusive.
I've tried disabling and enabling noise cancellation and all combinations of the in-call options.
There are 2 or 3 main theories which I've encountered:
1. The microphone goes to sleep when the phone display does. As soon as someone seems to not able to hear me, I move the phone away and the screen wakes up. This seems to sort it out temporarily.
2. Someone had posted on FixYa indicating that they tried putting a small piece of cotton after removing the back panel just behind where the mic is. Haven't tried this!
3. Everyone else seems to think that a factory reset would set it right. I haven't tried this as I need to find a bit of time to do this.
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).
the-0ne said:
I'm facing the same issue. Tried searching for any possible explanations, but haven't found anything conclusive.
I've tried disabling and enabling noise cancellation and all combinations of the in-call options.
There are 2 or 3 main theories which I've encountered:
1. The microphone goes to sleep when the phone display does. As soon as someone seems to not able to hear me, I move the phone away and the screen wakes up. This seems to sort it out temporarily.
2. Someone had posted on FixYa indicating that they tried putting a small piece of cotton after removing the back panel just behind where the mic is. Haven't tried this!
3. Everyone else seems to think that a factory reset would set it right. I haven't tried this as I need to find a bit of time to do this.
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).
Click to expand...
Click to collapse
Which ROM are you using right now?
Ihad the same issue on CM9 and got rid of it by flashing another radio. I originally had the xxlef, tried the xxlfb and ended up with the xxlf5 which works fine so far.
Try this for a fix
goto settings
sound
Toggle on then off or off then on the screen lock sounds then try again :good:
the-0ne said:
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).
Click to expand...
Click to collapse
Hey,
just so you know. I am on CM9 and I have kind of the same issue. Sometimes audio is unidirectional, both ways actually, unable to recreate it so far. What always seems to work is my bluetooth headset. Switiching between the two of them makes me lose audio entirely. I have tried many things, even rebooting the phone Sometimes it helps, sometimes it doesn't. I'm guessing it has something to do with BT.
I am NOT facing the issue with losing audio in the middle of the call when the display goes to sleep. The display goes to sleep because of the ligth sensor, btw. - not because the system is idling The display is not needed once the phone realizes it's attached to your ear (lights off).
It's driving me nuts
BUT: CM9 is amazing so far. It's fast, it's open, everything works just fine. Except for the phone as a phone of course
change modem
Oomahey said:
Which ROM are you using right now?
Click to expand...
Click to collapse
Using Stock right now. OTA updates till Jun 26th.
badaeng said:
Ihad the same issue on CM9 and got rid of it by flashing another radio. I originally had the xxlef, tried the xxlfb and ended up with the xxlf5 which works fine so far.
Click to expand...
Click to collapse
Mine's currently DDLF3
winwiz said:
Toggle on then off or off then off the screen lock sounds then try again
Click to expand...
Click to collapse
I've just tried this, will report back. How do you think lock sounds affect the mic, though?
avetny said:
change modem
Click to expand...
Click to collapse
Does CM9 come with an integrated modem switcher? I don't like messing around with "packages" too much. The more you mod everything, the less stuff has got to do with each other and it is more likely to run into trouble, because as a developer you can't really consider every side effect
So if this is actually about the modem (which I doubt, because the connection is just fine, it's just the audio output and input that is kind of broken) - what modem would I use with CM9? Can I just flash a random one over the current one?
Appreciate the advice.
Andreas
I notice that as soon as I take the phone away from my ear and the screen lights up I can again be heard... Wonder if there's a problem with the light off sensor affecting the mics too... It ALWAYS goes away when I remove the phone from my ear and the light sensor allows the backlight to come on again...
Might be a crazy thought but the evidence does seem to support this. I haven't turned off the light sensor in settings yet, if I even can, but was going to try next call...
I updated to BLG8 and I will see tomorrow if it happens again. Today I already had one call which lasted 11 minutes without interruptions. I will report as soon as I got more calls to test.
I had the same prob...
I just reflashed the official firmware frm the service centre.
Sent from my GT-I9300 using xda app-developers app
Same problem here. Tried several roms, kernels and modems. Only one working for me is Checkrom v3 with xxlbf... but here also after a while some calls it reappears... I reflash modem and I am set for the next couple calls... then again
Ps: i am from Romania on Vodafone
Sent from my GT-I9300 using xda premium
I'm the OP and I now didnt had the problem for 2 months with the last stock ICS build.
It seems to be resolved.
I'm now on JB since today (XXDLIH) and will report if it comes back.