webrtc_m130

History

kjellander bd5621f065 Revert of Android: Add FramerateRange class (patchset #2 id:60001 of https://codereview.webrtc.org/2010763003/ )

Reason for revert:
Breaks downstream Android tests:
java.lang.NoSuchFieldError: no field with name='framerate' signature='org/webrtc/CameraEnumerationAndroid$CaptureFormat$FramerateRange' in class Lorg/webrtc/CameraEnumerationAndroid$CaptureFormat;

We should have a similar test in WebRTC so we can catch such errors pre-commit.

Original issue's description:
> Android: Add FramerateRange class
>
> The Camera1 and Camera2 API use different framerate range types. Camera1
> uses int[2] and Camera2 uses Range<Integer>. Range<Integer> is
> unfortunately only available on Lollipop and later, so this CL adds a
> similar FramerateRange class in CaptureFormat.
>
> The purpose with this CL is to have a common framerate range type that can
> be reused from both Camera1 and Camera2 in helper functions such as
> CameraEnumerationAndroid.getClosestSupportedFramerateRange().
>
> BUG=webrtc:5519
> R=sakal@webrtc.org
>
> Committed: https://crrev.com/94cb67d6df1a78e7fa25e469f719c1a8809dc583
> Cr-Commit-Position: refs/heads/master@{#12942}

TBR=sakal@webrtc.org,magjed@webrtc.org
NOTRY=True
BUG=webrtc:5519

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

2016-05-30 06:06:31 +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

Revert of Android: Add FramerateRange class (patchset #2 id:60001 of https://codereview.webrtc.org/2010763003/ )

2016-05-30 06:06:31 +00:00

third_party/autobanh

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

2015-08-05 22:48:29 +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