Develop Bugs

[Q] HTC Desire, speakerphone turns on automatically

Hello,
I have HTC Desire (rooted), the ROM is stock.
Some week ago, I've noticed that sometimes, when I start the call or when I'm called - the speakerphone is on and I need to switch it off if I don't want that all people around me hear my conversation.
At first, this was happening quite occasionally. As the time goes by, it's happening randomly but more often.
I have tried to factory reset my phone, but the problem still exists - no improvement!
Also tried to uncheck car dock auto launch, although I'm not using any dock so it would be strange that dock mode would be activating.
No success whatever I've tried so far
Please is there some idea what could be causing that speakerphone issue?
Thanks,
Denis

You could try flashing a new rom. Besides fixing the issues, the stock-based roms in the dev section run better, and support init.d scripts.

abaaaabbbb63 said:
You could try flashing a new rom. Besides fixing the issues, the stock-based roms in the dev section run better, and support init.d scripts.
Click to expand...
Click to collapse
Thanks, I need some time to decide on moving to the new ROM but this one (MildWild CM-5.0) looks exactly as what I need. Are you aware of any shortcomings related to MildWild CM-5.0 (for instance GPS, sync, anything..)?
What stays quite confusing to me is that even after I did hard reset (wiped all and installed from scratch), the issue with speakerphone is still there. Looks almost like some hardware issue, is that possible?

denisdb said:
Thanks, I need some time to decide on moving to the new ROM but this one (MildWild CM-5.0) looks exactly as what I need. Are you aware of any shortcomings related to MildWild CM-5.0 (for instance GPS, sync, anything..)?
What stays quite confusing to me is that even after I did hard reset (wiped all and installed from scratch), the issue with speakerphone is still there. Looks almost like some hardware issue, is that possible?
Click to expand...
Click to collapse
Mildwild is the perfect balance between performance, looks and battery life. It's one of the best ROM's in this section.
Hard reset only deletes your data. It doesn't restore your system partition. That's where the problem is.

