Thank youhoaw do i debug my phone

Regarding Android: it was a very long time since those parts were written but as I recall it we had to go for a larger buffer size than 10 to make it work back then. My guess is that you could here glitches on some devices using 10 and that 20 helped. I don't know how essential this assumption is today since the Android audio layer has changed so much since the initial implementation in Chrome.

My recommendation is to: try to remove special parts for Android and use same approach as on other OS:es. Only use special cases if still really needed. 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/81c7ecbbe69b2be50bf2a6a30b4e88d72b09e249

commit 81c7ecbbe69b2be50bf2a6a30b4e88d72b09e249
Author: miu <miu@chromium.org>
Date: Tue Aug 16 20:59:18 2016

Use LocalMediaStreamAudioSource for screen-casting use cases.

Adds a new MediaStreamAudioSource implementation for taking input from a
local source, and passing it directly to sinks without going through the
WebRTC MediaStreamAudioProcessor. This new implementation will be used
by the screen casting use cases (e.g., tab or desktop audio capture).

Before this change, even if the MediaStreamAudioProcessor was disabled,
a rather large graph of objects, extra threads (for libjingle), and
additional audio buffers were being created; with audio being copied
into and out of the buffers; even though no processing was being done.

BUG= 577881 ,638081

Review-Url: https://codereview.chromium.org/2219933003
Cr-Commit-Position: refs/heads/master@{#412333}

[modify] https://crrev.com/81c7ecbbe69b2be50bf2a6a30b4e88d72b09e249/content/content_renderer.gypi
[modify] https://crrev.com/81c7ecbbe69b2be50bf2a6a30b4e88d72b09e249/content/public/common/media_stream_request.cc
[modify] https://crrev.com/81c7ecbbe69b2be50bf2a6a30b4e88d72b09e249/content/public/common/media_stream_request.h
[add] https://crrev.com/81c7ecbbe69b2be50bf2a6a30b4e88d72b09e249/content/renderer/media/local_media_stream_audio_source.cc
[add] https://crrev.com/81c7ecbbe69b2be50bf2a6a30b4e88d72b09e249/content/renderer/media/local_media_stream_audio_source.h
[modify] https://crrev.com/81c7ecbbe69b2be50bf2a6a30b4e88d72b09e249/content/renderer/media/media_stream_audio_processor.cc
[modify] https://crrev.com/81c7ecbbe69b2be50bf2a6a30b4e88d72b09e249/content/renderer/media/media_stream_audio_processor.h
[modify] https://crrev.com/81c7ecbbe69b2be50bf2a6a30b4e88d72b09e249/content/renderer/media/user_media_client_impl.cc
[modify] https://crrev.com/81c7ecbbe69b2be50bf2a6a30b4e88d72b09e249/content/renderer/media/webrtc/processed_local_audio_source.cc

[Re-triage] This seems to be still valid. Does anyone feel like picking it up, or know the answer to question 1 in the original report?

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Henrik, do you think we should close this one?

Don't know the details well enough to comment given all changes that are done in this area. Asking olka@ for confirmation instead.

That code seems to be mostly unchanged, including Android-specific part.