Google Git
Sign in
android / platform / frameworks / support / 6bff92c1917d18594f48209afdb53589131f4c88
commit6bff92c1917d18594f48209afdb53589131f4c88[log] [tgz]
authorPaul Rohde <[email protected]>Fri Sep 18 14:05:44 2020 -0700
committerPaul Rohde <[email protected]>Wed Sep 23 10:52:20 2020 -0700
tree4f31a6700a837ca4b12a874bbd843a36f6876201
parente34ab829267c2708d370f6e6be4ea90f596f654d [diff]
[CameraPipe] Add trace tags and reogranize threads

This change adds trace tags across a large number of blocking
interactions with Camera2. As a result of adding these trace tags, this
change improves the naming and organization of several internal threads
and executors to make it more obvious where blocking calls are
originating from when investigating systraces.

* Modify the Debug class to have inlined trace start/stop calls.
* Add tracing calls across different parts of the app.
* Reogranize threads to have CameraExecutor and CameraHandler that are
  passed to camera2 for callbacks.

Test: Ran the integration test app front/back on 2 devices.
Test: Captured and inspected systraces captured during app launch.
Test: Existing unit tests continue to pass.
Change-Id: Iacdab2bb76f5b2157aaa5d80c3f039e1a2f2e8dd
21 files changed
tree: 4f31a6700a837ca4b12a874bbd843a36f6876201
  1. .github/
  2. .idea/
  3. activity/
  4. ads/
  5. androidx-plugin/
  6. annotation/
  7. appcompat/
  8. appsearch/
  9. arch/
  10. asynclayoutinflater/
  11. autofill/
  12. benchmark/
  13. biometric/
  14. browser/
  15. buildSrc/
  16. buildSrc-tests/
  17. busytown/
  18. camera/
  19. cardview/
  20. collection/
  21. compose/
  22. concurrent/
  23. contentaccess/
  24. contentpager/
  25. coordinatorlayout/
  26. core/
  27. cursoradapter/
  28. customview/
  29. datastore/
  30. development/
  31. docs-fake/
  32. docs-runner/
  33. documentfile/
  34. drawerlayout/
  35. dynamic-animation/
  36. emoji/
  37. enterprise/
  38. exifinterface/
  39. fakeannotations/
  40. fragment/
  41. frameworks/
  42. gradle/
  43. gridlayout/
  44. heifwriter/
  45. hilt/
  46. inspection/
  47. interpolator/
  48. ipc/
  49. jetifier/
  50. leanback/
  51. leanback-preference/
  52. legacy/
  53. lifecycle/
  54. lint-checks/
  55. lint-demos/
  56. loader/
  57. localbroadcastmanager/
  58. media/
  59. media2/
  60. mediarouter/
  61. mppsample/
  62. navigation/
  63. paging/
  64. palette/
  65. percentlayout/
  66. placeholder-tests/
  67. playground/
  68. playground-common/
  69. preference/
  70. print/
  71. recommendation/
  72. recyclerview/
  73. remotecallback/
  74. room/
  75. samples/
  76. savedstate/
  77. security/
  78. serialization/
  79. sharetarget/
  80. slices/
  81. slidingpanelayout/
  82. sqlite/
  83. startup/
  84. swiperefreshlayout/
  85. test/
  86. testutils/
  87. textclassifier/
  88. tracing/
  89. transition/
  90. tv-provider/
  91. ui/
  92. vectordrawable/
  93. versionedparcelable/
  94. viewpager/
  95. viewpager2/
  96. wear/
  97. webkit/
  98. window/
  99. work/
  100. .gitignore
  101. .mailmap
  102. build.gradle
  103. cleanBuild.sh
  104. code-review.md
  105. CONTRIBUTING.md
  106. gradle.properties
  107. gradlew
  108. include-composite-deps.gradle
  109. include-support-library.gradle
  110. LICENSE.txt
  111. OWNERS
  112. PREUPLOAD.cfg
  113. README.md
  114. settings.gradle
  115. studiow
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

For contributions via GitHub, see the GitHub Contribution Guide.

Note: The contributions workflow via GitHub is currently experimental - only contributions to Paging, Room and WorkManager are being accepted at this time.

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.

  1. 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
  1. Configure Git with your real name and email address.
git config --global user.name "Your Name"
git config --global user.email "[email protected]"
  1. Create a directory for your checkout (it can be any name)
mkdir androidx-master-dev
cd androidx-master-dev
  1. Use repo command to initialize the repository.
repo init -u https://android.googlesource.com/platform/manifest -b androidx-master-dev --partial-clone
  1. 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 to 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

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

Full Test Package

  1. In the project side panel open the desired module.
  2. Find the directory with the tests
  3. 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.