/frameworks/native/libs/input/ |
D | InputTransport.cpp | 74 return body.motion.pointerCount > 0 in isValid() 75 && body.motion.pointerCount <= MAX_POINTERS; in isValid() 88 return sizeof(Header) + body.motion.size(); in size() 322 msg.body.motion.seq = seq; in publishMotionEvent() 323 msg.body.motion.deviceId = deviceId; in publishMotionEvent() 324 msg.body.motion.source = source; in publishMotionEvent() 325 msg.body.motion.action = action; in publishMotionEvent() 326 msg.body.motion.flags = flags; in publishMotionEvent() 327 msg.body.motion.edgeFlags = edgeFlags; in publishMotionEvent() 328 msg.body.motion.metaState = metaState; in publishMotionEvent() [all …]
|
/frameworks/av/media/libstagefright/codecs/on2/h264dec/omxdl/arm11/vc/m4p2/src/ |
D | omxVCM4P2_DecodePadMV_PVOP_s.s | 16 ; * Decodes and pads four motion vectors of the non-intra macroblock in P-VOP. 17 ; * The motion vector padding process is specified in subclause 7.6.1.6 of 29 ; * [in] pSrcMVLeftMB pointers to the motion vector buffers of the 32 ; * [in] pSrcMVUpperMB pointers to the motion vector buffers of the 35 ; * [in] pSrcMVUpperRightMB pointers to the motion vector buffers of the 42 ; * motion vector buffer is still filled with the 50 ; * [out] pDstMVCurMB pointer to the motion vector buffer of the current 51 ; * macroblock which contains four decoded motion vectors
|
/frameworks/av/media/libstagefright/codecs/on2/h264dec/omxdl/arm_neon/vc/m4p2/src/ |
D | omxVCM4P2_DecodePadMV_PVOP_s.s | 16 ; * Decodes and pads four motion vectors of the non-intra macroblock in P-VOP. 17 ; * The motion vector padding process is specified in subclause 7.6.1.6 of 29 ; * [in] pSrcMVLeftMB pointers to the motion vector buffers of the 32 ; * [in] pSrcMVUpperMB pointers to the motion vector buffers of the 35 ; * [in] pSrcMVUpperRightMB pointers to the motion vector buffers of the 42 ; * motion vector buffer is still filled with the 50 ; * [out] pDstMVCurMB pointer to the motion vector buffer of the current 51 ; * macroblock which contains four decoded motion vectors
|
/frameworks/native/include/input/ |
D | InputTransport.h | 105 } motion; member 361 eventTime = msg->body.motion.eventTime; in initializeFrom() 363 for (size_t i = 0; i < msg->body.motion.pointerCount; i++) { in initializeFrom() 364 uint32_t id = msg->body.motion.pointers[i].properties.id; in initializeFrom() 367 pointers[i].copyFrom(msg->body.motion.pointers[i].coords); in initializeFrom()
|
/frameworks/base/docs/html/guide/topics/sensors/ |
D | sensors_motion.jd | 9 <li><a href="#sensors-motion-accel">Using the Accelerometer</a></li> 10 <li><a href="#sensors-motion-grav">Using the Gravity Sensor</a></li> 11 <li><a href="#sensors-motion-gyro">Using the Gyroscope</a></li> 12 <li><a href="#sensors-motion-linear">Using the Linear Accelerometer</a></li> 13 <li><a href="#sensors-motion-rotate">Using the Rotation Vector Sensor</a></li> 44 <p>The Android platform provides several sensors that let you monitor the motion of a device. Two of 57 your car). In the first case, you are monitoring motion relative to the device's frame of reference 58 or your application's frame of reference; in the second case you are monitoring motion relative to 65 <p>All of the motion sensors return multi-dimensional arrays of sensor values for each {@link 70 parameters. Table 1 summarizes the motion sensors that are available on the Android platform.</p> [all …]
|
D | index.jd | 4 page.landing.intro=Use sensors on the device to add rich location and motion capabilities to your a…
|
D | sensors_environment.jd | 45 <p>Unlike most motion sensors and position sensors, which return a multi-dimensional array of sensor 48 Also, unlike motion sensors and position sensors, which often require high-pass or low-pass
|
D | sensors_overview.jd | 53 <p>Most Android-powered devices have built-in sensors that measure motion, orientation, 710 href="{@docRoot}guide/topics/sensors/sensors_motion.html#sensors-motion-accel">Acceleration 713 href="{@docRoot}guide/topics/sensors/sensors_motion.html#sensors-motion-gravity">Gravity 716 href="{@docRoot}guide/topics/sensors/sensors_motion.html#sensors-motion-gyro">Gyroscope</a></li> 718 href="{@docRoot}guide/topics/sensors/sensors_motion.html#sensors-motion-linear">Linear acceleration 747 sensors and methods return data that represent device motion or device position relative to the 753 href="{@docRoot}guide/topics/sensors/sensors_motion.html#sensors-motion-rotate">Rotation Vector
|
/frameworks/base/docs/html/training/gestures/ |
D | multi.jd | 82 <p>The order in which individual pointers appear within a motion event is 87 pointer's ID to track the pointer across all subsequent motion events in a 88 gesture. Then for successive motion events, use the {@link 90 the pointer index for a given pointer ID in that motion event. For example:</p>
|
D | movement.jd | 76 of each of the historical events by using the motion event's {@code 117 // Retrieve a new VelocityTracker object to watch the velocity of a motion.
|
D | viewgroup.jd | 103 * This method JUST determines whether we want to intercept the motion. 295 // "myButton" is the child view that should receive motion
|
/frameworks/base/docs/html/about/versions/ |
D | android-3.1-highlights.jd | 315 sources and motion events, across all views and windows. Developers can build on 320 <p>For mouse and trackball input, the platform supports two new motion event 325 <p>For joysticks and gamepads, the platform provides a large number of motion 328 Developers can also define custom axes if needed, to capture motion in 329 additional ways. The platform provides motion events to applications as a batch, 333 <p>Applications can query for the list of connected input devices and the motion 335 input and motion events from a single input device. For example, an application
|
D | android-3.1.jd | 196 <h3 id="motionevents">Support for new input devices and motion events</h3> 199 types of motion events, across all views and windows. Developers can build on 205 two new motion event actions:</p> 208 location at which a non-touch scroll motion, such as from a mouse scroll wheel, 234 <p>To describe motion events from these new sources, as well as those from mice 257 motion data to applications. For a full list of axes and their intended 261 <p>The platform provides motion events to applications in batches, so a single 290 values according to the source from which they originate. When handling a motion 299 <p>Finally, since the motion events from joysticks, gamepads, mice, and 301 passing them to a {@link android.view.View} as "generic" motion events. [all …]
|
D | android-2.3.jd | 135 quickly and smoothly to precise changes in device position and motion. The 343 <li>Improved motion events 348 work efficiently with motion events.</li> 349 <li>The input system now has logic to generate motion events with the new 351 system tracks multiple pointer IDs separately during a motion event, and
|
/frameworks/base/docs/html/training/custom-views/ |
D | making-interactive.jd | 19 <li><a href="#motion">Create Physically Plausible Motion</a></li> 49 the motion, and then 50 at the end sense momentum that carries the motion beyond the fling.</p> 139 <h2 id="motion">Create Physically Plausible Motion</h2>
|
/frameworks/base/docs/html/training/animation/ |
D | index.jd | 73 Learn how to animate between two views with a flipping motion.
|
/frameworks/base/docs/html/training/graphics/opengl/ |
D | motion.jd | 42 <p>In this lesson, you take another step forward into using OpenGL ES by learning how to add motion
|
D | index.jd | 69 <dt><b><a href="motion.html">Adding Motion</a></b></dt>
|
D | touch.jd | 7 previous.link=motion.html
|
D | projection.jd | 152 add motion to your shapes.</p>
|
D | draw.jd | 193 <p>Lastly, the triangle is stationary, which is a bit boring. In the <a href="motion.html">Adding
|
/frameworks/base/policy/src/com/android/internal/policy/impl/ |
D | ImmersiveModeConfirmation.java | 294 public boolean onTouchEvent(MotionEvent motion) { in onTouchEvent() argument
|
/frameworks/base/docs/html/tools/help/ |
D | monkey.jd | 111 <td><code>--pct-motion <percent></code></td> 112 <td>Adjust percentage of motion events.
|
D | systrace.jd | 14 application is slow to draw or stutters while displaying motion or animation. For more information
|
/frameworks/base/docs/html/tools/debugging/ |
D | systrace.jd | 199 for good performance. Having a regular rhythm for display ensures that animations and motion are 226 display of screen content, particularly for animations and motion. Interruptions in the regular
|