We currently have a UMA to return the hardware buffer size on Android. But this doesn't take into account whether Android supports the legacy path, low-latency path or pro-audio path. It would be really good to keep track of how often we get these paths, and also return the buffer sizes for each of these paths.
Additionally, if we could determine whether we're connecting to, say, usb or bluetooth headsets, that would be great in figuring out if the latencies are just horribly bad or if they're justifiably bad because it's a bluetooth headset.
Comment 1 by sheriffbot@chromium.org
, Jan 19 2018Status: Untriaged (was: Available)