| /frameworks/native/include/input/ |
| D | VelocityControl.h | 62 float acceleration; member
65 scale(1.0f), lowThreshold(0.0f), highThreshold(0.0f), acceleration(1.0f) { in VelocityControlParameters()
69 float highThreshold, float acceleration) : in VelocityControlParameters()
71 highThreshold(highThreshold), acceleration(acceleration) { in VelocityControlParameters()
|
| /frameworks/native/libs/input/ |
| D | VelocityControl.cpp | 77 scale *= mParameters.acceleration; in move()
83 * (mParameters.acceleration - 1); in move()
90 mParameters.acceleration, in move()
97 mParameters.acceleration); in move()
|
| /frameworks/native/services/sensorservice/ |
| D | LinearAccelerationSensor.cpp | 43 outEvent->data[0] = event.acceleration.x - outEvent->data[0]; in process()
44 outEvent->data[1] = event.acceleration.y - outEvent->data[1]; in process()
45 outEvent->data[2] = event.acceleration.z - outEvent->data[2]; in process()
|
| /frameworks/base/docs/html/guide/topics/sensors/ |
| D | sensors_motion.jd | 46 sensors can be either hardware-based or software-based (the gravity, linear acceleration, and
67 acceleration force data for the three coordinate axes, and the gyroscope returns rate of rotation
170 sensor, a linear acceleration sensor, and a rotation vector sensor. These sensors were updated in
183 <p>An acceleration sensor measures the acceleration applied to the device, including the force of
184 gravity. The following code shows you how to get an instance of the default acceleration sensor:</p>
194 <p>Conceptually, an acceleration sensor determines the acceleration that is applied
202 <p>However, the force of gravity is always influencing the measured acceleration according to
213 the real acceleration of the device, the contribution of the force of gravity must be removed from
251 <li>If you push the device on the left side (so it moves to the right), the x acceleration value
253 <li>If you push the device on the bottom (so it moves away from you), the y acceleration value is
[all …]
|
| D | sensors_overview.jd | 67 <p>These sensors measure acceleration forces and rotational forces along three axes. This
103 properties, such as acceleration, geomagnetic field strength, or angular change. Software-based
106 sensors or synthetic sensors. The linear acceleration sensor and the gravity sensor are examples of
127 <td>Measures the acceleration force in m/s<sup>2</sup> that is applied to a device on
160 <td>Measures the acceleration force in m/s<sup>2</sup> that is
163 <td>Monitoring acceleration along a single axis.</td>
718 href="{@docRoot}guide/topics/sensors/sensors_motion.html#sensors-motion-linear">Linear acceleration
|
| D | sensors_position.jd | 227 you how to translate acceleration sensor data into another frame of reference; the technique is
|
| /frameworks/base/docs/html/guide/topics/graphics/ |
| D | index.jd | 3 …t using Android's powerful graphics features such as OpenGL, hardware acceleration, and built-in U…
16 support hardware acceleration on tablets. With this new pipeline, all drawing operations performed
30 href="http://android-developers.blogspot.com/2011/03/android-30-hardware-acceleration.html">
|
| D | hardware-accel.jd | 51 acceleration, meaning that all drawing operations that are performed on a {@link
53 hardware acceleration, your app will consume more RAM.</p>
55 <p>Hardware acceleration is enabled by default if your Target API level is >=14, but can also
58 effects. However, because hardware acceleration is not supported for all of the 2D drawing
61 remedy this, Android gives you the option to enable or disable hardware acceleration at multiple
65 with hardware acceleration turned on to find any problems. The <a
67 hardware acceleration and how to work around them.</p>
70 <p>You can control hardware acceleration at the following levels:</p>
84 <code><application></code></a> tag to enable hardware acceleration for your entire
92 <p>If your application does not behave properly with hardware acceleration turned on globally, you
[all …]
|
| /frameworks/base/docs/html/guide/topics/renderscript/ |
| D | index.jd | 25 adding compute acceleration to your application. RS is interesting for compute
26 acceleration when you have large buffers of data on which you need to do significant
|
| /frameworks/base/docs/html/training/custom-views/ |
| D | optimizing-view.jd | 96 found in most newer Android devices. GPU hardware acceleration can result in a tremendous
103 in the Android Developers Guide for directions on how to enable acceleration at the
109 <p>Once you've enabled hardware acceleration, you may or may not see a performance increase.
112 get the most out of GPU acceleration, you should maximize the number of operations that the GPU is
|
| D | index.jd | 66 performance problems, and how to use hardware acceleration to make your
|
| /frameworks/native/include/android/ |
| D | sensor.h | 144 ASensorVector acceleration; member
|
| /frameworks/base/docs/html/tools/devices/ |
| D | emulator.jd | 13 <li><a href="#acceleration">Using Hardware Acceleration</a>
225 <h2 id="acceleration">Using Hardware Acceleration</h2>
228 take advantage of hardware acceleration, using a combination of configuration options, specific
235 acceleration feature for the emulator is experimental; be alert for incompatibilities and
238 <p>Graphics acceleration for the emulator takes advantage of your development computer's graphics
240 the graphics acceleration feature, you must have the following versions of the Android development
252 acceleration. In particular, the Browser application and applications using the {@link
253 android.webkit.WebView} component are not compatible with graphics acceleration.</p>
255 <p>To configure an AVD to use graphics acceleration:</p>
261 <li>If you want to have graphics acceleration enabled by default for this AVD, in the
[all …]
|
| /frameworks/base/docs/html/training/graphics/opengl/ |
| D | index.jd | 38 acceleration of graphics processing units (GPUs) provided on many Android devices.</p>
|
| /frameworks/base/core/java/android/view/ |
| D | ViewRootImpl.java | 4069 + mX.step + " dir=" + mX.dir + " acc=" + mX.acceleration in process()
4072 + mY.step + " dir=" + mY.dir + " acc=" + mY.acceleration in process()
4091 accel = mX.acceleration; in process()
4099 accel = mY.acceleration; in process()
4180 float acceleration = 1; field in ViewRootImpl.TrackballAxis
4188 acceleration = 1; in reset()
4212 acceleration = 1; in collect()
4222 acceleration = 1; in collect()
4236 float acc = acceleration; in collect()
4244 acceleration = acc < MAX_ACCELERATION ? acc : MAX_ACCELERATION; in collect()
[all …]
|
| /frameworks/base/docs/html/about/versions/ |
| D | android-2.0-highlights.jd | 181 hardware acceleration.</p>
|
| D | android-3.0.jd | 557 pipeline, but only if hardware acceleration is turned on for the view hierarchy. When hardware
558 acceleration is turned off, hardware layers behave exactly as software layers.</p>
560 software rendering pipeline, even if hardware acceleration is enabled. Software layers should be
809 expressed with acceleration and rotation rate data. A web page can register for orientation
|
| D | kitkat.jd | 787 <h4>GPU acceleration</h4>
791 acceleration, without code changes or recompiling. Since the Nexus 10 first
792 debuted RenderScript GPU acceleration, various other hardware partners have
798 acceleration is available on the Nexus 5, as well as the Nexus 4, Nexus 7
|
| D | android-4.0.jd | 1097 android.hardware.Sensor#TYPE_ROTATION_VECTOR}), and linear acceleration sensor ({@link
1553 <p>Beginning with Android 4.0, hardware acceleration for all windows is enabled by default if your
1557 {@code “14"} or higher. Hardware acceleration generally results in smoother animations, smoother
1560 <p>If necessary, you can manually disable hardware acceleration with the <a
1565 element. You can alternatively disable hardware acceleration for individual views by calling {@link
1568 <p>For more information about hardware acceleration, including a list of unsupported drawing
1720 {@code "14"} or higher, hardware acceleration is enabled by default.</p></li>
|
| /frameworks/base/docs/html/tools/help/ |
| D | emulator.jd | 426 <td>Enable KVM acceleration of the emulator virtual machine.</td>
428 <a href="{@docRoot}tools/devices/emulator.html#vm-linux">KVM-based VM acceleration</a>.
440 <td>Turn on graphics acceleration for the emulator.</td>
|
| /frameworks/base/docs/html/distribute/googleplay/quality/ |
| D | core.jd | 733 <td>Hardware acceleration</td>
738 <p style="margin-bottom:.5em;">Repeat <em>Core Suite</em> with hardware acceleration enabled.</p>
740 …<p style="margin-bottom:.25em;">To force-enable hardware acceleration (where supported by device),…
|
| /frameworks/base/docs/html/tools/revisions/ |
| D | platforms.jd | 387 href="{@docRoot}tools/devices/emulator.html#accel-graphics">graphics acceleration</a> in the
417 hardware graphics acceleration when used with SDK Tools r17 or higher.
|
| /frameworks/base/docs/html/guide/practices/ |
| D | optimizing-for-3.0.jd | 381 <h3>Enable hardware acceleration</h3>
388 <activity>}</a> elements. Hardware acceleration results in smoother animations, smoother
390 that you thoroughly test your application on a device that supports hardware acceleration.</p>
|
| /frameworks/base/docs/html/guide/topics/resources/ |
| D | animation-resource.jd | 652 acceleration for the {@link android.view.animation.AnticipateInterpolator}, or adjust the number of
696 <dd><em>Float</em>. The acceleration rate (default is 1).</dd>
|
| /frameworks/base/docs/html/guide/appendix/ |
| D | glossary.jd | 62 on the screen. However, it does not support hardware acceleration, as
|