Microphone level is too low while in call mode

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install ROM on Pantech Burst
2. Try to call someone
3. Your call mate will hardly hear a word you pronounce

What is the expected output? What do you see instead?
Microphone level adjustment setting present in settings menu or default 
microphone level be high enough

What version of the product are you using
10-20130406-UNOFFICIAL-presto

Please provide any additional information below.
Making a voice recording via voicerecorder app makes excellent records.

Please provide logcat and dmesg.

Original issue reported on code.google.com by GateKeep...@gmail.com on 12 Apr 2013 at 5:20

[GoogleCodeExporter]

its high enough.

Original comment by jie...@gmail.com on 12 Apr 2013 at 11:18

[GoogleCodeExporter]

I'd have not created a bug report if people I conversate with don't tell me 
they almost can't hear me at all. I can only use my phone for calls with 
headset now.

Original comment by GateKeep...@gmail.com on 12 Apr 2013 at 12:02

[GoogleCodeExporter]

switch on noise suppression in phone settings

Original comment by jie...@gmail.com on 12 Apr 2013 at 1:02

[GoogleCodeExporter]

Where exactly can I find this setting?

Original comment by GateKeep...@gmail.com on 12 Apr 2013 at 6:31

[GoogleCodeExporter]

open phone app, press menu button, press settings, scroll down

Original comment by jie...@gmail.com on 12 Apr 2013 at 6:46

[GoogleCodeExporter]

Gatekeep, I think its something on your end. Hope you can find a fix. My volume 
works fine and noise suppression is off.

Original comment by androidp...@gmail.com on 13 Apr 2013 at 1:15

[GoogleCodeExporter]

Infact From the start since when RIL is fixed completely, others reported they 
hear better than before . previously you need to stick your phone towards your 
mouth but not if its a little far than too i works well :) 

Original comment by trickyuj...@gmail.com on 13 Apr 2013 at 6:06

[GoogleCodeExporter]

its enough for me.

Original comment by Zorbeyd on 14 Apr 2013 at 1:06

[GoogleCodeExporter]

Ok. Someone in the Internet says it's of a bug based on incorrect audio devices 
routing while a voice call occurs. The system routes in both camera and voice 
microphones with camera mic being much more sensible so when the sys tries to 
handle autolevel of microphone sensivity it lowers global system microphone 
level and for that people can't hear me. Is that done the way I described here? 
If yes how to fix?

Original comment by GateKeep...@gmail.com on 17 Apr 2013 at 10:39

[GoogleCodeExporter]

Please provide logcat and dmesg

Original comment by jie...@gmail.com on 17 Apr 2013 at 10:56

[GoogleCodeExporter]

What's the proper ADT-tools version for linux working with this ROM? Mine can't 
see device at all even being run as root.

Original comment by GateKeep...@gmail.com on 17 Apr 2013 at 12:39

[GoogleCodeExporter]

open Terminal emulator
logcat > /sdcard0/logcat.txt
then attach it here, same for dmesg.

Original comment by jie...@gmail.com on 17 Apr 2013 at 12:48

[GoogleCodeExporter]

logcat can be truncated because I gave up on it after 2.5 hours of logcat 
output.

Original comment by GateKeep...@gmail.com on 18 Apr 2013 at 6:37

Attachments:

• logs.zip

[GoogleCodeExporter]

Any updates on bug investigation?

Original comment by GateKeep...@gmail.com on 22 Apr 2013 at 10:19

[GoogleCodeExporter]

i dont see calls on these logs

Original comment by jie...@gmail.com on 22 Apr 2013 at 10:36

[GoogleCodeExporter]

I/ActivityManager(  531): START {act=android.intent.action.CALL_PRIVILEGED 
dat=tel:xxxxxxxxxxxx flg=0x10000000 
cmp=com.android.phone/.PrivilegedOutgoingCallBroadcaster u=0} from pid 6482

what's this?

Original comment by GateKeep...@gmail.com on 22 Apr 2013 at 10:39

[GoogleCodeExporter]

this is not a call

Original comment by jie...@gmail.com on 22 Apr 2013 at 10:55

[GoogleCodeExporter]

Then the ROM version I noted at the top doesn't log calls. I have no other 
explaination. BTW how long does it usually take to 'logcat' all the logs of a 
phone?

Original comment by GateKeep...@gmail.com on 22 Apr 2013 at 11:00

[GoogleCodeExporter]

im sure it logs calls, btw no one experienced that problem, did you install any 
3th party software like call recorders or similar? did you try to make calls 
right after clean rom install, befoure apps restore? 

example of logs:
I/ActivityManager(  564): Displayed 
com.android.phone/.PrivilegedOutgoingCallBroadcaster: +198ms
D/CallController(  823): placeCall()...  intent = Intent { 
act=android.intent.action.CALL dat=tel:xxxxxxxx-xx-xx (has extras) }
D/PhoneUtils(  823): placeCall()... number: xxxxxxxxxxx, GW: null, emergency? 
false
I/AudioService(  564):  AudioFocus  requestAudioFocus() from 
AudioFocus_For_Phone_Ring_And_Calls
D/AudioHardwareInterface(  238): setMode(IN_CALL)
V/AudioHardwareMSM8660(  238): AudioStreamOutMSM8x60::setParameters() routing=1
V/AudioHardwareMSM8660(  238): set output routing 1
I/AudioHardwareMSM8660(  238): Routing audio to Handset
D/AudioHardwareMSM8660(  238): Routing audio to SND_DEVICE_NR_OFF_CT=24
V/AudioHardwareMSM8660(  238): doAudioRouteOrMute() device 18, mMode 2, 
mMicMute 1
V/AudioHardwareMSM8660(  238): do_route_audio_rpc(24, 2, 1)
I/AudioHardwareMSM8660(  238): In SND_DEVICE_NR_OFF_CT
D/AudioHardwareMSM8660(  238): new_rx = 26
D/AudioHardwareMSM8660(  238): new_tx = 27
V/AudioHardwareMSM8660(  238): Going to enable RX/TX device for voice stream

Original comment by jie...@gmail.com on 22 Apr 2013 at 11:27

[GoogleCodeExporter]

I've installed skvalex's CallRecorder. I've just disabled it and tested with a 
test call to my pal. That didn't help. Trying to logcat again through adb shell

Original comment by GateKeep...@gmail.com on 22 Apr 2013 at 11:37

[GoogleCodeExporter]

oh that would be good experience, i wanted test this app, but its not free

Original comment by jie...@gmail.com on 22 Apr 2013 at 11:49

[GoogleCodeExporter]

It's yours decision after all, but my experience is 5/5. Does what declares. 
Records calls from whatever source is available: API, kernel (root req), ALSA. 
I'd never experienced a problem with it so I didn't even think of it as a root 
of my microphone problem. Worked fine on my previous Desire HD.

Original comment by GateKeep...@gmail.com on 22 Apr 2013 at 11:59

[GoogleCodeExporter]

thats why we need to investigate that case, so i waiting logs

Original comment by jie...@gmail.com on 22 Apr 2013 at 12:01

[GoogleCodeExporter]

Got rid of that logcat usage. Here's logs

Original comment by GateKeep...@gmail.com on 22 Apr 2013 at 12:17

Attachments:

• logz.zip

[GoogleCodeExporter]

hmm, a dont see anything wrong

Original comment by jie...@gmail.com on 22 Apr 2013 at 1:10

[GoogleCodeExporter]

meanwhile the only solution that is marked as 'resolves issue' on russian 
forums (4pda.ru) is to stick camera microphone with a piece of adhesive tape 
under the back cover. 
http://4pda.ru/forum/index.php?showtopic=374748&view=findpost&p=18561064 - 
isn't the author of the post the same person as 'ninjah' on your forums?

Original comment by GateKeep...@gmail.com on 22 Apr 2013 at 1:14

[GoogleCodeExporter]

That was to manually disable the noise suppresion (audience chip).  Caused by a 
sporadic issue with the stock firmware. AFAIK it has no bearing on our custom 
firmware.  Correct me if i'm wrong.

Original comment by slayton1...@gmail.com on 22 Apr 2013 at 2:00

[GoogleCodeExporter]

If you trace back on quotations you'll find out that it was about sticking the 
camera's mic. hole first. Then on "try tricking with noise suppression". 
Nevertheless I've created this bug when NS was off on my device. Then, 
according to #3 I've turned it on. With no luck.

I'm still suffering of lack of microphone settings in all ROMs I tried (not 
only on this device).

OK. I've just tested the trick with adhesive tape. My callee says: "You sound 
louder but less plain. And totally different". I still insist the root of bug 
is in incorrect snd device routing.

I/AudioHardwareMSM8660(  222): DualMic feature Enabled
I/AudioHardwareMSM8660(  222): Routing audio to Handset
I/AudioHardwareMSM8660(  222): Routing audio to Handset with DualMike enabled

that's from my last logs. Isn't it of both microphones are routed in via voice 
call?

Original comment by GateKeep...@gmail.com on 22 Apr 2013 at 2:14

[GoogleCodeExporter]

The more I search the more it looks true:
https://github.com/R-M-S/android_hardware_qcom_audio/blob/master/msm8660/AudioHa
rdware.cpp:958 variables names are undoubtly clear of 'dualmic' stands for 
'back and main microphones' and line 1323 is the source of my previous 
message's first line of logs.

Original comment by GateKeep...@gmail.com on 22 Apr 2013 at 2:29

[GoogleCodeExporter]

https://github.com/R-M-S/android_hardware_qcom_audio/blob/master/msm8660/AudioHa
rdware.cpp#L958 fixed the URL

