11:18 p.m.
Hey everyone,
I am currently playing around with the WDS project and trying to get a
Microsoft WiFi Display dongle to work. On your wiki page its marked as
"working" when running the example desktop_source application (see [1]).
However I wasn't able to reproduce that yet using latest connman and wds
1.0.0. I always get a black screen and nothing is displayed. This can
have multiple reasons. I've verified that the different parts of the
stack are working and I see the gtstreamer pipeline up and delivering
buffers via UDP to the dongle.
Any thoughts on what can be wrong or hints why the dongle refuses to
display anything?
regards,
Simon
[1]: https://github.com/01org/wds/wiki
7:54 p.m.
On 10 February 2016 at 14:18, Simon Fels <simon.fels(a)canonical.com> wrote:
Hey everyone,
I am currently playing around with the WDS project and trying to get a
Microsoft WiFi Display dongle to work. On your wiki page its marked as
"working" when running the example desktop_source application (see [1]).
However I wasn't able to reproduce that yet using latest connman and wds
1.0.0. I always get a black screen and nothing is displayed. This can
have multiple reasons. I've verified that the different parts of the
stack are working and I see the gtstreamer pipeline up and delivering
buffers via UDP to the dongle.
Any thoughts on what can be wrong or hints why the dongle refuses to
display anything?
Sorry, missed this email originally...
I did play with the Microsoft dongle a long time ago... the only fatal
problems I remember with it was that it only responded properly to P2P
devices with specific device types (as mentioned in the Interoperabiility
wiki page). I've forgotten the specifics of how it failed if the source
advertized the wrong category but it sounds unlikely that your problem is
the same since you say it actually gets to streaming stage... Still, I'd
make sure the Wifi P2P device category is set to e.g. category 10,
subcategory 5 ("smartphone") to reproduce my test environment: setting the
categiry might happen automatically if you set hostnamed chassis type to
"handset" but I'm not making promises. Please double check in connman code
(or the actual Wifi P2P traffic).
If everything really is fine up to the streaming part, I can only guess
that we're sending a stream the dongle isn't prepared to handle... I'm not
up to date on how good the negotiation code is currently, but I'd make
sure that things like resolution are not too high compared to what the
dongle expects -- the desktop source implementation was very basic last I
looked: it is probably not doing a lot of checks on its own.
HTH a little,
Jussi
regards,
Simon
[1]: https://github.com/01org/wds/wiki
_______________________________________________
wysiwidi-dev mailing list
wysiwidi-dev(a)lists.01.org
https://lists.01.org/mailman/listinfo/wysiwidi-dev
8:18 p.m.
On 04.03.2016 09:54, Jussi Kukkonen wrote:
Sorry, missed this email originally...
No problem. In the mean time I got it working. However only after I've
connected an Android device first. If I don't do that the dongle doesn't
seem to open its RTP port and doesn't accept any data.
I did play with the Microsoft dongle a long time ago... the only
fatal
problems I remember with it was that it only responded properly to P2P
devices with specific device types (as mentioned in the Interoperabiility
wiki page). I've forgotten the specifics of how it failed if the source
advertized the wrong category but it sounds unlikely that your problem is
the same since you say it actually gets to streaming stage... Still, I'd
make sure the Wifi P2P device category is set to e.g. category 10,
subcategory 5 ("smartphone") to reproduce my test environment: setting the
categiry might happen automatically if you set hostnamed chassis type to
"handset" but I'm not making promises. Please double check in connman code
(or the actual Wifi P2P traffic).
Can do that and will also make sure that in our code this is correctly
implemented as our actual management daemon (see [1]) doesn't use
connman at all but directly communicates with wpa-supplicant over dbus
as long as we're missing P2P support in NetworkManager which we're bound
to in Ubuntu.
If everything really is fine up to the streaming part, I can only
guess
that we're sending a stream the dongle isn't prepared to handle... I'm not
up to date on how good the negotiation code is currently, but I'd make
sure that things like resolution are not too high compared to what the
dongle expects -- the desktop source implementation was very basic last I
looked: it is probably not doing a lot of checks on its own.
That is what I played with before as well but didn't showed any
difference. However now the whole streaming (can't speak for a gstreamer
setup as we build our owner MPEGTS packetizer + RTP sender) works
reliable and well.
regards,
Simon
[1]: https://launchpad.net/aethercast
2389
days inactive
2412
days old
2 comments
2 participants
participants (2)
-
Jussi Kukkonen -
Simon Fels