Playback stopping after 30 minutes on Android TV. Emby restart needed

[ArthurAttout 1]

This problem started showing up about on 19/11. Have been using the app on Android TV with no issue for close to a year (premium subscription enabled).

Managed to get an exact timestamp of when the playback issue shows up.

At around 2023-11-24 21:38, the playback on Android TV (v2.0.98g) stopped, after roughly 30 minutes of smooth playback.

ffmpeg suddenly stops, with no additional info I can make sense out of.

ffmpeg-transcode log :

>> ThrottleBySegmentRequest: RequestPosition: 00:24:06 - TranscodingPosition: 00:26:20 - ThrottleBuffer: 134s (Treshold: 120s)
21:39:03.389 elapsed=00:20:11.83 frame=31696 fps= 26 q=18.0 size=N/A time=00:22:02.11 bitrate=N/A throttle=100 speed=1.09x    
21:39:03.930 elapsed=00:20:12.37 frame=31701 fps= 26 q=19.0 size=N/A time=00:22:02.11 bitrate=N/A throttle=100 speed=1.09x    
21:39:04.486 elapsed=00:20:12.93 frame=31702 fps= 26 q=19.0 size=N/A time=00:22:02.19 bitrate=N/A throttle=100 speed=1.09x    
21:39:05.027 elapsed=00:20:13.47 frame=31702 fps= 26 q=19.0 size=N/A time=00:22:02.30 bitrate=N/A throttle=100 speed=1.09x    
>> ThrottleBySegmentRequest: RequestPosition: 00:24:06 - TranscodingPosition: 00:26:20 - ThrottleBuffer: 134s (Treshold: 120s)
21:39:05.568 elapsed=00:20:14.01 frame=31702 fps= 26 q=19.0 size=N/A time=00:22:02.41 bitrate=N/A throttle=100 speed=1.09x    
21:39:06.125 elapsed=00:20:14.57 frame=31705 fps= 26 q=19.0 size=N/A time=00:22:02.45 bitrate=N/A throttle=100 speed=1.09x    
21:39:06.665 elapsed=00:20:15.10 frame=31710 fps= 26 q=19.0 size=N/A time=00:22:02.45 bitrate=N/A throttle=100 speed=1.09x    
21:39:07.220 elapsed=00:20:15.66 frame=31710 fps= 26 q=19.0 size=N/A time=00:22:02.56 bitrate=N/A throttle=100 speed=1.09x    
>> ThrottleBySegmentRequest: RequestPosition: 00:24:06 - TranscodingPosition: 00:26:20 - ThrottleBuffer: 135s (Treshold: 120s)
21:39:07.761 elapsed=00:20:16.20 frame=31712 fps= 26 q=19.0 size=N/A time=00:22:02.62 bitrate=N/A throttle=100 speed=1.09x    
21:39:07.977 

[q] command received. Exiting.

emby logs :

2023-11-24 21:39:05.178 Info Server: http/1.1 POST http://‌‍‍192.168.1.67‌:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 9; AI PONT Build/PTO1.200330.001)
2023-11-24 21:39:05.178 Info Server: http/1.1 Response 204 to ‌‍‍192.168.1.5‌. Time: 1ms. http://‌‍‍192.168.1.67‌:8096/emby/Sessions/Playing/Progress
2023-11-24 21:39:07.873 Info Server: http/1.1 POST http://‌‍‍192.168.1.67‌:8096/emby/Sessions/Playing/Stopped. UserAgent: Dalvik/2.1.0 (Linux; U; Android 9; AI PONT Build/PTO1.200330.001)
2023-11-24 21:39:07.873 Info App: ProcessRun 'StreamTranscode cf40b7': Stopping ffmpeg process with q command for C:\Users\Vadim\AppData\Roaming\Emby-Server\programdata\transcoding-temp\EEC993\EEC993_86.ts
2023-11-24 21:39:08.059 Info App: AppendExtraLogData - Read graph file: C:\Users\Vadim\AppData\Roaming\Emby-Server\programdata\logs\ffmpeg-transcode-cf40b70a-03a8-457b-847e-0206a3c5443f_1graph.txt
2023-11-24 21:39:08.059 Info App: AppendExtraLogData - Deserialized GraphData fileStream: 15.987,00 bytes Graph Count: 1
2023-11-24 21:39:08.060 Info App: AppendExtraLogData - File Deleted
2023-11-24 21:39:08.062 Info App: ProcessRun 'StreamTranscode cf40b7' Process exited with code 0 - Succeeded
2023-11-24 21:39:08.063 Info SessionManager: Playback stopped reported by app AndroidTv 2.0.98g playing Philippi. Stopped at 1448016 ms
2023-11-24 21:39:08.063 Info Server: http/1.1 Response 204 to ‌‍‍192.168.1.5‌. Time: 190ms. http://‌‍‍192.168.1.67‌:8096/emby/Sessions/Playing/Stopped
2023-11-24 21:39:24.927 Info SystemEvents: SystemEvents_TimeChanged
2023-11-24 21:39:24.927 Info TaskManager: Daily trigger for Thumbnail image extraction set to fire at 11/25/2023 02:00:00, which is 260.58454165333336 minutes from now.
2023-11-24 21:39:26.011 Info SystemEvents: SystemEvents_TimeChanged

Additional info :

• It is NOT a network issue, the SMB server which serves my file is under docker with a fixed version. No hardware change, no software changes, everything exactly as it was when the playback worked fine 100% of the time
• I have already playback'd .mkv files with no issues
• I tried to send the Android TV logs as described in  How to report a problem ,but I could not find the "Debug Option"

