Fire TV - Session doesn't stop when shutting down

[MrPancake 10]

Hello,

I'm sorry if this has been reported before:

I have a Fire Stick 4K Max (latest version) and I use the Emby app (not the emby for fire stick).

Whenever somebody is watching, and presses the power button on the fire stick remote, the session is never "stopped" on Emby. It hangs until the fire stick is turned on again.

It annoys me because on the dashboard it always shows an active session because of this.

Restarting the server doesn't fix it.

Emby server is running on Version 4.9.0.33 beta

 

Thank you!

[ebr 16169]

3 hours ago, MrPancake said:

Restarting the server doesn't fix it.

Hi.  That would indicate that the device is actually still alive and requesting data.

The session really comes back when you restart the server?

[MrPancake 10]

46 minutes ago, ebr said:

Hi.  That would indicate that the device is actually still alive and requesting data.

The session really comes back when you restart the server?

Yes, it never leaves. 

The device is probably in a sleep mode because when turning on again it continues playing from the same spot, but a timeout would be nice? 

[MrPancake 10]

The logs has lots of these, about every 5 seconds:

2024-12-16 13:43:12.192 Info Server: http/1.1 Response 204 to host1. Time: 2ms. POST http://192.168.1.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Android&X-Emby-Device-Name=J's Fire TV&X-Emby-Device-Id=cbea422a28c2560b&X-Emby-Client-Version=3.4.16&X-Emby-Token=x_secret1_x&X-Emby-Language=en-gb&reqformat=json
2024-12-16 13:43:17.217 Info Server: http/1.1 POST http://192.168.1.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Android&X-Emby-Device-Name=J's Fire TV&X-Emby-Device-Id=cbea422a28c2560b&X-Emby-Client-Version=3.4.16&X-Emby-Token=x_secret1_x&X-Emby-Language=en-gb&reqformat=json. Source Ip: host1, UserAgent: Mozilla/5.0 (Linux; Android 11; AFTKRT Build/RS8125.2586N; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/126.0.6478.186 Mobile Safari/537.36
2024-12-16 13:43:17.218 Info Server: http/1.1 Response 204 to host1. Time: 2ms. POST http://192.168.1.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Android&X-Emby-Device-Name=J's Fire TV&X-Emby-Device-Id=cbea422a28c2560b&X-Emby-Client-Version=3.4.16&X-Emby-Token=x_secret1_x&X-Emby-Language=en-gb&reqformat=json
2024-12-16 13:43:22.248 Info Server: http/1.1 POST http://192.168.1.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Android&X-Emby-Device-Name=J's Fire TV&X-Emby-Device-Id=cbea422a28c2560b&X-Emby-Client-Version=3.4.16&X-Emby-Token=x_secret1_x&X-Emby-Language=en-gb&reqformat=json. Source Ip: host1, UserAgent: Mozilla/5.0 (Linux; Android 11; AFTKRT Build/RS8125.2586N; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/126.0.6478.186 Mobile Safari/537.36
2024-12-16 13:43:22.250 Info Server: http/1.1 Response 204 to host1. Time: 2ms. POST http://192.168.1.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Android&X-Emby-Device-Name=J's Fire TV&X-Emby-Device-Id=cbea422a28c2560b&X-Emby-Client-Version=3.4.16&X-Emby-Token=x_secret1_x&X-Emby-Language=en-gb&reqformat=json
2024-12-16 13:43:27.243 Info Server: http/1.1 POST http://192.168.1.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Android&X-Emby-Device-Name=J's Fire TV&X-Emby-Device-Id=cbea422a28c2560b&X-Emby-Client-Version=3.4.16&X-Emby-Token=x_secret1_x&X-Emby-Language=en-gb&reqformat=json. Source Ip: host1, UserAgent: Mozilla/5.0 (Linux; Android 11; AFTKRT Build/RS8125.2586N; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/126.0.6478.186 Mobile Safari/537.36
2024-12-16 13:43:27.322 Info Server: http/1.1 Response 204 to host1. Time: 79ms. POST http://192.168.1.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Android&X-Emby-Device-Name=J's Fire TV&X-Emby-Device-Id=cbea422a28c2560b&X-Emby-Client-Version=3.4.16&X-Emby-Token=x_secret1_x&X-Emby-Language=en-gb&reqformat=json
2024-12-16 13:43:32.286 Info Server: http/1.1 POST http://192.168.1.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Android&X-Emby-Device-Name=J's Fire TV&X-Emby-Device-Id=cbea422a28c2560b&X-Emby-Client-Version=3.4.16&X-Emby-Token=x_secret1_x&X-Emby-Language=en-gb&reqformat=json. Source Ip: host1, UserAgent: Mozilla/5.0 (Linux; Android 11; AFTKRT Build/RS8125.2586N; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/126.0.6478.186 Mobile Safari/537.36
2024-12-16 13:43:32.287 Info Server: http/1.1 Response 204 to host1. Time: 2ms. POST http://192.168.1.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Android&X-Emby-Device-Name=J's Fire TV&X-Emby-Device-Id=cbea422a28c2560b&X-Emby-Client-Version=3.4.16&X-Emby-Token=x_secret1_x&X-Emby-Language=en-gb&reqformat=json
2024-12-16 13:43:37.280 Info Server: http/1.1 POST http://192.168.1.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Android&X-Emby-Device-Name=J's Fire TV&X-Emby-Device-Id=cbea422a28c2560b&X-Emby-Client-Version=3.4.16&X-Emby-Token=x_secret1_x&X-Emby-Language=en-gb&reqformat=json. Source Ip: host1, UserAgent: Mozilla/5.0 (Linux; Android 11; AFTKRT Build/RS8125.2586N; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/126.0.6478.186 Mobile Safari/537.36
2024-12-16 13:43:37.281 Info Server: http/1.1 Response 204 to host1. Time: 2ms. POST http://192.168.1.100:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Android&X-Emby-Device-Name=J's Fire TV&X-Emby-Device-Id=cbea422a28c2560b&X-Emby-Client-Version=3.4.16&X-Emby-Token=x_secret1_x&X-Emby-Language=en-gb&reqformat=json

 

