TORKMARK

Android alpha · closed testing

Record the work. Understand the change.

Three things, on the phone in your hand. Keep the history of every part, repair and modification. Read what your vehicle reports. Put the readings before the work next to the readings after it.

Requires Android 10 or newer. Closed testing is open in the United States only. Vehicle readings need an ELM327-compatible Bluetooth OBD-II adapter.

Request early access Questions
A phone held in front of an open engine bay, showing decoded engine values read from the vehicle.

What it does

Build history, vehicle readings, and the comparison between them.

Everything below is in the closed-test build today. What is designed and not built has a section of its own further down, so the two are never mixed.

Build historyLog each part, repair or modification with its date, mileage, cost and notes; every change commits a new version and keeps the one it replaced. Record where you bought a part with a link; Torkmark does not store photos or documents.
Vehicle readingsTorkmark reads the standard OBD-II signals your vehicle answers to, including coolant, intake and ambient temperature, engine load, throttle, engine speed, speed, fuel trims and module voltage. Start a drive and it records what your vehicle reports, then keeps a summary of that drive on your phone.
Before and afterLog a change and Torkmark compares your most recent drive before it against your most recent drive after it, on the same reading. It reports what changed, not what caused it.
A Jeep in a garage with the front wheel removed, the brake rotor and hub bare and a bottle jack under the axle.
Figure 1 · The moment the record gets written

What it reads

Ten signals, in four groups.

These are the readings the closed-test build shows. Your vehicle is asked which of them it supports, and only those are polled, so the set you see is the set your vehicle answers to.

ThermalCoolant temperature, intake air temperature, ambient air temperature.
EngineEngine load, throttle position, engine speed, vehicle speed.
FuelLong-term fuel trim, bank 1 and bank 2.
ElectricalControl module voltage.

Coolant temperature is read today. Transmission and oil temperature are outside the standard set and are not yet proven on any vehicle.

Trouble codes

Torkmark reads stored, pending and permanent trouble codes and decodes them to plain English. In the current build they appear in the diagnostics log rather than on their own screen.

Module-level reads are planned and are not in the closed-test build.

Your limits, not ours

Set your own limits for each reading; Torkmark shows the number against the limit you set. There is no universal healthy number published here, because a number that is normal on one engine is not on the next.

When there is no number

A missing reading is never drawn as zero.

Anything Torkmark cannot read is shown as a dash, never as a number. Five different things can put that dash there, and they mean different things to you.

  • No data recordedNothing has been read for this signal yet.
  • Adapter disconnectedThe adapter is not connected, so nothing can be read right now.
  • Signal unavailableThe vehicle did not answer for this signal during negotiation.
  • Vehicle support unverifiedNobody has proven this reading on this vehicle yet.
  • Feature not yet releasedThe reading is designed and not in the closed-test build.

The app itself

What it actually looks like.

Two screenshots of the current build, cropped to the part that matters, and one panel drawn on this page to show the shape of a comparison. The panel is a drawing, not a screen.

The Torkmark dashboard on a phone: a coolant panel above a grid of nine reading tiles, every value shown as a dash because no adapter is connected.
The dashboard Every reading on one screen. Coolant leads, unless a reading has gone past a limit you set, and then that one takes the top. Here nothing is connected, so every tile shows a dash rather than a number. Cropped capture, sample data from the current build
A work entry in the Torkmark build log showing brand, part number, category, installed date, odometer at install and cost.
A work entry What went on the vehicle, when, at what mileage and what it cost. Changing the status commits a new version and keeps the one it replaced. Cropped capture, sample data from the current build

Illustrative example — sample data

Before

214 °F

Peak coolant, most recent drive before the work

The work

Fan clutch replaced

2 April 2026 · 79,404 miles

After

203 °F

Peak coolant, most recent drive after the work

The shape of a comparison Drawn on this page rather than taken from a screen, because a comparison needs drives on both sides of a change and this build has none to show. Every figure in it is made up.

Where it lives

On your phone, and what that costs you.

Your recorded readings upload to your account; your build history, drive summaries, trouble codes and settings stay on your phone.

ExportExport your build history from the app as readable text through the Android share sheet. The export covers the build history only, not your recorded readings.
No import, yetThere is no backup, import or phone-to-phone transfer today. Export your build history before changing or wiping a phone.
UninstallingUninstalling removes your build history and drive summaries from the phone, and there is no server copy to restore them from. Uploaded readings stay in your account until you ask for deletion.
During alphaReadings recorded during alpha may be reset before launch. You will be told before that happens.

No ads, no third-party analytics, and your data is not sold. The privacy policy sets out what is held, where, and for how long.

Designed, not built

What is not here yet.

Named so you can weigh it, not sold. Nothing in this section is in the closed-test build, and none of it has a date.

Settings changesOwner-accessible settings changes, each with the prior value captured first, are designed and not built. Torkmark reads your vehicle and does not write to it.
More reading categoriesA wider set of reading categories is designed and not yet in the closed-test build.
Module-level readsModule-level reads are planned and are not in the closed-test build.
A buyer-facing recordA buyer-facing record is planned and not built.

Early access

Request early access.

Email the Google account you use with Google Play. That address goes on the tester list and the reply carries the Play opt-in link. Signing in does not enrol you.

The full detail — who can join, what you need, what it costs today — is on the home page access section.

Email my access request