Searched refs:should (Results 1 – 25 of 319) sorted by relevance
12345678910>>...13
/frameworks/libs/modules-utils/ |
D | README.md | 10 This project uses a single source path for Java code. All Java code should go 12 `Android.bp` files should go alongside the java source files, and should only 15 Tests for java code should go in the `javatests` directory and follow the same
|
/frameworks/native/services/surfaceflinger/ |
D | surfaceflinger_flags.aconfig | 1 # This file is locked and should not be changed. Use surfaceflinger_flags_new.aconfig 30 # This file is locked and should not be changed. Use surfaceflinger_flags_new.aconfig 56 # This file is locked and should not be changed. Use surfaceflinger_flags_new.aconfig 82 # This file is locked and should not be changed. Use surfaceflinger_flags_new.aconfig 109 # This file is locked and should not be changed. Use surfaceflinger_flags_new.aconfig 130 …description: "Introduce protected displays to specify whether they should render protected content" 143 # This file is locked and should not be changed. Use surfaceflinger_flags_new.aconfig 177 # This file is locked and should not be changed. Use surfaceflinger_flags_new.aconfig 201 # This file is locked and should not be changed. Use surfaceflinger_flags_new.aconfig 236 # This file is locked and should not be changed. Use surfaceflinger_flags_new.aconfig
|
/frameworks/native/libs/binder/ndk/ |
D | stability.cpp | 27 #error libbinder_ndk should only be built in a system context 31 #error libbinder_ndk should only be built in a system context 35 #error libbinder_ndk should only be built in a system context
|
/frameworks/native/cmds/flatland/ |
D | README.txt | 11 Because it's measuring hardware performance, flatland should be run in as 12 consistent and static an environment as possible. The display should be 13 turned off and background services should be stopped before running the 17 with GPU rendering, those should be stopped as well (and ideally they'd be 20 Additionally, all relevant hardware clocks should be locked at a particular 30 time between 10 and 50 ms should address most thermal problems. 35 The output of flatland should look something like this: 69 scenario. In this case, simply rerunning flatland should yield a valid
|
/frameworks/av/media/audio/aconfig/ |
D | README.md | 12 All aconfig flags in this namespace should be defined in this directory, and all flags defined in 13 this directory should belong to this namespace. 32 Generally, `aconfig_declarations` and `{backend}_aconfig_library` should be 1-1, except in cases 59 file for platform code (for non-host). For tests, the library should be **statically** linked 65 Visibility should be controlled (private) so that flag cleanup remains maintainable by the team. 72 incremental rebuilds. Packages which end up in the framework should be avoided as much as possible, 84 classes, types, etc.) It also allows callers to make different decisions on when behavior can/should 88 its implementation should be deferred upwards, either by the injection interfaces, or by explicit 92 In general, flags should be scoped as precisely as possible while retaining orthogonality. If 101 In general, it is recommended that the moment a flag is added to the tree, it should be moved to [all …]
|
/frameworks/base/data/keyboards/ |
D | Vendor_2dc8_Product_6101.kl | 21 # Button labeled as "A" but should really produce keycode "B" 23 # Button labeled as "B" but should really produce keycode "A" 25 # Button labeled as "X" but should really produce keycode "Y" 27 # Button labeled as "Y" but should really produce keycode "X"
|
D | Vendor_0f0d_Product_00c1.kl | 19 # Button labeled as "Y" but should really produce keycode "X" 21 # Button labeled as "B" but should really produce keycode "A" 23 # Button labeled as "A" but should really produce keycode "B" 25 # Button labeled as "X" but should really product keycode "Y"
|
D | Vendor_057e_Product_2009.kl | 22 # Button labeled as "B" but should really produce keycode "A" 24 # Button labeled as "A" but should really produce keycode "B" 26 # Button labeled as "X" but should really product keycode "Y" 28 # Button labeled as "Y" but should really produce keycode "X"
|
/frameworks/native/opengl/specs/ |
D | EGL_ANDROID_presentation_time.txt | 76 specifies the time at which the current color buffer of surface should be 77 presented to the viewer. The time parameter should be a time in 81 display device, the time should correspond to the system monotonic up-time 109 2. How can the current value of the clock that should be used for the 117 or should it be a new parameter to an extended variant of eglSwapBuffers? 119 RESOLVED: The presentation time should be new state which is used by 131 - Clarified how uses that either do or do not need an absolute time should
|
/frameworks/av/media/libcpustats/include/cpustats/ |
D | README.txt | 5 * should be related to CPU usage statistics 6 * should be portable to host; avoid Android OS dependencies without a conditional
|
/frameworks/base/tools/hoststubgen/ |
D | README.md | 44 Run all tests. Many tests may fail, but at least this should run til the end. 45 (It should print `run-all-tests.sh finished` at the end) 74 - @HostSideTestNativeSubstitutionClass should automatically add class-keep to the substitute class. 80 - `helper-framework-*-src` should be moved to `frameworks/base/ravenwood` 81 - `test-framework` should be deleted.
|
/frameworks/base/tools/orientationplot/ |
D | README.txt | 53 point in between the two orientations; that is the gap. The gap should be 59 There should be no gap observed initially. The algorithm should pick one 62 settles, the confidence values should start trending to 0 again because 72 should be a fairly constant 60ms. If the latency jumps around wildly or 77 degrees (refer to MAX_TILT constant). Consequently, you should expect there 85 6. Orientation changes should be significantly harder when the device is held
|
/frameworks/base/services/core/java/com/android/server/flags/ |
D | pinner.aconfig | 7 description: "This flag controls if webview should be pinned in memory." 14 …description: "Ablation study flag that controls if home app odex/vdex files should be pinned in me…
|
/frameworks/wilhelm/doc/ |
D | README.txt | 1 When building applications using the OpenSL-ES API you should compile and link the OpenSLES_IID.c f… 2 have been automatically generated. Application developers should not edit these interface IDs.
|
/frameworks/base/packages/SystemUI/tools/lint/ |
D | README | 11 When you hit a lint error that should not be triggered, there are 3 19 3. If there are lint errors that should be fixed, but cannot be done 20 immediately for some reason, the issue should be added to
|
/frameworks/base/location/api/ |
D | module-lib-lint-baseline.txt | 35 …eter 1, "listener", in android.location.LocationManager.addNmeaListener) should be last to improve… 37 … "listener", in android.location.LocationManager.requestLocationUpdates) should be last to improve… 39 … "listener", in android.location.LocationManager.requestLocationUpdates) should be last to improve… 41 … "listener", in android.location.LocationManager.requestLocationUpdates) should be last to improve… 43 … 2, "listener", in android.location.LocationManager.requestSingleUpdate) should be last to improve… 45 … 2, "listener", in android.location.LocationManager.requestSingleUpdate) should be last to improve…
|
D | system-lint-baseline.txt | 35 …eter 1, "listener", in android.location.LocationManager.addNmeaListener) should be last to improve… 37 … "listener", in android.location.LocationManager.requestLocationUpdates) should be last to improve… 39 … "listener", in android.location.LocationManager.requestLocationUpdates) should be last to improve… 41 … 2, "listener", in android.location.LocationManager.requestSingleUpdate) should be last to improve… 43 … 2, "listener", in android.location.LocationManager.requestSingleUpdate) should be last to improve…
|
/frameworks/proto_logging/stats/atoms/dream/ |
D | dream_extension_atoms.proto | 41 // Configuration for when dream should begin. 62 // Configuration for when dream should begin. 72 // Configuration for when dream should begin. 98 // Setting for when dream should begin.
|
/frameworks/libs/systemui/viewcapturelib/ |
D | README.md | 3 ViewCapture.java is extremely performance sensitive. Any changes should be carried out with great c… 5 The following measurements should serve as a performance baseline (as of 02.10.2022):
|
/frameworks/compile/slang/tests/P_array_init/ |
D | array_init.rscript | 17 // Clang should implicitly promote this type to have a constant size of 3. 20 // Clang should implicitly promote this type to have a constant size of 1.
|
/frameworks/compile/slang/tests/P_reflection3264_divergent/ |
D | reflection3264_divergent.rscript | 74 // for arguments, should get a helper struct that looks like struct NonDivergent 77 // for arguments, should get a helper struct that looks like struct Divergent 80 // for arguments, should get a helper struct that looks like struct DivergentNest
|
/frameworks/compile/slang/tests/P_reflection3264_divergent_support/ |
D | reflection3264_divergent.rscript | 76 // for arguments, should get a helper struct that looks like struct NonDivergent 79 // for arguments, should get a helper struct that looks like struct Divergent 82 // for arguments, should get a helper struct that looks like struct DivergentNest
|
/frameworks/base/libs/WindowManager/Shell/src/com/android/wm/shell/docs/patterns/ |
D | TEMPLATE.md | 6 should/should not be used.
|
/frameworks/base/core/proto/android/app/ |
D | notificationmanager.proto | 66 // Whether notifications suppressed by DND should not interrupt visually 69 // FULL_SCREEN_INTENT, AMBIENT, and LIGHTS should be used instead. 71 // Whether notifications suppressed by DND should not interrupt visually 73 // PEEK should be used instead of ON.
|
/frameworks/base/tests/ActivityManagerPerfTests/ |
D | README.txt | 5 * Self-contained perf tests should go in frameworks/base/apct-tests/perftests 38 * The class should extend BasePerfTest 39 * Each test should call runPerfFunction() returning the elapsed time for a single iteration 50 * If the target package should be running before your test logic starts, add startTargetPackage();
|
12345678910>>...13