Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash when WifiDisplaySink.cpp:652 CHECK_EQ( err,(status_t)OK) #3

Open
gshu001 opened this issue Dec 18, 2014 · 2 comments
Open

Crash when WifiDisplaySink.cpp:652 CHECK_EQ( err,(status_t)OK) #3

gshu001 opened this issue Dec 18, 2014 · 2 comments

Comments

@gshu001
Copy link

gshu001 commented Dec 18, 2014

I use samsung Note2 as source . also I know the Note2 with hdcp, so the wfd failed. the sink crash when WifiDisplaySink.cpp:652 CHECK_EQ( err,(status_t)OK). The sink application crash seams not so friendly for user, how to avoid the application crash? thanks a lot.

@kensuke
Copy link
Owner

kensuke commented Dec 22, 2014

hint

// S3 to N7 (failed)
I/NetworkSession(1468): connecting socket 45 to 192.168.49.1:7236
I/WifiDisplaySink(1468): We're now connected.
E/WifiDisplaySink(1468): Invalid server_port description '19000'.
E/WifiDisplaySink(1468): rtpPort[19000] rtcpPort[1589504000] server_port[19000]
A/WifiDisplaySink(1468): frameworks/av/media/libstagefright/wifi-display/sink/WifiDisplaySink.cpp:654 CHECK_EQ( err,(status_t)OK) failed: -1007 vs. 0
A/WifiDisplaySink(1468): --------- beginning of crash

// N4 to N7 (success)
I/NetworkSession(1693): connecting socket 45 to 192.168.49.85:7236
I/WifiDisplaySink(1693): We're now connected.
I/RTPReceiver(1585): RTPReceiver::connect() mRTPMode[2] remoteHost[192.168.49.85] remoteRTPPort[52532] remoteRTCPPort[52533]
I/RTPReceiver(1693): connectUDPSession RTP successful.
I/RTPReceiver(1693): connectUDPSession RTCP successful.
I/WifiDisplaySink(1693): MediaReceiver initialization completed w/ err 0

@xuwen0306
Copy link

@kensuke the error log you post is based S3, and the root cause is sink code checking the fix style port from source side. The easy way to fix the issue is comment the check port part, or will cause IoT issue continuely

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants