Searched refs:should (Results 1 – 25 of 195) sorted by relevance
12345678
| /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/base/data/keyboards/ |
| 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 "Y" but should really produce keycode "X"
24 # Button labeled as "B" but should really produce keycode "A"
26 # Button labeled as "A" but should really produce keycode "B"
28 # Button labeled as "X" but should really product keycode "Y"
|
| /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
|
| D | EGL_ANDROID_recordable.txt | 99 RESOLVED: It should be a new attribute. It does not make sense to use up a
102 2. How should the new attribute affect the sorting of EGLConfigs?
104 RESOLVED: It should not affect sorting. Some implementations may not have
106 implementations should not have to double-up some of their configs to one
|
| /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/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/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/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/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
|
| /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/base/cmds/statsd/src/ |
| D | active_config_list.proto | 28 // the activation should be set to active for this duration.
34 // This metric should activate for remaining_ttl_nanos when we load the activations.
36 // When we load the activations, this metric should activate on next boot for the tll
|
| /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/base/core/proto/android/app/ |
| D | notificationmanager.proto | 64 // Whether notifications suppressed by DND should not interrupt visually
67 // FULL_SCREEN_INTENT, AMBIENT, and LIGHTS should be used instead.
69 // Whether notifications suppressed by DND should not interrupt visually
71 // PEEK should be used instead of ON.
|
| /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/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();
|
| /frameworks/base/packages/SystemUI/docs/ |
| D | dagger.md | 56 should be declared as a `@Subcomponent` of the root component. This requires
77 injector that creates the injected object for you. This other class should
94 instance should be created.
124 that maps to the instance provided by Dagger. The changes should be similar
163 Generally, you shouldn't need to inject for a view, as the view should
164 be relatively self contained and logic that requires injection should be
196 a Context, you will not get the one that the view should have with proper
|
| D | clock-plugins.md | 15 large blocks of color that cause the OPR to exceed 5% should be avoided.
17 To prevent screen burn-in, clocks should not be composed of large solid
18 blocks of color, and the clock should be moved around the screen to
91 action should be taken to change the shape of the clock face or increase the
|
| D | plugins.md | 13 …define the interface layer between the plugin and SysUI. This interface should be relatively stab…
15 …ey should be placed in the plugin library, under com.android.systemui.plugin or sub-packages. The…
18 …should be incremented. Incompatible changes are changes to the signature of any of the interface …
46 * Called when a plugin has been uninstalled/updated and should be removed
55 …inListener with the PluginManager. The constants for action and version should be defined on clas…
98 Implementing the interface is generally pretty straightforward. The version of the plugin should t…
113 …he plugin will receive the onDestroy callback. At this point the plugin should ensure that all it…
144 As long as the plugin doesn’t depend on any hidden APIs (which plugins should avoid anyway) and onl…
|
| /frameworks/base/tests/AccessoryDisplay/ |
| D | README | 42 These applications should be installed on two separate Android
45 so the USB OTG cable should be plugged directly into it.
47 When connected, the applications should automatically launch
|
| /frameworks/minikin/doc/ |
| D | minikin_style.md | 38 * `#include <...>` should be used for non local library files.
39 * `#include "..."` should be used for minikin header files.
|
| /frameworks/native/services/surfaceflinger/sysprop/ |
| D | SurfaceFlingerProperties.sysprop | 31 # automated testing using dumpsys gfxinfo [2] are recommended), they should not
147 # Return true if surface flinger should use vr flinger for compatible vr
148 # apps, false otherwise. Devices that will never be running vr apps should
159 # Returns true if surface flinger should start
179 # useColorManagement indicates whether SurfaceFlinger should manage color
304 # refreshRateSwitching indicates whether SurfaceFlinger should use refresh rate
350 # useSmart90ForVideo indicates whether Scheduler should detect content FPS, and try to adjust the
368 # Indicates whether Scheduler's idle timer should support a display driver timeout in the kernel.
369 # The value of set_idle_timer_ms should be shorter in time than the timeout duration in the kernel.
|
| /frameworks/base/core/proto/ |
| D | README.md | 8 1. If the proto describes the top level output of dumpsys, it should contain
34 1. If the proto represents the structure of an object, it should have `Proto` as
|
| /frameworks/compile/libbcc/tests/debuginfo/target-tests/driver-simple/ |
| D | ACTIVITY.java.template | 39 // Ideally an app should implement onResume() and onPause()
47 // Ideally an app should implement onResume() and onPause()
|
| /frameworks/rs/script_api/ |
| D | rs_debug.spec | 21 They should not be used in shipping applications.
36 This function is intended for debugging only and should not be used in shipping
|
12345678