Jump to content


Photo
unresponsive

Emby for Android TV becomes unresponsive as it attempts to establish connection with server

android tv

Best Answer FordGT90Concept , 23 December 2016 - 05:06 PM

This appears to be fixed in Emby Server 3.1 and Android TV 1.3

Go to the full post


  • Please log in to reply
17 replies to this topic

#1 FordGT90Concept OFFLINE  

FordGT90Concept

    Advanced Member

  • Members
  • 720 posts
  • Local time: 07:12 PM

Posted 19 October 2016 - 09:24 PM

This problem has been going on for a while and I upgraded the server from HDDs to SSDs to try to speed it up but it didn't help. This is an issue regardless if the device is connected via wireless or wired. It manifests in two scenarios:
1) Cold booting Android TV device, go straight to Emby, and it can take up to a minute to get the user list. How this usually presents:
a) spinning dial
B) sign in with Emby Connect screen
c) back out of app (not using Emby Connect) and run Emby again so it retries with the manual data
d) repeat steps 1-3 or presented with user login screen

2) The device was put to sleep with Emby running (e.g. it is sitting at TV show info screen). In this scenario, Emby is completely unresponsive with no spinning dial, error message, or anything until reconnection is established with the server.


In both situations, providing the user with more information would be hugely beneficial. I propose the following stages:

1) Waiting for network connection... Do I have an IP address?
2) Network connection found... I have an IP address.
3) Attempting to reconnect with Emby Server <(address if available)>... Does an Emby Server exist at the location I've been instructed to check?
4) Logging in <username>... Yes, try logging in as the last user.*

At any point in this reconnection sequence, allow "abort" which takes you back to the Emby Connect/manual login screen. If the above times out, additionally offer a "retry" button to restart the connection process.



* More broadly, it would be nice if each application/device had a setting to choose between multi-user and single-user. Some devices tend to get used by more than one user so the login screen should always be shown; some devices tend to get used by one user so it should always automatically log in. I think the web UI has this feature but Emby Home Theater and Android TV do not.

Edited by FordGT90Concept, 19 October 2016 - 09:29 PM.

  • Macburp likes this

#2 CBers OFFLINE  

CBers

    Advanced Member

  • Moderators
  • 15746 posts
  • Local time: 01:12 AM
  • LocationEngland

Posted 20 October 2016 - 03:32 AM

@FordGT90Concept

 

You'll have to supply the server log for when you see the unresponsiveness.

 

I've also had it in the past, but it's much better these days.

 

Do you have the SHOW PREMIERES row enabled ?? If so, try disabling it as this tend to make a lot of calls to the server.



#3 FordGT90Concept OFFLINE  

FordGT90Concept

    Advanced Member

  • Members
  • 720 posts
  • Local time: 07:12 PM

Posted 20 October 2016 - 04:41 AM

I think this is the relevant part which shows pretty clearly the server isn't at fault (done inside of a second):
2016-10-19 19:58:29.4492 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Users/82677126f7ef44ea9c710f93b8d35385/Items/9564fe2ffd880ed93b4045050a7177f1?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-19 19:58:29.4805 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 31ms. http://192.168.0.128:8096/emby/Users/82677126f7ef44ea9c710f93b8d35385/Items/9564fe2ffd880ed93b4045050a7177f1?format=json
2016-10-19 19:58:46.5601 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/system/info/public?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-19 19:58:46.6070 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 47ms. http://192.168.0.128:8096/emby/system/info/public?format=json
2016-10-19 19:58:46.6539 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/system/info?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-19 19:58:46.6851 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 31ms. http://192.168.0.128:8096/emby/system/info?format=json
2016-10-19 19:58:46.7320 Info HttpServer: HTTP GET http://192.168.0.128:8096/mediabrowser/users/82677126f7ef44ea9c710f93b8d35385?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-19 19:58:46.7476 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 16ms. http://192.168.0.128:8096/mediabrowser/users/82677126f7ef44ea9c710f93b8d35385?format=json
2016-10-19 19:58:46.8414 Info HttpServer: HTTP POST http://192.168.0.128:8096/emby/Sessions/Capabilities/Full. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-19 19:58:46.8414 Info HttpServer: WS ws://192.168.0.128:8096/emby/embywebsocket?api_key=5fd678faa9ad4621b2f0ddba7077a345&deviceId=f4143212e5cd946d. UserAgent: 
2016-10-19 19:58:46.8570 Info HttpServer: HTTP Response 204 to 192.168.0.214. Time: 16ms. http://192.168.0.128:8096/emby/Sessions/Capabilities/Full
2016-10-19 19:58:47.9039 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/system/info/public?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-19 19:58:47.9351 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 31ms. http://192.168.0.128:8096/emby/system/info/public?format=json
2016-10-19 19:58:47.9664 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/system/info?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-19 19:58:47.9976 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 31ms. http://192.168.0.128:8096/emby/system/info?format=json
2016-10-19 19:58:48.0289 Info HttpServer: HTTP GET http://192.168.0.128:8096/mediabrowser/users/82677126f7ef44ea9c710f93b8d35385?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-19 19:58:48.0445 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 16ms. http://192.168.0.128:8096/mediabrowser/users/82677126f7ef44ea9c710f93b8d35385?format=json
2016-10-19 19:58:48.1383 Info HttpServer: HTTP POST http://192.168.0.128:8096/emby/Sessions/Capabilities/Full. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-19 19:58:48.1539 Info HttpServer: HTTP Response 204 to 192.168.0.214. Time: 16ms. http://192.168.0.128:8096/emby/Sessions/Capabilities/Full
2016-10-19 19:58:48.1851 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Users/Public?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-19 19:58:48.1851 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 0ms. http://192.168.0.128:8096/emby/Users/Public?format=json
2016-10-19 19:58:52.3101 Info HttpServer: HTTP POST http://192.168.0.128:8096/emby/Users/AuthenticateByName?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-19 19:58:52.3257 Info UserManager: Authentication request for Lauren has succeeded.
2016-10-19 19:58:52.3257 Info SessionManager: Reissuing access token: 5fd678faa9ad4621b2f0ddba7077a345
2016-10-19 19:58:52.3413 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 31ms. http://192.168.0.128:8096/emby/Users/AuthenticateByName?format=json
2016-10-19 19:58:52.5757 Info HttpServer: HTTP POST http://192.168.0.128:8096/emby/Sessions/Capabilities/Full. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-19 19:58:52.6226 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/System/Info?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-19 19:58:52.6226 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/System/Endpoint?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-19 19:58:52.6382 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Registrations/androidtv?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-19 19:58:52.6382 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 16ms. http://192.168.0.128:8096/emby/System/Endpoint?format=json
2016-10-19 19:58:52.6382 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 0ms. http://192.168.0.128:8096/emby/Registrations/androidtv?format=json
2016-10-19 19:58:52.6538 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Users/82677126f7ef44ea9c710f93b8d35385/Views?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-19 19:58:52.6538 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 31ms. http://192.168.0.128:8096/emby/System/Info?format=json
2016-10-19 19:58:52.6538 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 0ms. http://192.168.0.128:8096/emby/Users/82677126f7ef44ea9c710f93b8d35385/Views?format=json
2016-10-19 19:58:52.6851 Info HttpServer: HTTP Response 204 to 192.168.0.214. Time: 109ms. http://192.168.0.128:8096/emby/Sessions/Capabilities/Full
I've never seen "show premieres" but I'm guessing this is something in the Android TV app and not in the server right?

Edited by FordGT90Concept, 20 October 2016 - 04:42 AM.


#4 CBers OFFLINE  

CBers

    Advanced Member

  • Moderators
  • 15746 posts
  • Local time: 01:12 AM
  • LocationEngland

Posted 20 October 2016 - 04:47 AM

I've never seen "show premieres" but I'm guessing this is something in the Android TV app and not in the server right?

 

Yes. I think it's disabled by default.

 

What version of the ATV app are you running ??

 

What device are you running it on ??



#5 FordGT90Concept OFFLINE  

FordGT90Concept

    Advanced Member

  • Members
  • 720 posts
  • Local time: 07:12 PM

Posted 20 October 2016 - 05:49 AM

I deleted all of the logs on the server and the following box has been off for at least 6 hours:
Leelbox Q1 Master (Android 6.0.1, Amlogic S905X)
App version: 1.2.66g

Here's the logs from the server:
2016-10-20 04:38:56.0571 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/system/info/public?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:38:56.0727 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 16ms. http://192.168.0.128:8096/emby/system/info/public?format=json
2016-10-20 04:38:56.1196 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/system/info?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:38:56.1508 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 31ms. http://192.168.0.128:8096/emby/system/info?format=json
2016-10-20 04:38:56.1977 Info HttpServer: HTTP GET http://192.168.0.128:8096/mediabrowser/users/82677126f7ef44ea9c710f93b8d35385?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:38:56.1977 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 0ms. http://192.168.0.128:8096/mediabrowser/users/82677126f7ef44ea9c710f93b8d35385?format=json
2016-10-20 04:38:56.3852 Info HttpServer: HTTP POST http://192.168.0.128:8096/emby/Sessions/Capabilities/Full. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:38:56.3852 Info HttpServer: WS ws://192.168.0.128:8096/emby/embywebsocket?api_key=5fd678faa9ad4621b2f0ddba7077a345&deviceId=f4143212e5cd946d. UserAgent: 
2016-10-20 04:38:56.4008 Info HttpServer: HTTP Response 204 to 192.168.0.214. Time: 16ms. http://192.168.0.128:8096/emby/Sessions/Capabilities/Full
2016-10-20 04:38:57.4476 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/system/info/public?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:38:57.4633 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 16ms. http://192.168.0.128:8096/emby/system/info/public?format=json
2016-10-20 04:38:57.4946 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/system/info?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:38:57.5258 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 31ms. http://192.168.0.128:8096/emby/system/info?format=json
2016-10-20 04:38:57.5570 Info HttpServer: HTTP GET http://192.168.0.128:8096/mediabrowser/users/82677126f7ef44ea9c710f93b8d35385?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:38:57.5727 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 16ms. http://192.168.0.128:8096/mediabrowser/users/82677126f7ef44ea9c710f93b8d35385?format=json
2016-10-20 04:38:57.7445 Info HttpServer: HTTP POST http://192.168.0.128:8096/emby/Sessions/Capabilities/Full. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:38:57.7445 Info HttpServer: HTTP Response 204 to 192.168.0.214. Time: 0ms. http://192.168.0.128:8096/emby/Sessions/Capabilities/Full
2016-10-20 04:38:57.7758 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Users/Public?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:38:57.7758 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 0ms. http://192.168.0.128:8096/emby/Users/Public?format=json
2016-10-20 04:38:58.0258 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Users/82677126f7ef44ea9c710f93b8d35385/Images/Primary?MaxHeight=370&EnableImageEnhancers=true. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:38:58.0258 Error ServiceStackHost: ServiceBase<TRequest>::Service Exception
	*** Error Report ***
	Version: 3.0.8200.0
	Command line: C:\Users\Lee\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe
	Operating system: Microsoft Windows NT 6.2.9200.0
	Processor count: 8
	64-Bit OS: True
	64-Bit Process: True
	Program data path: C:\Users\Lee\AppData\Roaming\Emby-Server
	Application Path: C:\Users\Lee\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe
	Lauren does not have an image of type Primary
	MediaBrowser.Common.Extensions.ResourceNotFoundException
	   at MediaBrowser.Api.Images.ImageService.GetImage(ImageRequest request, IHasImages item, Boolean isHeadRequest)
	   at ServiceStack.Host.ServiceRunner`1.Execute(IRequest request, Object instance, TRequest requestDto)
	
2016-10-20 04:38:58.0258 Error HttpServer: Error processing request for /emby/Users/82677126f7ef44ea9c710f93b8d35385/Images/Primary?MaxHeight=370&EnableImageEnhancers=true
	*** Error Report ***
	Version: 3.0.8200.0
	Command line: C:\Users\Lee\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe
	Operating system: Microsoft Windows NT 6.2.9200.0
	Processor count: 8
	64-Bit OS: True
	64-Bit Process: True
	Program data path: C:\Users\Lee\AppData\Roaming\Emby-Server
	Application Path: C:\Users\Lee\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe
	Lauren does not have an image of type Primary
	ServiceStack.HttpError
	No Stack Trace Available
	InnerException: MediaBrowser.Common.Extensions.ResourceNotFoundException
	Lauren does not have an image of type Primary
	   at MediaBrowser.Api.Images.ImageService.GetImage(ImageRequest request, IHasImages item, Boolean isHeadRequest)
	   at ServiceStack.Host.ServiceRunner`1.Execute(IRequest request, Object instance, TRequest requestDto)
	
2016-10-20 04:38:58.0258 Error ServiceStackHost: [::ffff:192.168.0.128]:8096 Request not found: /emby/Users/82677126f7ef44ea9c710f93b8d35385/Images/Primary?MaxHeight=370&EnableImageEnhancers=true
2016-10-20 04:38:58.0258 Info HttpServer: HTTP Response 404 to 192.168.0.214. Time: 0ms. http://192.168.0.128:8096/emby/Users/82677126f7ef44ea9c710f93b8d35385/Images/Primary?MaxHeight=370&EnableImageEnhancers=true
2016-10-20 04:38:58.0258 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Users/04e654fe79f64f44b5f13442efcc2882/Images/Primary?MaxHeight=370&EnableImageEnhancers=true. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:38:58.0258 Error ServiceStackHost: ServiceBase<TRequest>::Service Exception
	*** Error Report ***
	Version: 3.0.8200.0
	Command line: C:\Users\Lee\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe
	Operating system: Microsoft Windows NT 6.2.9200.0
	Processor count: 8
	64-Bit OS: True
	64-Bit Process: True
	Program data path: C:\Users\Lee\AppData\Roaming\Emby-Server
	Application Path: C:\Users\Lee\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe
	Lee does not have an image of type Primary
	MediaBrowser.Common.Extensions.ResourceNotFoundException
	   at MediaBrowser.Api.Images.ImageService.GetImage(ImageRequest request, IHasImages item, Boolean isHeadRequest)
	   at ServiceStack.Host.ServiceRunner`1.Execute(IRequest request, Object instance, TRequest requestDto)
	
2016-10-20 04:38:58.0258 Error HttpServer: Error processing request for /emby/Users/04e654fe79f64f44b5f13442efcc2882/Images/Primary?MaxHeight=370&EnableImageEnhancers=true
	*** Error Report ***
	Version: 3.0.8200.0
	Command line: C:\Users\Lee\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe
	Operating system: Microsoft Windows NT 6.2.9200.0
	Processor count: 8
	64-Bit OS: True
	64-Bit Process: True
	Program data path: C:\Users\Lee\AppData\Roaming\Emby-Server
	Application Path: C:\Users\Lee\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe
	Lee does not have an image of type Primary
	ServiceStack.HttpError
	No Stack Trace Available
	InnerException: MediaBrowser.Common.Extensions.ResourceNotFoundException
	Lee does not have an image of type Primary
	   at MediaBrowser.Api.Images.ImageService.GetImage(ImageRequest request, IHasImages item, Boolean isHeadRequest)
	   at ServiceStack.Host.ServiceRunner`1.Execute(IRequest request, Object instance, TRequest requestDto)
	
2016-10-20 04:38:58.0258 Error ServiceStackHost: [::ffff:192.168.0.128]:8096 Request not found: /emby/Users/04e654fe79f64f44b5f13442efcc2882/Images/Primary?MaxHeight=370&EnableImageEnhancers=true
2016-10-20 04:38:58.0258 Info HttpServer: HTTP Response 404 to 192.168.0.214. Time: 0ms. http://192.168.0.128:8096/emby/Users/04e654fe79f64f44b5f13442efcc2882/Images/Primary?MaxHeight=370&EnableImageEnhancers=true
2016-10-20 04:38:58.0414 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Users/35fbf5041d86427d9e10673642bf1317/Images/Primary?MaxHeight=370&EnableImageEnhancers=true. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:38:58.0414 Error ServiceStackHost: ServiceBase<TRequest>::Service Exception
	*** Error Report ***
	Version: 3.0.8200.0
	Command line: C:\Users\Lee\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe
	Operating system: Microsoft Windows NT 6.2.9200.0
	Processor count: 8
	64-Bit OS: True
	64-Bit Process: True
	Program data path: C:\Users\Lee\AppData\Roaming\Emby-Server
	Application Path: C:\Users\Lee\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe
	Lynn does not have an image of type Primary
	MediaBrowser.Common.Extensions.ResourceNotFoundException
	   at MediaBrowser.Api.Images.ImageService.GetImage(ImageRequest request, IHasImages item, Boolean isHeadRequest)
	   at ServiceStack.Host.ServiceRunner`1.Execute(IRequest request, Object instance, TRequest requestDto)
	
2016-10-20 04:38:58.0414 Error HttpServer: Error processing request for /emby/Users/35fbf5041d86427d9e10673642bf1317/Images/Primary?MaxHeight=370&EnableImageEnhancers=true
	*** Error Report ***
	Version: 3.0.8200.0
	Command line: C:\Users\Lee\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe
	Operating system: Microsoft Windows NT 6.2.9200.0
	Processor count: 8
	64-Bit OS: True
	64-Bit Process: True
	Program data path: C:\Users\Lee\AppData\Roaming\Emby-Server
	Application Path: C:\Users\Lee\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe
	Lynn does not have an image of type Primary
	ServiceStack.HttpError
	No Stack Trace Available
	InnerException: MediaBrowser.Common.Extensions.ResourceNotFoundException
	Lynn does not have an image of type Primary
	   at MediaBrowser.Api.Images.ImageService.GetImage(ImageRequest request, IHasImages item, Boolean isHeadRequest)
	   at ServiceStack.Host.ServiceRunner`1.Execute(IRequest request, Object instance, TRequest requestDto)
	
