-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Playback error on Android #5
Comments
I'm seeing something very similar when try to play live or recorded tv on any android device: 2015-02-21 13:06:28,148 (1a2c) : CRITICAL (core:572) - Exception (most recent call last): 2015-02-21 13:06:28,151 (1a2c) : DEBUG (runtime:106) - Sending packed state data (111 bytes) 2015-02-21 13:06:28,345 (193c) : DEBUG (runtime:106) - Sending packed state data (111 bytes) |
@matthewrknoll I just submitted a PR for the workaround I used to get past this on my system. You might want to try it out and see if it works for you. |
Not sure if this change was merged back to the main code stream. I found I had to make similar changes w/ latest to get it to work with Android. I've attached the file. |
Ta. I'll check I committed in GitHub. On Sat, Jan 2, 2016 at 9:37 PM -0800, "Jose Luis Pino" notifications@github.com wrote: Not sure if this change was merged back to the main code stream. I found I had to make similar changes w/ latest to get it to work with Android. I've attached the file. Styling with Markdown is supported Write Preview init.py.txt — |
Should be closed. |
I'm unable to play any NextPVR video on my Android device (HTC One S), either Live TV or Recordings; I'm able to browse the catalog but when trying to play any video the Plex Android client simply reports: "An error occurred while attempting to navigate to the selected item. It appears that the associated server is no longer available."
I looked at the plugin logs on my Plex server, and I found this exception:
I'm using what I believe are the most recent versions of the Plex Android app (3.8.3.295) and Plex Media Server (0.9.11.7.803-87d0708). Any ideas what the issue could be, or how to solve this?
The text was updated successfully, but these errors were encountered: