STINT← Back to STINT
STINTGPS Racing Watch · User Manual
© QSTARZ · v1.17STINT GTM · GPS Racing Watch
User Manual
STINT
One watch, five track personalities. Turn every drive into data you can replay, compare and share.
Display
240 × 240 round display
Modes
5 racing modes
Sensing
GPS + RaceBox
Manual version v1.17 (2026-09-24)
Model  STINT GTM (GPS Racing Watch)
Firmware  as shown on the watch’s Settings → About page (VER)
ℹ For editors: The retail product name is now STINT GTM (brand STINT, model GTM, signed off 2026-09-02) and has been filled in throughout. The remaining [Companion App] for the mobile app name; replace them globally with the real names before publishing. All screen images are engineering renders from the device (generated from the actual firmware drawing code and fonts, not photos/screenshots); text and layout match the real device, but physical details such as the case and screen reflections are not shown.
How to Use This Manual
!Tip boxes: behaviors worth knowing up front — reading them once saves you trouble.
Walkthrough
Paragraphs in this style walk you through one task end to end (for example, your first acceleration run).

Contents

  1. ! Safety & Legal Notice
  2. 01 Know Your STINT GTM
  3. 02 Quick Start (5 min)
  4. 03 Power · Off · Charge · PC
  5. 04 The Watch Face
  6. 05 Main Menu
  7. 06 Racing (Core Feature)
  8. 07 GPS Auto Lap
  9. 08 Standing-Start Drag
  10. 09 View & Manage Records
  11. 10 Settings
  12. 11 App & Device Connection
  13. 12 FAQ & Tips
  14. 13 Appendix
Safety & Legal

Safety & Legal Notice

Read this chapter carefully before use. Using this product means you understand and agree to the following.

01
Know Your Watch

Know Your STINT GTM

The STINT GTM is a GPS Racing Watch built for driving and track enthusiasts. It records your acceleration, lap times, mountain-road and off-road performance and saves each session’s track, speed and G-force (lateral / accel-brake) in full for later review on the watch, mobile app or computer. Day to day it is also an everyday watch with time, alarm, compass, barometer and heart rate.

1.1 Parts & the Four Buttons

The watch has a 240 × 240 full-color screen, four physical buttons and a backlight button that doubles as LAP during sessions.

ButtonGeneral use
UPMenu up, increase value, page
DOWNMenu down, decrease value, page
OKEnter, confirm, select
BACKBack, cancel
BacklightA short press turns the backlight on (it goes off after the AUTO OFF time); a long press keeps it on for the LONG PRESS time (default 3 min), and a short press during that time turns it off at once (see 10.2). On session screens it also acts as the LAP button (DAILY DRIVE and TOUGE don’t record laps); the backlight still toggles on or off when you press it

Button basics: most actions are a short press (press and release). A few need a long press; how long depends on the function (e.g. backlight ~1 s, ending a session ~2 s, power off ~5 s), and this manual clearly notes it.

1.2 Three GPS Sources

Sessions can use three positioning sources, freely switchable in Settings:

SourceCharacteristicsBest for
RaceBox Mini
(external)
High-precision GPS over Bluetooth, the highest update rate, with a built-in G-force sensor (measured)Users who want the most complete data (splits, G-force)
Built-in GPSBuilt into the watch, no accessory, ready at power-on. Lower update rate; in MAX mode the watch derives G-force from GPS (see below)When you want to travel light
Qstarz logger
(external)
A Qstarz GPS logger over Bluetooth (BL-1000GT / 818GT), no pairing — select it and it connects (moderate update rate, no G-force shown on the watch)Users who already own a Qstarz device and want to keep using it
Where each source’s G-force comes from
SourceG-forceNotes
RaceBox MiniMeasuredMeasured directly by the device’s built-in accelerometer, all three axes, highest accuracy.
Built-in GPS (MAX)GPS-derivedThe watch derives lateral and longitudinal G-force from changes in GPS speed and heading; it is shown live and stored in the record. Vertical G cannot be derived (fixed at 0). Low speeds are skipped automatically because accuracy is insufficient: below 2 km/h neither axis is counted, and between 2–10 km/h only the longitudinal axis (accel/brake) is.
Built-in GPS (ECO)NonePower-saving mode logs only 1 sample per second — too sparse to derive reliably, so it is not offered.
QstarzNot on the watchQstarz devices do have a sensor, but their mounting orientation is unverified, so the watch does not use it; the mobile app derives G-force from the track itself.
!Derived vs. measured GPS-derived G-force is good enough to show the overall trend (lateral correlation with measured RaceBox data is about 0.79), but it is not a direct measurement, so the numbers will not match a RaceBox exactly and are not suitable for precise comparison. For the most accurate G-force, use a RaceBox Mini.
02
Quick Start · 5 min

Quick Start (5 min)

Just got your watch? Follow these steps to make your first recording.

  1. Charge & power on Clip the supplied charging clip onto the watch body and charge it fully (while charging, the watch is in charging mode and cannot be operated). After you unplug the charger it powers on automatically, briefly showing the boot screen before the watch face.
  2. Set time & basics (face → OK → SETUP → System Settings)
    • Time: go to Time → Set Time and choose GPS SYNC, then go to an open outdoor area and wait for a fix — the time sets automatically. With no GPS signal you can also use MANUAL SET (see 10.2).
    • Language: English / Traditional Chinese / Simplified Chinese.
    • Units: metric or imperial for everyday display. (Racing speed units are set separately in Racing settings.)
  3. Choose a GPS source (SETUP → SET GPS)
    Start simplest: choose INTERNAL GPS — no pairing needed.
  4. Record your first session (face → OK → RACING)
    The watch searches for a fix → choose DAILY DRIVE → when the GPS dot turns green press OK to start → to finish hold BACK ~2 s; the screen shows Saving... and the session is saved.
  5. Review it Back at the watch face, press DOWN for the Racing overview — top speed, distance and more. For per-session detail go to face OK → RECORDS.

Done! The following chapters explain each screen one by one.

03
Power · Charge · Connect

Power · Off · Charge · PC

3.1 Power On
When
Powers on automatically when the charger is unplugged (while the charger is connected the watch stays in charging mode with no boot screen, see 3.3); or, depending on model, follow the on-screen prompt to power on from off.
Display
Black background with the brand boot logo centered.
Buttons
Buttons do nothing during the boot screen.
Exit
About 4 s later it enters the watch face automatically — no action needed.
開機畫面
Boot screenBrand boot logo
iThe picture above is the old boot screen. On STINT GTM firmware the boot screen shows a white STINT wordmark with an orange GTM (the About page logo is the same). New screenshot to come.
3.2 Power Off
When
At the watch face, hold BACK ~5 s.
Display
No power-off screen: the display simply goes dark and power cuts.
Buttons
Buttons do nothing during power-off; it cannot be canceled.
Exit
Power on again to return.
關機畫面
Power-off screenDisplay goes dark
3.3 Charging & PC Connection (USB)
When
Plug in the charger while on and the watch switches to charging mode (it reboots briefly). While recording (a session or FreeTilt), end and save the recording before connecting the charger.
Display
Battery %, charge icon, date and time (the colon blinks every half second). Press UP/DOWN for the battery detail page.
PC
When connected to a computer it appears as a USB flash drive; open the RACELOG folder to copy your session logs (see Chapter 11).
Exit
On the charging screen OK/BACK do nothing; unplug the charger to reboot back to the watch face.
充電畫面
Charging screenBattery & time
電量詳細頁
Battery detailCharge status / current / voltage / charge stage
!Tip After the level reads 99%, continued charging for a while shows 100% — normal fail-safe behavior.
3.4 Firmware Update
When
Start a firmware update from the [Companion App]. Before starting, return the watch to the watch face and make sure the battery is at 30% or more; otherwise the watch refuses to start the update (the app tells you why).
Display
First FW upgrading / Do NOT turn off watch appears (buttons locked — do not operate or cut power). The watch then reboots on its own and writes the new firmware, showing progress as a percentage; when done it shows FW upgrade complete (no boot screen this time).
Exit
On the update-complete page press OK to enter the watch face.
韌體升級中
Firmware upgradingDo-not-power-off notice
韌體更新完成
Update completePress OK for the watch face
▲Caution Do not cut power or unplug the charger during the update, to avoid a failed firmware write.
04
The Watch Face

The Watch Face

The watch has several switchable faces (see 10.2 System Settings to switch). Whichever you choose, the buttons work the same; which information appears depends on the face (see 4.4). This chapter covers the common operations and uses the classic faces as the example in 4.1.

4.1 Information on the Watch Face
數位錶面
Digital face
指針錶面
Analog face
iThe two pictures above still show the old Crest logo at the bottom; on current firmware neither classic face shows it, and the rest of the layout is unchanged. New screenshot to come.
4.2 Watch-Face Four-Button Table (the one you’ll use most)
ButtonShort pressLong press
OKEnter the main menu—
UPEnter FreeTilt (TILT); keep pressing up to cycle info pages (see 4.3)—
DOWNEnter the Racing overview—
BACKRefresh Bluetooth connectionPower off (hold for about 5 s; it does not power off while the charger is connected)
4.3 Info Page Carousel (press UP at the face)
Face → TILT (FreeTilt) → Compass → (HR monitor*) → Barometer → HR info → back to face
指南針
Compass
指南針校正
Compass calibration
氣壓圖
BarometerRecent trend
心率監控頁
HR monitor*must enable

Heart-rate monitor (*): appears only after System Settings → Heart Rate → HR Monitoring is enabled; shows a 4-hour heart-rate bar chart and live heart rate, returning to the face after ~60 s of inactivity.

4.4 Watch Faces and Switching

The watch ships with 8 watch faces in three groups: 2 Classic (the previous look), 4 Achievement (your cumulative results shown right on the face, see 4.6) and 2 Minimal (time and battery only). In the settings preview, achievement faces are labelled with the name shown in brackets (see “How to switch” below).

FaceGroupWhat it shows
Classic DigitalClassicLarge time (12/24-hour), weekday and date, battery gauge, and the Racing signature line (see 4.1).
Classic AnalogClassicTraditional dial with hour and minute hands, plus weekday, date, battery gauge and the Racing signature line (see 4.1).
Triple Stack
(OVERVIEW)
Default
AchievementTime, date and battery stay primary; below them lifetime distance, drives and today’s top speed sit side by side — the one to pick when you want everything at a glance. The default face on a new watch and after a factory reset (a watch upgraded from firmware without achievement faces keeps its classic face).
Odometer
(ODOMETER)
AchievementShows lifetime distance in an automotive odometer style, with drives and today’s top speed in small type below.
Racing Analog
(RACE DIAL)
AchievementAnalog dial with a band at the bottom showing lifetime distance, drives and today’s top speed (hour and minute hands in white and yellow).
Milestone
(MILESTONE)
AchievementShows your current distance, the next milestone target and a progress bar (see 4.6).
Pure AnalogMinimalDial markers, hands and battery only — no date, weekday or achievement data.
Pure DigitalMinimalLarge HH:MM and battery only; 12/24-hour follows your setting.

How to switch: main menu → SETUP → System Settings → Watch face (see 10.2). Inside, UP/DOWN steps through the previews (the preview is the real appearance; before you have any achievement data, an achievement face’s preview shows its name in the centre, e.g. OVERVIEW, instead of READY TO RACE), OK saves and applies, BACK discards. The list does not wrap — pressing UP on the first face or DOWN on the last will not jump to the other end.

!The classic signature line is not lifetime data The Racing signature line on both classic faces (Classic Digital and Classic Analog) keeps its previous meaning and covers only the newest 10 records in RECORDS; achievement faces show lifetime totals (see 4.6). It is normal for the two numbers to differ.
iScreenshots of the 8 faces are not included yet; they will be added once the designs are final.
4.5 FreeTilt (TILT)

FreeTilt is a GPS-free quick tilt tool: clamp the watch to a roll cage or dashboard at any angle, zero it once, and from then on you can see how far the vehicle is tilted relative to level — useful for levelling when parked and for judging slopes. Unlike ordinary inclinometers, you do not have to align the mount (Mount & Go).

FreeTilt screen
FreeTiltHorizon + R/P · hold BACK 1 s to re-zero
iThe picture above shows an earlier layout. On current firmware the R and P values sit in the upper half of the screen, and below them come the reference age (ZERO 5m) and then the BACK 1S: ZERO hint. New screenshot to come.
4.6 Achievement Data (the numbers on achievement faces)

Achievement faces (see 4.4) show two lifetime figures — lifetime distance and drives — plus today’s top speed. The lifetime figures are not limited to the last 10 sessions — deleting one record or all records in RECORDS keeps the totals (for the clearing options in SETUP, see 10.6).

ItemMeaning
Lifetime distance
(TOTAL KM / MI)
The sum of the distance of every session record, accumulated from when you started using this feature.
Drives
(DRIVES)
How many times you have pressed OK: START and completed a drive. One drive counts once — even if a very long recording is split automatically into several records (see 6.5), it still counts as 1.
Today’s top speed
(TODAY MAX)
The highest speed reached today, based on the watch’s local date; it resets automatically at midnight.
Milestones

The Milestone face shows how far you are from your next target. The steps are:

100 → 250 → 500 → 1,000 → 2,500 → 5,000 → 10,000 → every 5,000 after that

After you cross a milestone, the next time you return to that face (for example from the main menu or the info pages) it shows a MILESTONE! congratulation once, then switches to the progress toward the next target. Switching between KM and MI does not trigger a false congratulation.

!Watches upgraded from an earlier version The previous version kept only the last 10 sessions, so a true lifetime distance cannot be reconstructed; old records are not imported after the upgrade — lifetime distance and drives start counting from your first drive afterwards. Your existing records stay in RECORDS untouched.
iFor how achievement data behaves under the various clearing operations, see 10.6 “Reset and About”.
05
Main Menu

Main Menu

Press OK at the watch face to open the main menu. It has 3 items and shows one at a time; UP/DOWN cycle, OK enters, BACK returns to the face (the dots at the bottom show which item you are on).

ItemDescriptionGo to
RACINGStart a session (connect and go)Chapter 6
RECORDSBrowse per-session detailChapter 9
SETUPGPS, Bluetooth, units and moreChapter 10
RACING
RACING
RECORDS
RECORDS
SETUP
SETUP
06
Racing · Core Feature

Racing (Core Feature)

This is the heart of the watch. A complete Racing flow is:

Menu RACING → connect / find sats → pick mode → (DRAG: pick method / LAP TIMER: pick lap mode) → standby → start recording (Live)
6.0 Key Concepts (read before you start)

This section clears up the logic and terms most often misunderstood. Two minutes here saves a lot of trouble.

BUTTON lapping: laps are counted by your button press, not auto-detected
▲With BUTTON lapping, LAP TIMER does not automatically detect whether you crossed the start line. On each lap, press OK (or the LAP button) yourself — every press ends the previous lap and starts timing the next. The watch computes each lap time and the gap to your best, but when a lap counts is decided by your press. To have the watch count laps automatically, choose GPS AUTO when entering LAP TIMER (see Chapter 7).
What each of the five modes measures
Don’t pick the wrong DRAG method
!STANDING starts from a stop, ROLLING from motion — they can’t be compared directly, and the wrong method gives nonsensical numbers.
How best / slowest lap is decided

In the detail page, green (best) marks the shortest of all completed laps in that session; orange (slowest) marks the longest — not the first or last lap. The GPS AUTO warm-up and an unfinished final part-lap at save time are left out, and laps flagged for problems such as lost GPS are never picked as best.

The real ceiling on sample rate

Actual density = min(your set sample rate, the source’s real update rate). Built-in GPS and Qstarz have a far lower ceiling than an external RaceBox, so raising the sample rate does not truly refine the data — this isn’t a failed setting or a fault.

Switching GPS source isn’t instant

Switching source in SET GPS (between RACEBOX / INTERNAL GPS / QSTARZ) saves immediately, but takes effect only the next time you enter Racing; the current session keeps the source locked in at its start, and changing it in the app mid-session has no effect.

Long sessions split automatically

When a session fills up (depending on the actual sample rate: about 45 minutes at 25 Hz, 1.9 hours at 10 Hz, 3.75 hours at 5 Hz), the watch saves automatically and carries on in a new session: Saving... shows briefly with one long beep, and the timer and distance reset while the lap count carries on. Nothing else tells you a new session has begun; if a recording seems shorter than expected, this is why. MAX REC (see 6.4, Step 5) counts the whole run: even though the on-screen timer resets after a split, the automatic end still goes by the total time. Because MAX REC is at most 4 hours, at an actual sample rate of 2 Hz or less (including DAILY DRIVE, fixed at 1 Hz) a session never fills before it ends, so it is never split.

The speed-unit exception

Most screens follow RACING → SPEED UNIT (km/h ↔ mph), but these stay fixed in km/h and do not convert: speed on the LAP TIMER detail page, and the QUARTER MILE split thresholds (0–60 / 0–100 / 0–160 km/h; the 0-100 KM/H on the DRAG dial layout too). STANDING, by contrast, switches to mph thresholds with the unit (see 6.6).

6.1 Choosing a GPS Source
iNone of the three sources needs pairing Just pick the source and switch the device on nearby; nothing has to be set up in the app beforehand.
!Tip After switching source it takes effect the next time you enter Racing; the current session keeps the source it started with.
6.2 Using the RaceBox Mini

The RaceBox Mini does not need pairing — when the watch enters Racing it searches for a nearby RaceBox and connects to whatever it finds.

  1. Switch on the RaceBox Mini and put it in the vehicle (make sure it is charged).
  2. Set the watch’s GPS source to RACEBOX (see 10.1).
  3. Enter Racing; the watch shows Connect to GPS Devices... and connects automatically, then goes straight to the mode list.
▲When several RaceBoxes are nearby The watch connects to the first one it finds, which is not guaranteed to be yours. At track days and other shared events, switch on only your own device — the watch does not show which unit it connected to.
iIf no device is found, the watch reports it after about 5 minutes and returns to the face (see 6.7). Check that the RaceBox is on, charged and near the watch.
6.3 The Five Racing Modes
ModePurpose
DAILY DRIVEEveryday driving log, lightweight throughout
DRAGStraight-line acceleration (0–100, 100–200, 1/4 mile, etc., by method; pick a method after selecting)
LAP TIMERCircuit lap times, recording each lap (pick lap mode BUTTON / GPS AUTO after selecting)
TOUGEFree mountain-road runs
OFF-ROADOff-road, records body tilt (shown in detail afterward)
6.4 Starting a Session (step by step)
Step 1: Connect / find satellites

From the main menu choose RACING; the watch prepares according to your GPS source:

連線 RaceBox
Connecting RaceBox
搜尋內建 GPS
Searching built-in GPSFix progress
!Tip Search for satellites outdoors with open sky, away from tall buildings, tree cover and garages. The first fix, or one after a long gap, takes longer.
Step 2: Choose a mode

In the mode list use UP/DOWN to choose and OK to select. If you pick DRAG, next choose a method (see 6.6); if you pick LAP TIMER, next choose the lap mode, BUTTON (manual) or GPS AUTO (automatic, see Chapter 7). BACK drops the connection and returns to the main menu. If the mode list or the DRAG method screen sits for 5 minutes with no button pressed, the watch returns to the face.

DAILY
DAILY DRIVE
DRAG
DRAG
LAP
LAP TIMER
TOUGE
TOUGE
OFF-ROAD
OFF-ROAD
Step 3: Standby

The standby screen shows the mode name (abbreviated, e.g. DAILY; LAP TIMER appears as CIRCUIT; DRAG also shows the method), a speed preview, the mount (WRIST / VEHICLE), the current time and a GPS status dot (green = fix / yellow = external device connected but no fix yet / gray = source not ready).

待命畫面
Standby
存檔畫面
SavingTriggered by holding BACK
iThe standby screenshot above is the old screen: the current screen also shows WRIST / VEHICLE on the speed-unit line (plus the battery at the left with a RaceBox). New screenshot to come.
iMOUNT When MOUNT in the RACING settings is set to VEHICLE, the standby page shows VEHICLE in yellow (WRIST in gray when set to WRIST), and pressing OK first brings up a mount confirmation page (below) — check that the watch is fixed to the vehicle (face up is best) and press OK again to actually start. With WRIST (the default) it starts straight away.
iThe readiness line on the confirmation page Besides the SECURE WATCH / TO VEHICLE prompts, the confirmation page carries a live status line telling you how the tilt reference is coming along:
• GPS NOT READY (red) — the GPS source isn’t ready yet.
• HOLD STILL... (orange) — it is collecting stationary samples; keep the vehicle still.
• READY (green) — the reference is captured; you can go.
Only built-in GPS with MOUNT=VEHICLE has to wait for this; RaceBox, Qstarz and wrist mode report ready immediately. Pressing OK once it reads READY gives the most accurate tilt; if the vehicle moves again after that, the status drops back to HOLD STILL... and collection restarts. You can still press OK early once GPS is ready — the tilt reference for that session then has to be captured after the start instead (see 6.6).
VEHICLE MOUNT confirmation
VEHICLE MOUNT confirmationAppears when MOUNT=VEHICLE
Step 4: Start recording (Live)

Go! The Live dashboard shows your performance in real time (next section).

Step 5: Finish and save

Hold BACK ~2 s; the screen shows Saving... → saved → back to standby, ready to record another session.

The watch can also end and save a session by itself: it shows Saving..., then green SAVED with a yellow reason line, and after about 3 seconds (or any button) returns to standby.

Yellow reasonWhen it happens
TIME LIMITRecording time reached the MAX REC setting (default 1 hour; 30 min / 2 h / 4 h available, see 10.3)
NO MOVEMENTWith a fix, the watch stayed within about 30 m for 20 minutes in a row
LOW BATTBattery below about 3.5 V (it has to persist for about 10–15 s)
▲Recording longer? Change MAX REC before you set off By default a session ends automatically after 1 hour, and there is no “unlimited” option — it is the last safety net if you forget to stop. For endurance events or long mountain runs, set MAX REC to 2 H or 4 H on page 3 of SETUP → RACING first.

When a session file fills up, the watch splits it automatically (see 6.0): Saving... shows briefly (about 2–6 s) and recording carries on. If 300 records are already stored or space runs out at that point, no new part is started — the part just saved is kept, and the watch returns to standby showing STORAGE FULL.

!Tip Moving between connection and mode selection doesn’t reconnect; only pressing BACK in the mode list truly disconnects and returns to the main menu.
6.5 The Live Dashboard

The real-time screen while recording, showing the most relevant info per mode. Common elements:

ButtonAction
OK / LAP buttonMark a lap (LAP TIMER with BUTTON, QUARTER MILE, OFF-ROAD; in QUARTER MILE it also resets the screen to STAGED); in ROLLING, OK starts the countdown; no effect in DAILY DRIVE and TOUGE
OK (STANDING)Arm; press again while armed = disarm; on the result screen = dismiss the result (see Chapter 8)
OK / LAP button (GPS AUTO)OK has no effect; LAP sets the start/finish line while none is set, then adds a lap manually (see Chapter 7)
BACK short pressDuring a ROLLING sprint = abort the run; in STANDING, while armed = disarm, mid-sprint = keep the run as INCOMPLETE (see 8.3), on the result screen = dismiss the result; otherwise no effect
BACK hold 2 sSave and end the session, return to standby
UP / DOWNIn OFF-ROAD with MOUNT=VEHICLE, switch between the artificial horizon and the layout chosen in SCREEN LAYOUT; otherwise no effect
Live Daily
Live · Daily
Live Touge
Live · Touge
Live 通用
Live · Generic
!Tip The LAP button is the backlight button, so marking a lap also toggles the backlight on or off. A long press never clears data (that function is disabled to prevent accidents); it just keeps the backlight on for the LONG PRESS time (see 1.1). To end recording use “hold BACK.”
!Tip For very long sessions (e.g. tens of minutes at a high update rate), the watch splits and saves automatically, starting a new session, resetting timer and distance while the lap count carries on; Saving... shows briefly with one long beep. This is normal protection (see 6.0).
A different view: SCREEN LAYOUT

Every mode’s Live screen offers three layouts (A/B/C) — the data in the record is the same, only the presentation changes. Set it per mode in SETUP → RACING → page 3, SCREEN LAYOUT (see 10.3); it applies from the next session. Exceptions: in DRAG only QUARTER MILE uses A/B/C (STANDING has its own screen, ROLLING uses the generic screen), and LAP TIMER with GPS AUTO always uses the generic screen.

ModeA (default)BC
DAILYDashboardTrip stats (2×2 cells)Route breadcrumbs
DRAGDashboardChristmas treeAnalog dial (0–100 time)
LAPLarge speedLap listCircuit trace
TOUGEDashboardG-G friction circleElevation profile
OFF-ROADAttitude display (pitch/roll; readings with a RaceBox source only)Large compassTool grid (several values side by side)

Pressing OK in the SCREEN LAYOUT list opens a live preview that draws the layout with sample data, so you can confirm before applying.

SCREEN LAYOUT submenu
SCREEN LAYOUTPick A/B/C per mode
iWith MOUNT=VEHICLE, OFF-ROAD first shows an artificial-horizon layout; press UP/DOWN to switch to the A/B/C chosen above (see 6.6).
6.6 Mode Highlights
DRAG (straight-line) — three methods

After choosing DRAG, pick a method (your last choice is remembered):

MethodMeasures
STANDINGSplit acceleration from a standstill (0–100, 100–200, and 200 to the run’s top speed, km/h; with the speed unit set to mph: 0–60, 60–120, and 120 to top speed); full steps in Chapter 8, Standing-Start Drag
QUARTER MILE1/4 mile: 0–60, 0–100, 0–160 (always km/h), plus 1/4-mile time and trap speed
ROLLINGRolling acceleration: press OK for a 3-2-1 countdown → GO → lift off to finish automatically
STANDING
STANDING
QUARTER MILE
QUARTER MILE
ROLLING
ROLLING
OFF-ROAD artificial horizon
OFF-ROAD horizon layoutRed dot = recording · green dot = GPS ready
Walkthrough

Complete your first DRAG run

  1. Set units: SETUP → RACING → SPEED UNIT, pick KM/H or MPH.
  2. Choose source: confirm the GPS source (SETUP → SET GPS); RaceBox is recommended for complete data.
  3. Start: face OK → RACING, go outdoors and wait for a fix.
  4. Pick mode: choose DRAG → OK, then a method (STANDING for the first time).
  5. Standby: wait for the GPS dot to turn green, press OK to start.
  6. Accelerate: on a safe, legal straight, go full throttle; the watch captures each split automatically.
  7. Finish: hold BACK 2 s to save.
  8. View results: face OK → RECORDS, pick the session, page through for best times and the acceleration curve.
▲Always run acceleration tests on a legal venue, mindful of safety and speed limits.
6.7 GPS Fix & Wait Times
Why is entering racing mode sometimes instant and sometimes a wait?

Racing mode records your speed and route, so the watch must first “find satellites” and get a fix. On entry the screen shows search progress — percent complete, signal strength, satellites found and elapsed seconds. The moment a fix is obtained, the watch automatically goes to mode selection.

CR RACING GPS Searching... 45% S:32 N:5 8s Fix progress Near 100% means a fix is close Signal strength Higher is better Satellites found Usually 4+ needed for a fix Elapsed time Seconds since this screen opened
The four fields on the search screen (screen text is an engineering render)
How long you wait depends on how long since last use

The watch remembers its last fix, so the more recently you used it, the faster next time. Just remember two numbers: 5 minutes and 4 hours:

5 min4 hr Almost no waitGPS still activeA few secondsQuick re-fix on wakeTens of seconds+Re-downloading sat data
Since last useTypical waitWhy
Within 5 minAlmost noneGPS still active, satellites tracked continuously
5 min – 4 hrA few secondsGPS asleep but remembers satellite positions; re-fixes quickly on wake
Over 4 hr, or just powered onLonger, possibly tens of secondsStored satellite data has expired and must be re-downloaded
Environment matters more than time
✓Open skyFastest !Buildings · trees · in-carSlower ✕Indoors · undergroundUsually no fix
▲Without a signal the watch stays on the search screen and will not start a session. This is deliberate: starting without a proper fix would record inaccurate results. If nothing is found (up to 20 minutes), the watch reports no GPS and returns to the face.
CR RACING GPS not found returning...

Watch stuck searching? First check whether you’re indoors or obstructed — moving to open sky usually fixes it.

(With an external device, the second line shows RaceBox or Qstarz instead of GPS.)

GPS doesn’t shut off immediately after you leave racing mode

So you don’t wait repeatedly between sessions, GPS keeps running for 5 minutes after you leave racing mode. Re-enter within that window and the next session starts with almost no wait. After 5 minutes idle, GPS shuts off to save power.

When using an external device

With an external device (RaceBox / Qstarz) you wait for a Bluetooth connection rather than a satellite search: the watch looks for a nearby RaceBox and, once connected, goes to mode selection. If none is found within 5 minutes it reports no device and returns to the face. (No pairing is needed — just switch the RaceBox on nearby.) The GPS source is switched in SETUP → SET GPS, where you can also set built-in GPS precision.

Tips
6.8 Session Alerts (tone + vibration)

Key events during a session are announced with a tone and vibration, so you don’t have to watch the screen:

EventAlert
GPS source ready (connected / fix obtained)Two short beeps + short buzz
ROLLING arm / countdown / GO / finishTwo short beeps + short buzz (each stage)
Lap marked (OK / LAP button)Two short beeps + short buzz
Saved successfullyOne long beep + short buzz
Save failedTwo long beeps + long buzz
Long recording split automaticallyOne long beep (soft notice)
Automatic end (TIME LIMIT / NO MOVEMENT)One long beep + short buzz
Automatic end (LOW BATT)Two long beeps + long buzz
200-lap limit reachedOne long beep + long buzz; marking a lap after that: two long beeps + short buzz
STANDING: OK pressed to arm (accepted or refused)One short beep + short buzz
STANDING result readyTwo short beeps + short buzz
GPS AUTO: lap counted automaticallyTwo short beeps + short buzz
GPS AUTO: CHECK LAP shown (see Chapter 7)One long beep + two buzzes
GPS source lost / restored in Racing (with built-in GPS: fix lost / regained; also on standby and the mode list)Lost: two long beeps + long buzz; restored: two short beeps + short buzz
Mobile app connected / disconnectedConnected: one long beep + short buzz; disconnected: two long beeps (on any screen)

Tone and vibration can be switched separately: ALERT TONE / ALERT VIB under SETUP → RACING (both on by default, see 10.3). The two switches govern the events in the table above, including the app connection alerts, except the four STANDING and GPS AUTO rows, which still beep and buzz with the switches off.

07
GPS Auto Lap

GPS Auto Lap

7.1 What Is This?
CIRCUIT 選擇 BUTTON 或 GPS AUTO

In circuit mode (CIRCUIT) the watch can count laps for you. Set the start/finish line once at the start, and every time you cross it the watch logs the lap number and lap time automatically — no more looking down to press a button.

To enter: Menu → CIRCUIT → choose GPS AUTO.

To keep traditional button lapping, choose BUTTON — it works exactly as before.

7.2 Getting Started: Set the Start/Finish Line

After recording starts the screen shows SET START LINE. There are two ways to set the line:

Method 1 · On the move (recommended)

Start/finishPress LAP as you cross
Press LAP as you cross the spot you want; the watch builds a start/finish line perpendicular to your direction of travel.

Method 2 · At a standstill

Start/finishLaunch directionPress LAP on the line; auto-corrects after launch
Stop on the spot and press LAP; after driving a short distance (about 10–20 m) the watch auto-corrects to your launch direction.
Method 1On the move

As you ride/drive across the spot, press the LAP button once. The screen briefly shows SETTING... and it’s done.

SETTING 行進中設定
SETTING...Set on the move
Method 2At a standstill

Stop on the start/finish spot and press the LAP button once; the screen shows CALIBRATING. Calibration completes once you set off. Note: lap 1 is timed from the moment you press LAP, so time spent waiting on the line is included in lap 1 — press it when you are ready to go.

CALIBRATING 靜止設定
CALIBRATINGStandstill calibration
SET START LINE 尚未設線
SET START LINERecording, line not set yet
AUTO LAP 自動計圈啟動
AUTO LAPSet; auto lap armed
iOnce set, the top of the screen shows AUTO LAP and the large figure changes from WARM UP to the lap you are currently on (1 for the first lap), meaning auto lap is armed.
!Press LAP only once when setting the line While the screen still shows SETTING... or CALIBRATING, don’t press LAP again: doing so resets the start/finish line to where you are at that moment, with no separate notice. Wait until AUTO LAP appears.
iThe auto-lap screenshots in this chapter are design mock-ups and differ from the watch: on the watch the top status text is grey (LAP MARKED and CHECK LAP are yellow), the large figure shows WARM UP or the current lap number (not LAPS 0), crossing notices such as LAP N appear at the bottom of the screen, and the estimate symbol is ~. New screenshots to come.
7.3 How Auto Lap Works
AUTO LAP 正常完成一圈 LAP 3
  • Each time you cross the line from the correct direction, a lap completes automatically: the watch beeps and vibrates and shows the lap number and lap time.
  • The line is directional: crossing it the wrong way or passing on a parallel road won’t trigger a false lap.
  • Crossings below about 5 km/h (near walking pace) don’t trigger a lap, avoiding false counts from GPS drift while stopped. There is no alert for such a crossing, and the laps either side merge into one long lap — press LAP as you cross if you need it counted.
  • For a short time after a lap, it won’t count again — fine even on small karting circuits.
7.4 Manual Lap

If a lap isn’t detected automatically (e.g. a brief GPS dip), press the LAP button as you cross to mark it manually; the screen shows LAP MARKED.

  • If the watch detects that same crossing within about 2 seconds of your press (about 3 seconds with built-in GPS · ECO), it uses the GPS crossing time instead — no double count. After that window, the lap is recorded at the moment you pressed.
  • Don’t press LAP after the watch has already counted the lap: about 2 seconds later (about 3 s in ECO) an extra, very short lap is added, and that lap becomes the best lap.
LAP MARKED 手動補圈
LAP MARKEDManual lap logged
7.5 Buttons (CIRCUIT · GPS AUTO mode)
ButtonFunction
LAP short pressBefore the line is set: set start/finish. After: manual lap
OKNo effect (prevents mis-press; use BUTTON mode for manual lapping)
BACK hold 2 sStop and save the session
7.6 On-Screen Status Text
DisplayMeaning
SET START LINEStart/finish not set; press LAP to set
SETTING...LAP pressed; building the line from the next GPS sample
CALIBRATINGNot enough direction data yet (e.g. set at a standstill); completes after about 10–20 m of driving
AUTO LAPAuto lap running
WARM UP (large figure)Line not set yet; after setup it shows the lap you are currently on
LAP N + lap timeLap complete
~ LAP N + lap timeLap complete, but the time is estimated
EST LAP N/NO BESTLap complete, but high uncertainty; excluded from best lap
LAP MARKEDManual lap logged; recorded as a lap after about 2 s (about 3 s in ECO)
CHECK LAPConfirming a crossing with a large GPS gap, or a possible missed pass was detected
Connection lostExternal GPS (RaceBox / Qstarz) disconnected; replaces the top status and lap number. Recording continues and it recovers on reconnection

LAP N, ~ LAP N and EST LAP N are notices shown for about 3 seconds after a crossing, at the bottom of the screen (temporarily in place of the total time). CHECK LAP appears at the top while confirming, and also at the bottom when a possible missed pass is flagged. The rest are status words at the top.

7.7 Lap-Time Confidence Markers

GPS signal quality affects crossing-time precision. The watch honestly reports the confidence of each lap:

估算圈 ≈ LAP 3
~ EstimatedSlight estimate · still counts for best
高不確定圈 EST LAP NO BEST
EST · NO BESTExcluded from best
CHECK LAP 可能漏圈
CHECK LAPPossible missed pass
7.8 Stopping & What Gets Recorded

After holding BACK to stop, the watch returns to standby and briefly shows SAVED and the session’s counted lap total (N LAPS). The record file contains:

