search

kensuke / How-to-Miracast-on-AOSP

Miracast Patches to AOSP
216 stars 101 forks source link

Merging with with AOSP 4.4.2 as a sink #1

Open aniket-cuelogic opened 9 years ago

aniket-cuelogic commented 9 years ago

I am trying to patch 4.4.2 with your 4.4.2 branch.

I'm able to match dependencies, and build the systemimage. Now while testing the app (Mira4U), I have found following issues. (I'm testing this as a WFD sink)

  1. Without Special Mode /NetworkSession( 2609): connecting socket 52 to 192.168.49.7:7236
    I/WifiDisplaySink( 2609): We're now connected.
    E/WifiDisplaySink( 2609): Invalid server_port description '19000'.
    F/WifiDisplaySink( 2609): frameworks/av/media/libstagefright/wifi-display/sink/WifiDisplaySink.cpp:652 CHECK_EQ( err,(status_t)OK) failed: -1007 vs. 0
  2. WIth Special Mode on - E/NetworkSession( 3357): Recvfrom failed, 199/200 retries left
    I/TimeSyncer( 3357): timed out, sending another request

TimeSyncer keeps on trying to recieve content, and times out.

Can please help in solving this?

kensuke commented 9 years ago

also Source side required TimerSyncer on.

I'm confirmed TimerSyncer working on below combination. Source: Nexus 4 Stock with update.zip and TimerSyncer on. Sink: Nexus 10 20140117_mira03_aosp442r1_manta-ota-eng.zip and special mode on.

2014-10-21 0:01 GMT+09:00, aniket-cuelogic notifications@github.com:

I am trying to patch 4.4.2 with your 4.4.2 branch.

I'm able to match dependencies, and build the systemimage. Now while testing the app (Mira4U), I have found following issues. (I'm testing this as a WFD sink)

  1. Without Special Mode /NetworkSession( 2609): connecting socket 52 to 192.168.49.7:7236

    I/WifiDisplaySink( 2609): We're now connected.

    E/WifiDisplaySink( 2609): Invalid server_port description '19000'.

    F/WifiDisplaySink( 2609): frameworks/av/media/libstagefright/wifi-display/sink/WifiDisplaySink.cpp:652 CHECK_EQ( err,(status_t)OK) failed: -1007 vs. 0

  2. WIth Special Mode on - E/NetworkSession( 3357): Recvfrom failed, 199/200 retries left

    I/TimeSyncer( 3357): timed out, sending another request

TimeSyncer keeps on trying to recieve content, and times out.

Can please help in solving this?

Reply to this email directly or view it on GitHub: https://github.com/kensuke/How-to-Miracast-on-AOSP/issues/1

kensuke commented 9 years ago

both Source and Sink required TimerSyncer, or delete TimerSyncer code on sink side...

27/ 28 TimeSyncer allows us to synchronize time between a client and a server. 29 The client sends a UDP packet containing its send-time to the server, 30 the server sends that packet back to the client amended with information 31 about when it was received as well as the time the reply was sent back. 32 Finally the client receives the reply and has now enough information to 33 compute the clock offset between client and server assuming that packet 34 exchange is symmetric, i.e. time for a packet client->server and 35 server->client is roughly equal. 36 This exchange is repeated a number of times and the average offset computed 37 over the 30% of packets that had the lowest roundtrip times. 38 The offset is determined every 10 secs to account for slight differences in 39 clock frequency. 40/