| commit | a711fdad0b3cc17f35804c34301fbf623d36e4fc | [log] [tgz] |
|---|---|---|
| author | Ankit <[email protected]> | Sun Feb 04 11:57:31 2024 +0000 |
| committer | Ankit <[email protected]> | Sun Feb 04 12:09:53 2024 +0000 |
| tree | 0fa2337fd7d54efff3e535dd70bdb8a362313de2 | |
| parent | 77e91f44cbb35429a0e5f0291dfca89068562351 [diff] |
Disable charging experience for wear macrobenchmarks This is an experiment to see if disabling the charging experience fixes the flakiness of wear macro benchmarks. As of now, wear macrobenchmarks are failing for r11 targets because the charging screen takes over the display and components required for macro benchmark tests are no longer present during the test. Although it is difficult to see if making this change really helps with the flakiness in the continuous integration, if this succeeds, the next step would be to move this to a different common place. If this does not work, we may need to go back and see what else needs to be done to fix the flakiness. Bug: 189952249 Test: Existing tests Change-Id: I75559e1c615da94d02ab69c7cb0b96ab64e338cc
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.
Head over to the onboarding docs to learn more about getting set up and the development workflow!
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.
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
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(), or mavenCentral(). We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.
