-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
can't get it to work :( #15
Comments
Sure I’d be happy to help where I can. Did you set the correct up address from https://github.com/shivammaindola/AndroidWebRTC#changes-to-run-on-your-local-wifi-network? What logs do you see in your browser console? What logs do you see from your Python server? What logs do you see in Android Studio? |
Steps
Browser console logs INS: content-ads.js loaded: http://localhost:3000/ Android Studio console log ---------------------------- PROCESS STARTED (19306) for package com.myhexaville.androidwebrtc ---------------------------- |
Yeah the url on your android device can't be |
I got the IP to the server running on my windows machine. Another peer made a request to join room foo |
Great it would seem the Android device is now connected to the server. What are the Android logs now? They should be very different. https://github.com/shivammaindola/AndroidWebRTC/blob/master/VideoWebRTC/app/src/main/java/com/shivam/androidwebrtc/tutorial/CompleteActivity.java#L132 Shows the flow on the android side and shows the logs you are looking for to see where it’s stuck. Also it might be worth trying an input device on your PC that supports both video and audio. That might be a source of mismatch (although if I remember correctly it is possible to do just video and not audio). If you can’t figure it out post the logs from all devices with the fixed IP address and I’ll take a look and see if I see anything suspicious |
Oh and make sure you kill all processes between runs. Sometimes you can get stuck with multiple clients running. This implementation only supports 1 peer to 1 peer using a single room named “foo”. So close the browser tab, kill node, Kill the android app. Then start node. Start Android. Start browser |
Good news. I was able to connect now. thank you |
Great! Glad to hear it works now. As in 3 clients sharing video 3 ways? Or multiple rooms each with two clients? Neither are supported as is but the code can be modified to support it. For sharing video 3 ways you’d have to have the 3rd client join the room “foo” and have the 2 clients already connected each handshake with the third client without RE-handshaking with each other. For multiple rooms, just have the new clients use a different room name than “foo” |
Followed the example and can not even get it work locally.
Browser shows the webcam and in Android is shows the camera and that is all.
Please help.
The text was updated successfully, but these errors were encountered: