Movies don't resume, they start from beginning

[Nabukodonosor 16]

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

[JelloLabs 11]

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 1614]

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

-map_metadata -1
-map_chapters 0

[visproduction 361]

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 16]

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 361]

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 16]

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 1614]

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 1614]

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

[sa2000 775]

@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 16]

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

 

[sa2000 775]

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 16]

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 775]

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 16]

Just checked it, 2.1.46g version.