Edited December 16, 2024 by MrPancake

[ebr 16169]

Right so that would indicate that the device is not sleeping because those messages could not be sent if it were.  I suspect they are just turning off the display and not the device.

[MrPancake 10]

5 hours ago, ebr said:

Right so that would indicate that the device is not sleeping because those messages could not be sent if it were.  I suspect they are just turning off the display and not the device.

Sure looks like it, anything you can do in the Emby app to address it?

[Jdiesel 1431]

I see this occasionally with one of my users. I suspect they turn off the display and Next Up playback continues in the background. Does Android have the ability to detect the display state? If it does I think display off or not present should pause the playback. The default pause timeout would then kill the stream after enough time has passed.

Edited December 17, 2024 by Jdiesel

[Jdiesel 1431]

Seems like this is already and Amazon App requirement.

https://developer.amazon.com/docs/fire-tv/handling-hdmi-events.html#hdmi-state-changes

[MrPancake 10]

Even if you press home on the fire TV remote and go to their main dashboard, it still shows as playing until you open emby and press back. 

[ebr 16169]

On 12/17/2024 at 10:40 PM, Jdiesel said:

Does Android have the ability to detect the display state?

You should be able to setup CEC so that the device sleeps when the display is turned off.

[Luke 42077]

9 hours ago, MrPancake said:

Even if you press home on the fire TV remote and go to their main dashboard, it still shows as playing until you open emby and press back. 

But when you do this, the server should realize within a few minutes that the app is no longer talking to it.

[MrPancake 10]

On 19/12/2024 at 03:32, Luke said:

But when you do this, the server should realize within a few minutes that the app is no longer talking to it.

Hi, just wanted to ask if it might be in your list for bug fixes? 

 

Thank you

[Jdiesel 1431]

This is still an ongoing issue for me. I was hoping that the update to 2.1.23a might enable remote playback controls but maybe they just don't work at all on Amazon devices? I can stop playback remotely on Android devices just fine.

 

There is no way to kill these run away playback streams, even when taking my server office for 5 minutes they will continue back up immediately as soon as the server comes back online. There needs to be something on the client end that recognizes the display is off and pauses playback.

[ebr 16169]

30 minutes ago, Jdiesel said:

There needs to be something on the client end that recognizes the display is off and pauses playback

We've actually had the opposite request as there are people who want to play things in the background with the display off.

This issue really should be easily solvable by configuring your Fire device to go to sleep when the display is turned off.  If the device sleeps, our app will stop the stream. 

[MrPancake 10]

1 hour ago, ebr said:

We've actually had the opposite request as there are people who want to play things in the background with the display off.

This issue really should be easily solvable by configuring your Fire device to go to sleep when the display is turned off.  If the device sleeps, our app will stop the stream. 

That's what you might think, but actually when you press the off button on the fire TV remote, thats when you expect it to stop the stream. I actually think it pauses even. 

Note that I'm.not pressing off on the TV, I'm shutting down using the fire TV remote itself. 

[Jdiesel 1431]

The power button on the FireTV remote turns off the TV and not the FireTV itself. This is by design as Amazon wants the device to "always on" and ready. Maybe for immediate access or maybe for Alexa features...I'm not sure. This is why they have "Requirement 7.1" is their Requirements for Multimedia Apps documentation. Try powering off the TV while Prime or Netflix is playing and you will see that playback stops, not with Emby though. This is confusing to users who use multiple apps because Emby does not follow the expected behavior on the platform.

Whereas on my Shield TV turning off the TV will put the device to sleep.

[MrPancake 10]

36 minutes ago, Jdiesel said:

The power button on the FireTV remote turns off the TV and not the FireTV itself. This is by design as Amazon wants the device to "always on" and ready. Maybe for immediate access or maybe for Alexa features...I'm not sure. This is why they have "Requirement 7.1" is their Requirements for Multimedia Apps documentation. Try powering off the TV while Prime or Netflix is playing and you will see that playback stops, not with Emby though. This is confusing to users who use multiple apps because Emby does not follow the expected behavior on the platform.

Whereas on my Shield TV turning off the TV will put the device to sleep.

Makes sense, I wish emby was just like your shield TV. 

[ebr 16169]

21 hours ago, MrPancake said:

I wish emby was just like your shield TV

It is the exact same app on both devices.  It is the devices that are behaving differently.

[MrPancake 10]

3 hours ago, ebr said:

It is the exact same app on both devices.  It is the devices that are behaving differently.

I understand, but shouldn't there be something in the app to address it?

Today I tested instead of shutting down the fire stick with the power button, I selected its "sleep mode" - what it did was it put the stick to sleep, and the TV stayed on, and showed no signal for that input.

However, on Emby Server, the session was still there - and just like before, it shows as playing, but the timestamp never moves.

I'm sorry but based on what Jdiesel said above, it should even be a requirement of the app according to those guidelines?

[ebr 16169]

6 hours ago, MrPancake said:

However, on Emby Server, the session was still there

It may remain for at least 60 seconds - until the server realizes the app has gone away.