Unable to Write Data to the transport connection = Grey Screen on Android

[imadunatic 28]

I'm having trouble streaming anything (mkv, mp4, avi, and live tv) to my Droid Turbo. I was going to post this issue over on the Android forum, but it looks like I'm having some errors on the server side that may actually be causing the issue. It streams beautifully, but every once in a while (could be every 10 seconds, could be a minute), the video goes grey (see below) almost like the old days when you had the wrong video codec and then a few seconds later, comes back and looks fine. 

 

Server Version: 3.0.5781.1

Android Version: 2.4.30

Windows 7 64 Bit

 

Server Logs: http://pastebin.com/5HzScCvj

 

Android Logs: http://pastebin.com/1q4fX1Rx

 

Android Screenshot: 

 

 

 

 

If this is the wrong spot for this, can someone please move it to the appropriate forum? 

 

Thanks in advance for any and all help. 

Edited November 12, 2015 by imadunatic

[Luke 36999]

The server error you see in the log is not really an error, it's just what happens after the client hangs up. I would try lowering the bitrate in the app's settings.

[imadunatic 28]

Thanks Luke. I think that might be my issue. I've got a max bitrate of .75 set in my server and no matter what I set the quality at in my phone, it looks stunning while it's playing, even down to 144kbps (which I can only assume should look quite blocky). 

 

Should I ask this question in the Android forum instead of here? 

[imadunatic 28]

So I pulled the transcode log from a streaming session... and it appears to streaming at a much higher bitrate than 144kbs p: http://pastebin.com/eQXQBQnB

 

My guess is I have a setting somewhere overiding my client settings..? 

Edited November 12, 2015 by imadunatic

[Luke 36999]

i'm unable to view that log.

[imadunatic 28]

i'm unable to view that log.

It would really help if I didn't set it to private    ... http://pastebin.com/eQXQBQnB

 

Should be fixed. 

[Luke 36999]

the bitrate looks correct based upon what the client requested. have you checked within the app's settings?

[imadunatic 28]

I did, I currently have it set to 144p:

 

 

I also just tried to play the same file from Chrome at work with it set to 144p, this is the transcode log from that: http://pastebin.com/2hJvELQ8

 

Is there any way for me to verify at the client end what bitrate I'm getting?

[Luke 36999]

If you've set the value in the app then it looks like a bug in the app. i will have to review and test that. thanks.

[imadunatic 28]

Ok, Just started a transcode with the client set to 144p, this is the mediainfo of the transcode.ts file: 

 

General

ID                                       : 1 (0x1)

Complete name                            : G:\Temp\Temp\transcoding-temp\32c24e59e672cc6e12a5b5a37ff8bd3b - Copy.ts

Format                                   : MPEG-TS

File size                                : 26.4 MiB

Duration                                 : 3mn 57s

Overall bit rate mode                    : Variable

Overall bit rate                         : 931 Kbps

 

Video

ID                                       : 256 (0x100)

Menu ID                                  : 1 (0x1)

Format                                   : AVC

Format/Info                              : Advanced Video Codec

Format profile                           : High@L4.1

Format settings, CABAC                   : Yes

Format settings, ReFrames                : 4 frames

Codec ID                                 : 27

Duration                                 : 3mn 58s

Width                                    : 720 pixels

Height                                   : 404 pixels

Display aspect ratio                     : 16:9

Frame rate mode                          : Variable

Color space                              : YUV

Chroma subsampling                       : 4:2:0

Bit depth                                : 8 bits

Scan type                                : Progressive

Writing library                          : x264 core 146 r2555 0c21480

Encoding settings                        : cabac=1 / ref=1 / deblock=1:0:0 / analyse=0x3:0x3 / me=dia / subme=1 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=0 / me_range=16 / chroma_me=1 / trellis=0 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=0 / threads=6 / lookahead_threads=1 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=3 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=1 / weightb=1 / open_gop=0 / weightp=1 / keyint=250 / keyint_min=25 / scenecut=40 / intra_refresh=0 / rc=crf / mbtree=0 / crf=23.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / ip_ratio=1.40 / pb_ratio=1.30 / aq=1:1.00

 

Audio

ID                                       : 257 (0x101)

Menu ID                                  : 1 (0x1)

Format                                   : AAC

Format/Info                              : Advanced Audio Codec

Format version                           : Version 4

Format profile                           : LC

Muxing mode                              : ADTS

Codec ID                                 : 15

Duration                                 : 3mn 57s

Bit rate mode                            : Variable

Channel(s)                               : 2 channels

Channel positions                        : Front: L R

Sampling rate                            : 44.1 KHz

Compression mode                         : Lossy

Delay relative to video                  : -57ms

 

Menu

ID                                       : 4096 (0x1000)

Menu ID                                  : 1 (0x1)

Duration                                 : 3mn 57s

List                                     : 256 (0x100) (AVC) / 257 (0x101) (AAC)

Service name                             : Service01

Service provider                         : FFmpeg

Service type                             : digital television

 

Surely, I have something set somewhere overriding my clients... 

[imadunatic 28]

If you've set the value in the app then it looks like a bug in the app. i will have to review and test that. thanks.

@@Luke, 

 

I'm getting a similar result from Chrome... no chance I have something screwed up on my server side? 

 

 

 

EDIT: Thanks for all the help Luke. Let me know if there is anything I can do on my end. 

Edited November 12, 2015 by imadunatic