This is really bugging me because it makes the app unusable, I have to restart emby at each crash (no way to resume the playback after that).

Any insight ?

embyserver-63836458781.txt ffmpeg-transcode-cf40b70a-03a8-457b-847e-0206a3c5443f_1.txt

Edited November 24, 2023 by ArthurAttout

[ebr 14960]

57 minutes ago, ArthurAttout said:

but I could not find the "Debug Option"

Hi.  It is at the bottom of the "General Display" page.

However, first, please be sure you haven't enabled the "Are you still watching" feature in the app.

[ArthurAttout 1]

Okay, just sent the logs from Android TV.

• What you were doing and what happened
  • Playing the episode "Philippi" of "Rome". Not touching anything. The playback froze at timestamp 24:08. The image stayed still, and did not return to the main menu
• The time you sent the log
  • 24th November 2023, 17:20~ish (UTC-5)
• The name of the Emby user
  • Vadim

The "Are you still watching ?" feature is disabled.

There is another setting under the Android TV App : Startup > Automatic disconnection, which was set to 1h. I just set it now to "never". 1h does not really match the delay between the moment I started watching and the actual crash, but it is worth trying.

Edited November 24, 2023 by ArthurAttout

[ebr 14960]

I don't see any playback in that log. Did you send it right from the playback screen when the problem occurred?

Also, what device is this?  I don't recognize it.

[ArthurAttout 1]

10 hours ago, ebr said:

I don't see any playback in that log. Did you send it right from the playback screen when the problem occurred?

Also, what device is this?  I don't recognize it.

Oh .. I thought this would send the logs from previous sessions as well. Will try again today if the problem appears again and let you know.

The device is a Neufunk TV.

[ArthurAttout 1]

Just sent a set of logs from the Android TV device where the bug triggered

• What you were doing and what happened

  Playing the episode "Philippi" of "Rome". Not touching anything. The playback froze at timestamp 46:31. The image stayed still, and did not return to the main menu

• The time you sent the log

  25th November 2023, 04:55~ish (UTC-5)

• The name of the Emby user

  Vadim

Attached emby and ffmpeg logs. Timestamp corresponds to the same weird ffmpeg sudden halt.

2023-11-25 10:55:20.137 Info Server: http/1.1 POST http://‌‍‍192.168.1.67‌:8096/emby/Sessions/Playing/Stopped. UserAgent: Dalvik/2.1.0 (Linux; U; Android 9; AI PONT Build/PTO1.200330.001)
2023-11-25 10:55:20.139 Info App: ProcessRun 'StreamTranscode 95a8cd': Stopping ffmpeg process with q command for C:\Users\Vadim\AppData\Roaming\Emby-Server\programdata\transcoding-temp\556210\556210_482.ts
2023-11-25 10:55:20.252 Info App: AppendExtraLogData - Read graph file: C:\Users\Vadim\AppData\Roaming\Emby-Server\programdata\logs\ffmpeg-transcode-95a8cd19-5ac1-4cad-9fd5-af66332939da_1graph.txt
2023-11-25 10:55:20.262 Info App: AppendExtraLogData - Deserialized GraphData fileStream: 15.987,00 bytes Graph Count: 1
2023-11-25 10:55:20.262 Info App: AppendExtraLogData - File Deleted
2023-11-25 10:55:20.308 Info App: ProcessRun 'StreamTranscode 95a8cd' Process exited with code 0 - Succeeded
2023-11-25 10:55:20.310 Info SessionManager: Playback stopped reported by app AndroidTv 2.0.98g playing Philippi. Stopped at 2794655 ms

embyserver-63836506578.txt

ffmpeg-transcode-95a8cd19-5ac1-4cad-9fd5-af66332939da_1.txt

[ebr 14960]

Unfortunately, I still did not get playback information.  It looks like you backed out to the home screen to send the log.  There is a send log option on the cog menu of the OSD during playback.

However, I think there is a clue in  your log anyway as it is reporting a timeout on one of the requests to your server.  That very well may be what is happening during playback.  Wired or wireless connection for the device?

[ArthurAttout 1]

51 minutes ago, ebr said:

It looks like you backed out to the home screen to send the log

Totally did. Will be careful next time to look for that option on the playback menu.

52 minutes ago, ebr said:

However, I think there is a clue in  your log anyway as it is reporting a timeout on one of the requests to your server.  That very well may be what is happening during playback.  Wired or wireless connection for the device?

Connection is wireless. Though, it really is a brand new issue. Maybe some device (either the server or the Android TV app) got updated, which introduced a regression. The TV is next to the router, I can stream 4K stuffs via other streaming platforms for an extended period of time before anything goes awry.

Which line is showing timeout-related information btw ?

[ArthurAttout 1]

2 minutes ago, ArthurAttout said:

Which line is showing timeout-related information btw ?

Silly question. I suppose it is on the logs from the Android TV device, which I cannot see. Maybe you could upload it so I can take a look into it as well ?

[ebr 14960]

21 hours ago, ArthurAttout said:

Which line is showing timeout-related information

The log was all chopped up by the Android system so I cannot tell exactly which call it was but that is an indication of something awry.

21 hours ago, ArthurAttout said:

I can stream 4K stuffs via other streaming platforms

None of those are going across your network to your local server.

If you can get me a log sent from the playback screen right after it freezes, I may be able to tell more.

Thanks.

[ArthurAttout 1]

I gave another round of watching today after plugging the TV through direct ethernet connection.

Worked with no issue for today. This now looks very much like a wifi issue on the TV itself.

I guess the thread can be closed, because this is not Emby-related anymore. I will try to replicate the issue, fetch the logs with LogCat and dig through them if I can.

Thanks for the help !