Issue 29356 in chromium-os: Microphone: Microphone doesn't work for video chats.

6 views
Skip to first unread message

chrom...@googlecode.com

unread,
Apr 12, 2012, 1:39:47 AM4/12/12
to chromium...@chromium.org
Status: New
Owner: ----
Labels: ConOps-Issue

New issue 29356 by feedback...@gmail.com: Microphone: Microphone doesn't
work for video chats.
http://code.google.com/p/chromium-os/issues/detail?id=29356

http://feedback.corp.google.com/#/Cluster/2569904

Description:
Mic doesn't work for video chats.

Number of confirmed reports:
5

Total number of reports:
5

chrom...@googlecode.com

unread,
Apr 12, 2012, 3:27:26 AM4/12/12
to chromium...@chromium.org

Comment #1 on issue 29356 by dgr...@chromium.org: Microphone: Microphone

Mic doesn't work in Gtalk on ZGB. arecord works fine, so does google voice
search. Everything works on Alex.

chrom...@googlecode.com

unread,
Apr 12, 2012, 4:44:45 PM4/12/12
to chromium...@chromium.org
Updates:
Status: Assigned
Owner: dgr...@chromium.org
Labels: Area-AudioVideo Mstone-19

Comment #2 on issue 29356 by arsc...@chromium.org: Microphone: Microphone

(No comment was entered for this change.)

chrom...@googlecode.com

unread,
Apr 12, 2012, 4:46:25 PM4/12/12
to chromium...@chromium.org
Updates:
Labels: Pri-1

Comment #3 on issue 29356 by arsc...@chromium.org: Microphone: Microphone

chrom...@googlecode.com

unread,
Apr 12, 2012, 6:00:38 PM4/12/12
to chromium...@chromium.org

Comment #4 on issue 29356 by rajeevku...@chromium.org: Microphone:
Microphone doesn't work for video chats.
http://code.google.com/p/chromium-os/issues/detail?id=29356

Noticed this with R19 build "2046.30.0" on ZGB:

1.) Internal mic seems muted with google talk.
2.) External mic works fine with google talk though.
3.) But, the internal mic responds fine to arecord.


chrom...@googlecode.com

unread,
Apr 12, 2012, 6:03:58 PM4/12/12
to chromium...@chromium.org
Updates:
Cc: a...@google.com

Comment #5 on issue 29356 by dgr...@chromium.org: Microphone: Microphone

+ajm

I did a capture of the talk plugin when this was happening. Any ideas?

Thanks,

Dylan

Attachments:
echo.dump 176 KB

chrom...@googlecode.com

unread,
Apr 12, 2012, 6:09:13 PM4/12/12
to chromium...@chromium.org

Comment #6 on issue 29356 by a...@google.com: Microphone: Microphone

The capture-side files are empty, meaning capturing isn't occurring at all.

For Googlers, a plugin log file should always be created. Look in
$HOME/.config/google-googletalkplugin. You should find file(s) like
gtalkplugin-cXXXX.log.bz2. Upload the one corresponding to the call
(presumably the latest).

chrom...@googlecode.com

unread,
Apr 12, 2012, 6:21:47 PM4/12/12
to chromium...@chromium.org

Comment #7 on issue 29356 by dgr...@chromium.org: Microphone: Microphone

Not sure which errors in there are important, but there seem to be a few
about handle_capture being NULL.

Attachments:
gtalkplugin-c2051245270.log.bz2 5.9 KB

chrom...@googlecode.com

unread,
Apr 13, 2012, 12:14:28 AM4/13/12
to chromium...@chromium.org
Updates:
Cc: je...@chromium.org

Comment #8 on issue 29356 by angel...@chromium.org: Microphone: Microphone

(No comment was entered for this change.)

chrom...@googlecode.com

unread,
Apr 16, 2012, 10:22:50 PM4/16/12
to chromium...@chromium.org

Comment #9 on issue 29356 by a...@google.com: Microphone: Microphone

The first errors about PulseAudio are fine, it just means we're falling
back to ALSA. I think the "handle_capture is now set to NULL" error is
actually erroneous; from the code it looks like it shouldn't be an error
but an info message.

The handle_capture error indicates recording is being stopped a few times,
which might indicate an issue. On the other hand we can call start/stop to
test devices so this might be nothing. I don't see anything else in the log
which could indicate the source of the problem.

