07-22-2024 03:30 PM
I recently changed my modem to a more modern version (I owned the previous one since like 2014, so it got pretty old) - Arris Surfboard G34, which combines the modem & router in one - set all of my devices (phone, laptop, chromecast) to the new Wifi network, and since then I'm having a weird issue: when opening YouTube app, my Google Pixel 3a would occasionally not recognize the Chromecast device (it would keep searching and then just say "no device found"). Most of the time it does recognize it, but not always.
What's interesting is that this issue only pertains to the Youtube app on my phone, everything else works perfectly (e.g. Spotify app always recognizes the chromecast instantly, my laptop always recognizes chromecast instantly, etc). My initial guess was that it might have to do with the 5G vs 2.4 Wifi network (I know that Pixel 3a doesn't allow 5G, and I initially set up a 5G version of wifi), but even after I had reset my Wifi to 2.4 on all devices - the issue still rears its head.
My Chromecast is 2nd gen, I believe, and I've also made sure my Youtube app has the most recent updates.
Any advice on what the origins of the issue might be and a potential solution would be truly appreciated.
08-08-2024 06:50 PM
Hi there!
Thanks for posting over the community space.
It's quite odd that the issue is isolated to the YouTube app on your Pixel 3a, while other devices and apps work flawlessly. This suggests a problem specific to the YouTube app or its interaction with your phone's network or Chromecast.
Potential Solutions:
To get more information about this issues I recommend you to check on No Cast destination found.
By systematically going through these steps, you should be able to identify and resolve the root cause of the problem.
Regards,
Brandon.