Thanks I was just looking at your logs, that’s good news the original issue is fixed. The new crash is even odder though 
Do you have subtitles enabled at all? And do you have any of the preferences enabled that would limit your stream quality?
1 Like
@sixones I’ve downloaded your debug APK, and two things instantly were different to the standard APK.
- There was no option to disable the new player (re: your warning)
- I had a proper thumbnail and info in the dashboard for the Live TV session.
The latter makes me think that I won’t be able to reproduce the issue with this particular version of the APK
Ah sorry that option has been removed, completely forgot about that.
This version does contain a number of player improvements, including an updated ExoPlayer (latest version).
Have you experienced a crash with the build?
Not yet! Will leave it running today, will see how far it gets. Appreciate your help thus far.
BlockquoteThanks I was just looking at your logs, that’s good news the original issue is fixed. The new crash is even odder though
Do you have subtitles enabled at all? And do you have any of the preferences enabled that would limit your stream quality?
No, Everything was default preferences. No subtitles. Streaming not limited. Local Streaming, close range to wifi router. Gigabit ethernet and an AX6000 wifi router, so no speed issues.
Thanks for letting me know! Do you see the issue every time you play Live TV?
Hi @sixones. I don’t want to hijack the problem solving taking place for the fire stick but we also have the issue on our shield (android based as well so I’m assuming same exoplayer issue). We run CC on our live TV all the time due to having a loud house with kiddos and we will always see the issue unless we turn closed captions/subtitles off. The distinction seems to be direct play for the mpeg2 stream without CC vs the forced transcode due to EIA_608 subtitles causing transcodes; not supported in container
Enabling closed captioning and therefore transcoding will cause the issue for us without fail on shield. I’d be glad to test out an updated APK with enhanced logging there if providing that is trivial.
Hi @sixones,
Yes, every time I watch NBC the player crashes.
I just tried a different channel (quest) and it played for a while then I got a continuous spinning icon in the center of the screen. I checked the logs and found this.
If you scroll over to the right you will see the “time” increases until it gets to the “duration”. Once time is greater than duration(1800000), the player hangs indefinitely.
Also, PMS issues the following: INFO - Time value greater than duration.
I’ll PM you the log file.
Line 9002: 01-11 15:07:28.507 i: Fetching [method:GET] https://192.168.1.140:32400/:/timeline?airingID=222139&audioStreamID=288809&duration=1800000&guid=plex%3A%2F%2Fepisode%2F5fc6b788c40548002d4b4d57&key=%2Flivetv%2Fsessions%2F9ceb3b28-ad55-4918-88b7-b57a61e6b798&playbackTime=1086162&playQueueItemID=69.5-1610393400000&ratingKey=121443&state=playing&time=1790124&token=...gYad&X-Plex-Client-Identifier=c2ba770c8a492cb4-com-plexapp-android&X-Plex-Token=...gYad
Line 9051: 01-11 15:07:29.012 i: Fetching [method:GET] https://192.168.1.140:32400/:/timeline?airingID=222139&audioStreamID=288809&duration=1800000&guid=plex%3A%2F%2Fepisode%2F5fc6b788c40548002d4b4d57&key=%2Flivetv%2Fsessions%2F9ceb3b28-ad55-4918-88b7-b57a61e6b798&playbackTime=1086678&playQueueItemID=69.5-1610393400000&ratingKey=121443&state=playing&time=1790394&token=...gYad&X-Plex-Client-Identifier=c2ba770c8a492cb4-com-plexapp-android&X-Plex-Token=...gYad
Line 9313: 01-11 15:07:32.543 i: Fetching [method:GET] https://192.168.1.140:32400/:/timeline?airingID=222139&audioStreamID=288809&duration=1800000&guid=plex%3A%2F%2Fepisode%2F5fc6b788c40548002d4b4d57&key=%2Flivetv%2Fsessions%2F9ceb3b28-ad55-4918-88b7-b57a61e6b798&playbackTime=1090199&playQueueItemID=69.5-1610393400000&ratingKey=121443&state=playing&time=1794092&token=...gYad&X-Plex-Client-Identifier=c2ba770c8a492cb4-com-plexapp-android&X-Plex-Token=...gYad
Line 9399: 01-11 15:07:33.585 i: Fetching [method:GET] https://192.168.1.140:32400/:/timeline?airingID=222139&audioStreamID=288809&duration=1800000&guid=plex%3A%2F%2Fepisode%2F5fc6b788c40548002d4b4d57&key=%2Flivetv%2Fsessions%2F9ceb3b28-ad55-4918-88b7-b57a61e6b798&playbackTime=1091219&playQueueItemID=69.5-1610393400000&ratingKey=121443&state=playing&time=1795116&token=...gYad&X-Plex-Client-Identifier=c2ba770c8a492cb4-com-plexapp-android&X-Plex-Token=...gYad
Line 9816: 01-11 15:07:38.899 i: Fetching [method:GET] https://192.168.1.140:32400/:/timeline?airingID=222139&audioStreamID=288809&duration=1800000&guid=plex%3A%2F%2Fepisode%2F5fc6b788c40548002d4b4d57&key=%2Flivetv%2Fsessions%2F9ceb3b28-ad55-4918-88b7-b57a61e6b798&playbackTime=1096561&playQueueItemID=69.5-1610393400000&ratingKey=121443&state=playing&time=1800296&token=...gYad&X-Plex-Client-Identifier=c2ba770c8a492cb4-com-plexapp-android&X-Plex-Token=...gYad
Line 9820: 01-11 15:07:38.928 e: Error fetching https://192.168.1.140:32400/:/timeline?airingID=222139&audioStreamID=288809&duration=1800000&guid=plex%3A%2F%2Fepisode%2F5fc6b788c40548002d4b4d57&key=%2Flivetv%2Fsessions%2F9ceb3b28-ad55-4918-88b7-b57a61e6b798&playbackTime=1096561&playQueueItemID=69.5-1610393400000&ratingKey=121443&state=playing&time=1800296&token=...gYad&X-Plex-Client-Identifier=c2ba770c8a492cb4-com-plexapp-android&X-Plex-Token=...tml>
Line 9851: 01-11 15:07:39.100 i: Fetching [method:GET] https://192.168.1.140:32400/:/timeline?airingID=222139&audioStreamID=288809&duration=1800000&guid=plex%3A%2F%2Fepisode%2F5fc6b788c40548002d4b4d57&key=%2Flivetv%2Fsessions%2F9ceb3b28-ad55-4918-88b7-b57a61e6b798&playbackTime=1096683&playQueueItemID=69.5-1610393400000&ratingKey=121443&state=paused&time=1800353&token=...gYad&X-Plex-Client-Identifier=c2ba770c8a492cb4-com-plexapp-android&X-Plex-Token=...gYad
Line 9853: 01-11 15:07:39.103 e: Error fetching https://192.168.1.140:32400/:/timeline?airingID=222139&audioStreamID=288809&duration=1800000&guid=plex%3A%2F%2Fepisode%2F5fc6b788c40548002d4b4d57&key=%2Flivetv%2Fsessions%2F9ceb3b28-ad55-4918-88b7-b57a61e6b798&playbackTime=1096683&playQueueItemID=69.5-1610393400000&ratingKey=121443&state=paused&time=1800353&token=...gYad&X-Plex-Client-Identifier=c2ba770c8a492cb4-com-plexapp-android&X-Plex-Token=...tml>
Line 9879: 01-11 15:07:39.173 i: Fetching [method:GET] https://192.168.1.140:32400/:/timeline?airingID=222139&audioStreamID=288809&duration=1800000&guid=plex%3A%2F%2Fepisode%2F5fc6b788c40548002d4b4d57&key=%2Flivetv%2Fsessions%2F9ceb3b28-ad55-4918-88b7-b57a61e6b798&playbackTime=1096822&playQueueItemID=69.5-1610393400000&ratingKey=121443&state=paused&time=353&token=...gYad&X-Plex-Client-Identifier=c2ba770c8a492cb4-com-plexapp-android&X-Plex-Token=...gYad
Line 10068: 01-11 15:07:43.331 i: Fetching [method:GET] https://192.168.1.140:32400/:/timeline?airingID=11925&audioStreamID=288809&duration=1800000&guid=plex%3A%2F%2Fepisode%2F5fc6b788c40548002d4b4d57&key=%2Flivetv%2Fsessions%2F9ceb3b28-ad55-4918-88b7-b57a61e6b798&playbackTime=3672&playQueueItemID=69.5-1610393400000&ratingKey=121443&state=playing&time=0&token=...gYad&X-Plex-Client-Identifier=c2ba770c8a492cb4-com-plexapp-android&X-Plex-Token=...gYad
Line 10083: 01-11 15:07:49.025 i: Fetching [method:GET] https://192.168.1.140:32400/:/timeline?airingID=11925&audioStreamID=288809&duration=1800000&guid=plex%3A%2F%2Fepisode%2F5fc6b788c40548002d4b4d57&key=%2Flivetv%2Fsessions%2F9ceb3b28-ad55-4918-88b7-b57a61e6b798&playbackTime=3672&playQueueItemID=69.5-1610393400000&ratingKey=121443&state=playing&time=0&token=...gYad&X-Plex-Client-Identifier=c2ba770c8a492cb4-com-plexapp-android&X-Plex-Token=...gYad
Line 10089: 01-11 15:07:59.035 i: Fetching [method:GET] https://192.168.1.140:32400/:/timeline?airingID=11925&audioStreamID=288809&duration=1800000&guid=plex%3A%2F%2Fepisode%2F5fc6b788c40548002d4b4d57&key=%2Flivetv%2Fsessions%2F9ceb3b28-ad55-4918-88b7-b57a61e6b798&playbackTime=3672&playQueueItemID=69.5-1610393400000&ratingKey=121443&state=playing&time=0&token=...gYad&X-Plex-Client-Identifier=c2ba770c8a492cb4-com-plexapp-android&X-Plex-Token=...gYad
I’ve tried this build and I can’t tell if it fixes the issue as there seems to be additional issues added on top. Instead of 5 minutes of playback then nothing, it seems to be playing back 15 seconds in 5x speed then buffering, and getting the same 15 seconds back. There also seems to be a issue when tuning to a channel it doesn’t show any content. Going back to the latest beta build in the other thread these issues don’t appear, but the 5 minute limit does. Subtitles were enabled, but there’s no way as far as I can tell to disable them by default? I’ve DM’d you the logs with timestamps for everything I was doing.
@sixones similar situation here. Plex kicks me out of live tv stream after 5 or so minutes using the FireTV 4k stick trying to watch a 1080i channel (CBS). I can upload additional PMS logs if that would help, or create a new issue if that’s how things are done around here.
Recordings seem to playback great, but the live tv stream attempts to get transcoded, then transcoding sessions look to be killed when they probably shouldn’t have been.
HDHomerun’s app streams it just fine.
Please let me know if/how I can assist in the debug process.
Extra logs are always helpful from the client and PMS, something very odd is going on that is causing the issues and sadly they don’t seem to be replicating on the UK channels I have access too.
Hi @sixones,
I tried out the new beta APK in the fire stick 4k (kepler-armv7a-amazon-stdExo-8.12.0.22456-2a97bfe9.apk) and came away with the same issues as the apk that you provided.
I noticed that when watching NBC channel 6.1 it will play fine for a while then it will start "pausing and replaying the same part over and over. In the screenshot you can see the time increases fine until it reaches 772728 then it keeps repeating the 77xxxx. It goes on like this for a couple of minutes then the player finally crashes. I have no idea what the issue is. My iPhone plays this channel perfectly with Plex.
I’ll send you the full set of Fire Stick and PMS Debug logs in a PM.
Thank you and let me know what else I can do to test.
I can send you a .TS file from hdhomerun_config of the channel if you want. I tried to replicate by playing a downloaded .TS file, but it plays just fine since Plex doesn’t transcode when playing the .TS file, it just direct plays it even though it is 1080i.
01-12 20:14:16.120 e: [ExoPlayer][EventLogger] playerFailed [eventTime=388.70, mediaPos=319.02, window=0, period=0
com.google.android.exoplayer2.ExoPlaybackException: Unexpected runtime error
at com.google.android.exoplayer2.l0.handleMessage(SourceFile:30)
at android.os.Handler.dispatchMessage(Handler.java:98)
at android.os.Looper.loop(Looper.java:154)
at android.os.HandlerThread.run(HandlerThread.java:61)
Caused by: java.lang.IllegalStateException: Playback stuck buffering and not loading
at com.google.android.exoplayer2.l0.n(SourceFile:46)
at com.google.android.exoplayer2.l0.handleMessage(SourceFile:24)
... 3 more
]
01-12 20:14:16.121 e: [Player][ExoPlayer] Playback error detected
01-12 20:14:16.124 i: [FF] Releasing demuxer.
01-12 20:14:16.125 i: [FFmpeg] [INFO] Demuxer closing.
01-12 20:14:16.128 i: [FFmpeg] [INFO] Demuxer has been interupted...
01-12 20:14:16.129 e: An exception occurred: com.google.android.exoplayer2.ExoPlaybackException: Unexpected runtime error
01-12 20:14:16.131 i: [FFmpeg] [INFO] Demuxer has been closed, interrupting FFmpeg...
01-12 20:14:16.133 e: Stacktrace: com.google.android.exoplayer2.ExoPlaybackException: Unexpected runtime error
at com.google.android.exoplayer2.l0.handleMessage(SourceFile:30)
at android.os.Handler.dispatchMessage(Handler.java:98)
at android.os.Looper.loop(Looper.java:154)
at android.os.HandlerThread.run(HandlerThread.java:61)
Caused by: java.lang.IllegalStateException: Playback stuck buffering and not loading
at com.google.android.exoplayer2.l0.n(SourceFile:46)
at com.google.android.exoplayer2.l0.handleMessage(SourceFile:24)
... 3 more
01-12 20:14:16.134 i: [Player][Timeline] Handling player error
01-12 20:14:16.135 i: [Player][Timeline] Playback stopped (error: true)
Replicated the error this morning. I started the stream around 7:59 and it died around 8:02-8:03. PMS Logs seem to be timestamped an hour in the past, but I’ll send the relevant chunk of time here.Plex Media Server copy.log (921.5 KB)
I noticed yesterday that the stream will die when the forward and back arrows are grayed out as others have mentioned in this forum and other related posts about this. When I switch the quality (from auto to original, or original to auto, doesn’t seem to matter, just that you switch it once or twice), that gets the arrows to show up, and playback works as expected.
Hi @sixones,
I replicated the error again and this time also recorded the .TS file.
I was watching channel 6.1 for about 4 minutes before the Fire Stick player started to repeat itself over and over (with a spinning circle on the screen) then finally crashed.
I will send you a DM with the full App logs, PMS debug logs and 438mb .TS file.
App version: 8.12.0.22404 (818247752)
01-13 13:57:39.829 e: [ExoPlayer][EventLogger] playerFailed [eventTime=405.70, mediaPos=317.02, window=0, period=0
com.google.android.exoplayer2.ExoPlaybackException: Unexpected runtime error
at com.google.android.exoplayer2.l0.handleMessage(SourceFile:30)
at android.os.Handler.dispatchMessage(Handler.java:98)
at android.os.Looper.loop(Looper.java:154)
at android.os.HandlerThread.run(HandlerThread.java:61)
Caused by: java.lang.IllegalStateException: Playback stuck buffering and not loading
at com.google.android.exoplayer2.l0.n(SourceFile:46)
at com.google.android.exoplayer2.l0.handleMessage(SourceFile:24)
... 3 more
]
01-13 13:57:39.831 e: [Player][ExoPlayer] Playback error detected
01-13 13:57:39.834 e: An exception occurred: com.google.android.exoplayer2.ExoPlaybackException: Unexpected runtime error
01-13 13:57:39.835 e: Stacktrace: com.google.android.exoplayer2.ExoPlaybackException: Unexpected runtime error
at com.google.android.exoplayer2.l0.handleMessage(SourceFile:30)
at android.os.Handler.dispatchMessage(Handler.java:98)
at android.os.Looper.loop(Looper.java:154)
at android.os.HandlerThread.run(HandlerThread.java:61)
Caused by: java.lang.IllegalStateException: Playback stuck buffering and not loading
at com.google.android.exoplayer2.l0.n(SourceFile:46)
at com.google.android.exoplayer2.l0.handleMessage(SourceFile:24)
... 3 more
Managed to find a setup that I think replicates the same problem on a SHIELD instead of a Fire TV, the build below should fix the issue and allow Live TV to continue playing correctly instead of an endless loading spinner.
Fire TV / SHIELD Tube / armv7 build:
https://artifacts.plex.tv/android-experimental/8.12.0.22493-11f23d7a/PlexForAndroid-8.12.0.22493-11f23d7a-Armv7aAmazonFireExo.apk
SHIELD Pro / arm64 build:
https://artifacts.plex.tv/android-experimental/8.12.0.22493-11f23d7a/PlexForAndroid-8.12.0.22493-11f23d7a-Arm64v8aGooglePlayStdExo.apk
1 Like
I updated the plex app on our shield with the one provided and at first I was hopeful as it went quite a while without messing up. It no longer kicks the stream back out to the guide but instead started to do what seems like a buffer loop every second or so. After about 5 minutes of that it has frozen and is now spinning endlessly shieldlog.txt (1.1 MB)
Are these the logs that you need or are there others from the server itself that would give you. more insight?
Well that’s disappointing, there must be another issue at play, if you could share the server logs as well from the same playback attempt that would be a huge help.
1 Like
Same issue still exists with PlexForAndroid-8.12.0.22493-11f23d7a-Armv7aAmazonFireExo on Fire Stick 4k.
Channel 6.1 was playing fine, then a few commercials played, then it changed to a new commercial and started pausing buffering and replaying over and over. Then finally crashed.
I’ll PM you the logs.
01-13 19:53:16.231 e: [ExoPlayer][EventLogger] playerFailed [eventTime=748.06, mediaPos=498.00, window=0, period=0
com.google.android.exoplayer2.ExoPlaybackException: Unexpected runtime error
at com.google.android.exoplayer2.l0.handleMessage(SourceFile:30)
at android.os.Handler.dispatchMessage(Handler.java:98)
at android.os.Looper.loop(Looper.java:154)
at android.os.HandlerThread.run(HandlerThread.java:61)
Caused by: java.lang.IllegalStateException: Playback stuck buffering and not loading
at com.google.android.exoplayer2.l0.n(SourceFile:46)
at com.google.android.exoplayer2.l0.handleMessage(SourceFile:24)
... 3 more
]
01-13 19:53:16.236 e: [Player][ExoPlayer] Playback error detected
01-13 19:53:16.239 i: [FFmpeg] [INFO] Demuxer has been interupted...
01-13 19:53:16.240 i: [FFmpeg] [INFO] Demuxer has been closed, interrupting FFmpeg...
01-13 19:53:16.242 e: An exception occurred: com.google.android.exoplayer2.ExoPlaybackException: Unexpected runtime error
01-13 19:53:16.243 i: [PlaybackTimeBehaviour] Time: 739364 IsStarted: true
01-13 19:53:16.244 e: Stacktrace: com.google.android.exoplayer2.ExoPlaybackException: Unexpected runtime error
at com.google.android.exoplayer2.l0.handleMessage(SourceFile:30)
at android.os.Handler.dispatchMessage(Handler.java:98)
at android.os.Looper.loop(Looper.java:154)
at android.os.HandlerThread.run(HandlerThread.java:61)
Caused by: java.lang.IllegalStateException: Playback stuck buffering and not loading
at com.google.android.exoplayer2.l0.n(SourceFile:46)
at com.google.android.exoplayer2.l0.handleMessage(SourceFile:24)
... 3 more
Not sure exactly what logs you need but I think they were overwritten for the first event. I have started a new playback and observed the same issue. here are the logs:
Video of the issue: https://photos.app.goo.gl/ujZ375PEyq2fCJ4k6. I noticed on my receiver the signal for 5.1 kept cutting out. Maybe a clue. In this session I did some scrubbing toward the end and tried changing some settings but the buffer loop kept occurring.
