Yes I had known the gyroscope gives angular velocity and not orientation. I just want to confirm that none of the other sensor events ( other than TYPE_GYROSCOPE ) consider gyroscope hardware inputs to give out its results. Otherwise the results would be quite better.
Also with shakes I mean with very small movements this was large enough to just give just my linear accceleration and would normally come only if it used only accelerometer for its input. If gyroscope is combined to the results then this would not be the case. http://groups.google.com/group/android-developers/browse_thread/thread/a8b885c13c1ed87f/7eff726b9ee3d918?lnk=gst#7eff726b9ee3d918 In this post it seems that its still not used and will be in near future. But thanks for the answer. On Mar 15, 5:06 am, ip332 <[email protected]> wrote: > Here is the list of devices and the correspondedSensor.TYPE_XXX: > 1.Accelerometer (TYPE_ACCELEROMETER, TYPE_GRAVITY and > TYPE_LINEAR_ACCELERATION) > 2.Magnetic fieldsensor(TYPE_MAGNETIC_FIELD,TYPE_ORIENTATION) > 3.Gyroscope(TYPE_GYROSCOPE, TYPE_ROTATION_VECTOR) > 4.Lightsensor(TYPE_LIGHT) > 5.Proximity (TYPE_PROXIMITY) > > > Does TYPE_LINEAR_ACCELERATION uses both Acceleromter andGyroscope > > hardware at its best? > > No. TYPE_ACCELEROMETER reports absolute (raw) acceleration. According > to Android on-line docs, "The output of the accelerometer, gravity and > linear-acceleration sensors must obey the following relation: > acceleration = gravity + linear-acceleration" > > It looks like there is a common misunderstanding of MEMS gyro. It only > measures angular speed and nothing else. So if you do not rotate the > phone gyro output should be 0 even if you are accelerating. In other > words, gyro gives you the changes in orientation when the compass > (TYPE_ORIENTATION) - the absolute orientation. It seems to be a very > subtle difference but gyro gives better results in a real world due to > less sensitivity to the magnetic fields. > > > Also when tested on device ( Nexus S ) linear accelerations found to > > give high values for minor shakes , so assuming this removes gravity > > vector, this was not expected. > > Why not? A shake can have large acceleration value, here is an example > I recorded on my phone: > 7.1234417,6.033814,3.5140498 > while in rest the same device shows: > 0.20430522,0.47671217,9.493382 > > Removing gravity from the acceleration is only one issue. > You also need to take care about noise, orientation and variable > timing. > > On Mar 13, 3:03 am, Pritam <[email protected]> wrote: > > > Could someone help to know whichsensoruses which part of phone's > > hardware or in what combination of this on Nexus S in android 2.3 ? > > > Following are thesensorevents: > > > TYPE_ACCELEROMETER > > > TYPE_GYROSCOPE > > > TYPE_GRAVITY > > > TYPE_LINEAR_ACCELERATION > > > TYPE_ORIENTATION > > > TYPE_ROTATION_VECTOR > > > I assume first 2 corresponds to separate hardware (accelerometer and > >gyroscope), > > > but how with the other remaining ones ? > > > Does TYPE_LINEAR_ACCELERATION uses both Acceleromter andGyroscope > > hardware at its best? > > > I am actually interested in "linear aceleration" so should I need not > > worry about gyro events, if "linear acceleration" internally uses gyro > > to give out values ? > > > Also when tested on device ( Nexus S ) linear accelerations found to > > give high values for minor shakes , so assuming this removes gravity > > vector, this was not expected. > > > Thanks. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
