Jump to content

ATV app not fully loading


Recommended Posts

xXSagaiaXx
Posted

It seems whenever I don't use the app for an extended period of time, 3+ hours the app will load to the home screen and show nothing but emby, the time and the search. The only way to get to fully loaded is to clear the cache and force stop the app several times. I'm using on shield tv and I have the same issues on several units.

 

Sent from my SM-N920T using Tapatalk

xXSagaiaXx
Posted (edited)

I'm not sure what you are trying to say when you are posting a link. It would be helpful to say what I am missing in my above statement. If it's pics, well when this happens it's usually right when I wake up for work at 6 in the am and the first thing on my mind is not to take a pic of the issue. If it's a log you need then I'll try and provide but it'd be nice to know that's what you wanted!

 

Sent from my SM-N920T using Tapatalk

Edited by xXSagaiaXx
Posted

By home screen do you mean the device home or emby app home?

xXSagaiaXx
Posted

It's the emby app home screen. Here's a pic

81b8a523ee74318bd1e5bd7d8822521a.jpg

 

Sent from my SM-N920T using Tapatalk

xXSagaiaXx
Posted

Here's the log:

 

Like I said. I have to clear the cache and force stop the app multiple times in order for it to work again. I have this issue across several shield tv devices.

server-63588615375.zip

Posted

Never seen that before. Does your server go to sleep during that time perhaps?

Posted

Never seen that before. Does your server go to sleep during that time perhaps?

I have quite often.

 

It can sometimes takes 3 or 4 times of exiting and restarting the app to get it to load correctly.

 

I also get partial loads, whereby the library row is populated, but either the Next Up or Latest Movies is blank.

 

I see this mainly on my Fire TV, but that's probably because I use the app more on it than my Nexus Player.

 

I tried narrowing it down to something running in the Emby server, or something else running on the same PC as Emby server, but I've never been able to pin it down, although if Emby server has just restarted, it can take a while for it to sort itself out.

 

The Fire TV does sleep and when I wake it, the first thing I normally do, is start the Emby app and it's mainly at this point that I see the non-loading of content.

 

If it persists, then I tend to reboot the Fire TV itself.

 

In the server log above there are lots of subtitle download errors, so it could just be that the server was under load and couldn't respond to the requests from the app.

 

Perhaps change some of the scheduled tasks to run overnight so there's no impact during the day.

 

My Fire TV and Nexus Player are both connected to my network via Gigabit ethernet.

Posted

I have quite often.

 

Are you positive it is that exact screen?  Notice his doesn't even have a "Settings" row.

 

What you describe, I'm pretty sure is a different issue related to changes that are in process on the server.

Posted

I get the blank screen as per his image.

 

I don't leave the app open that long without using it.

Posted

I get the blank screen as per his image.

 

I don't leave the app open that long without using it.

 

Do you ever, at any point in time see anything on the screen?  I mean, do you see the rows at first and then they disappear or do you just get this blank screen and it stays that way?

Posted

When it happens, I get nothing displayed other than what's in the image above.

 

Next time it happens, I'll grab screenshots and the server log.

Posted

I've found it in his log.

 

There are a number of things going on but, ultimately, the issue is the server is just completely inundated and cannot respond to the request by the app.

 

1) As CBers noted, the subtitle download task is wreaking total havoc.  It is hitting its rate limit and then just keeps on going completely spamming the log and also probably bogging down the server with requests that all fail.  We need to make that thing quit when it hits the limit.

 

2) Something (presumably the server dashboard) is polling the activity log every second.  The problem is, each one of these requests is taking between 5 and 15 seconds to respond - probably building up an incredible thread backlog for those requests.

 

3) Finally, with all of this happening at the same time, you attempt to bring up the Fire TV app and the server is so inundated with activity that it simply cannot respond.  Look at the response times for these queries - they are between a minute and a half and 4+ minutes.

