Searched refs:is (Results 1 – 25 of 181) sorted by relevance
12345678
| /tools/apksig/src/apksigner/java/com/android/apksigner/ |
| D | help_sign.txt | 4 is performed using one or more signers, each represented by an asymmetric key
5 pair and a corresponding certificate. Typically, an APK is signed by just one
12 --in Input APK file to sign. This is an alternative to
14 options. Unless --out is specified, this file will be
18 APK is signed in-place, overwriting the input file.
24 signing using this scheme is enabled based on min and max
29 API Level 24. By default, signing using this scheme is
35 API Level 28. By default, signing using this scheme is
40 "lineage" option to make sure that the app is signed by
45 API Level 30. By default, signing using this scheme is
[all …]
|
| D | help_lineage.txt | 28 This option is required for each signer to be modified in the provided SigningCertificateLineage.
41 used in some situations on the platform even though the APK is now being signed
46 this value is not specified then the option will default to true.
50 no file is needed by KeyStore, which is the case for some
66 A password is required to open a KeyStore.
69 When the same file (including standard input) is used for
73 signer, KeyStore password is read before the key password
74 is read.
76 --key-pass Password with which the private key is protected.
85 If --key-pass is not specified for a KeyStore key, this
[all …]
|
| D | help_rotate.txt | 42 used in some situations on the platform even though the APK is now being signed
47 true or false; if this value is not specified then the option will default to
53 no file is needed by KeyStore, which is the case for some
69 A password is required to open a KeyStore.
72 When the same file (including standard input) is used for
76 signer, KeyStore password is read before the key password
77 is read.
79 --key-pass Password with which the private key is protected.
88 If --key-pass is not specified for a KeyStore key, this
92 If --key-pass is not specified for a private key file key,
[all …]
|
| /tools/external/fat32lib/ |
| D | NOTICE | 7 Everyone is permitted to copy and distribute verbatim copies
8 of this license document, but changing it is not allowed.
10 [This is the first released version of the Lesser GPL. It also counts
15 … your freedom to share and change free software--to make sure the software is free for all its use…
17 …arefully about whether this license or the ordinary General Public License is the better strategy …
27 … is no warranty for the free library. Also, if the library is modified by someone else and passed …
31 …is covered by the ordinary GNU General Public License. This license, the GNU Lesser General Public…
33 When a program is linked with a library, whether statically or using a shared library, the combinat…
37 …rary. A more frequent case is that a free library does the same job as widely used non-free librar…
41 … Lesser General Public License is Less protective of the users' freedom, it does ensure that the u…
[all …]
|
| /tools/apkzlib/src/test/resources/testData/packaging/text-files/ |
| D | rfc2460.txt | 23 and status of this protocol. Distribution of this memo is unlimited.
74 IP version 6 (IPv6) is a new version of the Internet Protocol,
84 addresses. The scalability of multicast routing is improved by
86 of address called an "anycast address" is defined, used to send
104 A new capability is added to enable the labeling of packets
130 to include, is specified in [ICMPv6].
139 host - any node that is not a router. [See Note below].
178 Note: it is possible, though unusual, for a device with multiple
242 is discarded if Hop Limit is decremented to
250 a Routing header is present). See [ADDRARCH]
[all …]
|
| /tools/acloud/internal/proto/ |
| D | internal_config.proto | 10 // distributed under the License is distributed on an "AS IS" BASIS,
31 // [CVD only] The project where stable host image is
35 // [GOLDFISH only] The project where stable host image is
39 // [CHEEPS only] The project where stable host image is
74 // If file is of this type, it will be compressed to avd-system.tar.gz
77 // is greater than 0
82 // this config is valid for.
87 // the home directory if the user is authenticated via Oauth2 method.
88 // The file name by convention usually starts with a dot noting it is
91 // user_agent is a string noting which software it is.
[all …]
|
| /tools/test/connectivity/acts/framework/acts/controllers/buds_lib/dev_utils/proto/google/protobuf/ |
| D | descriptor.proto | 79 // functionality of the descriptors -- the information is needed only by
112 // 0 is reserved for errors.
113 // Order is weird for historical reasons.
141 // 0 is reserved for errors
152 // If type_name is set, this need not be set. If both this and type_name
156 // For message and enum types, this is the name of the type. If the name
157 // starts with a '.', it is fully-qualified. Otherwise, C++-like scoping
163 // For extensions, this is the name of the type being extended. It is
175 // list. This field is a member of that oneof. Extensions of a oneof should
249 // through 99999. It is up to you to ensure that you do not use the
[all …]
|
| /tools/external_updater/ |
| D | README.md | 3 external updater is a tool to automatically updates libraries in external/ .
7 Check updates for a library, or verify METADATA is valid:
35 The most important part in the file is a list of urls.
41 If type of a URL is set to GIT, the URL must be a git upstream
48 IMPORTANT: It is suggested to set up a `upstream-master` branch to
55 If the version is a SHA, the tool will always try to upgrade to the
56 top of upstream. As long as there is any new change upstream, local
61 If the version is not a SHA, the tool will try to parse the version
62 to get a numbered version. Currently the supported version format is:
74 It is suggested to verify all local changes when upgrading. This can
[all …]
|
| /tools/metalava/ |
| D | README.md | 7 Metalava is a metadata generator intended for the Android source tree, used for
20 * Diffing versions of the API and determining whether a newer version is
60 command line. If metalava is dropped into an Android framework build for
87 * Support for an updated signature file format (which is described in FORMAT.md)
101 files. This is vital now that some of these annotations become part of the
106 syntax. Since the goal is to have **all** API elements explicitly state
154 need to be able to figure out which parts of the source code is included in
155 the API and which one is implementation; it is simply handed the filtered API
160 is done for Java files.
175 StringBuilder.setLength(int) was missing from the API signatures since it is a
[all …]
|
| D | FORMAT.md | 14 containing class is final.
16 2. The "new" format, which is described below, and is used in Android Q. This
21 3. This is format v2, but with all nullness annotations replaced by a
38 that we can not just record explicitly what the API contract is, but also
66 Here "2" is the major format version; the .0 allows for compatible minor
141 The above signature line is turned into
152 structure in the signature file. For example, in v1, an interface is called an
153 "abstract interface"; an interface extending another interface is said to
306 @android.annotation.ParameterName (which is hidden). This obviously isn't usable
323 is a compile-incompatible change.
[all …]
|
| D | DOWNLOADING.md | 6 1. Install `repo` (Repo is a tool that makes it easier to download multiple Git repositories at onc…
35 …pository is configured to pull only what you need for building and running Metalava. Download the …
42 … is already working in the `aosp/master` branch, you can use that repo checkout instead. For small…
|
| /tools/repohooks/ |
| D | README.md | 20 Sometimes you might want to bypass the upload checks. While this is **strongly
52 This file is checked in the top of a specific git repository. Stacking them
53 in subdirectories (to try and override parent settings) is not supported.
91 branch. This is typically latest commit in the remote-tracking branch.
95 * `PREUPLOAD_COMMIT`: The commit that is currently being checked.
108 will be repeated for each file automatically. If no string is preceding/attached
148 The key can be any name (as long as the syntax is valid), as can the program
149 that is executed. The key is used as the name of the hook for reporting purposes,
152 Whitespace in the key name is OK!
178 * `clang_format`: Run git-clang-format against the commit. The default style is
[all …]
|
| /tools/asuite/atest-py2/docs/ |
| D | develop_test_runners.md | 11 The test runner class is responsible for test execution. Its primary logic
14 top-level args consumed by atest passed onto the test runner. It is up to the
17 the atest CLI and your test runner's CLI. The reason for this is so that atest
25 First thing to choose is where to put the test runner. This will primarily
27 ```test_runners/``` is the default location.
41 * ```host_env_check()```: Check if host environment is properly setup for the
52 There is a parent helper method (```run```) that should be used to execute the
55 Once the test runner class is created, you'll need to add it in
56 ```test_runner_handler``` so that atest is aware of it. Try-except import the
57 test runner in ```_get_test_runners``` like how ```ExampleTestRunner``` is.
|
| D | developer_workflow.md | 15 Atest is essentially a wrapper around various test runners. Because of
18 and run. Note that the wrapper code is written in python, so we'll be
24 Its job is to translate user inputs into (1) build targets and (2)
29 If your contribution involves any of this functionality, this is the
40 This is the code that actually runs the test. If your change
41 involves how the test is actually run, you'll need to work with this
86 The `testtype/suite/AtestRunner.java` is the most important file in
89 `test_runners/atest_tf_test_runner.py`. This is the file you'll want
104 TradeFed itself is used to run the TradeFed unittests so you'll need
110 command to run an individual test file is:<br>
[all …]
|
| D | develop_test_finders.md | 11 A test finder class holds find methods. A find method is given a string (the
22 If the metadata used to find a test is unlike existing test finder classes,
23 that is the right time to create a new class. Metadata can be anything like
30 First thing to choose is where to put the test finder. This will primarily
32 ```test_finders/``` is the default location.
48 field as a dict. Check out ```ExampleFinder``` to see how the data field is
52 This is used by the class decorator to identify the find methods of the class.
54 Final bit is to add your test finder class to ```test_finder_handler```.
|
| D | atest_structure.md | 4 explain how atest is structured and where the major pieces live and what they
16 Atest is primarily composed of 2 components: [test finders](#test-finders) and
27 Atest will first check the environment is setup and then load up the
29 it). That is a critical piece that atest depends on. Module-info.json contains a
31 compatibility_suite, auto_gen_config, etc) that is used during the test finding
46 The final step is to run the tests which is where the test runners do their job.
49 the ```AtestTradefedTestRunner``` is used to kick off ```hello_world_test```.
55 Here is a list of major files and dirs that are important to point out:
102 # This file is executed by build/envsetup.sh
|
| /tools/asuite/atest/docs/ |
| D | develop_test_runners.md | 11 The test runner class is responsible for test execution. Its primary logic
14 top-level args consumed by atest passed onto the test runner. It is up to the
17 the atest CLI and your test runner's CLI. The reason for this is so that atest
25 First thing to choose is where to put the test runner. This will primarily
27 ```test_runners/``` is the default location.
41 * ```host_env_check()```: Check if host environment is properly setup for the
52 There is a parent helper method (```run```) that should be used to execute the
55 Once the test runner class is created, you'll need to add it in
56 ```test_runner_handler``` so that atest is aware of it. Try-except import the
57 test runner in ```_get_test_runners``` like how ```ExampleTestRunner``` is.
|
| D | developer_workflow.md | 15 Atest is essentially a wrapper around various test runners. Because of
18 and run. Note that the wrapper code is written in python, so we'll be
24 Its job is to translate user inputs into (1) build targets and (2)
29 If your contribution involves any of this functionality, this is the
40 This is the code that actually runs the test. If your change
41 involves how the test is actually run, you'll need to work with this
86 The `testtype/suite/AtestRunner.java` is the most important file in
89 `test_runners/atest_tf_test_runner.py`. This is the file you'll want
104 TradeFed itself is used to run the TradeFed unittests so you'll need
110 command to run an individual test file is:<br>
[all …]
|
| D | develop_test_finders.md | 11 A test finder class holds find methods. A find method is given a string (the
22 If the metadata used to find a test is unlike existing test finder classes,
23 that is the right time to create a new class. Metadata can be anything like
30 First thing to choose is where to put the test finder. This will primarily
32 ```test_finders/``` is the default location.
48 field as a dict. Check out ```ExampleFinder``` to see how the data field is
52 This is used by the class decorator to identify the find methods of the class.
54 Final bit is to add your test finder class to ```test_finder_handler```.
|
| D | atest_structure.md | 4 explain how atest is structured and where the major pieces live and what they
16 Atest is primarily composed of 2 components: [test finders](#test-finders) and
27 Atest will first check the environment is setup and then load up the
29 it). That is a critical piece that atest depends on. Module-info.json contains a
31 compatibility_suite, auto_gen_config, etc) that is used during the test finding
46 The final step is to run the tests which is where the test runners do their job.
49 the ```AtestTradefedTestRunner``` is used to kick off ```hello_world_test```.
55 Here is a list of major files and dirs that are important to point out:
102 # This file is executed by build/envsetup.sh
|
| /tools/test/connectivity/acts/ |
| D | README.md | 2 The Android Comms Test Suite, is a lightweight Python-based automation tool set
3 that is used to perform automated testing of current and upcoming Android
6 of utility functions to further ease test development. It is an ideal desktop
21 it is recommended for all new test cases.
37 Below is a high level view of the ACTS flow:
64 2. Tap Build number repeatedly until "You're a developer now" is displayed.
77 3. To verify ACTS is ready to go, at the location for README, and run:
96 - `act.py`: is the script that runs the test
97 - -c acts_confidence_test_config: is the flag and name of the configuration file
99 - -tc IntegrationTest: is the name of the test case
[all …]
|
| /tools/test/connectivity/acts/framework/acts/controllers/buds_lib/dev_utils/proto/ |
| D | plugin.proto | 33 // WARNING: The plugin interface is currently EXPERIMENTAL and is subject to
36 // protoc (aka the Protocol Compiler) can be extended via plugins. A plugin is
45 // flag "--${NAME}_out" is passed to protoc.
54 // An encoded CodeGeneratorRequest is written to the plugin's stdin.
69 // the fields above, even though this is not technically guaranteed by the
73 // is not similarly optimized on protoc's end -- it will store all fields in
97 // If the name is omitted, the content will be appended to the previous
106 // content here is to be inserted into that file at a defined insertion
114 // an identifier naming the point -- this is what other generators will use
118 // The double-@ is intended to make it unlikely that the generated code
[all …]
|
| /tools/aadevtools/avd/ |
| D | README.md | 2 This is a collection of developer tools to use AAOS AVDs for a better produtivity.
9 * test_avd_avd_image.sh is the test & also examples of how to use it.
11 * avd_img_list.csv is the default CSV file if non is provided & also as an example.
13 * test_create_avd.sh is the test & also examples of how to use it.
16 * test_patch_all_avds.sh is the test & also examples of how to use it.
18 * test_set_avds_force_cold_boot.sh is the test & also examples of how to use it.
|
| /tools/apksig/ |
| D | README.md | 3 apksig is a project which aims to simplify APK signing and checking whether APK signatures are
8 Android Nougat, API Level 24). apksig is meant to be used outside of Android devices.
10 The key feature of apksig is that it knows about differences in APK signature verification logic
12 signature is expected to verify on all Android platform versions supported by the APK. When signing
28 * `ApkVerifier` which checks whether the provided APK is expected to verify on all Android
31 This is useful in optimized APK building pipelines, such as in Android Plugin for Gradle,
33 where the APK to be signed is available upfront, the `ApkSigner` above is easier to use.
|
| /tools/treble/hacksaw/ |
| D | README.md | 5 ## What is Hacksaw?
7 … multiple git projects it can take a long time branch off a clean workspace. Hacksaw is a tool that
11 ## How much faster is it, really?
30 As you can see, the time it takes to set up a new hacksaw workspace is proportional to
108 ## How do I make sure that creating a hacksaw workspace is fast?
130 Hacksawd is a privileged system daemon whose only job is to manage bind mounts.
169 * Failing to create a workspace is not rolled back.
170 * Editing nested projects is not supported yet. So if you have a git project
172 * Git submodules are not supported yet, but the tool is designed with
|
12345678