Phani Kumar Yadavilli · 7 November 2026

PhoneMaxxing: teaching my laptop where my phone is

I streamed a CMF Phone 1’s gyroscope into a live 3D twin, measured how wrong it gets, and learned the same lesson we keep learning at SocialHz.

1. Hello, gyroscope: it only knows how fast the phone is turning, not where it points.
2. Integrate and pray: chaining 400 small rotations a second into a quaternion.
3. The pipeline, end to end: phyphox, a FastAPI loop, a CSV log, a WebSocket and a CSS 3D twin.
4. Everything that went wrong: a missing library, mirrored axes, a stale buffer and no reference point.
5. How wrong is it, actually? 0.16° of drift in 174.5 seconds, about 570 times better than the textbook case.
6. From sensor signals to social signals: noise, bias, duplicates and provenance in social data.
7. What's next: gravity, a drift budget and error bars.

All posts · API reference