| commit | a266d71d544ad51fc75a23917a215a8e3929fd58 | [log] [tgz] |
|---|---|---|
| author | Marcello Albano <[email protected]> | Fri May 10 10:02:48 2024 -0700 |
| committer | Marcello Albano <[email protected]> | Mon Oct 21 10:04:43 2024 -0700 |
| tree | aa047d183e8e2bc1dd496c7cd061a6a8d1129f17 | |
| parent | 67669211dad613daadcf5d54b1339907c34bf6a4 [diff] |
Fix baseline profiles and benchmarks on android multiuser Benchmark and Baseline profile generation require transfering files between storage accessible by shell and storage accessible by the user. Shell runs on user 0. When the android selected user is also zero, shell can see both storages. When the android selected user is not zero, shell cannot see user storage. As a result we cannot invoke shell commands operating in user storage to copy and move files. Instead we need to utilize the running instrumentation process to access user storage and shell to access shell storage. In order to communicate between these two, the class VirtualFile implements a number of methods to copy streams between the two. When in shell storage we can use commands like `cat` and `cp` from `/dev/stdin` to a file to write. When in user storage we use the java api of the running process. Test: Added and manually. Note we'll need to enable multiuser devices in CI. Bug: 356684617 Bug: 373641155 Relnote: (Experimental) Enable Baseline Profile generation, and benchmarking on apps installed to a secondary user, such as all apps on headless Android Auto devices. This support has been tested in some scenarios, but let us know with a bug if it doesn't work for you. Change-Id: I9fcbecf2a9c9075d161de69118c443d7a37102c0
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.
