Casting "Unable to find nearby devices"

itsJesski

I'm trying to get casting working again after switching to graphene recently. Specifically, I regularly use casting with the official Twitch and Youtube apps. For both of these I'm getting "unable to find nearby devices" after a few seconds of searching which clicking the cast button.

So far I've:

Made sure google play services has network, nearby devices, and notification access.
Tried running Twitch and Youtube without exploit protection compatibility mode.
Tried switching devices (both phone and casting device) to different wireless networks

I'm not really sure what else to do besides messing with more permissions, but none of the rest seem relevant. Has anyone run into this issue at all?

n3t_admin

itsJesski Google Cast can indeed be pretty tricky. It also depends on how the app implements the Cast framework. I only have experience with casting Apple Music. Make sure that you don't run any VPNs, try with private DNS disabled. Also make sure that your router doesn't block mDNS (or any firewalls that may be active for that matter). Permissions don't need to be invasive from my experience: just network should actually be enough.

schweizer

Streaming works for me in Youtube and Firefox app. I click on the stream icon within the app not the one in the dropdown menu. Streaming under settings never shows devices and also Vanadium does not support it. Correct me if I'm wrong.

n3t_admin

schweizer streaming under settings won't ever work since it's missing Cast components on a system level (remember: Cast is a proprietary Google protocol and not included in AOSP). I am just assuming here, but I'm pretty certain that Vanadium would also need to utilize "system Cast" for the same reason of not including proprietary blobs. Apps like Twitch or YouTube have the necessary libraries built in.

schweizer

n3t_admin streaming under settings won't ever work

While I am fine that it does not work I do not understand why they put it under settings in the first place.

And when Firefox can do it why Vanadium couldn't?

schweizer

n3t_admin streaming under settings won't ever work [...] (remember: Cast is a proprietary Google protocol and not included in AOSP)

n3t_admin it's in the settings, because it's part of AOSP.

That sounds like a contradiction and does not convince me.

The Quick Settings are highly configurable by the user and apps too can add own quick settings fields. So I do not see what "unneccessary problem" could be caused by hiding this specific one.

On the contrary I see a potential risk if there is code in GOS that is disfunctional. I doubt there is any testing on dead code. I am not a programmer however.

n3t_admin

schweizer it's in the settings, because it's part of AOSP. Removing it would just introduce unnecessary problems.

I don't know how Firefox does it. It doesn't use the standard com.google.android.gms.cast.framework.xxx service, so I can't really tell without checking their whole code. Probably some proprietary implementation that they did.

n3t_admin

schweizer it really isn't. The option is still there but it's missing the necessary libraries/services to work. This isn't the only example and AOSP has many of these holes. Same thing could be said about "Autofill with Google" in Vanadium. Just another remnant of Google's code found in GrapheneOS. Removing this setting would clear up confusion, but possibly introduce unknowns. Messing with AOSP code is generally problematic, as it introduces a bigger work load to take care of with each and every update.