Jump to content

Android TV wont play .strm files


siteripper2
Go to solution Solved by ebr,

Recommended Posts

siteripper2

Hello,

 

I have the problem, that the App is crashing when I try to start a Movie. My movies are .strm files which direct to .mp4 files (aac sound).

I have no problems playing them in Webbrowser or Kodi.

 

Here is the error log:

2017-04-27 15:33:48.9345 Info HttpServer: HTTP GET http://IP:8096/emby/Users/8f6a459d6e324e369cb816772bcab83f/Items/db8060deae1c96f3427e8dbd13852b03/Intros?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 7.0; SHIELD Android TV Build/NRD90M)
2017-04-27 15:33:48.9372 Info HttpServer: HTTP Response 200 to 91.58.205.131. Time: 3ms. http://IP:8096/emby/Users/8f6a459d6e324e369cb816772bcab83f/Items/db8060deae1c96f3427e8dbd13852b03/Intros?format=json
2017-04-27 15:33:49.0699 Info HttpServer: HTTP POST http://IP:8096/emby/Items/db8060deae1c96f3427e8dbd13852b03/PlaybackInfo?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 7.0; SHIELD Android TV Build/NRD90M)
2017-04-27 15:33:49.1052 Info App: Profile: Android-VLC, Path: https://LINKTOFILE, isEligibleForDirectPlay: True, isEligibleForDirectStream: True
2017-04-27 15:33:49.1052 Info App: Profile: Android-VLC, Path: https://LINKTOFILE, isEligibleForDirectPlay: True, isEligibleForDirectStream: True
2017-04-27 15:33:49.1064 Info HttpServer: HTTP Response 200 to 91.58.205.131. Time: 37ms. http://IP:8096/emby/Items/db8060deae1c96f3427e8dbd13852b03/PlaybackInfo?format=json
2017-04-27 15:33:49.7231 Info HttpServer: HTTP POST http://IP:8096/emby/Items/db8060deae1c96f3427e8dbd13852b03/PlaybackInfo?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 7.0; SHIELD Android TV Build/NRD90M)
2017-04-27 15:33:50.2992 Info App: Profile: Android-Exo, Path: https://LINKTOFILE, isEligibleForDirectPlay: True, isEligibleForDirectStream: True
2017-04-27 15:33:50.2992 Info App: Profile: Android-Exo, Path: https://LINKTOFILE, isEligibleForDirectPlay: True, isEligibleForDirectStream: True
2017-04-27 15:33:50.3002 Info HttpServer: HTTP Response 200 to 91.58.205.131. Time: 577ms. http://IP:8096/emby/Items/db8060deae1c96f3427e8dbd13852b03/PlaybackInfo?format=json
2017-04-27 15:34:16.2081 Error HttpServer: Error in SharpWebSocket: An exception has occurred while receiving a message.. Exception.Message: The header part of a frame cannot be read from the data source.
2017-04-27 15:34:24.0488 Info HttpServer: HTTP HEAD http://IP:8096/emby/Items/539a2d23aaa2805d35771e5264c887b0/Images/Primary/0?MaxWidth=10000&MaxHeight=10000&Format=original&Tag=6bb5be426e768e1c9d188bc1113d36c3. UserAgent: Kodi/17.1 (Linux; Android 7.0; SHIELD Android TV Build/NRD90M) Android/7.0.0 Sys_CPU/aarch64 App_Bitness/64 Version/17.1-Git:20170320-797847d
2017-04-27 15:34:24.0506 Info HttpServer: HTTP Response 200 to 91.58.205.131. Time: 2ms. http://IP:8096/emby/Items/539a2d23aaa2805d35771e5264c887b0/Images/Primary/0?MaxWidth=10000&MaxHeight=10000&Format=original&Tag=6bb5be426e768e1c9d188bc1113d36c3

I hope you can help me with this :)

Link to comment
Share on other sites

Hi there, can you please attach the complete emby server log, as well as the ffmpeg log (if there was one). thanks !

Link to comment
Share on other sites

  • Solution

Hi.  Can you install the beta and try that?  I think it will at least get past the error you are having now.  Thanks.

  • Like 1
Link to comment
Share on other sites

siteripper2

Hello,

 

I tried it with the Beta App, the App does not crash anymore. It still does not play the movie. It just skips everything and says "too many errors".

 

Furthermore it also does not work on Android Mobile App.

 

This time I got ffmpeg logs (A LOT!) I attached two of them.

 

I also attached the server log (the interesting times are 15:14 - 15:16 and 23:04 - 23:11)

 

I hope that helps to find the problem.

server-63628934400.txt

ffmpeg-directstream-503f9f35-2c6f-4816-851f-5bdbd77d86d9.txt

ffmpeg-directstream-ba89ba54-5d27-401f-a2ad-add9d3dcc689.txt

Edited by siteripper2
Link to comment
Share on other sites

it just looks like some kind of stall within ffmpeg. in order to test this we're going to need the actual video url.

Link to comment
Share on other sites

siteripper2

Hello,

 

I am really sorry but it seems as if I wasted a little bit of your precious time. The access to the file was locked this morning so it did not work.

 

Android mobile is still working. I will check now if Android TV is also working using the Beta.

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...