Android tv app stopped working

General Discussions
1

Hi, a few days ago my tv app stopped working, when starting a video I get the loading screen for a few moments then the app seems to re start and it goes back to the home screen.

I have th e latest server version and have tried reinstalling the tv app.

Other devices and apps work fine it’s just the android tv app.

Is any one else having issues like this?

Thanks

2

Please list the exact version of the Plex app you have. Also what type of TV is it?

3

Hello, Plex for Android world 6.13.6.3452
Manufacturer: PHILIPS Device: philips_MT5593FHT_EU
Model: QM152E Product: philips_MT5593FHT_EU Version: 5.1.1

Here is some data from the log about the error.

02-13 18:21:14.557 i: [FF][MediaPeriod] Selecting tracks.
02-13 18:21:14.557 i: [BufferHelper] Assumed Bitrate: 10000, Segment Count: 1171
02-13 18:21:14.558 i: [BufferHelper] Segment count: 1171
02-13 18:21:14.581 i: [Exo2VideoPlayer] Switching video surface to use a standard surface.
02-13 18:21:14.586 i: [FF] Input has been seeked to 101312000us.
02-13 18:21:14.618 e: [FF] Error occurred during demuxing, ending input.
02-13 18:21:19.305 i: [pms] /192.168.1.6:55499 - GET /logging
02-13 18:21:21.625 i: Fetching [method:GET] https://192.168.1.2:32400/:/timeline?bufferedTime=0&containerKey=%2FplayQueues%2F5507&duration=1447764&guid=com.plexapp.agents.thetvdb%3A%2F%2F300921%2F1%2F1%3Flang%3Den&key=%2Flibrary%2Fmetadata%2F77006&location=lan&machineIdentifier=96df4a7530ce71b7ce740941bc6ed5f97b493171&playQueueItemID=72962&ratingKey=77006&state=buffering&time=101312&token=...tLpp&X-Plex-Client-Identifier=2a022afe551592ad-com-plexapp-android&X-Plex-Token=...tLpp
02-13 18:21:24.067 i: Creating PreplayEpisodeActivity.
02-13 18:21:24.359 i: ------------------------------
02-13 18:21:24.360 i: Hello, Plex for Android world 6.13.6.3452 (debug: false)!
02-13 18:21:24.360 i: Manufacturer: PHILIPS Device: philips_MT5593FHT_EU Model: QM152E Product: philips_MT5593FHT_EU Version: 5.1.1
02-13 18:21:24.363 i: Screen size: Large Screen density: TV Resolution: 1280x720 DPI: 213 Touchscreen: false Marketplace: com.android.vending Architecture: armeabi-v7a
02-13 18:21:24.375 w: [BootBehaviour][Background] i took 2ms to execute on the background thread.

It’s the same with every video, even ones that have previously worked.

Music seems to work though.

Thanks

4

[FF] Input has been seeked to 101312000us.
That’s not right. That would be 28hrs into the video. Please provide the full log.

5

See Attached,

Thanks

6

Your logs have already rolled over past that point you mentioned earlier and I do not see the same error later on. Please recreate the issue and get me a new log.

7

If you look at 02-13 19:14:47.198 in the log, just before this is the point at which the error happened.

I selected a video to play, had the loading spinner then the app restarted and took me back to the home screen.

I will try to re create the same error from earlier.

Thanks

8

Here is the full log, goes back to yesterday.

I attempted to play a number of videos just now all with the same result, hopefully there is something useful in the log.

Video of the issue here
https://photos.app.goo.gl/W8KPvpMal2sj9oQn2

Thanks.

9

Thanks for the video. It does appear to be what I am seeing in your log. The app is crashing silently without any indication of an error. Are you familiar with using ADB and getting a logcat?

10

Is this what you need?

11

Thank you. I have requested one of the developers to take a look.

12

Is there any update on this? Still got the issue.

13

I do not have any updates. The devs are still trying to figure out the problem.

14

Hi, still no update?

Thanks

15

Is there any update? I have exactly the same problem. Philips TV (55PFT6510/12). I have the latest 6.14 plex tv app installed as well.

16

The devs have identified a cause of the crash. We are looking into a fix. No ETA yet.

17

If you are in the Android Beta program, the potential fix is in Plex for Android 6.14.1.3740-beta. Please let us know if you see any improvements.

18

An update has been installed recently that seems to have corrected the issue.

Thanks

19

I have updated to the new release issued on 28th Feb and that appears to have fixed the issue. Great!