| /tools/tradefederation/core/atest/docs/ |
| D | developer_workflow.md | 6 1. [Identify the code you should work on](#identify-the-code-you-should-work-on)
7 2. [Working on the Python Code](#working-on-the-python-code)
8 3. [Working on the TradeFed Code](#working-on-the-tradefed-code)
9 4. [Working on the VTS10-TradeFed Code](#working-on-the-vts10-tradefed-code)
10 5. [Working on the Robolectric Code](#working-on-the-robolectric-code)
13 ## <a name="what-code">Identify the code you should work on</a>
30 code you'll want to work on.
32 <p>For more details on how this code works, checkout the following docs:
51 ## <a name="working-on-the-python-code">Working on the Python Code</a>
78 ## <a name="working-on-the-tradefed-code">Working on the TradeFed Code</a>
[all …]
|
| D | atest_structure.md | 19 2. Find test(s) based on user input
29 it). That is a critical piece that atest depends on. Module-info.json contains a
51 Read on to learn more about the classes mentioned.
62 * ```test_finders/``` - Location of test finder classes. More details on test
68 * ```test_runners/``` - Location of test runner classes. More details on test
76 atest to find tests in the android repo based on the user's input (path,
81 For more details and instructions on how to create new test finders,
89 For more details and instructions on how to create new test runners, [go here](./develop_test_runne…
|
| /tools/asuite/atest/docs/ |
| D | developer_workflow.md | 6 1. [Identify the code you should work on](#identify-the-code-you-should-work-on)
7 2. [Working on the Python Code](#working-on-the-python-code)
8 3. [Working on the TradeFed Code](#working-on-the-tradefed-code)
9 4. [Working on the VTS10-TradeFed Code](#working-on-the-vts10-tradefed-code)
10 5. [Working on the Robolectric Code](#working-on-the-robolectric-code)
13 ## <a name="what-code">Identify the code you should work on</a>
30 code you'll want to work on.
32 <p>For more details on how this code works, checkout the following docs:
51 ## <a name="working-on-the-python-code">Working on the Python Code</a>
78 ## <a name="working-on-the-tradefed-code">Working on the TradeFed Code</a>
[all …]
|
| D | atest_structure.md | 19 2. Find test(s) based on user input
29 it). That is a critical piece that atest depends on. Module-info.json contains a
51 Read on to learn more about the classes mentioned.
62 * ```test_finders/``` - Location of test finder classes. More details on test
68 * ```test_runners/``` - Location of test runner classes. More details on test
76 atest to find tests in the android repo based on the user's input (path,
81 For more details and instructions on how to create new test finders,
89 For more details and instructions on how to create new test runners, [go here](./develop_test_runne…
|
| /tools/external/fat32lib/ |
| D | NOTICE | 17 …Public License is the better strategy to use in any particular case, based on the explanations bel…
27 … free library. Also, if the library is modified by someone else and passed on, the recipients shou…
37 For example, on rare occasions, there may be a special need to encourage the widest possible use of…
43 …cation follow. Pay close attention to the difference between a "work based on the library" and a "…
51 …ibrary or work which has been distributed under these terms. A "work based on the Library" means e…
55 …titute a work based on the Library (independent of the use of the Library in a tool for writing it…
57 …, in any medium, provided that you conspicuously and appropriately publish on each copy an appropr…
61 …y or copies of the Library or any portion of it, thus forming a work based on the Library, and cop…
69 …ctions as part of a whole which is a work based on the Library, the distribution of the whole must…
71 …rcise the right to control the distribution of derivative or collective works based on the Library.
[all …]
|
| /tools/apksig/src/apksigner/java/com/android/apksigner/ |
| D | help_sign.txt | 24 signing using this scheme is enabled based on min and max
30 enabled based on min and max SDK version (see
36 enabled based on min and max SDK version (see
41 an appropriate signer on all supported platform versions.
43 --min-sdk-version Lowest API Level on which this APK's signatures will be
48 --max-sdk-version Highest API Level on which this APK's signatures will be
73 points in the lineage and will be used on older platform
115 stdin password provided on standard input,
134 stdin password provided on standard input,
157 form encoded using the JVM default charset, and, on Java 8
[all …]
|
| D | help_verify.txt | 3 This checks whether the provided APK will verify on Android. By default, this
4 checks whether the APK will verify on all Android platform versions supported
16 --min-sdk-version Lowest API Level on which this APK's signatures will be
20 --max-sdk-version Highest API Level on which this APK's signatures will be
33 1. Check whether the APK's signatures are expected to verify on all Android
37 2. Check whether the APK's signatures are expected to verify on Android
|
| D | help_rotate.txt | 42 used in some situations on the platform even though the APK is now being signed
67 stdin password provided on standard input,
86 stdin password provided on standard input,
109 form encoded using the JVM default charset, and, on Java 8
114 to be provided for a KeyStore created by keytool on a
127 provider is chosen based on --ks-provider-name.
145 upgrade on-device. Without it, the platform will not
182 on the command-line.
|
| D | help_lineage.txt | 41 used in some situations on the platform even though the APK is now being signed
64 stdin password provided on standard input,
83 stdin password provided on standard input,
106 form encoded using the JVM default charset, and, on Java 8
111 to be provided for a KeyStore created by keytool on a
124 provider is chosen based on --ks-provider-name.
142 upgrade on-device. Without it, the platform will not
|
| /tools/test/connectivity/acts_tests/tests/google/bt/pts/instructions/ |
| D | GAP_PTS_INSTRUCTIONS | 10 # distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
198 Note: Do not accept pairing on phone until after you accept it on PTS
228 Note: Do not accept pairing on phone until after you accept it on PTS
242 [PTS Interaction] Enter PIN from PTS to phone (hit ok on phone before PTSbt )
275 Do not accept pairing on phone until after you accept it on PTS
311 Note: Do not accept pairing on phone until after you accept it on PTS
371 Accept Pairing on Phone (check contacts box)
384 [PTS Interaction] Select ok on PTS
529 Note: Run these commands before executing the testcase on PTS Side
537 Note: Run these commands before executing the testcase on PTS Side
[all …]
|
| /tools/metalava/ |
| D | README.md | 59 flags and translates them on the fly. Flags that are ignored are listed on the
105 * Support for a "compact" nullness format -- one based on Kotlin's
140 message running metalava on master: Enhancing docs:
152 javadoc or [Dokka](https://github.com/Kotlin/dokka) on the stubs files instead
166 but not versa). It also lets you diff directly on a source tree; it does not
184 checks on the public API in the codebase and flag issues that are discouraged
188 inside method bodies to see if you're synchronizing on this or the current
213 in a targeted way. For example, running the analysis on the current version of
274 * Built on top of a full, type-resolved AST. Doclava1 was integrated with
293 API usage. (Prior to this, this was based on signature file parsing in
[all …]
|
| /tools/test/connectivity/acts/framework/acts/controllers/buds_lib/dev_utils/proto/google/protobuf/ |
| D | descriptor.proto | 32 // Based on original Protocol Buffers design by
159 // message are searched, then within the parent, on up to the root
177 // on the extension range containing the extension's field number.
295 // the generated methods compute their results based on field values rather
305 // This option has no effect on when used with the lite runtime.
335 // these default to false. Old code which depends on generic services should
342 // Depending on the target platform, this can emit Deprecated annotations
387 // Depending on the target platform, this can emit Deprecated annotations
437 // a more efficient representation on the wire. Rather than repeatedly
452 // using lazy parsing on this field is worth the additional bookkeeping
[all …]
|
| /tools/repohooks/ |
| D | README.md | 4 perform various checks automatically such as running linters on your code.
7 turn on any hook it wishes to enforce.
33 the local project you're working on.
48 settings on top.
105 * `${PREUPLOAD_FILES}`: List of files to operate on.
106 * `${PREUPLOAD_FILES_PREFIXED}`: A list of files to operate on.
141 * `ignore_merged_commits`: If set to `true`, the hooks will not run on commits
142 that are merged. Hooks will still run on the merge commit itself.
146 This section allows for completely arbitrary hooks to run on a per-repo basis.
170 This section allows for turning on common/builtin hooks. There are a bunch of
[all …]
|
| /tools/test/connectivity/acts/framework/acts/test_utils/gnss/ |
| D | gnss_testlog_utils.py | 286 lambda item1, item2: pds.merge(item1, item2, on='time_row_num'), [
293 on='time_row_num')
299 lambda item1, item2: pds.merge(item1, item2, on='time_row_num'), [
306 on='time_row_num')
372 lambda item1, item2: pds.merge(item1, item2, on='phone_time'),
377 on='phone_time')
383 lambda item1, item2: pds.merge(item1, item2, on='phone_time'),
388 on='phone_time')
393 lambda item1, item2: pds.merge(item1, item2, on='phone_time'),
398 on='phone_time')
|
| /tools/apkzlib/src/test/resources/testData/packaging/text-files/ |
| D | rfc2460.txt | 98 more efficient forwarding, less stringent limits on the length
127 the effects of IPv6 on upper-layer protocols. The format and
324 There, normal demultiplexing on the Next Header field of the IPv6
363 octet fields within each extension header are aligned on their
530 ensure that multi-octet values within Option Data fields fall on
626 intermediate nodes to be "visited" on the way to a packet's
666 of the node depends on the value of the Segments Left field, as
797 transmission; ignored on reception.
807 In that node, dispatching on the Next Header field of the immediately
907 Routing header fields on each segment of the delivery path would be
[all …]
|
| /tools/apksig/ |
| D | LICENSE | 8 distributed under the License is distributed on an "AS IS" BASIS,
54 form, that is based on (or derived from) the Work and for which the
65 or by an individual or Legal Entity authorized to submit on behalf of
69 communication on electronic mailing lists, source code control systems,
70 and issue tracking systems that are managed by, or on behalf of, the
76 on behalf of whom a Contribution has been received by Licensor and
158 Contributor provides its Contributions) on an "AS IS" BASIS,
183 on Your own behalf and on Your sole responsibility, not on behalf
198 file or class name and description of purpose be included on the
211 distributed under the License is distributed on an "AS IS" BASIS,
|
| D | README.md | 4 expected to verify on Android. apksig supports
12 signature is expected to verify on all Android platform versions supported by the APK. When signing
13 an APK, apksig chooses the most appropriate cryptographic algorithms based on the Android platform
19 * apksigner -- a pure Java command-line tool based on the apksig library.
26 * `ApkSigner` which signs the provided APK so that it verifies on all Android platform versions
28 * `ApkVerifier` which checks whether the provided APK is expected to verify on all Android
44 * sign the provided APK so that it verifies on all Android platforms supported by the APK. Run
46 * check whether the provided APK's signatures are expected to verify on all Android platforms
51 of platform versions on the command-line.
|
| /tools/acloud/ |
| D | LICENSE | 42 form, that is based on (or derived from) the Work and for which the
53 or by an individual or Legal Entity authorized to submit on behalf of
57 communication on electronic mailing lists, source code control systems,
58 and issue tracking systems that are managed by, or on behalf of, the
64 on behalf of whom a Contribution has been received by Licensor and
146 Contributor provides its Contributions) on an "AS IS" BASIS,
171 on Your own behalf and on Your sole responsibility, not on behalf
186 file or class name and description of purpose be included on the
199 distributed under the License is distributed on an "AS IS" BASIS,
|
| /tools/test/openhst/ |
| D | LICENSE | 42 form, that is based on (or derived from) the Work and for which the
53 or by an individual or Legal Entity authorized to submit on behalf of
57 communication on electronic mailing lists, source code control systems,
58 and issue tracking systems that are managed by, or on behalf of, the
64 on behalf of whom a Contribution has been received by Licensor and
146 Contributor provides its Contributions) on an "AS IS" BASIS,
171 on Your own behalf and on Your sole responsibility, not on behalf
186 file or class name and description of purpose be included on the
199 distributed under the License is distributed on an "AS IS" BASIS,
|
| D | stress_test.proto | 11 * distributed under the License is distributed on an "AS IS" BASIS,
24 // The process name that this event can be found on, or LOGCAT to come from
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
70 // The filepath to save the output of this process on the local machine. If
96 // on the name), only the "latest" in the include chain will be used.
116 // Command to run on this test step.
155 // Events that trigger special actions on the device when the condition is
|
| D | README.md | 4 performance on Android devices with simple test set up. The goal of OpenHST is
6 Partners can easily adapt on their development.
17 * DSP hotword capability on test device (android handset)
19 * Internet connection on android handset
20 * No screen lock setting on android handset
23 * Install GNU make(3.81 above) on test machine (Linux, Mac, Windows)
27 Please follow below steps to set up HST on your test machine and make sure that
|
| /tools/treble/ |
| D | LICENSE | 42 form, that is based on (or derived from) the Work and for which the
53 or by an individual or Legal Entity authorized to submit on behalf of
57 communication on electronic mailing lists, source code control systems,
58 and issue tracking systems that are managed by, or on behalf of, the
64 on behalf of whom a Contribution has been received by Licensor and
146 Contributor provides its Contributions) on an "AS IS" BASIS,
171 on Your own behalf and on Your sole responsibility, not on behalf
186 file or class name and description of purpose be included on the
199 distributed under the License is distributed on an "AS IS" BASIS,
|
| /tools/trebuchet/ |
| D | LICENSE | 42 form, that is based on (or derived from) the Work and for which the
53 or by an individual or Legal Entity authorized to submit on behalf of
57 communication on electronic mailing lists, source code control systems,
58 and issue tracking systems that are managed by, or on behalf of, the
64 on behalf of whom a Contribution has been received by Licensor and
146 Contributor provides its Contributions) on an "AS IS" BASIS,
171 on Your own behalf and on Your sole responsibility, not on behalf
186 file or class name and description of purpose be included on the
199 distributed under the License is distributed on an "AS IS" BASIS,
|
| /tools/security/sanitizer-status/ |
| D | NOTICE | 8 distributed under the License is distributed on an "AS IS" BASIS,
54 form, that is based on (or derived from) the Work and for which the
65 or by an individual or Legal Entity authorized to submit on behalf of
69 communication on electronic mailing lists, source code control systems,
70 and issue tracking systems that are managed by, or on behalf of, the
76 on behalf of whom a Contribution has been received by Licensor and
158 Contributor provides its Contributions) on an "AS IS" BASIS,
183 on Your own behalf and on Your sole responsibility, not on behalf
|
| /tools/test/connectivity/acts_tests/tests/google/fuchsia/bt/pts/ |
| D | GATT_PTS_INSTRUCTIONS | 10 # distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
73 [Fuchsia interaction] Type 'y' on the bt-pairing-tool
96 [Fuchsia interaction] Type 'y' on the bt-pairing-tool
119 [Fuchsia interaction] Type 'y' on the bt-pairing-tool
162 [Fuchsia interaction] Type 'y' on the bt-pairing-tool
194 Fuchsia interaction] Type 'y' on the bt-pairing-tool
|