-
Notifications
You must be signed in to change notification settings - Fork 417
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
Wi-Fi Direct connection Fail #529
Comments
Looks like smartview or dex is some extension for miracast on samsung (just for anyone like me not knowing what that is) If the negotiation is aborted on samsung side then probably something else is needed (see windows extension on wiki for protocols extending miracast) You probably need to find out yourselve. About simpler case, attach logs for support (as described in wiki) so we can identify why it is failing See there's a problem with miraclecast where miracle-dhcp cannot create correctly the connection when miracle-sink is the group owner, see #491 if logs confirm it is able to connect when miracle-sink is not the GO, right now probably the only option is to force it to always be client (not GO) |
The device which is run miraclecast has wlan0,wlan1,p2p0. I also set supplicant.conf How do i do This is the miracle-sinkctl log
This is the miracle-wifid log
|
How it fails is that it stops at
P2P-GO-NEG-REQUEST
orconnect to <MAC> via pbc/(null)
.When I connect pure Wi-Fi Direct again after connecting SmartView or DeX, the connection succeeds without any problem.
Why does this problem occur and how do I fix it?
The text was updated successfully, but these errors were encountered: