Searched refs:should (Results 1 – 25 of 126) sorted by relevance
123456
11 Because it's measuring hardware performance, flatland should be run in as12 consistent and static an environment as possible. The display should be13 turned off and background services should be stopped before running the17 with GPU rendering, those should be stopped as well (and ideally they'd be20 Additionally, all relevant hardware clocks should be locked at a particular30 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
76 specifies the time at which the current color buffer of surface should be77 presented to the viewer. The time parameter should be a time in81 display device, the time should correspond to the system monotonic up-time109 2. How can the current value of the clock that should be used for the117 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 by131 - Clarified how uses that either do or do not need an absolute time should
99 RESOLVED: It should be a new attribute. It does not make sense to use up a102 2. How should the new attribute affect the sorting of EGLConfigs?104 RESOLVED: It should not affect sorting. Some implementations may not have106 implementations should not have to double-up some of their configs to one
53 point in between the two orientations; that is the gap. The gap should be59 There should be no gap observed initially. The algorithm should pick one62 settles, the confidence values should start trending to 0 again because72 should be a fairly constant 60ms. If the latency jumps around wildly or77 degrees (refer to MAX_TILT constant). Consequently, you should expect there85 6. Orientation changes should be significantly harder when the device is held
5 * should be related to CPU usage statistics6 * should be portable to host; avoid Android OS dependencies without a conditional
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.
42 These applications should be installed on two separate Android45 so the USB OTG cable should be plugged directly into it.47 When connected, the applications should automatically launch
39 // Ideally an app should implement onResume() and onPause()47 // Ideally an app should implement onResume() and onPause()
21 They should not be used in shipping applications.36 This function is intended for debugging only and should not be used in shipping
35 This function should not be called from inside a kernel, or from any function function50 This function should not be called from inside a kernel, or from any function function
43 // Ideally an app should implement onResume() and onPause()51 // Ideally an app should implement onResume() and onPause()
1 This should be uncompressed.
1 A simple data file that should *not* be copied to the output jar.
1 A simple data file that should be copied to the output jar unchanged.
19 #error wrap_gles.h should only be used as an auto-included header, don't directly #include it
19 theme automatically. These should setup the framework theme ready so45 Because of this, every time there is a third level theme set, there should be a second level
20 * **ok**: network access granted while app on background (NetworkInfo's state/detailed state should…21 …cess blocked while app on background (NetworkInfo's state/detailed state should be `DISCONNECTED` …
17 /frameworks/rs/test/lldb and type mm. This should successfully build the26 lldb-server and lldb should be built from the same source revisions.111 details of your specific environment. The user file should define a custom149 The following CMake variables should be enabled when generating:176 The following CMake variables should be enabled when generating:185 In the CMake configure step, you should see something similar to the205 The LLDB python bindings should have built in
6 // Declare an uninitialized external constant, which should be ok for our
140 // True if the device should stay on.169 // the dreaming or dozing state. Indicates whether a new dream should begin.309 // True if the device should wake up when plugged or unplugged.311 // True if the device should wake up when plugged or unplugged in theater mode.315 // True if the device should suspend when the screen is off due to proximity.340 // True if dreams should be activated on sleep.342 // True if dreams should be activated on dock.344 // True if doze should not be started until after the screen off transition.
8 - onAddEditTextToDialogView has been removed. Any code depending on overriding this method should
85 IEventQueueCallback.onEvent is designed to be oneway, because the server should87 should finish in a predictably short time, and should not block or run for an
25 and run adb install out/target/.../SmartCamera.apk. The application should37 should appear. From there, you can go to the gallery with the gallery button or
9 the helper itself) became final. Any code that depends on overriding these methods should be