We could have one of our TSEs repro and investigate this further. Dylan,
can you CC punya...@webrtc.org on this? Do you have a ZGB he could borrow
for testing?

chrom...@googlecode.com

unread,
Apr 16, 2012, 11:55:02 PM4/16/12
to chromium...@chromium.org
Updates:
Cc: punyabr...@webrtc.org

Comment #10 on issue 29356 by dgr...@chromium.org: Microphone: Microphone

Added punya...@webrtc.org. I'm sure we can dig up a ZGB for him to test
with.

chrom...@googlecode.com

unread,
Apr 17, 2012, 1:56:59 PM4/17/12
to chromium...@chromium.org
Updates:
Cc: kr...@chromium.org

Comment #11 on issue 29356 by rajeevku...@chromium.org: Microphone:

Microphone doesn't work for video chats.
http://code.google.com/p/chromium-os/issues/detail?id=29356

(No comment was entered for this change.)

chrom...@googlecode.com

unread,
Apr 17, 2012, 7:28:36 PM4/17/12
to chromium...@chromium.org

Comment #13 on issue 29356 by punyabr...@webrtc.org: Microphone: Microphone

I have now been able to reproduce the same issue after receiving a ChromeOS
canary update. I am currently running:

Version 20.0.1105.0 canary
Platform 2153.0.0 (Official Build) canary-channel x86-zgb_he
Firmware ZGB.03.61.0740.0062G7.010

I do not know how big of a delta it is between this version and the
previous working version, but it would be helpful if someone could
determine any CLs that might have changed to trigger this. The Gtalk plugin
when it was working before and when it stopped working now is the same at
2.8.5 but that could mean that something has changed to uncover something
in the talk plugin which would be helpful to find. I will keep looking into
this to see if our logs shed any more light on this.

/Ray

/Ray

chrom...@googlecode.com

unread,
Apr 18, 2012, 8:22:45 PM4/18/12
to chromium...@chromium.org

chrom...@googlecode.com

unread,
Apr 20, 2012, 3:22:59 AM4/20/12
to chromium...@chromium.org
Updates:
Labels: ReleaseBlock-Beta

Comment #15 on issue 29356 by dgr...@chromium.org: Microphone: Microphone

(No comment was entered for this change.)

chrom...@googlecode.com

unread,
Apr 20, 2012, 7:37:24 PM4/20/12
to chromium...@chromium.org

Comment #16 on issue 29356 by punyabr...@webrtc.org: Microphone: Microphone

I was able to run our internal test application and reproduce the issue
(uploaded the logfile from a loopback test entitled webrtc.txt). We seem to
be able to setup everything normally (no error is reported when choosing
the default device for capture) but once the call is started, we see
numerous logs noting that our capture thread has timed-out waiting for
samples from the soundcard. I see this on the playback side also even
though the playback is working well but this is most likely because this
was in a loopback call.

caputre snd_pcm_wait timeout //log that we see noting that our capture
process has timed-out as it has not received any samples from the soundcard.

This will take further investigation. Unfortunately I will be out of the
office next week until Thursday. But can anyone double check if anything
has changed with respect to the soundcard drivers within the versions where
it was working and not working.

Another datapoint might be good to see what the logs look like when it is
actually working to see.

Attachments:
webrtc.txt 2.6 MB

chrom...@googlecode.com

unread,
Apr 21, 2012, 4:20:45 PM4/21/12
to chromium...@chromium.org

Comment #17 on issue 29356 by dgr...@chromium.org: Microphone: Microphone

Ray, can you record the same log while using the external mic? You can get
an analog headset that works with ZGB at tech stop.

It also looks like the code in audio_device_alsa_linux will ensure there
are capture timeouts if it gets back a buffer and period size > 5ms. It is
getting a 46.5 mS buffer in this run, and telling snd_pcm_wait to timeout
after 5ms, not sure that's what's causing the problem, you might have to
give me a hand building GTalk on Monday so I can dig a little deeper.

Thanks.

chrom...@googlecode.com

unread,
Apr 23, 2012, 2:06:39 PM4/23/12
to chromium...@chromium.org

Comment #18 on issue 29356 by vikasmar...@webrtc.org: Microphone:
Microphone doesn't work for video chats.
http://code.google.com/p/chromium-os/issues/detail?id=29356

I will try with an external mic to compare the logs.

chrom...@googlecode.com