2016-10-20 04:38:58.0414 Error ServiceStackHost: [::ffff:192.168.0.128]:8096 Request not found: /emby/Users/35fbf5041d86427d9e10673642bf1317/Images/Primary?MaxHeight=370&EnableImageEnhancers=true
2016-10-20 04:38:58.0414 Info HttpServer: HTTP Response 404 to 192.168.0.214. Time: 0ms. http://192.168.0.128:8096/emby/Users/35fbf5041d86427d9e10673642bf1317/Images/Primary?MaxHeight=370&EnableImageEnhancers=true
2016-10-20 04:39:16.7599 Info HttpServer: HTTP POST http://192.168.0.128:8096/emby/Users/AuthenticateByName?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:39:16.7599 Info UserManager: Authentication request for Lauren has succeeded.
2016-10-20 04:39:16.7755 Info SessionManager: Reissuing access token: 5fd678faa9ad4621b2f0ddba7077a345
2016-10-20 04:39:16.7755 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 16ms. http://192.168.0.128:8096/emby/Users/AuthenticateByName?format=json
2016-10-20 04:39:17.0099 Info HttpServer: HTTP POST http://192.168.0.128:8096/emby/Sessions/Capabilities/Full. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:39:17.0255 Info HttpServer: HTTP Response 204 to 192.168.0.214. Time: 16ms. http://192.168.0.128:8096/emby/Sessions/Capabilities/Full
2016-10-20 04:39:17.1505 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Registrations/androidtv?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:39:17.1661 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Users/82677126f7ef44ea9c710f93b8d35385/Views?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:39:17.1661 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/System/Endpoint?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:39:17.1661 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 0ms. http://192.168.0.128:8096/emby/Users/82677126f7ef44ea9c710f93b8d35385/Views?format=json
2016-10-20 04:39:17.1661 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 0ms. http://192.168.0.128:8096/emby/System/Endpoint?format=json
2016-10-20 04:39:17.1817 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/System/Info?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:39:17.2130 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 31ms. http://192.168.0.128:8096/emby/System/Info?format=json
2016-10-20 04:39:17.2130 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Playback/BitrateTest?Size=1000000. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:39:17.2286 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Shows/NextUp?Limit=3&UserId=82677126f7ef44ea9c710f93b8d35385&Fields=PrimaryImageAspectRatio&format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:39:17.2286 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 16ms. http://192.168.0.128:8096/emby/Playback/BitrateTest?Size=1000000
2016-10-20 04:39:17.2286 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Users/82677126f7ef44ea9c710f93b8d35385/Items?Filters=IsResumable&Fields=PrimaryImageAspectRatio,Overview,ItemCounts,DisplayPreferencesId&recursive=true&sortOrder=Descending&Limit=2&SortBy=DatePlayed&IncludeItemTypes=Movie&format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:39:17.2442 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 16ms. http://192.168.0.128:8096/emby/Users/82677126f7ef44ea9c710f93b8d35385/Items?Filters=IsResumable&Fields=PrimaryImageAspectRatio,Overview,ItemCounts,DisplayPreferencesId&recursive=true&sortOrder=Descending&Limit=2&SortBy=DatePlayed&IncludeItemTypes=Movie&format=json
2016-10-20 04:39:17.3223 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Playback/BitrateTest?Size=3000000. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:39:17.3379 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 16ms. http://192.168.0.128:8096/emby/Playback/BitrateTest?Size=3000000
2016-10-20 04:39:17.4161 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Users/82677126f7ef44ea9c710f93b8d35385/Views?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:39:17.4161 Info HttpClient: HttpClientManager POST: https://www.mb3admin.com/admin/service/registration/validate
2016-10-20 04:39:17.4161 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Users/82677126f7ef44ea9c710f93b8d35385/Items?Filters=IsResumable&ImageTypeLimit=1&Fields=PrimaryImageAspectRatio,Overview,ItemCounts,DisplayPreferencesId&MediaTypes=Video&EnableTotalRecordCount=false&recursive=true&ExcludeLocationTypes=Virtual&sortOrder=Descending&Limit=50&SortBy=DatePlayed&format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:39:17.4317 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 16ms. http://192.168.0.128:8096/emby/Users/82677126f7ef44ea9c710f93b8d35385/Views?format=json
2016-10-20 04:39:17.4317 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 16ms. http://192.168.0.128:8096/emby/Users/82677126f7ef44ea9c710f93b8d35385/Items?Filters=IsResumable&ImageTypeLimit=1&Fields=PrimaryImageAspectRatio,Overview,ItemCounts,DisplayPreferencesId&MediaTypes=Video&EnableTotalRecordCount=false&recursive=true&ExcludeLocationTypes=Virtual&sortOrder=Descending&Limit=50&SortBy=DatePlayed&format=json
2016-10-20 04:39:17.4473 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Users/82677126f7ef44ea9c710f93b8d35385/Items/Latest?Limit=50&IncludeItemTypes=Movie&Fields=PrimaryImageAspectRatio,Overview&GroupItems=false&format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:39:17.4473 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Shows/NextUp?Limit=50&UserId=82677126f7ef44ea9c710f93b8d35385&ImageTypeLimit=1&Fields=PrimaryImageAspectRatio,Overview&format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:39:17.4630 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 234ms. http://192.168.0.128:8096/emby/Shows/NextUp?Limit=3&UserId=82677126f7ef44ea9c710f93b8d35385&Fields=PrimaryImageAspectRatio&format=json
2016-10-20 04:39:17.4786 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/LiveTv/Programs/Recommended?Limit=20&UserId=82677126f7ef44ea9c710f93b8d35385&IsAiring=true&EnableTotalRecordCount=false&ImageTypeLimit=1&Fields=Overview,PrimaryImageAspectRatio,ChannelInfo&format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:39:17.4786 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 31ms. http://192.168.0.128:8096/emby/Users/82677126f7ef44ea9c710f93b8d35385/Items/Latest?Limit=50&IncludeItemTypes=Movie&Fields=PrimaryImageAspectRatio,Overview&GroupItems=false&format=json
2016-10-20 04:39:17.5098 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/LiveTv/Recordings?EnableImages=true&Limit=40&UserId=82677126f7ef44ea9c710f93b8d35385&Id=82677126f7ef44ea9c710f93b8d35385&Fields=Overview,PrimaryImageAspectRatio&format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:39:17.5879 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 109ms. http://192.168.0.128:8096/emby/LiveTv/Programs/Recommended?Limit=20&UserId=82677126f7ef44ea9c710f93b8d35385&IsAiring=true&EnableTotalRecordCount=false&ImageTypeLimit=1&Fields=Overview,PrimaryImageAspectRatio,ChannelInfo&format=json
2016-10-20 04:39:17.6348 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 484ms. http://192.168.0.128:8096/emby/Registrations/androidtv?format=json
2016-10-20 04:39:17.6661 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 156ms. http://192.168.0.128:8096/emby/LiveTv/Recordings?EnableImages=true&Limit=40&UserId=82677126f7ef44ea9c710f93b8d35385&Id=82677126f7ef44ea9c710f93b8d35385&Fields=Overview,PrimaryImageAspectRatio&format=json
2016-10-20 04:39:17.7130 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Users/82677126f7ef44ea9c710f93b8d35385/Items?Filters=IsUnplayed&Fields=PrimaryImageAspectRatio,Overview,ItemCounts,DisplayPreferencesId&recursive=true&sortOrder=Descending&Limit=4&SortBy=DateCreated&IncludeItemTypes=Movie&format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:39:17.7442 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 31ms. http://192.168.0.128:8096/emby/Users/82677126f7ef44ea9c710f93b8d35385/Items?Filters=IsUnplayed&Fields=PrimaryImageAspectRatio,Overview,ItemCounts,DisplayPreferencesId&recursive=true&sortOrder=Descending&Limit=4&SortBy=DateCreated&IncludeItemTypes=Movie&format=json
2016-10-20 04:39:17.7911 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 344ms. http://192.168.0.128:8096/emby/Shows/NextUp?Limit=50&UserId=82677126f7ef44ea9c710f93b8d35385&ImageTypeLimit=1&Fields=PrimaryImageAspectRatio,Overview&format=json
2016-10-20 04:39:18.1817 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Items/9797c5d196b922a4f354ea0013a99f03/Images/Thumb?MaxHeight=300&EnableImageEnhancers=true&Tag=aeca1c020773fee9a91306cd78ae19fa. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:39:18.1973 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Items/f137a2dd21bbc1b99aa5c0f6bf02a805/Images/Primary?MaxHeight=300&EnableImageEnhancers=true&Tag=e56c98f23764467c06e62874170d39bc. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:39:18.4317 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 250ms. http://192.168.0.128:8096/emby/Items/9797c5d196b922a4f354ea0013a99f03/Images/Thumb?MaxHeight=300&EnableImageEnhancers=true&Tag=aeca1c020773fee9a91306cd78ae19fa
2016-10-20 04:39:18.4942 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Items/aace74323dc0131b345c60f91a7af87b/Images/Primary?MaxHeight=300&EnableImageEnhancers=true&Tag=148335e02546d1c31e1057a34ed81258. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:39:18.5098 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 16ms. http://192.168.0.128:8096/emby/Items/aace74323dc0131b345c60f91a7af87b/Images/Primary?MaxHeight=300&EnableImageEnhancers=true&Tag=148335e02546d1c31e1057a34ed81258
2016-10-20 04:39:18.5567 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 359ms. http://192.168.0.128:8096/emby/Items/f137a2dd21bbc1b99aa5c0f6bf02a805/Images/Primary?MaxHeight=300&EnableImageEnhancers=true&Tag=e56c98f23764467c06e62874170d39bc
2016-10-20 04:39:18.6661 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Items/d927ab72688990b4680b002bb498b59f/Images/Primary?MaxHeight=300&EnableImageEnhancers=true&Tag=cc582053f8eaa0e6fe13b7e7622149f4. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:39:18.7755 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Items/d927ab72688990b4680b002bb498b59f/Images/Primary?MaxHeight=300&EnableImageEnhancers=true&Tag=cc582053f8eaa0e6fe13b7e7622149f4. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:39:18.8223 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 156ms. http://192.168.0.128:8096/emby/Items/d927ab72688990b4680b002bb498b59f/Images/Primary?MaxHeight=300&EnableImageEnhancers=true&Tag=cc582053f8eaa0e6fe13b7e7622149f4
2016-10-20 04:39:18.9317 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 156ms. http://192.168.0.128:8096/emby/Items/d927ab72688990b4680b002bb498b59f/Images/Primary?MaxHeight=300&EnableImageEnhancers=true&Tag=cc582053f8eaa0e6fe13b7e7622149f4
2016-10-20 04:39:19.3223 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Items/f8620bb518728f04db29c683920d5164/Images/Primary?MaxHeight=300&EnableImageEnhancers=true&Tag=f9dbeb8b6b3f5b25ea87dbfec818f4ea. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:39:19.3223 Info HttpClient: HttpClientManager GET: https://s3.amazonaws.com/schedulesdirect/assets/p185953_l_h5_aa.jpg
2016-10-20 04:39:19.3223 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Items/4575225d691fbe27ae9fa1baafad294b/Images/Primary?MaxHeight=300&EnableImageEnhancers=true&Tag=da9986bc4f140140443c6df158a333b1. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:39:19.3380 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Items/25cef705c89f52fa423fcf6106fee687/Images/Primary?MaxHeight=300&EnableImageEnhancers=true&Tag=53fb2ef45b3da988a01b876d629bda5f. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:39:19.6973 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Items/d927ab72688990b4680b002bb498b59f/Images/Backdrop/0?MaxWidth=1200&EnableImageEnhancers=true&Tag=17a53a7bd8fbedf6c3ffd84a741c5f7d. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:39:19.9161 Info HttpClient: HttpClientManager GET: https://s3.amazonaws.com/schedulesdirect/assets/p504968_i_v6_aa.jpg
2016-10-20 04:39:19.9161 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 594ms. http://192.168.0.128:8096/emby/Items/f8620bb518728f04db29c683920d5164/Images/Primary?MaxHeight=300&EnableImageEnhancers=true&Tag=f9dbeb8b6b3f5b25ea87dbfec818f4ea
2016-10-20 04:39:19.9473 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Items/69bc4636f043329dfb66fa1e9e30cdb7/Images/Primary?MaxHeight=300&EnableImageEnhancers=true&Tag=d650ec384107f17b1c2229a4a838b17e. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:39:19.9473 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 0ms. http://192.168.0.128:8096/emby/Items/69bc4636f043329dfb66fa1e9e30cdb7/Images/Primary?MaxHeight=300&EnableImageEnhancers=true&Tag=d650ec384107f17b1c2229a4a838b17e
2016-10-20 04:39:19.9942 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 297ms. http://192.168.0.128:8096/emby/Items/d927ab72688990b4680b002bb498b59f/Images/Backdrop/0?MaxWidth=1200&EnableImageEnhancers=true&Tag=17a53a7bd8fbedf6c3ffd84a741c5f7d
2016-10-20 04:39:19.9942 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Items/f41e73c85760f34cb19ef4518cf7ddea/Images/Primary?MaxHeight=300&EnableImageEnhancers=true&Tag=6d7346c921715ffb2585d42882b622bf. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-20 04:39:20.0723 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 78ms. http://192.168.0.128:8096/emby/Items/f41e73c85760f34cb19ef4518cf7ddea/Images/Primary?MaxHeight=300&EnableImageEnhancers=true&Tag=6d7346c921715ffb2585d42882b622bf
2016-10-20 04:39:20.0880 Info HttpClient: HttpClientManager GET: https://s3.amazonaws.com/schedulesdirect/assets/p325642_l_h5_aa.jpg
2016-10-20 04:39:20.1036 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 781ms. http://192.168.0.128:8096/emby/Items/4575225d691fbe27ae9fa1baafad294b/Images/Primary?MaxHeight=300&EnableImageEnhancers=true&Tag=da9986bc4f140140443c6df158a333b1
2016-10-20 04:39:20.2755 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 937ms. http://192.168.0.128:8096/emby/Items/25cef705c89f52fa423fcf6106fee687/Images/Primary?MaxHeight=300&EnableImageEnhancers=true&Tag=53fb2ef45b3da988a01b876d629bda5f
Note the timestamps:
04:38:56.0571 -> 04:38:58.0414
I sat here for a bit trying to decide what to do...
04:39:16.7599 -> 04:39:20.2755
Logged in to get the version number then closed everything down...

