D34DC3N73R 18 Posted December 30, 2018 Posted December 30, 2018 (edited) I have a Pixel 2 XL on Verizon (Dec 5, 2018 Patch - build PQ1A.181205.002) and I'm unable to get playback to work over LTE using the Android Mobile app. I have the most recent version (updated Dec 25th, 2018) which the changelog states is 3.8.34. However, when opening the app details the app version is listed as 3.0.27. When switching to 420 kbps or under I'm able to get a few frames to play before freezing. Over wifi it works great (even when using a VPN - separate from the host server network). When using a port forward ssh tunnel over LTE, I can get 10Mbps playback through the browser. When connecting through https://emby.domain.tld I can get sustained playback at 480p - 420 Kbps. The server is Ubuntu 16.04 Docker v3.5.3.0. It has a Quadro P2000 (410.78 drivers with nvidia-docker2 package) and NVENC hw acceleration enabled as well as decode for H264, HEVC, MPEG2, MPEG4, and VC1. I use an nginx reverse proxy via the LS letsencrypt docker image and have the reverse proxy option enabled in the server settings. I've attached the server log. When browsing to the directory the app log is supposed to be in, nothing is there. Please let me know if there is any other info required to diagnose the issue. embyserver.txt ffmpeg-transcode-45af98d7-7878-40aa-9124-8ba6bd490beb.txt Edited December 30, 2018 by D34DC3N73R
Luke 42077 Posted December 30, 2018 Posted December 30, 2018 Hi, was there an ffmpeg log? Can you attach that too? Thanks.
D34DC3N73R 18 Posted December 30, 2018 Author Posted December 30, 2018 Hi, was there an ffmpeg log? Can you attach that too? Thanks. Attached to the original post.
Luke 42077 Posted December 30, 2018 Posted December 30, 2018 Strange. The log looks OK. Can you try turning off hardware transcoding on the server? Thanks.
D34DC3N73R 18 Posted December 30, 2018 Author Posted December 30, 2018 I did that as well as uninstalling and reinstalling the app to no avail.
D34DC3N73R 18 Posted January 1, 2019 Author Posted January 1, 2019 Seems to be resolved in the new update 3.0.28
Luke 42077 Posted January 2, 2019 Posted January 2, 2019 I would not have expected a big difference, but thanks for the feedback.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now