Ok, as tends to be the case with me I've figured out what my problem was only minutes after sending this request off: The root cause of my poor one-way audio latency is the android phone I was using to run my WebRTC app. For reference, the problem phone is an LG Optimus Zone 2 (Verizon, phone code VS415PP) running Android KitKat 4.4.2. I make the note in case someone else runs across a similar problem.
Also for reference, I have another low-end android device that works great with Crosswalk in this manner: ZTE Zinger (T-Mobile, Model #: Z667T). Both transmit and receive audio WebRTC latencies are below the quarter-second mark, which is much more palatable for my intended use. Rion From: Crosswalk-help [mailto:[email protected]] On Behalf Of Rion Carter Sent: Thursday, January 29, 2015 9:19 PM To: [email protected] Subject: [Crosswalk-help] Crosswalk WebRTC Latency on Android ARM devices Hi everyone, I recently built a WebRTC phone using the Plivo WebSDK and am running into a puzzling issue: there is a one-second delay when the person I call via WebRTC speaks to me. It does not matter what the endpoint is (Another WebRTC client, a SIP phone or a hard-line, it's always about a seconds worth of delay. What doesn't make sense to me is that when I talk on my WebRTC phone app, the other end receives the audio within a quarter second. This leads me to my question: Is there a way to tune WebRTC latencies in Crosswalk? Being new to WebRTC I'm not sure how much lag an 'incoming' audio stream is subject to before being played back. I am using Android ARM Webview version 10.39.235.15. Any guidance, advice or suggestions are appreciated. I'm chasing down all my leads at this point. Rion
_______________________________________________ Crosswalk-help mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-help