unread,
Apr 25, 2012, 12:56:24 PM4/25/12
to chromium...@chromium.org

Comment #19 on issue 29356 by dgr...@chromium.org: Microphone: Microphone
Any luck with log comparing?

chrom...@googlecode.com

unread,
Apr 25, 2012, 11:42:26 PM4/25/12
to chromium...@chromium.org

Comment #20 on issue 29356 by vikasmar...@google.com: Microphone:
Microphone doesn't work for video chats.
http://code.google.com/p/chromium-os/issues/detail?id=29356

Hi Dylan,

I have had no luck so far comparing the working versus non-working logs. I
plan to add trace in the alsa file to see if i can narrow down further.

regards.
Vikas

chrom...@googlecode.com

unread,
Apr 30, 2012, 10:14:30 AM4/30/12
to chromium...@chromium.org

Comment #21 on issue 29356 by dgr...@chromium.org: Microphone: Microphone
Ray, will you have time to look at this with your new position? (congrats
BTW). Or is there someone else who can help out. We've really tight
against the Beta and now Stable build for R19, and this would have to hold
it up.

chrom...@googlecode.com

unread,
Apr 30, 2012, 4:24:59 PM4/30/12
to chromium...@chromium.org

Comment #22 on issue 29356 by punyabr...@google.com: Microphone: Microphone
Thanks Dylan. I will look into it further today and get others involved if
I don't make much progress. What I have found so far is that the following
call in our ALSA implmentation in the function where our recording thread
runs (RecThreadProcess( ) in http://goo.gl/w76Zr)

//return a positive number of frames ready otherwise a negative error code
avail_frames = LATE(snd_pcm_avail_update)(_handleRecord);

is returning with a 0. We are not getting any samples from the soundcard.
As you have verified "arecord -Ddefault -c 2 -f S16_LE -r 48000 test.pcm"
seems to work find where I am able to play the recorded file using "aplay
test.pcm".

I will keep investigating.

Ray





chrom...@googlecode.com

unread,
May 1, 2012, 9:03:40 PM5/1/12
to chromium...@chromium.org

Comment #23 on issue 29356 by rajeevku...@chromium.org: Microphone:
Microphone doesn't work for video chats.
http://code.google.com/p/chromium-os/issues/detail?id=29356

Noticed this today with "gtalk", after adding onto build "2227.0.0" on all
devices.

1.) Pressing (F8) mute key for speakers mutes audio from the mic briefly,
but then it seems to unmute. One can still hear input from external mic.

2.) But, playing an audio file or audio/video link & pressing the mute key
(F8) works fine, no audio is heard.

3.) ZGB internal mic is still unresponsive as before.


chrom...@googlecode.com

unread,
May 3, 2012, 5:02:29 PM5/3/12
to chromium...@chromium.org
Updates:
Cc: xi...@chromium.org

Comment #24 on issue 29356 by xi...@chromium.org: Microphone: Microphone
Ray,

Could you please try moving the snd_pcm_wait code after the snd_pcm_readi?
More explicitly, try snd_pcm_readi() even though snd_pcm_avail_update
returns 0.
And please also tell me what device name we are using to open the device?


chrom...@googlecode.com

unread,
May 3, 2012, 9:30:25 PM5/3/12
to chromium...@chromium.org

Comment #25 on issue 29356 by punyabr...@google.com: Microphone: Microphone
Just to double check, this is what I did below but to no avail:
//return a positive number of frames ready otherwise a negative error code
avail_frames = LATE(snd_pcm_avail_update)(_handleRecord);
if (avail_frames < 0)
{
WEBRTC_TRACE(kTraceError, kTraceAudioDevice, _id,
"capture snd_pcm_avail_update error: %s",
LATE(snd_strerror)(avail_frames));
ErrorRecovery(avail_frames, _handleRecord);
UnLock();
return true;
}
//else if (avail_frames == 0)
//{ // no frame is available now
// UnLock();

//maximum time in milliseconds to wait, a negative value means
infinity
//err = LATE(snd_pcm_wait)(_handleRecord,
// ALSA_CAPTURE_WAIT_TIMEOUT);
// err = LATE(snd_pcm_wait)(_handleRecord,
// -1);
// if (err == 0) //timeout occured
// WEBRTC_TRACE(kTraceStream, kTraceAudioDevice, _id,
// "caputre snd_pcm_wait timeout");

// return true;
//}

if (static_cast<WebRtc_UWord32>(avail_frames) > _recordingFramesLeft)
avail_frames = _recordingFramesLeft;


With respect to your question, which device name we are using to open the
device? I am assuming "default". Here are some valid logs:

AudioMixerManagerLinuxALSA::OpenMicrophone(name=default)
DEBUGINFO ; (10:40:18:562 | 0) AUDIO DEVICE: 1 99; 4027;
snd_mixer_attach(_inputMixerHandle, default)
DEBUGINFO ; (10:40:18:563 | 1) AUDIO DEVICE: 1 99; 4027;
Mic element found
DEBUGINFO ; (10:40:18:563 | 0) AUDIO DEVICE: 1 99; 4027;
Capture element set
DEBUGINFO ; (10:40:18:563 | 0) AUDIO DEVICE: 1 99; 4027;
the input mixer device is now open (0x10eb7f0)



APICALL ; (10:40:29:659 | 0) VOICE: 1 99; 4027;
SetRecordingDevice(index=0, recordingChannel=2)
DEBUGINFO ; (10:40:29:683 | 278) AUDIO DEVICE: 1 99; 4027;
Enum device 1 - default:CARD=Intel
DEBUGINFO ; (10:40:29:683 | 0) AUDIO DEVICE: 1 99; 4027;
Enum device 2 - front:CARD=Intel,DEV=0
DEBUGINFO ; (10:40:29:683 | 0) AUDIO DEVICE: 1 99; 4027;
Enum device 3 - surround40:CARD=Intel,DEV=0
DEBUGINFO ; (10:40:29:683 | 0) AUDIO DEVICE: 1 99; 4027;
Enum device 4 - surround41:CARD=Intel,DEV=0
DEBUGINFO ; (10:40:29:683 | 0) AUDIO DEVICE: 1 99; 4027;
Enum device 5 - surround50:CARD=Intel,DEV=0
DEBUGINFO ; (10:40:29:683 | 0) AUDIO DEVICE: 1 99; 4027;
Enum device 6 - surround51:CARD=Intel,DEV=0
DEBUGINFO ; (10:40:29:683 | 0) AUDIO DEVICE: 1 99; 4027;
Enum device 7 - surround71:CARD=Intel,DEV=0
DEBUGINFO ; (10:40:29:683 | 0) AUDIO DEVICE: 1 99; 4027;
number of availiable audio input devices is 8

/Ray


chrom...@googlecode.com

unread,
May 4, 2012, 1:30:03 AM5/4/12
to chromium...@chromium.org

Comment #26 on issue 29356 by or...@chromium.org: Microphone: Microphone
Is this the same issue as 30524 (no mic or camera in hangouts on 2046.68.0
zgb)?

chrom...@googlecode.com

unread,
May 4, 2012, 7:33:14 AM5/4/12
to chromium...@chromium.org

Comment #27 on issue 29356 by xi...@chromium.org: Microphone: Microphone
Ray,

Two things to try out:
1) Change the code:
else if (avail_frames == 0) {
avail_frames = _recordingFramesLeft;
}

while (true) {
frames = LATE(snd_pcm_readi)(_handleRecord, buffer, avail_frames);
if (frame < 0) {
UnLock();
return true;
} else if (frames < avail_frames) {
// Put a log here.
err = LATE(snd_pcm_wait)(_handleRecord, ALSA_CAPTURE_WAIT_TIMEOUT);
if (err <= 0) {
// Log the timeout.
}
avail_frames -= frames;
} else {
// frames == avail_frames
break;
}
}


2) hack into the AudioDeviceLinuxALSA::StereoRecordingIsAvailable(), and
force it to return false, so we can try out mono recording.

chrom...@googlecode.com

unread,
May 4, 2012, 8:39:33 PM5/4/12
to chromium...@chromium.org

Comment #28 on issue 29356 by punyabr...@google.com: Microphone: Microphone
Sorry, no go. I have uploaded the alsa source file just in case I
misunderstood your instructions for you to double check.
/Ray

Attachments:
audio_device_alsa_linux.cc 61.1 KB

chrom...@googlecode.com

unread,
May 7, 2012, 10:02:39 PM5/7/12
to chromium...@chromium.org
Updates:
Cc: jhorw...@chromium.org

Comment #29 on issue 29356 by puneets...@chromium.org: Microphone:
Microphone doesn't work for video chats.
http://code.google.com/p/chromium-os/issues/detail?id=29356

Issue 30524 has been merged into this issue.

chrom...@googlecode.com

unread,
May 8, 2012, 6:00:14 AM5/8/12
to chromium...@chromium.org

Comment #30 on issue 29356 by xi...@chromium.org: Microphone: Microphone
Ray,
Please forget the code, snd_pcm_avail_update returns 0 is a valid case
since we are using very aggressive polling, and timeout happens due to no
data. They should not be the problems.

Sorry that I did not have time to check the logs carefully, but when I
looked at the webrtc.txt in #16, I did see the recording callbacks
RecordedDataIsAvailable(), which indicates that it gets data from the
soundcard.

Too bad that I don't have any machine to test.

Ray, could you please use StartRecordingMicrophone() to see if it does
recording?
Meanwhile, use StartPlayingFileAsMicrophone() to narrow down the issue more.

BR,
/SX

chrom...@googlecode.com

unread,
May 8, 2012, 1:52:17 PM5/8/12
to chromium...@chromium.org

Comment #31 on issue 29356 by dgr...@chromium.org: Microphone: Microphone
Could this be analog-AGC related? The ZGB has a separate "Internal Mix
Boost" ALSA control which is separate from "Mic Boost". "Mic Boost"
applies to a headset (which works), and "Internal Mic Boost" applies to the
build in Mic (doesn't work).

chrom...@googlecode.com

unread,
May 8, 2012, 2:00:10 PM5/8/12
to chromium...@chromium.org

Comment #32 on issue 29356 by xi...@chromium.org: Microphone: Microphone
It is pretty easy to disable AGC to verify it, Ray, do you have time to do
it?


BR,

/SX

chrom...@googlecode.com

unread,
May 9, 2012, 1:53:36 AM5/9/12
to chromium...@chromium.org

Comment #36 on issue 29356 by punyabr...@google.com: Microphone: Microphone
I did not get a chance to try this today but will do so tomorrow (Wed).
Thanks. /Ray

chrom...@googlecode.com

unread,
May 9, 2012, 2:37:56 PM5/9/12
to chromium...@chromium.org

Comment #38 on issue 29356 by or...@chromium.org: Microphone: Microphone
Any news? Mic doesn't work for hangouts and gtalk.

chrom...@googlecode.com

unread,
May 9, 2012, 3:28:02 PM5/9/12
to chromium...@chromium.org

Comment #39 on issue 29356 by punyabr...@google.com: Microphone: Microphone
Yes, we got another set of AEC debug recordings and, unlike last time, we
have a near-end signal recorded. In the first set of AEC logs, the near-end
signals were all zero.
But currently, the signal is completely zero at the output of our AEC so we
are still investigating.

chrom...@googlecode.com

unread,
May 10, 2012, 1:36:01 PM5/10/12
to chromium...@chromium.org

Comment #40 on issue 29356 by xi...@chromium.org: Microphone: Microphone
I think I know why, from the log:
AudioMixerManagerLinuxALSA::MicrophoneVolume() => vol=31
VoEBaseImpl::RecordedDataIsAvailable(nSamples=480, nBytesPerSample=4,
nChannels=2, samplesPerSec=48000, totalDelayMS=76, clockDrift=0,
currentMicLevel=31)
MaxMicrophoneVolume Microphone hardware volume range, min: 0, max: 31

It looks like the OS reports a max microphone volume as 31, which is
completely wrong. The valid range in linux is 0 - 65535. A value of 31 is
close to being muted.

Dylan, any idea? can we run alsa-mixer in the terminal in chromebook?

BR,
-SX

chrom...@googlecode.com

unread,
May 10, 2012, 1:38:53 PM5/10/12
to chromium...@chromium.org

Comment #41 on issue 29356 by a...@google.com: Microphone: Microphone
That know that range is typical for PulseAudio Shijing; is it the same for
ALSA?

Ray and I are going to dig into it this afternoon.

chrom...@googlecode.com

unread,
May 10, 2012, 2:13:20 PM5/10/12
to chromium...@chromium.org

Comment #42 on issue 29356 by xi...@chromium.org: Microphone: Microphone
It might depends a bit on the devices. But usually it is 65535 for ALSA too
if I don't remember wrong. I may be wrong here, please double check it.

chrom...@googlecode.com

unread,
May 10, 2012, 3:17:01 PM5/10/12
to chromium...@chromium.org

Comment #43 on issue 29356 by dgr...@chromium.org: Microphone: Microphone
What units is 65535 in?

On ZGB, R19, the range for "Capture Volume"is 0 - 31, which maps
non-linearly to -16.5 to +30 dB of gain.

The "Internal Mic Boost" control ranges from 0 to 3, each step is 12dB
0 min to +36dB max.

chrom...@googlecode.com

unread,
May 10, 2012, 3:21:27 PM5/10/12
to chromium...@chromium.org

Comment #44 on issue 29356 by dgr...@chromium.org: Microphone: Microphone
For R20+ I've got the new audio server running and will re-map this into
one control. but for R19 we're stuck with this weirdness.

chrom...@googlecode.com

unread,
May 10, 2012, 3:57:07 PM5/10/12
to chromium...@chromium.org

Comment #45 on issue 29356 by or...@chromium.org: Microphone: Microphone
When did this issue started? Does ZGB mic works on R18?

chrom...@googlecode.com

unread,
May 10, 2012, 4:41:50 PM5/10/12
to chromium...@chromium.org

Comment #46 on issue 29356 by dgr...@chromium.org: Microphone: Microphone
This is a new breakage in R19. R18 worked. The alsa controls available
are different in R19 as it's based on kernel 3.2

chrom...@googlecode.com

unread,
May 10, 2012, 5:16:46 PM5/10/12
to chromium...@chromium.org

Comment #47 on issue 29356 by punyabr...@google.com: Microphone: Microphone
Dylan - I don't know if this also lines up with your observations but I
noticed that it was working on Version 20.0.1087.0 canary but stopped
working Version 20.0.1105.0 canary

(Working version)
Version 20.0.1087.0 canary
Platform 2061.0.0 (Official Build) canary-channel x86-zgb
Firmware ZGB.03.61.0740.0062G7.010

(Stopped working version)
Version 20.0.1105.0 canary
Platform 2153.0.0 (Official Build) canary-channel x86-zgb_he
Firmware ZGB.03.61.0740.0062G7.010

/Ray

chrom...@googlecode.com

unread,
May 10, 2012, 5:34:12 PM5/10/12
to chromium...@chromium.org

Comment #48 on issue 29356 by dgr...@chromium.org: Microphone: Microphone
Those are R20 builds, it seems broken there too, interesting that it worked
for a few builds...

R19 builds are numbered 2046.XX.0 that's where we need it fixed ASAP.

chrom...@googlecode.com

unread,
May 10, 2012, 10:00:57 PM5/10/12
to chromium...@chromium.org

Comment #49 on issue 29356 by a...@google.com: Microphone: Microphone
Ray and I think we discovered the root problem today. We open audio devices
in stereo by default, even if it's a true mono device. When using a mono
codec (all the time, at the moment) we downmix before processing.

The problem is that ALSA is providing stereo channels which are near exact
inverses of each other! When we downmix (add the signals) we get a nearly
zero output. Presumably this weird stereo behavior is only happening in the
ChromeOS versions that exhibit the no-audio problem.

I've attached example left and right audio channels (16 kHz), and an image
which shows the inverted signals.

Dylan, any idea what could be causing this?

Attachments:
input_left.pcm 171 KB
input_right.pcm 171 KB
inverted.png 21.0 KB

chrom...@googlecode.com

unread,
May 10, 2012, 11:01:40 PM5/10/12
to chromium...@chromium.org

Comment #50 on issue 29356 by dgr...@chromium.org: Microphone: Microphone
I verified that is what alsa is returning. And on kernel 3.0, Left and
Right were identical. Now to figure out why...

chrom...@googlecode.com

unread,
May 10, 2012, 11:55:07 PM5/10/12
to chromium...@chromium.org

Comment #51 on issue 29356 by dgr...@chromium.org: Microphone: Microphone
Fix here: https://gerrit.chromium.org/gerrit/#change,22193

chrom...@googlecode.com

unread,
May 11, 2012, 1:13:34 AM5/11/12
to chromium...@chromium.org

Comment #52 on issue 29356 by a...@google.com: Microphone: Microphone
Doesn't look like the right link Dylan. (I was curious to see what the fix
was)