SegmentDescription
Warm-up (before the line is set; the screen shows WARM UP)Track before the start/finish line is set: kept in the record file but not an official lap, and not listed in the RECORDS lap list
LAP 1...NCompleted official laps
PARTIAL (listed as L-- / PART)The unfinished segment from the last crossing to stopping: saved as a separate record, not a formal lap, and never chosen as the best or worst lap. Not saved once 200 counted laps are reached

In the RECORDS detail summary, LAPS counts official laps only and the best lap is chosen from them; KM and TIME cover the whole session, including warm-up and cool-down.

Lap limit per session

Each session records at most 200 counted laps (GPS auto lap keeps one warm-up record besides that, so a file holds at most 201). Once you reach the limit:

i200 laps is far more than a normal track day needs. If you do fill it and want to keep timing laps, hold BACK to close the session and start a new one.
7.9 GPS Modes & Precision
GPS sourceSample rateBest for
RaceBox (external)25HzTrack days demanding top precision
Qstarz (external)10HzWhen using a Qstarz external GPS
Built-in GPS · MAX5HzGeneral circuits and karting
Built-in GPS · ECO1HzLong rides, power saving first
!Tip ECO mode still auto-laps, but times are more often marked as estimates (~). For precise laps use RaceBox or MAX mode.
7.10 Viewing in the App
7.11 Where to Place the Line?
PIT ✓Straight ✕Hairpin ✕Parallel section ✕Pit entrance
7.12 FAQ
Q: Started without setting the line?No problem — the track before setup is kept as WARM-UP. Press LAP as you cross the spot you want, anytime, to begin official lapping.
Q: What if GPS drops mid-run?Recording continues. Auto lap re-arms when the signal returns; any laps missed meanwhile can be marked with LAP as you cross the line.
Q: Does the lap in progress at stop count?No. Only fully crossed laps count; the unfinished segment is saved separately as PARTIAL (listed as L-- / PART in RECORDS) and is not a lap.
Q: Can I switch back to button lapping mid-session?The lap mode is set at the start of each session; changing it mid-session takes effect from the next one.
08
Standing-Start Drag

Standing-Start Drag

8.1 What Standing-Start Drag Is

Standing-start drag measures the time from a standstill to a target speed. The watch detects your launch automatically to start timing and records the run automatically after the sprint — press OK once before each run to arm, and after that no more button presses are needed, so you can focus on driving. The session itself is saved when you hold BACK to end it.

Each run records three split results, each one the time for that segment alone (not a running total from 0):

Speed unitSplit 1Split 2Split 3
km/h0-100100-200200-MAX
mph0-6060-120120-MAX

0-100 is launch to 100 km/h; 100-200 is 100 to 200; 200-MAX is from passing 200 to the moment the run’s top speed first appears — it climbs as you set new highs and freezes when you lift. 200-MAX is for reference and not used to pick the best run. Splits you don’t reach show --, without affecting the splits you did achieve.

8.2 Before You Measure
  1. Enter RACING and wait for GPS to be ready (external RaceBox, Qstarz or built-in GPS).
  2. Choose the DRAG → STANDING method to reach the standby screen.
  3. You can only arm (ARM) once the GPS signal is stable; if it’s weak the watch refuses — move to open sky.
8.3 Flow of One Run
① Arm
Stop, press OK to declare the next launch as timed
② Confirm stop
Fully still ~1 s to enter READY
③ Launch
Timing starts the moment the vehicle moves
④ Sprint
Live splits, VMAX and current speed
⑤ Finish
Ends and records the run after you slow and stop
待命 OK ARM NEXT RUN
StandbyPress OK to arm next run
武裝後等待靜止
ArmedWAIT FOR STOP
靜止確認 READY
ReadyHOLD... READY
衝刺中 分段與 VMAX
SprintingSplits + VMAX + current speed
成績畫面 RESULT
ResultSplit times and top speed
iThe sprint and result screenshots above still show the old third split 200-300; the current screen shows 200-MAX (see 8.1). New screenshots to come.
!Changing your mind mid-run Armed but not launched (ARMED / READY): short-press OK or BACK to disarm — nothing is recorded and the run number stays (pressing OK again after arming cancels; it does not confirm). Mid-sprint (RUNNING / DECEL): short-press BACK and the run is kept as INCOMPLETE — the screen shows R# RESULT with yellow INCOMPLETE, then returns to standby after about 3 seconds (or OK / BACK). It uses up a run number; splits already reached are shown, but it can’t be the best run.
8.4 Many Runs per Session

Standing mode supports multiple runs per session: after each run, return to standby and press OK to arm the next. Runs are numbered R1, R2, R3…, up to 200 runs per session; once full the prompt changes to RUN LIMIT and no further run can be armed (everything else in the session still saves normally). On standby the prompt in the middle of the screen reads OK: ARM NEXT RUN (another run can be armed), STOP TO ARM (still moving), GPS NOT READY (no fix yet), GPS SEARCHING... (searching for GPS) or RUN LIMIT (200 runs reached).

The state words you will see on screen

Standing mode shows which stage it is in directly on screen:

On screenMeaning
UNARMEDOn standby, not armed. Acceleration now is not recorded.
ARMEDArmed, waiting for the vehicle to come to a complete stop.
READYStationary confirmed; timing starts the moment you launch.
RUNNINGRun in progress; split times lock in as you reach them.
DECELDeceleration detected, waiting to finish (below about 10 km/h for 2 seconds).
RESULTThe result screen for that run; it closes after about 3 seconds, or press OK or BACK.
iPressed OK but it won’t arm? The screen tells you why: GPS NOT READY means there is no fix yet; STOP TO ARM means the vehicle is still moving — come to a stop and press again.
✓
Return trips aren’t mis-recorded

Only an armed, official launch produces a result. Driving back to the start, or any acceleration while not armed, is never recorded as a run — no need to worry about return trips cluttering your log.

8.5 GPS Signal Safeguards

Accuracy depends entirely on GPS, so the watch has three layers of protection:

Poor quality ignored

When fix quality drops (e.g. under an overpass), that data isn’t counted toward the result and won’t falsely trigger a launch or finish.

Brief dropouts tolerated

Brief GPS instability during a sprint (within 2 seconds) is skipped automatically, without affecting the result.

Too long → aborted

If a dropout lasts 2 seconds without a break, the run aborts and is marked GPS LOST; it’s kept for reference but excluded from best results.

GPS LOST 中止 INCOMPLETE

If GPS fails after arming but before launch, arming clears automatically — just re-arm from the standby screen.

▲A run aborted by a GPS dropout shows red GPS LOST and INCOMPLETE on the live screen, and GPS LOST on its RECORDS run page. Splits and top speed reached before the dropout are kept; splits not reached show --. The run is excluded from best.
iThe screenshot above still shows the old third split 200-300; the current screen shows 200-MAX (see 8.1). New screenshots to come.
iBuilt-in GPS speed guard The built-in GPS occasionally reports 0 speed while the car is still moving. When the watch detects this (the position keeps moving), the live screen shows CURRENT -- km/h instead, so a run isn’t mistaken for a stop and ended early; in standby it shows GPS NOT READY and won’t arm for the moment. External RaceBox / Qstarz sources are not affected.
8.6 Reviewing Results

Main menu RECORDS (see Chapter 9) → select the session to view:

iHow the best run is marked Page 1 of the detail view is titled BEST 0-100 (BEST 0-60 in mph): the large figure is the best 0-100 time, with RUNS / BEST / VMAX below. A run ended by a short BACK mid-sprint, or cut short by holding BACK, is marked INCOMPLETE — and will not be chosen as the best run even if it reached a high speed.
紀錄詳情 P1 BEST 摘要
P1 · SummarySession BEST hero
紀錄詳情 趟次 BEST
Run · BESTR1/3 best run
紀錄詳情 GPS LOST 趟
Run · GPS LOSTR3/3 incomplete
加速曲線頁
Accel curveSpeed–time curve
iThe STANDING screenshots in this section and in 8.3 are still the old screens: the third split reads 200-300 (the per-run page shows cumulative 0-200 / 0-300) and the middle cell of the summary page reads BEST RUN. The current screens show 0-100 / 100-200 / 200-MAX, and the middle cell reads BEST. New screenshots to come.
8.7 Tips
09
View & Manage Records

View & Manage Records

There are two places to view records: DOWN at the face (quick overview) and RECORDS in the main menu (per-session detail).

9.1 Racing Overview (press DOWN at the face)
記錄總覽
Racing overview
9.2 Per-Session Detail (main menu RECORDS)
Record list
How to enter
Main menu → RECORDS.
Display
Each row shows date/time and a mode badge, and the focused row also shows a stats summary; newest on top. The last row is DELETE ALL.
Buttons
UP/DOWN scroll; OK opens that session’s detail; BACK returns to the menu. With none it shows NO SESSIONS / START A MODE TO LOG.
記錄列表
Record list
Session detail

On entry it loads that session (large files show READING LOG briefly). Use DOWN next/UP previous to page, BACK to the list. Page count and content vary by mode; in every mode (tilt records included) the second-to-last page is INFO (session info, see below) and the last page is Delete (see 9.3):

ModeMain content
DAILYDistance & time / avg / top speed → speed-band distribution → route map
DRAGBest result → run list (best run marked with a green star) → best-run splits → acceleration curve; STANDING records show Summary → runs (OK switches runs) → accel curve (see 8.6)
LAP TIMERBest lap → per-lap times & gaps → route map with max G
TOUGEDistance / time / avg / top speed → route map → elevation profile & total climb
OFF-ROADMax tilt → attitude page (total-tilt gauge) → route map
DAILY 詳情
DAILY detail
DRAG 詳情
DRAG detail
LAP 詳情
LAP detail
TOUGE 詳情
TOUGE detail
OFF-ROAD 詳情
OFF-ROAD detail
!Tip The LAP TIMER detail page currently shows speed fixed in km/h; other modes convert to your unit setting.
!Tip If the off-road attitude page shows NO TILT / NEEDS VEHICLE MOUNT, no attitude reference was taken for that session — check that MOUNT is set to VEHICLE (see 10.3), that the watch really is fixed to the vehicle, and that the vehicle was briefly stationary around the start. Note that the source matters too: Qstarz sessions carry no tilt data at all (see 6.3).
The INFO page: how this session was recorded

The INFO page gathers the recording conditions of the session, so you can check afterwards which GPS was used, at what rate, and how it ended. Rows that don’t apply are hidden; OK does nothing on this page.

RowOn screenMeaning
SRCRACEBOX / QSTARZ / INTERNALThe GPS source used. The built-in GPS shows INTERNAL for both MAX and ECO — tell them apart by RATE
RATEe.g. 25HZ, 10HZ, 5HZ, 1HZSample rate, derived from the mode setting at the start and the source’s limit — not a measured value
DRAGQUARTER / STANDING / ROLLINGDRAG records only: the method used
BATTe.g. 87>62%RaceBox records only: RaceBox battery at the start and at the end
ENDsee belowHow the session ended
FIXe.g. Q0-Q3Lowest and highest fix quality seen in the session (0 = no fix, 2 = 2D, 3 = 3D)
PTSa numberTrack points (samples for tilt records)
FWe.g. GTM003The firmware version when the session was recorded, not the watch’s current version
END showsMeaning
MANUALYou ended and saved it
AUTOThe watch ended it: TIME LIMIT (MAX REC reached), NO MOVEMENT (a long stop), or the first part when a full file is split automatically (see 6.4)
LOW BATT (red)The battery ran low and the watch stopped and saved automatically (see 6.4, 13.1)
LINK LOST (red)The GPS source dropped out at some point during recording, even if it came back
iINFO on older records Records made before September 2026 may show SDK_V4.5.1 under FW — back then that field held the SDK version, not the firmware version. If no sample rate was stored, RATE shows -. A screenshot of the INFO page will be added later.
9.3 Deleting Records
刪除確認
Delete confirmation
▲Deletion can’t be undone — back up important records via USB or the app first.
iDeleting records in RECORDS (one, or DELETE ALL) does not affect the lifetime distance and drives on achievement faces — they are stored separately. Conversely, SETUP → Delete and both resets zero the achievements but do not delete records (see 4.6 / 10.6).
Walkthrough

