GNOME Bugzilla – Bug 674542
Rygel doesn't show up on Samsung UE40ES6100 TV
Last modified: 2012-06-13 19:58:13 UTC
Rygel doesn't appear as a DLNA device on the Samsung UE40ES6100 TV (2012 model). Minidlna does show up. I see traffic between my machine and the TV, and will attach a packet capture.
Created attachment 212520 [details] Packet capture for samsung TV The Samsung UE40ES6100 has the IP address 192.168.11.116. The IP address the machine Rygel is running on is 192.168.11.101. This command was run on my Fedora F17 machine and used to capture the traffic: $ sudo tcpdump -pi p6p1 -s 0 -w rygel.pcap host 192.168.11.116 No firewall. Wireless network used to connect to TV.
Created attachment 212542 [details] Samsung <-> Minidlna tcpflow dump This is a dump of minidlna showing up successfully on the Samsung TV. I added some whitespace while I was looking around, and remove the big blob of binary PNG toward the end.
Created attachment 212543 [details] Samsung <-> Rygel tcpflow dump This is a dump of rygel *not* showing up on the Samsung TV. I added some whitespace while I was looking around. It didn't bother to ask for the PNG. In both of these tcpdlow dumps, the Samsung TV seems to request each XML file twice (ie: connection manager twice, content directory twice, and so on).
Hmmm, when i run rygel from jhbuild, I see the 'Test Streams' on my Samsung TV. Installing ffmpeg makes those Test Streams actually work.
Er... That's weird. The Samsung <-> Rygel tcpdump suggests that you already used force-downgrade-for for the Samsung?
I have it working now, oddly enough. But I ran out of time trying to filter it down into something specific. I added headers, downgrade, and tried adding some other XML elements. I'll play with this a bit more next weekend.
Would be great if we could distil this into one of our device hacks :)
Created attachment 216346 [details] [review] Fix compatibility with Samsung's UE40E* devices
Attachment 216346 [details] pushed as d804c19 - Fix compatibility with Samsung's UE40E* devices