androidx / androidx/media

Position accuracy problems when starting media

Open
#1,252 0 comments 0 reactions 1 assignee View on GitHub

@marcbaechinger is already working on this.

Since Apr 15, 2024.

bug needs triage
Dominant language
Java
Stars
3k
Forks
955
Avg merge
12d 14h
Merged PRs (30d)
2

Description

Version

Media3 1.3.0

More version details

No response

Devices that reproduce the issue
  • Pixel 6 Api 34 emulator
  • Google Pixel 6
    (I assume it is reproducible on close to all devices)
Devices that do not reproduce the issue

No response

Reproducible in the demo app?

Yes

Reproduction steps

Start playing the media.

This is not reproducing all the time, maybe 1/10(or more), so to speed up reproduction, start playing and repeatedly click previous button to quickly restart the media. Alternatively, take your time to go back to the media list and press the media again, eventually it should be reproducible.

Expected result

isPlaying -> mediaPos from EventLogger reports 0.00 consistently, as this is the beginning of the media.

Actual result

About 1 out of 10(or more) times, isPlaying -> mediaPos from EventLogger reports > 0.00(e.g. 0.04).

In the following screenshot I have removed the formatting for the time string and reported in ms directly:
Skjermbilde 2024-04-08 kl  15 52 35

Media

I've tried with Clear DASH -> HD (MP4, H264) and Misc -> Apple 10s (AAC), but I assume it is reproducible on close to all formats/assets.

Bug Report
  • You will email the zip file produced by adb bugreport to android-media-github@google.com after filing this issue.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.