Movies don't resume, they start from beginning

[Nabukodonosor 17]

It's the same. Did you change anything? I mean, what was it that you expected to happen?

[JelloLabs 12]

Add me to the list.
I have the same issue on 3.5.36 android shield tv client , resume causes to play from beginning even if show is half way in, it's random. I can't reproduce now ofc, but will get a recording next time i resume something, not just one show or 1 movie, been going on for months. 

[yocker 1683]

Try and install the diagnostic plugin from the catalog and add this:

-map_metadata -1
-map_chapters 0

[visproduction 362]

What if the drive where the media is located has some issue?  Older drives can do that.  If you move the media to another drive, does it still fail to continue play?  Another question is what if the media has some metadata timeline corruption issue and only fails at some point in the timeline.  

The argument that since media starts to play fine or tests fine on other players doesn't rule out that there might be some other timeline metadata corruption.  Just skipping testing the media properly because it seems to play fine at the start or with another player is not a valid test that the media is fine.  The media can still be bad and act this way.  That's like saying. it can't be the motor when the car stalls on the freeway, because it starts up fine. Did anyone actually check the media?

[Nabukodonosor 17]

Well, the logic tells me that nothing you said can't be true. For instance, I have regular Emby for android and this NEVER happens. Also, it would be very unusual if now all of the sudden all new media I download is corrupted.

[visproduction 362]

OK, You used a double negative in your answer.  "Nothing you said can't be true".  That doesn't actually make sense.  I assume you disagree with my previous post. 

Did you test the exact same media copy in your android player and did that work?  If that is true, than it could be a Fire TV app related problem. That answer would be helpful to try to pinpoint what is going on.  It's nice to get exact step by step list, the cable or Wifi connections the TV model, the Fire TV hardware model and Emby App version.  It's important to duplicate the issue to know how to fix it. 

Edited June 1 by visproduction

[Nabukodonosor 17]

22 hours ago, yocker said:

Try and install the diagnostic plugin from the catalog and add this:

-map_metadata -1
-map_chapters 0

Tried it, didn't work.

[yocker 1683]

4 hours ago, Nabukodonosor said:

Tried it, didn't work.

Damn, it works to solve a similar problem with chromecast so hoped it would work here.

[yocker 1683]

Looking at the log you uploaded.
Question: are you using wifi when connecting to the server ?

[sa2000 784]

@Nabukodonosor If this is still happening, I would suggest updating to tha latest Android TV App beta which is 2.1.46 at this moment and the amazon app download zipped file is here: Emby Android TV Release Notes (BETA) and with some controlled tests noting down exact times and with matching set of Emby Server logs and App uploaded logs, we can try and isolate the issue as being server or app issue

The test and captured diagnostics would need to cover the time when the movie is played first and reaching a specific offset when stopped and then the time when the movie is resumed from xx:xx:xx but actually starts from 00:00

So run the Emby for Anroid TV amazon app with this enabled "Enable debug options" in App Settings / General Display settings

and there is no harm in also having the emby server debug logging enabled for this controlled test 

The remote controller for the Amzon Fire TV has precise clicks and selection for the buttons - so if Resume from xx:xx was selected and goes green and clicks then it ought to be what is selected and actioned when the center button is pressed

If you note down the times then we can see what gets reported in the emby server log by the android TV app when playback is stopped at initial playback before the resume that goes wrong

And as before give the details of when you do the "Send Logs" within the Android TV app

and attach here the downloaded embyserver logs covering the times of stopping the playback and later when the resume goes wrong - and please indicate the times when these are done

Thanks

 

 

 

[Nabukodonosor 17]

Already did that. You can check my logs on page 1.

 

[sa2000 784]

25 minutes ago, Nabukodonosor said:

You can check my logs on page 1.

I have and that is why I said what I said - anyway - the tests i am asking for is not just upgrading - it is a controlled test covering both the stopping of the playback and the resume later which goes wrong

I only found one log from you and it shows a Fire TV running AndroidTv 2.1.30a and not 2.1.46. As i said what I was suggesting was a controlled test getting matching sets of logs from the android TV app and server with debug logging and noting down times of the specific actions

 

[Nabukodonosor 17]

I will try. But I couldn't install that beta version. Tried both versions, google and amazon, and failed. I will try again. But I think 2.1.46 is on my stick at the moment, I think that's the latest from Amazon App Store. Is that good enough?

Edited June 1 by Nabukodonosor

[sa2000 784]

12 hours ago, Nabukodonosor said:

But I think 2.1.46 is on my stick at the moment, I think that's the latest from Amazon App Store. Is that good enough?

yes - 2.1.46 is what is showing as the latest beta in this release note post Emby Android TV Release Notes Beta

[Nabukodonosor 17]

Just checked it, 2.1.46g version.

[Nabukodonosor 17]

So you guys really can't fix this? It's annoying AF!

[sa2000 784]

@NabukodonosorIf you have a reasonable size movie that this happens on, i could send you an upload link and we will see if we can reprodudce the issue on an Amazon Fire TV - by reasonable size I mean 3Gb or under. The issue may be as suggested by @speechlesearlier in this thread in this post

Your screen capture video that you posted here confirms that the resume offset for the user account was passed on to the emby app by the server

A couple of statements you made are some clues which we need to keep in mind

1. In this post you stated 

Quote

I just exit my media, and tomorrow I can't resume.

is it always the next day or after ?

2. And in this post you mentioned

Quote

If it's the first time I'm resuming a movie, it will happen, but every time after that it will not.

So the first time after a period of time, the app is failing to respect the resume offset or loses it in its handover to the video player.

Edited 7 hours ago by sa2000

[Nabukodonosor 17]

Quote

is it always the next day or after ?

Yeah, I've noticed that the more time passed the greater are the chances it will happen. But I will test it out to see if it happens after a few minutes or something.

Quote

If it's the first time I'm resuming a movie, it will happen, but every time after that it will not.

I'm not sure about this anymore. I will test this too.

Edited 36 minutes ago by sa2000

[JelloLabs 12]

I noticed if i go back into emby after long time (after player went to sleep, powered down...), and let's say an episode played 50%, if i'm too fast it happens, BUT if i let the theme.mp3 play first then it resumed fine ? not sure if it helps..

[sa2000 784]

45 minutes ago, JelloLabs said:

If i'm too fast it happens, BUT if i let the theme.mp3 play first then it resumed fine ? not sure if it helps..

Is this Android on Amazon Fire TV ?

Suggests we have a timing issue or some actions happen too early before all data/parameters settle down

 

[JelloLabs 12]

Just now, sa2000 said:

Is this Android on Amazon Fire TV ?

Suggests we have a timing issue or some actions happen too early before all data/parameters settle down

 

Emby for Android, even 3.5.37 on shield pro 

[sa2000 784]

Just now, JelloLabs said:

Emby for Android, even 3.5.37 on shield pro

Interesting - because the issue was not seen by @Nabukodonosorusing the universal Emby for Android app

[Nabukodonosor 17]

No, in the Android app this has NEVER happened.