Latency is an important system performance metric. While many kinds of audio latency metrics exist, one useful and well-understood metric is round-trip latency, defined as the time it takes for an audio signal to enter the input of a mobile device, be processed by an app running on the application processor, and exit the output.
This page provides round-trip audio latency measurements for select Nexus/Pixel devices and Android platform versions.
Why we measure latency
Google measures and reports latency so Android application developers have the data they need to make informed decisions about available latency on actual devices. By sharing latency numbers for select Nexus and Pixel devices, we hope to encourage the entire Android community to measure, publish, and reduce latency on all Android devices. Please join us in our commitment to reducing audio latency!
App impact on latency
Signal processing can add the following types of delay to latency:
- Algorithmic. This delay is inherent and does not vary with the CPU. An example is the delay added by a finite impulse response (FIR) filter.
- Computational. This delay is related to the number of required CPU cycles. For example, attenuation of a signal is usually done by a multiplication operation that takes a varying number of cycles depending on the CPU.
How we measure
We made the measurements listed on this page using the Dr. Rick O'Rang audio loopback dongle and an audio feedback (Larsen effect) test. Measurements assume the application signal processing adds zero algorithmic delay and near-zero computational delay.
We measure round-trip latency via the headset connector for several reasons:
- Important music applications (such as guitar and voice processing) use the headset connector.
- Measuring round-trip latency of the on-device microphone and speaker can be cumbersome, as it is difficult to keep a feedback loop in open air from entering uncontrolled oscillation.
- On-device transducers are small and sacrifice frequency response to achieve their small size. To compensate, digital signal processing is applied but increases algorithmic delay for the on-device path.
There are cases where on-device microphone and speaker latencies do matter, but they are usually for one direction, not round-trip. Techniques for measuring unidirectional latency are described at Measuring Output Latency and Measuring Input Latency.
The measurements listed below are specific to a build number. Devices are listed in approximate order of initial release and by platform version; you can also view latencies in a chart. The test application uses the Android native audio API based on OpenSL ES.
± one buffer