HackerTube.dev

Sensor Fusion on Android Devices: A Revolution in Motion Processing

Google TechTalks · 517.1K views · 2010-08-09 · 46:27

Open on YouTube ↗

If playback is restricted in your region, try opening the original video. Use Mark watched to add it to your marked videos.

Overview

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.

On Hacker News

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

Recommended by 2 HN people across 2 months · HN mentions 2012–2026

Topics

Search by tags

What people said

gregsadetsky · 2026-07 · Strong recommendation

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: [VIDEO] (the whole video is incredible, but this is the magical bit)

Read the original HN comment ↗
cpitman · 2015-03 · Recommendation

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

Read the original HN comment ↗
FabHK · 2021-10 · Reference

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: [VIDEO] Or here: [LINK] > As a concrete example consider a tilt error of just 0.05 [degrees]. This error will cause a component of the acceleration due to gravity with magnitude 0.0086 m/s2 to be projected onto the horizontal axes. This residual bias causes an error in the horizontal position which grows quadratically to 7.7 m after only 30 seconds [and thus to 770 m after 5 minutes, unless I'm mistaken, and 110 km after an hour] Or here: [LINK] (search for "Accuracy of Velocity and Position Estimates"). [1] such as assuming that your foot has velocity zero while on the ground, which does not hold when you're in an elevator, for example, and which you can't use in a drone without some serious sensor fusion.

Read the original HN comment ↗

Sources

Video by Google TechTalks, played through YouTube.

Data and selection notes

HN summaries and labels may contain AI errors. HN dates refer to discussions, not video publication.

HN Library: HackerTube export (2026-10-31) and open-index/hacker-news. Upstream summaries and classifications may contain AI errors.

Views, duration and playback status refresh separately from the published catalog. When an update fails, existing data remains visible.

Selection checks
  • SaaS & AI candidates: Topic keywords do not match
  • Editor-approved picks: Editorial review is required

Rule matches identify candidates. They do not guarantee video quality or financial results.

About the library and its sources