Windows does not see device using libwds

[carlblakepmi]

I have libwds working on an Ubuntu 14.04 system. I can connect android devices to it and display their screens. However, windows doesn't see the device at all. What needs to be done so that windows will work with libwds? It seems to me that some additional subelements need to be added to the registration for the p2p client. Does this sound right?

[jku]

We have this as issue #70. If the issue is still the same I expect it's about missing parameters in RTSP messages.

[jku]

Actually now I see you said the sink is not seen at all, reopening. Note that other people have had this working...

[jku]

Please see the note in the end of https://github.com/01org/wds/wiki/Interoperability -- I remember sending patches for "television" chassis type to hostnamed but not sure if that and the connman change are committed... I would look for the code in connman and try to find out if it sets the correct device type.

[carlblakepmi]

On Thu, 2017-06-29 at 00:38 -0700, Jussi Kukkonen wrote: Please see the note in the end of https://github.com/01org/wds/wiki/Interoperability -- I remember sending patches for "television" chassis type to hostnamed but not sure if that and the connman change are committed... I would look for the code in connman and try to find out if it sets the correct device type.

I'm running this on an ubuntu 14.04 system. I don't believe it is using systemd although there do seem to be some elements of systemd in it. For example, hostnamectl is available and seems to allow me to set the hostname. It complains bitterly if I attempt to use it to set the chassis type to television. Do I need to patch hostnamectl to allow me to set the chassis type to television and also use a connman that handles the chassis type correctly to get this part to work? I understand that there are also problems with wds not sending rtsp parameters that are needed by windows systems. One step at a time. Thanks for your help. Carl

…

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[jku]

I'm fairly certain WDS cannot set the device category -- it's controlled by connman. I just checked and connman does not support "television" at the moment so even modifying hostnamed would not be enough...

In your position I would build a version of connman that hard codes category and subcategory for testing: that way you could make sure this really is the issue you are seeing. See plugins/wifi.c::set_device_type() in connman source code.

Afterwards you can think of a real solution -- I have a vague recollection the systemd folks objected to a "television" form factor (see CHASSIS in "man machine-info" for currently accepted values). It's possible this needs to be fixed in connman level. They won't be exactly overjoyed if you suggest additional API though...

[carlblakepmi]

On Fri, 2017-06-30 at 07:59 +0000, Jussi Kukkonen wrote: I'm fairly certain WDS cannot set the device category -- it's controlled by connman. I just checked and connman does not support "television" at the moment so even modifying hostnamed would not be enough... In your position I would build a version of connman that hard codes category and subcategory for testing: that way you could make sure this really is the issue you are seeing. See plugins/wifi.c::set_device_type() in connman source code. Afterwards you can think of a real solution -- I have a vague recollection the systemd folks objected to a "television" form factor (see CHASSIS in "man machine-info" for currently accepted values). It's possible this needs to be fixed in connman level. They won't be exactly overjoyed if you suggest additional API though...

To test and implement this I'm going to need the wps primary device type for television. Do you know what that is, or better yet a document that describes the codes for the different device types?

…

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[jku]

From https://github.com/01org/wds/wiki/Interoperability

Microsoft Wireless Display will only respond to devices of specific device type. "television" (category 7, subcategory 1) is known to work for sinks

If I remember correctly, I found these values by evesdropping on 3rd party sink and Microsoft source, but all the possible values can be found in Wi-Fi P2P spec. It was a years ago so I could be wrong though.

[carlblakepmi]

I found the WiFi p2p specs and tried hard coding connman to give 7-50f204-1 as the device type, but windows still wouldn't see it. Sent from my Galaxy Tab® A -------- Original message --------From: Jussi Kukkonen <[email protected]> Date: 7/2/17 10:22 AM (GMT-07:00) To: 01org/wds <[email protected]> Cc: cdbamiga <[email protected]>, Author <[email protected]> Subject: Re: [01org/wds] Windows does not see device using libwds (#174) From https://github.com/01org/wds/wiki/Interoperability Microsoft Wireless Display will only respond to devices of specific device type. "television" (category 7, subcategory 1) is known to work for sinks If I remember correctly, I found these values by evesdropping on 3rd party sink and Microsoft source, but all the possible values can be found in Wi-Fi P2P spec. It was a years ago so I could be wrong though. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread. {"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/01org/wds","title":"01org/wds","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/01org/wds"}},"updates":{"snippets":[{"icon":"PERSON","message":"@jku in #174: From https://github.com/01org/wds/wiki/Interoperability\r\n\u003e Microsoft Wireless Display will only respond to devices of specific device type. \"television\" (category 7, subcategory 1) is known to work for sinks\r\n\r\nIf I remember correctly, I found these values by evesdropping on 3rd party sink and Microsoft source, but all the possible values can be found in Wi-Fi P2P spec. It was a years ago so I could be wrong though."}],"action":{"name":"View Issue","url":"#174 (comment)"}}}

[carlblakepmi]

I updated connman from V1.28 to V1.34 and now windows devices see my device as a display. I didn't have to make any other changes other than this.

It still won't connect, but at least it sees my device. During the connection sequence it doesn't seem to get to the point of establishing IP addresses.