Searched refs:north (Results 1 – 4 of 4) sorted by relevance
| /frameworks/native/services/sensorservice/ |
| D | Fusion.cpp | 303 vec3_t north(cross_product(up, east)); in checkInitComplete() local
304 R << east << north << up; in checkInitComplete()
383 vec3_t north( cross_product(up, east) ); in handleMag() local
385 const float l_inv = 1 / length(north); in handleMag()
386 north *= l_inv; in handleMag()
388 update(north, Bm, mParam.magStdev*l_inv); in handleMag()
|
| /frameworks/native/libs/ui/tests/ |
| D | vec_test.cpp | 241 vec3 north(0, 1, 0); in TEST_F() local
242 vec3 up( cross(east, north) ); in TEST_F()
244 EXPECT_EQ(dot(east, north), 0); in TEST_F()
246 EXPECT_EQ(distance(east, north), sqrtf(2)); in TEST_F()
|
| /frameworks/base/docs/html/guide/topics/sensors/ |
| D | sensors_position.jd | 190 point north but instead to some other reference. That reference is allowed to drift by the
195 you do not care about where north is, and the normal rotation vector does not fit your needs
234 reference (specifically, magnetic north). The following code shows you how to get an instance of the
250 <li>Azimuth (degrees of rotation around the z axis). This is the angle between magnetic north
251 and the device's y axis. For example, if the device's y axis is aligned with magnetic north
|
| /frameworks/base/docs/html/about/versions/ |
| D | android-4.3.jd | 874 …, the {@link android.hardware.Sensor#TYPE_GAME_ROTATION_VECTOR} is not based on magnetic north.</p>
|