Hide notification when chromecasting and retain volume control on cast-receiver

[FilipKastrupGP]

I’m using Media3 version 1.5.1 and encountering an issue with Chromecast.

When casting, I end up with two media control players:

• One from my MediaSession
• One from Chromecast

I can disable the Chromecast-provided media controls using com.google.android.gms.cast.framework.OptionsProvider. However, when I do this, the hardware volume buttons on my phone no longer control the volume of the cast receiver—they only adjust the phone’s volume instead.

Is there a way to:

• Have only one media control player / notification,
• Keep the AudioService running, and
• Still use the hardware volume buttons to adjust the cast receiver’s volume?

[oceanjules]

Hi @FilipKastrupGP,

Thank you for your report. You are right that removing those controls is not the solution, purely because it changes the DeviceInfo from DeviceInfo.PLAYBACK_TYPE_REMOTE to DeviceInfo.PLAYBACK_TYPE_LOCAL and that's why the volume buttons then only affect the phone, not the device you are casting to.

Am I right in assuming that you are using media3's CastPlayer?

[FilipKastrupGP]

@oceanjules Thank for responding.
Yes we are using the media3's CastPlayer.

Note:
Usinge a ReplaceableForwardingPlayer. When I cast I can see in logcat that the deviceinfo changes from local to remote.

[AntonMishanin]

I have the same issue with media notification

If I disable cast media session, like in issue, I can't change volume via hardware buttons
#39

.setCastMediaOptions(
    CastMediaOptions.Builder()
         .setMediaSessionEnabled(false)
         .setNotificationOptions(null)
         .build()
)

[FilipKastrupGP]

So.. I my case the DeviceInfo is DeviceInfo.PLAYBACK_TYPE_REMOTE but the DeviceInfo.routingControllerId is null.
Looks like this happens because CastPlayer.fetchDeviceInfo() only gets one RoutingController from mediaRouter2.

[AquilesCanta]

Hi folks, for volume adjustment to work we need an active media session. But we also don't want to use the Cast one (because otherwise we'll see some jankiness in the notification and output switcher), so calling

.setCastMediaOptions(
    CastMediaOptions.Builder()
         .setMediaSessionEnabled(false) <--- this
         .setNotificationOptions(null)
         .build()
)

is the right thing to do. We just need to re-route your media session's volume provider volume events to player calls.

I'll come back to you in a few days once I get a few cycles to fix this.

[albinus-sc]

@AquilesCanta Hey Aquiles, do you have an update on this?