Original comment by GateKeep...@gmail.com on 22 Apr 2013 at 2:34

[GoogleCodeExporter]

why are you pointing at dualmic feature? you checked audio with enabled and 
disabled dualmic feature, and you have same result. And they are work totaly 
different.
and noise suppression is not working now. Dualmic - it just only flag, with it 
help, we decide in what audio path route audio. And now with dualmic:true it 
route sound to default(SoCA)(something wrong with code, i didnt check it yet). 
with dualmic:false it uses pantech(NR - off) audio routes.  

Original comment by jie...@gmail.com on 22 Apr 2013 at 3:16

[GoogleCodeExporter]

did you use noise suppression on stock rom?

Original comment by jie...@gmail.com on 22 Apr 2013 at 3:22

[GoogleCodeExporter]

I've rooted and reflashed my device just after unpacked the box I've received 
at post office, so no, I did try neither NS nor w/o NS voice calls.

> you checked audio with enabled and disabled dualmic feature
Not sure of that. Just accepting as the truth dualmic stands for wheter NR code 
is applied, I assume you point my tries to turn NS on and off. I'll try to 
logcat both of the setting states tomorrow to ensure.

Original comment by GateKeep...@gmail.com on 22 Apr 2013 at 4:54

[GoogleCodeExporter]

please wait until i compile rom with working NS...pm me on 4pda, i will give 
you a link, when it be ready

Original comment by jie...@gmail.com on 22 Apr 2013 at 5:00

[GoogleCodeExporter]

pm'ed (if I guessed you're ninjah83 right)

Original comment by GateKeep...@gmail.com on 23 Apr 2013 at 9:15

[GoogleCodeExporter]

yes, i saw your message, rom isnt ready yet

Original comment by jie...@gmail.com on 23 Apr 2013 at 9:19

[GoogleCodeExporter]

Attached a sample incoming call from my wife. My voice is undistinquishable 
from the noise. The same comes to the line. Recorded by callrecorder in kernel 
mode.

Original comment by GateKeep...@gmail.com on 24 Apr 2013 at 5:57

Attachments:

• samplerec.wav

[GoogleCodeExporter]

Personal build of ROM haven't resolved the issue.

Original comment by GateKeep...@gmail.com on 26 Apr 2013 at 7:41

[GoogleCodeExporter]

I've installed ALSA on the phone. It seems to be working. What info from ALSA 
could be useful being provided here?

Original comment by GateKeep...@gmail.com on 26 Apr 2013 at 7:50

[GoogleCodeExporter]

What you did?

Original comment by jie...@gmail.com on 26 Apr 2013 at 8:45

[GoogleCodeExporter]

I've installed skvalex's AlsaMixer from Play Market. It installs userlevel 
binaries that can provide info or change parameters of Alsa devices found:

alsa_amixer
alsa_ctl
alsa_aplay

It also could have installed some libraries, I didn't investigate for full list 
of changes it does to the system. So, do you need any info from alsa_amixer?

Original comment by GateKeep...@gmail.com on 26 Apr 2013 at 8:52

[GoogleCodeExporter]

is it opensource? Link?

could you provide logcat and dmesg?

Original comment by jie...@gmail.com on 26 Apr 2013 at 9:04

• Added labels: Audio

[GoogleCodeExporter]

https://play.google.com/store/apps/details?id=com.skvalex.alsamixer

Can't say if it's opensource. If you want logcat for the installation process - 
I haven't one cause I didn't logcat the installation process. Here's dmesg

Original comment by GateKeep...@gmail.com on 26 Apr 2013 at 9:59

Attachments:

• dmesg.out

[GoogleCodeExporter]

thank you for dmesg, but i need also logcat while call..

Original comment by jie...@gmail.com on 26 Apr 2013 at 10:03

[GoogleCodeExporter]

Test call with logcat (did it with `adb logcat > logcat.log` hence SIGPIPE in 
the middle of log, I guess)

Original comment by GateKeep...@gmail.com on 26 Apr 2013 at 10:34

Attachments:

• logcat.log

[GoogleCodeExporter]

Any updates?

Original comment by GateKeep...@gmail.com on 4 May 2013 at 9:16

[GoogleCodeExporter]

im working on it now

Original comment by jie...@gmail.com on 16 May 2013 at 6:28

[GoogleCodeExporter]

https://docs.google.com/file/d/0BzovpbT5_xxBWXRLazhKR2ctQ3M/edit

check this build plz

Original comment by jie...@gmail.com on 19 May 2013 at 8:49

[GoogleCodeExporter]

Same problem even with this build

Original comment by GateKeep...@gmail.com on 22 May 2013 at 7:02

[GoogleCodeExporter]

and check this one
https://docs.google.com/file/d/0BzovpbT5_xxBOVBzbUdjT1BucFU/edit

with/without Noise Suppression

Original comment by jie...@gmail.com on 22 May 2013 at 7:40