Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Disclaimer: I do not know any Android specifics, it's likely also handset specific. I merely speaking from a physics background.</p> <p>You will need to integrate acceleration to velocity, and integrate velocity to displacement (position).</p> <p>You will suffer from integrational drift. Each time you integrate, an integration constant will be introduced. Multiple integrations compound this error.</p> <p>You will also need to worry about angular acceleration. ie. What happens when the handset is rotated, but remains in the same physical location?</p> <p>There are ways to help reduce these sources of error.</p> <p>If there are multiple accelerometers you can compare them, to try and determine any angular components. </p> <p>If there are gyro's, you can use the gyro's to help cancel out the angular components.</p> <p>If the compass is accurate enough, you can try to cancel at least the components in the horizontal plane.</p> <p>GPS can be used to try and remove displacement integration errors. When the GPS says you are stopped, zero out the integration constants.</p> <p>You will need to start looking at numerical integration and filtering algorithms. Without hardware acceleration, this could be computationally expensive.</p> <p>At which point you really need to start asking yourself, does your problem really need precise displacement measurements? Will GPS displacement suffice? Can you achieve the same result with only acceleration?</p> <p>You should try reading up on:</p> <p><a href="http://en.wikipedia.org/wiki/Inertial_navigation_system" rel="nofollow">http://en.wikipedia.org/wiki/Inertial_navigation_system</a></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload