Home
last modified time | relevance | path

Searched refs:to (Results 1 – 25 of 2849) sorted by relevance

12345678910>>...114

/cts/tests/tests/hardware/src/android/hardware/input/cts/tests/
DREADME.md1 How to add a test for a new HID device
4 1. Connect the device of interest to Android
6 3. Go to /sys/kernel/debug/hid/0005:0B05:4500.000F
8 Just print the /sys/kernel/debug/hid directory to see what it is for you.
9 This identifier will also change each time you reconnect the same physical device to Android.
15 To observe the MotionEvents that Android receives in response to the hid reports, write a small
17 There, print all of the event data that has changed. For MotionEvents, ensure to look at the
/cts/hostsidetests/appsecurity/res/pkgsigverify/
DREADME.txt13 OID-params: PKI object identifiers indicating how to use the provided key
14 to generate the signature. See, e.g. rfc3279 and rfc4055.
16 extra_info: additional notes to distinguish packages. Currently this denotes
17 which test certificates were used to generate a proof-of-rotation object,
19 capabilities of those certificates according to APK Signature Scheme v3.
23 android source tree. Please refer to the usage instructions there for how to
26 README in tools/apksig/) to create invalid or unsupported outcomes.
/cts/hostsidetests/sustainedperf/dhrystone/
DLICENSE.TXT18 Permission is hereby granted, free of charge, to any person obtaining a copy of
19 this software and associated documentation files (the "Software"), to deal with
20 the Software without restriction, including without limitation the rights to
22 of the Software, and to permit persons to whom the Software is furnished to do
23 so, subject to the following conditions:
33 Urbana-Champaign, nor the names of its contributors may be used to
51 to that code.
54 applies to all code in the LLVM Distribution, and nothing in any of the
55 other licenses gives permission to use the names of the LLVM Team or the
56 University of Illinois to endorse or promote products derived from this
DRationale15 satisfies a need for an easy-to-use integer benchmark; it gives a first
19 With the increasing use of the benchmark, it seems necessary to
20 reconsider the benchmark and to check whether it can still fulfill this
43 o As far as it is possible without changes to the Dhrystone statistics,
47 removal" or "dead variable elimination"). This has lead to the
58 know some suggestions for improvement, I didn't want to change the
61 outweight the benefits. If I were to write a new benchmark program, I
65 always be encouraged to use more than just one benchmark.
71 Readers who want to use the benchmark for their own measurements can
87 outside the measaurement loop. As a concession to older compilers,
[all …]
/cts/hostsidetests/theme/
DREADME9 * Unless required by applicable law or agreed to in writing, software
21 theme tests, a device must be able to generate images that are identical to the
25 modifications to the reference images will invalidate the test results.
38 export ANDROID_SDK_ROOT = /path/to/sdk
44 3. Use the SDK's AVD Manager tool to create a single virtual device using the
52 5. Use the reference image script to generate the reference images. The script
66 2. Use the reference image script to generate the reference images:
70 There is an option to build locally an Android system image and use an emulator that is stored in
72 require a SDK and can be used to generate images with locally modified source code: for example
79 2. Use the reference image script to generate the reference images. The script
[all …]
/cts/tools/dasm/src/dasm/
DDasmCatchBuilder.java46 String to; field in DasmCatchBuilder.UnprocessedCatch
62 UnprocessedCatch(String exception, String from, String to, in UnprocessedCatch() argument
65 this.to = to; in UnprocessedCatch()
154 if (uc.to.compareToIgnoreCase(end) != 0) in add()
159 + ") and different end addresses (" + uc.to in add()
184 lte = labels_table.get(uc.to); in build()
186 throw new RuntimeException("Label " + uc.to + " not defined"); in build()
187 CodeAddress to = lte.code_address; in build() local
214 CatchTable.Entry entry = new CatchTable.Entry(from.getAddress(), to in build()
/cts/apps/CameraITS/build/scripts/
Dgpylint_rcfile3 # Only show warnings with the listed confidence levels. Leave empty to show
10 # file where it should appear only once).You can also use "--disable=all" to
12 # you want to run only the similarities checker, you can use "--disable=all
13 # --enable=similarities". If you want to run only the classes checker, but have
35 # The configuration modes to activate (default: base).
38 # The mode to use when import path setup fails (default: style).
50 # The configuration mode to use for tests (default: test).
56 # Directories to add to sys.path.
68 # Add a comment according to your evaluation note. This is used by the global
73 # note). You have access to the variables errors warning, statement which
[all …]
/cts/tests/tests/icu/resources/android/icu/cts/expectations/
Dicu-known-failures.txt2 * This file contains expectations for tests that are known to fail.
5 // Uncomment this to exclude all tests and then add result: "SUCCESS" to any specific tests that
6 // need to be run.
14 description: "Serialized forms have not been converted to use repackaged classes",
/cts/tests/libcore/wycheproof/
DOWNERS1 # NOTE: Each source root in CTS should have an OWNERS file as a reminder to
2 # add owners to it. It's okay for this file to be empty because the parent
/cts/tests/libcore/wycheproof-bc/
DOWNERS1 # NOTE: Each source root in CTS should have an OWNERS file as a reminder to
2 # add owners to it. It's okay for this file to be empty because the parent
/cts/tests/libcore/jsr166/
DOWNERS1 # NOTE: Each source root in CTS should have an OWNERS file as a reminder to
2 # add owners to it. It's okay for this file to be empty because the parent
/cts/tests/libcore/okhttp/
DOWNERS1 # NOTE: Each source root in CTS should have an OWNERS file as a reminder to
2 # add owners to it. It's okay for this file to be empty because the parent
/cts/tests/libcore/runner/
DOWNERS1 # NOTE: Each source root in CTS should have an OWNERS file as a reminder to
2 # add owners to it. It's okay for this file to be empty because the parent
/cts/tests/libcore/ojluni/
DOWNERS1 # NOTE: Each source root in CTS should have an OWNERS file as a reminder to
2 # add owners to it. It's okay for this file to be empty because the parent
/cts/tests/libcore/luni/
DOWNERS1 # NOTE: Each source root in CTS should have an OWNERS file as a reminder to
2 # add owners to it. It's okay for this file to be empty because the parent
/cts/hostsidetests/rollback/app/src/com/android/cts/rollback/host/app/
DHostTestHelper.java95 Rollback.from(TestApp.A2).to(TestApp.A1)); in testApkOnlyCommitRollback()
103 Rollback.from(TestApp.A2).to(TestApp.A1)); in testApkOnlyCommitRollback()
127 Rollback.from(TestApp.A2).to(TestApp.A1)); in testApkOnlyConfirmRollback()
172 Rollback.from(TestApp.Apex3).to(TestApp.Apex2)); in testApexOnlyCommitRollback()
179 Rollback.from(TestApp.Apex3).to(TestApp.Apex2)); in testApexOnlyCommitRollback()
250 Rollback.from(TestApp.Apex3).to(TestApp.Apex2), in testApexAndApkCommitRollback()
251 Rollback.from(TestApp.A2).to(TestApp.A1)); in testApexAndApkCommitRollback()
258 Rollback.from(TestApp.Apex3).to(TestApp.Apex2), in testApexAndApkCommitRollback()
259 Rollback.from(TestApp.A2).to(TestApp.A1)); in testApexAndApkCommitRollback()
284 Rollback.from(TestApp.Apex3).to(TestApp.Apex2), in testApexAndApkConfirmRollback()
[all …]
/cts/
DAndroid.bp5 // Set of error prone rules to ensure code quality
34 // Set of error prone rules to ensure code quality of tests
35 // Goal is to eventually merge with cts_error_prone_rules
53 // Used with an android_test / android_test_helper_app, this is equivalent to
66 // Used with different module types, this is equivalent to:
/cts/hostsidetests/jvmti/run-tests/test-1939/app/
DOWNERS1 # DO NOT DELETE: OWNERS is intended to be empty as module owner and bug component are defined
3 # need to tell the difference between "no owner is specified for this module" vs "explicitly
4 # defer to parent OWNERS file"
/cts/hostsidetests/jvmti/run-tests/test-1901/app/
DOWNERS1 # DO NOT DELETE: OWNERS is intended to be empty as module owner and bug component are defined
3 # need to tell the difference between "no owner is specified for this module" vs "explicitly
4 # defer to parent OWNERS file"
/cts/hostsidetests/jvmti/run-tests/test-928/app/
DOWNERS1 # DO NOT DELETE: OWNERS is intended to be empty as module owner and bug component are defined
3 # need to tell the difference between "no owner is specified for this module" vs "explicitly
4 # defer to parent OWNERS file"
/cts/hostsidetests/jvmti/run-tests/test-1912/app/
DOWNERS1 # DO NOT DELETE: OWNERS is intended to be empty as module owner and bug component are defined
3 # need to tell the difference between "no owner is specified for this module" vs "explicitly
4 # defer to parent OWNERS file"
/cts/hostsidetests/jvmti/run-tests/test-1903/
DOWNERS1 # DO NOT DELETE: OWNERS is intended to be empty as module owner and bug component are defined
3 # need to tell the difference between "no owner is specified for this module" vs "explicitly
4 # defer to parent OWNERS file"
/cts/hostsidetests/jvmti/run-tests/test-951/app/
DOWNERS1 # DO NOT DELETE: OWNERS is intended to be empty as module owner and bug component are defined
3 # need to tell the difference between "no owner is specified for this module" vs "explicitly
4 # defer to parent OWNERS file"
/cts/hostsidetests/jvmti/run-tests/test-1922/
DOWNERS1 # DO NOT DELETE: OWNERS is intended to be empty as module owner and bug component are defined
3 # need to tell the difference between "no owner is specified for this module" vs "explicitly
4 # defer to parent OWNERS file"
/cts/hostsidetests/jvmti/run-tests/test-947/
DOWNERS1 # DO NOT DELETE: OWNERS is intended to be empty as module owner and bug component are defined
3 # need to tell the difference between "no owner is specified for this module" vs "explicitly
4 # defer to parent OWNERS file"

12345678910>>...114