The peer server seems to work fine. I get the messages on the server for the connection. When I make a call it does actually connect - I see the "outgoing call initiated" and "incoming call received" messages. I can also debug through the code on both desktop and Android with no errors, and see the assigned stream when I inspect the DOM, again on both platforms.
When the connection is received, the remote window is erratic. It sometimes collapses itself to a 2 pixel square, sometimes shows half black and half white, sometimes all white. I did make a change to the sample to add a server IP field rather than hardcoding, but that's it. Here's a variety of things I've tried: - Now attempted on a Nexus 4, Nexus 10, Samsung Galaxy S4, and HTC One for Android, and Windows 7, Ubuntu, and Max OSX for desktop. Perfectly consistent results - it always works with desktop, always fails if either is Android. - Tried it both inside the NAT and outside (with appropriate port forwarding on 9000). Again, don't think the PeerJS server is the issue, since the systems do find each other, per the messages. - Debugged through, was able to see the src field for the video being set on both sides. So, again, don't think the peering is the problem. I have no idea what's missing here, but the consistency of the results is discouraging. On Mon, Dec 8, 2014 at 12:34 AM, Shao, Changbin <[email protected]> wrote: > Hi, > Thank you for trying out Crosswalk WebRTC! > I've tested the sample application per guide from > https://crosswalk-project.org/documentation/webrtc.html. It works on my > ZTE Geek phone. > Could you please check that your android phone is connected to the > server? It ought to print message as 'new connection with id xxx' from > server side. > Below is my test procedure for your reference. > Server(10.239.37.35): > 1) ./run.sh, got the ip address and port. 10.239.37.35:9000 > > Linux desktop client(10.239.37.35): > 1) edit main.js, line 'var SERVER_IP = '192.168.0.25';' to the correct > server ip address 10.239.37.35. > 2) make sure all chrome processes are killed, by '$killall chrome' > 3) run index.html by > $ google-chrome --allow-file-access-from-files file:///<path to > xwalk-webrtc>/client/index.html > > Android mobile client(192.168.42.223): > 1) Fork new webrtc sample application, > 2) Connect android phone to linux desktop with USB cable. > 3) Let the phone share desktop's network, then '$ifconfig' to check the > assigned ip address for android phone. '192.168.42.223' > 3) Edit main.js to the assigned ip address. 192.168.42.223 > 6) make_apk(crosswalk-9.38.208.10) and then install on android device. > > Also add Smith Elliot in the loop, I think he is the author of the > sample application and may provide your with more details:) > > Changbin > > ------------------------------ > *From:* Crosswalk-help [[email protected]] > on behalf of Kevin Allen [[email protected]] > *Sent:* Saturday, December 06, 2014 7:33 AM > *To:* [email protected] > *Subject:* [Crosswalk-help] Crosswalk WebRTC streams get no remote feed > > I'm starting to work with WebRTC, and trying out Crosswalk as a > potential for use in the Android part of the system. I've been trying to > get the demo up and running, but whenever I make the call, I get no remote > video on either end of the connection. Here's things I've tried/confirmed: > > - Basic setup works. I can connect fine using two tabs in the same > browser > - Communication obviously works (previous test) > - If an Android device is in the mix, it fails. This holds true for > Android--Desktop, and Android--Android > - Sample code from the repository is unchanged, with the sole exception > that I added a Server IP field for entry, replacing the hardcoded IP > - Attempted debug/inspection. The full JS completes on each call/event. > No errors are reported or exceptions thrown. Element inspection looks > fine, and in both cases the successful Desktop--Desktop case shows no > visible differences from the Android--Desktop case. Checked on both the > desktop and the devices via remote debugging and chrome://inspect. > - Tried three different devices (Nexus 4, Nexus 10, Samsung Galaxy S4) > with identical results on each > - Tried two different versions of Crosswalk (9 and 8) > > ...and I'm out of other ideas. Any help appreciated! >
_______________________________________________ Crosswalk-help mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-help
