webrtc_m130

History

skvlad 4c4cb5b984 Separate the JNI function that controls logging levels into two.

The parameters for Logging.enableTracing() were creating the impression
that they control level and severity of one tracing system and they are
meant to be used together. In fact the "levels" parameter controlled one
tracing system (WEBRTC_TRACE), and the "severity" parameter was
responsible for a completely different one: setting the severity level
above which log messages from LOG() will be directed to the
platform-specific debug output (logcat on Android).

The method signature suggested that the "path" parameter applied to both
systems - while it was only meaningful for the WEBRTC_TRACE; LOG
messages were directed to ADB logcat no matter what the Path value was.
It is possible to redirect LOG messages to a file, but that is done
using a completely different set of APIs
 - PeerConnectionFactory.startInternalTracingCapture().

I've separated these two methods to make it more clear which of the
parameters controls which system.

NOTRY=true

Review-Url: https://codereview.webrtc.org/2110853003
Cr-Commit-Position: refs/heads/master@{#13334}

2016-06-29 22:30:48 +00:00

res

Add an option to disable built-in AEC to AppRTC Android Demo

2016-05-25 07:09:50 +00:00

src/org/appspot/apprtc

Separate the JNI function that controls logging levels into two.

2016-06-29 22:30:48 +00:00

third_party/autobanh

Add GN targets for AppRTC Demo on Android.

2016-06-29 12:55:12 +00:00

AndroidManifest.xml

UI for AppRTC Android demo that doesn't require Design Support Library

2016-05-24 07:18:18 +00:00

ant.properties

Move all the examples from the talk directory into the webrtc examples directory.

2015-08-05 22:48:29 +00:00

build.xml

Move all the examples from the talk directory into the webrtc examples directory.

2015-08-05 22:48:29 +00:00

project.properties

Move all the examples from the talk directory into the webrtc examples directory.

2015-08-05 22:48:29 +00:00

README

Use the new appr.tc URL

2016-04-15 14:16:19 +00:00

README

This directory contains an example Android client for https://appr.tc

Prerequisites:
- "Getting the code" on http://www.webrtc.org/native-code/android
- Set up webrtc-related GYP variables:
  export GYP_DEFINES="OS=android $GYP_DEFINES"
- When targeting both desktop & android, make sure to use a different output_dir
  value in $GYP_GENERATOR_FLAGS - for example
  export GYP_GENERATOR_FLAGS="$GYP_GENERATOR_FLAGS output_dir=out_android"
  or you'll likely end up with mismatched ARM & x86 output artifacts.
  If you use an output_dir other than out/ make sure to modify the command-lines
  below appropriately.
- Finally, run "gclient runhooks" to generate Android-targeting .ninja files.

Example of building & using the app:

cd <path/to/webrtc>/src
ninja -C out/Debug AppRTCDemo
adb install -r out/Debug/apks/AppRTCDemo.apk

In desktop chrome, navigate to https://appr.tc and note the r=<NNN> room
this redirects to or navigate directly to https://appr.tc/r/<NNN> with
your own room number. Launch AppRTC on the device and add same <NNN> into the room name list.

You can also run application from a command line to connect to the first room in a list:
adb shell am start -n org.appspot.apprtc/.ConnectActivity -a android.intent.action.VIEW
This should result in the app launching on Android and connecting to the 3-dot-apprtc
page displayed in the desktop browser.
To run loopback test execute following command:
adb shell am start -n org.appspot.apprtc/.ConnectActivity -a android.intent.action.VIEW --ez "org.appspot.apprtc.LOOPBACK" true