Inconsistent Cast notification configuration between CastParams and manifest options

Version

Media3 1.11.0

More version details

Cast Params were introduced in version 1.11.0 and now the documentation recommends them over the old manifest-provided cast options. However, they seem to behave differently.

When using CastParams, we can't disable the Cast session notification, so we're forced to use the old method.

https://github.com/user-attachments/assets/9fbd79e0-34e8-4a51-afca-40739c1dc0d7

For some reason the old method just doesn't work as per documentation. Both the Cast SDk documentation and media3's docs mention to use setNotificationOptions(null) with setMediaSessionEnabled(false) to get rid of the notification, but it only worked for me when I passed an empty builder instead of null.

https://github.com/user-attachments/assets/f8cd3c63-dd11-4669-bd8c-eff98661d645

https://github.com/user-attachments/assets/1c440845-d3e8-472c-a1ed-cc1c1a704a47

Devices that reproduce the issue

Samsung S25+ (Api 36.1)

Devices that do not reproduce the issue

No response

Reproducible in the demo app?

Yes

Reproduction steps

0. Use manifest initialized cast options with setNotificationOptions = null and setMediaSessionEnabled = false
1. Play media in media session demo
2. Connect to Cast

Expected result

No cast session notification, only app session notification

Actual result

Cast session notification is shown

Media

Album Folder -> Wake Up -> Play

Bug Report

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