| /tools/test/connectivity/acts_tests/tests/google/bt/pts/instructions/ |
| D | GAP_PTS_INSTRUCTIONS | 9 # Unless required by applicable law or agreed to in writing, software
17 Note: Use this stack change to test all LE testcases:
18 …rce.com/#/c/319838/1/stack/btm/btm_ble_multi_adv.cc TSPC_bd_addr_iut should be set to 4AF441CF285A.
19 This sets the random address to a static address.
48 [PTS Interaction] Answer NO to non-connectable adv question
138 Note: PTS is very flacky, rerun multiple times to pass.
189 Note: Run the test a first time and it will fail. Change the address to
194 Set PTS IXIT value iut_privacy_enabled to False
199 Enter pin from phone to PTS
200 [PTS Interactoin] OK to disconnect
[all …]
|
| D | HOGP_PTS_INSTRUCTIONS | 9 # Unless required by applicable law or agreed to in writing, software
22 [PTS Interaction] Enter PIN from phone to PTS
30 [PTS Interaction] Enter PIN from phone to PTS
38 [PTS Interaction] Enter PIN from phone to PTS
46 [PTS Interaction] Enter PIN from phone to PTS
55 [PTS Interaction] Enter PIN from phone to PTS
64 [PTS Interaction] Enter PIN from phone to PTS
77 [PTS Interaction] Enter PIN from phone to PTS
86 [PTS Interaction] Enter PIN from phone to PTS
99 [PTS Interaction] Enter PIN from phone to PTS
[all …]
|
| D | SM_PTS_INSTRUCTIONS | 9 # Unless required by applicable law or agreed to in writing, software
48 [Enter Pin from console to PTS]
59 [Enter Pin from console to PTS]
66 [Enter Pin from console to PTS]
73 [Enter Pin from console to PTS]
91 [Enter Pin from console to PTS]
98 [Enter Pin from console to PTS]
105 [Enter Pin from console to PTS]
112 [Enter Pin from console to PTS]
115 Need to be able to send security request via cmd line
[all …]
|
| D | L2CAP_PTS_INSTRUCTIONS | 9 # Unless required by applicable law or agreed to in writing, software
21 [Wait up to 10-15 seconds]
27 [Wait up to 10-15 seconds]
33 [Wait up to 10-15 seconds]
37 [Wait up to 10-15 seconds]
41 [Wait up to 10-15 seconds]
50 [Wait up to 10-15 seconds]
64 [Wait up to 10-15 seconds]
69 [Wait up to 10-15 seconds]
75 [Wait up to 10-15 seconds]
[all …]
|
| /tools/asuite/atest-py2/docs/ |
| D | developer_workflow.md | 3 This document explains the practical steps for contributing code to atest.
16 this division, your first step should be to identify the code
19 referring to it as the "Python Code".
24 Its job is to translate user inputs into (1) build targets and (2)
25 information needed for the test runner to run the test. It then invokes
26 the appropriate test runner code to run the tests. As the tests
28 the user. It uses Test Finder and Test Runner classes to do this work.
30 code you'll want to work on.
41 involves how the test is actually run, you'll need to work with this
56 (path relative to android repo root)
[all …]
|
| D | atest_structure.md | 3 You're here because you'd like to contribute to atest. To start off, we'll
5 do. If you're more interested in how to use atest, go to the [README](../README.md).
28 module-info.json file (and build it if it's not detected or we want to rebuild
32 process. We create the results dir for our test runners to dump results in and
33 proceed to the first juicy part of atest, finding tests.
35 The tests specified by the user are passed into the ```CLITranslator``` to
37 required and optional bits used to run the test as how the user intended.
39 used to run the test. Optional bits would be additional args for the test and
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```.
[all …]
|
| D | develop_test_runners.md | 3 Learn about test runners and how to create a new test runner class.
14 top-level args consumed by atest passed onto the test runner. It is up to the
15 test runner to translate those args into the specific args the test runner
18 can have a consistent CLI for args instead of requiring the users to remember
20 determine its specific dependencies that need to be built prior to any test
25 First thing to choose is where to put the test runner. This will primarily
33 > rules apply, rerun ```build/envsetup.sh``` to update ```$PYTHONPATH```.
37 to see what a simple test runner will look like.
40 You'll need to override the following parent methods:
44 to be built prior to test execution.
[all …]
|
| /tools/asuite/atest/docs/ |
| D | developer_workflow.md | 3 This document explains the practical steps for contributing code to atest.
16 this division, your first step should be to identify the code
19 referring to it as the "Python Code".
24 Its job is to translate user inputs into (1) build targets and (2)
25 information needed for the test runner to run the test. It then invokes
26 the appropriate test runner code to run the tests. As the tests
28 the user. It uses Test Finder and Test Runner classes to do this work.
30 code you'll want to work on.
41 involves how the test is actually run, you'll need to work with this
56 (path relative to android repo root)
[all …]
|
| D | atest_structure.md | 3 You're here because you'd like to contribute to atest. To start off, we'll
5 do. If you're more interested in how to use atest, go to the [README](../README.md).
28 module-info.json file (and build it if it's not detected or we want to rebuild
32 process. We create the results dir for our test runners to dump results in and
33 proceed to the first juicy part of atest, finding tests.
35 The tests specified by the user are passed into the ```CLITranslator``` to
37 required and optional bits used to run the test as how the user intended.
39 used to run the test. Optional bits would be additional args for the test and
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```.
[all …]
|
| /tools/trebuchet/ |
| D | CONTRIBUTING.md | 1 # How to Contribute
3 We'd love to accept your patches and contributions to this project. There are
4 just a few small guidelines you need to follow.
8 Contributions to this project must be accompanied by a Contributor License
9 Agreement. You (or your employer) retain the copyright to your contribution,
10 this simply gives us permission to use and redistribute your contributions as
11 part of the project. Head over to <https://cla.developers.google.com/> to see
12 your current agreements on file or to sign a new one.
14 You generally only need to submit a CLA once, so if you've already submitted one
15 (even if it was for a different project), you probably don't need to do it
|
| D | LICENSE | 19 "control" means (i) the power, direct or indirect, to cause the
28 including but not limited to software source code, documentation
33 not limited to compiled object code, generated documentation,
34 and conversions to other media types.
38 copyright notice that is included in or attached to the work
46 separable from, or merely link (or bind by name) to the interfaces of,
51 to that Work or Derivative Works thereof, that is intentionally
52 submitted to Licensor for inclusion in the Work by the copyright owner
53 or by an individual or Legal Entity authorized to submit on behalf of
56 to the Licensor or its representatives, including but not limited to
[all …]
|
| /tools/test/openhst/docs/ |
| D | contributing.md | 1 # How to Contribute
3 We'd love to accept your patches and contributions to this project. There are
4 just a few small guidelines you need to follow.
8 Contributions to this project must be accompanied by a Contributor License
9 Agreement (CLA). You (or your employer) retain the copyright to your
10 contribution; this simply gives us permission to use and redistribute your
11 contributions as part of the project. Head over to
12 <https://cla.developers.google.com/> to see your current agreements on file or
13 to sign a new one.
15 You generally only need to submit a CLA once, so if you've already submitted one
[all …]
|
| /tools/test/openhst/ |
| D | stress_test.proto | 10 * Unless required by applicable law or agreed to in writing, software
24 // The process name that this event can be found on, or LOGCAT to come from
27 // The name of the event to trigger.
29 // A list of regexes that can be used to detect the specified event.
42 // The regex to extract the string containing the timestamp.
44 // The format string to pass to the python datetime constructor for the
47 // The multiplier used on the parsed monotonic time to convert it to seconds.
52 // The file that should be cat-ed on device to get information. Will be used
55 // The filepath to save the output of this file on the local machine. If
58 // The information needed to extract timestamps from the config.
[all …]
|
| /tools/external/fat32lib/ |
| D | NOTICE | 7 Everyone is permitted to copy and distribute verbatim copies
15 …to take away your freedom to share and change it. By contrast, the GNU General Public Licenses are…
17 …to some specially designated software packages--typically libraries--of the Free Software Foundati…
19 …e, we are referring to freedom of use, not price. Our General Public Licenses are designed to make…
21 …need to make restrictions that forbid distributors to deny you these rights or to ask you to surre…
23 …t provide complete object files to the recipients, so that they can relink them with the library a…
25 …brary, and (2) we offer you this license, which gives you legal permission to copy, distribute and…
27 To protect each distributor, we want to make it very clear that there is no warranty for the free l…
29 Finally, software patents pose a constant threat to the existence of any free program. We wish to m…
31 … to certain designated libraries, and is quite different from the ordinary General Public License.…
[all …]
|
| /tools/ndkports/ |
| D | README.md | 4 tooling to build them.
6 If you're an Android app developer looking to *consume* these libraries, this is
7 probably not what you want. This project builds AARs to be published to Maven.
8 You most likely want to use the AAR, not build it yourself.
16 where to fetch the source, apply any patches needed, build, install, and package
20 Projects define the name and version of the port, the URL to fetch source from,
21 a list of modules (libraries) to build, and the build steps.
32 ndkports requires an NDK to be used for building to be specified on the command
33 line as well as a list of packages to build. For example, to build cURL:
36 $ ./gradlew run --args='--ndk /path/to/android-ndk-r20 openssl curl'
[all …]
|
| /tools/repohooks/ |
| D | README.md | 7 turn on any hook it wishes to enforce.
13 Normally these execute automatically when you run `repo upload`. If you want to
20 Sometimes you might want to bypass the upload checks. While this is **strongly
23 `--no-verify` when running `repo upload` to skip all upload checks. This will
42 Simply check this in to the manifest git repo and you're done.
53 in subdirectories (to try and override parent settings) is not supported.
80 generally be relative to that point.
82 A few environment variables are set so scripts don't need to discover things.
86 * `REPO_PATH`: The path to the project relative to the root.
90 * `REPO_LREV`: The name of the remote revision, translated to a local tracking
[all …]
|
| /tools/apksig/src/apksigner/java/com/android/apksigner/ |
| D | help_rotate.txt | 3 This takes the provided keys and creates a SigningCertificateLineage entry linking the old to the
12 to rotate the signing certificate for an APK.
16 --out File into which to put the binary representation of a
27 --old-signer The signing information for the signer from which to be rotated. This will
28 be used to sign a new entry in the SigningCertificateLineage allowing the
33 --new-signer The signing information for the signer to which you want to rotate. This will
37 There are two ways to provide the signer's private key and certificate: (1) Java
41 The --set-xx capability options allow an older signing certificate to still be
45 during rotation to act as a default level of trust when moving to a newer
47 true or false; if this value is not specified then the option will default to
[all …]
|
| D | help_lineage.txt | 4 This can be used to revoke capabilities of a previous signing certificate once the install base
5 has been migrated to the new signing certificate.
16 --out File into which to put the binary representation of a
28 This option is required for each signer to be modified in the provided SigningCertificateLineage.
30 --signer Indicates the start of a new signing certificate to be modified.
35 private key and certificate must be specified. There are two ways to provide
40 The --set-xx capability options allow an older signing certificate to still be
44 to act as a default level of trust when moving to a newer signing certificate.
46 this value is not specified then the option will default to true.
66 A password is required to open a KeyStore.
[all …]
|
| /tools/apkzlib/src/test/resources/testData/packaging/text-files/ |
| D | rfc2460.txt | 21 improvements. Please refer to the current edition of the "Internet
32 also sometimes referred to as IP Next Generation or IPng.
54 8.4 Responding to Packets Carrying Routing Headers..........29
75 designed as the successor to IP version 4 (IPv4) [RFC-791]. The
76 changes from IPv4 to IPv6 fall primarily into the following
81 IPv6 increases the IP address size from 32 bits to 128 bits, to
85 adding a "scope" field to multicast addresses. And a new type
86 of address called an "anycast address" is defined, used to send
87 a packet to any one of a group of nodes.
91 Some IPv4 header fields have been dropped or made optional, to
[all …]
|
| /tools/treble/split/ |
| D | README.md | 6 projects necessary to build a given target. If a project isn't used for building
8 used to sync the Android source tree and build the specific target. This sync
12 The `treble_manifest_split` tool is used to automatically create a split
14 and the build outputs. The tool attempts to infer as many dependencies as it
15 can, but some will be missed due to implicit dependencies in the build system
17 specific to your target.
24 completed build in order to have a full view of the dependency graph. While the
28 Use standard Android build commands to build your target.
33 # Change to the directory where you ran the full build.
34 cd /path/to/android
[all …]
|
| /tools/test/connectivity/acts/framework/acts/controllers/buds_lib/dev_utils/proto/google/protobuf/ |
| D | descriptor.proto | 16 // contributors may be used to endorse or promote products derived from
36 // A valid .proto file can be translated directly to a FileDescriptorProto
58 optional string name = 1; // file name, relative to root of source tree
158 // rules are used to find the type (i.e. first the nested types within this
159 // message are searched, then within the parent, on up to the root
176 // not set this since the oneof to which they belong will be inferred based
218 // FieldDescriptorProto.type_name, but must refer to a message type.
235 // just annotations which may cause code to be generated slightly differently
242 // across all *Options messages. We then use this field to populate the
249 // through 99999. It is up to you to ensure that you do not use the
[all …]
|
| /tools/acloud/ |
| D | README.md | 5 Acloud is a command line tool that assists users to create an Android Virtual
15 Add acloud to your $PATH by lunching your environment.
30 You should now be able to call acloud from anywhere.
51 (running on your local host) use cases. You also have the option to use
62 * Remote instance using a locally built image (use `m` to build the image)
71 * Local instance using a locally built image (use `m` to build the image)
82 * `--build-target`: Defaults to the phone target for cuttlefish (e.g.
85 * `--build-id`: Default to the Last Known Good Build (LKGB) id for the branch and
91 This will be used to choose the default hw properties and infer build target
94 * `--autoconnect`: This defaults to true and upon creation of a remote instance,
[all …]
|
| D | LICENSE | 19 "control" means (i) the power, direct or indirect, to cause the
28 including but not limited to software source code, documentation
33 not limited to compiled object code, generated documentation,
34 and conversions to other media types.
38 copyright notice that is included in or attached to the work
46 separable from, or merely link (or bind by name) to the interfaces of,
51 to that Work or Derivative Works thereof, that is intentionally
52 submitted to Licensor for inclusion in the Work by the copyright owner
53 or by an individual or Legal Entity authorized to submit on behalf of
56 to the Licensor or its representatives, including but not limited to
[all …]
|
| /tools/apksig/ |
| D | LICENSE | 7 Unless required by applicable law or agreed to in writing, software
31 "control" means (i) the power, direct or indirect, to cause the
40 including but not limited to software source code, documentation
45 not limited to compiled object code, generated documentation,
46 and conversions to other media types.
50 copyright notice that is included in or attached to the work
58 separable from, or merely link (or bind by name) to the interfaces of,
63 to that Work or Derivative Works thereof, that is intentionally
64 submitted to Licensor for inclusion in the Work by the copyright owner
65 or by an individual or Legal Entity authorized to submit on behalf of
[all …]
|
| /tools/treble/ |
| D | LICENSE | 19 "control" means (i) the power, direct or indirect, to cause the
28 including but not limited to software source code, documentation
33 not limited to compiled object code, generated documentation,
34 and conversions to other media types.
38 copyright notice that is included in or attached to the work
46 separable from, or merely link (or bind by name) to the interfaces of,
51 to that Work or Derivative Works thereof, that is intentionally
52 submitted to Licensor for inclusion in the Work by the copyright owner
53 or by an individual or Legal Entity authorized to submit on behalf of
56 to the Licensor or its representatives, including but not limited to
[all …]
|