Save track-day results to a computer

  1. Connect the watch to a computer with USB; it appears as a flash drive.
  2. Open the drive, go to the RACELOG folder and copy the .BIN files you want to keep.
  3. Put the files in the input/ folder of the desktop parser tool.
  4. Double-click parse.bat.
  5. Each session produces: a Google Earth track (.kml), a spreadsheet with a speed chart (.xlsx) and an interactive map (.html).
10
Settings

Settings

Main menu → SETUP, containing:

ItemDescription
SET GPSGPS source & precision (10.1)
System SettingsBacklight, sound, time, language, units, etc. (10.2)
RACINGSpeed unit & per-mode sample rates (10.3)
DeleteResets achievement data to zero (watch face choice kept); does not delete Racing records (see 9.3, 10.6)
ResetRestore factory settings (10.6)
AboutVersion & device info (10.6)
SETUP 選單
SETUP menu
10.1 SET GPS (source & precision)

Three screens: status page → settings page → selection list.

GPS status page
SET GPS status
GPS settings page
SET GPS settings
GPS source selection list
Source selection listThree sources · filled dot = current
10.2 System Settings

One item per page, set in turn:

ItemDescription
Satellite positioning (GNSS)Enable/disable multi-GNSS
Backlight (BACKLIGHT)Four items: BRIGHTNESS 1–5 (default 2), AUTO OFF 5/10/20/30/60 s (default 5 s), RAISE TO WAKE ON/OFF (default OFF), and LONG PRESS — how long a long press of the backlight button keeps it on: 3/10/30 min (default 3 min). UP/DOWN picks an item, OK opens it; on the edit page UP/DOWN changes the value, OK saves, BACK cancels (brightness previews live and is restored on cancel). Item names are always in English
Key soundOn/off
Key vibrationOn/off
TimeTime zone, date format, DST, Set Time (GPS sync / manual set / auto-sync switch, see below), 24-hour
Alarm5 independent alarms (10.4)
LanguageEnglish / Traditional Chinese / Simplified Chinese
UnitsMetric / imperial (everyday display)
Heart rateHeart-rate settings (10.5)
Compass calibrationRotate the watch as prompted to calibrate
Watch facePreview and switch between 8 faces: UP/DOWN preview, OK save, BACK cancel (the list does not wrap, see 4.4)
系統設定選單
System Settings menu
時間子選單
Time submenu
語言選擇
Language select
錶面選擇
Face preview select
!Tip After changing the time zone or running GPS time sync, the watch time updates automatically.
Set Time (GPS sync and manual setting)

Time → Set Time opens a text submenu with three items:

Set Time submenu
Set Time submenuThree items
Manual time setting
Manual time settingField by field · underline = editing
10.3 RACING Settings

RACING settings span 3 pages. UP/DOWN move within a page and turn to the next page at either end (the dots along the right edge show the current page).

PageItemOptionsTakes effect
P1SPEED UNITKM/H ↔ MPHImmediate (session screens and detail convert; exceptions: LAP TIMER detail speed stays in km/h, distances in the RECORDS list and in LAP TIMER / OFF-ROAD detail stay in KM, and STANDING records keep the unit they were recorded in)
MOUNTWRIST (worn, default) ↔ VEHICLE (mounted)Takes effect next session (see 6.4 / 6.6)
ALERT TONEON ↔ OFF (default ON)Immediate (governs all session alerts, see 6.8)
ALERT VIBON ↔ OFF (default ON)Immediate (as above)
P2DAILY sample rateFixed at 1 Hz (not adjustable)—
DRAG / CIRCUIT / TOUGE / OFF-ROAD sample rateAdjustableTakes effect next session
P3MAX REC (longest single recording)OK cycles 30 MIN / 1 H (default) / 2 H / 4 H; there is no “off”Takes effect next session (see 6.4)
SCREEN LAYOUTA/B/C per modeTakes effect next session (see 6.5)
RACING settings P1
P1Units · mount · alerts
RACING settings P2
P2Sample rate per mode
RACING settings P3
P3MAX REC · SCREEN LAYOUT
iThe P3 screenshot above is the old screen, with only the SCREEN LAYOUT row; the current P3 also has MAX REC above it. New screenshot to come.
!Tip Recorded detail is limited by the lower of your set sample rate and the source’s real update rate. Setting a rate higher than the source won’t refine the data. RaceBox has the highest rate; built-in GPS is lower.
10.4 Alarms
鬧鐘列表
Alarm list
鬧鐘編輯
Alarm edit
10.5 Heart Rate
心跳設定
Heart-rate settings menu
10.6 Reset & About
How each clearing operation affects achievement data

Achievement data (lifetime distance / drives / today’s top speed, see 4.6) is stored separately from the record files: deleting records in RECORDS does not affect your totals, while SETUP → Delete and both resets zero the achievements but do not delete session records:

OperationSession recordsAchievement dataWatch face choice
Delete one recordThat record is deletedKeptKept
DELETE ALL in RECORDSAll deletedKeptKept
SETUP → DeleteKept (not deleted)Reset to zeroCurrent choice kept
Reset → system resetKept (not deleted)Reset to zeroBack to the default “Triple Stack”
Reset → all resetKept (not deleted)Reset to zeroBack to the default “Triple Stack”
重置
Reset screen
關於頁
About page
11
App · Connect & Sync

App & Device Connection

The [Companion App] is the STINT watch’s track companion app. Use it to connect to the watch, sync track logs, review post-session data and manage device status. All screens in this chapter are actual app screens.

iJust remember: the app connects to the watch, and the watch records and returns the track data. The RaceBox Mini is an external high-precision GPS whose status the watch reports — the app does not connect to it directly.
11.1 Before Connecting
App 首頁:尚未連接手錶,顯示搜尋手錶按鈕123

Before you start, check these:

  • Phone Bluetooth is on.
  • The STINT watch is powered on and near the phone.
  • The [Companion App] is open. On first launch a welcome screen (cloud backup sign-in) appears first; tap Browse first to skip it — you can sign in later under Settings → STINT ID. Then start from “Search for watch” on the home screen.
  1. The status row at the top of the home screen reads Watch · not connected, and the “Next step” card below it says Connect your watch.
  2. Tap Search for watch to begin pairing.
  3. While disconnected you can still browse synced sessions and use speed alerts (the home screen notes that neither needs a connection).
iThe picture above is the old home screen (headed “No watch connected yet”, with the mode list below). The current home screen shows, from top to bottom, the status row, the “Next step” card, recent sessions and two tools (speed alerts / video OSD). New screenshot to come.
11.2 First Connection to the STINT Watch
正在搜尋附近手錶
SearchingLooking for nearby watches
正在與手錶建立連線
ConnectingEstablishing link, please wait
手錶已連接12
ConnectedReady to sync
  1. Tap Search for watch on the home screen.
  2. The app begins searching for nearby watches (about 8 seconds); keep the watch on and near the phone.
  3. When the search ends, a Select your watch list appears (names are STINT GTM plus four characters; see 11.3). Even if only one watch is found, tap your watch.
  4. The app establishes a link with the watch — just a moment.
  5. Once linked, the app briefly shows Connected and returns to the previous screen by itself; the home status row then shows a green dot and the watch name.
iThe “Connected” screen (callouts ① connected status, ② preparing to sync track logs) appears only briefly before the app returns on its own.
iConnecting again later The app remembers the last watch it connected to. When you tap Search for watch again (or open the Device tab), that watch is shown straight away — just tap Reconnect, no new search needed. To switch to another watch, tap Search for other watches.
11.3 What If the Watch Isn’t Found
找不到手錶錯誤畫面

Don’t worry when you see Watch not found — it usually doesn’t mean a fault. Check in order:

  1. Is the watch powered on.
  2. Is the watch near the phone.
  3. Is the phone’s Bluetooth on.
  4. Is the watch connected to another device (one phone at a time).
  5. Tap Search again.
iIf the phone’s Bluetooth is off, the app shows Can’t connect to watch — with the explanation that the watch is busy or connected to another device — rather than “Watch not found”. Turn on the phone’s Bluetooth first, then tap Retry.
iWhich watch is mine? The app lists the watch as STINT GTM plus four characters (e.g. STINT GTM CA01). Those four characters are the last four characters of the Bluetooth address shown under Settings → About on the watch (an address ending in CA:01 gives STINT GTM CA01) — use them to tell watches apart when several are nearby. This name is used from firmware GTM003 onward; earlier firmware shows CREST-CR5L.
11.4 Confirming the Watch Is Connected
首頁已連線卡片與同步場次按鈕1234

Once connected, the status row at the top of the home screen changes:

  1. The connected watch name, in the form STINT GTM plus four characters (e.g. STINT GTM CA01; see 11.3).
  2. A green dot before the name means connected; after you have synced, the last sync time follows the name (e.g. “synced 5 min ago”).
  3. Tap the status row (Device › on the right) to open the “My Devices” page with the firmware version and RaceBox (see 11.5).
  4. The “Next step” card below becomes Sync to phone; tap Sync sessions to read the watch’s records.
iThe picture above is the old home-screen watch card (with battery, distance and RaceBox status). The current home screen shows no battery, distance or RaceBox — only a single status row. New screenshot to come.
!Visible on the watch too While the app is connected, a white Bluetooth symbol appears to the right of the battery gauge on the watch face; connecting gives one long beep + short buzz and disconnecting gives two long beeps (both can be switched off with ALERT TONE / VIB in the RACING settings, see 6.8).
11.5 My Devices & RaceBox Mini
我的裝置頁:手錶狀態與 RaceBox 說明123

The My Devices page (the Device tab at the bottom) shows the watch’s firmware version, connection state and last sync time, plus the RaceBox currently assigned to the watch.

  1. Watch info: firmware, connection state, last sync. Battery currently shows “—” (the app cannot read the watch battery yet).
  2. RaceBox card: shows “Not paired” or “Paired · address”, with a note that the app reads RaceBox status through the watch.
  3. Pair RaceBox / Change RaceBox button: assigns a RaceBox in the app (currently this does not affect which unit the watch actually connects to — see the note below).
iThe picture above shows mock-up values: in the current app the RaceBox card does not show GPS lock, satellite count or battery, and the watch name appears as STINT GTM plus four characters. New screenshot to come.
▲The app reads RaceBox status through the watch, not by connecting to it directly. During sessions it is the watch that connects to the RaceBox.
iIn the current firmware the watch does not match a specific device — on entering Racing it connects to the first RaceBox it finds (see 6.2). Selecting a device in the app therefore does not change which unit the watch actually connects to.
11.6 Syncing Track Logs from the Watch
正在從手錶讀取場次清單
Reading listFetching sessions from the watch
選擇要同步的 Race Log123
Choose sessionPick a Race Log
同步進行中,顯示進度百分比
SyncingDownload progress
  1. Make sure the watch is connected.
  2. Tap Sync sessions on the home screen.
  3. The app reads the session list from the watch (no re-search or reconnect).
  4. Choose the Race Log to sync.
  5. The app downloads the track log, showing a progress percentage.
  6. When done, view the post-session data in the app.

Labels in the session list mean:

GPSThis session contains GPS data.
IMUThis session is mainly sensor data.
SyncedAlready imported. Tap any session to sync/re-sync.
Tilt recordingA tilt recording made with FreeTilt (see 11.14).
IncompleteWhen a file has a problem, a problem label is shown instead. Red Incomplete / Not finalized / Read failed mean the content may be incomplete: tapping one first explains why and asks whether to Download anyway. Grey No samples / Summary unavailable can still be downloaded directly.
11.7 If Sync Is Interrupted
同步中斷,已下載資料保留

If the signal is only briefly unstable during a download, the app retries a few times by itself. If the connection really drops, the session’s row shows a red error (e.g. “Download failed: …”) and the app also says “Watch disconnected, please reconnect”. Then:

  • Bring the phone near the watch.
  • In the Device tab tap Reconnect (or tap Search for watch on the home screen) to connect again.
  • Tap Sync sessions on the home screen, then tap that session again to download it again.
