Jump to content

v3.0.31 playback crash to home screen


revengineer

Recommended Posts

revengineer

@@Luke, as promised here the documentation of v3.0.31 crashing to the home screen on my 7th gen Kindle Fire. The issue occurs after 1-5 min of playback time. The time for the issue to occur varies but I have reproduced this about 10 times now with one particular movie. On the other hand, I have watched TV shows that play for an hour without issues. The relevant snippet from the server log (v4.0.0.2) is shown below. The key entries are 

2019-01-18 19:23:31.942 Error HttpServer: WebSocket ConnectionClosedPrematurely
2019-01-18 19:23:31.943 Info HttpServer: SocketException: http://192.168.1.50:8096/emby/Videos/24766/stream.mp4?Static=true&mediaSourceId=9e7bff2e5fa75ff057ae8d465091b496&deviceId=76dce0426f7e7b75&api_key=346b4d34535042e49a54d70d569bba01

Extended snippet below

2019-01-18 19:23:01.015 Info HttpServer: HTTP POST http://192.168.1.50:8096/emby/Sessions/Playing. UserAgent: Mozilla/5.0 (Linux; Android 5.1.1; KFAUWI Build/LVY48F; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/59.0.3071.125 Safari/537.36
2019-01-18 19:23:01.018 Info HttpResultFactory: Setting range response values for M:\Movies\J-L\LITTLE_WOMEN.m4v. RangeRequest: bytes=614926688- Content-Length: 1748716056, Content-Range: bytes 614926688-2363642743/2363642744
2019-01-18 19:23:01.020 Info HttpServer: HTTP Response 204 to 192.168.1.76. Time: 4ms. http://192.168.1.50:8096/emby/Sessions/Playing
2019-01-18 19:23:01.042 Info HttpServer: SocketException: http://192.168.1.50:8096/emby/Videos/24766/stream.mp4?Static=true&mediaSourceId=9e7bff2e5fa75ff057ae8d465091b496&deviceId=76dce0426f7e7b75&api_key=346b4d34535042e49a54d70d569bba01
2019-01-18 19:23:01.042 Info HttpServer: HTTP Response 206 to 192.168.1.76. Time: 2885ms. http://192.168.1.50:8096/emby/Videos/24766/stream.mp4?Static=true&mediaSourceId=9e7bff2e5fa75ff057ae8d465091b496&deviceId=76dce0426f7e7b75
2019-01-18 19:23:01.067 Info HttpServer: HTTP GET http://192.168.1.50:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=7&minDate=2019-01-18T00%3A23%3A01.049Z&hasUserId=true. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36
2019-01-18 19:23:01.067 Info HttpServer: HTTP GET http://192.168.1.50:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=4&minDate=2019-01-12T00%3A23%3A01.050Z&hasUserId=false. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36
2019-01-18 19:23:01.067 Info HttpServer: HTTP GET http://192.168.1.50:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=7&minDate=2019-01-18T00%3A23%3A01.050Z&hasUserId=true. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36
2019-01-18 19:23:01.072 Info HttpServer: HTTP GET http://192.168.1.50:8096/emby/Users/2daf8f90b6a24446a79bfe82efaaced7. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36
2019-01-18 19:23:01.073 Info HttpServer: HTTP Response 200 to 192.168.1.11. Time: 1ms. http://192.168.1.50:8096/emby/Users/2daf8f90b6a24446a79bfe82efaaced7
2019-01-18 19:23:01.081 Info HttpServer: HTTP Response 200 to 192.168.1.11. Time: 15ms. http://192.168.1.50:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=4&minDate=2019-01-12T00%3A23%3A01.050Z&hasUserId=false
2019-01-18 19:23:01.083 Info HttpServer: HTTP GET http://192.168.1.50:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=4&minDate=2019-01-12T00%3A23%3A01.050Z&hasUserId=false. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36
2019-01-18 19:23:01.094 Info HttpServer: HTTP Response 200 to 192.168.1.11. Time: 27ms. http://192.168.1.50:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=7&minDate=2019-01-18T00%3A23%3A01.049Z&hasUserId=true
2019-01-18 19:23:01.106 Info HttpServer: HTTP Response 200 to 192.168.1.11. Time: 40ms. http://192.168.1.50:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=7&minDate=2019-01-18T00%3A23%3A01.050Z&hasUserId=true
2019-01-18 19:23:01.118 Info HttpServer: HTTP Response 200 to 192.168.1.11. Time: 35ms. http://192.168.1.50:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=4&minDate=2019-01-12T00%3A23%3A01.050Z&hasUserId=false
2019-01-18 19:23:01.286 Info HttpServer: HTTP POST http://192.168.1.50:8096/emby/Items/24766/PlaybackInfo?UserId=e0997acd42d1404c9e5337164159811c&StartTimeTicks=0&IsPlayback=false&AutoOpenLiveStream=false&MaxStreamingBitrate=140000000. UserAgent: Mozilla/5.0 (Linux; Android 5.1.1; KFAUWI Build/LVY48F; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/59.0.3071.125 Safari/537.36
2019-01-18 19:23:01.288 Info App: User policy for htpcuser. EnablePlaybackRemuxing: True EnableVideoPlaybackTranscoding: True EnableAudioPlaybackTranscoding: True
2019-01-18 19:23:01.288 Info App: Profile: Unknown Profile, Path: \\JEEVES\Movies\J-L\LITTLE_WOMEN.m4v, isEligibleForDirectPlay: True, isEligibleForDirectStream: True
2019-01-18 19:23:01.288 Info App: RemoteClientBitrateLimit: 3000000, RemoteIp: 192.168.1.76, IsInLocalNetwork: True
2019-01-18 19:23:01.288 Info App: Profile: Unknown Profile, Path: \\JEEVES\Movies\J-L\LITTLE_WOMEN.m4v, isEligibleForDirectPlay: True, isEligibleForDirectStream: True
2019-01-18 19:23:01.288 Info App: RemoteClientBitrateLimit: 3000000, RemoteIp: 192.168.1.76, IsInLocalNetwork: True
2019-01-18 19:23:01.288 Info App: Profile: Unknown Profile, Path: \\JEEVES\Movies\J-L\LITTLE_WOMEN.m4v, isEligibleForDirectPlay: True, isEligibleForDirectStream: True
2019-01-18 19:23:01.288 Info App: RemoteClientBitrateLimit: 3000000, RemoteIp: 192.168.1.76, IsInLocalNetwork: True
2019-01-18 19:23:01.289 Info HttpServer: HTTP Response 200 to 192.168.1.76. Time: 3ms. http://192.168.1.50:8096/emby/Items/24766/PlaybackInfo?UserId=e0997acd42d1404c9e5337164159811c&StartTimeTicks=0&IsPlayback=false&AutoOpenLiveStream=false&MaxStreamingBitrate=140000000
2019-01-18 19:23:01.677 Info HttpServer: HTTP POST http://192.168.1.50:8096/emby/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Linux; Android 5.1.1; KFAUWI Build/LVY48F; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/59.0.3071.125 Safari/537.36
2019-01-18 19:23:01.928 Info HttpServer: HTTP GET http://192.168.1.50:8096/emby/Users/2daf8f90b6a24446a79bfe82efaaced7. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36
2019-01-18 19:23:01.929 Info HttpServer: HTTP Response 200 to 192.168.1.11. Time: 1ms. http://192.168.1.50:8096/emby/Users/2daf8f90b6a24446a79bfe82efaaced7
2019-01-18 19:23:01.942 Info HttpServer: HTTP GET http://192.168.1.50:8096/emby/Users/e0997acd42d1404c9e5337164159811c. UserAgent: Mozilla/5.0 (Linux; Android 5.1.1; KFAUWI Build/LVY48F; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/59.0.3071.125 Safari/537.36
2019-01-18 19:23:01.942 Info HttpServer: HTTP Response 200 to 192.168.1.76. Time: 1ms. http://192.168.1.50:8096/emby/Users/e0997acd42d1404c9e5337164159811c
2019-01-18 19:23:01.945 Info HttpServer: HTTP GET http://192.168.1.50:8096/emby/System/Logs. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36
2019-01-18 19:23:01.945 Info HttpServer: HTTP GET http://192.168.1.50:8096/emby/System/Configuration. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36
2019-01-18 19:23:01.949 Info HttpServer: HTTP Response 200 to 192.168.1.11. Time: 5ms. http://192.168.1.50:8096/emby/System/Logs
2019-01-18 19:23:01.949 Info HttpServer: HTTP Response 200 to 192.168.1.11. Time: 4ms. http://192.168.1.50:8096/emby/System/Configuration
2019-01-18 19:23:02.406 Info HttpServer: HTTP Response 204 to 192.168.1.76. Time: 729ms. http://192.168.1.50:8096/emby/Sessions/Playing/Progress
2019-01-18 19:23:05.873 Info HttpServer: HTTP GET http://192.168.1.50:8096/emby/System/Logs/Log?name=embyserver.txt. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36
2019-01-18 19:23:05.992 Info HttpServer: HTTP Response 200 to 192.168.1.11. Time: 119ms. http://192.168.1.50:8096/emby/System/Logs/Log?name=embyserver.txt
2019-01-18 19:23:11.923 Info HttpServer: HTTP POST http://192.168.1.50:8096/emby/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Linux; Android 5.1.1; KFAUWI Build/LVY48F; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/59.0.3071.125 Safari/537.36
2019-01-18 19:23:11.929 Info HttpServer: HTTP Response 204 to 192.168.1.76. Time: 6ms. http://192.168.1.50:8096/emby/Sessions/Playing/Progress
2019-01-18 19:23:21.928 Info HttpServer: HTTP POST http://192.168.1.50:8096/emby/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Linux; Android 5.1.1; KFAUWI Build/LVY48F; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/59.0.3071.125 Safari/537.36
2019-01-18 19:23:21.929 Info HttpServer: HTTP Response 204 to 192.168.1.76. Time: 1ms. http://192.168.1.50:8096/emby/Sessions/Playing/Progress
2019-01-18 19:23:31.942 Error HttpServer: WebSocket ConnectionClosedPrematurely
2019-01-18 19:23:31.943 Info HttpServer: SocketException: http://192.168.1.50:8096/emby/Videos/24766/stream.mp4?Static=true&mediaSourceId=9e7bff2e5fa75ff057ae8d465091b496&deviceId=76dce0426f7e7b75&api_key=346b4d34535042e49a54d70d569bba01
2019-01-18 19:23:31.943 Info HttpServer: HTTP Response 206 to 192.168.1.76. Time: 30927ms. http://192.168.1.50:8096/emby/Videos/24766/stream.mp4?Static=true&mediaSourceId=9e7bff2e5fa75ff057ae8d465091b496&deviceId=76dce0426f7e7b75
2019-01-18 19:23:38.593 Info HttpServer: HTTP GET http://192.168.1.50:8096/emby/System/Logs/Log?name=embyserver.txt. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36
Link to comment
Share on other sites

revengineer

Additional info: The movie above plays fine in the web browser on my windows machine. I also tried another movie and I tried transcoding to a lower bitrate. I was able to reproduce this under all scenarios. Only exception seem to be the TV shows even though the have a similar bitrate.

Link to comment
Share on other sites

revengineer

I tried the chrome browser on the Fire and the movies play flawlessly there. Also download to external SD card worked with chrome. 

Link to comment
Share on other sites

revengineer

If you lower the in-app quality to force a full transcode, does this change anything?

 

As I wrote in post #2, transcoding to a lower bitrate did not resolve the issue. I cannot says whether or not it prolonged the viewing before crashing because the time for the issues to occur varies but is no more than a couple of minutes.

Link to comment
Share on other sites

revengineer

I also need to correct the post in my other thread: The issue has nothing to do with using subtitles. I have now confirmed that the issue occurs with and without subtitles.

Link to comment
Share on other sites

revengineer

I think there are. There seems to be a pattern that my movies encoded in handbrake all with the same setting have this issue while TV shows recorded by emby and subsequently compressed with handbrake do not. The bitrate is about the same. As reported before all play fine via the web browser on the device to wifi does not seem to be the issue.

Link to comment
Share on other sites

revengineer

So I watched one of those TV episodes that I thought were working and encountered the crash to the home screen after about 35 minutes. The time for the issue to occur was markedly longer but the unwanted event did eventually occur. I also tried my two test movies with an an external player (VLC). That seems to work without interruption  (tested for 10 min). Draw back here was that once I exited the playback I could not get that same movie to play again even after closing and restarting the apps. I found one hour later that one movie showed as playing on the server even though the client long aborted the playback. This is a separate issue but it supports my impression that I am playing whack-a-mole with the bugs in the android app.

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...