Cast not working on release 2026062300

vocalize_undefined

Hello,

Pixel 7, Stable channel with sandboxed Play Services installed. Recently updated to 2026062300 (Android 17) via OTA and now casting no longer works in YouTube, Google Home app, or the OS built-in "cast" quick settings tile. No cast targets are ever found to select. This was definitely working as recently as the previous stable release the day before I upgraded. All related apps (Play Services, Play Store, and the media apps) have "Network" and "Nearby devices" permissions granted. I suspect an issue with the new ACCESS_LOCAL_NETWORK permission as part of Android 17, which I understand should be covered by the "Nearby devices" permission, yet I still get an EPERM in my logcat:

06-26 10:07:47.654  3006 10869 E AOSP-MdnsDiscoveryManag: Failed to send a multicast mDNS packet. [CONTEXT service_id=168 ]
06-26 10:07:47.654  3006 10869 E AOSP-MdnsDiscoveryManag: java.io.IOException: sendto failed: EPERM (Operation not permitted)
06-26 10:07:47.654  3006 10869 E AOSP-MdnsDiscoveryManag:       at libcore.io.IoBridge.maybeThrowAfterSendto(IoBridge.java:738)
06-26 10:07:47.654  3006 10869 E AOSP-MdnsDiscoveryManag:       at libcore.io.IoBridge.sendto(IoBridge.java:705)
06-26 10:07:47.654  3006 10869 E AOSP-MdnsDiscoveryManag:       at java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:126)
06-26 10:07:47.654  3006 10869 E AOSP-MdnsDiscoveryManag:       at java.net.DatagramSocket.send(DatagramSocket.java:723)
06-26 10:07:47.654  3006 10869 E AOSP-MdnsDiscoveryManag:       at hqpk.run(:com.google.android.gms@262031035@26.20.31 (260400-919905943):101)
06-26 10:07:47.654  3006 10869 E AOSP-MdnsDiscoveryManag:       at java.lang.Thread.run(Thread.java:1572)
06-26 10:07:47.654  3006 10869 E AOSP-MdnsDiscoveryManag: Caused by: android.system.ErrnoException: sendto failed: EPERM (Operation not permitted)
06-26 10:07:47.654  3006 10869 E AOSP-MdnsDiscoveryManag:       at libcore.io.Linux.sendtoBytes(Native Method)
06-26 10:07:47.654  3006 10869 E AOSP-MdnsDiscoveryManag:       at libcore.io.Linux.sendto(Linux.java:280)
06-26 10:07:47.654  3006 10869 E AOSP-MdnsDiscoveryManag:       at libcore.io.ForwardingOs.sendto(ForwardingOs.java:745)
06-26 10:07:47.654  3006 10869 E AOSP-MdnsDiscoveryManag:       at libcore.io.BlockGuardOs.sendto(BlockGuardOs.java:413)
06-26 10:07:47.654  3006 10869 E AOSP-MdnsDiscoveryManag:       at libcore.io.ForwardingOs.sendto(ForwardingOs.java:745)
06-26 10:07:47.654  3006 10869 E AOSP-MdnsDiscoveryManag:       at libcore.io.IoBridge.sendto(IoBridge.java:703)
06-26 10:07:47.654  3006 10869 E AOSP-MdnsDiscoveryManag:       ... 4 more

There is also a curious note in the GrapheneOS release notes for this release possibly related:

"Sandboxed Google Play compatibility layer: add stub for NsdManager.registerService() to handle lack of ACCESS_LOCAL_NETWORK"

Thanks for any help!

Johnnyloans

vocalize_undefined

Hello, welcome :)

For YouTube, give YouTube the nearby devices permission

Give Google play services the nearby devices permission

lndshrk

vocalize_undefined

Same here, right down to the mdns errors.

vocalize_undefined

Johnnyloans

Thanks for the suggestion, but I already have "Nearby devices" granted to Google Play Services, Google Play Store, and YouTube but still have the same issue. I've even tried removing the permission from these apps and re-adding it, and rebooting the device, but it still does not work.

Johnnyloans

Double check that these 3 apps also have the network permission too. Then force close YouTube and reopen. Try out casting there.

vocalize_undefined Google Play Services, Google Play Store, and YouTube

eliz0x

I've just noticed the exact same issue on my phone. I'm on the 2301 release using a Pixel 6 Pro. It worked yesterday evening before I updated from the android 16 release.

None of the streaming apps can detect a Chromecast. The Google Home app itself will also say it can't see the Chromecast on my WiFi network.

I have a pixel 9 pro xl running stock android 17 to test on the same network and that works fine.

eliz0x

As per this thread: https://discuss.grapheneos.org/d/36930-casting-to-2nd-gen-chromecast-broken-since-17/2

I had to go into the permissions list for the Google Play Services app, set "Nearby Devices" to allow and then restart the phone. Now works fine!

vocalize_undefined

Maybe I am having a different but similar issue?

All my apps have "Nearby devices" and "Network" permissions granted. This includes:

Google Play Services
Google Play Store
Google Home
YouTube
YouTube Music

And I rebooted my device. Still getting the same EPERM Failed to send a multicast mDNS packet in my logcat as in my OP, and no cast targets appear in YouTube, YouTube Music, Google Home, or the OS built in "Cast" quick settings tile.

ieuan

Seeing the same issue. All these apps have Network and Nearby Devices permission (and I've revoked/re-added and rebooted the device multiple times since).

comicmuse

Same here. Same errors in the log files. No sign of my Chromecast devices. Have added Nearby Services permissions to Home, Play Services, Play Store and the media player (and upgraded from "Allow to keep working" to "Allow" for the media player) and rebooted multiple times. Google Home app itself says it doesn't see the devices on this wifi network.

mkgrapheneos

Same over here. I can cast to devices and groups with VLC, but all Google/YouTube Apps stopped working after the upgrade.

GrapheneOS

Revoke Nearby Devices from Play services and grant it back again. It won't automatically receive the local network permission unless it requests it which is likely doesn't do. This is because Play services targets API 37 (Android 17) but isn't designed to provide a good experience as an unprivileged app by requesting permissions it doesn't have.

mkgrapheneos

GrapheneOS that worked!

vocalize_undefined

GrapheneOS

Thought I did this but apparently not. Removing and re-adding Nearby devices permission to Google Play Services worked! Thanks!

Would there be any way to make this more seamless in a future release? As it is the permissions UI post-upgrade enters a state where it isn't conveying the full status of permissions.

de0u

mkgrapheneos Thanks for reporting back!

Schiglip

I had a similar issue. Granting "nearby devices" to Google Play Services solved it for me too.
THANK YOU SO MUCH, for that release, and for the 5-star support

Details:
Since GOS 2026062301 (Android 17) on Pixel 9 Pro XL,
using cast from the be.rtbf.auvio app , or from the cast button in the settings menu was not finding any device to talk to. Missing target devices were Sony Android TV, and Google Chromecast (maybe V2).

Changing just that one permission for Google Play Services solved it. NB: I didn't have to remove it first. It appeared it was not granted, and I just granted it.

de0u

Schiglip Thanks for the report!

happysquid

Same issue but the two areas I am experiencing issues is Spotify and the Cast quick settings tile. Following the same steps to solve

Deny Nearby Permissions in Play Services
Reboot
Allow Nearby Permissions in Play Services

worked perfectly for Spotify, but resulted in no change for the Cast feature for the overall device.

I also downloaded YouTube and YouTube Music, neither featured the Cast icon until the Nearby Devices was given (obviously). But when I downloaded VLC it downloaded with the Nearby Devices already given and listed all my speakers.

Since you can't alter the Nearby Devices permissions for the Settings app (which is where the Cast permissions are located)...how can I resolve this?

Johnnyloans

happysquid

Start at this comment and read further
https://discuss.grapheneos.org/d/36930-casting-to-2nd-gen-chromecast-broken-since-17/16

When I said "google", it seems that the required app is actually "google home"