Greetings,
First post here, I hope this is the appropriate section for it. I have google'd and forum searched extensively and have yet to find a thread dedicated soley to this issue. Many people have reported it within various ROM threads only to have the next poster state he doesn't have the issue and the problem get buried in a 500 page thread.
Having gotten my feet wet with the stock ICS ROM that came with my Galaxy S3, I was happy to enter the world of custom ROM's and flashed CM 10 M2 as my first custom ROM. I was very much enjoying CM 10 when I received my first phone call after switching. Being an exclusive speakerphone user, I answered the call and enabled the speakerphone as usual. The caller stated they couldn't understand me as there was an echo on the line. I turned speakerphone off and they stated the problem was fixed. After finishing the call, I called my cell phone from my landline and enabled the speakerphone on my S3, then walked to the other side of the house to minimize any close vicinity interference. When I spoke into my landline I could hear myself echo making a conversation almost impossible. I disabled the speakerphone on my S3 and the problem went away.
I restored my stock ICS ROM and was unable to duplicate the problem. I assumed the bug was specific to CM 10 and tried AOKP JB milestone 1 and had the same issue. Today I tried Task and Ktoonsez's latest AOKP JB 4.12 ROM and The Collective's AOCP ROM with the same results. All the problem ROM's were JB builds so perhaps it's a JB related issue. I will be trying a touchwiz based JB ROM next to see if I still have the issue.
I think alot of people assume when they read this bug report they blow it off as they can't actually hear the echo unless the person on the other line reports it. Maybe alot of people don't use speakerphone? I don't think it's a universal problem or more people would be reporting this but it's not intermittent either. I can reproduce it 100 percent of the time and it goes away when I recover to stock. I also removed my case when testing this and it had no effect. If there is a workaround or fix for this I would be very thankful to learn of it as I very much enjoyed the custom ROM's but I just can't give up speakerphone. Thanks in advance! :fingers-crossed:
I'm having the same issue...
+1
Follow up
kenrothman said:
I'm having the same issue...
+1
Click to expand...
Click to collapse
So today I tried newest builds of Parandoid Android, and Liquid Smooth with the same result. Pretty much all the popular ROM's in the "AT&T Galaxy S III Original Android Development" contain this bug, I'm assuming because they share alot of code. Seems like they base alot of work off of Cyanogen Mod so perhaps that's where it lies, I don't know.
What I do know is I installed DrewGaren's Jellybean 747 Milestone 7 ROM which is Touchwiz based and the speakerphone echo went away. So my stock ICS ROM and this one do not contain the issue but every other JB based ROM I have tried does. I don't have the knowledge to troubleshoot this issue I just wanted to share what I've found and hopefully someone with the knowledge can help track it down.
I do prefer the CM 10 style ROM's over the stock experience but I can't live without speakerphone so hopefully this issue gets resolved, thanks for listening!
I have the problem too. I bought my S3 3 weeks ago and within a few days rooted it and installed the latest CM10 nightly. The first time I used the speakerphone I became aware of the echo problem with the it. So I switched back to the stock rom and the problem was gone, so I knew it wasn't a hardware problem with my phone. I've tried every nightly CM10 rom including the recently released stable build. I also tried the latest official AOKP as well as Task and Koonsez's latest build and they all produce the echo.
My buddy suggested I try the black jelly rom, and that's the only one I've been able to use that doesn't have any echo, but it's a touchwiz/Samsung based build. It's not bad, but it doesn't support wifi tethering and it's not as smooth as CM or AOKP. I really want to run CM but can't live without speakerphone.
On a side note, I rooted and rom'd my wife's and friends S3 the exact same way as mine and neither of theirs have the speakerphone echo problem. I suspect there are some hardware differences with Samsung phones. Maybe different parts suppliers that aren't playing properly with the drivers in the CM10 build.
From my tests this bug sounds like the mic is turned up max when speakerphone is on so it's super sensitive. Also, the volume level doesn't have any effect on the speakerphone volume whether you raise or lower it.
Really hope the dev's can fix this so I can run CM or AOKP once and for all.
On a final note, my phone is blue, while both my wife's and my buddy's are white. I don't want to conclude that the white phones don't have the speakerphone echo problem with CM roms. Hope it's just a coincidence.
for cm10 there is an official bug ticket for it here : https://code.google.com/p/cyanogenm...on Model Network Owner Summary Stars Priority
Randomacts said:
for cm10 there is an official bug ticket for it here : https://code.google.com/p/cyanogenm...on Model Network Owner Summary Stars Priority
Click to expand...
Click to collapse
thanks for pointing that out. looks like it's not really a popular issue, or popular enough to get them focussed on fixing it
anyone have any thoughts as to why identical phones don't behave the same, ie some S3's have the echo and some don't? I have 3 days left (30 day purchase return policy) to exchange my phone, and am contemplating getting it swapped to see if I get lucky with another unit which won't have an echo problem running CM10 or AOKP.
gots54 said:
thanks for pointing that out. looks like it's not really a popular issue, or popular enough to get them focussed on fixing it
anyone have any thoughts as to why identical phones don't behave the same, ie some S3's have the echo and some don't? I have 3 days left (30 day purchase return policy) to exchange my phone, and am contemplating getting it swapped to see if I get lucky with another unit which won't have an echo problem running CM10 or AOKP.
Click to expand...
Click to collapse
Hi, just wondering if anyone has found a fix for this or any other AOSP JB Roms that has the speakerphone echo fixed?
ladd76 said:
Greetings,
First post here, I hope this is the appropriate section for it. I have google'd and forum searched extensively and have yet to find a thread dedicated soley to this issue. Many people have reported it within various ROM threads only to have the next poster state he doesn't have the issue and the problem get buried in a 500 page thread.
Having gotten my feet wet with the stock ICS ROM that came with my Galaxy S3, I was happy to enter the world of custom ROM's and flashed CM 10 M2 as my first custom ROM. I was very much enjoying CM 10 when I received my first phone call after switching. Being an exclusive speakerphone user, I answered the call and enabled the speakerphone as usual. The caller stated they couldn't understand me as there was an echo on the line. I turned speakerphone off and they stated the problem was fixed. After finishing the call, I called my cell phone from my landline and enabled the speakerphone on my S3, then walked to the other side of the house to minimize any close vicinity interference. When I spoke into my landline I could hear myself echo making a conversation almost impossible. I disabled the speakerphone on my S3 and the problem went away.
I restored my stock ICS ROM and was unable to duplicate the problem. I assumed the bug was specific to CM 10 and tried AOKP JB milestone 1 and had the same issue. Today I tried Task and Ktoonsez's latest AOKP JB 4.12 ROM and The Collective's AOCP ROM with the same results. All the problem ROM's were JB builds so perhaps it's a JB related issue. I will be trying a touchwiz based JB ROM next to see if I still have the issue.
I think alot of people assume when they read this bug report they blow it off as they can't actually hear the echo unless the person on the other line reports it. Maybe alot of people don't use speakerphone? I don't think it's a universal problem or more people would be reporting this but it's not intermittent either. I can reproduce it 100 percent of the time and it goes away when I recover to stock. I also removed my case when testing this and it had no effect. If there is a workaround or fix for this I would be very thankful to learn of it as I very much enjoyed the custom ROM's but I just can't give up speakerphone. Thanks in advance! :fingers-crossed:
Click to expand...
Click to collapse
+1
speakerphone echo
I also have this problem. using baked 8. with kt747 and its awesome!! They seem to be aware and working on it. tried a different kernel but no dice. Ive been in every setting cant seem to get rid of it. my phone is white so its not that. hope someone can figure this out soon. tw roms dont have this problem and I like the aosp feel.It would be nice to know if anyone even an idea of the cause, maybe the users could check files and find something.
I confirm that I LOVE these ROMs, but absolutely need a working speakerphone too.
Some other thread said something about changing the radio to ULVA3 or something like that... not sure if anyone had any luck with that.
Anyways, thought I'd break my lurked tendencies and post for my 1st time here.
Love my GS3!
So I've been very happily using the Samsung-based ROM called Devils Reject since Dec 2012, and have been on V7 since it came out a few months ago and have been really happy with it. It's pretty smooth and stable, has great battery life, has tethering, custom toggles, various battery icons, AOKP lockscreen, power button menus, plus a bunch of other stuff I can't remember, and of course, there are no speakerphone problems.
But I've always been curious about giving CM another chance with CM10.1 and especially with the latest RC2 out.
Does anyone know if the speakerphone bug still exists with it?
speakerphone echo bug in CM10.1 RC2 for quincyatt
gots54 said:
So I've been very happily using the Samsung-based ROM called Devils Reject since Dec 2012, and have been on V7 since it came out a few months ago and have been really happy with it. It's pretty smooth and stable, has great battery life, has tethering, custom toggles, various battery icons, AOKP lockscreen, power button menus, plus a bunch of other stuff I can't remember, and of course, there are no speakerphone problems.
But I've always been curious about giving CM another chance with CM10.1 and especially with the latest RC2 out.
Does anyone know if the speakerphone bug still exists with it?
Click to expand...
Click to collapse
I have the speakerphone echo bug on my Samsung Galaxy Note with CM10.1 RC2. This has happening on earlier versions as well, but I thought a reset/wipe fresh install would fix it. Would like to stay on CM10.1 but I really depend on my speakerphone.
Related
I've seen several threads about the problem of the call issues, When first the call echo now the bad quality sound on CM and MIUI..
Devs I love your roms. they are amazing and I know that you all probably had tried to solve the call issue once it for all. Even though you make magic to the call issues, it still not gone completely.
There might be other users like me that love roms. special if we want to run JB or MIUI or any other than Stock TW. but the call issues are taking us from using these amazing roms..
I personal am so jealous because I love to use miui on my phone or JB but everytime I do my wife calls me and boom I have to flash back to stock TW because of these issues. I think you all know that people you are talking to is the ones who cant hear you or have an echo...
Now some say the that problem is hardware some say its drivers I dont know what it is and I'm sure you ''DEVS'' know what it is causing it.
My question here is wether we are gonna get rid of this issue once it for all or are we close to it or there is nothing to do.
I know Eugene have done wonderful on getting it fix but although in my end the issue still comes...
P.S some say that problem is on one of the mics ''top one to be exactly'' is there a way to just shut it off,
Then again Im not trying to flame anybody this is something that just gets on my nerves. Now if you have some sarcasm to say keep it to your self Xda for me is like a family. and we all try to help each other
If someone knew how to fix it, don't you think it'd be fixed?
Sent from my SGH-T989 using xda premium
born2gethard said:
If someone knew how to fix it, don't you think it'd be fixed?
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
That's what I was thinking
just like any variant in the Galaxy S Line. There is no sure fire fix, because these roms are built off the SGSII and ported (officially/unofficially) to our's and other variants. the T-Mobile SGS 1 had the same microphone issues. These are driver related and won't be properly fixed without Device source information related the OS in question.
the easiest "temp" fix is to mute/unmute after recieving a phone call. This will generally fix the issue for the duration of that phone call.
for future reference though if your gonna go samsung, and plan on being a rom flasher, I would suggest you invest in an International Device as they recieve updates quicker, and tend to have there sources available (which means smoother more stable roms)
even the SGSIII is going to run into issues due to the chipset variation from the world version (dual core vs quad core)
on that note though, now that 4.0.4 has been officially released for the Hercules, we should see Small issues like this addressed in the aosp 4.0.4 for our device.
I see you showed interest in Jellybean, i'll be frank on this. Unless we get JB officially from samsung for our SGSII there will never be a "perfect" fix to the microphone issue. (maybe a possibility if the skyrocket were to get JB or even the Sprint Variant) but the 4'3 inch SGSII is seperate hardware therefore drivers aren't compatible.
If you are referring to ICS, the call quality issues were resolved long ago.
If you are using JB AOKP / CM, make sure you have enabled noise suppression within your call settings. Go to your dialer, hit the menu button and scroll down to noise suppression.
With that being said, I have no problems with call quality using the latest AOKP JB ROMs though YRMV.
Rod3 said:
If you are referring to ICS, the call quality issues were resolved long ago.
If you are using JB AOKP / CM, make sure you have enabled noise suppression within your call settings. Go to your dialer, hit the menu button and scroll down to noise suppression.
With that being said, I have no problems with call quality using the latest AOKP JB ROMs though YRMV.
Click to expand...
Click to collapse
ICS hasnt been fixed all the way.. The issue are still on Miui and CM9 although it is better but not gone completely.
I even been having problems where I have to speak louder so the other person can hear me on stock rom, also I noticed that every now and then this issue comes on ICS Miui. sometimes I have to hung up and call back.
I know CM10 has been made "stable" on this device but I just have a few questions regarding it. My wife has been using the nightlies since the first previews were available and I'm not sure if our issues are common or something I am doing wrong.
She is currently on a nightly from a few days ago but these issues have persisted for about a month. I have done a full wipe and flash multiple times and we still have the same issues.
Skype: She can't barely here the other user and the other user hears nothing but static. I have tested with multiple other users. I have wiped data for Skype and reinstalled it, still has the same issue.
Force Close - Many apps. Happens randomly and it's not the same apps every time. I feel it is an OS issue and not an app issue.
Speakerphone is randomly activated by default. She usually has to tap the mic button a few times (deactivate, reactivate, deactivate) in order to get it switched to the handset.
Depending on what nightly she flashes the caller on the other end gets echo. It hasn't been happening with recent flashes but every couple weeks it pops up again for a nightly and then disappears.
I understand there are many issues due to Samsung not releasing sources, etc, just want to verify I am not alone. I have looked through the forums and see some people have some of the issues from time to time but I am hoping for some verification.
Thanks for everything.
I noticed the same thing a few days ago on Skype but didn't think much of it at the time.
Just checked again and sure enough I'm having the same experience you are with static.
Flashed back to stock and the problem disappears.
Must be a problem with CM10.
Ever try flashing the Stable version? Or a different rom for that matter? Maybe AOKP?
The issue existed before Stable and it exists in Stable. I just tried [ROM] AOKP(Jellybean 4.1.2)Task & Ktoonsez (11/18) and the issue with Skype exists there as well. If anybody knows of a AOKP or CM build that doesn't have any issues I would swap over. I have been wiping and flashing roms like crazy lately and I we really can't stand stock samsung rom. I may end up selling the phone and picking up something different, it's quite frustrating. Last time I buy a Samsung phone, that's for sure. They basically **** on devs.
DarthDerron said:
Ever try flashing the Stable version? Or a different rom for that matter? Maybe AOKP?
Click to expand...
Click to collapse
I see you have the same phone as my wife. Any chance you have time to test Skype on your current rom? If so thanks in advance, I appreciate it.
Sent from my LG-E973 using xda app-developers app
Thanks guys. Just going to return her to stock and sell it. Going to find a device with better support from manufacturer.
Sent from my LG-E973 using xda premium
after flashing the blazer v2.1 on my sprint galaxy s3 i now have an echo while in calls. I test it by calling my voicemail, but its also evident while talking to people, it sounds like im in a tunnel and repeating myself. Does anyone know of a fix for this? I've reverted back to my nandroid backup and it does not echo, so i know its not just the root.
anyone?
I'm not familiar with running blazer roms. Thisbisba stretch by trying changing kernels and see if that works. Or do an update in your phone settings and see if that changes anything. I could be wrong but its worth a shot.
Sent From My Samsung Galaxy S3 from far far away...
I have had it with several roms. My sons use dumbphones and get the same thing sometimes. Network issue more than likely
Living my life's not hard enough,
Burn me alive inside
I've had the same problem on different AOSP ROMs, like the Paranoid Android port. Trying to figure out what gives!
I don't notice it until the caller asks me if I'm on speakerphone or something, because they keep hearing their own words echoed back to them. It's very distracting to them!
Is anyone else experiencing this? I went from stock, to rooting with the tool kit. I have twrp recovery. First I flashed frosty jelly bean, then I tried domination because I thought it was the ROM. Whats happening is, when I make a call the first ring sounds like a choppy ring like it is not a good connection, then that little tune that plays(the connection sound I guess) is delayed until after the first ring. Normally I would hear that little tune first, then it would start ringing. When the other person picks up on the other end, they can barely hear me. They have said I sound far away or I sound like darth vator lol. They keep saying "what, what", everytime I say something. This does not happen every call though. I immediately thought it was frosty jelly bean, so I flashed Denomination instead, but same call issue. Another problem im having with Denomination is: I read on the forum a little bit that some people when switching from 4.2. to 4.1. their gps wasnt working. I guess thats besides the point since I didnt flash any 4.2 Roms yet, but with my gps problem, its a little different. When I turn on google maps, originally without gps enabled it was able to pick up my location using mobile networks or wifi (yes they are turned on). It does in fact locate when gps is on. What do you guys think about these 2 problems?
Have you tried changing the Kernel? I have had the odd call sound issues on certain combinations of kernels and roms.
jcbofkc said:
Have you tried changing the Kernel? I have had the odd call sound issues on certain combinations of kernels and roms.
Click to expand...
Click to collapse
No. Whatever Kernel that it comes with I guess. Are you talking about in the aroma installer, it asks you if you want aggressive, optimal, extreme RAM free, etc? Are those the different kernels? If not, what are those options?
So I have a CM 10.2 on my T989 Hercules for a while, and since couple of days every time I pickup the call or try to call back I can't hear jack sh*t unless I reboot the phone. Is this something that can be fixed or should I be looking for a new ROM ? There is so many of them I'm getting confused :silly:
i have this issue as well, but i am using pa 4.6 beta 1. any fix to this?
same problem here on mine and my girlfriends phones (Hercules) on either CM10.2 or PA 4.6 beta. restarting didn't help for the CM but did on the PA rom. only thing is, I don't know whats causing it. my phone could ring and when I answer I hear nothing and they don't hear me and vice versa when I call out. yes, both were clean installs on both phones with double wipes before flash with either roms.
Same Issue!
I am actually getting the same exact issue, at times I cannot hear anything on either end and the only remedy is to reboot and it only fixes it for a little bit.
Anyone know anything about this?
I've no issue with PA 4.5 Beta 1 (most stable in my case) nor 4.4 Final. Ran into the same issue with 4.5 Beta 4 once tonight but I was playing with disabling google play services and install the new Hangout.
I am curious too...anybody have a working solution yet?
I feel I've run into this problem before on jb. I'm curious to know which BASEBAND in installed on your devices.
I think there is a newer radio (modem) needed for jellybean and odd sound/wifi/data issues arise if you're using an older radio.
I'm using UVMC6 on CM11.
http://direct.xda-developers.com/wiki/Samsung_Galaxy_S_II/SGH-T989/Radios
I just flashed CM11 ROM from Sultanxda on my 2 T989's I have. One is having this issue the other is not. They were purchased at the same time. Not sure why this is happening. I have also had this issue on the previous CM10.2 version.
I have updated the Radio on the one that didn't work, but alas it still does not fix it. If the phone is rebooted, it magically works for a while.
I'm hoping that @Sultanxda will have a look at this issue.