This doesn't show the problem at all because I counted to 20 seconds the first time I tried to connect and I think it didn't connect until the third time (so very likely a full minute of waiting around). The problem is 100% in the Android TV client. That said, I clicked "Send Logs" from the app in that time frame above. Hopefully there's something enlightening in there.

Edited by FordGT90Concept, 20 October 2016 - 05:51 AM.


#6 CBers OFFLINE  

CBers

    Advanced Member

  • Moderators
  • 15746 posts
  • Local time: 01:12 AM
  • LocationEngland

Posted 20 October 2016 - 07:01 AM

Hopefully EBR can shed some light on this.

 

Is that Android box a proper Android TV box ??



#7 FordGT90Concept OFFLINE  

FordGT90Concept

    Advanced Member

  • Members
  • 720 posts
  • Local time: 07:12 PM

Posted 20 October 2016 - 07:40 AM

What do you mean by that? It's one of these:
https://www.amazon.c...g/dp/B01J9ZSG2U

It has happened on an Amlogic S905 (Android 5.1.1) Leelbox too.

The device itself is responsive when this happens.


The key is cold boot. If it was on an hour or two ago, it will likely reach the server quickly. If it has been off for many hours, this delay occurs.

Edited by FordGT90Concept, 20 October 2016 - 07:44 AM.


#8 CBers OFFLINE  

CBers

    Advanced Member

  • Moderators
  • 15746 posts
  • Local time: 01:12 AM
  • LocationEngland

Posted 20 October 2016 - 07:54 AM

Is it a Google certified Android TV box ??

 

Just asking, not casting aspersions :)



#9 FordGT90Concept OFFLINE  

FordGT90Concept

    Advanced Member

  • Members
  • 720 posts
  • Local time: 07:12 PM

Posted 20 October 2016 - 08:20 AM

Oh, no, it definitely isn't certified. AFAIK, there's only three:
-Xiaomi Mi Box
-NVIDIA SHIELD
-Razer Forge TV

Edited by FordGT90Concept, 20 October 2016 - 08:21 AM.


#10 CBers OFFLINE  

CBers

    Advanced Member

  • Moderators
  • 15746 posts
  • Local time: 01:12 AM
  • LocationEngland

Posted 20 October 2016 - 08:27 AM

Four, if you included Nexus Player, but these are now discontinued.

I wasn't aware that the Razer Forge was an ATV box.

#11 ebr OFFLINE  

ebr

    Chief Bottle Washer

  • Administrators
  • 50887 posts
  • Local time: 08:12 PM

Posted 20 October 2016 - 10:18 AM

* More broadly, it would be nice if each application/device had a setting to choose between multi-user and single-user. Some devices tend to get used by more than one user so the login screen should always be shown; some devices tend to get used by one user so it should always automatically log in. I think the web UI has this feature but Emby Home Theater and Android TV do not.

 

The Android TV app does have this option.  It is the very first option on the settings page.


  • FordGT90Concept likes this

#12 ebr OFFLINE  

ebr

    Chief Bottle Washer

  • Administrators
  • 50887 posts
  • Local time: 08:12 PM

Posted 20 October 2016 - 10:30 AM

This issue is either at the network layer or the server end.  Are you sure your server wasn't asleep during the first attempt to contact it?  The server log you posted doesn't start until the device is actually able to connect to it.  What is before that in the server log?

 

The app log you sent shows the device trying to contact your server four times and all of them timing out and you being kicked to the Connect screen.   Automatic server discovery also fails during this time.

 

Then, when either the server wakes up or the network properly initializes, we connect fine.  That's when your server log starts.

 

I'll have to look at some ways to provide more UI feedback when this type of thing is happening.



#13 FordGT90Concept OFFLINE  

FordGT90Concept

    Advanced Member

  • Members
  • 720 posts
  • Local time: 07:12 PM

Posted 20 October 2016 - 08:08 PM

I was listening to music on my computer through Emby Home Theater within 15 minutes of clearing the logs and running the test. My server never sleeps.

What you see there pasted above is literally all of it (deleted logs, powered on device, got connected, sent logs, powered off device, copied logs here).

The app log sounds accurate.


What does "automatic server discovery" entail because I don't think I've ever seen it work (always have to type in the IP). Server is at 192.168.0.128:8096 and this particular Leelbox is at 192.168.0.214. I can't think of any reason why they wouldn't find each other quickly.



Edit: I went to the same device (192.168.0.214) after it has been off since the last time I tried (about 16 hours ago). The first thing I did this time was open Firefox. It opened up the Yahoo search page just fine. I backed out of that and opened up Emby. The same bug presented itself (took 2 or 3 attempts to connect). I uploaded the app logs again but I doubt there's anything new in there.

I also know the server is not sleeping this time because it was actively streaming the Presidential Debate to a different Leelbox (Amlogic S905, Android 5.1.1).


So it definitely has network access and the server is not asleep.

I am not using Emby Connect and the server IP is static at 192.168.0.128:8096


Edit: It should be noted that my server is Windows Server 2012 R2 and it is a Windows Domain Controller for Active Directory. I doubt that matters but...it might.

Edited by FordGT90Concept, 21 October 2016 - 12:15 AM.


#14 ebr OFFLINE  

ebr

    Chief Bottle Washer

  • Administrators
  • 50887 posts
  • Local time: 08:12 PM

Posted 21 October 2016 - 11:14 AM

Server discovery is done via UDP.  Make sure a firewall on the server isn't blocking that.

 

I'm not sure exactly what is going on but the logs clearly show time outs trying to contact your server the first few times.  


  • FordGT90Concept likes this

#15 FordGT90Concept OFFLINE  

FordGT90Concept

    Advanced Member

  • Members
  • 720 posts
  • Local time: 07:12 PM

Posted 21 October 2016 - 01:00 PM

It appears setup created two firewall rules: "Emby HTTP" and "Emby HTTPS" where both were configured for TCP only. Since I'm not using HTTPS (router should be blocking external access to Emby), I deleted that one, renamed "Emby HTTP" to "Emby TCP", copied that, renamed it to "Emby UDP" and made the appropriate changes.

I'm headed to bed now so I can't test if this change fixed it but I will soon.

#16 FordGT90Concept OFFLINE  

FordGT90Concept

    Advanced Member

  • Members
  • 720 posts
  • Local time: 07:12 PM

Posted 21 October 2016 - 08:49 PM

It's not fixed. The last time 214 was used was at 4:50 PM:
2016-10-21 16:50:44.7369 Info HttpServer: HTTP Response 204 to 192.168.0.214. Time: 234ms. http://192.168.0.128:8096/emby/Items/d5701dae90102d0b57015f72336cad63
At 7:00 PM, server started recording two programs:
2016-10-21 19:00:00.6797 Info App: Writing file to path: E:\Recordings\MacGyver\Season 1\MacGyver S01E05 Toothpick.ts
2016-10-21 19:00:00.9141 Info App: Writing file to path: E:\Recordings\Hell's Kitchen\Season 16\Hell's Kitchen S16E05 Walking the Plank.ts
Now here's me trying to test at 7:09 PM. When I turned the Leelbox on, it was sitting at some program info in Emby so I backed out and tried to get back in:
2016-10-21 19:09:00.2906 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/system/info/public?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-21 19:09:00.3375 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 47ms. http://192.168.0.128:8096/emby/system/info/public?format=json
2016-10-21 19:09:00.4156 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/system/info?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-21 19:09:00.4625 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 47ms. http://192.168.0.128:8096/emby/system/info?format=json
2016-10-21 19:09:00.5250 Info HttpServer: HTTP GET http://192.168.0.128:8096/mediabrowser/users/82677126f7ef44ea9c710f93b8d35385?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-21 19:09:00.5406 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 16ms. http://192.168.0.128:8096/mediabrowser/users/82677126f7ef44ea9c710f93b8d35385?format=json
2016-10-21 19:09:00.6661 Info HttpServer: HTTP POST http://192.168.0.128:8096/emby/Sessions/Capabilities/Full. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-21 19:09:00.6817 Info HttpServer: HTTP Response 204 to 192.168.0.214. Time: 16ms. http://192.168.0.128:8096/emby/Sessions/Capabilities/Full
2016-10-21 19:09:00.6973 Info HttpServer: WS ws://192.168.0.128:8096/emby/embywebsocket?api_key=5fd678faa9ad4621b2f0ddba7077a345&deviceId=f4143212e5cd946d. UserAgent: 
2016-10-21 19:09:01.7442 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/system/info/public?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-21 19:09:01.7754 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 31ms. http://192.168.0.128:8096/emby/system/info/public?format=json
2016-10-21 19:09:01.8067 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/system/info?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-21 19:09:01.8379 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 31ms. http://192.168.0.128:8096/emby/system/info?format=json
2016-10-21 19:09:01.8692 Info HttpServer: HTTP GET http://192.168.0.128:8096/mediabrowser/users/82677126f7ef44ea9c710f93b8d35385?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-21 19:09:01.8848 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 16ms. http://192.168.0.128:8096/mediabrowser/users/82677126f7ef44ea9c710f93b8d35385?format=json
2016-10-21 19:09:01.9786 Info HttpServer: HTTP POST http://192.168.0.128:8096/emby/Sessions/Capabilities/Full. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-21 19:09:01.9942 Info HttpServer: HTTP Response 204 to 192.168.0.214. Time: 16ms. http://192.168.0.128:8096/emby/Sessions/Capabilities/Full
2016-10-21 19:09:02.1036 Info HttpServer: HTTP GET http://192.168.0.128:8096/emby/Users/Public?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 6.0.1; Leelbox Build/MHC19J)
2016-10-21 19:09:02.1192 Info HttpServer: HTTP Response 200 to 192.168.0.214. Time: 16ms. http://192.168.0.128:8096/emby/Users/Public?format=json
I sent the logs at this time. It did not connect to the server the first attempt but it did the second.

The logs after this are related to the ongoing recordings, I believe:
2016-10-21 19:12:37.3774 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/description.xml. UserAgent: DAFUPnP
2016-10-21 19:12:37.4087 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/description.xml. UserAgent: DAFUPnP
2016-10-21 19:12:37.4087 Info Dlna: No matching device profile found. The default will need to be used.
	Cache-Control: no-cache
	Connection: Keep-Alive
	Pragma: no-cache
	Accept: text/xml, application/xml
	User-Agent: DAFUPnP
	Host: 192.168.0.128:8096
2016-10-21 19:12:37.4087 Info Dlna: No matching device profile found. The default will need to be used.
	Cache-Control: no-cache
	Connection: Keep-Alive
	Pragma: no-cache
	Accept: text/xml, application/xml
	User-Agent: DAFUPnP
	Host: 192.168.0.128:8096
2016-10-21 19:12:37.4399 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 63ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/description.xml
2016-10-21 19:12:37.4399 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 31ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/description.xml
2016-10-21 19:12:37.4555 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/description.xml. UserAgent: Microsoft-Windows/10.0 UPnP/1.0
2016-10-21 19:12:37.4555 Info Dlna: No matching device profile found. The default will need to be used.
	Cache-Control: no-cache
	Connection: Close
	Pragma: no-cache
	Accept: text/xml, application/xml
	User-Agent: Microsoft-Windows/10.0 UPnP/1.0
	Host: 192.168.0.128:8096
2016-10-21 19:12:37.4555 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 0ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/description.xml
2016-10-21 19:12:37.4555 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/description.xml. UserAgent: Microsoft-Windows/10.0 UPnP/1.0
2016-10-21 19:12:37.4555 Info Dlna: No matching device profile found. The default will need to be used.
	Cache-Control: no-cache
	Connection: Close
	Pragma: no-cache
	Accept: text/xml, application/xml
	User-Agent: Microsoft-Windows/10.0 UPnP/1.0
	Host: 192.168.0.128:8096
