Server Version#: 1.22.1.4200
Player Version#: 8.14.1.23548 (88dd4b13)
On Android, If i change the “quality” during playback to anything 720p or less, the app immediately soft-crashes. By this I mean it just goes back to the splash screen and immediately reboots. (It doesn’t formally crash as in the Plex app never exits back to my phone screen. It just restarts the application while it’s running.)
This is what I’ve tried in order to debug it myself:
-
Using windows browser to open plex and transcoding the same video file to any of the formats (720p, 480p, etc.) all work fine.
-
On my Android device, setting to “convert automatically” or “1080p” work but are super slow and buffer’y. But the playback never crashes in the same way as the lower resolutions.
-
I tried setting up two different plex servers. One on a FreeNAS machine. And another using a synology NAS. Regardless of which one I choose on Android, the symptom is the same.
-
I tried going on the Android phone to Settings > Help & Support > Debugging > Share Debugging Info. But it looks mostly like gibberish and not human readable logs. (Plex for Android Logs (mrhappyasthma@gmail.com) - Google Drive)
-
I enabled ‘Network logging’ on Android at my local host (192.168.0.249:32500/logging). This maybe provided some useful info, but I’m not 100% sure what I’m looking at. (Log file: log.txt - Google Drive)
There’s a few exceptions in the log from the client, but I think the interesting one is
03-29 14:07:25.217 e: Fatal exception occurred. 03-29 14:07:25.218 e: An exception occurred: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 03-29 14:07:25.218 e: Stacktrace: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.get(ArrayList.java:437) at com.plexapp.plex.player.engines.exoplayer.v.b(SourceFile:3) at com.plexapp.plex.player.engines.exoplayer.v.i(SourceFile:2) at com.plexapp.plex.player.engines.n1.n2(SourceFile:26) at com.plexapp.plex.player.engines.n1.N(SourceFile:6) at com.google.android.exoplayer2.k0$b.p(SourceFile:1) at com.google.android.exoplayer2.k0$b.q(Unknown Source:0) at com.google.android.exoplayer2.g.a(Unknown Source:2) at com.google.android.exoplayer2.c0$a.a(SourceFile:2) at com.google.android.exoplayer2.k0.K(SourceFile:2) at com.google.android.exoplayer2.k0.w(SourceFile:1) at com.google.android.exoplayer2.k0$b.run(SourceFile:11) at com.google.android.exoplayer2.k0.U(SourceFile:4) at com.google.android.exoplayer2.k0.e0(SourceFile:12) at com.google.android.exoplayer2.k0.J(SourceFile:19) at com.google.android.exoplayer2.k0.P(SourceFile:1) at com.google.android.exoplayer2.k0.Q(Unknown Source:0) at com.google.android.exoplayer2.d.run(Unknown Source:4) at android.os.Handler.handleCallback(Handler.java:938) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loop(Looper.java:246) at android.app.ActivityThread.main(ActivityThread.java:8506) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:602) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1130)
This seems like an issue with the Android app itself and not something specific to my server setups.