iThe original records on the watch are not affected, and sessions that finished syncing stay in the app. The interrupted session keeps nothing of the partial download, so downloading it again starts from the beginning.
iThe picture above is an earlier design of the “connection lost” screen. The current app does not show this screen and has no “Retry connection”, “Keep downloaded · try later” or “Cancel sync” buttons. New screenshot to come.
11.8 No New Sessions
手錶沒有新場次

No new sessions (“no new sessions on the watch”) isn’t an error — it means the watch currently holds no records at all to download.

The watch doesn’t delete records by itself, so as long as old sessions remain on it, the app lists them as usual and marks the imported ones “Synced” (see 11.6) instead of showing this screen. After recording a new session (see Chapter 6), come back and tap Sync sessions.

11.9 App Connection FAQ
Q: The app can’t find my watch?Make sure the watch is on and near the phone with Bluetooth enabled, then tap Search again. The watch connects to one phone at a time — disconnect any other phone first.
Q: If the connection drops, will data be lost?No. The original records on the watch are unaffected, and sessions that finished syncing are kept. For the interrupted session, reconnect and tap it again to download it again (it starts from the beginning; see 11.7).
Q: Does the app connect to the RaceBox Mini directly?No. The app reads RaceBox status through the watch, not directly; during sessions the watch connects to the RaceBox.
Q: Why are there no new sessions?This screen means the watch holds no Race Log at all right now (for example, right after clearing its records). If old sessions remain, the app lists them and marks the imported ones “Synced”. Record a new session, then come back and sync.
Q: What does “Synced” mean?It means the session is already imported. To update it, re-sync/overwrite.
11.10 Pulling Files to a Computer via USB

Besides the app, you can connect the watch to a computer: it appears as a flash drive, with sessions stored in the RACELOG folder (each filename is the recording start time encoded as an 8-digit hexadecimal number, e.g. 6AB4C368.BIN). The desktop parser (double-click parse.bat) produces track maps, spreadsheets and speed charts (see the Chapter 9 walkthrough).

!Records are never deleted automatically The watch does not clear out old records by itself. RECORDS can browse up to 300 records (sessions and tilt recordings combined), 10 at a time, page by page, with number 1 being the newest. When space runs out you have to delete some yourself (see 9.3), so back up important records early. The HOME overview and the classic face’s signature line are unaffected and always summarize only the newest 10 records (tilt recordings take slots but don’t count as sessions) (see 9.1 / 4.4).
11.11 [Firmware update (app side) — TBD]
11.12 Setting the GPS Source in the App

The watch’s GPS source and built-in precision can be changed from the app as well as on the watch (see 10.1), in the Watch section of the Settings tab at the bottom (the watch must be connected; when it isn’t, the options are greyed out with the hint that they can be set after connecting the watch):

iThe app currently offers only two sources The watch itself supports three (RaceBox / built-in / Qstarz, see 1.2), but this version of the app lists only the first two. To use Qstarz, switch the source on the watch (SETUP → SET GPS). Note: when the watch is set to Qstarz, the app shows the source as “RaceBox”; choosing a source in the app at that point overwrites the watch’s Qstarz setting.
11.13 Exporting Tracks and Sharing Achievements

Every session can be exported as a KML track file (openable in Google Earth and similar map software), or turned into an achievement image to share. All five modes are supported. The session page also has Export CSV / GPX: CSV has one sample per row and opens in Excel or any spreadsheet; GPX is the standard GPS track format for map and analysis software. Both contain coordinates, and the start/end handling follows the same per-mode defaults as KML (see below).

Exporting KML
▲GPS data is sensitive A full track contains the exact coordinates where you set off and arrived, and may reveal your home, workplace or meeting point. Treat it like your home address and don’t share it publicly without thinking. The app warns you again when you choose “full track”.
Sharing achievements
11.14 Tilt Recordings and Video OSD

Tilt recordings made with FreeTilt (see 4.5) can be synced to the app, which can overlay the attitude onto your driving video and export a new file. Race sessions can be overlaid too: tap Overlay video on the session summary, or start from the home-screen tool Video OSD (pick the videos first, then the record), to burn speed, distance, G-force and similar data into the video; alignment and export work as described below.

  1. Sync: pick a tilt recording in the watch record browser and download it over Bluetooth. Once downloaded it appears in the session list alongside your sessions, marked as a tilt recording.
  2. Pick a video: choose driving footage from the same period. The app aligns them automatically using the watch recording’s timestamps and the video’s capture time; you can fine-tune by hand if they drift.
  3. Export: the artificial horizon and R/P values are overlaid onto the video and exported as a new file. One tilt recording can be applied to several videos at once for batch export.
!Tip The OSD overlay supports video files only. Automatic alignment relies on the video’s own capture-time metadata; if the video was re-encoded and lost it, you will need to align manually. Video export is currently iOS only; the Android version shows a message that exporting video is iOS-only for now and the Android version is in development.
iApp screenshots for 11.12–11.14 are not included yet; they will be added once the app home-screen redesign (IA restructure) is complete.
iFirmware updates are started from the [Companion App] (for the watch-side screens and cautions, see 3.4). The app-side screens and step-by-step instructions will be added here once the app’s firmware update feature is final.
12
FAQ & Tips

FAQ & Tips

Q: Can’t find GPS / slow to fix?Go outdoors with open sky, away from tall buildings, tree cover, garages and tunnels. The first fix, or one after a long gap, takes longer — that’s normal.
Q: No G-force shown?It depends on the source: RaceBox is measured; built-in GPS derives it from GPS only at MAX precision (ECO power-saving mode does not provide it); Qstarz shows no G-force on the watch, and none in the app either after syncing (the app says there is no measured G-force). See 1.2.
Q: Off-road attitude shows NO TILT / NEEDS VEHICLE MOUNT?Check the source first: built-in GPS uses the watch’s own IMU and a RaceBox uses its own, so both can produce tilt; Qstarz sessions provide no tilt at all. With built-in GPS, go to SETUP → RACING, set MOUNT to VEHICLE, fix the watch to the vehicle, and wait for the pre-start confirmation screen to read READY (or keep the vehicle briefly stationary after starting) so the watch can take an attitude reference. MOUNT only affects built-in GPS; RaceBox sessions ignore it and need a moment somewhere in the recording where the vehicle is briefly stationary for the detail page to calculate tilt.
Q: Watch can’t find the RaceBox?The RaceBox does not need pairing — check that it is on, charged and near the watch. The watch searches automatically after entering Racing and only gives up after about 5 minutes.
Q: A recording split into two sessions?For very long sessions the watch splits and saves automatically to protect data — this is normal.
Q: Max sample rate but no finer data?Actual detail is limited by the source’s update rate. Built-in GPS is lower, so setting above it adds no density; use RaceBox for the highest density.
Q: How long until it returns to the face?Normal screens return to the face after about 11 minutes of inactivity; the Racing mode list and the DRAG method picker after about 5 minutes, standby after 20 minutes (about 5 minutes if the GPS source drops out and is not ready), and a built-in GPS search that finds nothing after 20 minutes. A recording never returns to the face for inactivity, but it does end automatically under the conditions in 6.4. And on any screen, 24 hours without a button press while not charging powers the watch off.
Q: Buttons seem unresponsive at low battery?When the low-battery warning shows, the first key press only clears the warning; press again to perform the key’s normal function.
Q: How do I power off?At the watch face, hold BACK.
Q: It shows STORAGE FULL, or nothing saves?The watch does not delete old records automatically, so storage does fill up. When there are 300 records, the records total about 16 MB, or the watch runs short of free space, it shows STORAGE FULL with DELETE OLD LOGS before a recording starts (or when an automatic split tries to continue into the next segment) — delete a few sessions by hand in RECORDS (see 9.3), or sync with the app first and then clear them. If it shows STORAGE ERROR instead, the storage had a read/write error that deleting records won’t fix; back up your records with the app or over USB first.
Q: I get SAVE FAILED?A failed save is announced with two long beeps and a long buzz (see 6.8). It means a read/write error occurred while writing the recording — not that storage is full (a lack of space is caught before recording starts, with STORAGE FULL). When a session was split automatically, the segments already saved are not lost. Try again; if it keeps happening, back up your records with the app or over USB first.
Q: LOW BATTERY or CHARGE TO REC — it won’t start a new recording?Below about 3.5 V the watch refuses to start a new recording, so it can’t die mid-session and leave a broken file. Charge it first. If the battery drops below 3.5 V during a recording, the watch stops and saves automatically (the screen shows SAVED / LOW BATT, see 6.4).
Q: Several RaceBoxes nearby — the watch connected to someone else’s?The watch doesn’t match a specific RaceBox: on entering Racing it connects to the first one it finds, and the watch doesn’t show which unit it connected to (see 6.2, 11.5). Switch on only your own, or turn the others off and re-enter Racing.
Q: The detail page shows NO DATA / NO LAPS / NO RUNS / NO ELEVATION?It means the session has no data of that kind — not a fault. NO LAPS = no lap was completed; NO RUNS = no DRAG run was completed; NO ELEVATION = no usable altitude change; NO GPS DATA = there was no GPS fix for the whole recording, so no route can be drawn (see 1.2). Separately, NO IMU on a screen during recording means no valid attitude data has arrived for about 3 seconds in a row. READING LOG or CALC simply means it is still loading — wait a moment.
13
Appendix

Appendix

