commit | 0ecb70d37c6d0a9c19a2f0c9b289c1d063f9bcf3 | [log] [tgz] |
---|---|---|
author | Chris Craik <ccraik@google.com> | Tue Mar 22 15:55:15 2022 -0700 |
committer | Chris Craik <ccraik@google.com> | Wed Mar 23 16:32:56 2022 -0700 |
tree | 240e50faa19e55d50e14e82bb52b1acf18292350 | |
parent | dbf1b6e8210555d48c093791c7011ac55bf01727 [diff] |
Switch to dumpsys gfxinfo framestats for detecting launch completion Fixes: 226179160 Relnote: Overhaul activity launch completion detection to fix 'Unable to read any metrics' exception in startup macrobenchmarks. Test: TrivialStartupBenchmark Test: MacrobenchmarkScopeTest#getFrameStats (verified on 23,26,27,28,29) There are two remaining possible problems that could be causing the "Unable to read any metrics" exception in startup benchmarks (when the process is named correctly in the trace, and end of trace marker is present): 1) `am start -w` doesn't actually wait for first frame to finish rendering 2) activity isn't actually launched / rendered (unlikely, though we've seen this in very specific scenarios in CI) This change is expected to solve problem 1). `am start -w` has been historically flakey, and extremely hard to narrow down problem scenarios, so this CL uses framestats as a 'backup' method to verify launch completion. We now only consider a launch to be complete when the data for the corresponding first frame shows up in framestats dump command. Fortunately, framestats is available back to API 23, the min api of macrobench, though the "flag" column (which we want to use to detect launch frames) is unreliable pre API 29 (in both local and CI testing). Change-Id: Ia517c59c07d9c24e4471e86fb603dca56a6f855f
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.
For contributions via GitHub, see the GitHub Contribution Guide.
Note: The contributions workflow via GitHub is currently experimental - only contributions to the following projects are being accepted at this time:
When contributing to Jetpack, follow the code review etiquette.
We are not currently accepting new modules.
NOTE: You will need to use Linux or Mac OS. Building under Windows is not currently supported.
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
git config --global user.name "Your Name" git config --global user.email "you@example.com"
mkdir androidx-main cd androidx-main
repo
command to initialize the repository.repo init -u https://android.googlesource.com/platform/manifest -b androidx-main --partial-clone --clone-filter=blob:limit=10M
repo sync -j8 -c
You will use this command to sync your checkout in the future - it’s similar to git fetch
To open the project with the specific version of Android Studio recommended for developing:
cd path/to/checkout/frameworks/support/ ANDROIDX_PROJECTS=MAIN ./gradlew studio
and accept the license agreement when prompted. Now you're ready to edit, run, and test!
You can also the following sets of projects: ALL
, MAIN
, COMPOSE
, or FLAN
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
.
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
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/' }
NOTE: In order to see your changes in the project, you might need to clean your build (Build > Clean Project
in Android Studio or run ./gradlew clean
).
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.
Run FooBarTest
Run androidx.foobar
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.
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
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.
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.