Home	Sort by relevance Sort by last modified time

Full Search Definition Symbol File Path History   | | Help

    Searched full:reported (Results 276 - 300 of 3442) sorted by null

<<11121314151617181920>>

/toolchain/binutils/binutils-2.25/gas/testsuite/gas/ieee-fp/
x930509a.exp	17 # Reported 93/05/09 by Jim Wilson: IEEE single-precision FLT_MIN value gets
/docs/source.android.com/src/devices/input/
touch-devices.jd	213 tools. Likewise, touching tools and hovering tools are reported to applications 215 <p>Touching tools are reported to applications as touch events 218 <p>Hovering tools are reported to applications as generic motion events using 358 <p>For a touch screen, the system automatically interpolates the reported touch 364 <p>A touch screen may report touches outside of the reported active area.</p> 373 area. If a touch exits the active area, it should be reported as being outside of 374 the active area, or it should not be reported at all.</p> 387 <p>The values reported by <code>ABS_PRESSURE</code> or <code>ABS_MT_PRESSURE</code>, if they 388 are reported at all, must be non-zero when the tool is touching the device 395 <p>The values reported by <code>ABS_TOOL_WIDTH</code>, <code>ABS_MT_TOUCH_MAJOR</code>, <code>ABS_MT_TOUCH_MINOR</code>     [all...]
/development/samples/training/multiscreen/newsreader/src/com/example/android/newsreader/
NonsenseGenerator.java	49 "is expected to buy", "is expected to sell", "was reported to have met with", 58 "expected to buy", "expected to sell", "reported to have met with", 145 pickOneOf(", claimed", ", said", ", reported"));
/docs/source.android.com/src/devices/sensors/
suspend-mode.jd	48 reported and operations resume as normal.</p> 58 reported. That is, the sensor must wake the SoC up and deliver the events 63 milliseconds each time an event is being reported. <em>That is, the SoC should not
hal-interface.jd	56 sensors will be reported to the applications. Usually, the base sensors appear 100 being reported through the HAL, in nanoseconds. See the <a href="#max_report_latency_ns">max_report_latency_ns</a> paragraph for more details.</p> 160 be delayed and stored in the hardware FIFO before being reported through the 162 <p>A value of zero signifies that the events must be reported as soon as they are 167 <p>When <code>max_report_latency_ns&gt;0</code>, sensor events do not need to be reported as soon 169 reported in batches, as long as no event is delayed by more than 175 event is reported does not impact the event timestamp. The timestamp must be 177 the time it is being reported. </p> 284 reported values. The sensor must be able to report values without saturating 292 always more that the power consumption reported in the datasheet of th     [all...]
/docs/source.android.com/src/security/bulletin/
2016-02-01.jd	45 <p>We have had no reports of active customer exploitation of these newly reported 170 with the CVE, associated bug, severity, affected versions, and date reported. 191 <th>Date reported</th> 232 <th>Date reported</th> 266 <th>Date reported</th> 294 <th>Date reported</th> 322 <th>Date reported</th> 348 <th>Date reported</th> 374 <th>Date reported</th> 399 <th>Date reported</th     [all...]
/external/libpcap/
README.linux	94 Statistics reported by pcap are platform specific. The statistics 95 reported by pcap_stats on Linux are as follows: 108 but won't be reported by, for example, tcpdump output.
/external/lz4/
NEWS	3 Fixed : GCC 4.9 bug on highest performance settings, reported by Greg Slazinski 4 Fixed : bug within LZ4 HC streaming mode, reported by James Boyle 5 Fixed : older compiler don't like nameless unions, reported by Cheyi Lin
/frameworks/opt/net/wifi/service/java/com/android/server/wifi/scanner/
ScanScheduleUtil.java	128 * Returns true if the given scan result should be reported to a listener with the given 142 * requested in the settings. Will return null if the result should not be reported. 146 * the bucket was definitely not scanned then the scan data will not be reported.
/hardware/libhardware/include/hardware/
vr.h	67 * reported in the thermal.h HAL. Specifically, the current skin temperature 68 * must accurately be reported for DEVICE_TEMPERATURE_SKIN and the 69 * vr_throttling_threshold reported for this device must accurately report the
activity_recognition.h	82 * reported to the framework. An event of this type should be generated only if flush() has been 148 // events - Array of activity_event_t s that are reported. 171 * Activates monitoring of activity transitions. Activities need not be reported as soon as they 172 * are detected. The detected activities are stored in a FIFO and reported in batches when the 175 * batch FIFO. Whenever events need to be reported (like when the FIFO is full or when the
/prebuilts/go/darwin-x86/src/go/ast/
resolve.go	69 // remaining unresolved identifiers are reported as undeclared. If the files 71 // different package names are reported and then ignored. 103 // (error has already been reported)
/prebuilts/go/linux-x86/src/go/ast/
resolve.go	69 // remaining unresolved identifiers are reported as undeclared. If the files 71 // different package names are reported and then ignored. 103 // (error has already been reported)
/system/bt/stack/mcap/
mca_api.c	323 ** MCA_CONNECT_IND_EVT is reported to the application via its 327 ** reported. The security mask parameter overrides the outgoing 384 ** reported to the application via its control callback function. 409 ** When the response is received, a MCA_CREATE_CFM_EVT is reported 416 ** is reported. This data channel is identified as tMCA_DL. 491 ** is reported. This data channel is identified as tMCA_DL. 584 ** When the response is received, a MCA_RECONNECT_CFM_EVT is reported. 589 ** is reported. 653 ** is reported. 720 ** is reported. This data channel is identified as tMCA_DL     [all...]
/system/core/metricsd/
README.md	67 crash is reported. This thread is kept as simple as possible to ensure the 97 in the overflow bucket. Also, the reported mean of the data will be correct 117 ### How can I test that my histogram was reported correctly?
/cts/tests/tests/hardware/src/android/hardware/cts/
SingleSensorTests.java	46 * The event ordering test verifies the ordering of the sampled data reported by the Sensor under 47 * test. This test is used to guarantee that sensor data is reported in the order it occurs, and 48 * that events are always reported in order. It verifies that each event's timestamp is in the 60 * The jitter test verifies that the event jittering associated with the sampled data reported by 68 * reported by the sensor under test. This test is used to validate the requirement imposed by the 75 * This test is used to verify that the data reported by the sensor is close to the expected 82 * each axis of the sampled data reported by the sensor under test. This test is used to validate
/external/chromium-trace/catapult/third_party/Paste/paste/exceptions/
errormiddleware.py	353 reported = False 369 reported = True 377 reported = True 385 reported = True 397 reported = True 407 reported = True 416 if not reported and error_stream:
/frameworks/base/core/java/android/util/
DisplayMetrics.java	225 * The reported display width prior to any compatibility mode scaling 231 * The reported display height prior to any compatibility mode scaling 237 * The reported display density prior to any compatibility mode scaling 243 * The reported display density prior to any compatibility mode scaling 249 * The reported scaled density prior to any compatibility mode scaling 255 * The reported display xdpi prior to any compatibility mode scaling 261 * The reported display ydpi prior to any compatibility mode scaling
/external/kernel-headers/original/uapi/linux/
input.h	51 * @value: latest reported value for the axis. 57 * joydev interface and reported as 0 instead. 58 * @resolution: specifies resolution for the values reported for 61 * Note that input core does not clamp reported values to the 64 * Resolution for main axes (ABS_X, ABS_Y, ABS_Z) is reported in 66 * (ABS_RX, ABS_RY, ABS_RZ) is reported in units per radian.
/cts/apps/CameraITS/tests/scene3/
test_reprocess_edge_enhancement.py	49 Object containing reported edge mode and the sharpness of the output 132 print "Reported edge modes:", edge_mode_reported_regular 159 print "Reported edge modes:", edge_mode_reported
/cts/apps/CtsVerifier/src/com/android/cts/verifier/sensors/
MagneticFieldMeasurementTestActivity.java	55 * This test is used to verify that the data reported by the sensor is close to the expected 63 * which the data are reported and the expectations are set are different. 97 * of the sampled data reported by the Sensor under test.
/external/clang/www/analyzer/
faq.html	24 reported here since my custom error handler will safely end the execution before 38 reported here since my custom error handler will safely end the execution before 73 You can use the <tt>(void)x;</tt> idiom to acknowledge that there is a dead store in your code but you do not want it to be reported in the future.</p>
/external/deqp/doc/testspecs/GLES2/
functional.lifetime.txt	51 reported by the Is* family of GL functions, the state of bindings as 52 reported in various state variables, and the behavior of containers with 64 whether a new object was created for the name (as reported by the result
/external/deqp/doc/testspecs/GLES3/
functional.lifetime.txt	57 reported by the Is* family of GL functions, the state of bindings as 58 reported in various state variables, and the behavior of containers with 70 whether a new object was created for the name (as reported by the result
/external/deqp/framework/common/
tcuTestHierarchyIterator.hpp	88 * For executable (test case) nodes STATE_LEAVE_NODE will always be reported 94 * or leave the parent group if the reported node was last child of that 97 * Root node is never reported, but instead iteration will start on first

Completed in 684 milliseconds

<<11121314151617181920>>