13.1 Specifications
Platform
ProcessorMediaTek MT2523 (ARM Cortex-M4 + FPU), 104 MHz
Memory / storage4 MB RAM + 128 KB TCM; 4 MB flash
Display240 × 240 full-color TFT
ButtonsFour physical buttons (UP/DOWN/OK/BACK) + backlight button (doubles as LAP during a session)
Positioning
Built-in GNSSSony CXD5605GF, supporting GPS / GLONASS / BeiDou / Galileo / QZSS / SBAS
Positioning accuracy2DRMS 1.0 m (at a signal strength of −130 dBm)
Time to first fixAbout 35 s cold start; about 2 s hot start (real-world times depend on how much sky is obstructed, see 6.7)
Receiver sensitivity−161 dBm tracking; −147 dBm cold start
GPS sourceExternal RaceBox Mini (Bluetooth, with G-force) / built-in GPS / external Qstarz logger (Bluetooth, BL-1000GT · 818GT)
Data update rateRaceBox Mini up to 25 Hz; built-in GPS up to 5 Hz (1 Hz in power-saving mode); Qstarz about 5.6 Hz (limited by the Bluetooth connection interval). Actual recording density is also bounded by each mode’s sample-rate ceiling (see 6.0)
Sensors
Motion sensing3-axis accelerometer + 3-axis magnetometer (used for the compass and for vehicle roll and pitch)
Heart rateOptical heart-rate sensor (PPG)
BarometerBarometric sensor (altitude and pressure trend graph)
Connectivity and records
ConnectivityBluetooth (to the [Companion App], RaceBox and Qstarz); USB (charging / reading records on a computer)
Record retentionRECORDS browses up to 300 records (sessions and tilt combined), 10 per page; old records are never deleted automatically — clear them yourself when full. The HOME overview always summarizes only the newest 10 records (tilt recordings take slots but don’t count as sessions; see 9.1 / 9.3; achievement data is unaffected, see 4.6)
Laps per sessionUp to 200 laps per session (GPS auto lap adds one warm-up lap); at the limit it shows LAP FULL while distance and track keep recording (see 7.8)
Watch faces8 (2 classic / 4 achievement / 2 minimal, see 4.4)
Other featuresTime, alarm, compass, barometer, heart rate
Power
BatteryRechargeable lithium battery (4.2 V standard, also supports 4.3 V high-capacity cells). [TBD: capacity in mAh]
Battery lifeAbout 3 months on standby (not recording); about 1–2 weeks with daily wear and ordinary logging; about 8–12 hours with GPS and sensors running continuously. High sample rates and a long-lit screen draw the most power.
ChargingClip the supplied charging clip onto the watch body and charge over USB; below about 3.0 V it first pre-charges at 70 mA (the screen stays dark meanwhile), then charges at 300 mA. About 1 hour to 80%. While charging the watch switches to charging mode: you can only view the battery (see 3.3); no other functions are available.
Charging protectionCharging stops at a battery temperature of 50 °C or more, or below 0 °C; a single charge runs for at most 24 hours
Low-battery behaviorWhen not charging, the watch shuts down automatically once the battery drops below about 3.4 V; at that level it also switches off again right after power-on, so charge it first. Below about 3.5 V a recording stops and saves automatically, and a new one cannot start (see 4.5 / 6.4)
Physical
Water resistance50 m (5 ATM). Fine for swimming, rain and washing your hands; not for diving, jumping into water or high-speed water sports, and keep it away from steam rooms, saunas, hot springs and hot showers. This is the rating as shipped; it degrades as seals age and with impacts or contact with soap, sunscreen and other chemicals, and is not a permanent property.
Size / weight[TBD]
Operating temperature[TBD]
iThe processor, positioning and power figures in this table come from chip datasheets and firmware settings; battery life, water resistance and physical dimensions must follow hardware measurements and certification results, to be filled in before publication.
13.2 Button Quick Reference
SituationAction
Open main menuFace OK
Quick session overviewFace DOWN
TILT / compass / info pagesFace UP (TILT comes first, see 4.3)
Power offFace hold BACK ~5 s
Start a sessionMain menu → RACING
Mark a lap in sessionLAP TIMER (BUTTON): Live screen OK or LAP; GPS AUTO: LAP sets the line / adds a manual lap, OK has no effect (see 7.5). DAILY DRIVE and TOUGE don’t record laps
End & save sessionLive screen hold BACK 2 s
Refresh BluetoothFace short-press BACK
13.3 Mini Glossary
G-forceThe force felt when accelerating, braking or cornering; lateral G reflects cornering, longitudinal G reflects accel/brake. RaceBox measures it with a sensor; built-in GPS (MAX) derives it from changes in speed and heading (see 1.2).
GPS-derived GG-force worked back from changes in GPS speed and heading when there is no accelerometer. Good for trends, less accurate than a measurement, and with no vertical component.
trap (speed)Instantaneous speed at the end of a distance (e.g. 1/4 mile).
STANDINGAcceleration measured from a standstill.
ROLLINGAcceleration measured while already moving, started on cue.
Sample rate (Hz)Data points recorded per second; higher means a finer track.
RaceBox MiniExternal high-precision GPS accessory with G-force sensing.
Qstarz loggerAn external GPS logger (BL-1000GT / 818GT); no G-force is shown on the watch (the mobile app derives it itself).
FreeTilt (TILT)A GPS-free quick tilt tool: mount it at any angle, zero it, and see the vehicle’s roll and pitch live (see 4.5).
Lifetime distance (TOTAL KM / MI)The sum of the distance of all session records; not limited to the last 10 sessions and not reset by deleting records (see 4.6).
Drives (DRIVES)How many drives you have completed after pressing OK: START; a drive split automatically into several records still counts as 1.
Today’s top speed (TODAY MAX)The highest speed reached today, based on the watch’s local date and reset at midnight.
Milestone (MILESTONE)Staged targets for lifetime distance (100 / 250 / 500 / 1,000 / 2,500 / 5,000 / 10,000, then every 5,000); the face congratulates you once when you cross one.
MOUNTThe mounting setting: WRIST (worn) or VEHICLE (fixed to the vehicle); affects the OFF-ROAD horizon and the start confirmation page.
13.4 Known Limitations
13.5 Regulatory Statements and Warranty

Taiwan NCC statement (certification no.: [TBD]) — reproduced in the original Chinese as required by law

取得審驗證明之低功率射頻器材,非經核准,公司、商號或使用者均不得擅自變更頻率、加大功率或變更原設計之特性及功能。低功率射頻器材之使用不得影響飛航安全及干擾合法通信;經發現有干擾現象時,應立即停用,並改善至無干擾時方得繼續使用。前述合法通信,指依電信管理法規定作業之無線電通信。低功率射頻器材須忍受合法通信或工業、科學及醫療用電波輻射性電機設備之干擾。

United States FCC statement (FCC ID: [TBD])

This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.

EU CE / RED: This product complies with the essential requirements of the EU Radio Equipment Directive (RED 2014/53/EU). For the full Declaration of Conformity (DoC), contact the manufacturer. (CE marking and EU representative details: [TBD])

Warranty: one-year limited warranty — 12 months from the date of purchase; where no proof of purchase can be provided, 15 months from the date of manufacture. Service is provided within Taiwan (R.O.C.) only; customers outside Taiwan bear the round-trip shipping, duties and customs charges. To request service, provide the product serial number and proof of purchase; we also recommend including the diagnostic code produced by the app’s “Device Check”, which resolves most cases without shipping the unit. The battery is an exception: if its capacity falls below 80% within 300 charge cycles and this is confirmed by inspection, it is treated as a defect and remains covered. The warranty card supplied with the product governs in full. (Support contact: [TBD]). Damage caused by improper use, use contrary to this manual, unauthorized disassembly or the use of non-original accessories is not covered (see “Safety and Disclaimer”, item 7).