chrom...@googlecode.com

unread,
May 11, 2012, 1:17:35 AM5/11/12
to chromium...@chromium.org

Comment #53 on issue 29356 by dgr...@chromium.org: Microphone: Microphone
Correct link: https://gerrit.chromium.org/gerrit/#change,22440



chrom...@googlecode.com

unread,
May 11, 2012, 1:18:37 AM5/11/12
to chromium...@chromium.org

Comment #54 on issue 29356 by dgr...@chromium.org: Microphone: Microphone
Not an exciting fix, just updated to coefficients for the mic.

chrom...@googlecode.com

unread,
May 11, 2012, 1:39:10 AM5/11/12
to chromium...@chromium.org
Updates:
Labels: Merge-Approved

Comment #55 on issue 29356 by or...@google.com: Microphone: Microphone
Merge approved for R19

chrom...@googlecode.com

unread,
May 11, 2012, 11:22:57 AM5/11/12
to chromium...@chromium.org
Updates:
Status: Fixed

Comment #56 on issue 29356 by or...@chromium.org: Microphone: Microphone
Was merged to R19 with:
https://gerrit.chromium.org/gitweb/?p=chromiumos/third_party/kernel.git;a=commitdiff;h=8a330e4

Please re-open if this patch did not fix the problem.

chrom...@googlecode.com

