SDK / exoplayer

Issue: #5788
PiperOrigin-RevId: 245440858

PiperOrigin-RevId: 245411528

There are no logic changes here. It's just moving code around and removing
the "internal" part of names where no longer required.

PiperOrigin-RevId: 245407238

PiperOrigin-RevId: 245405316

PiperOrigin-RevId: 245401274

PiperOrigin-RevId: 245397736

PiperOrigin-RevId: 245388082

PiperOrigin-RevId: 245243488

We currently toggle the view in onTouchEvent ACTION_DOWN which is non-standard
and causes problems when used in a ViewGroup intercepting touch events.

Switch to standard Android click handling instead which is also what most
other player apps are doing.

Issue:#5784
PiperOrigin-RevId: 245219728

PiperOrigin-RevId: 245218900

This also removes the build warning about the experimental flag.

PiperOrigin-RevId: 245218251

Also add some unit tests for codecs strings parsing.

PiperOrigin-RevId: 245210490

PiperOrigin-RevId: 245014381

The two behave identically, and containsAllOf is being removed.

More information:
  go/containsall-lsc

Tested:
    TAP --sample for global presubmit queue
    http://test/OCL:244737393:BASE:244782138:1555991083653:3080d7c7
PiperOrigin-RevId: 244886736

The two behave identically, and isNotSameAs is being removed.

More information:
  go/issameas-lsc

Tested:
    TAP --sample for global presubmit queue
    http://test/OCL:244736857:BASE:244751659:1555988098671:1e0f72c5
PiperOrigin-RevId: 244886651

PiperOrigin-RevId: 244864742

Disabling stack trackes currently logs messages twice, once with and once
without stack trace.

PiperOrigin-RevId: 244853127

The AndroidX bundled version (0.42) lags behind the most up-to-date public
release (0.44) making it more difficult to stay close to the actual head
revision which is used internally.

PiperOrigin-RevId: 244848568

PiperOrigin-RevId: 244838165

This ensures we keep the loading period in sync with the the playing period in
PlybackInfo, when the latter changes to something new.

PiperOrigin-RevId: 244838123

Also re-enable two of them, although note that the fix here is
not related to the flakiness that caused them to be disabled.
I'm re-enabling them since much has changed in DownloadManager,
and the hope is that these tests are no longer flaky.

PiperOrigin-RevId: 244826225

Experiments show this is beneficial for rebuffers with only minor impact
on battery usage.

Configurations which explicitly set a minimum buffer duration are unaffected.

Issue:#2083
PiperOrigin-RevId: 244823642

PiperOrigin-RevId: 244816212

Before this change we'd release the audio track and create a new one as soon
as audio processors had drained when reconfiguring.

Fix this behavior by stop()ing the AudioTrack to play out all written data.

Issue: #2446
PiperOrigin-RevId: 244812402

- We had buildAddRequest and sendNewDownload. Converged to
  buildAddDownload and sendAddDownload.
- Also fixed a few more inconsistencies, and brought the
  action constants into line as well.

PiperOrigin-RevId: 244274041

PiperOrigin-RevId: 244268855

PiperOrigin-RevId: 244267255

- Listener based reporting of progress allows the content length
  to be persisted into the download index (and notified via a
  download state change) as soon as it's available.
- Moved contentLength back into Download proper. It should only
  ever change once, so I'm not sure it belongs in the mutable part
  of Download.
- Made a DownloadProgress class, for naming sanity.

PiperOrigin-RevId: 244242487

PiperOrigin-RevId: 244226680

PiperOrigin-RevId: 244223870

PiperOrigin-RevId: 244216620

PiperOrigin-RevId: 244210737

PiperOrigin-RevId: 244196081

Assuming there is no text language preference.

PiperOrigin-RevId: 244176667

PiperOrigin-RevId: 244173887

PiperOrigin-RevId: 244170391

PiperOrigin-RevId: 244170179

PiperOrigin-RevId: 244168713

PiperOrigin-RevId: 244167456

PiperOrigin-RevId: 244139959