I figured I'd start this thread for everyone to discuss problems relating to call audio.
Today I tried from a fresh CM10 copying all the audio cfg files from Holics 1.3 (fixing files names to match CM10 where required), reboot, make calls.
I am certain that I got the back speaker louder for notifications music (to the point now where it distorts), however speaker phone and headset vol are still about the same.
The volume up/down has no effect on the volume. I can see in the live log that when I press the vol rocker, the phone is "setting" the volume step, but it has no audible effect.
I also tried copying the AIC and TPA and Adie cfg files from an HTC One V (which I'm guessing uses the same audio chips since the cfg files are named the same). No change detected.
While testing calls with a friend, he noticed that when he spoke in a low voice, or made non-word noises (banging, clapping, etc) he did not hear that echo. Whispering didn't echo. Just "regular" volume speech.
I'm starting to wonder if the changes made to the A1026 to enable in-call for AT&T phones have caused the echo issue (and possibly the broken vol control and/or seemingly single-level volume).
That's it for tonight. Feel free to post any steps you followed to test the issue here.
Im up for this
Yea I keep getting that. In calls it. Echoes or sounds muffled I have noise cancelation checked
Sent from my Vivid 4G using Tapatalk 2
Being that the remote user hears themselves echo, it almost sounds like the gain on the second mic is too high. So when their voice comes through on the handset speaker, the second mic pics it up, and the echo is produced. What carrier and device does everyone have? Im on ATT with a Vivid and from what I understand there's no echo, at least none that has been reported.
homeslice976 said:
Being that the remote user hears themselves echo, it almost sounds like the gain on the second mic is too high. So when their voice comes through on the handset speaker, the second mic pics it up, and the echo is produced. What carrier and device does everyone have? Im on ATT with a Vivid and from what I understand there's no echo, at least none that has been reported.
Click to expand...
Click to collapse
I'm on ATT and Vivid. Sometimes it happens sometimes it doesn't. Mostly people report I sound garbled but not with every conversation.
I'm getting reports that people are hearing themselves echo..
In Toronto on the chatr network..but the phones were originally from Rogers. On my end I have zero echo, everything is crystal clear, if a little quiet.
Sent from my Vivid 4G using xda premium
Second mic gain is what I suspect too, since quitter noises don't echo, but in my testing, I don't seem to be able to affect the mic/headset speaker gains using the configs. Though with that said, I wasn't specifically trying to reduce the top mic gain last time. I suppose that's the next step, as well as reviewing the code that loads the CSV values and sets values in software.
I'm wondering if we are not actually loading the values that are in the CSV, and are instead relying on defaults that were built in. Or the values are only loaded once. Or we have bypassed the loading or checking for changes, or something like that.
If anyone has the time to sleuth around github/XDA or wherever to find examples of kernel audio adjustments for other phones (on the same or similar boards) that would be a big help. I have had a hard time finding things on github. The advanced search seems a little less than useless to me.
I dont hear myself echo the other person does with noise cancelation unchecked and with it checked they say i sound muffled
Sent from my HTC Vivid 4G
I wonder if this is our problem - maybe the phone is ignoring the tpa config files and defaulting to stock board values, which are probably wack. I'd like to see dcacklam's git to see exactly what he's doing, but haven't found it yet. haven't looked too hard tbh. I have an idea of what he's trying to do though, I think, and may play around later - otherwise i'll try some stuff tomorrow.
He appears to be building a kernel for CM10 for the Amaze and just posted this a few hours ago (maybe helping maintain cm10, haven't searched too hard. I'm feeling lazy this evening, can you tell?):
dcacklam said:
[/COLOR]Think I have the audio-volume licked...
The phone was IGNORING the TPA2051_CFG.csv file and going with the hardcoded defaults in the driver source-file...
So I put a mix of HTC defaults, and EclipzeRemix's SpeedRom amplifier-config values (using SpeedRom numbers where no data existed in the stock TPA file) into the source-file...
And I am waiting for the kernel to build with these changes!
Click to expand...
Click to collapse
So as it turns out my remote parties hear themselves echo too
Lol - no one ever cared to tell me until tonight...
Same symptoms though - they hear themselves echo. But with me it doesn't seem to matter whether noise suppression is on or off, they still hear an echo of themselves, but hear me ok, and i hear them ok.
This may make it a little easier for me to troubleshoot though.
Sorry I've been telling everyone I'm not affected
I didnt know either until someone told me. At least we knowhere now
Sent from my HTC Vivid 4G
Hmmmm.... Could this method in board-audio.c have something to do with the volume being stuck at one volume?
Code:
int holiday_get_rx_vol(uint8_t hw, int network, int level)
{
int vol = 0;
/* to be implemented */
pr_aud_info("%s(%d, %d, %d) => %d\n", __func__, hw, network, level, vol);
return vol;
}
ess.boyer said:
Hmmmm.... Could this method in board-audio.c have something to do with the volume being stuck at one volume?
Code:
int holiday_get_rx_vol(uint8_t hw, int network, int level)
{
int vol = 0;
/* to be implemented */
pr_aud_info("%s(%d, %d, %d) => %d\n", __func__, hw, network, level, vol);
return vol;
}
Click to expand...
Click to collapse
I saw this the other day - that was the only int vol reference I found actually. I don't understand the language well enough to know exactly what's going on or how it would need to be edited. Have you tried editing the 0 value to see if anything changes? Or do you know the language wee enough to tell it to look at the tpa configs for values...or even if that's where it would need to be done?
homeslice976 said:
I saw this the other day - that was the only int vol reference I found actually. I don't understand the language well enough to know exactly what's going on or how it would need to be edited. Have you tried editing the 0 value to see if anything changes? Or do you know the language wee enough to tell it to look at the tpa configs for values...or even if that's where it would need to be done?
Click to expand...
Click to collapse
I'm doing a build right now with that value set to 3 to see if it changes anything.
I'm wondering if that is the method that catches the vol up/down commands and passes on the volume change.
If that's the case, what I would expect is that it has a usable range of 0-5. 0 is loudest, 5 is quietest. If that's true, here is where we would fix the volume control not working. However, that's not going to help us get the in-call volume up any higher.
ess.boyer said:
I'm doing a build right now with that value set to 3 to see if it changes anything.
I'm wondering if that is the method that catches the vol up/down commands and passes on the volume change.
If that's the case, what I would expect is that it has a usable range of 0-5. 0 is loudest, 5 is quietest. If that's true, here is where we would fix the volume control not working. However, that's not going to help us get the in-call volume up any higher.
Click to expand...
Click to collapse
I'm also testing a theory right now based on reverting this (https://github.com/Sportsstar89/and...mmit/9261a3aab974db0a376d3a398e4302e6ba53ca76) and this (https://github.com/Sportsstar89/and...mmit/56d56f55bf08dd25295bd93ae40b2df78ec30f52) (but leaving the att in call audio fix alone)
Comparing to HTC's sources (which could very possibly be very incomplete), these changes weren't there (obviously, or else they wouldn't be changes). Of course, we didn't have ATT in call audio with HTC's sources either. In the first commit, htc acoustic table values are directed to new sources (.csv files). In ATT's source, both audience and non audience were directed to aic3254 txt files. I'm thinking, since my previous "audiofix" which played with some TPA2051 values seemed to improve other audio, maybe these dsp .csv configs are only for non-call audio, and the in call audio requires a the aic .txt files? With the second commit - again, in HTC's source, they didn't have any indicators for ATT SKU 1 or ATT SKU 2, just ATT SKU3 had support_audience=1. What if not all of the ATT Vivid's have the audience chip? Only a select batch.(Edit: New theory for this is the support_audience=1 that was listed is actually defined for all 3 ATT SKU's, and the other entry "Default" is for the other models. So it's possible that the in call mic always worked if you screamed in it for ATT users, but maybe no one ever tried?) IFFFFF these theories were to pan out - it would possibly explain why some have echo and some don't, why in call audio seems worse for some people (and can't be adjusted), and possibly even why some ATT users have no trouble with in call audio on the first try, and others do. All theories though. h8rift seems like a smart dude, so chances are reverting these changes won't help a bit. But honestly, the ratio of things I've done that haven't worked/things I've fixed is like 200/3, so I won't be disappointed if nothing happens
Edit: Also - in HTC's sources "int vol = 0" as well
Edit: Well audio did initialize on the first call after flashing the new kernel and rebooting. Also rebooted again after that to test, and in call audio kicked in on the first call again. In the past after any kind of reboot, first call didn't work. Audio adjustment still doesn't work. I'll call my wife shortly to see if the echo still exists. But this appears to have at least killed the first call audio not working bug. If anyone else wants to test here you go:
zImage and bcmdhd.ko are here (https://docs.google.com/folder/d/0B8HUFb41pK2eQjFZMWx6UE43VnM/edit)
Don't know about other recoveries, but with WCX, in Developer Options, you can make and flash boot from zImage. Follow on screen instructions. maybe someone else can make a boot.img and I'll make a flashable package.
Edit 2: Still echoes on remote end. Slightly, but it's there. I don't know how bad it was before though - didn't try it for myself til now. Also my wife just said it still echoes, but it's not as bad. Please test and post results (in which case I have a few other thoughts as well, but I'm going to lunch now )
The couple of calls I had over lunch said there wasn't any echo. Anyone give this a go yet?
Feedback on this^ flashed it and reports are crystal clear. Only complaint was that I was really quite. The person I called had just gotten off a call with someone else and the volume was fine so it looks like it is on my side.
Thanks for the feedback. Hopefully we get a few more that report the same, then I'll start trying to tweak volumes
Sent from my Vivid 4G using Tapatalk 2
mind posting your boot.img esloan? I tried repacking homeslice's zImage into mine but it won't boot. I must be missing something.
Is there any way to disable the secondary mic? This would (a) verify that the mic is causing the echo, and (b) provide a temporary workaround until a proper solution can be found.
Related
Hello All,
I searched first by the way :-/
Recently my Nexus has had its earpiece too loud for both Incoming and Outgoing Calls.
At first I thought it had something to do with the radio, so I downgraded. It actually worked on the first call but after that it was loud as heck even on the lowest volume.
I tried to retrace my steps with my applications next, but nothing that would point to the earpiece. The last apps installed updated where mostly games like Fruit Ninja and Aliens vs. Humans, so I think we can rule out that.
The specs in my sig should be up to date.
The only variable that has changed other than the ones listed above is the fact that I recently bought a Jawbone Icon Bluetooth Headset. But to my memory, this issue began before that.
Can't find a solution anywhere cause it seems most people have an issue with the phone being too soft lol.
I'm really looking for some help guys. I'm just short of wiping the phone clean and reinstalling CM6 and my apps. If that dosen't work I'll have to use the warranty I guess. Had the phone from about Sept 10 I believe.
Let me know if I missed anything guys. All ideas are welcomed to fix this issue.
It's probably because of CM. CM uses a audio boost kernel by default, so I'm guessing that's the problem. Try installing no audio boost kernel to see if it solves the issue.
yeah if you are using cyanogen ROM, they added an audio boost hack long ago. on cyan 5.0.8 the audio boost was so loud that over 50% volume started to distort the speaker and kill your ears. so in later releases they split the difference and lowered it somewhat.
but the boost has always been there. the only likely possibility is that you recently started enabling DSP settings like compression or the EQ, which would suddenly now make things way louder.
Wow thanks guys. Had no clue that CM had an audio boosted kernel. Guess I'll be flashing something else for the while. Something as close to vanilla I guess.
Oh, I also checked the DSP settings, everything was off but was worth a shot.
Thanks again for the replies!
Just to let anyone with the same issue know, I found away around it. I installed one of Wildmonks kernels without the audio fix.
Kernel 2.6.35.10 to be exact. I get to keep my cyan features and have a decent volume ear piece too. Yay!
Good work. It's funny cause most people complain this phone is too quiet. If only they see this post!
So apparently, I am just finding out now that this is a major issue with all Bionics and seems to be something related to the Gingerbread kernels. This is actually an issue I first noticed with my Thunderbolt back when testing out Gingerbread builds. I won't go into too many details as most of it is in the following thread: Click Here
The idea seems to be that the kernel was not properly written to account for the device's amplifier and it takes about a second for it to boot up after the first sound is made. Then if you keep producing sounds it will be at the proper volume. But don't touch it for about 5-10 seconds and it goes "idle" and then the first sound again is quieter and then accompanying sounds will be louder again.
A good way for you guys to test this is try the following:
1. Make sure your volume is all the way up
2. Go to the dialer app and press a number like 2 on the dialpad and listen to the sound (you can hear it sounds as if it starts quiet and then grows louder)
3. Keep pressing the same number and any other number you will hear they all sound the normal loud volume now
4. Don't touch the dialpad for 5 seconds
5. Press any of the numbers again and you will hear the same issue (sound of the key pressed grows from quiet to loud)
6. Keep pressing any number and you will hear it sounds normal again
This issue is not only in the dial but pretty much any system sound. It has been determined that it is related to the kernel and perhaps now with the kernel source released maybe a developer can look into this issue?
Wow I never noticed that before. Guess its not a huge issue in my use. Oh well....maybe we'll get some custom kernel apps now that the source is released.
Bump for more exposure
I never noticed this before but it happens on my phone as well. I don't really see what the big deal is. It's probably a battery saving trade off of some sort. It's not like this happens in the middle of a song.
My Bionic with D3Blurr3d rom on it does not do this. Either through the speaker or headphones. BTW, you made me call someone in Mauritania by punching a bunch of 2's in my dialer!!! (not really, but wouldn't that be funny?)
I don't have this issue on liberty 48
Not a kernel issue it's a hardware issue.
https://supportforums.motorola.com/message/469889#469889
If you test 10 different Bionics you will get 10 different results, but what we know is that it's due to piss-poor EMI shielding or grounding. Not trying to **** on your thread or anything, I (almost) hope it is a kernel issue, as an OTA could possibly resolve the issue.
quentin0 said:
Not a kernel issue it's a hardware issue.
https://supportforums.motorola.com/message/469889#469889
If you test 10 different Bionics you will get 10 different results, but what we know is that it's due to piss-poor EMI shielding or grounding. Not trying to **** on your thread or anything, I (almost) hope it is a kernel issue, as an OTA could possibly resolve the issue.
Click to expand...
Click to collapse
The OP was referring to a different issue, not headphone whine. But on that topic, it's not a Bionic issue, it's a Motorola issue. I took a trip on Sprint with the Photon before getting the Bionic and it has the high pitched whine also, even though it uses a different processor (and i'm assuming sound codec). It wasn't as loud as the Bionic's, but it was there.
People always complaining me about my low voice when i talk them. I tested it, the mic volume is really low. I found some article about increasing mic volume level but it is for galaxy S2 and it is not work on galaxy note. If you know how to increase please help me get rid of this boring problem. Thanks
any help?
omg nobody knows?
Which rom you are on?
its supposed to be working if you are on stock firmware or any custom rom based on stock
A) Enter service mode by typing below code on your dialer :
*#*#197328640#*#*
click the following:
[5] AUDIO
[1] NB (VOICE CALL)
Choose Handset, headset, Speaker (which ever you want higher volume)
[1] VOLUME
[1] SRC Speech RX Volume
Change default values and higher the values any number of your choosing, here is an example:
[0]0_lvl : 68
[1]1_lvl : 72
[2]2_lvl : 76
[3]3_lvl : 80
[4]4_lvl : 84
[5]5_lvl : 88 Higher these values to until hear volume improvement.
Credits goes to original author
sahilarora2003 said:
Which rom you are on?
its supposed to be working if you are on stock firmware or any custom rom based on stock
A) Enter service mode by typing below code on your dialer :
*#*#197328640#*#*
click the following:
[5] AUDIO
[1] NB (VOICE CALL)
Choose Handset, headset, Speaker (which ever you want higher volume)
[1] VOLUME
[1] SRC Speech RX Volume
Change default values and higher the values any number of your choosing, here is an example:
[0]0_lvl : 68
[1]1_lvl : 72
[2]2_lvl : 76
[3]3_lvl : 80
[4]4_lvl : 84
[5]5_lvl : 88 Higher these values to until hear volume improvement.
Credits goes to original author
Click to expand...
Click to collapse
i tried but when i click 5 audio nothing happens. Always turn back to main menu whrn i click audio. My rom is kingdroid v7.4
? any other suggestions
I really need help please tell me something
you could try shouting lol
Probably above needs some more testing.
If you have the issue with all people then warrantee maybe? It might be just one. Maybe they aren't holding phone right. Speaker wrong end or not in ear lol.
You can try setting option noice cancellation in dialer off. It might help.
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
you could try shouting lol
Probably above needs some more testing.
If you have the issue with all people then warrantee maybe? It might be just one. Maybe they aren't holding phone right. Speaker wrong end or not in ear lol.
You can try setting option noice cancellation in dialer off. It might help.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Anyway noise reduction already off. The menu which is mentioned as a setting to set the mic volume, is not shown on my rom. If there is another way to increase the mic volume (from CWM by installing a zip file etc.) i want to know. Just it.
How can i increase the Mic volume? Is there any mod? do not tell me the "*#*#197328640#*#*" thing... It doesnt work for me. Yes the Menu is opening but i cant enter the [5]AUDIO section... Is there any other mods? for ex. Flashing through CWM etc?
hotboy_ist said:
How can i increase the Mic volume? Is there any mod? do not tell me the "*#*#197328640#*#*" thing... It doesnt work for me. Yes the Menu is opening but i cant enter the [5]AUDIO section... Is there any other mods? for ex. Flashing through CWM etc?
Click to expand...
Click to collapse
u can fix it?, i have the same problem :C
ershock said:
u can fix it?, i have the same problem :C
Click to expand...
Click to collapse
No I couldn't fix it...
I type in this code on Note N7100 and hit the call button, tell's me invalid code? any ideas?
Amazing...
Just thought I'd check in tonite and see what's going on with my favorite problem... namely, crappy audio and Mic-gain on the Note2... the "flagship" (At least at one fleeting moment) of the Samsung Fleet. LOL.
Reading the bogus information about kernels (which are only for the "Oh, Wow" and "Far Out" crowd with underclocking and overclocking and a combo of undervolting and overvolting and all combinations in between, nobody had an answer. Hah!
Well... believe it or not, I still have my N7100, and rooted on stock 4.4.2 (the late and great last rom from Sham-sung) and I fixed my audio problem a long time ago... after buying all of the "Pro" apps that were supposed to "cure" the audio problems.
Not ONE of them actually cured anything, but actually created a ton of other problems like caller's voices echoing back at them while talking to me.
I guess that's "technology" for 'ya... give it enough time, and all things are swept under the rug... with the new phones having all the same problems and still no answers or cures for the problem at hand.
As an aside... does anybody here remember the film, Mommy Dearest?
Remember that scene where Joan Crawford freaks out over wire coat hangers and beats the crap outta her daughter for having them in her closet?
That's the way I am now with rear-facing speakers.
No more low-volume crap with rear-facing speakers and multiple microphones for regular calls or speaker phone.
Nope, no way.
Anyway, long story short... there's another thread about Mic-Gain on this site that actually made it so that if I use Speakerphone, the other person can actually hear me.
Unfortunately, everybody in Wal-Mart can hear my convo over the rear facing speaker.
Register 21 is now open.
i have the same problem, i cant find the file
The Solution
Hello i have THE solution!!!! I'm sorry my rusty english but this is it.
You must to download (es file manager) your device must be rooted go to device - system - etc and open default_gain.conf must to change value of (IN1L Volume) in there has a value in number maybe 20 or less my 1st falue change is 40 but is verry loud i recomend a value 35 but is up to you and your device my device is Galaxy note 2 n7100 and i lost 2 days breaking my head and google it but i found the solucion i hope is good for all of you
This one works
Microphone Amplifier​
Microphone Amplifier - Apps on Google Play
Discover the small voice around you and high quality wav format recording.
play.google.com
I did this on my N5 and I recall it being mixer_paths.xml and then you find something along the lines of path name=handset or incall etc. followed by a line RX(X) Digital Volume value= (something along the lines of 80). I did a search and that was about it so I went into this expecting to find something much the same.
I can find reference to RX digital volumes in the listing of initial values at the start of the file and these have an expected value of 84 but I cant find a path name= with a likely suspect like handset, incall, voice, etx. followed by this line where I would make the actual change.
Anyone else dug into this yet? I'm wondering if I can simply make the changes in the initial values? I cant remember if the N5 had those lines but I'm guessing it must have. There are seven of them as you would expect with the stock call volume stepping. I've been contemplating giving them a small nudge to 86 and see what happens, good idea or not?
As an aside I found a line for in call recording mode which is currently set to 0...
krabman said:
I did this on my N5 and I recall it being mixer_paths.xml and then you find something along the lines of path name=handset or incall etc. followed by a line RX(X) Digital Volume value= (something along the lines of 80). I did a search and that was about it so I went into this expecting to find something much the same.
I can find reference to RX digital volumes in the listing of initial values at the start of the file and these have an expected value of 84 but I cant find a path name= with a likely suspect like handset, incall, voice, etx. followed by this line where I would make the actual change.
Anyone else dug into this yet? I'm wondering if I can simply make the changes in the initial values? I cant remember if the N5 had those lines but I'm guessing it must have. There are seven of them as you would expect with the stock call volume stepping. I've been contemplating giving them a small nudge to 86 and see what happens, good idea or not?
As an aside I found a line for in call recording mode which is currently set to 0...
Click to expand...
Click to collapse
take a look here
if u need somethig tell me,but without root we can t do more
https://drive.google.com/file/d/0BwTULBGmnkwqWjJKWlRZUFJ0bm8/view?usp=sharing
I have root (maxx) and I've been going through the build.prop and some other files including the mixer_paths.xml and mixer_path_i2s.xml and I cannot find the digital volume= X in any likely looking path=. I think it has to be there and I'm just missing it or else it may be we would adjust the initial volume? In i2s.xml the digital volume shown only has 4 steps and still doesn't come after any path that looks likely. It would seem to me that rx1 through 7 are certainly a smoking gun. DEC should be speaker, ADC mic, and HPHL/R would be headphone correct?
Since no one jumped in with a warning I went ahead and backed up mixer_path.xml and then edited the values mentioned changing the stock initial value of 84 to a value of 86 on RX1 through RX7 and it appears to have worked over a couple calls I made although it may be I got lucky with a couple of unusually good connections. If someone wants to give it a go and verify the results we may have a working method of increasing the in call volume. Anyone testing that hasn't done this before should be aware that small changes in the values have a large effect so its best to take baby steps, keep in mind the stock speaker may not have much headroom so play it safe unless you're feeling brave. Be sure to backup the file before editing.
krabman said:
Since no one jumped in with a warning I went ahead and backed up mixer_path.xml and then edited the values mentioned changing the stock initial value of 84 to a value of 86 on RX1 through RX7 and it appears to have worked over a couple calls I made although it may be I got lucky with a couple of unusually good connections. If someone wants to give it a go and verify the results we may have a working method of increasing the in call volume. Anyone testing that hasn't done this before should be aware that small changes in the values have a large effect so its best to take baby steps, keep in mind the stock speaker may not have much headroom so play it safe unless you're feeling brave. Be sure to backup the file before editing.
Click to expand...
Click to collapse
i will test it
tell me what to do
Edited both files and raised volumes to 95 for RX values and to 90 the Dec values that were arrounf 70 and 80 something. Clearly a noticeable improovement. Even call volume is raised and sounds excellent.
---------- Post added at 07:34 PM ---------- Previous post was at 07:28 PM ----------
These are my edited Moto Maxx mixer files. Use if you like and check if they work for you. Remember, only for Maxx, and i am not responsible if your phone catches the Ebola virus. Just unzip files and move to system/etc folder and set correct permissions. Let me know.
https://copy.com/x3TmPejOwitAwDab
The DEC should be speaker, headphones can also be adjusted in the same way which should be HPHL and HPHR. I thought we had a runner but I wasn't positive because call quality is so hit and miss around here. I'd be wary of making that large an adjustment but I may be overly paranoid about it because I blew the speaker on my sgs3 this way. The thing there being I only made a modest change much like I did here but in hindsight it would later become apparent by the number of blow speakers people had that they had limited the volume on those release handsets to where they did because that was as much as the speaker could take.
You need root danger, I think you are on the Turbo aren't you? Maybe I'm mistaken, at any rate all you have to do is make a backup, mount the file, edit the initial values, save it and reboot.
krabman said:
The DEC should be speaker, headphones can also be adjusted in the same way which should be HPHL and HPHR. I thought we had a runner but I wasn't positive because call quality is so hit and miss around here. I'd be wary of making that large an adjustment but I may be overly paranoid about it because I blew the speaker on my sgs3 this way. The thing there being I only made a modest change much like I did here but in hindsight it would later become apparent by the number of blow speakers people had that they had limited the volume on those release handsets to where they did because that was as much as the speaker could take.
You need root danger, I think you are on the Turbo aren't you? Maybe I'm mistaken, at any rate all you have to do is make a backup, mount the file, edit the initial values, save it and reboot.
Click to expand...
Click to collapse
we don t have root on Droid turbo
Hi,
I have a (pretty much new out of the box) rooted Z3C (D5803) on stock .291 firmware. This phone has the frequently documented problem where people who call me hear a massive echo of their own voice when I have the phone in hands free or speaker mode, which renders the hands free useless. When I'm using the phone next to my head the problem doesn't happen. I have the 'microphone noise suppression' and 'slow talk' options in Call Settings disabled but have also tried enabling them - made no difference. I've also tried flashing don'tbelieve's audio mod (v25) and it made no difference.
I've read some other posts, one in particular about the z5 compact, where editing values in the mixer_path.xml file has fixed the problem, apparently by reducing the input gain of the secondary mic (noise cancellation mic near the primary speaker). This makes sense to me but I've got not idea which part of the xml file relates to that particular function and the 'dmic2' entry in the mixer_path.xml file for the z5c that is referenced in this thread doesn't seem to have an equivalent in the z3c file.
Can anyone point me in the right direction so I can start tinkering? I really love the phone in every other respect but hands free speaker mode is a pretty essential feature for me.
Thanks,
Bill.