Samsung Galaxy S3, Galaxy Note 2, can't find media

On previous Samsung Galaxy phones and tablets a DLNA app was included that worked fine with Serviio. The newest devices have a revamped DLNA support, and unfortunately does not work with Serviio (which is unfortunate, as Serviio is the only DLNA server that works well with my Samsung TV and BR player, doh).

The Serviio server is visible, but when trying to connect, the app on the phone/tablet says it can't find media (location unavailable). It does lists files in a WMP share (but we all know how bad those play!)

Here's some logs:

  Code:

2012-10-09 22:32:33,847 DEBUG [FeedUpdaterThread] Checking for new and expired online resources
2012-10-09 22:32:33,847 DEBUG [OnlineRepositoryDAOImpl] Reading all OnlineRepositories
2012-10-09 22:33:01,913 DEBUG [DiscoveryAdvertisementNotifier] Multicasting SSDP alive using interface eth3 (Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller) and address 192.168.1.10, timeout = 0
2012-10-09 22:33:01,913 DEBUG [DiscoveryAdvertisementNotifier] Sending 6 'alive' messages describing device 8dee68fe-0370-3fc8-a5f5-ae4a1fb10a65
2012-10-09 22:33:03,713 DEBUG [DiscoveryAdvertisementNotifier] Will advertise again in 00:00:37
2012-10-09 22:33:33,845 DEBUG [FeedUpdaterThread] Checking for new and expired online resources
2012-10-09 22:33:33,845 DEBUG [OnlineRepositoryDAOImpl] Reading all OnlineRepositories
2012-10-09 22:33:39,655 DEBUG [WebServer] Incoming connection from /192.168.1.207:54908
2012-10-09 22:33:39,656 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.1.207
2012-10-09 22:33:39,657 DEBUG [ServiceEventSubscriptionRequestHandler] ServiceEvent renewal request received for service ContentDirectory and subscription uuid:f80edbdf-9c23-4302-b48c-8bf79c891584
2012-10-09 22:33:39,657 DEBUG [ServiceEventSubscriptionRequestHandler] Event subscription renewed for service urn:upnp-org:serviceId:ContentDirectory and subscription f80edbdf-9c23-4302-b48c-8bf79c891584
2012-10-09 22:33:41,548 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target upnp:rootdevice from address /192.168.1.207:43786
2012-10-09 22:33:41,548 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.1.207
2012-10-09 22:33:41,549 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.207:43786
2012-10-09 22:33:41,559 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:CE:1 from address /192.168.1.207:43786
2012-10-09 22:33:41,559 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.1.207
2012-10-09 22:33:41,560 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaServer:1 from address /192.168.1.207:43786
2012-10-09 22:33:41,560 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.1.207
2012-10-09 22:33:41,560 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dmc-samsung-com:device:SyncServer:1 from address /192.168.1.207:43786
2012-10-09 22:33:41,560 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.1.207
2012-10-09 22:33:41,560 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.207:43786
2012-10-09 22:33:41,561 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:samsung.com:device:MainTVServer2:1 from address /192.168.1.207:43786
2012-10-09 22:33:41,561 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.1.207
2012-10-09 22:33:41,562 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:samsung.com:device:RemoteControlReceiver:1 from address /192.168.1.207:43786
2012-10-09 22:33:41,562 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.1.207
2012-10-09 22:33:41,562 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.1.207:43786
2012-10-09 22:33:41,562 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.1.207
2012-10-09 22:33:46,561 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target upnp:rootdevice from address /192.168.1.207:50695
2012-10-09 22:33:46,561 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.1.207
2012-10-09 22:33:46,562 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:CE:1 from address /192.168.1.207:50695
2012-10-09 22:33:46,562 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.207:50695
2012-10-09 22:33:46,562 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.1.207
2012-10-09 22:33:46,563 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaServer:1 from address /192.168.1.207:50695
2012-10-09 22:33:46,563 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.1.207
2012-10-09 22:33:46,564 DEBUG [DiscoverySearchResponder] Sending 1 M-SEARCH response message(s) to /192.168.1.207:50695
2012-10-09 22:33:46,570 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:dmc-samsung-com:device:SyncServer:1 from address /192.168.1.207:50695
2012-10-09 22:33:46,570 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.1.207
2012-10-09 22:33:46,571 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:samsung.com:device:MainTVServer2:1 from address /192.168.1.207:50695
2012-10-09 22:33:46,571 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.1.207
2012-10-09 22:33:46,572 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:samsung.com:device:RemoteControlReceiver:1 from address /192.168.1.207:50695
2012-10-09 22:33:46,572 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.1.207
2012-10-09 22:33:46,573 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.1.207:50695
2012-10-09 22:33:46,573 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.1.207
2012-10-09 22:33:52,762 DEBUG [DiscoveryAdvertisementNotifier] Multicasting SSDP alive using interface eth3 (Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller) and address 192.168.1.10, timeout = 0
2012-10-09 22:33:52,762 DEBUG [DiscoveryAdvertisementNotifier] Sending 6 'alive' messages describing device 8dee68fe-0370-3fc8-a5f5-ae4a1fb10a65
2012-10-09 22:33:54,563 DEBUG [DiscoveryAdvertisementNotifier] Will advertise again in 00:00:38



