Support
Questions, invitation requests, bug reports, moderation appeals and privacy requests all go through one channel. We answer in Armenian, Russian or English.
Contact
Write to us and include your phone model, OS version and, for recording problems, the run's quality reasons as shown in the app. Never send raw sensor files or screenshots with other people's data.
To request a beta invitation, tell us your phone, your car and where you can record at a permitted closed-course session.
Frequently asked questions
Why did my run get no time?
Draggo returns a time only when it can be calculated under the protocol: a start detected from stationary calibration and the inertial launch detector, valid speed samples all the way to 100 km/h, and no long gaps. If any of that is missing, the run gets a reason instead of a number.
The reasons you can see are: missing launch (the start could not be detected), target not reached (the car did not reach 100 km/h), stale speed (the GPS kept repeating an old value), excessive gap (samples stopped for too long), mount movement (the phone moved during the run) and interrupted capture (the OS suspended recording, a call came in, or a permission was withdrawn). Draggo never fills the gap with an invented time.
What do CHECKS_PASSED, LIMITED and UNUSABLE mean?
CHECKS_PASSED: the recording met the automatic checks and the time can be compared with your other eligible runs. It is not a guarantee of accuracy and not a verification of the car or the driver.
LIMITED: a time was calculated but the data was weaker than the protocol wants, for example a short gap or a reduced fix quality. The run stays private and is excluded from personal bests and comparison. Limited data does not mean something is wrong with your car.
UNUSABLE: no comparable time could be calculated; the reasons are listed on the run.
Why is 0–60 mph not the same as 0–100 km/h?
60 mph is about 96.6 km/h, so a 0–60 mph time is shorter than a 0–100 km/h time for the same run. Many published 0–60 figures also use a rollout, where the first 30 cm or so of travel are excluded before the clock starts. Draggo measures 0–100 km/h from detected first motion with zero rollout, so its numbers are not directly comparable with those figures.
Draggo shows 0–100 km/h only. Switching the display to mph changes the labels, not the metric, and never changes the number that was measured.
Why does Draggo not show horsepower?
A phone cannot measure engine power. Turning an acceleration curve into power needs the car's exact mass, the slope, wind, drivetrain losses, tyre slip and more, none of which the phone knows. A number produced that way would look precise and be wrong.
Owners can type declared power into a setup. It is shown as declared, with the owner's source if given, and is never presented as measured.
Can I use Draggo on a public road?
No. Draggo is for permitted closed-course and private sessions. It has no public-road challenges, no top-speed rankings and no location-based rivals, and the community rules remove content recorded on public roads.
Do I need an account?
No, not for recording. Recording, saving, comparing and deleting runs work offline without an account. An account is needed only for cloud backup and the community.
How accurate is it?
We publish measured error figures per device model after field validation against a reference logger. Until a device model has passed that validation, Draggo makes no accuracy claim for it, and its runs stay private and experimental. Times are displayed to 0.1 s; demonstrated uncertainty is published separately.
Supported devices
The minimum operating system versions are below. OS eligibility alone does not establish accuracy: a phone must also pass field validation before its results are comparable.
- Android 10 (API 29) or newer with GPS and motion sensors, precise location permission and a fixed mount.
- iOS 16 or newer with precise location and motion authorization and a fixed mount.
- Validated models: specific validated models are published after the M0 field validation.
Reduced or approximate location permission allows browsing, not arming the recorder.
Measurement limits
What a Draggo time is, and is not:
- A phone-recorded estimate of 0–100 km/h from detected first motion with zero rollout. Not official timing, not a certified measurement.
- GPS update rate, fix quality, phone model, mount and sky view all affect the result. A requested rate is not a guaranteed rate.
- Slope, wind, load and surface are unknown to the phone and are not corrected.
- No quarter-mile, no 100–200 km/h, no top speed, no horsepower or torque estimation in this version.
- Runs from different phones or app versions are compared only when both have passed validation for the same protocol.
- Hashes and checks detect corrupted files; they do not prove that a run was driven honestly.