Roon not detecting Pixel 10 Pro XL after update (ref#P7KRXM)

Support
1

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· Roon isn't finding my Pixel 10 pro Xl phone since last update of Roon, other devices are shown under Audio.

Tell us about your home network

· Typical Bell Fibe modem/router

2

Hi @Greg_Beardall,

Welcome back to the Roon Community! I understand how frustrating it is when a previously working device suddenly drops off your Roon Audio list after an update.

Since your other devices are showing up without issue on your Bell Fibe network, the problem is likely isolated to the phone itself. Sometimes, app or OS updates can automatically revoke or reset certain app permissions for security reasons. We need to verify that the Roon app still has the necessary permissions to discover devices on your local network and access your audio hardware.

Here is how you can check and re-enable these permissions on your Pixel 10 Pro XL:

  1. Open your Pixel's Settings app.
  2. Navigate to Apps and select Roon (you may need to tap See all apps first).
  3. Tap on Permissions.
  4. Check the Allowed and Not allowed lists. You must ensure that permissions like Nearby devices (crucial for local network discovery) and Music and audio are set to Allow.
Additionally, once those are confirmed, open the Roon app on your Pixel, navigate to Settings > Audio, and verify that the phone has not simply been disabled as an audio zone.

Please let us know if adjusting these permissions brings your Pixel back to your Audio tab.

3

That worked! The Google Pixel must have also has an update that effected the integration with Roon. Thanks!

4

Hi @Greg_Beardall,

That is great news! I am glad to hear that adjusting those permissions got your Pixel 10 Pro XL showing up in Roon again.

You are absolutely right; Android OS updates will often reset or revoke certain app permissions (like ‘Nearby devices’) in the background as a security and privacy measure, which immediately blocks the app from communicating with your local network.

I will go ahead and make sure this thread remains marked as resolved. If you run into any other issues in the future, please don’t hesitate to open a new topic.

Happy listening!