Questions about MotionRecord?
We answer.
MotionRecord is a small app from Bavaria — there's a person behind every reply, not a ticket system. WhatsApp is the fastest way to reach us.
Talk to us
Found a bug, missing a feature, or something isn't clear? Write to us. Marco reads every message himself, and good feedback often makes it into the next version.
Usually an answer within a day — sometimes faster on weekends.
Kurvenfokus on WhatsApp
Follow the channel — no account, no ads
The channel carries news from MotionRecord and Kurvenfokus, plus tour reports where every corner is counted. Short updates, mute them any time.
View channelNobody can reply inside the channel — that is simply how WhatsApp channels work. For questions and bug reports use the options above; those reach us directly.
Frequently asked questions
Where do I get MotionRecord?
On Android from the Google Play Store, on iOS as a TestFlight beta. Both free, no account needed. Just message us if you'd like to join the iOS test group.
How should I mount my phone?
Bolted down beats nicely visible. Vibration is the enemy of every measurement — a loose mount noticeably degrades the sensor data. Orientation, on the other hand, doesn't matter: MotionRecord works out how the phone sits and converts all readings into the vehicle's frame of reference.
Does recording continue while I navigate?
Yes. MotionRecord keeps recording in the background while you navigate with Calimoto, Komoot or Google Maps. On Android a persistent notification keeps the recording alive — please don't swipe it away.
How often does it measure?
The motion sensors run at up to 100 readings per second, GPS at one per second. The GPS rate is deliberately fixed: on consumer hardware, higher rates add no real information but cost noticeable battery life.
Which export do I need?
For analysis in Kurvenfokus, use the Kurvenfokus export. For your own work in Excel or Python, use the CSV or JSON export — it carries the complete sensor data at full resolution. GPX suits other map apps but contains only the route, no sensor data.
Where does my data end up?
On your device. No account, no server, no cloud requirement — even crash reporting is switched off. What you export and share is entirely your call.
The readings look odd — why?
Usually the mount: any play in the holder produces spikes that look like riding manoeuvres. Also check that the standstill calibration completed. If it still looks strange after that, send us the recording and we'll take a look.
MotionRecord or Kurvenfokus — what's the difference?
MotionRecord records: high-resolution sensor data, laps, sectors, G-forces. Kurvenfokus analyses tours: counting corners, rating lean angles, comparing routes. MotionRecord is the racetrack, Kurvenfokus the back road — and both speak the same export format.
For beta testers
Two things that cost the most time in practice — both learned the hard way on our own test rides:
- No engine data at the start? Restart the recording. If the OBD adapter fails to connect on the first attempt, it almost never recovers on its own. Restarting the recording usually fixes it within seconds — waiting it out can cost you an entire ride.
- Engine data only ever goes to one app at a time. The adapter holds exactly one connection. If another app is running alongside on the same device, MotionRecord gets nothing. So close anything else using the adapter before you set off.
Questions about Kurvenfokus?
Tour analysis has its own help page with FAQs, withdrawal policy and contact options:
kurvenfokus.de/en/support →Beta note: MotionRecord is in beta. All displayed readings are computed estimates derived from your smartphone's sensor data and are not certified measurements. Not suitable for safety-critical applications.