google / google/oboe

Motorola moto g(20) - aaudio timestamp latency and measured latency disagree, ~100ms missing from timestamp latency

Open
#1,562 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
C++
Stars
4.1k
Forks
639
Avg merge
2d 23h
Merged PRs (30d)
8

Description

Android version(s): 11
Android device(s): moto g(20)
Oboe version: 1.6.2
App name used for testing: OboeTester

**Short description**
Latency estimates derived from AAudio timestamps are low by about 100ms when playing over this phone's speakers.

**Steps to reproduce**
Open OboeTester
Navigate to ROUND TRIP LATENCY
Tap "MEASURE"

**Expected behavior**
latency.msec and timestamp.latency.msec are comparable

**Actual behavior**
latency.msec is ~260ms, timestamp.latency.msec is ~160ms

**Device**

```
ro.product.brand = motorola
ro.product.manufacturer = motorola
ro.product.model = moto g(20)
ro.product.device = java
ro.product.cpu.abi = arm64-v8a
ro.build.description = p352_Natv-user 11 RTA31.68-34 34 release-keys
ro.hardware = ums512_1h10
ro.hardware.chipname =
ro.arch =
| grep aaudio =
```

**Any additional context**

From aligning tracks by hand, the measured latency is closer to the actual latency. This appears to be an issue with the speaker output, as the timestamp estimates are producing much better results in our app when using headphones.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.