Since I had to re-read the wifi display spec I thought I'd share my findings. Tomasz: please comment if you have anything to add (note that my interpretation of the spec is a bit different than it was on first read). First a little context for those who haven't heard of this: Connman uses "go-intent" (a 0-15 figure that describes how much it wants to be group owner & DHCP server) to a value 7. Android source seems to use value 0 -- I'll still have to confirm the android value though. It seems that using 7 with our desktop-source exposes bad bugs in some sinks: Connman will end as the GO and DHCP server and It looks like the sinks have not been tested in a situation where they are not the GO & DHCP server. The section "3.2.1 Wi-Fi P2P" says this: | If a WFD Session including a single WFD Sink, either a WFD Source | or a WFD Sink may be a P2P GO. If a WFD Session includes both a | Primary Sink and a Secondary Sink, then the WFD Source shall be a | P2P GO. So what connman is doing _should_ be ok... "4.9.4 WFD Device Pairing" says: | If the underlying connectivity mechanism is resolved as Wi-Fi P2P, | one of the following sequences is used to setup the corresponding | connection between the WFD Source and WFD Sink(s): | (a) If a P2P Group exists with the WFD Source as the P2P GO, the | Primary and the Secondary Sinks join the existing P2P Group, or | (b) The Primary or the Secondary Sink initiates a P2P Group | formation procedure with the WFD Source setting the GO-intent | to zero as defined in [7], indicating preference not to be the | GO for the P2P Group (prior to the ensuing GO-negotiation phase | of the Wi-Fi P2P connection setup), or | (c) The WFD Source initiates a P2P Group formation procedure with | the Primary Sink setting its GO-intent to indicate ‘GO-only’ | prior to the ensuing GO-negotiation phase of the Wi-Fi P2P | connection setup. The above is all in context of _coupled sink_ operation. It's written quite badly but I read it like this: b) If coupled sink initiates P2P group formation, sink should set go-intent=0 c) If source initiates P2P group formation with primary (coupled) sink, source should set go-intent=15 Implied: go-intent of the peer that does not initiate P2P group formation is not specified My first idea was that we should do what the coupled sink procedure specifies in every case: If we're a sink, set go-intent=0. If we're a source, set go-intent=15. The problem is that this seems to go directly against the test results: when we're a source and become the GO, the Netgear Push2TV will get an IP but will then try to make an RTSP connection to "1.0.168.192" -- seemingly an endianness bug in their end: I can only assume they've never tested the case where they are DHCP client. If I modify connman to use go-intent=0, then the Netgear device will become GO & DHCP server and things Just Work... At the moment I have no idea what connman or or wysiwidi should do with regards to go-intent... I'll re-check the go-intent values android source and some sinks are using at least. Jussi