Develop Bugs

[Q] S3 Speakerphone Echo Bug

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.

[Q] CM10 on Bell Galaxy S III (d2att)

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

[Q] 4.2 Bluetooth issues still present?

I've been ignoring custom roms for about 6 months after I tried one previously and found the bluetooth bug. Just curious if this has found a fix at this point? I'd love to run a CM10.1 rom, but bluetooth audio is a must have for me.

cegna09 said:
I've been ignoring custom roms for about 6 months after I tried one previously and found the bluetooth bug. Just curious if this has found a fix at this point? I'd love to run a CM10.1 rom, but bluetooth audio is a must have for me.
Click to expand...
Click to collapse
the issues from 6 months ago have been gone for sometime now.

fantastic, thank you.
Life's been pretty crazy so i'm out of the loop on where everything has progressed. Once i get AT&T to warranty my phone for the GPS issues i'm having i'll try out one of the new builds.

Bluetooth audio has been working fine
But from my experience there have been problems with Bluetooth dialing.
A recent update of slimbean (version 6) seems to have corrected the problem.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I don't know that the issue really is fixed in 4.2.2. Doesn't seem to matter what ROM I run (I've tried CM, Carbon, AOKP), I can't get Bluetooth to work at all. It won't scan/find any of my devices or even turn on. I've resorted going back to stock rooted.
Has anyone found a work around or fix?

If bluetooth worked, it wont be 4.2.2. Best to go back to 4.1.x.
Sent from my SAMSUNG-SGH-I747 using xda premium

kt314 said:
I don't know that the issue really is fixed in 4.2.2. Doesn't seem to matter what ROM I run (I've tried CM, Carbon, AOKP), I can't get Bluetooth to work at all. It won't scan/find any of my devices or even turn on. I've resorted going back to stock rooted.
Has anyone found a work around or fix?
Click to expand...
Click to collapse
once in the past, when the CM roms were having bluetooth problems, I tried a different kernel and that fixed issues. The BMS Kernel is pretty stable and great performance/battery. you might give that a try.

[Q] Android 4.4 Roms on Galaxy Note II Causing Headphone Audio Problems

Android 4.4 Roms on my Galaxy Note II have been causing headphone audio problems. Otherwise audio works fine, as with any other non 4.4 rom. Has this been happening to anyone else, and if so, does anyone have a solution? =/ Been looking forward to 4.4 for monthes, this is just so disappointing.

bump

Try viber4android on the play store. Works great.
Sent from my SGH-T889 using XDA Premium 4 mobile app

ShogoX000 said:
Android 4.4 Roms on my Galaxy Note II have been causing headphone audio problems. Otherwise audio works fine, as with any other non 4.4 rom. Has this been happening to anyone else, and if so, does anyone have a solution? =/ Been looking forward to 4.4 for monthes, this is just so disappointing.
Click to expand...
Click to collapse
What type of problems are you having. There's a general low audio volume on the 4.4 roms but other than that there's no issues with audio for me. I'm running omnirom 4.4.2

Explanation
It's strange. Once I have it installed, I have sound without headphones. However if i plug in the headphones, I do not get any sound. It sort of goes out after a certain point and doesn't come back unless I take out headphones again and play sound THEN plug in headphones.

Just tried viper4android and it keeps asking me to verify if its rooted -.-.

I get random sounds like the pop sound when I hit a group folder, but only get sound otherwise on apps if i take headphone out, press play or whatever, then plug headphone in

ShogoX000 said:
It's strange. Once I have it installed, I have sound without headphones. However if i plug in the headphones, I do not get any sound. It sort of goes out after a certain point and doesn't come back unless I take out headphones again and play sound THEN plug in headphones.
Click to expand...
Click to collapse
I had the same problem for the longest time. If you move from anything pre 4.4 to 4.4 you get that effect. I have solved the problem by doing a full factory reset, cache wipe, dalvik wipe, and the secret is wiping internal storage as well but I also wipe system but I'm fairly certain it has to do with internal storage but I wipe all of those to be sure and it fixes the problem. Hope this helps! I use twrp so I can't confirm it works with cwm or philz

Thank you so much dadudeguy44. It's worth a try, will have to figure it out since I'm still relatively new to rooting
Sent from my SGH-T889 using Tapatalk

ShogoX000 said:
Thank you so much dadudeguy44. It's worth a try, will have to figure it out since I'm still relatively new to rooting
Sent from my SGH-T889 using Tapatalk
Click to expand...
Click to collapse
I'm not sure what the problem is. I was on a ROM, updated to the next version of that ROM and the problem came back. I wiped everything but systen and reflashed and problem came back then wiped everything including system and reflashed and problem solved so it has to do with system. Side note wiping system on my cwm will wipe EVERYTHING including your external sd and all the data on your phone. I learned the hard way but I think I was on an older version of cwm. I have used twrp ever since. Let me know how it works out for ya

I thought id take your advice and try twrm but when I tried to install through goomanager I still end up booting into cwm. Any idea why that might be hapoening ?
Sent from my SGH-T889 using Tapatalk

Urgent and Serious issue with audio! HELP needed. please!

Guys, I have this one major issue with audio in my phone and its the rarest of the problems! The whole audio output stops completely. By completely, i mean even the receiver sound. completely dumb! cant hear anything if someone calls me. This has been occurring since a month or so. I am running on Cyanogenmod 11 M8. Even if i restart the phone its stays the same way. And all of sudden, randomly, the audio back again, working properly. when it goes dumb it stays like that for 5 6 hours. it happens quite often. this is throwing me off totally.
Device : Galaxy S3 SGH i747 - At&t
This problem happens:
1) when i am on call, suddenly it goes mute.
2) when the phone is kept idle for more than 3 4 hrs. So every morning its dumb when i wake up.
These are what I've tried and what I've found out:
1) I reverted back to stock 4.3 to check if its the problem with audio hardware. But in stock it worked perfectly and flawlessly. no issues there. SO its definitely got to do with cyanogenmod.
2) I flashed ktoonsez kernel on CM 11 M8, to check if its kernel problem. But its happening again. SO its not the problem with kernel.
3) I recently found out that if I wipe the cache from recovery, audio is back working. SO its definitely something in the cache thats messing with the audio. Some app may be.
this thread can be referred for more details on this issue:
http://forum.cyanogenmod.org/topic/81373-audio-stops-working-from-time-to-time/
and I dont know what else to do now. Ive tried uninstalling all the apps that access audio. But the problem still persists.
I really really need help fixing this one. PLEASE HELP.

s.vivekananda007 said:
Guys, I have this one major issue with audio in my phone and its the rarest of the problems! The whole audio output stops completely. By completely, i mean even the receiver sound. completely dumb! cant hear anything if someone calls me. This has been occurring since a month or so. I am running on Cyanogenmod 11 M8. Even if i restart the phone its stays the same way. And all of sudden, randomly, the audio back again, working properly. when it goes dumb it stays like that for 5 6 hours. it happens quite often. this is throwing me off totally.
Device : Galaxy S3 SGH i747 - At&t
This problem happens:
1) when i am on call, suddenly it goes mute.
2) when the phone is kept idle for more than 3 4 hrs. So every morning its dumb when i wake up.
These are what I've tried and what I've found out:
1) I reverted back to stock 4.3 to check if its the problem with audio hardware. But in stock it worked perfectly and flawlessly. no issues there. SO its definitely got to do with cyanogenmod.
2) I flashed ktoonsez kernel on CM 11 M8, to check if its kernel problem. But its happening again. SO its not the problem with kernel.
3) I recently found out that if I wipe the cache from recovery, audio is back working. SO its definitely something in the cache thats messing with the audio. Some app may be.
and I dont know what else to do now. Ive tried uninstalling all the apps that access audio. But the problem still persists.
I really really need help fixing this one. PLEASE HELP.
Click to expand...
Click to collapse
I've had that issue a month or two ago but haven't seen it on the latest ROMs. I'm not sure what causes it but I would suggest you flash another ROM if CM messes up with your sound (or another version of CM).

BWolf56 said:
I've had that issue a month or two ago but haven't seen it on the latest ROMs. I'm not sure what causes it but I would suggest you flash another ROM if CM messes up with your sound (or another version of CM).
Click to expand...
Click to collapse
Hi, Thanks for the response. I personally like CM and the extent of customization it offers. I actually dont mind switching cuz sound is bigger deal. Would you mind suggesting ROMs that are similar or comes closer to CM and also good at the same time? which ROM are you on?

s.vivekananda007 said:
Hi, Thanks for the response. I personally like CM and the extent of customization it offers. I actually dont mind switching cuz sound is bigger deal. Would you mind suggesting ROMs that are similar or comes closer to CM and also good at the same time? which ROM are you on?
Click to expand...
Click to collapse
I don't suggest ROM to avoid flaming but you can look in my sig

BWolf56 said:
I don't suggest ROM to avoid flaming but you can look in my sig
Click to expand...
Click to collapse
Hey it got fixed in the latest nightly ( cm-11-20140721-NIGHTLY ). I had put it in cyanogenmod forum, I guess they read the issue and fixed it. Audio is perfectly fine now! Feels so great to use cyanogenmod again.
Thank you cyanogenmod!

I have this issue too but it doesn't have to do with the audio disappearing; it's simply gone from the get-go after clean flashing a ROM.
As you've said, stock FW and ROM works fine, but anything custom will just totally break it. Seems to be a very isolated issue with the phone itself, I've searched all over for people with the same problem but could never find anything.

gsm22 said:
I have this issue too but it doesn't have to do with the audio disappearing; it's simply gone from the get-go after clean flashing a ROM.
As you've said, stock FW and ROM works fine, but anything custom will just totally break it. Seems to be a very isolated issue with the phone itself, I've searched all over for people with the same problem but could never find anything.
Click to expand...
Click to collapse
Oh. It used to happen to me once or twice. No audio when I install CM, after it boots the first time. I think you should check the new nightly of 7/23. Looks like its fixed. They've fixed a number of audio issues over the last few nightlies. And I've always preferred CM over any other roms, so I've no idea about why it isn't working on other roms.

s.vivekananda007 said:
Oh. It used to happen to me once or twice. No audio when I install CM, after it boots the first time. I think you should check the new nightly of 7/23. Looks like its fixed. They've fixed a number of audio issues over the last few nightlies. And I've always preferred CM over any other roms, so I've no idea about why it isn't working on other roms.
Click to expand...
Click to collapse
Thanks for the suggestion, I may as well give it a try since most everything else I've tried has had the same issue.
edit:
Clean flashed latest CM nightly, sound worked for around 2 minutes, then stopped when I plugged headphones in. Rebooted, got it to work via speakers again but then DSP manager force closed and left me without sound.
Rebooted into recovery, cleared cache, still no dice.
Going to try another clean flash to see if I can get sound to last a while longer.
edit 2: It seems to be screwed completely now, no sound after install + reboot.
Same logcat lines as in http://forum.xda-developers.com/galaxy-s3-att/help/audio-wide-custom-roms-t2825135