Here's the log from each of the devices I get now when connecting to VLC using
v2.2.
On the Samsung Tab10.1 running 3.1 (app compiled with Android 2.3.3) I get,
04-29 11:21:37.540: E/AndroidRuntime(947): at
android.os.StrictMode$AndroidBlockGuardPolicy.onNetwork(StrictMode.java:1077)
04-29 11:21:37.540: E/AndroidRuntime(947): at
dalvik.system.BlockGuard$WrappedNetworkSystem.write(BlockGuard.java:290)
04-29 11:21:37.540: E/AndroidRuntime(947): at
org.apache.harmony.luni.net.PlainSocketImpl.write(PlainSocketImpl.java:462)
04-29 11:21:37.540: E/AndroidRuntime(947): at
org.apache.harmony.luni.net.SocketOutputStream.write(SocketOutputStream.java:55)
04-29 11:21:37.540: E/AndroidRuntime(947): at
net.majorkernelpanic.streaming.RtspServer.writeContent(RtspServer.java:325)
I believe this issue is Honeycomb related on the Tab10.1 (android 3.1).
http://stackoverflow.com/questions/6976317/android-http-conncetion-exception
On Motorola Droid running 2.3.4 (app compiled with Android 2.3.3) I get,
04-29 11:36:17.915: I/MediaRecorderJNI(5044): prepare: surface=0x2c53d8
(identity=40)
04-29 11:36:21.355: E/MediaRecorder(5044): stop called in an invalid state: 1
04-29 11:36:21.385: D/RTSPServer(5044): RTSP/1.0 200 OK
04-29 11:36:21.385: D/RTSPServer(5044): Cseq: 3
04-29 11:36:21.385: D/RTSPServer(5044): Content-Length: 294
04-29 11:36:21.385: D/RTSPServer(5044): Content-Base: 192.168.1.117:8087/
04-29 11:36:21.385: D/RTSPServer(5044): Content-Type: application/sdp
04-29 11:36:21.385: D/RTSPServer(5044):
04-29 11:36:21.385: D/RTSPServer(5044): m=audio 5004 RTP/AVP 96
04-29 11:36:21.385: D/RTSPServer(5044): b=AS:128
04-29 11:36:21.385: D/RTSPServer(5044): b=RR:0
04-29 11:36:21.385: D/RTSPServer(5044): a=rtpmap:96 AMR/8000
04-29 11:36:21.385: D/RTSPServer(5044): a=fmtp:96 octet-align=1;
04-29 11:36:21.385: D/RTSPServer(5044): a=control:trackID=0
04-29 11:36:21.385: D/RTSPServer(5044): m=video 5006 RTP/AVP 96
04-29 11:36:21.385: D/RTSPServer(5044): b=RR:0
04-29 11:36:21.385: D/RTSPServer(5044): a=rtpmap:96 H264/90000
04-29 11:36:21.385: D/RTSPServer(5044): a=fmtp:96
packetization-mode=1;profile-level-id=42801e;sprop-parameter-sets=Z0KAHpWgKA9fQA
==,aM48gA==;
04-29 11:36:21.385: D/RTSPServer(5044): a=control:trackID=1
04-29 11:36:21.445: I/MediaRecorderJNI(5044): prepare: surface=0x2c53d8
(identity=40)
04-29 11:36:23.355: W/IMediaDeathNotifier(5044): media server died
04-29 11:36:26.685: D/RTSPServer(5044): SETUP 192.168.1.117:8087/trackID=0
RTSP/1.0
04-29 11:36:26.685: D/RTSPServer(5044): CSeq: 4
04-29 11:36:26.685: D/RTSPServer(5044): User-Agent: LibVLC/2.0.1 (LIVE555
Streaming Media v2011.12.23)
04-29 11:36:26.685: D/RTSPServer(5044): Transport:
RTP/AVP;unicast;client_port=5004-5005
04-29 11:36:26.685: D/RTSPServer(5044):
04-29 11:36:26.695: D/RTSPServer(5044): RTSP/1.0 200 OK
04-29 11:36:26.695: D/RTSPServer(5044): Cseq: 4
04-29 11:36:26.695: D/RTSPServer(5044): Content-Length: 0
04-29 11:36:26.695: D/RTSPServer(5044): Transport:
RTP/AVP/UDP;unicast;client_port=5004-5005;server_port=54782-54783;ssrc=17a118bb;
mode=play
04-29 11:36:26.695: D/RTSPServer(5044): Session: 1185d20035702ca
04-29 11:36:26.695: D/RTSPServer(5044): Cache-Control: no-cache
04-29 11:36:26.695: D/RTSPServer(5044):
I had to change to port 8087 on the droid for some reason. It always complains
the port is already in use.
BTW, Is there a problem recompiling to use port 5006 for Wowza? That is, I see
this line of code,
public void h264TestResult(VideoQuality videoQuality, String[] params, SurfaceHolder holder) {
streamingManager.addH264Track(MediaRecorder.VideoSource.CAMERA, 5006, params, videoQuality, holder);
respondDescribe();
}
Original issue reported on code.google.com by mik...@gmail.com on 2 May 2012 at 11:04
Original issue reported on code.google.com by
mik...@gmail.comon 2 May 2012 at 11:04