[Illico]

What is the local IP address of your devices (PC, TV, Pone,etc)?

The PC is 192.168.1.10 (and has been bound to that IP, to see if it would help - it didn't), the Galaxy S3 is 192.168.1.207. All the others are in the 192.168.1.x range as well but not sure exactly of the X.

[Illico]

Do you see 192.168.1.207 device on serviio console and what is the profile selected ?

It's using the Generic DLNA profile. I have also tried all the Samsung options - none work.

[zip]

are there any requests to Browse() from the IP in your log? (I dont see it in the provided snippet)

It does not.

[zip]

Do you have TCP 8895 port open on your PC?

Firewalls and virus scanners have been disabled. I have not actively checked the port to be open (how ?) but I don't see how it could be closed. Also, at the same time, (Samsung) TV and BR can use Serviio fine, as can other mobile phones and tablets using older Samsung DLNA software. It's a specific compatibility issue between the Serviio and the *new* Samsung software.

I've also gone through the debug logs on the S3 and Note 2, unfortunately they don't print anything helpful.

Do you have TCP 8895 port open on your PC?

it is possible to customize (config files, console,...) the port 8895 (for example 8895--> 6686)?

Hi,

I'm facing the same problem. It seems that all Samsung phones that are released after the Galaxy S III have this issue. I own a Galaxy S III, Galaxy Note II and Galaxy Note 10.1 and all of them cannot access Serviio. My Galaxy S, Galaxy S II and Galaxy Note are able to.

In the older devices, we need to use AllShare application to access DLNA servers. When a server is selected, the 3 folders will be shown (Audio, Image, Video). But in the newer devices, the DLNA servers must be accessed directly from the Video Player and Gallary applications (or AllShare Play application, which seems to work with Samsung DLNA servers only). When the server is choosen, it supposed to directly show the files. So, the Gallery application would list Image only while the Video Play would list Video only. I tested this by hosting the DLNA server on one of the phones.

The newer devices also comes with AllShare Play. Serviio could not be detected by this application but it can detect all AllShare servers either from the phones or PC. When accessed via AllShare Play, after selecting a AllShare host, it would display the 3 folders (Audio, Image, Video).

Thanks.

I also have this problem. Port scan shows port 8895 is open.




Sent from my SGH-T999 using Tapatalk 2

I was hoping to find answers here, my girlfriend purchased a Galaxy Note 10.1 today and although AllSharePlay can see serviio server on my NAS, it can't read the library:

"Unable to load the list due to a network error. Refresh the page"

I've tried changing the "unrecognised device" from generic DLNA profile to all Samsung profiles, but they don't work obviously. Anyone been able to get them talking to one another?

Cheers,
Nick