One . Determine whether the upper layer initiates the connection process , And connected Sink Is the name right , If it's not right here , It may be necessary to check AP The logic there is ：
2085 07-21 01:43:07.443357 866 903 I WifiDisplayController: requestConnect, address = 02:08:22:da:29:fc
2086 07-21 01:43:07.443631 866 903 I WifiDisplayController: resetReconnectVariable
2087 07-21 01:43:07.443822 866 903 I WifiDisplayController: connect: device name = Android_2dc0
Two . Check to see if... Has been successfully established P2P Connect （ The yellow part below describes P2P Almost succeeded , Preparing to build RTSP Connect ）
2089 07-21 01:43:07.443989 866 903 I WifiDisplayController: Connecting to Wifi display: Android_2dc0
2123 07-21 01:43:07.477403 866 903 I WifiDisplayController: Initiated connection to Wifi display: Android_2dc0
2101 07-21 01:43:07.450709 866 903 I WifiDisplayController: Listening for RTSP connection on 127.0.0.1:7236 from Wifi display: Android_2dc0 , Speed-Up rtsp setup, DRM Content isPlaying = false
3、 ... and . If not established P2P Connect , Please find P2P Colleagues help deal with .
Four . If set up P2P Connect , But there are still problems . Need to use wireshark analysis netlog 了 , Operate as follows （ If no corresponding RTSP Of netlog, Then maybe it's also P2P Not established successfully , Follow the third step ）：
5、 ... and . If the previous processes are successful , But still no connection succeeded . You can see if there are the following lOG：
2355 07-21 01:43:18.696528 866 903 I WifiDisplayController: Opened RTSP connection with Wifi display: Android_2dc0
6、 ... and . If you still can't find the cause of the problem through the previous Links , Please submit mtklog, And need to start netlog.