[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.

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

Microphone issues with smp600 --ROM or hardware related?

Been running Temasek ROMs for a while now. Just noticed lately that the mic no longer seems to be working. Could this at all be ROM related, or is more likely a disconnected mic? Anyone else have similar issues other than the one that I did find on this forum? BTW Is Temasek still working on these for the smp 60x's? IIRC there was a blurb that he quit. Sure hope not, I always appreciate his work that he does provide. ;-Deano

Hello.
I got some issues too, using skype the mic starts to blurring to the point it is unusable, but removing and re-inserting the p2 cable fix it for a while. I can't tell if it is related to the aosp/cm roms but after getting the Official debloated 5.1.1 roms it no longer happened to me in Both p600 and p601 roms.

DeanoD said:
Been running Temasek ROMs for a while now. Just noticed lately that the mic no longer seems to be working. Could this at all be ROM related, or is more likely a disconnected mic? Anyone else have similar issues other than the one that I did find on this forum? BTW Is Temasek still working on these for the smp 60x's? IIRC there was a blurb that he quit. Sure hope not, I always appreciate his work that he does provide. ;-Deano
Click to expand...
Click to collapse
I had the same problem on mine and it was ROM related, not hardware. Oddly, Temseks unofficial cm 12.1 build was the only lollipop ROM that the mic DID work on. When I first noticed the problem after updating to lollipop I flashed several different ROMs and found that the mic didn't seem to work on anything but Temseks unofficial 12.1 build. I usemy mic regularly so I stuck to Temseks build (which is otherwise a great ROM too). I recently updated to Temseks cm 13 build and my mic is still working perfectly. So I suggest trying a few different ROMs before condemning the mic itself. Perhaps try a kit kat based ROM like hyperdrive just to check functionality of the mic. My mic worked with that ROM as well.

Sound crackling and distortion on the galaxy A5 (2017)

Hi. I'm kinda new to xda forums.
When I stream music via youtube, soudcloud, drive, spotify (you got it), the sound is completely ok.
When I play an mp3 however, the sound is distorted.
My AOSP rom is based of lineageos, so I tried my best deleting audiofx via debloat (magisk module) and deleting audio_effects.conf and soundeffects in /system/vendor/lib, yet the problem persists. I'm completely lost.
If anybody knows about this issue or how to fix it, help is appreciated. Thank you!
If you need a logcat, gtfo or anything, I'll be available.

is this your 1st experience with kind of aosp rom?
that's normal.. and that's why i back to stock
nothing can fix this problem. even with viper4android. but neither for stock rom.

leo31 said:
is this your 1st experience with kind of aosp rom?
that's normal.. and that's why i back to stock
nothing can fix this problem. even with viper4android. but neither for stock rom.
Click to expand...
Click to collapse
But is has to be. I used AOSP on a s3 mini and htc one. Both didn't had this issue. Only this one had.

Try disabling google now or whatever that was, you should check the official LoS thread, also i dont reccomed using aosp roms on this phone since HWC is broken so the battery is very poor

CoinKiller said:
Try disabling google now or whatever that was, you should check the official LoS thread, also i dont reccomed using aosp roms on this phone since HWC is broken so the battery is very poor
Click to expand...
Click to collapse
1. About the battery, that is certainly not true. Battery life is greater than expected. If you think about an older phone, then I would agree, but here, even fast charging works (even though it constantly says slow charging, I think that's just a minor bug). In short, no need to complain.
2. What do you mean google now? I think that's dead since 2017. Are you bringing me back to 2015? Nowadays, it's just called my feed, and there is no way disabling it, heck, what is even doing with audio? If you are referring to google assistant, I used it on my previous AOSP phone and nothing happens.
3. Unfortunately there is no talk regarding about the audio in the custom rom forums.
Sorry for being rough and negative, I just want to clarify :victory:. Please don't be mad at me.
The known bugs on my experience are:
Casting
Missing libgdx.so
Sometimes advanced restart does not work
Audio crackling
Keeps telling slow charging
No internet at OTA update (when I actually have)
Some are minor, others are frustrating. Thanks for your reply.

Check google app settings and disable ok google now
Also battery life was trash when i installed the rom for myself

TechGuyOnTechIT said:
1. About the battery, that is certainly not true. Battery life is greater than expected. If you think about an older phone, then I would agree, but here, even fast charging works (even though it constantly says slow charging, I think that's just a minor bug). In short, no need to complain.
2. What do you mean google now? I think that's dead since 2017. Are you bringing me back to 2015? Nowadays, it's just called my feed, and there is no way disabling it, heck, what is even doing with audio? If you are referring to google assistant, I used it on my previous AOSP phone and nothing happens.
3. Unfortunately there is no talk regarding about the audio in the custom rom forums.
Sorry for being rough and negative, I just want to clarify :victory:. Please don't be mad at me.
The known bugs on my experience are:
Casting
Missing libgdx.so
Sometimes advanced restart does not work
Audio crackling
Keeps telling slow charging
No internet at OTA update (when I actually have)
Some are minor, others are frustrating. Thanks for your reply.
Click to expand...
Click to collapse
We've gone quiet on the audio front because we just have to accept it's not good. Changes of this nature happen on ALL devices. E.g. I had Xperia SP years ago. Amazing camera on stock... completely crap in LOS (CM at the time). Galaxy S3 mini... battery. Moto X Play...camera (absolutely important s it has a 21mp camera). They take time to get sorted. Some are done well...others not so well.
It's the high-end mid-range phones that suffer (A5 2017 and the above mentioned) the most. Cheap phones are perfect (LG Spirit 4G and the Alcatel Pixi 3 both work better with LOS based ROMs than they did on stock).

moozer said:
We've gone quiet on the audio front because we just have to accept it's not good. Changes of this nature happen on ALL devices. E.g. I had Xperia SP years ago. Amazing camera on stock... completely crap in LOS (CM at the time). Galaxy S3 mini... battery. Moto X Play...camera (absolutely important s it has a 21mp camera). They take time to get sorted. Some are done well...others not so well.
It's the high-end mid-range phones that suffer (A5 2017 and the above mentioned) the most. Cheap phones are perfect (LG Spirit 4G and the Alcatel Pixi 3 both work better with LOS based ROMs than they did on stock).
Click to expand...
Click to collapse
I understand that this rom is unnoficial and comes with bugs, but the problem is software-wise, which means it can be fixed, even though we need to dig deeper to the root files. Maybe we can recreate or port the samsung drivers used for audio, deleting all traces of audiofx and other minor fixes just to acomplish this. This may sound unrealistic, impossible and bluffing, but the limits are not only from the rom. Maybe we need custom kernel, or who knows.
Heck, there is little to no talk regarding this issue, so I presume some don't have this issue which could mean only a handful of devices have, because of revisions, idk.
So to sum it up, it could be fixed, but I guess no one has the time and motivation to do it.