Marc Baechinger

A general note: API levels from and above 31 create the notification from the information available in the media session rather than in the notification. Below 31 until 29(?) a...

Closing and marking as duplicate of #140. We will update the other issue as soon as we have pushed the commit that maps the available commands to the legacy playback...

In general, ExoPlayer only can report what it knows about and ExoPlayer is not aware of the internal workings of the IMA SDK which is a black box for ExoPlayer...

That's currently not possible in a declarative way I'm afraid. The `MediaItem` only has a field for the ad tag URI only and headers can't be declared. You can use...

Thanks for the context - makes sense. How would you add these headers if you'd use the ad SDK directly without the ExoPlayer extension?

If the `DefaultMediaItemConverter` is sending a `MediaItemQueueItem` to the cast device it includes the data of the `MediaItem` in a JSON document that is stored as the custom data. In...

Thanks for reporting! Android Auto is using the `MediaLibraryService` to navigate in the catalogue as you describe. When the user selects an item, Android Auto is preparing the player with...

I don't think there is something the Media3 library can do to avoid that as long as Android Auto is using Media1. When AA is browsing your catalogue they are...

Thanks for reporting! Interesting case. :) Reason for the wrong behaviour you describe: We are [masking](https://github.com/androidx/media/blob/release/libraries/session/src/main/java/androidx/media3/session/MediaControllerImplBase.java#L432) the state change to `playWhenReady=true` (and other state changes) in `MediaControllerImplBase.play()`. This means we...

Do you think setting the suppression reason `PLAYBACK_SUPPRESSION_REASON_TRANSIENT_AUDIO_FOCUS_LOSS` wouldn't be the accurate action for the `ForwardingPlayer` intercepting a `play` call? I'm not a believer of a single truth in design...