2016-10-21 19:12:37.4555 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 0ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/description.xml
2016-10-21 19:12:37.4712 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo240.png. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50
2016-10-21 19:12:37.4712 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo240.jpg. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50
2016-10-21 19:12:37.4712 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 0ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo240.png
2016-10-21 19:12:37.4712 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 0ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo240.jpg
2016-10-21 19:12:37.4868 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo120.png. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50
2016-10-21 19:12:37.4868 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 0ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo120.png
2016-10-21 19:12:37.4868 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo120.jpg. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50
2016-10-21 19:12:37.4868 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 0ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo120.jpg
2016-10-21 19:12:37.4868 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo120.png. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50
2016-10-21 19:12:37.4868 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 0ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo120.png
2016-10-21 19:12:37.5024 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo48.png. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50
2016-10-21 19:12:37.5024 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 0ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo48.png
2016-10-21 19:12:37.5024 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo48.jpg. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50
2016-10-21 19:12:37.5024 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 0ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo48.jpg
2016-10-21 19:12:37.5181 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/contentdirectory/contentdirectory.xml. UserAgent: Microsoft-Windows/10.0 UPnP/1.0
2016-10-21 19:12:37.5181 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/contentdirectory/contentdirectory.xml. UserAgent: Microsoft-Windows/10.0 UPnP/1.0
2016-10-21 19:12:37.5649 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 47ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/contentdirectory/contentdirectory.xml
2016-10-21 19:12:37.5649 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 47ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/contentdirectory/contentdirectory.xml
2016-10-21 19:31:54.1696 Info TaskManager: IntervalTrigger fired for task: Convert media
2016-10-21 19:31:54.1696 Info TaskManager: Queueing task SyncConvertScheduledTask
2016-10-21 19:31:54.1696 Info TaskManager: Executing Convert media
2016-10-21 19:31:54.1852 Info TaskManager: Convert media Completed after 0 minute(s) and 0 seconds
2016-10-21 19:31:54.1852 Info ServerManager: Sending web socket message ScheduledTaskEnded
2016-10-21 19:31:54.1852 Info TaskManager: ExecuteQueuedTasks
2016-10-21 19:32:07.7224 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/description.xml. UserAgent: DAFUPnP
2016-10-21 19:32:07.7224 Info Dlna: No matching device profile found. The default will need to be used.
	Cache-Control: no-cache
	Connection: Keep-Alive
	Pragma: no-cache
	Accept: text/xml, application/xml
	User-Agent: DAFUPnP
	Host: 192.168.0.128:8096
2016-10-21 19:32:07.7224 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 0ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/description.xml
2016-10-21 19:32:07.7224 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/description.xml. UserAgent: Microsoft-Windows/10.0 UPnP/1.0
2016-10-21 19:32:07.7224 Info Dlna: No matching device profile found. The default will need to be used.
	Cache-Control: no-cache
	Connection: Close
	Pragma: no-cache
	Accept: text/xml, application/xml
	User-Agent: Microsoft-Windows/10.0 UPnP/1.0
	Host: 192.168.0.128:8096
2016-10-21 19:32:07.7224 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 0ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/description.xml
2016-10-21 19:32:07.7224 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo240.png. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50
2016-10-21 19:32:07.7224 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 0ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo240.png
2016-10-21 19:32:07.7224 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo240.jpg. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50
2016-10-21 19:32:07.7224 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 0ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo240.jpg
2016-10-21 19:32:07.7380 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo120.png. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50
2016-10-21 19:32:07.7380 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 0ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo120.png
2016-10-21 19:32:07.7380 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo120.jpg. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50
2016-10-21 19:32:07.7380 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 0ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo120.jpg
2016-10-21 19:32:07.7380 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo48.png. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50
2016-10-21 19:32:07.7380 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 0ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo48.png
2016-10-21 19:32:07.7380 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo48.jpg. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50
2016-10-21 19:32:07.7380 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 0ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo48.jpg
2016-10-21 19:32:07.7536 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/contentdirectory/contentdirectory.xml. UserAgent: Microsoft-Windows/10.0 UPnP/1.0
2016-10-21 19:32:07.7536 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 0ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/contentdirectory/contentdirectory.xml
2016-10-21 19:32:07.8786 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/description.xml. UserAgent: DAFUPnP
2016-10-21 19:32:07.8786 Info Dlna: No matching device profile found. The default will need to be used.
	Cache-Control: no-cache
	Connection: Keep-Alive
	Pragma: no-cache
	Accept: text/xml, application/xml
	User-Agent: DAFUPnP
	Host: 192.168.0.128:8096
2016-10-21 19:32:07.8786 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 0ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/description.xml
2016-10-21 19:32:07.8786 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/description.xml. UserAgent: Microsoft-Windows/10.0 UPnP/1.0
2016-10-21 19:32:07.8786 Info Dlna: No matching device profile found. The default will need to be used.
	Cache-Control: no-cache
	Connection: Close
	Pragma: no-cache
	Accept: text/xml, application/xml
	User-Agent: Microsoft-Windows/10.0 UPnP/1.0
	Host: 192.168.0.128:8096
2016-10-21 19:32:07.8786 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 0ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/description.xml
2016-10-21 19:32:07.8786 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo240.png. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50
2016-10-21 19:32:07.8786 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 0ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo240.png
2016-10-21 19:32:07.8786 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo240.jpg. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50
2016-10-21 19:32:07.8786 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 0ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo240.jpg
2016-10-21 19:32:07.8942 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo120.png. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50
2016-10-21 19:32:07.8942 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 0ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo120.png
2016-10-21 19:32:07.8942 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo120.jpg. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50
2016-10-21 19:32:07.8942 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 0ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo120.jpg
2016-10-21 19:32:07.8942 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo48.png. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50
2016-10-21 19:32:07.8942 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 0ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo48.png
2016-10-21 19:32:07.8942 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo48.jpg. UserAgent: User-Agent: Microsoft-DLNA DLNADOC/1.50
2016-10-21 19:32:07.8942 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 0ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/icons/logo48.jpg
2016-10-21 19:32:07.8942 Info HttpServer: HTTP GET http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/contentdirectory/contentdirectory.xml. UserAgent: Microsoft-Windows/10.0 UPnP/1.0
2016-10-21 19:32:07.8942 Info HttpServer: HTTP Response 200 to 192.168.0.44. Time: 0ms. http://192.168.0.128:8096/dlna/4d38467527df3ecb957ef5f56c0940eb/contentdirectory/contentdirectory.xml
2016-10-21 19:32:13.1306 Error HttpServer: Error in SharpWebSocket: An exception has occurred while receiving a message.. Exception.Message: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

Edited by FordGT90Concept, 21 October 2016 - 08:50 PM.


#17 FordGT90Concept OFFLINE  

FordGT90Concept

    Advanced Member

  • Members
  • 720 posts
  • Local time: 07:12 PM

Posted 23 December 2016 - 05:06 PM   Best Answer

This appears to be fixed in Emby Server 3.1 and Android TV 1.3



#18 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 153382 posts
  • Local time: 08:12 PM

Posted 23 December 2016 - 05:08 PM

Thanks for reporting back !







Also tagged with one or more of these keywords: unresponsive, android tv

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users