SDK / exoplayer

Using all lower case RTSP headers is perfectly valid, as the spec mandates case
insensitively. However, some RTSP servers do not implement the RTSP spec
closely and does not recognize the lower case headers. This change aims
at using the header names as defined in the RTSP spec to maximize compatibility.

Issue: #9182
PiperOrigin-RevId: 386224566

PiperOrigin-RevId: 386207381

PiperOrigin-RevId: 386206960

PiperOrigin-RevId: 386194874

PiperOrigin-RevId: 386194496

PiperOrigin-RevId: 386185285

PiperOrigin-RevId: 386177945

r2.14.2

#minor-release

PiperOrigin-RevId: 386048024

#minor-release

PiperOrigin-RevId: 386048024

This also deletes several files that should have been deleted as part
of the 2.14.0 release - both javadoc for classes that were removed in
that release and all the *-frame.html files that no longer seem
to be produced by the javadoc compiler. Also a jquery file
(jquery-1.10.2.js) that's no longer produced by the compiler.

#minor-release

PiperOrigin-RevId: 385997294

PiperOrigin-RevId: 385996618

PiperOrigin-RevId: 385995740

This URL no longer resolves.

#minor-release

Issue: #9205
PiperOrigin-RevId: 385772688

PiperOrigin-RevId: 385736588

This also deletes several files that should have been deleted as part
of the 2.14.0 release - both javadoc for classes that were removed in
that release and all the *-frame.html files that no longer seem
to be produced by the javadoc compiler. Also a jquery file
(jquery-1.10.2.js) that's no longer produced by the compiler.

#minor-release

PiperOrigin-RevId: 385997294

#minor-release

PiperOrigin-RevId: 385996618

PiperOrigin-RevId: 385995740

FileDataSourceException subclasses DataSourceException and can be handled
in the same fashion.

PiperOrigin-RevId: 385983103

In some DataSources, it is not easy to assign an error code at the throw site.
For example, CronetDataSource.readInternal() throws SocketTimeoutException
on L1033, and is caught at L754 as IOException and is thrown.

We need the logic to assign error code for the actual type of the error cause.
While we can certainly do in individual DataSources, IMO there's value in
making this logic generic at a higher level (like what is in this CL).

The catch and translation logic is borrowed from EPII:L646.

PiperOrigin-RevId: 385789629

PiperOrigin-RevId: 385783671

PiperOrigin-RevId: 385781004

This URL no longer resolves.

#minor-release

Issue: #9205
PiperOrigin-RevId: 385772688

PiperOrigin-RevId: 385763366

PiperOrigin-RevId: 385758742

This field is to be associated with the artworkData.

PiperOrigin-RevId: 385757480

#minor-release
Issue: #1611
PiperOrigin-RevId: 385741535

PiperOrigin-RevId: 385736588

Issue: #9037
#minor-release
PiperOrigin-RevId: 385630065

PiperOrigin-RevId: 385595264

Before this fix, if DefaultDrmSessionManager.release() was called while
there was at least one 'external' session reference still active (i.e.
session.referenceCount > 1) then the manager will release it's reference
immediately but when the session's reference count subsequently drops to
1 (due to external references being released) the manager will schedule
a task to release its internal reference *again*.

This change fixes the problem by only scheduling the timed release if
the manager is unreleased. This ensures that the internal references
are only released once.

Issue: #9193

PiperOrigin-RevId: 385580741

* Add release note for `RtspMediaSource.Factory.setTimeoutMs()`
* Remove mention of what we don't support (any such list is necessarily non-exhaustive)
* Remove markdown quote character ('>')

PiperOrigin-RevId: 385143574

#minor-release
Issue: #9100
PiperOrigin-RevId: 384962258

Issue: #9183

RFC2326 Section C.1.1 specifies that the URI to identify a track can be either
absolute (like rtsp://example.com/path) or relative (like "path"). Currently
we don't handle absolute URI, and this CL is to add the support.

Note though, we don't currently use the Content-Base or Content-Location
headers for the session URI.

PiperOrigin-RevId: 384649818

Applications may need to pass a non-visual context when creating
a DefaultTrackSelector (e.g., because they're audio-only or are
creating the selector in a background service).

Obtaining the default display via DisplayManager avoids the strict
mode violation that occurs when retrieving it via WindowManager.

#minor-release

PiperOrigin-RevId: 384487363

Most of the super-interfaces are deprecated, but the intention is that
only the types are deprecated and the methods themselves shouldn't be.
In order to reflect this in javadoc we override all the methods in
`Player.Listener` in order to 'cancel' the deprecation.

This change deliberately doesn't override methods that are explicitly
deprecated with documented replacements (like
`Player.EventListener#onPlayerStateChanged`) - these should contine to
be marked as deprecated in javadoc.

PiperOrigin-RevId: 384253725

Issue: #9037
#minor-release
PiperOrigin-RevId: 385630065

PiperOrigin-RevId: 385595264

Fix release notes duplication introduced by https://github.com/google/ExoPlayer/commit/22ab14844ba7deedb6f7b2823fa315e6febf7ac2

PiperOrigin-RevId: 385582191