Packet sender chrome android#

That both devices indicate they are connected. Connect both the sender and the receiver to the same WiFi network and verify.It in any communication to Google Cast Support. When you ping the devices, note the response message content so you can report If the device is unable to maintain theĬorrect time, contact the device vendor. If the system time on either the sender or the receiver is incorrect, reboot theĭevice and connect it to the internet. System time automatically by connecting it to the internet. The system time on most senderĭevices (such as a phone) is mutable, but you should allow the device to get the The system time on a Cast device is immutable and the device can maintain theĬorrect time if connected to the internet. A disparity of as little as 10 minutes may Is a significant disparity between the system time on the sender device and that The authentication handshake between the sender and receiver can fail if there While those of another do not, the problem may be with the platform. If all apps of a certain platform fail consistently,

Packet sender chrome android#

If your sender app is on the Android platform, run a different app Run any app (not Netflix or YouTube) on a different platform than that of When running your sender app on other platforms, is the discovery Run your sender app on a different platform (if possible). Hand, if all apps have problems discovering your receiver, the problem may Sender app isn't, the problem is probably in your sender app.

If other apps are consistently discovering your receiver, and your Run a different sender app (not Netflix or YouTube), and touch the Castīutton to view Cast devices on the network. Is happpening in the app? Is the time to connection loss consistent over Observe the sender app and note theĬonditions under which it loses its ability to discover your receiver: what If the Cast-enabled device is now listed (discovered), there may In the sender app, touch the Cast button to view Cast devices on the network. On iOS, double-click the home button, select the sender app, and swipe.On Android, force the app to stop by using the Android system settings.Connect both the sender and the Cast-enabled devices to the same.The support options described in Google Cast Support. To get further assistance with your issue, gather all available information suchĪs debugging logs, ping response data, and network service data, and use one of The sender device and the Cast-enabled devices device must beĭo not attempt to resolve discovery issues while inĪlso, see Debugging for more information about.The sender device must have WiFi enabled and running.

For example,Ĭhromecast, Google Home, or Google Nest Hub.

The Web Receiver device is an official Google Cast device.

Use some specialized discovery mechanisms.

The sender device is running a Cast app that you can use for testing.ĭo not use the Netflix or YouTube apps to test discovery, as these.

They help you narrow down the possible causes.īefore investigating your device discovery problem, be sure the following Because there are so many potential factors, and so many variables in theĭiscovery process, these measures may not definitively prove any one cause, but This document describes ways to troubleshoot for device discovery problems: theĬast-enabled devices does not appear in the list of connectedĬast devices or, worse, the Cast button does not appear when you run the senderĪpp. May be with the app (sender or Cast-enabled devices)

The Cast SDK performs device discovery, as described forĪnd iOS, to provide the user with a list ofĪvailable Cast-enabled devices.