unread,
May 11, 2012, 3:04:28 PM5/11/12
to chromium...@chromium.org
Updates:
Status: Verified

Comment #57 on issue 29356 by rajeevku...@chromium.org: Microphone:
Microphone doesn't work for video chats.
http://code.google.com/p/chromium-os/issues/detail?id=29356

Verified build "2046.88.0" on ZGB & ZGB he.

Noticed both internal mic & external mic work fine with gtalk.


chrom...@googlecode.com

unread,
May 11, 2012, 3:09:28 PM5/11/12
to chromium...@chromium.org

Comment #58 on issue 29356 by rohi...@chromium.org: Microphone: Microphone
Dylan, is this also fixed on R20?

chrom...@googlecode.com

unread,
May 11, 2012, 4:00:25 PM5/11/12
to chromium...@chromium.org

Comment #59 on issue 29356 by dgr...@chromium.org: Microphone: Microphone
Not merge to R20 yet. Just landed in ToT.

chrom...@googlecode.com

unread,
May 11, 2012, 4:05:51 PM5/11/12
to chromium...@chromium.org
Updates:
Status: Assigned
Labels: -Merge-Approved Mstone-20

Comment #60 on issue 29356 by rohi...@chromium.org: Microphone: Microphone
Thanks Dylan!

chrom...@googlecode.com

unread,
May 14, 2012, 3:51:31 PM5/14/12
to chromium...@chromium.org
Updates:
Status: Fixed

Comment #61 on issue 29356 by dgr...@chromium.org: Microphone: Microphone
Merged to R19 and R20.

chrom...@googlecode.com

unread,
May 16, 2012, 3:57:51 PM5/16/12
to chromium...@chromium.org

Comment #62 on issue 29356 by rohi...@chromium.org: Microphone: Microphone
Verified with R19 build 2046.95.0 / 19.0.1084.48 on ZGB.

Will mark this issue verified after verifying it on R20 and R21.

chrom...@googlecode.com

unread,
May 23, 2012, 1:36:59 PM5/23/12
to chromium...@chromium.org
Updates:
Status: Verified

Comment #63 on issue 29356 by rohi...@chromium.org: Microphone: Microphone
R20 2268.23.0 / 20.0.1132.5

Verified using G+ hangout.

chrom...@googlecode.com

unread,
Jul 1, 2012, 10:02:25 PM7/1/12
to chromium...@chromium.org
Updates:
Cc: blumb...@chromium.org

Comment #67 on issue 29356 by ed...@chromium.org: Microphone: Microphone
Mic is still not working on R20 beta on Lumpy with Google+ Hangouts or
Gmail Call Phones. Seems to work on first boot, but never works after
resume from sleep or after first use. This is *not* working on 2268.105 /
20.0.1132.54.

Google Chrome 20.0.1132.54 (Official Build 144397) beta
Platform 2268.105.0 (Official Build) beta-channel lumpy

chrom...@googlecode.com

unread,
Jul 1, 2012, 11:25:56 PM7/1/12
to chromium...@chromium.org

Comment #68 on issue 29356 by rohi...@chromium.org: Microphone: Microphone
This issue is for ZGB. For Lumpy, please add your comments on
crosbug.com/p/10399 . Thanks!

Reply all
Reply to author
Forward
0 new messages