SDK / exoplayer

If a surface was previously passed to the player then an output buffer
renderer was set, we would remove surface callbacks but not clear the
surface on renderers that accept MSG_SET_SURFACE.

PiperOrigin-RevId: 274532266

Add a javadoc explanation for ProgressiveDownloader that explains that it tries to skip downloading already cached bytes.

download calls through to CacheUtil#cache, which handles skipping already downloaded bytes.

It is useful for callers to know that ProgressiveDownloader has this behavior - otherwise, they might reimplement the logic themselves.

I hope this behavior is something that can be part of the public API :)

PiperOrigin-RevId: 274202995

This is useful for apps that want to access HDR metadata that MediaCodec puts
in its output format.

PiperOrigin-RevId: 274169985

This is a proof of concept for cleanup we should do for all of
our DataSource implementations as we move toward stabilizing
parts of the API.

- Move all XDataSourceFactory classes to be inner classes.
- Remove chained constructors for XDataSourceFactory classes. Keep
  required args going through constructors. Use setters for the
  rest.
- Not applicable in this case, but we probably want to deprecate
  all but the no-arg method for instantiating eac XDataSource
  instance (with the all-arg method kept but with the intention
  of making it package private).

PiperOrigin-RevId: 274162076

PiperOrigin-RevId: 274161845

Issue: #6523
PiperOrigin-RevId: 274160232

PiperOrigin-RevId: 274148614

PiperOrigin-RevId: 274148026

- Verifies that playWhenReady doesn't become true if audio focus
  is denied.
- Also verifies there's no suppression reason in this case, because
  the denial is permanent rather than temporary.

PiperOrigin-RevId: 274141099

Also removed "to be executed" from all the comments, since it
didn't seem to add value.

PiperOrigin-RevId: 274139837

It's documented to be for temporary loss only (i.e. the case where
externally reported playWhenReady is still true)

PiperOrigin-RevId: 274129922

Currently, ndk cpu-features is being used.
This is now deprecated and google open-source
cpu_features library is recommended.

PiperOrigin-RevId: 273987647

PiperOrigin-RevId: 273971120

Issue: #3353
PiperOrigin-RevId: 273949689

This supports both chunkless & traditional preparation

PiperOrigin-RevId: 273938344

PiperOrigin-RevId: 273937090

PiperOrigin-RevId: 273929000

PiperOrigin-RevId: 273928626

PiperOrigin-RevId: 273919032

If a user has checked out libgav1 they almost certainly want to
build the extension, so fail if CMake is not present but
libgav1 is present. Also add a note to the README linking to
instructions for installing CMake.

Also remove the NDK check, as ndk.dir is apparently deprecated
and Android Studio appears to install this automatically anyway.

PiperOrigin-RevId: 273918142

PiperOrigin-RevId: 273760294

When the user calls setRepeatMode, the state modifications are
observed as immediate, in spite of being sent to the receiver app
as asynchronous operations.

PiperOrigin-RevId: 273754931

Also move the masking internal state update before the message
dispatch, so as to ensure the result of the operation prevails
over the masking state.

PiperOrigin-RevId: 273740585

PiperOrigin-RevId: 273734495

Playback cannot be suppressed if playWhenReady=false

PiperOrigin-RevId: 273726084

PiperOrigin-RevId: 273712563

PiperOrigin-RevId: 273706425

PiperOrigin-RevId: 273549830

The limit of this.supplementalData was not reset.

PiperOrigin-RevId: 273515718

This doesn't offer anything on top of the functionality in the main demo app.
There's less code but we have a blog post and presentations that walk through
how to use the extension, so it seems fine to delete the code so we don't need
to maintain it. This also avoids potential confusion about what the demo app
means on IMA-related GitHub issues.

PiperOrigin-RevId: 273501720

PiperOrigin-RevId: 273475232

When newIndex overlaps oldIndex with newstarttime < oldstarttime, according to the segNum of endtime
in newIndex and oldIndexLastSegnum to calculate the segmentNumShift.

Issue: #6297
PiperOrigin-RevId: 273297284

PiperOrigin-RevId: 273296545

PiperOrigin-RevId: 273296461

PiperOrigin-RevId: 273296236

When the user calls setPlayWhenReady, the state modifications are
observed as immediate, in spite of being sent to the receiver app
as asynchronous operations.

PiperOrigin-RevId: 273289768

PiperOrigin-RevId: 273270892

PiperOrigin-RevId: 273263822

It's confusing that app:played_color also modifies the colors
that derive from it, but the corresponding setter does not. It
seems generally clearer just to define constants.

PiperOrigin-RevId: 273249557