New issue
Advanced search Search tips

Issue 682442 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Feb 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Add UMA to measure latency options available on Android with corresponding buffer sizes

Project Member Reported by rtoy@chromium.org, Jan 18 2017

Issue description

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.
 
Project Member

Comment 1 by sheriffbot@chromium.org, Jan 19 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
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. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

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

Comment 2 by rtoy@chromium.org, Feb 6 2018

Status: Archived (was: Untriaged)
Closing.  Reopen or file a new issue if we actually get around to doing this.

Sign in to add a comment