2016-01-17 21:53:25.9021 Info HttpServer: HTTP Response 200 to ::ffff:192.168.1.81. Time: 150364ms (slow). http://192.168.1.245:8096/emby/Users/5dd6b59487d547c4870a276688503c50/Views?format=json
2016-01-17 21:53:25.9156 Info HttpServer: HTTP Response 200 to ::ffff:192.168.1.81. Time: 150368ms (slow). http://192.168.1.245:8096/emby/Shows/NextUp?EnableImageTypes=&Limit=3&UserId=5dd6b59487d547c4870a276688503c50&Fields=PrimaryImageAspectRatio&format=json
2016-01-17 21:53:25.9156 Info HttpServer: HTTP Response 200 to ::ffff:192.168.1.81. Time: 72550ms (slow). http://192.168.1.245:8096/emby/Users/5dd6b59487d547c4870a276688503c50/Views?format=json
2016-01-17 21:53:25.9621 Info HttpServer: HTTP Response 200 to ::ffff:192.168.1.81. Time: 150412ms (slow). http://192.168.1.245:8096/emby/Users/5dd6b59487d547c4870a276688503c50/Items?Years=&EnableImageTypes=&ArtistIds=&Filters=IsResumable&Fields=PrimaryImageAspectRatio%2COverview%2CItemCounts%2CDisplayPreferencesId&Genres=&MediaTypes=&Ids=&PersonTypes=&recursive=true&ExcludeLocationTypes=&ExcludeItemTypes=&AirDays=&sortOrder=Descending&Limit=2&SortBy=DatePlayed&StudioIds=&PersonIds=&ImageTypes=&IncludeItemTypes=Movie&VideoTypes=&LocationTypes=&SeriesStatuses=&format=json
2016-01-17 21:53:25.9621 Info HttpServer: HTTP Response 200 to ::ffff:192.168.1.81. Time: 83886ms (slow). http://192.168.1.245:8096/emby/Users/5dd6b59487d547c4870a276688503c50/Views?format=json
2016-01-17 21:53:25.9621 Info HttpServer: HTTP Response 200 to ::ffff:192.168.1.81. Time: 132595ms (slow). http://192.168.1.245:8096/emby/Shows/NextUp?EnableImageTypes=&Limit=3&UserId=5dd6b59487d547c4870a276688503c50&Fields=PrimaryImageAspectRatio&format=json
2016-01-17 21:53:25.9621 Info HttpServer: HTTP Response 200 to ::ffff:192.168.1.81. Time: 102594ms (slow). http://192.168.1.245:8096/emby/Shows/NextUp?EnableImageTypes=&Limit=3&UserId=5dd6b59487d547c4870a276688503c50&Fields=PrimaryImageAspectRatio&format=json
2016-01-17 21:53:25.9621 Info HttpServer: HTTP Response 200 to ::ffff:192.168.1.81. Time: 102606ms (slow). http://192.168.1.245:8096/emby/Users/5dd6b59487d547c4870a276688503c50/Views?format=json
2016-01-17 21:53:25.9621 Info HttpServer: HTTP Response 200 to ::ffff:192.168.1.81. Time: 113890ms (slow). http://192.168.1.245:8096/emby/Shows/NextUp?EnableImageTypes=&Limit=3&UserId=5dd6b59487d547c4870a276688503c50&Fields=PrimaryImageAspectRatio&format=json
2016-01-17 21:53:26.8807 Info HttpServer: HTTP Response 200 to ::ffff:192.168.1.81. Time: 114796ms (slow). http://192.168.1.245:8096/emby/Users/5dd6b59487d547c4870a276688503c50/Items?Years=&EnableImageTypes=&ArtistIds=&Filters=IsResumable&Fields=PrimaryImageAspectRatio%2COverview%2CItemCounts%2CDisplayPreferencesId&Genres=&MediaTypes=&Ids=&PersonTypes=&recursive=true&ExcludeLocationTypes=&ExcludeItemTypes=&AirDays=&sortOrder=Descending&Limit=2&SortBy=DatePlayed&StudioIds=&PersonIds=&ImageTypes=&IncludeItemTypes=Movie&VideoTypes=&LocationTypes=&SeriesStatuses=&format=json
2016-01-17 21:53:27.0097 Info HttpServer: HTTP Response 200 to ::ffff:192.168.1.81. Time: 133630ms (slow). http://192.168.1.245:8096/emby/Users/5dd6b59487d547c4870a276688503c50/Items?Years=&EnableImageTypes=&ArtistIds=&Filters=IsResumable&Fields=PrimaryImageAspectRatio%2COverview%2CItemCounts%2CDisplayPreferencesId&Genres=&MediaTypes=&Ids=&PersonTypes=&recursive=true&ExcludeLocationTypes=&ExcludeItemTypes=&AirDays=&sortOrder=Descending&Limit=2&SortBy=DatePlayed&StudioIds=&PersonIds=&ImageTypes=&IncludeItemTypes=Movie&VideoTypes=&LocationTypes=&SeriesStatuses=&format=json
2016-01-17 21:53:27.0097 Info HttpServer: HTTP Response 200 to ::ffff:192.168.1.81. Time: 114934ms (slow). http://192.168.1.245:8096/emby/Users/5dd6b59487d547c4870a276688503c50/Views?format=json
2016-01-17 21:53:27.0287 Info HttpServer: HTTP Response 200 to ::ffff:192.168.1.81. Time: 133662ms (slow). http://192.168.1.245:8096/emby/Users/5dd6b59487d547c4870a276688503c50/Views?format=json
2016-01-17 21:53:27.0522 Info HttpServer: HTTP Response 200 to ::ffff:192.168.1.81. Time: 189319ms (slow). http://192.168.1.245:8096/emby/LiveTv/Programs/Recommended?IsAiring=true&Limit=20&UserId=5dd6b59487d547c4870a276688503c50&Fields=Overview%2CPrimaryImageAspectRatio%2CChannelInfo&format=json
2016-01-17 21:53:27.1078 Info HttpServer: HTTP Response 200 to ::ffff:192.168.1.81. Time: 249412ms (slow). http://192.168.1.245:8096/emby/LiveTv/Programs/Recommended?IsAiring=true&Limit=20&UserId=5dd6b59487d547c4870a276688503c50&Fields=Overview%2CPrimaryImageAspectRatio%2CChannelInfo&format=json
2016-01-17 21:53:27.1078 Info HttpServer: HTTP Response 200 to ::ffff:192.168.1.81. Time: 189377ms (slow). http://192.168.1.245:8096/emby/LiveTv/Programs/Recommended?IsAiring=true&Limit=20&UserId=5dd6b59487d547c4870a276688503c50&Fields=Overview%2CPrimaryImageAspectRatio%2CChannelInfo&format=json
2016-01-17 21:53:27.1078 Info HttpServer: HTTP Response 200 to ::ffff:192.168.1.81. Time: 219410ms (slow). http://192.168.1.245:8096/emby/LiveTv/Programs/Recommended?IsAiring=true&Limit=20&UserId=5dd6b59487d547c4870a276688503c50&Fields=Overview%2CPrimaryImageAspectRatio%2CChannelInfo&format=json
2016-01-17 21:53:27.1393 Info HttpServer: HTTP Response 200 to ::ffff:192.168.1.81. Time: 219451ms (slow). http://192.168.1.245:8096/emby/Users/5dd6b59487d547c4870a276688503c50/Items?Years=&EnableImageTypes=&ArtistIds=&Filters=IsResumable&Fields=PrimaryImageAspectRatio%2COverview%2CItemCounts%2CDisplayPreferencesId&Genres=&MediaTypes=&Ids=&PersonTypes=&recursive=true&ExcludeLocationTypes=&ExcludeItemTypes=&AirDays=&sortOrder=Descending&Limit=50&SortBy=DatePlayed&StudioIds=&PersonIds=&ImageTypes=&IncludeItemTypes=Movie%2CEpisode%2CVideo%2CProgram&VideoTypes=&LocationTypes=&SeriesStatuses=&format=json
2016-01-17 21:53:27.1518 Info HttpServer: HTTP Response 200 to ::ffff:192.168.1.81. Time: 249463ms (slow). http://192.168.1.245:8096/emby/Users/5dd6b59487d547c4870a276688503c50/Items?Years=&EnableImageTypes=&ArtistIds=&Filters=IsResumable&Fields=PrimaryImageAspectRatio%2COverview%2CItemCounts%2CDisplayPreferencesId&Genres=&MediaTypes=&Ids=&PersonTypes=&recursive=true&ExcludeLocationTypes=&ExcludeItemTypes=&AirDays=&sortOrder=Descending&Limit=50&SortBy=DatePlayed&StudioIds=&PersonIds=&ImageTypes=&IncludeItemTypes=Movie%2CEpisode%2CVideo%2CProgram&VideoTypes=&LocationTypes=&SeriesStatuses=&format=json
2016-01-17 21:53:27.2093 Info HttpServer: HTTP Response 200 to ::ffff:192.168.1.81. Time: 189522ms (slow). http://192.168.1.245:8096/emby/LiveTv/Recordings?EnableImages=true&Limit=40&UserId=5dd6b59487d547c4870a276688503c50&Id=5dd6b59487d547c4870a276688503c50&Fields=Overview%2CPrimaryImageAspectRatio&format=json
2016-01-17 21:53:27.2522 Info HttpServer: HTTP Response 200 to ::ffff:192.168.1.81. Time: 249561ms (slow). http://192.168.1.245:8096/emby/Users/5dd6b59487d547c4870a276688503c50/Items?Years=&EnableImageTypes=&ArtistIds=&Filters=IsUnplayed&Fields=PrimaryImageAspectRatio%2COverview%2CItemCounts%2CDisplayPreferencesId&Genres=&MediaTypes=&Ids=&PersonTypes=&recursive=true&ExcludeLocationTypes=&ExcludeItemTypes=&AirDays=&sortOrder=Descending&Limit=50&SortBy=DateCreated&StudioIds=&PersonIds=&ImageTypes=&IncludeItemTypes=Movie&VideoTypes=&LocationTypes=&SeriesStatuses=&format=json
2016-01-17 21:53:27.2522 Info HttpServer: HTTP Response 200 to ::ffff:192.168.1.81. Time: 219563ms (slow). http://192.168.1.245:8096/emby/Users/5dd6b59487d547c4870a276688503c50/Items?Years=&EnableImageTypes=&ArtistIds=&Filters=IsUnplayed&Fields=PrimaryImageAspectRatio%2COverview%2CItemCounts%2CDisplayPreferencesId&Genres=&MediaTypes=&Ids=&PersonTypes=&recursive=true&ExcludeLocationTypes=&ExcludeItemTypes=&AirDays=&sortOrder=Descending&Limit=50&SortBy=DateCreated&StudioIds=&PersonIds=&ImageTypes=&IncludeItemTypes=Movie&VideoTypes=&LocationTypes=&SeriesStatuses=&format=json

You have given up waiting and are trying to force-close the app or clear its cache/data by the time these queries actually respond.

 

The first thing I'd do is turn off the subtitle downloader until we get that under control and see if that makes a difference.

Posted

Those "(slow)" messages are worse than the ones I previously posted about!

 

Definitely seems to be the server causing the issues with the client. I sometimes get similar issues when using the Emby for Samsung Smart TV app.

xXSagaiaXx
Posted

Okay, it seems like the subtitle download is what was bogging down the server. I turned it off cause it's not working right anyway (I dont have my movies and shows the same as opensubtitles). I have also changed all the scheduled tasks to do there thing at night when no one would be using emby. I'll try this and let you know but I think will fix the issue.

 

Thanks for checking.

rfischer1984
Posted (edited)

mine on my aftv will be blank when i open it after not using it for a while. I have to force close every time to have it open up. Which is annoying. Especially when my wife only knows how to find the app and play it. Not go to the application and force close it. So if im not a around she gets frustrated with it. lol

Edited by rfischer1984
Posted

mine on my aftv will be blank when i open it after not using it for a while. I have to force close every time to have it open up. Which is annoying. Especially when my wife only knows how to find the app and play it. Not go to the application and force close it. So if im not a around she gets frustrated with it. lol

 

Have you looked at your server log at that time?  Probably the same problem - the server taking a very long time to respond.

rfischer1984
Posted

Have you looked at your server log at that time?  Probably the same problem - the server taking a very long time to respond.

Well I have had 2 separate servers and both had this problem. My server is a docker image running on unraid. I wonder if that would could be causing the issue with it? 

rfischer1984
Posted

Ill need to go home and try to open it again and see what i get on the server end. I looked at my logs and didnt see any slow response times. I only see slow times when it is being accessed remotely. But I will look when i get home. 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...