Related
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!
I've searched for this problem, found some stuff that is close but I haven't been able to find it exactly.
Speakerphone and built-in microphone work fine.
But when I use my headset (Bose MIE2), the microphone fades in and out when I am on a call. People say it will sound fine and then start to sound "tinny" or like I'm "in a can". Seems like this happens when I stop talking and they speak and the background noise becomes louder to the caller. And it doesn't last. It fades in and out, several times on a call.
This headset worked fine on stock AT&T Gingerbread.
About two months ago, I decided to root my phone for the first time and install a modded ROM. So I flashed CM7. Headphone mic worked fine on CM7.
Bose microphone was also working fine on CM9 - one of the early release candidates.
At that point, flashing became easy so I started on the nightlies (I'm sounding like an addict, aren't I? I feel like one!!!).
Then I found my dream flasher/pusher, Task! I've been on AOKP ROM (currently up to date on the 5.1.2012 release) ever since. Awesome ROM, if you haven't tried it.
Still having the headphone mic issue though.
I've wiped fully several times (yes, I read every post in your thread, Task), trying to clear this up.
I also wondered if the headphones where jacked so I returned them to Bose and the new pair is presenting the same issue.
I have read all about the built-in mic swapping issues with the different kernels.
I've tried NEAK and Siyah and I'm careful to be sure I have the mic swapping versions for AOKP/CM. My phone does not like NEAK at all. Loves Siyah - getting fantastic battery life (14 hours today, 27% screen time and WiFi on all day with 20% battery remaining) and responsive. I'm currently on the latest Siyah ICS [v3.2rc1] with UC 200 to 1000, lulz/vr only. It is also awesome, thanks, Ktoonsez!
I'm wondering if that mic swapping on the phone has anything to do with the mic on the headset.
Also, is there anything else I can check to help troubleshoot this in more detail?
Finally, are there any controls for headphone mics or even microphone settings in ROM Control or anywhere else that can be adjusted?
Thanks for your help in advance!
The NEAK kernel only has one choice for Tasks rom, no need to pick between mic swap.
Sent from my SGH-I777 using, xda premium
brobinson2102 said:
.
I've tried NEAK and Siyah and I'm careful to be sure I have the mic swapping versions for AOKP/CM.
Click to expand...
Click to collapse
There's your problem. You have to use the AOSP version bro.
Sent from my SGH-I777 using XDA
Biporch said:
There's your problem. You have to use the AOSP version bro.
Click to expand...
Click to collapse
I'm wishing it was that simple. On NEAK, I've tried the AOSP - still have the issue. My phone freezes too often on that kernel.
On Siyah, I get the mic swap version for AOKP/CM - still having the issue.
The latest Siyah runs like a beast and gets fantastic battery, just has the fading issue.
Sent from my SGH-I777 using XDA
Can't replicate the problem... Sorry.
Biporch said:
Can't replicate the problem... Sorry.
Click to expand...
Click to collapse
Appreciate you trying!
Sent from my SGH-I777 using XDA
hello new here i followed all the directions to a tee got everything install very easy as im not new to flashing roms. i have a rhod400 (sprint tp2) and i have the issue of no sound from the rear speaker when receiving phone calls or anything really. it all comes from the front earpiece speaker. is there a update to flash to fix this? or any easy way to get it working. ive tried numerous times thinking about a bad flash with no luck and yes i have task29'ed it after each to make sure. however the gbx0 3.3.x kernal works perfectly with sound but i like the normal omgb rom better personally for some reason the gbx0 nand rom on my phone seems much slower to respond and much slower going through menus etc for some reason and ive flashed it a few times to make sure
also im running the newest verizon .37 radio as well.
sorry for asking here and not in the thread i needed more posts and really hope someone can help with that. ill be posting more so hopefully will be able to ask there soon but i really wanted to get this fixed asap since i use this phone daily.
Never heard of that before, but I had to move the thread. Sorry.
Good luck & post logs. I doubt it's an issue with the ROM tho, as I run that same ROM myself. Same phone, same radio (assuming you're on the 2.37VZ radio), etc.
You're using the latest OMGB and the latest CWM recovery - not AOSP?
I know that OMGB is using the older kernel, and I want to say that the 3.x kernels got a serious audio code re-write. That could account for the difference. Unfortunately as it seems there is no more development happening in the OMGB rom there will not be support of the newer kernels. Perhaps you should consider using the GBX nand version rather than the OMGB.
wizardknight said:
I know that OMGB is using the older kernel, and I want to say that the 3.x kernels got a serious audio code re-write. That could account for the difference. Unfortunately as it seems there is no more development happening in the OMGB rom there will not be support of the newer kernels. Perhaps you should consider using the GBX nand version rather than the OMGB.
Click to expand...
Click to collapse
I guess I assumed the OP was using the kernel from OMGB.
Is that the case OP? Please stick to the kernel provided with OMGB and report back.
arrrghhh said:
I guess I assumed the OP was using the kernel from OMGB.
Is that the case OP? Please stick to the kernel provided with OMGB and report back.
Click to expand...
Click to collapse
The way I read his post was that he tried GBX w/3.x kernel and OMGB, but only saw the sound issue in OMGB. However he wanted to use OMGB as it seemed to have a better performance. It sounds like his issue might be related to using the older kernel in OMGB. Not necessarily so much that he was swapping bits and parts around.
wizardknight said:
The way I read his post was that he tried GBX w/3.x kernel and OMGB, but only saw the sound issue in OMGB. However he wanted to use OMGB as it seemed to have a better performance. It sounds like his issue might be related to using the older kernel in OMGB. Not necessarily so much that he was swapping bits and parts around.
Click to expand...
Click to collapse
I've just never heard of any sound issues with OMGB. I did a quick search, can't find anyone with sound issues on OMGB at all, whatsoever...
OP has been PMing me and said the same issue is present on another RHOD400. I have to think he's doing something wrong, but I have no clue what he could do wrong that would cause everything BUT sound to work...
arrrghhh said:
I've just never heard of any sound issues with OMGB. I did a quick search, can't find anyone with sound issues on OMGB at all, whatsoever...
OP has been PMing me and said the same issue is present on another RHOD400. I have to think he's doing something wrong, but I have no clue what he could do wrong that would cause everything BUT sound to work...
Click to expand...
Click to collapse
That is an odd issue. I have to agree with all your points.
wizardknight said:
That is an odd issue. I have to agree with all your points.
Click to expand...
Click to collapse
ive heard of this with really old sdcard builds... i seem to recall if you set the volume to one step below max the audio kinda worked the way its supposed to. let us know if your still having issues.
Me Too
I can confirm I'm having this issue as well on OMGB on my RHOD400. Can't hear notification tones or incoming ringer. Volume level "beeps" when you hit the buttons are also very quiet (at all levels) and come from earpiece instead of speaker.
Logcat with unanswered call and poor volume attached. Also, attaching logcat with info from startup.
I too am still using this as my daily phone...I'm missing calls and pissing people off (not that I care) due to this. It used to fix after a reboot, but now it's just stuck like this.
I'm seeing permissions issues trying to access the audio*.csv files from the SD Card, it looks like it finds a default instead. I'm not sure if this is normal.
NeoMatrixJR said:
I can confirm I'm having this issue as well on OMGB on my RHOD400. Can't hear notification tones or incoming ringer. Volume level "beeps" when you hit the buttons are also very quiet (at all levels) and come from earpiece instead of speaker.
Logcat with unanswered call and poor volume attached. Also, attaching logcat with info from startup.
I too am still using this as my daily phone...I'm missing calls and pissing people off (not that I care) due to this. It used to fix after a reboot, but now it's just stuck like this.
I'm seeing permissions issues trying to access the audio*.csv files from the SD Card, it looks like it finds a default instead. I'm not sure if this is normal.
Click to expand...
Click to collapse
Do you have this issue with the GBX Nand build?
wizardknight said:
Do you have this issue with the GBX Nand build?
Click to expand...
Click to collapse
Just got it installed. Ringer works fine on GBX0* + 3.3.6
NeoMatrixJR said:
Just got it installed. Ringer works fine on GBX0* + 3.3.6
Click to expand...
Click to collapse
Makes me think there's some acoustic patch that's missing in the OMGB .27 kernel...
That's a bummer. Strange only some experience the bug...
Hi, most of you should know me because Hybrid Bootstacks. But today, I'm here to talk about something new. (or not so new.)
Some people are getting Low audio output when on CM-12.1+ or any other aosp based. (I'm getting too.)
The problem here, is that not everybody has this issue, so, I need to you guys answer this poll with your G2 variant.
But only if you are facing this audio bug!
Attention, it is only about output volume, don't answer the poll if you have only the low mic issue. (Just reply the topic, with infos.)
Thanks,
Daniel Stuart
daniel.stuart14 said:
Hi, most of you should know me because Hybrid Bootstacks. But today, I'm here to talk about something new. (or not so new.)
Some people are getting Low audio output when on CM-12.1+ or any other aosp based. (I'm getting too.)
The problem here, is that not everybody has this issue, so, I need to you guys answer this poll with your G2 variant.
But only if you are facing this audio bug!
Thanks,
Daniel Stuart
Click to expand...
Click to collapse
I have d802 and i was facing this problem and all the people i know with g2 complain about that. I know that you need to change the mixer_phat to increase the volume.
Enviado desde mi LG-D802 mediante Tapatalk
Edit mixer paths or use Kernel Auditor. It's that simple.
Having issues, it's too darn low! Had to edit mixer_paths... d802 SEA Variant...
khanjui said:
Edit mixer paths or use Kernel Auditor. It's that simple.
Click to expand...
Click to collapse
Yes it is, but I'm working to push a fix on cyanogen repo.
theshrink89 said:
Having issues, it's too darn low! Had to edit mixer_paths... d802 SEA Variant...
Click to expand...
Click to collapse
Yeah, seems that it is a d802 only problem. I'll wait a little more until start to work on it.
Can you just answer one thing for me? Your microphone is low too? (cm13.0, cm12.1 has a mic bug.)
Just increasing values in mixer_paths did raise the volume. Problem was that it started to distort sound on the highest volume step. The solution was to flash viper4android, it made it possible to use a high value and not get sound distortion. D802
Sure, no problem... My girlfriend has been complaining that she doesn't hear me loud enough since I flashed 12.1, will have to test it on my own though by switching phones with her and will let you know... Editing the mixer_paths is not the solution because of the distortion, as stated above, and also the volume isn't quite linear in the final 3 steps, it's like it is jumping over two steps... Or we can't find the correct setup for the file... It can't be that we need to change just one (or three) value(s)...
d800 5.1.1 while recording at times when sound was loud it would sound very low at that part when record was played.. also using whats app audio messages it will start high for a second then very low, but only my messages that i sent recorded with g2 phone, the other end or friend could hear me out clear and loud just normal. and i could hear they messages loud just normal. only thing was my messages recorded with g2.
migueldbr said:
Just increasing values in mixer_paths did raise the volume. Problem was that it started to distort sound on the highest volume step. The solution was to flash viper4android, it made it possible to use a high value and not get sound distortion. D802
Click to expand...
Click to collapse
Yes, we need to find the best editing mixer_paths + kernel audio driver gain.
theshrink89 said:
Sure, no problem... My girlfriend has been complaining that she doesn't hear me loud enough since I flashed 12.1, will have to test it on my own though by switching phones with her and will let you know... Editing the mixer_paths is not the solution because of the distortion, as stated above, and also the volume isn't quite linear in the final 3 steps, it's like it is jumping over two steps... Or we can't find the correct setup for the file... It can't be that we need to change just one (or three) value(s)...
Click to expand...
Click to collapse
raptorddd said:
d800 5.1.1 while recording at times when sound was loud it would sound very low at that part when record was played.. also using whats app audio messages it will start high for a second then very low, but only my messages that i sent recorded with g2 phone, the other end or friend could hear me out clear and loud just normal. and i could hear they messages loud just normal. only thing was my messages recorded with g2.
Click to expand...
Click to collapse
Can you guys try cm13.0? Seems like mic has been fixed on it. (Here it's ok now, just a little low. On cm-12.1 it was trash.)
Will give it a shot tomorrow since I need a fully operable phone today for work...
daniel.stuart14 said:
Yes, we need to find the best editing mixer_paths + kernel audio driver gain.
Can you guys try cm13.0? Seems like mic has been fixed on it. (Here it's ok now, just a little low. On cm-12.1 it was trash.)
Click to expand...
Click to collapse
cloudy 3.3 on it , as it treated? Set 12 cm does not help
Update on the situation, the mic is a bit better on cm13 but the sound is still freakin' low...
YES i have this problem on my Lg g2 international every time which i switched on every custom rom my audio it is too low.Now iam used cyanogen the last but the problem it is still exists(((((((Really too low audio.Thanks hope to fix that!
daniel.stuart14 said:
Hi, most of you should know me because Hybrid Bootstacks. But today, I'm here to talk about something new. (or not so new.)
Some people are getting Low audio output when on CM-12.1+ or any other aosp based. (I'm getting too.)
The problem here, is that not everybody has this issue, so, I need to you guys answer this poll with your G2 variant.
But only if you are facing this audio bug!
Attention, it is only about output volume, don't answer the poll if you have only the low mic issue. (Just reply the topic, with infos.)
Thanks,
Daniel Stuart
Click to expand...
Click to collapse
I have an LG G2 D801. I flashed crDroid 6.0.0 a few day ago. Speaker volume is very low. I have no idea how to increase the volume!! Tried Viper4Android but I don't even notice a difference.
When I call someone, they can hardly hear me.
Does anyone know how I might increase the speaker volume for my phone? Any good advice will be appreciated.
I remember a time when people were helpful on XDA. They would share knowledge, help others who know less. Unfortunately, those days are long gone.
I have referred many friends and acquaintances to XDA Developers, telling them there are many very experienced guys - and girls - who are happy to help you... It gives many of them the experience they need.
But a number of these people would tell me that the people on XDA are, basically, jerks! Rather than complain along with others, I hope to get through to at least one of you.
XDA began as a site where anyone with a specific handheld device could ask any question in order to get help...with any problem they would encounter. It grew and added other devices. Now XDA has become the most reputable go-to site for help with any kind of phone. If anyone knows anything about phones they know XDA Developers.
Guys, this should not be a place to show-of, or to be rude or intimidating. Often, there are people with questions, or need help, advice...and they don't know anything. These are the people who need help the most. Your help. Please treat people the way YOU would want to be treated when YOU did not know anything at all. That is all I ask.
Thank you.
I have d802 and i had to change mixer_paths to hear voice navigation commands during driving my car. The speaker audio is low and changing paths was the solution. It is true that there is a little distortion but when you set CM built in Audio mixer properly then no issues.
@CiscoKydd
If you are using the CM then you could edit the mixer_paths to raise the speaker volume output (have no idea about mic) or you could install cutom CAF kernel for d801 and then change the speaker and mic gain via Kernel Auditor.
I have no knowledge about the d801 kernels because I personally have the d802 version.
Thank you, @sunekosuri. I increased volume by editing mixer_paths. Volume increased to the point of distortion.
As for the mic... Well, that goes on my To Do list.
Thanks again, Sunekosuri.
Now I used to live with this very low sound. Camera and sound are the only issues I think of going back to stock.
hey, i was facing the same problem using last nitly from cyanogem mod 13 on my lg g2 d802 32gb. the only way that seems to boost around 50% the sound ouput was with this app.
hope it help you guys too.
Volume Booster GOODEV
Is this issue fixed now?
Hi all
Please bare with me as I'm not the best when it comes to typing out what im thinking or trying to say
This info is mainly for our awesome devs but also for everyone else. Shout outs to @Unjustified Dev @DrakenFX @tdm and anyone else who can fix this
I was just wanting to help get this fixed as this one bug is keeping a lot of users including myself from moving away from stock and enjoying all the other roms available. I believe the bug has to do with the the work our beloved anonymous dev who helped correct the speaker issues a few months ago. Specifically this---> https://review.lineageos.org/#/c/168154/.
I'm pretty confidant it has nothing to do with any of the different modems people are flashing. I have tested this with all of the different modem versions for my G variant and none have made a difference
Also, there are other users that are getting this bug confused with another potential bug that has to do with distorted sound coming out when activating speakerphone while in call or something like that. I have not experienced that bug so I dont know the specifics. People are just using the term "Speakerphone bug" as both of these bugs involve the speakerphone
Now I can create the bug at will and have attached logcats below in the different scenarios. Hopefully the info is there for those who know how to fix
The steps I do to recreate the bug are as follows
1 - unlock phone and using the volume buttons, make sure the ringtone is NOT set to vibrate/silent and Do Not Disturb is NOT activated.
2 - Make a call. Call comes through earpiece as expected, no issues. Person on the other side can hear perfectly. Repeat as many times as you want, sound always comes through earpiece
3 - using volume buttons, reduce ringtone volume to vibrate/silent or turn on Do Not Disturb
4 - Make a call. Call comes through earpiece as expected, Hang up
5 - With the ringtone still set to silent/vibrate, turn the screen off using the power button and let it sit for about 5 - 10 seconds
6 - Unlock the phone and try to make a call. Call will connect but no sound will come from earpiece. Person on the other side can hear everything as per normal but we cant hear them
7 - While in call, toggle the speakerphone or if you have dial pad sounds enabled in the sound menu, press a number on the dial pad, sound now comes through earpiece as expected
From my testing and the procedure above, you can see that the bug happens when the phones ringer is put in silent/vibrate or when do not disturb is activated and the phone is locked/unlocked.
logcat 1 is with everything working normally, ringtone set to sound and call coming through earpiece as expected
logcat 2 is with ringtone set to silent and making a call. No sound comes from earpiece
logcat 3 is the same as 2 but during the call toggling speakerphone to fix
Now I dont know what is going on in the logs but I do see a lot of errors from "TFA9890"
This was all done on a fresh install of the universal bootloader, twrp 3.1.1.0, A2017G N Modem, latest LOS and Open Gapps mini and logcats were captured with MatLog on my G variant
Oh see this is Incredibly interesting, because tfa4990 is the route being used.... This is potentially incredibly helpful!!!!
I'm going to analyze these I've the weekend and see if I can figure something out. Thank you for the logs
Interesting timing on this post. I've been working on the axon7mini the past 10 days or so, and it also uses the tfa9890 amp. So I've started to familiarize myself with how all this stuff works. (I have pretty much zero experience with android audio in the past).
Fantastic post, well done. I have only encountered the problem a couple of times but upon reading what you wrote a little light bulb went off, that is exactly the situation that it occurs for me as well. It's this sort of interaction and support between the users and devs at xda have that makes it all so worthwhile. Thanks again.
As someone who's dealt with this bug for a long, long time... I have to commend you on a fantastic post. Thanks, and I hope this leads to a solution!
I hope this is looked into in the process of porting LOS 15. Would be cool to see this issue disappear.
Would this bug also happen on the U variant? I tried to recreate it using the steps above and it worked fine.
arecad said:
Would this bug also happen on the U variant? I tried to recreate it using the steps above and it worked fine.
Click to expand...
Click to collapse
I think I have read somewhere that it is not affecting U which might be the reason this has not yet been fixed but I cannot remember where I read this.
We would need the logs from an U variant to check if it looks the same.
sToRm1nG said:
I think I have read somewhere that it is not affecting U which might be the reason this has not yet been fixed but I cannot remember where I read this.
We would need the logs from an U variant to check if it looks the same.
Click to expand...
Click to collapse
It does affect the U variant. I have one and it happened a few times that when I would call someone I had no ringing tone coming from the earpiece unless I toggled the speakerphone on/off.
same problem here in a2017g aosp extended...
So I take it we can give up trying to solve this? Seems to exist in all non stock roms.
Wish someone would fix it. I don't even know where to begin, and with what I've read about the axon 9, i wont be switching phones for quite some time.
Knuxyl said:
Wish someone would fix it. I don't even know where to begin, and with what I've read about the axon 9, i wont be switching phones for quite some time.
Click to expand...
Click to collapse
simply use macrodroid fix it when phone call is activated.Speakerphone on ,speakerphone off .
Thats it
Dodgexander said:
So I take it we can give up trying to solve this? Seems to exist in all non stock roms.
Click to expand...
Click to collapse
Knuxyl said:
Wish someone would fix it. I don't even know where to begin, and with what I've read about the axon 9, i wont be switching phones for quite some time.
Click to expand...
Click to collapse
did you guys try the fix that @Miustone plasters all over XDA?
@Miustone Could you make a flashable zip with ONLY THAT ONE FIX for the Fluence stuff? Pretty please?
Choose an username... said:
did you guys try the fix that @Miustone plasters all over XDA?
@Miustone Could you make a flashable zip with ONLY THAT ONE FIX for the Fluence stuff? Pretty please?
Click to expand...
Click to collapse
Fluence settings will not fix driver implementation. Miustone's claims are misleading. I have tested it to death
The only way to fix would be by a Dev with audio skills. Good luck finding one. I've tried
Stay on a stock roms or risk not hearing in calls in other roms
Tebor said:
Fluence settings will not fix driver implementation. Miustone's claims are misleading. I have tested it to death
The only way to fix would be by a Dev with audio skills. Good luck finding one. I've tried
Stay on a stock roms or risk not hearing in calls in other roms
Click to expand...
Click to collapse
I fixed all Mic Bugs, Just the Echo is left which seams to came from /system/vendor/etc. Don't blame Me for the Bugs, i never touched the Sources of the Axon 7 and besides Kranoner has No Dev ever asked Me about it again. That My Patch is fixing Bugs means Just that there are Things Missing which are working and present on other Devices too...
I was coming from the LG G5 which has used almost the Same Fluence and Mic Configs as currently present in the Patch. Point.
Miustone said:
I fixed all Mic Bugs, Just the Echo is left which seams to came from /system/vendor/etc. Don't blame Me for the Bugs, i never touched the Sources of the Axon 7 and besides Kranoner has No Dev ever asked Me about it again. That My Patch is fixing Bugs means Just that there are Things Missing which are working and present on other Devices too...
I was coming from the LG G5 which has used almost the Same Fluence and Mic Configs as currently present in the Patch. Point.
Click to expand...
Click to collapse
Well, you have a chance to prove it! Make a flashable zip with ONLY the call bug fixes. If it actually fixes their problems then they'll believe you. otherwise they're right not to.
It's next to pointless using a custom rom if you want a good daily driver.
I bought this phone because I thought things like this could be solved this day and age but I won't be making that mistake next time!
Sent from my ZTE A2017U using Tapatalk
Miustone said:
I fixed all Mic Bugs, Just the Echo is left which seams to came from /system/vendor/etc. Don't blame Me for the Bugs, i never touched the Sources of the Axon 7 and besides Kranoner has No Dev ever asked Me about it again. That My Patch is fixing Bugs means Just that there are Things Missing which are working and present on other Devices too...
I was coming from the LG G5 which has used almost the Same Fluence and Mic Configs as currently present in the Patch. Point.
Click to expand...
Click to collapse
Omg who is blaming you for bugs? Your claiming you fixed it but many others still have this issue
This thread is not about mic issues. Please re-read first post and for the hell of it, check out the logcats. They might help you actually fix it
Unless your digging into the audio/dac driver code, I'm doubtful it will ever be fixed
Why do yall think its the driver? I dont have any problems with audio, its how the Phone app is handling it. If i was to debug this I would check the source for the Phone app and trace it from there. It seems like something might not be using the driver correctly, but the driver seems to be working fine. I could be wrong but I'm not new to linux and android, just no experience with audio development.
Maybe try installing stock phone app on LOS or RR and see if it still has problems. That would either show where the problem is or eliminate Phone app from being source of problem.