Several people have complained of hearing their own voice echoing back to them when on a call with me.
I tried *228 option 1 and 2, different ROMs, and turning the in-call volume down. But no luck.
I heard something about echo cancellation and hearing-aids, but haven't been able to find any fixes.
Anyone have a fix for this, or suggestion?
Ive noticed it happen a few times. A reset usually fixes it.
WalkingTaco said:
Ive noticed it happen a few times. A reset usually fixes it.
Click to expand...
Click to collapse
By that do you mean power-down and re-boot? I do that pretty regularly (at least every other day) and still have the problem.
Thanks though!
TheAtheistReverend said:
Several people have complained of hearing their own voice echoing back to them when on a call with me.
I tried *228 option 1 and 2, different ROMs, and turning the in-call volume down. But no luck.
I heard something about echo cancellation and hearing-aids, but haven't been able to find any fixes.
Anyone have a fix for this, or suggestion?
Click to expand...
Click to collapse
Suggestions that I have heard - update the radio, although I will not doing that on mine.
I have not seen any fixes that you have not already mentioned.
As a hearing aid user, I have been trying to follow this and see where the cause is. Mind if I ask,
What ROMs have you used specifically?
What are your software settings?
So far in all the reading, it is across the board so to speak. Have not seen any real fixes as of yet.
feel free to PM to discuss further.
dianeofarcadia said:
Suggestions that I have heard - update the radio, although I will not doing that on mine.
I have not seen any fixes that you have not already mentioned.
As a hearing aid user, I have been trying to follow this and see where the cause is. Mind if I ask,
What ROMs have you used specifically?
What are your software settings?
So far in all the reading, it is across the board so to speak. Have not seen any real fixes as of yet.
feel free to PM to discuss further.
Click to expand...
Click to collapse
I have used: Official21, Vanilla, Legend Build(EE), Eris Lightning, EvilEris2.01, Aloysius2.0, and Ivans0.8T2. I am now using Sense-able as it is the least buggy for me so far with OC. The only ones I can say for sure that have had the echo for me have been the last 4 including Sense-able.
Not sure what settings you're looking for, but here goes the ones I think may be related:
TTY off
Hearing Aids off
Voice Privacy off
In-Call Volume at about 75%
TheAtheistReverend said:
I have used: Official21, Vanilla, Legend Build(EE), Eris Lightning, EvilEris2.01, Aloysius2.0, and Ivans0.8T2. I am now using Sense-able as it is the least buggy for me so far with OC. The only ones I can say for sure that have had the echo for me have been the last 4 including Sense-able.
Not sure what settings you're looking for, but here goes the ones I think may be related:
TTY off
Hearing Aids off
Voice Privacy off
In-Call Volume at about 75%
Click to expand...
Click to collapse
Thanks for the information, Evil Eris 2.0.1 does have the echo (which I need) Next on my list is Ivans, hope to be able to get time in the next day to try out.
As for settings, I am interested in comparison are these numbers.
Firmware Version: 2.1
Baseband Version: 2.32.40.11.09
Kernal Version : 2.6.29oc/[email protected]#25
Software number 2.2.651.1
PRI: 2.11_002
I have tried Zen EXP by .mac. I like it, ran nice however heard no echo on it.
(edit: might want to try that one and see if the echo is present for you,)
Currently using Evil Eris 2.0.1 (edit: trying Ivan's 1.0 - nice, no problems so far and echo is present)
dianeofarcadia said:
Thanks for the information, Evil Eris 2.0.1 does have the echo (which I need) Next on my list is Ivans, hope to be able to get time in the next day to try out.
As for settings, I am interested in comparison are these numbers.
Firmware Version: 2.1
Baseband Version: 2.32.40.11.09
Kernal Version : 2.6.29oc/[email protected]#25
Software number 2.2.651.1
PRI: 2.11_002
I have tried Zen EXP by .mac. I like it, ran nice however heard no echo on it.
(edit: might want to try that one and see if the echo is present for you,)
Currently using Evil Eris 2.0.1 (edit: trying Ivan's 1.0 - nice, no problems so far and echo is present)
Click to expand...
Click to collapse
Firmware: 2.1
Baseband: 2.40.00.01.22
Kernel: 2.6.29 [email protected] #46
Software number: 2.26.605.4
PRI:2.11_002
I'll look into the Zen EXP, Thanks!
Related
Hey everyone. im from the Hero CDMA forum. i have made audio fix patches for the hero that fixed the audio loss for 2.1 roms.
I recently ended development for the audio fixes because the issue began to rise in people with stock heros. but with that aside, i will create a fix for eris users if enough of you have the problem. i believe i have seen 7-8 people with it. anyways leave a comment telling me you have the issue, when it happened, what roms cause it, and what your software builds are, and what roms dont cause the issue. thanks for the cooperation and i hope i can help
Hey Avalaunchmods!
Thanks for the help with this! I am running the Aloysius (Coincidentally a Hero port):
http://forum.xda-developers.com/showthread.php?t=663893
Audio usually cuts out for me when I am receiving a notification. It will kind of stutter/jitter and then continue to play.
one of my custom ringtones cut out on an incoming call once, but only once. so it may have only been a fluke. hadnt happened before or after.
ivans .8
alexhendershott said:
Hey Avalaunchmods!
Thanks for the help with this! I am running the Aloysius (Coincidentally a Hero port):
http://forum.xda-developers.com/showthread.php?t=663893
Audio usually cuts out for me when I am receiving a notification. It will kind of stutter/jitter and then continue to play.
Click to expand...
Click to collapse
I get the same using VanillaDroid ROM.
Thanks for the help!
I have had this problem pop up intermittently, but with increasing regularity (up to 2-3 times daily at its worst). The sound profile and volumes remain unchanged, but sometimes for no apparent reason, all audio drops. If I get a call, there is no ringer. If I get a notification, there is no audible alert. If I place/answer a call, the earpiece/speakerphone are silent, and the other party doesn't hear me. The rest of the phone's functions still work, and vibrate still works, but there is no audio from any apps or OS functions until I reboot the phone.
As for particular triggers, I haven't found any yet. I had been running ivan's 0.8t2, but have downgraded to his older 0.5.4 to see if the problem is fixed. So far it hasn't popped up, but it's only been a few days.
Thanks again for your willingness to help. I'll be sure to let you know if I see the problem resurface.
I know the fix is only possible in rooted phones, but I wanted to chime in and let you know that a lot of people on 2.1 leak v2 non-rooted are having this issue, so you can see some of the symptom reports in these threads on androidforums:
http://androidforums.com/htc-droid-...en-phone-goes-silent-multiple-times-week.html
http://androidforums.com/htc-droid-eris/57804-calling-problems.html
thenestor said:
I know the fix is only possible in rooted phones, but I wanted to chime in and let you know that a lot of people on 2.1 leak v2 non-rooted are having this issue, so you can see some of the symptom reports in these threads on androidforums:
androidforums.com/htc-droid-eris/66298-phone-useless-when-phone-goes-silent-multiple-times-week.html
androidforums.com/htc-droid-eris/57804-calling-problems.html
Click to expand...
Click to collapse
I have a non-rooted phone and I have the same issues...
If by audio problems, you mean no sound via ringtones, notification or voice over the ear piece, then I have experienced it with Ivan's 08T2. I've had it happen about three times. I did a reboot and it corrected it.
another Aloysius user here, and yep, audio problems out the wazoo. good thing I text mostly.
alright this got moved to general?
i though this would fit in development haha.
anyways ill get on a fix i believe. ill put it somewhere. not dev..
I've had audio issues, but the only thing that seems to cause it for me us getting a force close on any program that is currently playing audio, such as a music player or (worse) an alarm clock.
I've never had audio just randomly cut out on me, but it definitely all stops working after such a force close
I'm having the same audio issues. I'm currently on VanillaDroid v1.0. I experienced the issue on the eris21official-root ROM as well. It usually happens after I use the camera to snap a few pictures. If I don't use the camera, it is pretty stable. Let me know if you need any further information.
Avalaunchmods said:
alright this got moved to general?
i though this would fit in development haha.
anyways ill get on a fix i believe. ill put it somewhere. not dev..
Click to expand...
Click to collapse
Thanks ..... I don't think I have had these problems (but maybe I have and just didn't realize it) but its nice nowing there is a fix out there and people like you are out there using your time to create fixes
I i use it ..... i will "buy your time back"
Avalaunchmods said:
Hey everyone. im from the Hero CDMA forum. i have made audio fix patches for the hero that fixed the audio loss for 2.1 roms.
I recently ended development for the audio fixes because the issue began to rise in people with stock heros. but with that aside, i will create a fix for eris users if enough of you have the problem. i believe i have seen 7-8 people with it. anyways leave a comment telling me you have the issue, when it happened, what roms cause it, and what your software builds are, and what roms dont cause the issue. thanks for the cooperation and i hope i can help
Click to expand...
Click to collapse
Avalaunchmods,
Since the Droid Eris kernel code was made available from HTC, have you been able to make any further progress fixing the audio loss bug for the Eris and Hero?
Right now the only solution we know of is to replace the phone. (Those of us who have gotten warranty replacements have not had the problem resurface.)
But even if the problem is related to certain hardware, it seems like there might be a way to fix the kernel's *reaction* to the problem, so that the phone doesn't become unusable.
Having the problem too.
Happened on Evil Eris and Ivans.
Any update on this? I am having the same issue on both CyanogenEris v1.1 and ELB-Cyanogen.
i am having this issue as well, running Ivans Eris_Official 1.0 Alpha. Experienced this issue on the 0.82t also. No audio from the phone's earpiece (speakerphone wont work either) when a call comes in, or if i try to call them back. have to reset the phone and then it works. I'm running setcpu at 710 now, but i wasn't on 0.82t so probably not the culprit.
My software version stats, in case it matters -
Firmware - 2.1
Baseband - 2.42.00.04.12
Kernel - 2.6.29oc [email protected]#26
Build # - 2.36.605.1 CL1165907 release-keys
Software - 2.36.605.1
PRI - 2.11_002
PRL - 51739
Eri - 5
*double post oops*
hi..i'm havin this issue too!
I'm on a froyo rom now. I was on an xtr rom when I noticed this problem. Tried to flash a new rom to get rid of it and it's still there. I can use the phone for a few hours and then the only way i can answer calls is through speakerphone.
Model Number-FroyoEris
Android Version-2.2
Baseband-2.42.00.04.12
Kernel - 2.6.29 [email protected]#3
build number-kaosfroyo v13
HEEELLLLPPPP!!!!
Audio Problem
I've had this problem every since the 2.1 update. My wife and I both had it (we both have a Eris) on unrooted phones. I rooted to ErisLightning and still had it, switched to Tainted Vanilla, and now I'm on Lightning Bolt. My wife is on Droid Does Pink and we've had the problem with every single rom. Sometimes when we receive or make calls, the phone will go completely mute. We can't hear the other person and they can't hear us. We can't hear a ring tone if calling someone either.
I use Google Voice and I sometimes get ghost voicemails. It will save the entire length of the voicemail, but it will be completely mute. Even if I restart and re-open GV it's still mute.
For now, we're just rebooting whenever we have this problem. Seems to be the only way to get audio back.
Does it happen to you?
You are talking on a call (on your Froyo'ed Eris), and you feel your phone vibrate twice; you can't hear the other party, so you look at your screen, and sure enough, it says "call lost" (or similar). So you go to redial, but then after a few seconds, you realize: the other party is still on the line!
If you were using the speakerphone toggle, it will have been turned off.
I really don't yak on my phone much, so the fact that I've seen it a few times leads me to think it is pretty common.
My phone has been solid as a rock since Drop Day (Nov 6th), and I never experienced this on 1.5 or 2.1 stock, or any 2.1 dev ROMs, but I've seen it on both Tazz V6 and Kaos V29.
Has it happened to you?
bftb0
[SIZE=+1]Edit 2/15/2011 - A very likely fix for this problem has been identified. See this post:[/SIZE]
http://forum.xda-developers.com/showthread.php?t=956091
Edit 9/14/2010 - see diagnostic information in post #27
bftb0 said:
Does it happen to you?
You are talking on a call (on your Froyo'ed Eris), and you feel your phone vibrate twice; you can't hear the other party, so you look at your screen, and sure enough, it says "call lost" (or similar). So you go to redial, but then after a few seconds, you realize: the other party is still on the line!
If you were using the speakerphone toggle, it will have been turned off.
I really don't yak on my phone much, so the fact that I've seen it a few times leads me to think it is pretty common.
My phone has been solid as a rock since Drop Day (Nov 6th), and I never experienced this on 1.5 or 2.1 stock, or any 2.1 dev ROMs, but I've seen it on both Tazz V6 and Kaos V29.
Has it happened to you?
bftb0
Click to expand...
Click to collapse
I believe with Froyo it auto reconnects dropped calls, this happens all the time to me and I actually like it.
the vibrations are in your settings
one buzz = call connected
two buzzs = call dropped
jrozga said:
I believe with Froyo it auto reconnects dropped calls, this happens all the time to me and I actually like it.
the vibrations are in your settings
one buzz = call connected
two buzzs = call dropped
Click to expand...
Click to collapse
I poked around a little and couldn't find any mention of it as an official feature of 2.2; do you have a link?
Does it seem to happen to you about as frequently as you were getting plain ole' dropped calls on 2.1 or 1.5, or more frequently?
bftb0
Never had a call dropped =\ can't say, sorry.
this happens to me all the time
im on tazz v8 froyo
I get one buzz then the lost call sound but after like one or two seconds i can hear the person on the other side
It happens frequent
carycooke said:
this happens to me all the time
im on tazz v8 froyo
I get one buzz then the lost call sound but after like one or two seconds i can hear the person on the other side
It happens frequent
Click to expand...
Click to collapse
Does it happen more frequently than the rate at which you used to get dropped calls when you were on 2.1 (or 1.5) ROMs?
I don't know whether it is a bug or not - if jrozga is correct, then it should happen about as often as plain-ole dropped calls occurred with 1.5 or 2.1 ROMs. (Or maybe to be fair, as often as dropped calls occur with stock 2.1 phones with the July 2010 OTA - they have the same radio as most rooters are using)
I still haven't found anything on line from "official" sources that mention that this is expected behavior in Android 2.2 phones. The last time it happened to me, I questioned the other party on the line, and they said "I heard one buzz for about half a second". (They were on a land-line, so it eliminates their end of the connection as the source of the trouble.)
That's a little bit bizarre if they heard the first of the two vibrations on my Eris - it means my Eris had decided that the call had terminated even though it had not. That alone inclines me to believe it is a bug, not a feature.
bftb0
I get it on about every call since installing 2.2
Sent from my FroyoEris using XDA App
I'm running celb 2.1 and today made a phone call in a poor signal area and still made it all the way thru without dropping or anything is it a radio problem per chance?
tburns said:
I get it on about every call since installing 2.2
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
That's exactly why I think it is a problem with the current batch of developer 2.2 (Froyo) ROMs.
As I said, I don't make that many calls, so I don't really know how often it happens - but given that it has happened to me a couple of times now (given the small amount of calling that I do), it makes me think it is not just a signal reception issue.
Which ROM and Radio firmware are you using BTW?
I've used kaos for about a month and been on celb for almost a week and have not had such an issue. I use my phone frequently for work, too. I have had the current radio from the july update since a week after it was available.
Sent from my ERIS using XDA App
Bump.
We now have 15 people on XDA (in the Eris forums) reporting the symptom:
bftb0: Tazz V6; Kaos Froyo V29 [Froyo]
jrozga: (unknown) [Froyo]
carycooke: Tazz V8 [Froyo]
tburns: ??? [Froyo]
mcook1670: "All Froyo ROMs" [Froyo]
punkxdead: CELB [CyanogenMod]; CELB Froyo [Froyo]
Macrodroid: Kaos & Tazz [Froyo]
droiderisuser: ??? "2.1"
danwguy: CELB 2.7 cyamogenmod 5.0.8-DS firmware 2.1-update1 [CyanogenMod]
pablocasiano: WW4.6, KaosFroyo V29
crax0r: KaosFroyo V29
tjthebest: CELB 2.8-CM5.0.8
mistaj: CELB 2.8-CM5.0.8
npong: CELB 2.8-CM5.0.8
mflane: CELB 2.8-CM5.0.8
Some of them say "it happens all the time"
And 10 more people over in the AF Eris forum reporting the same oddity - on different Froyo/AOSP ROMs:
erisuser1: Tazz V6; Kaos Froyo V29 [Froyo]
snozzcumber: Kaos Froyo V?? [Froyo]
TJTHEBEST: CELB 2.9 [CyanogenMod]
MrBojenglz: Buufed v???
BlueDC2: CELB v?, Kaos V?
rick311:
BellaSkye: Kaos V32
Kaessa: Kaos V32
tpatnoe: Kaos V30
rc346: Kaos V34
funkyfender: "CM6"
john58543: KaosV30
So far, only one user has said "this also happened to me on a 2.1 ROM" - droiderisuser
[ Edit ]: At least two people have reported this on older radios, and and also on non-Froyo (but CyanogenMod ROMs)
If it happens to you, and you have the SDK set up on your PC, and it is convenient to do so, try to make a note of the time when it happens, and then when your call is complete, dump a "logcat" to your PC, and post up the log during that same minute here.
Code:
C:\blech> [B][COLOR=green]adb shell logcat > strange_call_reconnect.txt[/COLOR][/B]
[I](wait about 30 seconds and then hit ^C (Control-C) )[/I]
I've had it happen on all Froyo roms. I work for the FDOT so I'm on the highway 8 hours a day. I don't know if its the phone changing towers or what. I always have a good signal because the towers are next to the highway. Not sure what it is but its annoying
Sent from my ERIS using XDA App
Houston, we have a problem.
TJTHEBEST over on AF indicates he experienced the same problem using an older radio firmware on CELB
I have not found any evidence to support or deny jrozga's claim that this is a Froyo "feature", rather than a bug. I'll try to poke around a little and see if I can find anything further.
bftb0 said:
Houston, we have a problem.
TJTHEBEST over on AF indicates he experienced the same problem using an older radio firmware on CELB
I have not found any evidence to support or deny jrozga's claim that this is a Froyo "feature", rather than a bug. I'll try to poke around a little and see if I can find anything further.
Click to expand...
Click to collapse
I also had this problem with CELB with the 2.41.04.02.02 radio. I switched to CELB Froyo after it 'matured' (hoping to resolve it) and still had the issue. I have since switched to KaosFroyo v29 and the latest "July" radio. The issue is still present.
BTW Heres a quote from my post in the CELB Froyo thread awhile back:
punkxdead said:
I have had this problem with ErisLightningBolt and CELB Froyo, (and KaosFroyo when I tested it). I never had this issue in a Sense based ROM (PlainJane), only in the AOSP/Cyanogen based ROMs. I live in a city with great 3G coverage and never experience the issue while at home, however I travel alot for work. When driving through rural areas it happens to me all the time. My call "ends" screen goes away, phone beeps and vibrates (like when you end a call), audio drops out, 5 secs later, screen comes back, call resumes. The caller on the other end always assumes I had another call/call waiting beep, etc. I believe the phone is switching from 3G to 1x in the process causing this, but I can't be certain. I have been patiently searching/working to find a solution but to no avail. Just thought I'd post since I'm finally hearing of others with this issue.
Click to expand...
Click to collapse
Never happens to me, and I make phone calls about twice per day.
punkxdead,
Thank you for that detailed report. Very useful information
Turns out that TJTHEBEST from AndroidForums experienced the problem on 2.1 CELB, which is not Froyo - but I guess it is a CyanogenMod build. That further corroborates your experience.
So far, nobody has reported this in a Sense-based ROMs. I'm a little fuzzy on the genealogy of the kernels in the various roms, although I suppose the problem could also be occurring in "rild" or it's supporting libraries.
It's not a show stopper by any means, but it is annoying; it would be nice if we could figure out how to get it fixed, since it seems to appear in lots of different dev ROMs.
If you are able to do the 'logcat' thing to see if we can find some more info, please give it a try; I will do likewise.
bftb0
punkxdead said:
I also had this problem with CELB with the 2.41.04.02.02 radio. I switched to CELB Froyo after it 'matured' (hoping to resolve it) and still had the issue. I have since switched to KaosFroyo v29 and the latest "July" radio. The issue is still present.
BTW Heres a quote from my post in the CELB Froyo thread awhile back:
Click to expand...
Click to collapse
I can confirm the 3g to 1x theory. This has happened twice on my phone, several times on my wifes since,we loaded tazz v8. It also happens on kaos. Not on any of the 2.1 roms ive used. Each time, the phone,is,in the 1x data state. I've had it on speaker amd watched this happen each time. When 3g comes back, so does the,other caller. I think it may have something to do with network selection in froyo.
I have recently changed mine from automatic to home only... So far, no bug yet (only been a couple of days, though..).
Sent from my Froyo Eris using XDA App
Macrodroid said:
I can confirm the 3g to 1x theory. This has happened twice on my phone, several times on my wifes since,we loaded tazz v8. It also happens on kaos. Not on any of the 2.1 roms ive used. Each time, the phone,is,in the 1x data state. I've had it on speaker amd watched this happen each time. When 3g comes back, so does the,other caller. I think it may have something to do with network selection in froyo.
I have recently changed mine from automatic to home only... So far, no bug yet (only been a couple of days, though..).
Sent from my Froyo Eris using XDA App
Click to expand...
Click to collapse
Hmmm. Interesting. I think EVDO (3G) and CDMA Voice are mutually exclusive (simultaneously, anyway - a fundamental technical limitation of the way EVDO is implemented as an overlay in CDMA networks). I suppose it could be that if the ROM thinks that the voice call has ended, the "3G" icon appears right away. So it's not too surprising that you would see something changing in the display at the moment the call is "temporarily lost".
bftb0
bftb0 said:
Hmmm. Interesting. I think EVDO (3G) and CDMA Voice are mutually exclusive (simultaneously, anyway - a fundamental technical limitation of the way EVDO is implemented as an overlay in CDMA networks). I suppose it could be that if the ROM thinks that the voice call has ended, the "3G" icon appears right away. So it's not too surprising that you would see something changing in the display at the moment the call is "temporarily lost".
bftb0
Click to expand...
Click to collapse
I'm not really sure what the network option really would do. I do know that froyo isn't an eris os, so maybe it's something related to how it interacts with our phones... Either way, i'm waiting to see if the bug comes back on home only. Still love froyo, regardless!
Sent from my Froyo Eris using XDA App
Not sure if this helps but I have an Eris and pre Froyo when I was using Plain Jane I believe it was not sure precisely but It was a 2.1 rom for sure I had this happened to me quite frequently. So I would assume it is not just a 2.2 issue.
I've searched around but can't find anything about this so I humbly ask you guys not to flame me and point me in the right direction if I've overlooked something. Over the last month or so when I use any Kernel that has Voodoo my callers get an echo on their end when talking to me. I'm pretty sure it's Voodoo because when I run just KB1 or KB5 stock for instance the call is clear. When I load Voodoo I get reports of the echo.
Currently I'm on stock KB5 deodexed [Found Here] and the Bali KERNEL v1.7.2 [Found Here]. The only thing I can think of maybe is that it's because I'm running a stock ROM with a custom KERNEL, but I can't find anything that specifically says I can't do that. Any insight from anyone would be awesome. Thank you in advance for your time and assistance.
I'll try it out for ya tonight if nobody else posts a fix by the time i get off and see if i can reproduce your issue. I agree there shouldnt be any problems with this setup, kinda weird really. I will say people are having issues with 2.2 stock lately maybe thats ur issue, i dunno? you really shouldn't have any issues. Maybe try a diff kernel or modem? They are really easy just flash whenever, no need for 100% batt or to let phone sit really.
+1 on the links. easier to undrstand and see what ur doing to ur phone.
ok, I have it figured out. It's definitely the Wifi Calling App. I only get an Echo when I have it enabled. Now all I have to do is figure out how to fix that. Any clues anyone?
I dont have any wifi calling app and i was about to post confirmed here were my results:
- I made a call on Malice1.3.1 w/ Bullet 1.42Ghz kernel and NO ECHO.
- Flashed Stock froyo 2.2 and Bali kernel Voodoo disabled NO ECHO
- Enabled Voodoo made a call ECHO
my test was done with the same person each time. Good luck!
Hi all,
maybe someone can help, i have been using the cyanogenmod 7.1 for the last couple of days and my only bug so far is that whenever im on a call, where im using the speakerphone, the other person complains of hearing themselves, like echoing. I am running cm7.1 with glitch v12 beta, and ed05 radio. Anyone experiencing the same and have a fix? or anyone else running cm7.1 without the issue (please post kernal and radio used)?
i really like the rom and would have to hate to downgrade but i really need the speakerphone. Thanks in advance for any help guys!
Can anyone help or offer a suggestion?
Sent from my SCH-I500 using XDA App
Nope. Known issue.
good day.
So nothing can be done? Can you give your opinion on a good stable Rom....
Sent from my SCH-I500 using XDA App
If you're hung up on speaker phone go stock. But Pool Party suits all my needs and wants out of a rom.
good day.
Does pool party have the same speakerphone issue?
Sent from my SCH-I500 using XDA App
benfikaman said:
Does pool party have the same speakerphone issue?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I believe all MTD ROMs have this issue.
Ok great I appreciate the help, thanks guys
The search continues, too bad because i really like cm7.1
Sent from my SCH-I500 using XDA App
Just an update, I am currently running powerwashed Rom and for those looking for a daily, this is the way to go, it's excellent, thanks ccampos!
Sent from my SCH-I500 using XDA App
benfikaman said:
Just an update, I am currently running powerwashed Rom and for those looking for a daily, this is the way to go, it's excellent, thanks ccampos!
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Did u try to modify dsp settings on speaker?
Yup i tried everything, seems it's a known issue and can't be fixed until source code is released....
Sent from my SCH-I500 using XDA App
Ya. All Mtd roms have the issue...I brought it up to ssewx in the glitch kernel and he took the job.. He is currently working on Bluetooth echo, speakerphone echo, and 3.5 jack echo.. I believe he has made progress on Bluetooth echo so far.. Don't flock to him with questions off era's as it takes from his coding time, and you will be reminded of the first rule of cm.. NO CTA'S.. But if you like. Go thank the man
Sent from the fascinate that holds the record on antutu benchmark
My girlfriend is addicted to speakerphone (annoying to me) but she also doesn't like the touchwiz interface. Big thumbs up to the devs putting time into fixing this issue, it'll make my life much easier once it's fixed.
So, so far there is no fix for this? Because I just went from Mik Shifted G to CM7 and it is SOOOO much better, but I have to take calls a lot and I literally can't hear the other person at all, so i had to go back to mik. Until theres a fix looks like I'm stuck.
Speakerphone Echo
benfikaman said:
Hi all,
maybe someone can help, i have been using the cyanogenmod 7.1 for the last couple of days and my only bug so far is that whenever im on a call, where im using the speakerphone, the other person complains of hearing themselves, like echoing. I am running cm7.1 with glitch v12 beta, and ed05 radio. Anyone experiencing the same and have a fix? or anyone else running cm7.1 without the issue (please post kernal and radio used)?
i really like the rom and would have to hate to downgrade but i really need the speakerphone. Thanks in advance for any help guys!
Click to expand...
Click to collapse
I'm having the same problem on my AT&T Galaxy S3. Person on other end of line experienced terrible echo when I turn speakerphone on. I don't have the issue on my stock ICS ROM only on the custom JB ROM's I have tried: CM 10 M2, AOKP M1, AOCP newest build etc... I'm assuming all these ROM's share some common code. It's definitely the the case as I have tried taking it off and on with no effect. If you have found a solution., I'm all ears. Thanks!
ladd76 said:
I'm having the same problem on my AT&T Galaxy S3. Person on other end of line experienced terrible echo when I turn speakerphone on. I don't have the issue on my stock ICS ROM only on the custom JB ROM's I have tried: CM 10 M2, AOKP M1, AOCP newest build etc... I'm assuming all these ROM's share some common code. It's definitely the the case as I have tried taking it off and on with no effect. If you have found a solution., I'm all ears. Thanks!
Click to expand...
Click to collapse
This should help
http://forum.xda-developers.com/showthread.php?p=33551613
Actually, a solution has been posted over and over and over again, more than a few times by myself. But, I also know that the forum search tool here doesn't work very well - I personally can't stand using it. Therefore, rather than grumble (much) about having to repeat myself again, here it is.
The speakerphone echo is caused by a combination of too high of a boost in the speakerphone call audio plus too high of a microphone gain in speakerphone mode. Both of these can be adjusted in a few places, but my preferred method is to use the Home Screen -> hit the menu button -> "System Settings" -> "Device Options" -> "In-Call Volume Controls" path.
Once you've got that open, adjust your "Speakerphone Volume" setting down to 1. Some people prefer 0. 2 will almost certainly cause echo. 3 will give you echo with severe distortion and probably melt your eardrums while causing a significant space-time anomaly in your fridge which will immediately consume all your beer, sending it back to 1955. You've been warned.
Next, adjust your speakerphone mic gain down some. I've found that 14 is a good value. Some may prefer slightly more or less. I've found that anything above 19 usually results in an echo. You'll just have to play with this one. If you have it above, say, 25, then you will almost certainly get some echo along with over-modulation, and the kernel will freak out and send an email to your parents and grandparents with your entire collection of nasty sheep porn attached. You've been warned.
Finally, make sure you hit OK, or all these settings will not be applied. They *should* stick after a reboot. Mine do.
I've made a blog post about this so that maybe a Google search will turn up some usable results for you all. Here it is: http://blog.efpophis.net/2012/11/speakerphone-echo-on-samsung-fascinate.html
Sent from my SCH-I500 using xda premium
Oops
hhp_211 said:
This should help
http://forum.xda-developers.com/showthread.php?p=33551613
Actually, a solution has been posted over and over and over again, more than a few times by myself. But, I also know that the forum search tool here doesn't work very well - I personally can't stand using it. Therefore, rather than grumble (much) about having to repeat myself again, here it is.
The speakerphone echo is caused by a combination of too high of a boost in the speakerphone call audio plus too high of a microphone gain in speakerphone mode. Both of these can be adjusted in a few places, but my preferred method is to use the Home Screen -> hit the menu button -> "System Settings" -> "Device Options" -> "In-Call Volume Controls" path.
Once you've got that open, adjust your "Speakerphone Volume" setting down to 1. Some people prefer 0. 2 will almost certainly cause echo. 3 will give you echo with severe distortion and probably melt your eardrums while causing a significant space-time anomaly in your fridge which will immediately consume all your beer, sending it back to 1955. You've been warned.
Next, adjust your speakerphone mic gain down some. I've found that 14 is a good value. Some may prefer slightly more or less. I've found that anything above 19 usually results in an echo. You'll just have to play with this one. If you have it above, say, 25, then you will almost certainly get some echo along with over-modulation, and the kernel will freak out and send an email to your parents and grandparents with your entire collection of nasty sheep porn attached. You've been warned.
Finally, make sure you hit OK, or all these settings will not be applied. They *should* stick after a reboot. Mine do.
I've made a blog post about this so that maybe a Google search will turn up some usable results for you all. Here it is: http://blog.efpophis.net/2012/11/speakerphone-echo-on-samsung-fascinate.html
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Oops my bad... I thought this was an S3 discussion. I appreciate the solution thought. I wish I had those options in my phone so I could alter them. If so I'm not finding them, thanks!
hhp_211 said:
This should help
http://forum.xda-developers.com/showthread.php?p=33551613
Actually, a solution has been posted over and over and over again, more than a few times by myself. But, I also know that the forum search tool here doesn't work very well - I personally can't stand using it. Therefore, rather than grumble (much) about having to repeat myself again, here it is.
The speakerphone echo is caused by a combination of too high of a boost in the speakerphone call audio plus too high of a microphone gain in speakerphone mode. Both of these can be adjusted in a few places, but my preferred method is to use the Home Screen -> hit the menu button -> "System Settings" -> "Device Options" -> "In-Call Volume Controls" path.
Once you've got that open, adjust your "Speakerphone Volume" setting down to 1. Some people prefer 0. 2 will almost certainly cause echo. 3 will give you echo with severe distortion and probably melt your eardrums while causing a significant space-time anomaly in your fridge which will immediately consume all your beer, sending it back to 1955. You've been warned.
Next, adjust your speakerphone mic gain down some. I've found that 14 is a good value. Some may prefer slightly more or less. I've found that anything above 19 usually results in an echo. You'll just have to play with this one. If you have it above, say, 25, then you will almost certainly get some echo along with over-modulation, and the kernel will freak out and send an email to your parents and grandparents with your entire collection of nasty sheep porn attached. You've been warned.
Finally, make sure you hit OK, or all these settings will not be applied. They *should* stick after a reboot. Mine do.
I've made a blog post about this so that maybe a Google search will turn up some usable results for you all. Here it is: http://blog.efpophis.net/2012/11/speakerphone-echo-on-samsung-fascinate.html
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Awesome. Thanks for the helpful information and link. The image in the blog post was helpful so that I knew exactly what settings screen I was looking for. For me, I needed to go to "Settings > [Device] Advanced > [Volume Controls] In-Call Volume Controls". Those settings seem to have done the trick for me.
Thanks again!
Anyone else experiencing the other party complaining of an echo when your using speakerphone? I’ve read that it may be an issue with some cases, so I removed mine and had a few tests with no good results. I’m trying to narrow the problem down to either software or hardware related. I have lightly blown out both microphones and both speakers with compressed air. running uclf6 flapjaxxx latest update
simbill said:
Anyone else experiencing the other party complaining of an echo when your using speakerphone? I’ve read that it may be an issue with some cases, so I removed mine and had a few tests with no good results. I’m trying to narrow the problem down to either software or hardware related. I have lightly blown out both microphones and both speakers with compressed air. running uclf6 flapjaxxx latest update
Click to expand...
Click to collapse
I'm having the same issue with the 2.9b update. I'm currently look as well. if I find the issue, I'll post it here. Thanks.
joey30 said:
I'm having the same issue with the 2.9b update. I'm currently look as well. if I find the issue, I'll post it here. Thanks.
Click to expand...
Click to collapse
I have the same problem - Revolt ROM. Any progress?
I have tried two roms now (ReVolt, SlimBeam), and BOTH are producing the 'echo' issue on speakerphone. Does anyone have a handle on this or can they point me in the right direction to fix? Search has not been helpful so far.
Thanks!
The last ROM I ran that didn't have the speaker phone echo was the JamieD81 SlimBean 20130420 build. I believe there were some changes in the CM10.1 code that all the devs for aocp and aokp ROMs use that is causing this. That's just my guess though, I'm only a user not a developer. The only way I've found to get around the problem is to plug in my ear buds when I use speaker phone.
Speaker Phone Echo
Really now said:
The last ROM I ran that didn't have the speaker phone echo was the JamieD81 SlimBean 20130420 build. I believe there were some changes in the CM10.1 code that all the devs for aocp and aokp ROMs use that is causing this. That's just my guess though, I'm only a user not a developer. The only way I've found to get around the problem is to plug in my ear buds when I use speaker phone.
Click to expand...
Click to collapse
Yes I have noticed it on all of the CM10.1 based roms Collective, Pandroid, but on BlackStar no issue.
You're right about the Black Star ROM. It's built from the new 4.1.2 Samsung release and not on the CM 10.1 base. I did downgrade to the official Samsung release and didn't have echo nor on a debloated and deodexed version of it although it wasn't Black Star. And while I appreciate that we finally got an official release they were a little late to the party as far as I'm concerned. I'll take the occasional bugs in the CM 10.1 variants along with the speaker phone echo. Looking back to when we first got JB last summer the devs have made tremendous improvements and brought us options and customizations that the stock ROMs will never have.