Home
last modified time | relevance | path

Searched refs:should (Results 1 – 25 of 235) sorted by relevance

12345678910

/frameworks/native/cmds/flatland/
DREADME.txt11 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/native/opengl/specs/
DEGL_ANDROID_presentation_time.txt76 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/base/tools/orientationplot/
DREADME.txt53 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/data/keyboards/
DVendor_057e_Product_2009.kl22 # 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/hardware/interfaces/bufferhub/1.0/
DREADME.md4 as this interface should only be used by the Android platform. Vendors should use
/frameworks/av/media/libcpustats/include/cpustats/
DREADME.txt5 * should be related to CPU usage statistics
6 * should be portable to host; avoid Android OS dependencies without a conditional
/frameworks/wilhelm/doc/
DREADME.txt1 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/
DREADME11 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/opt/gamesdk/third_party/protobuf-3.0.0/objectivec/Tests/
DGPBMessageTests.m49 // TODO(thomasvl): this should get split into a few files of logic junks, it is
611 // Initially they should all not have values.
620 // They should auto create something when fetched.
640 // Although they were created, they should not respond to hasValue until that
651 // mutable (so a second fetch should give the same object).
661 // And the default objects for a second message should be distinct (again,
722 // Mutable copy should not copy autocreated messages.
736 // Call clear on an intermediate submessage should cause it to get recreated
764 // Should be the same object, and should still be live.
781 // Setting submessage to nil should cause it to lose its creator.
[all …]
/frameworks/base/cmds/statsd/src/
Dactive_config_list.proto28 // 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/opt/gamesdk/third_party/protobuf-3.0.0/src/google/protobuf/compiler/
Dplugin.proto44 // plugin should be named "protoc-gen-$NAME", and will then be used when the
59 // code generator should generate code only for these files. Each file's
83 // should exit with status code zero even if it reports an error in this way.
85 // This should be used to indicate errors in .proto files which prevent the
88 // unparseable -- should be reported by writing a message to stderr and
107 // If non-empty, indicates that the named file should already exist, and the
115 // which allows it to be placed in a comment. NAME should be replaced with
129 // other declarations that should be placed in this scope.
135 // should be indented the same amount as any inserted code will need to be
/frameworks/base/core/proto/android/app/
Dnotificationmanager.proto64 // 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/base/tests/ActivityManagerPerfTests/
DREADME.txt5 * 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/
Ddagger.md56 should be declared as an `@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
Dclock-plugins.md15 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
Dplugins.md13 …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/opt/gamesdk/third_party/protobuf-3.0.0/objectivec/
DGPBUtilities.m111 @"%@: All messages should have storage (from init)",
193 //%// Only exists for public api, no core code should use this.
212 //% @"%@: All messages should have storage (from init)",
229 //%// Only exists for public api, no core code should use this.
235 //%// Only exists for public api, no core code should use this.
268 // This exists only for briging some aliased types, nothing else should use it.
288 @"%@: All messages should have storage (from init)",
303 // should be done when their value is set to nil. Is the intention just to
309 // appear in debug, but the could should be changed so the intention is
435 // Only exists for public api, no core code should use this.
[all …]
/frameworks/opt/gamesdk/third_party/protobuf-3.0.0/m4/
Dacx_check_suncc.m49 dnl docs say should never be overridden except by the user. It also isn't
10 dnl cross-compile safe. We should fix these problems, but since I don't have
51 dnl This should just be set in CPPFLAGS and in LDFLAGS, but libtool
/frameworks/base/tests/AccessoryDisplay/
DREADME42 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/
Dminikin_style.md38 * `#include <...>` should be used for non local library files.
39 * `#include "..."` should be used for minikin header files.
/frameworks/opt/gamesdk/third_party/protobuf-3.0.0/js/
DREADME.md67 If you want to use Closure imports, your build should run a command
89 Once you've done this, you should be able to import your types with
99 If you want to use CommonJS imports, your build should run a command
106 code will depend on the core runtime, which should be in a file called
107 `google-protobuf.js`. If you are installing from `npm`, this file should
113 Once you've done this, you should be able to import your types with
/frameworks/base/core/proto/
DREADME.md8 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/native/services/surfaceflinger/sysprop/
DSurfaceFlingerProperties.sysprop31 # 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
312 # useSmart90ForVideo indicates whether Scheduler should detect content FPS, and try to adjust the
330 # Indicates whether Scheduler's idle timer should support a display driver timeout in the kernel.
331 # The value of set_idle_timer_ms should be shorter in time than the timeout duration in the kernel.
/frameworks/rs/script_api/
Drs_debug.spec21 They should not be used in shipping applications.
36 This function is intended for debugging only and should not be used in shipping
/frameworks/compile/libbcc/tests/debuginfo/target-tests/driver-simple/
DACTIVITY.java.template39 // Ideally an app should implement onResume() and onPause()
47 // Ideally an app should implement onResume() and onPause()

12345678910