![]() |
Problem playing video in Android app - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting) +--- Thread: Problem playing video in Android app (/t-problem-playing-video-in-android-app) |
Problem playing video in Android app - mjremijan - 2025-06-30 Hi all. I have a video which plays successfully through the Microsoft Edge using the Jellyfin web app. However, I cannot get that same video to play through the Android app. On Android, the I get the video splashscreen then it seems to timeout forever. I have tried force stopping and restarting the Jellyfin Android app multiple times. Still no luck. Are there any logs I can use to try and troubleshoot this problem? RE: Problem playing video in Android app - bitmap - 2025-06-30 Dashboard > Logs Alternatively: https://jellyfin.org/docs/general/administration/configuration#log-directory You can remove your domain or other private data like a public IP and post them to privatebin.net or similar pastebin and we can take a look. If transcoding is triggered, those logs would be useful as well. RE: Problem playing video in Android app - mjremijan - 2025-06-30 Ok, so I checked the log files and the only one that seems to be getting changed today is " jellyfin20250630.log " I tailed this log file when making the request to play the problematic video. From --- Android --- the logs were consistent and looked as follows. Code: [2025-06-30 11:09:54.260 -05:00] [INF] User policy for "jellyfin-parent". EnablePlaybackRemuxing: True EnableVideoPlaybackTranscoding: True EnableAudioPlaybackTranscoding: True Android never starts playing the video. The android app shows an image from the video like a waiting splash screen, but it just gets stuck there. I also tried playing the problematic video from Microsoft Edge through the Jellyfin web app. When I do, it streams successfully. The log files look identical though. Code: [2025-06-30 11:27:26.472 -05:00] [INF] User policy for "jellyfin-parent". EnablePlaybackRemuxing: True EnableVideoPlaybackTranscoding: True EnableAudioPlaybackTranscoding: True I also tried on Android streaming a few different videos and they were able to successfully play. For example, one video played successfully and I saw this in the logs: Code: [2025-06-30 15:27:07.343 -05:00] [INF] User policy for "jellyfin-parent". EnablePlaybackRemuxing: True EnableVideoPlaybackTranscoding: True EnableAudioPlaybackTranscoding: True A different video played successfully without using ffmpeg, an it looked like this in the logs: Code: [2025-06-30 15:28:42.839 -05:00] [INF] User policy for "jellyfin-parent". EnablePlaybackRemuxing: True EnableVideoPlaybackTranscoding: True EnableAudioPlaybackTranscoding: True NOW, HERE IS A FINAL BIT OF FUN INFORMATION. If I use the same server URL in Chrome on Android, I can successfully stream the problematic video, but the Jellyfin app on Android still can't stream it. (2025-06-30, 01:19 PM)bitmap Wrote: Dashboard > Logs RE: Problem playing video in Android app - bitmap - 2025-07-01 Is the behavior different remotely vs. locally? Are you using a reverse proxy like nginx or Caddy? I've been seeing so many posts lately where folks haven't paid attention to websocket requirements and the symptoms are similar...probably just my brain connecting unrelated incidents. The video that played successfully appears to have been transcoding, whereas the others appear to be attempting direct play. I'm not certain why the behavior would be different when transcoding vs. not, but it's a clue at least. RE: Problem playing video in Android app - mjremijan - 2025-07-01 No reverse proxy. I haven't tried the Android app with a local IP address, but I will give it a shot. On my phone, both the Jellyfin Android app and Chrome use the same remote hostname; Chrome works fine but the Android app does not. Once I try the Android app with a local IP address I will reply again. RE: Problem playing video in Android app - mjremijan - 2025-07-01 Well, I can't tell you what changed but it working with the Android App now. |