iThe certification numbers and the support contact in this section are TBD before publication; the actual content will follow the certification results and the official shipping documents.
Version History
VersionDateNotes
v1.02026-07-15First release. End-user oriented, page-by-page operation plus walkthroughs. Brand name shown as placeholders, to be replaced before publishing.
v1.172026-09-24Aligned with develop @ 106a2c77 (firmware GTM003): features merged after 9/2 added, low-battery figures corrected. ① §13.1 correction: when not charging, the watch shuts down below about 3.4 V (Mis1.cpp:248). The 2.9 V previously written is the fuel gauge’s system floor SHUTDOWN_SYSTEM_VOLTAGE, not the shutdown point a user meets. The firmware has no threshold matching “won’t power on below about 3.5 V” (3500 only sets the fuel-gauge wake-up period while suspended), so that sentence was rewritten too. The old figures in the v1.12 row are a historical record and stay as they were. ② §9.2 INFO page added (PR #194 / #117): second-to-last page in every mode — SRC / RATE / DRAG / BATT / END / FIX / PTS / FW. #117, listed as “not yet merged” in v1.16, was merged on 9/14. ③ Automatic session end and MAX REC (important) (PR #208): TIME LIMIT (default 1 hour; 30 min / 2 h / 4 h on page 3 of SETUP → RACING; no off), NO MOVEMENT (20 min), LOW BATT (about 3.5 V); below 3.5 V at start it shows LOW BATTERY / CHARGE TO REC; built-in GPS search timeout 60 → 20 min; standby returns to the face after 20 min; any screen powers off after 24 h without a button press while not charging (§6.4 / 6.7 / 10.3 / 12 / 13.1 / 13.4). ④ Storage pre-check (PR #232 / #233): sessions and FreeTilt share the 300-record and space check (STORAGE FULL / DELETE OLD LOGS / STORAGE ERROR); v1.16’s “FreeTilt can’t start with 10 session records” no longer applies; auto-split shows Saving...; FreeTilt’s 2-hour auto-stop is now documented (§4.5 / 6.4 / 13.4). ⑤ STANDING (PR #230 / #231): splits are now 0-100 / 100-200 / 200-MAX (each its own segment time; 200-MAX runs to the run’s top speed and is not used for the best run); a short BACK mid-sprint keeps the run as INCOMPLETE; built-in GPS false-zero guard; detail page 1 is titled BEST 0-100 (§6.6 / 8.1 / 8.3 / 8.5 / 8.6). The STANDING screenshots in 8.3 / 8.6 (live and detail) are still the old ones, marked “new screenshots to come”. ⑥ Bluetooth name (PR #251 / #252): from GTM003 it is STINT GTM plus four characters (the last four of the Bluetooth address on the About page), §11.3 / 11.4. ⑦ Backlight (PR #207): four BACKLIGHT items (BRIGHTNESS / AUTO OFF / RAISE TO WAKE / LONG PRESS); “Clock power saving” removed (§1.1 / 10.2). ⑧ PR #240 switched the boot screen and About page to the STINT GTM wordmark: text unchanged, the §3.1 boot screenshot still shows the old logo and is marked “new screenshot to come”. ⑨ No user-visible change: #241 (update file found via a candidate list; every released STINT build already has it), #181 / #174 (docs), #234 / #238 (performance), #253 (old model targets removed). ⑩ Japanese edition: leftover Chinese translated in the §9.2 DRAG row and captions/alt text, six rows of the §10.2 table, the §10.4 / 10.5 headings and the §10.4 captions. ⑪ Whole-manual check against the product (2026-09-24): about 440 statements were checked one by one against GTM003 firmware (develop 0d7a880a; the firmware code is identical to the GTM003 build c55838df) and App main 43a27a1, and about 100 mismatches were corrected. Highlights: there are 8 watch faces (Today’s Hero and Race Card were removed; the default is the three-stat face); powering off takes holding BACK for about 5 s; charging stops when the battery is at or above 50 °C or at or below 0 °C, and below about 3.0 V it first pre-charges at 70 mA; SETUP → Delete and all reset do not delete Racing records (use RECORDS → DELETE ALL), while SETUP → Delete resets achievements; LAP TIMER asks for a LAP MODE (BUTTON / GPS AUTO) after the mode; auto-split keeps the lap count and shows Saving...; RaceBox battery shows only on the standby screen; the orange/cyan G is lateral G; the OFF-ROAD live horizon always uses the watch IMU; GPS auto lap drops ALREADY COUNTED / GPS LOW / ≈ BEST, which the firmware does not have, and now warns not to press LAP after an auto lap; STANDING sprint screen, closing the result, disarming, 2 s of continuous GPS loss and how GPS LOST is shown; chapter 11 rewritten to match the current app (an interrupted sync re-downloads from the start, home and device screen contents, the watch list on first connection); chapter 12 drops WRONG DEVICE and “the app estimates G for Qstarz”, which are not true. Screenshots that no longer match are marked “New screenshot to come.” Firmware and app issues found along the way are listed separately for Brad and are not written into the manual. Not verified on hardware: MAX REC / no-movement / low-battery auto end, live 200-MAX display, backlight settings on STINT GTM (written from the code and test plans). Still TBD: battery capacity, size/weight, operating temperature, NCC/FCC/CE numbers, support contact, the [Companion App] name; screenshots of the INFO page, the STANDING per-run page and the boot screen.
v1.162026-09-02Retail product name STINT GTM filled in, and aligned with develop @ 4b69101a. ① Product name: brand STINT, model GTM, full name STINT GTM (signed off 2026-09-02). Six placeholders replaced per language — footer, cover model line, chapter 1 in the contents, the chapter 1 heading and opening sentence, and the “For editors” box (only [Companion App] is left). The wording inside the v1.14 changelog row is a historical record and was deliberately left alone. ② Retention policy changed (important): the firmware has disabled automatic deletion of old records (`race_tilt_log.c`: “boot/commit automatic retention is disabled”), and RECORDS now browses up to 300 records (sessions and tilt combined, 10 per page — PR #185 / #186). Every “keeps the 10 most recent, oldest deleted automatically” statement has been rewritten (§9.1 / 9.3 / 12 / 13.1 / 13.4). The HOME overview and the classic face’s signature line still summarize only the newest 10 sessions — that has not changed. The limitation that FreeTilt cannot start once 10 session records are stored has been added. ③ §4.5 FreeTilt sampling rate corrected from 2 Hz to 25 Hz (PR #189 / #190). ④ §7.8 documents the PARTIAL record: the half lap you were on when you stopped is kept separately but never counts as a formal lap and is never best or worst (PR #202). ⑤ The Japanese edition’s §11.10 heading, still in Chinese, was translated. ⑥ Merge status corrected: of the five items v1.15 listed as unmerged, #121 the 10 watch faces (#183), #175 half laps (#202), #184 FreeTilt 25 Hz (#189 / #190) and #138 record capacity (#185 / #186) all merged between 8/19 and 8/20; only #117, the record-detail INFO page, remains. The watch-side protocol for app-driven firmware updates (#209 / #210, PR #213) is merged, but §11.11 stays a placeholder because the app-side screens are not final. Still TBD: battery capacity, size/weight, operating temperature, NCC/FCC/CE numbers, support contact, and the [Companion App] name.
v1.152026-08-19Aligned with develop @ bdcec103 and inventoried every branch. ① String correction: the §8.3 caption read HOLD… READY, but the watch shows HOLD... READY with three plain periods; the Japanese edition’s leftover Chinese word in the same caption was corrected too. ② §8.4 gained the standing-mode on-screen state table (UNARMED / ARMED / READY / RUNNING / DECEL / RESULT), the standby prompts OK: ARM NEXT RUN / OK: NEXT RUN, the RUN LIMIT shown after 200 runs, and the two reasons OK may refuse to arm (GPS NOT READY / STOP TO ARM). ③ §8.6 now names the best-result page BEST RUN and explains that a cancelled or cut-short INCOMPLETE run is never chosen as the best. ④ Merge status corrected: #144 standing multi-run (8/12), #176 Auto Lap live UX (8/13) and #180 the boot-recovery fix that was deleting FreeTilt records (8/13) are all merged, so the earlier “#144 not merged” note is void. Still on branches, not yet merged (deliberately not written into the body of this version): #121 the 10 watch faces (wf/face-onto-develop, which also adds face names to the settings preview), #117 the record-detail INFO page, #138 raising record capacity from 10 to 300 (once merged, every “10 most recent sessions” in §13.1 and §9 must be rewritten), #175 half-lap PARTIAL records, and #184 FreeTilt’s logging rate going from 2 Hz to 25 Hz (once merged, the §4.5 sample rate must change).
v1.142026-08-14Specifications and warranty signed off by A. ① The charging accessory is now correctly called a charging clip (previously “cable”; the accessory actually supplied is a clip-on charger); §1.5 Safety and §2 Quick Start updated, and it is now stated explicitly that the watch switches to charging mode while charging — the buttons do nothing and it cannot be used. ② Three blank rows in §13.1 filled in: battery life (about 3 months standby / 1–2 weeks daily wear with ordinary logging / 8–12 hours with GPS and sensors running), the Charging row now names the charging clip and “about 1 hour to 80%”, and water resistance is set to 50 m (5 ATM) with the permitted and prohibited water activities and the seal-ageing disclaimer. ③ §13.5 warranty filled in with the final terms: one-year limited warranty (15 months from manufacture without proof of purchase), service within Taiwan only, serial number and proof of purchase required, battery below 80% within 300 cycles covered as a defect; the note in that section now says the certification numbers and the support contact are pending, not the warranty terms. Still TBD: battery capacity, size/weight, operating temperature, NCC/FCC/CE certification numbers, support contact, [Product Name] placeholder (the model is GTM; the retail product name is not settled).
v1.132026-08-12Aligned with develop @ b6ce9f5a after a full audit (method: extract the firmware’s 367 on-screen strings and mechanically diff them against the manual text). Two substantive errors corrected: ① off-road tilt is not “independent of the GPS source” — `race_tilt2_g_is_true_3axis_imu()` uses the watch’s IMU for built-in GPS, the RaceBox’s own IMU for RaceBox, and excludes Qstarz entirely; §6.3 / 6.5 / 9.3 / 12 now state the two conditions (MOUNT=VEHICLE and a source with true three-axis data). ② the off-road detail page is not an artificial horizon — P1 is a single maximum-tilt figure and P2 a total-tilt gauge (left and right carry no direction; R-P reads -- because the split is unimplemented); §6.5 / 9.2 updated, and the Japanese edition’s untranslated Chinese row was translated at the same time. Three shipped but undocumented features added: §6.5 RaceBox battery (RB 51% / RB CHG while charging, four color bands — PR #163 / issue #116); §6.4 pre-start readiness (GPS NOT READY / HOLD STILL... / READY, only built-in GPS with VEHICLE has to wait — PR #164); §7.8 the 200-lap-per-session limit and LAP FULL (recording continues past the limit — PR #173 / issue #127). Five edge-state entries added to §12 (STORAGE FULL / SAVE FAILED / LOW BATT / WRONG DEVICE / the various NO ... empty states). The §13.1 lap row is corrected from the mistaken “64 laps on the detail page” to the 200-lap recording limit. Merge status corrected: #136 FreeTilt (8/11), #137 OFF-ROAD horizon (8/10) and #140 GPS auto lap (8/10) are all merged into develop, so the earlier “not yet merged” notes are void; only #121, the 10 watch faces, is still unmerged.
v1.122026-08-08§13.1 specification summary substantially filled in. It previously had only 8 rows with battery, water resistance and dimensions left blank; it is now reorganized into six groups — platform / positioning / sensors / connectivity and records / power / physical — totalling 24 rows. Every newly added figure is sourced: MT2523 processor at 104 MHz, 4 MB RAM + 128 KB TCM, 4 MB flash and the 240×240 display (docs/01_overview.md, Display.h); the built-in GNSS is confirmed as the Sony CXD5605GF, supporting six constellations, with 2DRMS 1.0 m accuracy, 35 s cold / 2 s hot TTFF and −161 / −147 dBm sensitivity (docs/datasheet/CXD5605GF_datasheet_notes.md); charging at 70 mA pre-charge / 300 mA fast charge, the 60 °C and 24-hour charging protections, and the 3.5 V no-boot / 2.9 V auto-shutdown thresholds (cust_battery_meter.h, docs/05_peripherals.md); 10-session retention and the 64-lap-per-session ceiling (RACE_STORAGE_MAX_FILES / RACE_VIEW_MAX_LAPS in race_storage.h). Battery life, capacity in mAh, time to full charge, water resistance, dimensions and operating temperature remain TBD — none of these exist in the firmware and they require hardware measurement and certification results; the power-consumption measurements in docs/test_plan/ are currently marked TBD.
v1.112026-08-06Added four already-shipped app-side features (previously only connection and syncing were covered; these four were merged from 2026-07-17 onward but the manual had not caught up): new §11.12 “Setting the GPS source in the app” (source / built-in output rate, applies next time you enter Race; noting that the app currently lists only built-in and RaceBox, so Qstarz must be switched on the watch), §11.13 “Exporting tracks and sharing achievements” (full-track vs. protect-start/end KML modes and the per-mode defaults, the GPS-sensitive-data warning, and the fact that achievement cards contain no positioning data), §11.14 “Tilt recordings and video OSD” (Bluetooth sync, merging into the session list, automatic video alignment and batch export). Cross-reference added to §4.5; §11.5 notes that since pairing was removed, selecting a device in the app does not change which unit the watch connects to. App screenshots for these three sections are pending the app home-screen redesign (IA restructure).
v1.102026-08-06RaceBox no longer requires pairing (firmware PR #169, merged and shipped). The shipping default bind policy is “connect to the first one found”, so the NOT PAIRED screen never appears in the production build. Changes: §6.1 now marks all three sources as pairing-free; §6.2 rewritten from “Pairing RaceBox” to “Using the RaceBox Mini” (app pairing steps and the NOT PAIRED tip removed, warning added about connecting to the first of several nearby units); §6.7 rewritten around searching for nearby devices, with the heading covering Qstarz; §12 FAQ and §13.3 updated to match.
The concurrent firmware PR #167 (QSTARZ Phase B + unified packaging chain, 40 commits) is entirely bootloader / OTA / Release Center infrastructure with no user-visible change, so the manual is unaffected.
v1.9.22026-08-03Converged after a two-way check against the CD edition: adopted CD’s corrected §10.3 table structure (the engineering-side v1.8 edit left an unclosed <table>, duplicating the header and wrapping later content into the table) and aligned the cover and footer version marks (which had been stuck at v1.0). A section-by-section comparison confirmed the CD edition and this one are now identical in body content, with no differences across 65 sections and 101 image references.
v1.9.12026-08-03Adopted CD’s typographic work from this round into the current edition: added .tbd (TBD placeholders in gray, easy to scan before publication) and .legalhd / .legaltext (smaller size, looser leading, justified text and orphan/widow control for the §13.5 regulatory block). The CD edition was not imported wholesale — CD’s master had merged only up to v1.7 and lacks v1.8’s five firmware-alignment corrections and v1.9’s watch faces / achievement system, so a full import would have reintroduced four already-corrected errors.
v1.92026-08-03Added the 10 watch faces and the achievement system (PR #121, not yet merged into develop; written up on Brad’s instruction): §4.4 expanded from 2 faces to 10 (2 classic / 6 achievement / 2 minimal) with the non-wrapping list and app-side selection; new §4.6 “Achievement data” (lifetime distance / drives / today’s top speed, unit rules, large-number abbreviation, empty-state copy, when it counts, milestone steps and the congratulation message, and the fact that upgraded watches do not import old records); §9.3 and §10.6 gained tables of how each clearing operation affects achievement data; §10.2 / §13.1 / §13.3 updated to match. Face screenshots pending the final designs.
v1.82026-08-03Aligned with the shipping firmware (develop as of 2026-08-02). Five statements that did not match the actual device were corrected: ① ODO removed from the main menu, leaving 3 items — RACING / RECORDS / SETUP (§5); ② G-force now described per source — RaceBox measured / built-in MAX GPS-derived (a new feature; the previous “no G-force” was wrong) / built-in ECO none / Qstarz none on the watch (§1.2 / 6.5 / 12 / 13.3 / 13.4); ③ off-road tilt now depends on MOUNT, not the GPS source, with the on-screen text NO TILT / NEEDS VEHICLE MOUNT (§6.3 / 6.6 / 12 / 13.4); ④ added the SCREEN LAYOUT system (5 modes × A/B/C, §6.5 / 10.3); ⑤ RACING settings reorganized into 3 pages with MOUNT / SCREEN LAYOUT added (§10.3). §6.7 gained the 5-minute built-in GPS warm-hold. Screens: 14 RECORDS and detail pages redrawn per #135 “larger log text and graphics”, plus 3 main-menu and 4 settings screens.
v1.72026-07-29Included three in-development features (on Brad’s instruction). Status correction (v1.8): of these, race-alert session alerts (PR #128) and MOUNT / tilt self-calibration (PR #134) have been merged into develop, contrary to the original note; FreeTilt (#136) and the OFF-ROAD horizon (#137) remain unmerged on their branches. Content: new §4.5 FreeTilt (with the 4.1 / 4.3 carousel updated); the OFF-ROAD horizon layout and the MOUNT setting / VEHICLE start confirmation page (§6.4 / 6.6 / 10.3 / 13.3); new §6.8 session alerts with the ALERT TONE / VIB switches and the app connection icon on the face (§4.1 / 10.3 / 11.4). Four new rendered screens.
v1.62026-07-29Aligned with the latest merges on firmware develop: added Qstarz as a third GPS source (PR #123 — §1.2 rewritten for three sources, connection and setup notes in §6.1/6.2/6.4/10.1, §13.1/13.3/13.4 and the FAQ updated, plus a new source-selection screen); added manual time setting and the auto-sync switch (PR #120 — the §10.2 Set Time submenu (GPS SYNC / MANUAL SET / AUTO SYNC) and the field-by-field editing screen, with the quick-start steps updated to match).
v1.52026-07-25Backfilled the changelog entry for Chapter 11 “App and device connection” (originally missing; the chapter and §11.1–11.10 were added on 2026-07-16); §4.4 gained the watch-face and switching description; §13.1 gained data-update-rate and watch-face rows, with battery, water resistance and dimensions marked TBD; new §13.5 “Regulatory statements and warranty” (NCC / FCC / CE numbers TBD); new §11.11 placeholder for firmware update (app side).
v1.42026-07-16Added §6.7 “GPS Fix & Wait Times” to the Racing chapter (search-screen annotations, wait timeline, environment comparison, no-GPS screen).
v1.32026-07-16Added Chapter 8 “Standing-Start Drag” (with the ARM→save flow and three-layer GPS protection); former chapters 8–12 shifted to 9–13, with TOC and cross-references updated.
v1.22026-07-16Added Chapter 7 “GPS Auto Lap” (with the line-setting flow, track overhead and record-structure diagrams); former chapters 7–11 shifted to 8–12, with TOC and cross-references updated.
v1.12026-07-16Added the “Safety & Legal Notice” chapter, Racing “Key Concepts (6.0)” and the appendix “Known Limitations (13.4)”; expanded the logic for lap counting, DRAG methods and the sample-rate ceiling.