Sensor Fusion on Android Devices: A Revolution in Motion Processing

Google TechTalks · 517K views · 2010 · 46:27

Open on YouTube

Embedded systems & DIY electronicsConsumer devices & gadgetstalk

Why Hacker News recommends it

HN recommends it as the definitive talk on mobile motion sensing, including why integrating acceleration twice drifts so badly.

What it is

David Sachs of InvenSense explains how gyroscopes, accelerometers and compasses work on their own and together, demonstrated on a modified Android handset. He covers sensor fusion algorithms and why rotation math such as Euler angles matters.

Recommended by 2 HN commenters across 2 different months, 2012 to 2026.

What Hacker News said

Strong rec gregsadetsky · 2026-07 · on “Show HN: Physically accurate black hole you can put in your room”

When this topic comes up, I'm always happy to share this incredible lecture from many many years ago about dead reckoning and how you _cannot_ integrate acceleration twice: [this video] (the whole video is incredible, but this is the magical bit)

Recommends cpitman · 2015-03 · on “Darpa to re-invent GPS navigation without the use of satellites”

Then you would be surprised how bad they are. A great talk on using mobile sensors is here: [this video] Long story short, expect something like 20 cm/s of position drift trying to do dead reckoning off of mobile sensors.

Cites losvedir · 2012-02 · on “You’ll Download Physical Objects Sooner Than You Think”

> The big winner will be an easy 3d modeler. Oh, I agree 100%. I was thinking a phone could be ideal here. You'd just wave it through the air, drawing what you want, you could review what you've drawn in the screen and adjust parameters, and it could vibrate to give haptic feedback to help you draw in a straight line, or let you know when your path connects to another that you've drawn. Stuff like that. Unfortunately, it looks like there's too much noise in the accelerometers to make the double integration to position meaningful. Something like Sensor Fusion[1] can make it more accurate by incorporating data from the gyroscope and compass, but even so it's not enough. In any case, like you I

Cites FabHK · 2021-10 · on “Plans to shift aviation from magnetic navigation to true navigation”

That is surprising, you must have had an extremely accurate accelerometer and gyro, or employed tricks [1]. There are two problems with determining position from acceleration measurements: 1. You're integrating twice (acceleration to obtain velocity, then velocity to obtain position). So if you have any noise or error, you're integrating that, and integrate that again. Hello, parabola. 2. Gravity. It's strong. So you have to subtract it (as it induces an apparent acceleration upwards). If the difference between actual down and where your model thinks is down is just a fraction of a degree, you'll be totally off within minutes. See eg here: [this video] Or here: [LINK] > As a concrete example cons