commit	a4cc62b2250d6bb2f79ca5d8e2e6eb5d2255dd86	[log] [tgz]
author	Scott Nien <scottnien@google.com>	Wed Apr 22 12:22:02 2020 +0800
committer	Scott Nien <scottnien@google.com>	Tue May 19 17:47:34 2020 +0800
tree	bc1ad19c2b77b74da94825427d16961ca4e58423
parent	1dd0060eec5646716e1b98256a1bb185737ac093 [diff]

Enable Camera2Interop request option to override all other request options.

(1) Apps can set any camera2 request options via Camera2Interop and will
    be the higest precendence over all other request options.

(2) Currently only Camera2Interop request option values
    are set as ALWAYS_OVRRIDE, all other option values are still the
    default value OPTIONAL.

    So everything is working as previously (CameraEventCallback
    onRepeating options > CameraControl options > use case options.
    ) The only change is now Camera2Interop can override all the
    other options even CameraEventCallback.

(3) Based on the new behavior of OptionPriority in Config,
    if priority needs to be kept after option copy , it needs
    modifications.
    Currently Camera2SessionOptionUnpacker /
    Camera2CaptureOptionUnpacker / UseCase#applyDefaults /
    CaptureConfig are modified to keep the option priority.

(4) Move Camera2InteropTest to non-instrumental tests and adds
a device test Camera2InteropDeviceTest to ensure the options can
be overridden successfully in devices. and Added
Camera2ImplConfigTest and moved some tests from
Camera2InteropTest to it.

Relnote: "Allowed applications to set any camera2 capture request
      parameters via Camera2Interop without causing a crash.
      Please note that if there are issues that arise as a result
      of overriding parameters, it won't be considered a bug.
      Reported bugs must be reproduciable without overriding
      parameters using Camera2Interop."
Bug: 149103700
Test: Camera2InteropDeviceTest, Camera2InteropTest,
  Camera2ImplConfigTest, Camera2SessionOptionUnpackerTest,
  Camear2CaptureOptionUnpackerTest, UseCaseTest,
  CaptureConfigTest.
Change-Id: Ibe5a101775aac7a7d257e4dfcb287ba66dd6df1d

15 files changed

tree: bc1ad19c2b77b74da94825427d16961ca4e58423

README.md

Android Jetpack

Jetpack is a suite of libraries, tools, and guidance to help developers write high-quality apps easier. These components help you follow best practices, free you from writing boilerplate code, and simplify complex tasks, so you can focus on the code you care about.

Jetpack comprises the androidx.* package libraries, unbundled from the platform APIs. This means that it offers backward compatibility and is updated more frequently than the Android platform, making sure you always have access to the latest and greatest versions of the Jetpack components.

Our official AARs and JARs binaries are distributed through Google Maven.

You can learn more about using it from Android Jetpack landing page.

Contribution Guide

Code Review Etiquette

When contributing to Jetpack, follow the code review etiquette.

Accepted Types of Contributions

Bug fixes - needs a corresponding bug report in the Android Issue Tracker
Each bug fix is expected to come with tests
Fixing spelling errors
Updating documentation
Adding new tests to the area that is not currently covered by tests
New features to existing libraries if the feature request bug has been approved by an AndroidX team member.

We are not currently accepting new modules.

Checking Out the Code

NOTE: You will need to use Linux or Mac OS. Building under Windows is not currently supported.

Install repo (Repo is a tool that makes it easier to work with Git in the context of Android. For more information about Repo, see the Repo Command Reference)

mkdir ~/bin
PATH=~/bin:$PATH
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo

Configure Git with your real name and email address.

git config --global user.name "Your Name"
git config --global user.email "you@example.com"

Create a directory for your checkout (it can be any name)

mkdir androidx-master-dev
cd androidx-master-dev

Use repo command to initialize the repository.

repo init -u https://android.googlesource.com/platform/manifest -b androidx-master-dev

Now your repository is set to pull only what you need for building and running AndroidX libraries. Download the code (and grab a coffee while we pull down 6GB):

repo sync -j8 -c

You will use this command to sync your checkout in the future - it’s similar to git fetch

Using Android Studio

To open the project with the specific version of Android Studio recommended for developing:

cd path/to/checkout/frameworks/support/
./studiow

and accept the license agreement when prompted. Now you're ready edit, run, and test!

If you get “Unregistered VCS root detected” click “Add root” to enable git integration for Android Studio.

If you see any warnings (red underlines) run Build > Clean Project.

Builds

Full Build (Optional)

You can do most of your work from Android Studio, however you can also build the full AndroidX library from command line:

cd path/to/checkout/frameworks/support/
./gradlew createArchive

Testing modified AndroidX Libraries to in your App

You can build maven artifacts locally, and test them directly in your app:

./gradlew createArchive

And put the following at the top of your ‘repositories’ property in your project build.gradle file:

maven { url '/path/to/checkout/out/androidx/build/support_repo/' }

Continuous integration

Our continuous integration system builds all in progress (and potentially unstable) libraries as new changes are merged. You can manually download these AARs and JARs for your experimentation.

Running Tests

Single Test Class or Method

Open the desired test file in Android Studio.
Right-click on a test class or @Test method name and select Run FooBarTest

Full Test Package

In the project side panel open the desired module.
Find the directory with the tests
Right-click on the directory and select Run androidx.foobar

Running Sample Apps

The AndroidX repository has a set of Android applications that exercise AndroidX code. These applications can be useful when you want to debug a real running application, or reproduce a problem interactively, before writing test code.

These applications are named either <libraryname>-integration-tests-testapp, or support-\*-demos (e.g. support-v4-demos or support-leanback-demos). You can run them by clicking Run > Run ... and choosing the desired application.

Password and Contributor Agreement before making a change

Before uploading your first contribution, you will need setup a password and agree to the contribution agreement:

Generate a HTTPS password: https://android-review.googlesource.com/new-password

Agree to the Google Contributor Licenses Agreement: https://android-review.googlesource.com/settings/new-agreement

Making a change

cd path/to/checkout/frameworks/support/
repo start my_branch_name .
# make needed modifications...
git commit -a
repo upload --current-branch .

If you see the following prompt, choose always:

Run hook scripts from https://android.googlesource.com/platform/manifest (yes/always/NO)?

If the upload succeeds, you'll see output like:

remote:
remote: New Changes:
remote:   https://android-review.googlesource.com/c/platform/frameworks/support/+/720062 Further README updates
remote:

To edit your change, use git commit --amend, and re-upload.

Getting reviewed

After you run repo upload, open r.android.com
Sign in into your account (or create one if you do not have one yet)
Add an appropriate reviewer (use git log to find who did most modifications on the file you are fixing or check the OWNERS file in the project's directory)

Handling binary dependencies

AndroidX uses git to store all the binary Gradle dependencies. They are stored in prebuilts/androidx/internal and prebuilts/androidx/external directories in your checkout. All the dependencies in these directories are also available from google(), jcenter(), or mavenCentral(). We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.