DASHFORGE USER GUIDE
For DashForge v3.99.110 · AppForged · support@appforged.cc
Updated 2026-10-30.

==================================================================================================
HOW TO USE THIS GUIDE
==================================================================================================
Each feature has its own block. Every block uses the same headings:

  Where:   how to get there. "☰ Menu ▸ Dashboard ▸ Units…" means: tap the dashboard to show the top
           bar, tap "☰ Menu", tap the "Dashboard" tile, then tap "Units…".
  Needs:   what the feature needs before it works:
             Free             works for everyone (DashForge, the free app).
             DashForge Plus   needs the one-time Plus unlock, for hand tuning (see 1.5).
             DashForge Pro    needs the one-time Pro unlock (see 1.5).
             DashForge Track  needs the DashForge Track subscription (see 14).
           "DashForge Pro or DashForge Track" means either one unlocks it, and "DashForge Plus or
           Pro" means either one-time unlock does. Pro includes everything in Plus.
           The line also says whether the feature needs a connected ECU, a verified ECU, a firmware
           family, a sensor in your Android device, or internet access.
  Notes:   limits, safety points, and what you see when something it needs is missing.

Button and menu names are in quotes, exactly as they appear on screen. When you can't find a
setting, tap "☰ Menu ▸ Find a setting…" and type a word from its name.

Different Android devices have different sensors. Head units often have no accelerometer or
gyroscope, and their GPS can be weak. Phones usually have all of these. Section 16 lists which
features need which sensors.

==================================================================================================
CONTENTS
==================================================================================================
   1. Welcome and what you need
   2. Getting started
   3. The dashboard screen
   4. Dashboard settings
   5. Alerts
   6. Display and HUD
   7. Tuning
   8. Logging, analysis and dyno
   9. Trip / fuel computer
  10. Vehicle and calibration
  11. Connection menu
  12. Navigation
  13. Lap timer
  14. DashForge Track
  15. Diagnostics and app menu
  16. Which features need which sensors
  17. Troubleshooting
  18. Getting help


##### 1. WELCOME AND WHAT YOU NEED #####

==================================================================================================
1.1  What DashForge does
==================================================================================================
Where:   The dashboard is the home screen. Tap it to show the top bar, then tap "☰ Menu".
Needs:   Free to start. Some features need DashForge Pro or DashForge Track (see 1.5).

What it does
  DashForge turns any Android device (a phone, a tablet or the screen in your car) into a
  full-screen dashboard, datalogger,
  navigator and tuner for your engine ECU. It talks to MS3/MS2, MS1, Speeduino and rusEFI ECUs
  (see 1.2) over a USB cable or a Bluetooth adapter. A second Android device can show the
  dashboard as a windshield HUD over Wi-Fi.

  The menu is a grid of tiles. Each top-level tile is one group:
  - "Find a setting…": search every menu and setting by name.
  - "Dashboard ▸": choose and import dashboards, what each gauge shows, colours, units, warning
    banners and notifications, day / night, language, HUD and screen rotation.
  - "Tuning ▸": your ECU's tables and settings, in the same sections as your tuning software;
    VE auto-tune, cranking tools, the tune library, and ECU setup and verification.
  - "Logging & dyno ▸": datalogs, the log viewer, the virtual dyno and the performance meter.
  - "Navigation ▸": the turn-by-turn map, the lap timer, DashForge Track and the outside
    temperature.
  - "Trip / fuel computer…": fuel used, MPG, range and the fuel level.
  - "Vehicle & calibration ▸": the vehicle profile, coast-down, TPS and VSS calibration, gear
    detection and output tests.
  - "Connection ▸": connect, set up a new ECU, firmware and ECU type (see 11).
  - "Diagnostics & app ▸": unlock codes, the check-engine and event logs, support tools, probes
    and About (see 15).

Notes
  - DashForge never changes your tune until this ECU has passed verification on this device (see
    2.4), except on a few grandfathered firmwares (2.4). Until then you can still watch the gauges,
    log and look at every setting.
  - Writing to the ECU also needs the Tuning unlock (DashForge Plus or Pro).

==================================================================================================
1.2  Supported ECUs
==================================================================================================
Where:   ☰ Menu ▸ Connection ▸ Detect firmware… shows what your ECU reports and whether the app
         knows it.
Needs:   Free · a connected ECU to identify it.

What it does
  DashForge knows some firmware builds out of the box. Any other build of the same families can
  be set up from its own INI file, right on the device (see 2.2).

  Built into the app:
  - MS3 / MS3-Pro / MS3X: firmware 0523.15, 0566.05, 0569.00 and 0592.13, including their "P"
    and "U" builds where the app lists them.
  - MS2/Extra and MicroSquirt: Serial310, comms330NP, comms342a2, comms342h2, comms342hP and
    comms342hU.
  - MS1 / MSnS-Extra: 029y3.
  - Speeduino: 202501.
  - rusEFI: nothing built in. During setup the app reads the INI from the ECU itself (or you
    choose it), then uses it.

  What each family can do:
  - Every supported ECU: the live dashboard and datalogging as soon as it connects, and viewing
    every setting and table once the app has a definition for it.
  - MS3/MS2, MS1 and Speeduino: editing (write and burn) and MSQ import / export after the ECU
    passes verification on this device (see 2.4). A few grandfathered firmwares can edit before
    that (2.4).
  - A firmware set up from your own INI: the same, plus one extra step ("Turn on editing"). Until
    your first Burn, writes are refused while the engine may be running: edit with it off.
  - MS1: it holds one settings page in RAM, so burn your changes before you move to a table or
    setting on another page. If the ECU is set for a MAP sensor other than 115 kPa, editing stays
    off; the dashboard and datalogging still work.
  - rusEFI: the dashboard, datalogging and reading the tune. Editing isn't available in this
    version. The app doesn't show the dashboard's verification reminder for it.

Notes
  - A few features belong to one family: the check-engine banner reads MS3 faults (MS3 with a
    built-in definition). The cranking optimizer works on every firmware.
  - A firmware from another family entirely is refused when you add its INI: "“<file>” is for
    “<signature>”, a firmware family the app doesn't support yet (MS3/MS2, MS1 and Speeduino are)."
  - MS3 and MS2 ECUs can't tell the app which hardware model they are. Pick yours in ☰ Menu ▸
    Connection ▸ ECU model so channels get the right names (see 11.6).

==================================================================================================
1.3  Connection hardware
==================================================================================================
Where:   ☰ Menu ▸ Connection ▸ Connect…, or "Connect" on the top bar.
Needs:   Free · a USB host (OTG) port, or Bluetooth, on the Android device.

What it does
  DashForge links to the ECU over a USB serial cable or a Bluetooth serial adapter.

  USB cables and adapters:
  - FTDI USB-serial cables (the usual MS3/MS2 cable). Picked and connected by themselves.
  - USB "CDC/ACM" serial devices: an Arduino Mega or Teensy (Speeduino), a CH9102 adapter, and a
    rusEFI board's own USB port. Picked and connected by themselves.
  - CH340 and CP210x adapters. These work, but the app never picks one by itself the first time:
    choose it once in the "Connect to ECU" list, and it's remembered.
  - PL2303 adapters are not supported.
  - Over USB the app sets the speed itself: 115200 baud, or 9600 for an MS1.

  Bluetooth adapters:
  - Classic Bluetooth serial adapters (the serial port profile, SPP).
  - Pair the adapter first in Android's Bluetooth settings. DashForge only lists paired adapters;
    it doesn't scan.
  - The adapter's own baud rate must match the ECU's serial port: usually 115200, 9600 for an MS1.
    You set this in the adapter, not in DashForge.
  - On a Speeduino linked through its secondary serial port, set that port to the tuning-software
    protocol, or the ECU won't report its signature.

Notes
  - A phone or tablet needs a USB OTG adapter or cable for a USB ECU cable.
  - With neither USB host nor Bluetooth, the top bar says "No USB or Bluetooth".
  - Android 12 and later ask for the "Nearby devices" permission before the app can list or use
    a Bluetooth adapter.
  - If Bluetooth is off the top bar says "Bluetooth is off — turn it on to connect", and the app
    offers to turn it on (once per session).
  - A CH340 / CP210x adapter that links but gets no data shows "No ECU data over the <chip>
    adapter — send details to support". Use an FTDI or CDC adapter, or Bluetooth, meanwhile.
  - A PL2303 shows "<chip> adapter not supported yet".

==================================================================================================
1.4  Android devices
==================================================================================================
Where:   ☰ Menu ▸ Dashboard ▸ Display ▸ HUD & display… ▸ "This device" (head unit or phone).
Needs:   Android 6.0 or newer.

What it does
  DashForge runs on any Android device: a phone, a tablet or the screen in your car. The dashboard
  opens in landscape.

  The app decides whether this device is a head unit or a phone / tablet. On "Auto" it counts the
  device as a head unit if it sees any one of these: a car-mode setting, Android's car mode or
  automotive feature, a known head-unit system, or no accelerometer. Otherwise it's a phone or
  tablet. If it guessed wrong, set "This device" yourself: "Auto (detected: …)", "Head unit" or
  "Phone or tablet".

  What changes with it: only the outside temperature. Google doesn't allow its weather service in
  a car's own screen, so a head unit never fetches the temperature itself. A phone or tablet
  connected as the HUD device fetches it (with a Google key entered on the phone) and sends it to
  the head unit. The Navigation menu's temperature row says "(Google Weather, from your HUD
  phone)" on a head unit.

Notes
  - Sensors differ a lot. Head units often have no accelerometer or gyroscope and a weak GPS;
    phones usually have all of them. Check yours with ☰ Menu ▸ Diagnostics & app ▸ Sensor & GPS
    probe… (see 15.6).
  - GPS feeds road speed (if you choose GPS), the trip computer's MPG and range, the gear
    estimate, the position in datalogs and the maps. It needs the location permission with
    "precise" on.
  - Screen rotation is a switch in ☰ Menu ▸ Dashboard ▸ Display. Tablets and large screens on
    Android 16 and later always turn with the device, whatever the switch says.
  - Other things some features need: Wi-Fi (HUD), internet (maps, languages, DashForge Track), and
    a text-to-speech voice (spoken directions).

==================================================================================================
1.5  DashForge, DashForge Plus, DashForge Pro and DashForge Track
==================================================================================================
Where:   ☰ Menu ▸ Diagnostics & app ▸ Unlock / codes… (see 15.1). DashForge Track: ☰ Menu ▸
         Navigation ▸ DashForge Track (map source, devices)… (see 14).
Needs:   —

What it does
  DashForge comes in four tiers:
  - DashForge: the app itself, free.
  - DashForge Plus: a one-time unlock for hand tuning, for good, on up to 3 devices. It can be
    upgraded to Pro later, for the difference in price.
  - DashForge Pro: a one-time unlock, for good, on up to 3 devices. It includes everything in
    Plus. You can try it free for 7 days first (see the notes).
  - DashForge Track: a subscription. It works on its own, with or without Plus or Pro. There's no
    free trial.
  Plus, Pro and Track are bought on the DashForge website, dashforge.appforged.cc. You then type
  the code it gives you into the app: a Plus or Pro key (DFP-XXXX-XXXX-XXXX) in ☰ Menu ▸
  Diagnostics & app ▸ Unlock / codes… (15.1), a Track link code in ☰ Menu ▸ Navigation ▸
  DashForge Track… (14.2).

  DashForge (free)
  - Connecting, the built-in dashboards and their colours, units, warning banners and
    notifications.
  - Viewing every setting and table. ECU setup and verification.
  - Datalogging and the log viewer, VE analysis, captured starts and the optimizer's suggestions.
  - The trip / fuel computer, the vehicle profile, coast-down and VSS calibration, gear
    detection.
  - Saving your ECU's tune to the tune library, sharing and backing it up, and exporting it as an
    MSQ (export needs a verified ECU). Opening an offline tune to look at.
  - The check-engine and event logs, support tools, languages.

  DashForge Plus (one-time, for good)
  - "Tuning": hand tuning on a connected ECU — editing settings, 2D curves and 3D tables and
    burning them, the tuning tools, TPS calibration, and loading your own saved tunes back onto
    the ECU.

  DashForge Pro (one-time, for good)
  Everything in DashForge Plus, and:
  - "Quick-tune": quick-tune buttons on imported dashboards, which load a saved tune into RAM.
  - "Output tests": firing injectors and coils, and the other actuator tests (10.6).
  - "Offline tune editing": changing a saved tune without the car, and saving it back.
  - "Tune import": bringing a .mst or .msq file into the tune library, and loading it.
  - "Imported dashboards": dashboards made in the Dash Designer (dashdesigner.appforged.cc).
  - "HUD": mirroring the dashboard and navigation to a second device over Wi-Fi.
  - "Navigation": turn-by-turn with a map and voice, using your own Geoapify key.
  - "Dashboard maps": the live map and next-turn elements inside imported dashboards.
  - "Performance meter": 0–60, quarter-mile, braking.
  - "Lap timer": lap and sector times from GPS. The delta to your best lap, the predicted lap,
    per-lap g and ECU figures and the shared track list come with DashForge Track.
  - "Virtual dyno": power and torque curves, live or from a log.
  - "VE auto-tune": learning your fuel table while the engine runs (its writes also need Tuning).

  DashForge Track (subscription, up to 3 devices)
  On its own, without Pro, Track unlocks:
  - Navigation (the map, search and routing, with no Geoapify key of your own), and the map and
    next-turn elements in dashboards.
  - The lap timer, with the delta to your best lap, the predicted lap, per-lap g and ECU figures
    and the shared track list.
  - The HUD on a second device.
  - Cloud sync and backup across your devices, share links, and your files on the web.
  - A dashboard design emailed to you each month. It loads with Track alone; other imported
    dashboards still need Pro.

Notes
  - A locked feature shows 🔒. Tapping it opens the unlock screen for that feature. On a HUD
    display device, and on quick-tune buttons, it only shows a short message instead.
  - The HUD is checked on each device: the head unit and the HUD device each need Pro, or each
    need to be linked to Track.
  - A Tuning unlock can be tied to one car. Your unlock then tunes only that ECU (see 15.1).
  - The 7-day DashForge Pro trial: on the Unlock screen, "Try DashForge Pro free for 7 days" gives
    "All of DashForge Pro (not DashForge Track) for 7 days, once per device. Starting it needs the
    internet, and it ends by itself." It's offered on a device without Pro, so a device with
    DashForge Plus can take it too.
  - Upgrading DashForge Plus to Pro is done on the DashForge website (your account page there),
    not in the app; the app only says "DashForge Plus can be upgraded to Pro on our website". The
    key stays the same. Once a day, while it's online, a device with Plus checks whether its
    purchase was upgraded, and switches to Pro by itself.
  - Nothing locks while you drive: a feature found unlocked stays unlocked until the app
    restarts.
  - A Plus or Pro key activates online once on each device, then works offline. It works on up
    to 3 devices; to free a place, remove a device on your account page at
    dashforge.appforged.cc. That device loses Plus or Pro the next time it's online.
  - Refunds and chargebacks: a refunded Plus or Pro key or code (a chargeback counts as a refund)
    switches off the next time the app starts after the device has been online, never
    mid-drive. If a dispute is decided in your favour, access comes back. The app checks a public
    list of refunded codes when it starts (if it's online) and every 6 hours while it runs. If an
    upgrade to Pro is refunded, the key goes back to Plus on each device.
  - Track's features on the device (navigation, dashboard maps, the HUD, the lap timer's extras
    and the monthly dashboard) keep working for up to 7 days offline after the device last
    checked in.

==================================================================================================
1.6  Where your files live
==================================================================================================
Where:   Documents/DashForge on the device's storage. Open it with any file manager.
Needs:   Free · on Android 10 and older, the storage permission.

What it does
  DashForge keeps your files in Documents/DashForge, so cleaning apps don't empty it and it stays
  when the app is uninstalled.
  - Datalogs: dashforge_<date>_<time>.msl and a matching .csv, in Documents/DashForge itself.
  - Tunes: Documents/DashForge/Tunes — the tune library's .mst files and the .msq files you
    export.
  - Probe reports: Documents/DashForge/Probe — saved when you tap "Share" on the Settings probe or
    the Tune health probe.
  - Support bundles: Documents/DashForge/Support — saved there when the device has no email app.

How to use it
  Opening files from another app (email, messaging, a file manager, Bluetooth):
  1. In that app, tap the file and choose "Open with" ▸ DashForge, or "Share" ▸ DashForge.
  2. DashForge asks "Open in DashForge? (from <app>)" and lists where each file will go: "ECU
     setup (definition)", "ECU setup (tune)", "ECU setup (sensor table)", "ECU setup", "tune
     library" or "dashboards".
  3. Tap "Open". Nothing is used before you do.
  4. A single MSQ asks "What should DashForge do with this tune?": "Set up this ECU" or "Add to
     tune library". Adding a tune to the library needs DashForge Pro (Tune import); using an MSQ
     to set up the ECU is free.

  After a reinstall on Android 11 or later:
  1. Android hides the files an earlier install saved. DashForge offers "Your DashForge files
     from before".
  2. Tap "Choose the folder". In Android's folder picker open Documents ▸ DashForge and tap "Use
     this folder".
  3. If you tapped "Not now", use ☰ Menu ▸ Logging & dyno ▸ Show logs & tunes from before this
     install… later. The row only shows when it's needed.

Notes
  - Files DashForge opens from other apps: INI (.ini), MSQ (.msq), DashForge tunes (.mst), MS1
    sensor tables (.inc), zips of these, and dashboards (.msdash). Up to 20 at a time. What a
    file is goes by what's inside it, not its name.
  - Datalogs (.msl, .csv) can't be opened this way. Any other file gets "Not a file DashForge
    opens: <name>. It takes INI and MSQ files, .mst tunes, .msdash dashboards, and zips of them."
  - Importing a dashboard needs DashForge Pro ("Imported dashboards").
  - Some devices block apps from writing to Documents. DashForge then writes to a DashForge
    folder at the top of the storage. On Android 10 without the storage permission it uses
    Download/DashForge. As a last resort it uses the app's own private folder.
  - The wrong folder in step 2 gives "That isn't the DashForge folder. Pick Documents ▸
    DashForge." A device with no folder picker says "This device has no folder picker, so the
    app can't be given a folder."


##### 2. GETTING STARTED #####

==================================================================================================
2.1  Installing and the first launch
==================================================================================================
Where:   Install DashForge on the Android device, then open it from the app list.
Needs:   Free · Android 6.0 or newer.

What it does
  The app opens straight on the dashboard, in English. A few questions come up the first time.
  Each one appears only when it's needed.

How to use it
  1. Android 10 and older: the app asks for storage access once, so it can save logs and tunes in
     Documents/DashForge.
  2. Location: the app asks for location ("precise" and "approximate" together). GPS gives road
     speed, the trip computer's MPG and range, the gear estimate, the position in logs, and the
     map. Choose "precise": with approximate only, the app says "GPS speed needs precise
     location. Turn on "Use precise location" in DashForge's location permission."
  3. Choosing your adapter: with no adapter saved and no USB cable plugged in, the "Connect to
     ECU" list opens once. The top bar says "No adapter selected — pick your USB/Bluetooth
     adapter." (See 2.3.)
  4. Nearby devices (Android 12 and later): asked when you choose or list a Bluetooth adapter.
  5. USB access: when the app first opens a USB cable, Android asks whether DashForge may use
     it. For the common ECU cables Android also offers to open DashForge when the cable is
     plugged in.
  6. The first time a new or unverified ECU connects, the "Set up this ECU" screen opens by
     itself (see 2.2). It waits until you're back on the dashboard, and until the car stops if
     it's moving.
  7. Once per app start, an ECU that isn't verified on this device gets a short reminder with
     "Set up now", "Verify now" or "Check now" (see 2.4). "Later" brings it back next start.
  8. The first time editing turns on, "Before you tune" appears. Tap "I understand". It shows
     only once.

Notes
  - To change the language: ☰ Menu ▸ Dashboard ▸ Display ▸ "Language: English (built in)  (tap
    to change)". Other languages are downloaded, so this needs internet once.
  - Only used with the HUD (see 6): Android 17 asks for local network access (it calls it
    "Nearby devices"); a dedicated HUD device needs "Display over other apps" to start on boot.
  - The app doesn't ask for notification permission. DashForge's "notifications" are shown on the
    dashboard itself.
  - "Before you tune" says: "Changing your ECU's tune can damage your engine or make the car
    unsafe. You're responsible for every change you make. Keep a backup, change one thing at a
    time, and don't tune while driving on public roads."

==================================================================================================
2.2  Set up a new ECU
==================================================================================================
Where:   ☰ Menu ▸ Connection ▸ Set up a new ECU…
         Also: ☰ Menu ▸ Tuning ▸ Set up & verify this ECU — <status>…; the dashboard reminder's
         "Set up now" / "Verify now" / "Check now"; "Set it up" in Detect firmware…; it also
         opens by itself the first time a new or unverified ECU connects.
Needs:   Free · a connected ECU (key on; the engine can run) · your INI file (only for a firmware
         the app doesn't know) and an MSQ saved by your tuning software.

What it does
  "Set up this ECU" is one guided screen with four steps: "① Connect", "② Your files",
  "③ Verify" and "④ Done". It takes you from plugged in to verified. A finished step gets a ✓;
  tap it to look at it again. The title bar has "Details" and "Send to support".

  For a firmware the app doesn't know, it builds the definition from your INI right here on the
  device. The gauges and datalogging use it straight away; editing comes after verification.

Notes
  - A failed step never takes the dashboard away: "You can still use the dashboard and
    datalogging. Editing stays off until this passes."
  - On a device set up as a HUD display the screen says so and offers "HUD & display…": set up
    the ECU on the device connected to the ECU instead.
  - If an offline tune is open, tap "Close the offline tune and connect". With unsaved offline
    edits it asks first: "Discard & connect" or "Keep editing".

--------------------------------------------------------------------------------------------------
2.2.1  ① Connect
--------------------------------------------------------------------------------------------------
How to use it
  1. Turn the key on ("Turn the key on. The engine can be running or off.").
  2. Tap "Connect". The app tries the saved adapter, or a USB cable it can use.
  3. If it can't pick one, it lists them under "Choose your adapter:". Tap yours. On Android 12+
     you may first need "Allow Nearby devices" for Bluetooth adapters.
  4. When it links you see "✓ Connected: <signature> · <release> · <built into the app | set up
     from your INI | not known yet — you'll add its files next>".
  5. Tap "Next: Your files" (or "Next: Verify" when no files are needed).

Notes
  - "Nothing answered. Check the key is on and the cable is seated. A Bluetooth adapter's baud
    must match the ECU: 115200, or 9600 for an MS1 (the app tries an MS1 by itself)." Use "Try
    again", "Choose another adapter" or "Send details to support".
  - "The ECU answered but didn't report a signature…": check the cable or adapter and "Try
    again". On a Speeduino, set the secondary serial port to the tuning-software protocol.
  - "USB access wasn't allowed…": tap "Allow USB access" and choose Allow.
  - "No adapter found…": plug in the ECU's USB cable (key on), or pair its Bluetooth adapter in
    Android's Bluetooth settings, then tap "Connect".
  - "The dashboard isn't running (the app was restarted)…": tap "Back to the dashboard", let it
    link, then open setup again. Your files are kept.

--------------------------------------------------------------------------------------------------
2.2.2  ② Your files
--------------------------------------------------------------------------------------------------
How to use it
  1. Read what the step asks for:
     - The app knows this firmware: "It needs one file: your tune (MSQ), saved by your tuning
       software while connected to this ECU."
     - The app doesn't know it: "Add your firmware's INI and your tune (MSQ). Pick both at once,
       or a .zip that holds them."
  2. Tap "Choose files" and pick them, or use "Found on this device" below (step 4).
  3. Each file gets a row: "Firmware INI" and "Your tune (MSQ)" (an MS1 also has "Sensor tables
     (optional)"). A ✓ means it's accepted.
  4. "Found on this device" lists matching INI, MSQ and zip files the app can see. Tap "Use" on
     one, or "Use both". "Look again" searches again.
  5. When the files are in, tap "Next: Verify".

  How the INI is built on the device: when you add an INI for a firmware the app doesn't know,
  the app reads it, checks it's for the ECU you're connected to, and installs a definition from
  it: "✓ <file> · <n> settings, <n> tables, <n> live channels · installed — the gauges and
  datalogging use it". A rusEFI ECU is read first: "Reading this ECU's INI from the ECU itself…".

Notes
  - Where to find the files (the screen's own help): the INI comes with the firmware, or from
    your tuning software's project on the PC (often mainController.ini). The MSQ: in your tuning
    software, connected to this ECU, save the tune (often CurrentTune.msq). Any names work.
  - Send them to the device any way you like (email, messaging, USB stick, Bluetooth), then open
    them from that app and choose DashForge (see 1.6). They land here, no picker needed.
  - Android 11 and later only let the app search a folder you pick, and never the top of
    Download. Tap "Pick a folder to search" (a folder inside Download, Bluetooth, WhatsApp
    Documents, or one you made). Older Android may ask for storage: "Allow and look".
  - An INI the app already knows is set aside: "<file> set aside — the app already knows this
    firmware. It's used if you choose “Use my own INI instead”."
  - Refused INIs say why, for example "“<file>” is for “<a>”, but your ECU reports “<b>”. Choose
    the INI for <b>." or "“<file>” wasn't used: its live-data command (ochGetCommand) isn't a
    plain read… Use the INI from your tuning software's project folder."
  - Refused MSQs: "“<file>” was made by DashForge, so it can't check the app. Save one from your
    tuning software." and "“<file>” was saved from “<a>”, but your ECU reports “<b>”…".
  - MS1: if your ECU was built with its own sensor tables, add those .inc files too. The app asks
    "Which table is “<name>”?" when it can't tell.
  - After an app update with a kept verification, no files are needed: "No files needed: Check
    again uses your last verification (<date>, <file>)."

--------------------------------------------------------------------------------------------------
2.2.3  ③ Verify
--------------------------------------------------------------------------------------------------
How to use it
  1. Tap "Verify" (or "Check again"). See 2.4 for what the three checks do.
  2. Watch the progress. "Stop" asks "Stop verification?" with "Keep going" or "Stop".
  3. When it stops for a reason, the screen says what happened and offers the fix as a button.

--------------------------------------------------------------------------------------------------
2.2.4  ④ Done
--------------------------------------------------------------------------------------------------
How to use it
  1. You see "✓ Verified — editing and MSQ import/export are on for <signature>."
  2. A definition built from your INI needs one more step: "✓ Verified. One more step: turn on
     editing for your own definition." Tap "Turn on editing", then "Turn on editing" again in
     the question (or "Not now").
  3. After that the app may ask "Help other owners of this ECU?". "Send the INI" opens an email
     with just the INI and the check results, not your tune. You tap Send. Or "No thanks".
  4. Tap "Back to the dashboard".

Notes
  - What's next (from the screen): tables and settings are in ☰ Menu ▸ Tuning. They open
    read-only; tap "Edit" to change values. A change is live in RAM at once; "Burn" keeps it.
    Every write is read back and each burn is CRC-checked.
  - The check also saves a backup of your tune: "Your tune was backed up as “<name>” (Tune
    library)."

--------------------------------------------------------------------------------------------------
2.2.5  Details
--------------------------------------------------------------------------------------------------
How to use it
  1. Tap "▸ Details" at the bottom (or "Details" in the title bar).
  2. It shows the ECU and definition, and one card per check: "✓ Passed", "✗ Failed", "Out of
     date" or "Not run", with "View report" and "Run again".

Settings on this screen
  - "Use my own INI instead…": shown when the built-in definition reads your settings
    differently from your MSQ. Builds a definition from your INI instead.
  - "Go back to the built-in definition" / "Remove my firmware definition": undo your INI's
    definition. The app reconnects.
  - "Send my verified INI to the developer": the same email as in Done.
  - "Forget this ECU's verification": clears all three results on this device. Editing and MSQ
    import / export turn off until you verify again with an MSQ.
  - "Other firmwares on this device": other ECUs this device has checked, and how far they got.
  - "Settings probe (check vs an MSQ)…" and "Tune health probe (tables + temps)…": the single
    checks on their own (see 2.4).
  - "Test display speed": optional, for support. It draws each built-in dash off screen for a few
    seconds; the results go with "Send to support".

==================================================================================================
2.3  Connecting
==================================================================================================
Where:   "Connect" on the top bar, or ☰ Menu ▸ Connection ▸ Connect…
Needs:   Free · USB host (OTG) or Bluetooth · the ECU powered (key on).

What it does
  Tapping "Connect" opens the "Connect to ECU" list of USB devices and paired Bluetooth adapters.
  The one you pick is saved, and from then on the app links to it by itself: when the dashboard
  opens, when the cable is plugged in at key-on, and after a key cycle. The status line in the
  top bar shows what's happening.

How to use it
  1. Bluetooth only: pair the adapter in Android's Bluetooth settings first.
  2. Tap "Connect" on the top bar.
  3. In "Connect to ECU", tap your adapter: "USB (FTDI): …", "USB: …" or "BT: <name>".
  4. USB: if Android asks whether DashForge may use the device, tap Allow.
  5. The button reads "Connecting…", then "Disconnect" once linked. The status line shows
     "Connected: " and the firmware your ECU reports.

Notes
  - Plugging in at key-on: when the saved USB cable powers up, the app links without changing the
    screen you're on. If the app isn't running, the dashboard starts.
  - Only the saved adapter is taken. With nothing saved, a plugged-in FTDI cable (or the only
    other USB serial device the app can drive) is used. While a Bluetooth adapter is saved, USB
    devices are left alone. A USB stick, phone or other dongle on the same hub is ignored.
  - Auto-reconnect keeps trying every few seconds while you're not linked. A link that stops
    sending data is dropped and made again.
  - Auto-reconnect pauses when you tap "Disconnect" (on the bar, or ☰ Menu ▸ Connection ▸
    Disconnect (stay on this tune)). It comes back with "Connect" / "Connect…", or by
    re-plugging the saved USB cable. The status line says "Disconnected — auto-reconnect paused.
    Tap Connect… to reconnect." (USB: "…Tap Connect… or re-plug USB to reconnect.")
  - The app doesn't link while an offline tune is open, or on a device set up as a HUD display.
  - The USB permission question only appears over the dashboard or the setup screen, never over
    the map or an editor. A refused USB permission isn't asked again until you tap "Connect" or
    re-plug the cable.
  - Status line messages (green = fine, red = a problem):
      "Tap Connect" — nothing linked yet.
      "Connecting to <name>…" / "Connecting (<adapter>)…" — trying.
      "Waiting for USB permission…" — answer Android's question.
      "USB device not attached — tap Connect" — the saved cable isn't plugged in or powered.
      "Bluetooth is off — turn it on to connect".
      "Allow Nearby devices so DashForge can reach your Bluetooth adapter" — tap the line to ask.
      "No ECU data — check baud (…)" / "No ECU data — check module baud (…)" — linked but no
        answer for about 30 s. The adapter's baud must match the ECU (115200; 9600 for an MS1).
      "Connected — no signature yet (…)" — see 2.2.1.
      "Connected — no reply from the MS1 (check the link is 9600 baud)" / "MS1: no answer".
      "Disconnected: <reason>" — for example "the Bluetooth adapter didn't answer (out of range
        or powered off?)", "the USB adapter was unplugged or reset", "garbled data from the
        adapter (check the baud rate)".
  - Starting on boot: only a dedicated HUD device can start DashForge on boot ("Auto-start as HUD
    on power / boot" in HUD & display, which needs the HUD unlock; see 6). Any other device starts
    it when the ECU cable is plugged in, as above.

==================================================================================================
2.4  Verifying your ECU
==================================================================================================
Where:   ☰ Menu ▸ Tuning ▸ Set up & verify this ECU — <status>… (status: "not set up", "<n> of 3
         checks passed" or "✓ verified"), then "③ Verify". Also the dashboard reminder, and
         ☰ Menu ▸ Connection ▸ Set up a new ECU…
Needs:   Free · a connected ECU (key on; the engine can be running or off) · an MSQ saved from
         this ECU by your tuning software.

What it does
  Verification proves that DashForge reads your tune exactly the way your tuning software does,
  before it's allowed to write anything. It only reads: nothing is written to the ECU. It takes
  about a minute over USB. All three checks must pass:
  - "① Settings probe (vs MSQ)" — "Your settings match your tune": every setting the ECU holds is
    compared with your MSQ, and converted both ways.
  - "② Tune health (connected)" — "The tune reads cleanly from the ECU": every table, curve and
    setting decodes, and temperatures make sense.
  - "③ Tune health (saved tune)" — "A saved copy reads back the same": the whole tune is saved to
    the Tune library and read back.

  Passing turns on editing and MSQ import / export for this firmware, on this device.

How to use it
  1. Have your MSQ in "② Your files" (see 2.2.2).
  2. On "③ Verify", tap "Verify".
  3. Wait for "The checks passed." If a check fails, the screen names it and offers the next step.
  4. After an app update that changed the firmware definition, the reminder says "Check this ECU
     again". Tap "Check now": about a minute, no files needed, as long as the ECU still runs
     the same firmware release.

Notes
  - Verification is kept per device. Verify again on each Android device you use.
  - It refuses while RAM may not hold your burned tune, and tells you how to fix it:
      a quick tune is live — "Revert to daily tune", or turn the key off and on and tap "The
        ignition was cycled";
      unburned changes — "Burn now", or turn the key off and tap "The key was cycled".
  - If the connection drops, it waits up to 2 minutes for the same ECU to come back, then carries
    on. Over USB it relinks by itself; on Bluetooth tap "Connect". If the ECU isn't back in time,
    or a different ECU or firmware answers, the run stops and nothing is recorded. Nothing is
    recorded until the two reads agree.
  - "The tune changed while it was being read (auto-tune or another tuning app?) — stop it and
    Verify again. Nothing was recorded."
  - A new firmware release on the ECU needs a fresh MSQ ("Choose a fresh MSQ").
  - If the built-in definition reads some settings differently from your MSQ, "Use my own INI
    instead" lets you build the definition from your INI.
  - Grandfathered firmwares: six firmwares were cleared for editing before verification existed:
    MS2/Extra comms330NP, comms342hU and comms342a2, MS3 0566.05 and 0566.05P, and Speeduino
    202501. They keep editing (MSQ import / export still needs verification), but show "⚠ This
    ECU hasn't been verified on this device…" in the Tuning menu and a reminder at every start
    until verified.
  - The single checks: ☰ Menu ▸ Tuning ▸ Settings probe (check vs MSQ)… ("Load MSQ…", "Run") and
    Tune health probe (tables + temps)… ("Run"; also works on an open offline tune). Each has
    "Copy" and "Share". They don't verify on their own: use the setup screen for that.
  - Until verified, the editors refuse with "Read-only until this ECU is verified (Tuning ▸ Set
    up & verify this ECU) — nothing written." (Not on a grandfathered firmware: see above.)


##### 3. THE DASHBOARD SCREEN #####

==================================================================================================
3.1  The dashboard and its top bar
==================================================================================================
Where:   It opens when you start DashForge. From the menu, "⌂ Dash" brings you back to it.
Needs:   Free · works with or without an ECU (with no ECU data, ECU readings show "--")

What it does
  The dashboard is DashForge's home screen: up to three pages of gauges, with a see-through button
  bar over them. The bar hides itself after a few seconds so the gauges get the whole screen.

How to use it
  1. Tap anywhere on the dashboard. The bar appears, with a "‹" arrow at the left edge, a "›"
     arrow at the right edge and the app's version number in the lower-right corner. They all hide
     again 5 seconds after your last touch.
  2. The bar, from left to right:
     - "☰ Menu": opens the menu (see 3.4). The "‹" arrow does the same.
     - The status line: what the ECU connection is doing ("Tap Connect", "Connecting to …",
       "Waiting for USB permission…"). Problems show in red.
     - "🧭 Navigation": opens the Navigation map. The "›" arrow does the same.
     - "Connect" / "Disconnect": "Connect" opens the "Connect to ECU" list of your USB adapters
       and paired Bluetooth adapters. While it reads "Connecting…", a tap cancels the attempt.
       "Disconnect" drops the ECU link.
     - "⏱ Laps" / "⏹ Laps": only there when you turn it on in the Lap timer ("Start / end button
       on the dashboard"). It starts a lap session at the track you are at, or ends the running one.
     - "● Log" / "■ Rec": "● Log" starts a datalog. While it records, the button reads "■ Rec";
       tap it to stop and save the log.
     - "✕ Exit": closes DashForge completely.
  3. In portrait the bar sits along the bottom of the screen, and the buttons show only their
     symbols (☰ 🧭 ⏱ ● ✕). The status line and the Connect button keep their words.

What you see when you use the buttons
  - Start a log: "Logging to <folder>". Stop it: "Log saved — <rows> rows, <n> with data (frame
    <size> B)". If it can't start: "Could not start log".
  - Disconnect: "Disconnected — auto-reconnect paused. Tap Connect… to reconnect." (Bluetooth), or
    "Disconnected — auto-reconnect paused. Tap Connect… or re-plug USB to reconnect." (USB). The
    app does not reconnect by itself until you tap "Connect" or plug the USB cable in again.
  - Start a lap session: "Lap session: <track>" (with "· datalog on" or "· datalog when the ECU
    connects" when the Lap timer is set to log). With no track here: "No track here: drop its
    start / finish line in the Lap timer first (☰ ▸ Lap timer)."
  - End a lap session: "End the lap session?" / "Its laps are saved (Lap timer ▸ Sessions…)." with
    "End" and "Cancel".

Leaving the app
  1. Tap "✕ Exit", or press Android's Back key on the dashboard.
  2. If you are connected to the ECU and "Confirm before exit while connected" is on (it is on
     unless you turn it off), DashForge asks "Leave DashForge?". The message starts "You're
     connected to the ECU." and adds, when they apply:
     - "A quick tune is live in RAM — it stays until you revert or key off."
     - "Auto-tune changes aren't burned: they stay in ECU RAM until key-off."
  3. Tap "Stay" to keep going, or "Leave".

Settings that change the bar
  - "Confirm before exit while connected": ☰ Menu ▸ Connection ▸ Confirm before exit while
    connected.
  - "Hide the 🧭 Navigation button (swipe down instead)": ☰ Menu ▸ Dashboard ▸ Display ▸
    HUD & display…. Swiping down still opens Navigation.
  - "Start / end button on the dashboard": in the Lap timer (☰ Menu ▸ Navigation ▸ Lap timer…).

Notes
  - "✕ Exit" ends everything with the app: the ECU link, a running datalog, the HUD link and
    navigation. Leaving with the Back key also ends the ECU link and the datalog.
  - "🧭 Navigation" is greyed while Navigation (DashForge Pro or DashForge Track) isn't unlocked;
    tapping it opens the unlock screen. On a HUD display device it follows the HUD unlock instead,
    and a tap only shows a short message.
  - On a phone set up as the HUD display device there is no "Connect" button: that phone gets its
    data from the head unit, not from the ECU.
  - When the status line reads "Allow Nearby devices so DashForge can reach your Bluetooth
    adapter", tap it: DashForge asks for the permission again, or opens Android's settings if
    Android won't show the question any more. Bluetooth needs this permission on Android 12 and
    later.
  - On Android 10 and older, the first "● Log" asks for storage permission. If you say no, the
    log is still written, to a folder the app can use; the "Logging to …" message names it.
  - A flashing "● Logging" label sits in the lower-right corner of every screen while a datalog is
    recording (see 3.3.7).

==================================================================================================
3.2  Gestures on the dashboard
==================================================================================================
Where:   On the dashboard, while the menu is closed and no warning banner is up.
Needs:   Swipe left / right: Free · Swipe down: DashForge Pro or DashForge Track · Double-tap:
         DashForge Pro or DashForge Track, on a head unit set up to send to a HUD device

What it does
  Swipes move between your dashboard pages and open Navigation. On a head unit that feeds a HUD
  device, a double-tap changes what the HUD device shows.

How to use it
  1. Swipe left to go to the page on the right. Swipe right to go to the page on the left. You can
     have up to three pages: Home in the middle, plus a left page and a right page (set them in
     ☰ Menu ▸ Dashboard ▸ Dashboards (change / import / delete)…, see 4.1). The new page slides in
     and a short message shows dots for the pages and the dashboard's name, e.g. "○ ● ○  Speed".
  2. If there is no page that way you see "No dashboard to the right — set one in Menu ▸
     Dashboard ▸ Dashboards." or "No dashboard to the left — set one in Menu ▸ Dashboard ▸
     Dashboards."
  3. Swipe down to open Navigation (the same as "🧭 Navigation").
  4. On a head unit that sends to a HUD device: double-tap an empty part of the dashboard. If the
     HUD is showing gauges (its own, or the dashboard you're on), it switches to Navigation ("HUD →
     Nav"). Otherwise it shows the dashboard you're on ("HUD → <dashboard name>"). See 6.4.4.

Notes
  - DashForge always starts on the Home page.
  - Swipes do nothing while the menu is open, and while a full-screen warning banner is up (tap
    "DISMISS" first, see 5.1).
  - If Navigation isn't unlocked, a swipe down only shows "🔒 Navigation — unlock it in Menu ▸
    Diagnostics & app ▸ Unlock / codes". The "🧭 Navigation" button opens the unlock screen instead
    (on a HUD display device: the HUD unlock, and a short message only).
  - A HUD display device has no pages: it shows what the head unit sends, so left / right swipes do
    nothing there.
  - On any other device a double-tap is just two taps. It only means something on a head unit
    with the HUD set up in ☰ Menu ▸ Dashboard ▸ Display ▸ HUD & display….

==================================================================================================
3.3  Banners and reminders on the dashboard
==================================================================================================
Where:   Strips stacked just above the button bar (at the top of the screen in landscape, at the
         bottom in portrait), pills near the top of the screen, and a few one-off questions.
Needs:   Free (each one appears only when the feature behind it is in use)

What it does
  These tell you about something you must not miss: changes that are not burned yet, a quick
  tune in RAM, the engine's start and warm-up, a check-engine fault, lost ECU data, a running
  datalog. The strips stack in this order: unburned changes (red), check engine (amber), start and
  warm-up, VE auto-tune (teal).

--------------------------------------------------------------------------------------------------
3.3.1  Unburned tuning changes
--------------------------------------------------------------------------------------------------
Needs:   DashForge Plus or Pro (Tuning) · ECU connected

  - In the menu, when a tuning screen changed values and you left without burning: "⚠ 2 unburned
    pages — tap to burn". Tap it; DashForge asks "Burn 2 pages to flash?" ("Changes made in
    Settings, Tables & curves or the tuning tools are live in RAM but go away at key-off until
    they're burned. Each page is CRC-checked after the burn.") with "Burn" and "Cancel".
  - Unburned changes live only in the ECU's RAM. Turning the key off loses them.

--------------------------------------------------------------------------------------------------
3.3.2  Quick tune LIVE / revert
--------------------------------------------------------------------------------------------------
Needs:   DashForge Pro (Quick-tune) · ECU connected

  - When a quick tune is loaded into the ECU's RAM, the quick-tune button on the dashboard shows
    "● LIVE · RAM". On a dashboard without that button a pill shows instead: "● Quick tune LIVE —
    tap to revert". The menu shows the same row at the top of every level. Tap it to go back to your
    daily tune.
  - "⚠ A quick tune may still be in RAM — tap": a quick tune was loaded before the app restarted,
    so DashForge can't be sure what the ECU is running. Tap it: "A quick tune may still be in RAM"
    explains that turning the ignition off and on goes back to your daily tune. Answer "The
    ignition was cycled" once you have done that, or "Not yet". Quick-tune swaps are held until
    then.
  - Full quick-tune rules: 7.9.

--------------------------------------------------------------------------------------------------
3.3.3  Start & warm-up strip
--------------------------------------------------------------------------------------------------
Needs:   Free · ECU connected · not on rusEFI

  - While the engine cranks, runs on afterstart enrichment or warms up, a strip shows the stage
    ("CRANKING", "AFTERSTART (ASE)", "WARMUP") with the AFR against its target and the enrichment.
    It goes away when the engine is fully warm. Tapping it does nothing.
  - With the engine off, the same place can show "capturing start…" while a start is being
    recorded, and tuning advice when "Optimize (suggest)" is on.
  - Full details and the switch that hides it: 5.3.

--------------------------------------------------------------------------------------------------
3.3.4  VE auto-tune strip
--------------------------------------------------------------------------------------------------
Needs:   DashForge Pro (VE auto-tune) · ECU connected

  A teal strip while VE auto-tune has something open. Tap it to open the VE auto-tune screen.
  - "● VE auto-tune tuning · 12 cells changed, unburned — tap to open" (or "paused", "dry run").
  - "VE auto-tune: 12 cells changed, unburned — tap to review".
  - "An auto-tune session was left open — tap to review it".
  - "A setting is switched off for VE auto-tune — tap to open and restore it". When you next
    connect to that car, DashForge turns the setting back on by itself and says "Restored the
    setting switched off for VE auto-tune ✓".

--------------------------------------------------------------------------------------------------
3.3.5  Check-engine banner
--------------------------------------------------------------------------------------------------
Needs:   Free · ECU connected · MS3 only

  An amber strip, "⚠ CHECK ENGINE: <fault names>", while the ECU reports a fault. Tap it to see
  the check-engine log and to dismiss the alert. Full details: 5.4.

--------------------------------------------------------------------------------------------------
3.3.6  No ECU data
--------------------------------------------------------------------------------------------------
Needs:   —

  - A red pill near the top: "⚠ NO ECU DATA — values not live". The link stopped bringing data,
    so the readings are not live. ECU readings show "--", and the start, check-engine and
    notification displays clear.
  - After you tap "Disconnect" it reads "Disconnected — no ECU data" instead.
  - It stays up until data comes back, then goes away by itself.

--------------------------------------------------------------------------------------------------
3.3.7  Logging badge
--------------------------------------------------------------------------------------------------
Needs:   —

  - "● Logging", a small red label in the lower-right corner. It flashes on every screen while a
    datalog is recording (it stays steady if Android's animations are turned off).
  - It is only a reminder: tapping it does nothing. Stop the log with "■ Rec" on the dashboard or
    "■ Stop datalog" in ☰ Menu ▸ Logging & dyno.

--------------------------------------------------------------------------------------------------
3.3.8  Questions and short messages that appear on the dashboard
--------------------------------------------------------------------------------------------------
Needs:   ECU connected (for the ECU reminders)

  - ECU verification reminder: once each time the app starts, while you are connected to an ECU
    that isn't verified on this device. It never appears over another screen or on a HUD display
    device. "Later" brings it back at the next start. One of:
    - "Set up <firmware>" with "Set up now": the app doesn't know this firmware yet.
    - "Verify this ECU" with "Verify now": "Editing and MSQ import/export are off until this ECU is
      verified. About a minute, with an MSQ saved from your tuning software."
    - "Check this ECU again" with "Check now": "The app was updated. Check this ECU again — about
      a minute, no files needed."
  - The first time a device sees a new ECU, the setup screen may open by itself. It waits until
    you are back on the dashboard, and until the car has stopped.
  - "Your DashForge files from before": after a reinstall on Android 11 and later, Android hides
    the logs and tunes the earlier install saved. "Choose the folder" lets you give DashForge its
    folder again (Documents ▸ DashForge, then "Use this folder"); "Not now" stops the question.
  - "Start captured: …": a start was recorded (when "Auto-capture starts" is on).
  - "Android restarted the screen — logging continues in a new file": Android rebuilt the
    dashboard while a log was running, so logging carries on in a new file.
  - "🔒 Imported dashboards aren't unlocked — showing a built-in (Menu ▸ Diagnostics & app ▸
    Unlock / codes)": see 4.1.

--------------------------------------------------------------------------------------------------
3.3.9  Full-screen warnings and notifications
--------------------------------------------------------------------------------------------------
  - Warning banners you set up fill the whole screen, flash and can sound an alarm. See 5.1.
  - Notification pills, toasts and tiles you set up appear near the top. See 5.2.

==================================================================================================
3.4  The menu
==================================================================================================
Where:   "☰ Menu" on the dashboard bar, or the "‹" arrow at the left edge.
Needs:   Free

What it does
  Every setting and tool in DashForge is in the menu. It opens over the dashboard as a grid of
  see-through tiles, one level at a time.

How to use it
  1. Tap "☰ Menu". The menu slides in from the left, at the top level.
  2. Tap a tile. A tile ending in "▸" opens the next level (its hint line says "Open ▸"). Other
     tiles open a screen, run an action, or flip a switch.
  3. Along the top:
     - "← Back": one level up. At the top level it closes the menu. Android's Back key does the
       same.
     - The breadcrumb, e.g. "Menu  ▸  Dashboard  ▸  Alerts": tap an earlier part to jump back to
       that level.
     - "⌂ Dash": closes the menu and goes back to the dashboard.
  4. When you close a screen you opened from the menu, the menu comes back at the same level and
     the same scroll position.

How to read the tiles
  - The top-level tiles have an icon, a name and a one-line description (for example Dashboard:
    "What's on the screen — dash style, gauges, colours, units").
  - Switches show their state on the second line: "ON ●" or "OFF ○". Tap the tile to flip it.
  - Rows that pick between choices show the current one, e.g. "Day / night: Auto (follow head
    unit)  (tap to change)". Each tap moves to the next choice.
  - There are 2 to 4 tiles per row, depending on how wide the screen is.

Locked and greyed tiles
  - DashForge Pro features: while a feature isn't unlocked, its tile is greyed and its name starts
    with "🔒". Tapping it opens the unlock screen, never the feature. (On a HUD display device it
    only says "🔒 <feature> isn't unlocked on this HUD device".) Unlock in ☰ Menu ▸ Diagnostics & app
    ▸ Unlock / codes….
  - Not on this firmware: some tiles are greyed because your ECU can't use them, e.g. "Calibrate
    TPS… — not on this firmware" or "Calibrate VSS… — no VSS on this ECU". Tap one to see why, e.g.
    "This firmware has no TPS calibration this app knows — calibrate TPS in your tuning software."
  - Off in this setup: in the firmware's own menus (under Tuning), a greyed row "<name> — Off in
    this setup" is one your tuning software also greys out. Tapping it says: "Off in this setup:
    your tuning software greys this out because of how the ECU is set up (another setting turns it
    off). Turn that setting on first, then this opens."

Rows that stay on top
  - While they apply, these rows sit at the top of every level so you can't miss them: "● Quick
    tune LIVE — tap to revert", "⚠ A quick tune may still be in RAM — tap" and "⚠ 2 unburned
    pages — tap to burn" (see 3.3.1 and 3.3.2).

Notes
  - "Unlock the device to open the menu": the dashboard is showing over the phone's lock screen
    (for example, a HUD device that started by itself). Unlock the phone first. Every ECU write
    sits behind the menu, so it stays shut until then.
  - A full-screen warning banner always shows on top of the menu.
  - The Tuning level changes with the connected ECU: it shows the menus of the firmware you are
    connected to (or the last one this device saw).

==================================================================================================
3.5  Find a setting…
==================================================================================================
Where:   ☰ Menu ▸ Find a setting… (the 🔍 tile, first in the top level)
Needs:   Free

What it does
  Searches the name of every row on every level of the menu, including the firmware's own menus
  (the same sections your tuning software shows) and each row on the Units screen. Tap a result to
  go straight to it.

How to use it
  1. Tap "Find a setting…". The "Find a setting" box opens with the keyboard up.
  2. Type a word (the hint suggests "e.g. needle, mph, boost, rotation…"). Results appear as you
     type: the row's name, and under it where it lives (e.g. "Menu ▸ Dashboard ▸ Alerts").
  3. Tap a result. A row that opens a screen opens it. A switch, an action or a group is shown in
     its place in the menu and flashes, so you can tap it yourself; Find never runs it for you.
  4. "Close" closes the box.

What it finds
  - Row names. Name matches come first, then rows whose path contains the word. Up to 60 results.
  - Extra words people use, for example: "mph", "celsius" or "psi" find Units; "needle", "layout"
    or "designer" find Dashboards; "alarm" finds Warning banners; "pill" or "toast" find
    Notifications; "ase" or "cranking" find Start & warm-up banner; "rotate" or "portrait" find
    Screen rotation; "headlight" finds Night / illumination signal; "speedo" or "gps" find Road
    speed from; "bluetooth" or "usb" find Connect…; "lambda" or "o2" find Closed-loop EGO;
    "wastegate" or "2-step" find the firmware's Boost or Launch menus, where it has them.
  - Units rows: each row of the Units screen is listed as "<name> — units", e.g. "Coolant gauge —
    units". Tapping one opens the Units screen.

Notes
  - "No matches — try another word.": nothing matched.
  - "“<name>” isn't available right now.": the row exists only in some situations (for example
    "Disconnect (stay on this tune)" while you aren't connected).
  - A locked row found here still goes through the unlock check.

==================================================================================================
3.6  What you see on a dashboard
==================================================================================================
Where:   On the dashboard. Which elements you get depends on the dashboard picked in 4.1.
Needs:   Built-in dashboards: Free · imported dashboards: DashForge Pro (Imported dashboards) · see
         each item

What it does
  A dashboard is made of elements: gauges, tiles, bars and so on, each showing one channel. You
  choose what each element shows in ☰ Menu ▸ Dashboard ▸ Assign channels… (4.3), and the
  colours in ☰ Menu ▸ Dashboard ▸ Colours & theme… (4.4).

--------------------------------------------------------------------------------------------------
3.6.1  Gauges, studio dials, digital tiles and bars (built-in dashboards)
--------------------------------------------------------------------------------------------------
Needs:   Free

  - Analog gauges: round needle dials. Each "Analog" built-in has 1 to 6 of them. "Analog — Grid
    of 6" shows RPM, MAP, coolant, AFR, battery voltage and TPS.
  - Digital tiles: boxes with a value, its unit and a label. "Digital — tach bar + 6 tiles" adds a
    bar-graph tach across the top; "Digital — 9 tiles" is all tiles.
  - Studio dial: a big designed dial; the built-in is "Studio tach".
  - Gauges mark their warning and danger ranges, and readouts turn the "Warning" and "Danger /
    redline" colours inside them.
  - "--" means no reading: there's no ECU data, or the channel isn't on this firmware. Assign
    another channel in 4.3.

--------------------------------------------------------------------------------------------------
3.6.2  The Speed dashboard
--------------------------------------------------------------------------------------------------
Needs:   Free · GPS or an ECU road-speed (VSS) signal for the speed · gear detection for the gear

  - A wrap-around tach with eight readout cells around it, and a centre cluster showing RPM,
    GEAR and SPEED. Four shift lamps light as the revs rise (two amber, then two red).
  - The cluster's speed comes from the "Road speed from" choice (☰ Menu ▸ Dashboard ▸ Display):
    GPS, or the ECU's VSS (with GPS used when the ECU has none).
  - The gear is the firmware's own gear reading when it reports one; otherwise DashForge's own
    estimate, once ☰ Menu ▸ Vehicle & calibration ▸ Gear detection… is set up. Without either it
    shows "–".
  - On the device you can change: what each of the eight cells shows, the tach style (needle,
    gradient fill bar, or both) and the four shift-light RPM points. All are in ☰ Menu ▸
    Dashboard ▸ Assign channels… (4.3). The fill bar's colours and transparency are in Colours &
    theme (4.4).

--------------------------------------------------------------------------------------------------
3.6.3  Elements only imported dashboards have
--------------------------------------------------------------------------------------------------
Needs:   DashForge Pro (Imported dashboards), plus what each item lists

  An imported dashboard (designed at dashdesigner.appforged.cc, see 4.2) can also have:
  - Lamps and shift lights that light from a channel.
  - Notification elements: a pill or tile that shows when a channel crosses a limit, or a toast
    that pops once.
  - Quick-tune buttons (needs DashForge Pro (Quick-tune) and a connected ECU). Each loads a saved
    tune into the ECU's RAM; nothing is burned, and turning the key off goes back to your daily
    tune. A button's small label says its state: "tap to pick a tune" (not set yet), "tap → RAM"
    (ready), "● LIVE · RAM" (its tune is running; tap again to revert), "unavailable" (no ECU
    link) or "🔒 locked" (Quick-tune isn't unlocked). The first tap asks you to pick a tune from
    your Tune library ("Quick-tune: <label> — pick a tune", with "Ask before loading
    (recommended)", "Bind", "Cancel"). Press and hold a button to change or "Remove" its tune. The
    buttons show and hide with the top bar; one whose tune is live stays up. The safety rules are
    in 7.9.
  - A live map and a next-turn panel (needs DashForge Pro or DashForge Track, see the next item).
  - A mood figure (see 3.6.5) and moving backgrounds (see 3.6.6).

--------------------------------------------------------------------------------------------------
3.6.4  Live map and next-turn elements
--------------------------------------------------------------------------------------------------
Needs:   DashForge Pro or DashForge Track · GPS · a map source (your own Geoapify key or DashForge
         Track) · internet for the map

  - Map: a small live map with your position and route, drawn inside the dashboard. It needs the
    same map source as Navigation. Its message says what is missing:
    - "🔒 Map isn't unlocked": Dashboard maps isn't unlocked.
    - "Map needs a Geoapify key or DashForge Track (Navigation ▸ Source)": no map source set.
    - "Waiting for GPS…": no GPS fix yet.
    - "Map: head unit only": on a HUD display device the map element doesn't draw.
  - Next turn: the next turn's arrow, distance and street. It shows only while Navigation is guiding
    you along a route (Navigation needs DashForge Pro or DashForge Track) and stays empty the rest
    of the time.

--------------------------------------------------------------------------------------------------
3.6.5  Mood figure
--------------------------------------------------------------------------------------------------
Needs:   DashForge Pro (Imported dashboards: mood figures come only in imported dashboards)

  - A small animated picture whose mood follows the engine, as the dashboard's designer set it up:
    for example bored at idle, sweating when the coolant is hot, asleep with the engine off.
  - It is decoration, not a warning. Your warning banners stay the alerts.
  - "Animate mood figures" (☰ Menu ▸ Dashboard ▸ Display) turns the animation off; the pictures
    then stay still.
  - The pictures don't move in HUD projection or on a HUD display device.
  - The channels its moods watch can be changed in Assign channels (rows "Mood figure · <mood>").

--------------------------------------------------------------------------------------------------
3.6.6  Moving backgrounds
--------------------------------------------------------------------------------------------------
Needs:   DashForge Pro (Imported dashboards)

  - An animated effect behind the whole dashboard, or on a dial's face, such as stars, rain, snow,
    flames or a grid. The designer picks it; some effects speed up with the RPM or road speed.
  - There is no switch on the device; pick a dashboard without one if you don't want it.
  - In HUD projection or on a HUD display device nothing moves: the plain background shows.

--------------------------------------------------------------------------------------------------
3.6.7  Readings from the device itself
--------------------------------------------------------------------------------------------------
Needs:   Free · the sensor each one uses (see Notes)

  Besides ECU channels, any element can show values DashForge works out itself: Clock, GPS
  Speed, Device batt (this device's battery %), MPG, Avg MPG, Range and Fuel (from the Trip / fuel
  computer), Long g, Lateral g and Combined g, and the lap timer's Lap time, Lap delta, Predicted
  lap, Last lap, Best lap and Lap.

Notes
  - GPS Speed and the map need GPS and location permission with "Use precise location" on.
    With approximate location only you see "GPS speed needs precise location. Turn on "Use
    precise location" in DashForge's location permission."
  - The g readings need an accelerometer. They work out which way the car points from GPS, so
    they need a few speed changes and turns first. A head unit with no accelerometer uses the HUD
    phone's g readings when a HUD phone is connected.

--------------------------------------------------------------------------------------------------
3.6.8  Battery icon
--------------------------------------------------------------------------------------------------
Where:   ☰ Menu ▸ Dashboard ▸ Display ▸ Battery icon (switch; on unless you turn it off)
Needs:   Free · a device with a battery

  - A small upright battery in the top-right corner shows this device's charge, with a lightning
    bolt while charging. Full details: 6.7.


##### 4. DASHBOARD SETTINGS #####

==================================================================================================
4.1  Dashboards (change / import / delete)…
==================================================================================================
Where:   ☰ Menu ▸ Dashboard ▸ Dashboards (change / import / delete)…
         Also: open a .msdash file from a file manager, or share one to DashForge.
Needs:   Built-in dashboards: Free · "Import dashboard…" and showing imported ones: DashForge Pro
         (Imported dashboards) · deleting: Free

What it does
  Chooses which dashboard each of your three swipe pages shows, and imports or deletes your own
  dashboards (.msdash files).

How to use it: pick the dashboard for each page
  1. The screen says "Swipe left / right on the dashboard to move between these pages." and lists
     three buttons:
     - "Home: <dashboard>": the page DashForge starts on.
     - "Left page (swipe right): <dashboard or none>"
     - "Right page (swipe left): <dashboard or none>"
  2. Tap a page. A list of every dashboard opens: the built-ins first, then your imported ones
     (shown as "<name>  (imported)"). The left and right pages also offer "None".
  3. Tap a dashboard. It's saved straight away. "Close" leaves the list as it was.

The built-in dashboards
  "Analog — Single", "Analog — Two", "Analog — Three", "Analog — Hero + 2", "Analog — Grid of 4",
  "Analog — Hero + 3", "Analog — 3 + 2", "Analog — Grid of 6", "Digital — tach bar + 6 tiles",
  "Digital — 9 tiles", "Speed", "Studio tach".

How to use it: import a dashboard
  1. Get the .msdash file onto the device (see 4.2).
  2. Tap "Import dashboard…". Where the device has a file picker you can choose "Choose with the
     file picker" or "Browse this device" (DashForge's own list of .msdash files in Download,
     Documents and storage).
  3. Pick the file. "Importing…" shows while it's checked.
  4. "Imported “<name>”" appears, asking "Show it on your home page now?". Tap "Show now" to put it
     on the Home page, or "OK" to keep your current one.
  5. If DashForge found something it had to skip, the title reads "Imported “<name>” — with notes"
     and lists them (see Notes).
  6. If it's a newer export of a dashboard you imported before, the message says so ("It's an
     updated version of “<name>”, which you imported before: your channel choices from it were
     kept."). "Remove old copy" asks "Remove “<name>”?" ("The earlier copy goes from your
     dashboards; wherever it was showing, this one takes its place. Your original .msdash file is
     untouched.") Tap "Remove".
  7. A dashboard with credited artwork lists it ("Artwork: …").

Other ways to import
  - Open the .msdash file from a file manager and choose DashForge, or share it to DashForge from
    email, a browser, a messaging app or Bluetooth. DashForge asks "Import dashboard?" / "Import
    “<file>” into your dashboards?" with "Import" and "Cancel", then carries on as above. Some
    file managers don't offer DashForge for .msdash files; "Import dashboard…" always works.

How to use it: delete an imported dashboard
  1. Tap "Delete imported dashboard…". A list of your imported dashboards opens ("Delete imported
     dashboard").
  2. Tap one. "Delete “<name>”?" / "Removes this dashboard from the app. Your original .msdash file
     is untouched." Tap "Delete". You see "Deleted.".
  3. Built-in dashboards can't be deleted. With none imported you see "No imported dashboards to
     delete."

Notes
  - The dashboard design DashForge Track emails each month loads with Track alone; any other
    imported dashboard needs DashForge Pro. Those designs are signed by DashForge. One that was
    changed or damaged on the way is refused: "This dashboard says it was signed by DashForge,
    but its signature doesn't check out (the file was changed or damaged), so it wasn't imported.
    Download it again from the email it came in."
  - Imported dashboards need DashForge Pro. While Imported dashboards isn't unlocked, "Import
    dashboard…" shows "🔒" and is greyed (a tap opens the unlock screen), locked ones show "🔒" in the
    lists, and the dashboard shows a built-in instead, once saying "🔒 Imported dashboards aren't
    unlocked — showing a built-in (Menu ▸ Diagnostics & app ▸ Unlock / codes)". The file is kept, so
    it comes back once you unlock. Deleting is always free.
  - When you delete the dashboard that was on Home, Home goes back to a built-in. A deleted side
    page becomes "none". Quick-tune buttons bound on that dashboard lose their tunes.
  - Import notes you may see: "Not on this firmware: <channel> — it reads "--" until assigned in
    Menu ▸ Dashboard ▸ Assign channels.", "<element>: channel "<x>" is not a known channel — it will
    read "--".", "It uses custom datalog channels that can't be checked until the ECU has been
    connected once."
  - How a dashboard looks (gauge face, needle, layout) comes from its file: change it in the
    designer (4.2). What each element shows is Assign channels (4.3); colours are Colours & theme
    (4.4).
  - On a HUD display device the head unit chooses what it shows. A dashboard you pick here on the
    HUD device wins over the one the head unit sent.
  - With DashForge Track, cloud sync also backs up your imported dashboards and brings them to
    your other linked devices.
  - Files over about 4 MB, or not made as a .msdash dashboard, are refused (see 17.4).

==================================================================================================
4.2  The DashForge Designer (dashdesigner.appforged.cc)
==================================================================================================
Where:   A website: dashdesigner.appforged.cc, in any web browser (computer, tablet or the car's
         device). About… in the app names it too.
Needs:   Free to use · internet to open it · showing the result in DashForge: DashForge Pro
         (Imported dashboards) · map and next-turn elements: DashForge Pro or DashForge Track; on a
         HUD display device a map element reads "Map: head unit only"

What it does
  You design a dashboard in the browser: place gauges, tiles, bars, lamps, maps, quick-tune
  buttons, mood figures, warning banners and moving backgrounds, and pick each one's channel and
  colours. The result is a .msdash file that DashForge imports.

How to use it
  1. Open dashdesigner.appforged.cc.
  2. Start from scratch ("New"), from an example ("Sample", "Integrated"), or restyle one of the
     app's own dashboards ("Built-ins…"). "Import…" opens a .msdash you made before.
  3. "Day" / "Night" previews both colour sets; "▶ Demo" moves the gauges with made-up driving
     data.
  4. Tap "Export .msdash". The browser downloads the file. If the designer's self-check finds
     problems it lists them first and asks "Export anyway?".
  5. Get the file onto the car's device:
     - Easiest: open the designer in the device's own browser and export there, so the file lands
       in its Download folder.
     - Or copy it from your computer (USB cable, email, a cloud drive or a messaging app).
  6. In DashForge, ☰ Menu ▸ Dashboard ▸ Dashboards (change / import / delete)… ▸ "Import
     dashboard…", or open / share the file to DashForge (4.1). Tap "Show now".

Notes
  - Restyling a built-in keeps the channel choices you made for it: they come along on import.
  - Moving backgrounds don't move in HUD projection or on a HUD display device.
  - A dashboard can carry its own warning banners. They run alongside the ones you set up in
    5.1; they never replace yours.

==================================================================================================
4.3  Assign channels…
==================================================================================================
Where:   ☰ Menu ▸ Dashboard ▸ Assign channels…
Needs:   Free · the firmware's channel list comes from the connected ECU (or the last one this
         device saw)

What it does
  Chooses what each element of the dashboard on screen shows: any standard channel, or any
  channel your firmware sends, with its own label, units and range. On the Speed dashboard it also
  sets the eight readout cells, the tach style and the shift lights.

How to use it
  1. On the dashboard, go to the page you want to change (Assign channels works on the dashboard
     that's showing). Then open ☰ Menu ▸ Dashboard ▸ Assign channels….
  2. The title reads "Assign channels — <dashboard name>", with the hint "Pick what each element
     shows. “Default” uses the channel the dashboard was designed with."
  3. Each element is listed by its label (or "Gauge 1", "Tile 2", "Bar 1", "Tach"). Its button
     shows its channel and "· default", "✎ changed" or "⚠ not on this firmware — tap to assign".
  4. Tap the button. Choose:
     - "Default (<channel>)": back to what the dashboard was designed with.
     - "＋ Custom datalog channel…": any channel the firmware sends. Pick it from the list ("Filter
       channels…" narrows it), then fill in "Label", "Units (optional, e.g. %)", "Decimals",
       "Min (scale start)" and "Max (scale end)", and tap "Set".
     - "✎ Edit <channel> — label, units, range…": change a custom channel's setup.
     - Any standard channel in the list, shown as "<name> (<key>)".
  5. Choices save straight away.

The Speed dashboard's extras
  - "Speed readout cells", "Cell 1" to "Cell 8": tap to choose what a cell shows, the same way
    (custom channels too). A cell that still has the dashboard's choice shows "(this dashboard's
    own)". "↺ Undo this pick (back to <channel>)" returns a cell to it.
  - "Tach: needle  (tap to switch)": each tap moves to "gradient fill bar", then "needle + fill
    bar", then back. If the dashboard sets its own, the button reads "Tach: <style>  (set by this
    dashboard)" and can't be changed.
  - "Shift lights…": four RPM points, "Amber 1 (lowest RPM)", "Amber 2", "Red 1" and "Red 2
    (redline)". "Shift-light RPM points for this dashboard. Blank = the dashboard's own (shown
    faded); 0 = automatic, from the redline:". Tap "Save" ("Shift lights saved").

Notes
  - Choices are kept per dashboard. Importing an updated copy of the same dashboard keeps them.
  - The tach style choice applies to every Speed-style dashboard that doesn't set its own.
  - A warning at the top, "⚠ 2 custom channels aren't on this firmware and read “--”: … Tap the
    marked ones to assign.", means the dashboard asks for channels this ECU doesn't send.
  - Offline, the channel list is the last firmware this device was connected to.
  - "This dashboard has no assignable channels." / "This dashboard couldn't be read. Pick another
    one in Menu ▸ Dashboard ▸ Dashboards."

==================================================================================================
4.4  Colours & theme…
==================================================================================================
Where:   ☰ Menu ▸ Dashboard ▸ Colours & theme…
Needs:   Free

What it does
  Sets the colours of every dashboard, as one palette: "One palette shared by every dashboard —
  built-in and imported." Each colour role has a Day and a Night colour.

How to use it
  1. The top of the screen is a live preview of the dashboard you're using. "Preview: Day" and
     "Preview: Night" switch it.
  2. Under "Day colours" and "Night colours", each role has a swatch and an "Edit" button. Tap
     "Edit": pick one of the preset swatches or move the R, G and B sliders (the colour's code
     shows above them), then "OK" (or "Cancel").
  3. Changes save straight away; the dashboard uses them when you go back to it.
  4. "Reset all to defaults" asks "Reset all colours?" ("Every colour on this screen goes back to
     its default, day and night. This can't be undone.") Tap "Reset".

The colour roles
  "Background", "Text", "Tile background", "Tile value", "Tile label", "Tile edge / 3D border",
  "Accent (band / bars)", "Needle", "Center / trim", "Warning", "Danger / redline", "Quick-tune
  active", "Speed fill — low RPM", "Speed fill — high RPM".

Settings on this screen
  - "Gradient fill" / "Fill opacity: <n>%": the transparency of gradient tach fills (the Speed
    dashboard's fill tach, and designer fills that use the "Speed fill" colours). It applies to
    day and night.

Day and night
  - Pick the mode in ☰ Menu ▸ Dashboard ▸ Display ▸ "Day / night: …  (tap to change)". Each tap
    moves on: "Auto (follow head unit)", "Day", "Night".
  - Auto follows the head unit's day / night signal (its headlight wire) where it has one,
    otherwise Android's dark-theme setting. On a HUD display device, Auto follows the head unit.
    The app checks once a second, so the gauges change soon after the headlights do.
  - What follows day / night: the dashboard's background and gauges, the battery icon,
    notification pills and tiles, the quick-tune LIVE pill (the "Quick-tune active" colour), the
    dashboard's own warning banners and the map element. If you set manual day / night brightness
    in ☰ Menu ▸ Dashboard ▸ Display ▸ HUD & display…, the screen brightness follows too.

Notes
  - An imported dashboard can fix some of its colours itself in the designer. Those parts keep
    their own colours whatever you set here.

==================================================================================================
4.5  Units…
==================================================================================================
Where:   ☰ Menu ▸ Dashboard ▸ Units…   (Find a setting also lists every row, e.g. "Coolant gauge —
         units")
Needs:   Free

What it does
  Chooses imperial or metric units for each place in the app that shows a value, one by one. For
  example: everything metric, but temperatures in °F.

How to use it
  1. "Pick a baseline with All Imperial / All Metric, then flip just the readouts you want the
     other way."
  2. Tap "All Imperial" or "All Metric" ("All set to imperial" / "All set to metric").
  3. The rows are grouped by type (TEMPERATURE, SPEED, PRESSURE, FUEL ECONOMY, DISTANCE, FUEL
     VOLUME, POWER, TORQUE). Each group's "all:" buttons set the whole group at once.
  4. Each row has two buttons; the one in use is green. Tap the other to switch.

The rows (imperial / metric)
  - Temperature (°F / °C): "Coolant gauge", "Intake-air (IAT) gauge", "Outside temperature".
  - Speed (mph / km/h): "Speed (VSS) gauge", "Road speed (GPS speed, Speed cluster)", "Nav speed",
    "Performance meter (speeds, stopping distance)".
  - Pressure (psi / kPa): "MAP gauge", "Vac/Boost gauge" (its buttons are "inHg/psi" and "bar"),
    "Barometer gauge", "Oil Pressure gauge", "Fuel Pressure gauge", "Boost / dome target tables",
    "Overrun (DFCO) MAP threshold".
  - Fuel economy (mpg / L/100): "MPG gauge / readout", "Trip economy", "Nav MPG box".
  - Distance (mi / km): "Trip distance / range", "Nav distances".
  - Fuel volume (gal / L): "Fuel level gauge", "Fuel used / tank".
  - Power (hp / kW): "Dyno power". Torque (lb·ft / N·m): "Dyno torque".

Notes
  - Units only change how DashForge shows values. Nothing is written to the ECU, and the ECU's
    own unit settings stay as they are.
  - Temperatures in your datalogs, captured starts and the cranking and auto-tune screens use
    the "Coolant gauge" choice. The log viewer's road speed uses the "Speed (VSS)
    gauge" choice.
  - Warning-banner thresholds don't follow these choices: they are typed in the channel's own
    unit (the editor says "temperatures are °F"). See 5.1.
  - Changes show on the next screen you open.


##### 5. ALERTS #####

==================================================================================================
5.1  Warning banners…
==================================================================================================
Where:   ☰ Menu ▸ Dashboard ▸ Alerts ▸ Warning banners…
Needs:   Free · ECU connected (they watch live ECU data) · sound plays at Android's alarm volume

What it does
  Watches any channel your ECU sends and, when it goes above or below a limit, fills the screen
  with a flashing banner and sounds an alarm. For example: oil pressure below 20 while the engine
  runs, coolant above 230, knock above 0.

How to use it
  1. Tap "+ Add" at the top. ("Banners show full-screen, flashing, most-severe first. Dismiss
     silences until it clears (or snoozes).")
  2. Fill in "New warning":
     - "Name": what the list calls it.
     - "Channel": tap and pick from "Trigger channel" ("Filter channels…" narrows the list). Each
       channel shows its unit.
     - "Condition": tap to switch between "is above" and "is below".
     - "Threshold": "In the channel's own unit, shown beside its name — temperatures are °F. Above
       and below are strict."
     - "Only while the engine is running" and "Engine running above (RPM)": the warning waits
       until the RPM has stayed above this for 3 seconds, so it doesn't fire at key-on, while
       starting or at shutdown. Keep it well below your idle. It ticks itself when you choose "is
       below", unless you've set it yourself.
     - "Message": the big text on the banner.
     - "Severity": tap to move through "Info", "Warning", "Critical".
     - "Banner colour" and "Text colour": Red, Orange, Amber, Green, Blue, Slate, Black or White.
     - "Flash until dismissed".
     - "Audible alert" and "Alert sound": "Built-in beep (tap to choose a file)". Tap it to pick
       your own sound ("Accepted: MP3, WAV, OGG, M4A/AAC, FLAC. Pick from permanent storage (not a
       temp download).").
     - "Also write to the event log".
     - "Enabled".
     - "Preview": "▶  Preview banner + sound" shows the banner full screen and plays its sound
       ("Preview — tap to close").
     - "Debounce (s)": how long the condition must hold before the banner shows (0.5 s to start).
     - "On dismiss": "Silence until clear" or "Snooze", and "Snooze (s)".
  3. Tap "Save". Without a channel it stays open: "Pick a channel first — a warning with no channel
     never fires".
  4. Tap a warning in the list to edit it. "Delete" asks "Delete “<name>”?" ("This warning stops
     watching for its condition. This can't be undone.").

When a warning fires
  - The banner fills the screen in its colours, with its message and a "DISMISS" button. It
    shows over everything on the dashboard, the menu included.
  - Tap "DISMISS", or press and hold anywhere on the banner. "Silence until clear" keeps it away
    until the reading goes back inside the limit; "Snooze" brings it back after the snooze time
    if the reading is still out.
  - If several fire at once, the most severe shows first and the others wait behind it.
  - The sound repeats while the banner is up, and turns other audio down while it plays.
  - The list shows each warning's summary, e.g. "Oil Pressure  is below  20  while running   ·
    Warning · flash". Switched-off warnings show "(off)".

Notes
  - Banners and their sound work only while the dashboard is on screen. A warning that fires while
    another screen is open sounds when you come back to the dashboard.
  - The sound uses Android's alarm volume. If it is at zero you see "Alarm volume is off —
    warning sounds are silent. Turn up the alarm volume in Android settings."
  - If your sound file won't play, the built-in beep plays instead.
  - A reading must stay back inside the limit for about 1.5 seconds before the warning can fire
    again, so a reading hovering at the limit doesn't keep popping it up.
  - When ECU data stops, active warnings clear and wait for data again. Ones you dismissed or
    snoozed stay that way.
  - "Also write to the event log" adds a "WARNING: <message>" line with a snapshot (RPM, MAP,
    coolant) to ☰ Menu ▸ Diagnostics & app ▸ Event log (knock / faults / limiters), at most once
    every 30 seconds per warning. It writes only while the event log is ON (15.3).
  - An imported dashboard can bring its own warning banners. They run alongside yours (yours
    win when both fire) and use built-in tones only.
  - The channel list comes from the connected firmware, or the last one this device saw.

==================================================================================================
5.2  Notifications…
==================================================================================================
Where:   ☰ Menu ▸ Dashboard ▸ Alerts ▸ Notifications…
Needs:   Free · ECU connected (they watch live ECU data)

What it does
  Small, quiet on-screen notices from any channel: a pill that shows while something is on, a
  toast that pops once when it starts, or a tile that always shows a live value. No sound and
  nothing to dismiss; for loud alarms use Warning banners (5.1).

How to use it
  1. Tap "+ Add" at the top. ("No notifications yet. Tap “+ Add” to watch a channel — e.g. an ASE
     bit as a pill, or CLT above a limit as a toast.")
  2. Pick the channel ("Pick a channel"). The "Add notification" box opens:
     - "Channel: <name>": tap to change it.
     - "Trigger": "When ON (bit / nonzero)", "When above a value" or "When below a value".
     - "threshold value (<unit>)": for above / below.
     - "Label (shown on screen)".
     - "Show as": "Pill (shows while active)", "Toast (pops once when it triggers)" or "Tile
       (always-on live value)".
     - "Enabled".
  3. Tap "Save".
  4. Tap a notification in the list to edit it. Tap its "✕" to remove it; "Removed “<label>” — tap
     to undo" lets you bring it back for 8 seconds.

On the dashboard
  - Pills and tiles sit in a row near the top centre of the screen. A tile reads "<label>: <value>
    <unit>" (a bit channel reads "on" or "off").
  - A toast pops once each time its trigger starts (again 5 seconds later at the earliest).
  - Each pill holds its state for at least a second, so a flickering channel doesn't flash it.
  - With no ECU data, tiles read "—" and pills hide.
  - They take the dashboard's day / night colours.

Notes
  - The screen says how many channels you can pick from: "<n> channels available on the connected
    firmware." Offline it uses the last firmware this device saw ("offline set — connect the ECU to
    see all of them").
  - Switched-off notifications show "(off)" in the list.

==================================================================================================
5.3  Start & warm-up banner
==================================================================================================
Where:   ☰ Menu ▸ Dashboard ▸ Alerts ▸ Start & warm-up banner (switch: "ON ●" / "OFF ○"; on unless
         you turn it off)
Needs:   Free · ECU connected · MS3/MS2, MS1, Speeduino, or a firmware set up from your INI that
         has an engine-status channel · not on rusEFI

What it does
  A strip on the dashboard during a start: which stage the engine is in, with the AFR against the
  target and the enrichment, until the engine is fully warm.

What it shows
  - The stage: "CRANKING" (dark red), "AFTERSTART (ASE)" (dark amber; some firmware adds the
    afterstart percentage, e.g. "AFTERSTART (ASE) +12%") or "WARMUP" (dark blue).
  - "AFR 13.2 / tgt 13.5" followed by "RICH", "LEAN" or "on-tgt" (within 0.3 of the target), or
    "AFR warming" while the wideband reading isn't usable yet.
  - "enrich 112%": the ECU's current enrichment, where the firmware sends it.
  - It goes away when the engine is running fully warm. Tapping it does nothing.

How to use it
  1. Leave it on to watch your starts and warm-ups.
  2. Tap "Start & warm-up banner" in Alerts to turn it off.

Notes
  - Turning it off hides only the cranking / afterstart / warm-up strip. These still show: the
    "capturing start…" note and the tuning advice while the engine is off, the check-engine
    banner and your warning banners.

==================================================================================================
5.4  Check-engine banner
==================================================================================================
Where:   Appears on the dashboard by itself. Its history: ☰ Menu ▸ Diagnostics & app ▸ Check-engine
         log (see 15.2).
Needs:   Free · ECU connected · MS3 with DashForge's built-in MS3 support (not MS2/Extra, MS1,
         Speeduino, rusEFI, or an MS3 set up from your own INI)

What it does
  When the ECU flags a check-engine fault, an amber strip names it, e.g. "⚠ CHECK ENGINE: Coolant
  sensor, TPS". The moment a new fault appears it is also written to the check-engine log with
  the time and a snapshot of RPM, coolant, MAP, TPS, battery voltage and AFR, so you can see what
  tripped it even if you weren't looking.

What can raise it
  "MAP sensor", "IAT sensor", "Coolant sensor", "TPS", "Battery voltage", "O2 / AFR sensor", "Loss
  of sync", "EGT sensor", "Flex-fuel sensor", "MAF sensor", "Knock sensor", "Cam sensor", "Oil
  pressure", "Fuel pressure", "EGT safety shutdown", "AFR safety shutdown", "Water-injection low",
  "Safety shutdown". For loss of sync the ECU's reason number is added, e.g. " (sync reason 3)".

How to use it
  1. Tap the strip. The "Check-engine log" opens with the most recent events.
  2. "Dismiss alert" hides the strip for the faults showing now ("Check-engine alert dismissed").
     A new, different fault brings it back.
  3. "Clear log" asks "Clear the check-engine log?" ("Every recorded entry goes. This can't be
     undone.") Tap "Clear". "Close" just closes.

Notes
  - Dismissing only hides DashForge's strip. The ECU keeps the fault until it clears it itself
    (after a key cycle, or from your tuning software).
  - The log is kept when the app or the car restarts. With nothing recorded it says "No
    check-engine events recorded yet."
  - The strip hides while there's no ECU data.
  - On other firmware there is no check-engine banner. You can make a warning banner (5.1) on your
    firmware's own fault or status channel instead.


##### 6. DISPLAY AND HUD #####

==================================================================================================
6.1  Day / night
==================================================================================================
Where:   ☰ Menu ▸ Dashboard ▸ Display ▸ Day / night: <choice>  (tap to change)
Needs:   Free · no ECU needed · "Auto" uses a day/night signal from the head unit when it has one

What it does
  Switches DashForge between its day look and its night look. At night the dashboard uses the night
  colours from Colours & theme…, the map is tinted for night, the notification pills follow, and,
  if you set manual brightness, the screen dims to your night level.

How to use it
  1. Tap the row. Each tap moves to the next choice: "Auto (follow head unit)" → "Day" → "Night" →
     back to "Auto (follow head unit)".
  2. The row always shows the choice in use, for example "Day / night: Night  (tap to change)".

Settings on this screen
  - "Auto (follow head unit)" (the default): the app follows the device.
      On a head unit that reports day/night (many set it from the headlight / illumination wire),
      the look changes with your headlights.
      On a phone or tablet, or a head unit that doesn't report it, it follows Android's own night
      mode (dark theme).
      On a HUD device (set to "HUD client (receive)"), it follows the head unit's day/night, sent
      over the HUD link, because nothing on the HUD device is wired to the headlights.
  - "Day": always the day look.
  - "Night": always the night look.

Notes
  - Day or Night picked by hand always wins, on a HUD device too.
  - The app checks about once a second, so the look changes within a second or so of the lights.
  - The day and night brightness levels are set in ☰ Menu ▸ Dashboard ▸ Display ▸ HUD & display… ▸
    "Screen brightness" ▸ "Manual (separate day / night)" (see 6.4.9). With "System / auto",
    Android keeps control of the brightness.
  - "HUD projection" always uses full brightness, day or night (see 6.4.8).
  - If "Auto" never turns to night when you switch the headlights on, your head unit signals night
    in some other way. Run Night / illumination signal… (6.3) and send the result to support.
    Until then, pick "Day" or "Night" by hand.

==================================================================================================
6.2  Language
==================================================================================================
Where:   ☰ Menu ▸ Dashboard ▸ Display ▸ Language: <language>  (tap to change)
Needs:   Free · internet to see the list and to download a language · no ECU needed

What it does
  Changes the language of the app's text. English is built in. Every other language is a download
  that is fetched only when you pick it, and only the language you chose is kept on the device.

How to use it
  1. Tap the row. The app shows "Checking which languages are available…".
  2. Pick a language from the "Language" list. "English (built in)" is always at the top.
  3. The app shows "Downloading <language>…", then "<language> is on. Text already on the
     dashboard switches when DashForge next starts."
  4. Close DashForge and start it again so the dashboard's own text changes too.

Notes
  - Once downloaded, the language works with no internet. While a language other than English is
    chosen, the app checks for a newer version of it at most once a day when it's online, and
    swaps it in by itself.
  - No internet: "Can't reach the language list. Connect to the internet and try again. English is
    always available." The list opens only after it has been fetched, so switching back to English
    also needs a connection.
  - A download that fails: "<language> couldn't be downloaded. Check the internet connection and
    try again."
  - Every language file is signed. One that is damaged or not genuine is never used: "The
    <language> file didn't pass its check, so it wasn't used."
  - Any text that isn't translated yet shows in English.
  - Right-to-left languages (Arabic, Hebrew and Urdu): the text itself reads
    right to left, but the screens keep their left-to-right layout. Buttons, gauges and menus stay
    where they are in English. Dates keep the digits 0–9.
  - Spoken navigation: if the device has no text-to-speech voice for your language, turn-by-turn
    guidance is asked for and spoken in English instead.

==================================================================================================
6.3  Night / illumination signal…
==================================================================================================
Where:   ☰ Menu ▸ Dashboard ▸ Display ▸ Night / illumination signal…
Needs:   Free · no ECU needed · run it on the head unit, parked, with the headlight switch in reach

What it does
  A finder for support, for a head unit whose day/night "Auto" doesn't follow the headlights. It
  records every system setting the device has with the lights off, records them again with the
  lights on, and lists what changed. The head unit's night signal is usually in that list. This
  screen doesn't change any setting itself: you send the list to support.

How to use it
  1. Headlights OFF: tap "Capture A (lights off)". Wait for "Captured A: <n> keys. Now turn lights
     ON and Capture B."
  2. Headlights ON: tap "Capture B (lights on)". Wait for "Captured B: <n> keys. Now tap Show
     changes."
  3. Tap "Show changes (A → B)". The list starts "Changed keys (A → B):" with how many changed.
  4. Tap "Share the list…" and send it to support (email, a chat app, and so on).

Notes
  - "Reading…" shows while a capture runs; it takes a moment.
  - Tapping "Show changes (A → B)" before both captures: "Capture A and B first."
  - Tapping "Share the list…" before "Show changes (A → B)": "Tap Show changes first."
  - "(nothing changed — this unit probably signals night another way. Share this with support
    anyway: it tells them to look elsewhere.)"
  - Switching the headlights on can turn the screen to its night look during the test. That's
    expected, and your first capture is kept.
  - The captures are deleted when you leave the screen.

==================================================================================================
6.4  HUD & display…
==================================================================================================
Where:   ☰ Menu ▸ Dashboard ▸ Display ▸ HUD & display…   (screen title "HUD & display")
         Also: Find a setting…, then type for example "mirror", "brightness" or "windshield".
Needs:   Free for the windshield mirror, brightness and dashboard bar · DashForge Pro or DashForge
         Track on BOTH devices for the HUD link · Wi-Fi on both devices for the link

What it does
  One screen for everything about the screen itself, and for the HUD link: the head unit (connected
  to the ECU) sends its live dashboard, and the map while Navigation is open, to a second device
  over Wi-Fi. That second device, usually a phone or tablet on the dash or under the windshield, is
  the HUD. It needs no ECU connection of its own.

  In this guide's HUD sections, and in the app's HUD messages, "head unit" means the device
  connected to the ECU. It can be any Android device: the screen in your car, a phone or a
  tablet.

  The screen's sections, top to bottom:
    "Device role"                                        6.4.1
    "This device"                                        6.4.2
    "Wi-Fi link" and "Pairing" (only for a HUD role)     6.4.3
    what the HUD shows, and the double-tap               6.4.4
    "Dashboard bar"                                      6.4.5
    "VE auto-tune coaching (set on the HUD device)"      6.4.6
    "Dedicated HUD device"                               6.4.7
    "Windshield projection"                              6.4.8
    "Screen brightness"                                  6.4.9
  Outside temperature and g-force from the HUD phone:    6.4.10

Notes
  - Changes are saved straight away and take effect when you go back to the dashboard.
  - The dashboard and Navigation screens keep the screen switched on while they are open, on every
    device. There is no setting for this.

--------------------------------------------------------------------------------------------------
6.4.1  Device role
--------------------------------------------------------------------------------------------------
Where:   HUD & display… ▸ "Device role"
Needs:   "Normal": Free · "Broadcast to HUD" and "HUD client (receive)": DashForge Pro or DashForge
         Track, checked on each device by itself

What it does
  Tells DashForge what this device does.

How to use it
  1. On the head unit (the device connected to the ECU), tap "Broadcast to HUD".
  2. On the phone or tablet that will be the HUD, tap "HUD client (receive)".
  3. On Android 17 and later, allow "Nearby devices" when Android asks (see 6.4.3).
  4. Then pair the two devices (6.4.3).

Settings on this screen
  - "Normal": reads the ECU and shows the dashboard. No HUD link. This is the default.
  - "Broadcast to HUD": the same as Normal, and also sends the live data to the HUD device over
    Wi-Fi, plus the map position and route while the Navigation screen is open.
  - "HUD client (receive)": receives what the head unit sends and only displays it. It doesn't
    connect to the ECU. It shows the dashboard, or the Nav map if you open Navigation on it.

Notes
  - Each device checks its own unlock, so the HUD link needs DashForge Pro or DashForge Track on the
    head unit AND on the HUD device. Locked choices show "🔒" and are greyed; a tap opens the unlock
    screen. A device already set to HUD client never opens it and only says "🔒 HUD isn't unlocked on
    this HUD device".
  - A device whose role is set but whose HUD isn't unlocked says "🔒 The HUD isn't unlocked, so
    this device works as Normal for now."
  - The HUD device needs no ECU set-up: it learns which ECU the head unit has over the link.

--------------------------------------------------------------------------------------------------
6.4.2  This device
--------------------------------------------------------------------------------------------------
Where:   HUD & display… ▸ "This device"
Needs:   Free

What it does
  Tells DashForge whether this device is a car's own screen (a head unit) or a phone or tablet. It
  matters for the outside temperature: Google doesn't allow its weather service in a car's own
  screen, so a head unit never fetches it. A phone or tablet connected as the HUD device fetches
  it and sends it to the head unit (6.4.10).

Settings on this screen
  - "Auto (detected: Head unit)" or "Auto (detected: Phone or tablet)" (the default): the app
    decides by the device's car settings, its make, or having no motion sensor.
  - "Head unit": always treat this device as a head unit.
  - "Phone or tablet": always treat it as a phone or tablet.

Notes
  - If Auto guessed wrong, pick one of the other two.

--------------------------------------------------------------------------------------------------
6.4.3  Setting up the HUD link: Wi-Fi and pairing
--------------------------------------------------------------------------------------------------
Where:   HUD & display… ▸ "Wi-Fi link" and "Pairing" (shown once the role is "Broadcast to HUD" or
         "HUD client (receive)")
Needs:   DashForge Pro or DashForge Track on both devices · both on the same Wi-Fi network · Android
         17 and later: the "Nearby devices" permission on both · DashForge up to date on both

What it does
  Links the head unit and the HUD device. You pair them once with a code. After that they find
  each other by themselves whenever both are on the same Wi-Fi. Only a device paired with the
  head unit's code can show its data, so nothing else on the Wi-Fi can put values, routes or
  dashboards on your HUD.

How to use it
  1. Update DashForge on both devices first. A version from before pairing can't talk to one with
     it, in either direction.
  2. On the head unit: set "Broadcast to HUD" (6.4.1). Under "Pairing" it shows its code: 12
     letters and digits, like ABCD-EFGH-JKMN.
  3. On the HUD device: set "HUD client (receive)". Under "Pairing", type the head unit's code in
     the box (XXXX-XXXX-XXXX) and tap "Pair". The app says "Paired. The HUD shows the head unit's
     data as soon as it arrives." and then "Paired with the head unit whose code ends in <last 4>."
  4. Put both devices on the same Wi-Fi network. The simplest way: turn on a Wi-Fi hotspot on the
     HUD phone and join it from the head unit. Or put both on the same router, such as a travel
     router, with its "AP isolation" or "client isolation" turned off.
  5. Check "This device's Wi-Fi IP: …" on both devices. They must be on the same network. A phone
     running a hotspot shows two addresses: one of them must match the head unit's network.
  6. Go back to the dashboard on both. Until it connects to the ECU, the head unit's status line
     says "Broadcasting over Wi-Fi (:45654)". The HUD device goes from "Waiting for head unit on
     Wi-Fi (:45654)" to "HUD linked — waiting for ECU data" and then "HUD linked — live".

Settings on this screen
  - "Make a new code" (head unit): asks "Make a new pairing code?" — "Every HUD device paired
    with the current code stops showing this head unit's data until the new code is typed on it."
  - "Un-pair" (HUD device): forgets the code. The HUD then shows nothing from the head unit.
  - "Allow Nearby devices (local network)" or "Open DashForge's settings" (Android 17 and later,
    only while the permission is missing): see the notes.

Notes
  - You pair once. Both devices keep the pairing through restarts.
  - Type the code any way: capitals or not, with or without the dashes. Codes never use 0, 1, I, L
    or O. A wrong-length code: "That isn't a pairing code. It's 12 letters and digits, like
    ABCD-EFGH-JKMN."
  - Until it's paired, the HUD device shows nothing from the head unit, and its status line says
    "Not paired with a head unit: Menu ▸ Dashboard ▸ Display ▸ HUD & display". Tap the status
    line to open this screen.
  - A HUD device that has an old or mistyped code says "The head unit's data doesn't match this
    HUD's pairing code: check it in Menu ▸ Dashboard ▸ Display ▸ HUD & display". Tap it, and type
    the code the head unit shows now.
  - Android 17 and later: the link can't use Wi-Fi until you allow "Nearby devices". The app asks
    when you pick a HUD role and when the dashboard opens. If you said no, the screen and the
    status line say "Allow Nearby devices so the HUD link can use Wi-Fi". Tap the status line, or
    the button here. If Android won't ask again, the button opens DashForge's settings so you can
    allow it there. The link starts as soon as it's allowed, with no restart.
  - The link stays on your local Wi-Fi (UDP broadcast on port 45654) and is very small. It doesn't
    need the internet. While it runs, the app keeps the device's Wi-Fi out of power saving so the
    gauges don't stutter.
  - Wi-Fi tips, from testing in a car:
      Use 5 GHz Wi-Fi if both devices can. On 2.4 GHz, which the car's Bluetooth also uses, the HUD
      can freeze for 1–5 seconds every few seconds. Many phones let you pick the hotspot's band.
      On a travel router: 5 GHz, "DTIM" set to 1, client power saving off, AP / client isolation
      off.

--------------------------------------------------------------------------------------------------
6.4.4  What the HUD shows, and the double-tap
--------------------------------------------------------------------------------------------------
Where:   the dashboard on both devices; double-tap on the head unit's dashboard or Nav screen
Needs:   DashForge Pro or DashForge Track on both devices · for the map: Navigation (DashForge Pro
         or DashForge Track) on the head unit, and a map source on the HUD device · for the lap
         delta: DashForge Track on the head unit

What it does
  The HUD device shows:
  - The dashboard, with the head unit's live data: any built-in dashboard, or the head unit's
    imported dashboard when the head unit sends it with a double-tap.
  - The trip computer's figures (fuel economy, fuel left, range) as the head unit works them out.
  - Day or night, as the head unit is.
  - The Nav map: while the Navigation screen is open on the head unit, its position and route are
    sent to the HUD.
  - VE auto-tune's coaching while the head unit tunes (6.4.6).
  - The lap timer: while a lap session runs on the head unit, the lap readouts on the HUD's
    dashboard follow it. The delta to your best lap and the predicted lap need DashForge Track.

How to use it
  1. On the head unit's dashboard, double-tap an empty part of the screen (not a button).
  2. If the HUD already shows the dashboard you're on, it switches to the map, and the head unit
     shows "HUD → Nav".
  3. Otherwise, or on the next double-tap, the HUD shows the dashboard you're on, and the head
     unit shows "HUD → <dashboard name>".
  4. To send a different dashboard, swipe to it on the head unit and double-tap.
  5. On the head unit's Navigation screen, a double-tap on the map (not on a button) swaps the HUD
     between "HUD → Nav" and "HUD → Gauges".

Notes
  - The double-tap does this only on the head unit ("Broadcast to HUD"). On any other device a
    double-tap is just two taps.
  - Imported dashboards: the head unit sends a copy along with your Assign channels… choices for it.
    The HUD device keeps the last 12 it was sent. Showing them there needs the HUD unlock on the
    HUD device, not a dashboard-import unlock. A very large dashboard (over about 1 MB) isn't sent,
    and the HUD keeps showing what it had.
  - Mood figures and moving backgrounds are never drawn on a HUD device or with HUD projection on:
    moving light in your view is a distraction. The rest of the dashboard shows as normal.
  - When the head unit loses the ECU, the HUD says "Head unit has no ECU data" and doesn't freeze
    on old values.
  - The map on the HUD device draws its own map, so it needs a map source set up on that device
    (see Navigation). Without one it says "No Geoapify key — tap Source to paste one."
  - If you close Navigation on the head unit, the HUD's map keeps going on the HUD device's own
    GPS and says "○ Using this device's GPS — the head unit isn't relaying". With no GPS of its
    own it says "HUD nav client — waiting for head unit…".

--------------------------------------------------------------------------------------------------
6.4.5  Dashboard bar
--------------------------------------------------------------------------------------------------
Where:   HUD & display… ▸ "Dashboard bar" ▸ "Hide the 🧭 Navigation button (swipe down instead)"
Needs:   Free

What it does
  Removes the "🧭 Navigation" button from the dashboard's top bar to make room. Swipe down on the
  dashboard to open Navigation instead.

Notes
  - Reminder of the dashboard gestures, as the screen gives them: swipe DOWN opens Navigation; swipe
    left / right moves between your dashboard pages; double-tap (head unit only) sends the
    dashboard you're on, or Nav, to the HUD device.

--------------------------------------------------------------------------------------------------
6.4.6  VE auto-tune coaching on the HUD
--------------------------------------------------------------------------------------------------
Where:   HUD & display… ▸ "VE auto-tune coaching (set on the HUD device)" ▸ "Show VE auto-tune's
         coaching while the head unit tunes"
Needs:   DashForge Pro or DashForge Track on both devices · a VE auto-tune session on the head unit
         (see VE auto-tune)

What it does
  While a VE auto-tune session is tuning on the head unit, the HUD shows the cells around where
  the engine is running, the AFR against its target, and an arrow to the next cell that needs data,
  instead of the dashboard. You can follow the tune without looking down at the table.

How to use it
  1. On the HUD device, leave the box ticked (it's on by default).
  2. Start VE auto-tune on the head unit. The HUD switches to the coaching view by itself, and back
     to the dashboard when the session stops.

Notes
  - This setting belongs to the device showing the HUD. Untick it there to keep the dashboard.
  - A session that has been stopped but is still open (not yet burned) doesn't take over the HUD.
  - If the head unit goes quiet, the HUD goes back to its dashboard after about 5 seconds.

--------------------------------------------------------------------------------------------------
6.4.7  Dedicated HUD device (auto-start)
--------------------------------------------------------------------------------------------------
Where:   HUD & display… ▸ "Dedicated HUD device" ▸ "Auto-start as HUD on power / boot"
Needs:   DashForge Pro or DashForge Track (the start at boot happens only while the HUD is unlocked)
         · "Display over other apps" (asked for from Android 6) · a device that stays in the car on
         USB power

What it does
  For a spare phone or tablet that lives in the car only as a HUD. DashForge opens its dashboard
  when the device starts up, wakes the screen when the car powers on (USB power connected), and
  shows over the lock screen, with no taps.

How to use it
  1. On the HUD device, set "HUD client (receive)" and pair it (6.4.1, 6.4.3).
  2. Tick "Auto-start as HUD on power / boot".
  3. If "Grant "Display over other apps"" appears, tap it and allow DashForge. If that page
     doesn't open, the app says "Open Settings → Apps → DashForge → Display over other apps".
  4. Under "When it auto-boots, come up on:", pick "Dashboard (gauges)" or "Navigation (map)".
  5. In Android's Developer options, turn on "Stay awake", so the screen stays on while charging.

Notes
  - Leave this OFF on the device connected to the ECU, and on a phone you also use day to day.
  - The wake on car power works while DashForge is still running on the device. After the device
    has been fully off, DashForge starts again when it boots.
  - The head unit's double-tap also changes what the HUD comes up on next time: it comes up on
    whatever the head unit last sent it to.
  - While the device is still locked, the menu stays shut ("Unlock the device to open the menu")
    and Navigation won't take a destination ("Unlock the device to pick a destination"). The
    gauges and the map still show.
  - The battery icon (6.7) shows the HUD device's own charge.

--------------------------------------------------------------------------------------------------
6.4.8  Windshield projection
--------------------------------------------------------------------------------------------------
Where:   HUD & display… ▸ "Windshield projection" ▸ "HUD projection (mirror the gauges, max
         brightness)". Also the "HUD" button on the Navigation screen turns it on and off.
Needs:   Free · works on any device, with or without the HUD link

What it does
  Mirrors the gauges so they read the right way round when the screen lies flat and reflects in the
  windshield, and drives the screen to full brightness. The top bar and the menu stay the right way
  round, so you can still use them. The dashboard, the Nav map and the performance meter are all
  mirrored.

How to use it
  1. Tick "HUD projection (mirror the gauges, max brightness)".
  2. Pick "Horizontal", "Vertical" or "Both". "Which mirror you need depends on how the device faces
     the glass — cycle until the reflection reads the right way round."

Notes
  - Projection always uses full brightness, whatever "Screen brightness" says.
  - Mood figures and moving backgrounds aren't drawn while projection is on.
  - The battery icon flips with the gauges, so it reads at the upper right in the reflection.
  - This is a setting of each device: turn it on on the device that faces the glass.

--------------------------------------------------------------------------------------------------
6.4.9  Screen brightness
--------------------------------------------------------------------------------------------------
Where:   HUD & display… ▸ "Screen brightness"
Needs:   Free

What it does
  Sets how bright DashForge makes the screen, by day and by night.

How to use it
  1. Tap "Manual (separate day / night)".
  2. Drag "Day" and "Night (deep black)" to the levels you want. The screen previews each level
     while you drag, and it's saved when you let go.

Settings on this screen
  - "System / auto" (the default): Android's own brightness, including its auto-brightness.
  - "Manual (separate day / night)": your own levels. "Day" starts at 100%, "Night (deep black)"
    at 25%. DashForge switches between them with Day / night (6.1).

Notes
  - The levels apply to the dashboard, the menus and the map alike.
  - "On an LCD/QLED head unit, lower brightness gives visibly deeper blacks — the backlight is what
    makes "black" look grey, so dimming (especially at night) helps most. OLED screens can stay
    bright and still look black. HUD projection always uses full brightness."

--------------------------------------------------------------------------------------------------
6.4.10  Outside temperature and g-force from the HUD phone
--------------------------------------------------------------------------------------------------
Where:   automatic over the HUD link, once it's set up (6.4.3)
Needs:   DashForge Pro or DashForge Track on both devices · the HUD device set as "HUD client
         (receive)"; for the temperature, also seen as a phone or tablet (6.4.2) Temperature: a
         Google Maps Platform key with the Weather API, entered on the phone · "Outside temperature
         on the map (Google Weather)" switched on on the phone · the map's data switched on
         ("Data:On") on the phone · internet on the phone g-force: the phone's accelerometer · GPS
         speed from the head unit

What it does
  - Outside temperature: Google doesn't allow its weather service in a car's own screen, so a head
    unit never fetches the temperature itself. The HUD phone fetches it for where you are and sends
    it to the head unit, which shows it on its map. On the head unit the menu row reads "Outside
    temperature on the map (Google Weather, from your HUD phone)".
  - g-force: many head units have no accelerometer. The HUD phone measures g, learns which way the
    car faces from the head unit's GPS speed, and then sends forward and sideways g to the head unit
    about 15 times a second. A head unit with no working motion sensor of its own uses it, for
    example for the lap timer's g readings.

Notes
  - Keys stay on the device you enter them on. On a head unit the Google key box says "Google key
    (not used on a head unit — enter it on the HUD phone)".
  - Without the phone, a head unit shows no outside temperature.
  - While the phone is still learning the car's direction, the lap timer shows "g: learning the
    car's direction". Once it works, the g reading on the head unit ends in "(HUD phone)".

==================================================================================================
6.5  Screen rotation
==================================================================================================
Where:   ☰ Menu ▸ Dashboard ▸ Display ▸ Screen rotation (switch)
Needs:   Free · a device with a motion sensor to turn with

What it does
  Off (the default): every DashForge screen stays in landscape. On: every screen turns with the
  device, in both landscapes and in portrait.

How to use it
  1. Tap the switch. The screen you're on changes straight away.

Notes
  - In portrait, the dashboard's button bar moves to the bottom of the screen and the menu opens
    upward, for one-handed use.
  - On a tablet or other large screen with Android 16 or later, the menu shows: "Tablets and large
    screens always follow the device: Android 16 and later turn the screen with it whatever this
    says." Every screen works both ways round, so nothing breaks.
  - Turning with the device needs its motion sensor. A head unit fixed in the dash usually has
    none, so it simply stays as it is.

==================================================================================================
6.6  Animate mood figures
==================================================================================================
Where:   ☰ Menu ▸ Dashboard ▸ Display ▸ Animate mood figures (switch)
Needs:   Free for the switch · mood figures come on imported dashboards (dashboard import is
         DashForge Pro)

What it does
  A mood figure is a small animated picture on a dashboard that changes with the engine's state.
  On (the default): the figures play their animation. Off: each figure holds the first frame of its
  picture. It still changes picture with the engine, just without the motion. For drivers who find
  motion distracting.

How to use it
  1. Tap the switch. The figures start again from their first frame.

Notes
  - None of the built-in dashboards has a mood figure. They come with dashboards you import.
  - Mood figures are never drawn on a HUD device or with HUD projection on, whatever this says.

==================================================================================================
6.7  Battery icon
==================================================================================================
Where:   ☰ Menu ▸ Dashboard ▸ Display ▸ Battery icon (switch)
Needs:   Free · a device with a battery

What it does
  Shows a small upright battery at the top right of the dashboard. The fill shows how much charge
  is left, and a lightning bolt shows while it charges. There is no number. It's drawn in the
  dashboard's text colour and follows day / night. On by default.

How to use it
  1. Tap the switch to show or hide it. Each device has its own setting.

Notes
  - Most useful on a phone or tablet used as the HUD, which runs on its own battery when the car is
    off.
  - A head unit wired to the car usually has no battery. Nothing shows there, so you can also just
    switch it off.
  - The top bar covers the icon while the bar is showing.
  - With HUD projection on, the icon flips with the gauges.

==================================================================================================
6.8  Road speed from
==================================================================================================
Where:   ☰ Menu ▸ Dashboard ▸ Display ▸ Road speed from: <source>  (tap to change)
Needs:   Free · "GPS": a GPS fix (this device's, or the head unit's on a HUD device) · "ECU (VSS)":
         an ECU connected that sends a road speed (VSS)

What it does
  Picks where the dashboard's road speed comes from (the big speed on the Speed dashboard, for
  example). Each tap swaps between the two. Vehicle & calibration explains road speed in full.

Settings on this screen
  - "GPS" (the default): the device's GPS speed. On a HUD device, it's the head unit's GPS speed,
    sent over the HUD link.
  - "ECU (VSS)": the speed sensor the ECU reads.

Notes
  - If you pick "ECU (VSS)" but your firmware doesn't send a road speed, the dashboard quietly
    uses the GPS speed instead.
  - If the ECU's speed reads wrong, fix it with ☰ Menu ▸ Vehicle & calibration ▸ Calibrate VSS….
  - Head units often have a weak GPS; a phone's is usually better.


##### 7. TUNING #####

==================================================================================================
7.1  Before you tune
==================================================================================================
Where:   ☰ Menu ▸ Tuning ▸ (every tuning screen)
Needs:   Free to look · DashForge Plus or Pro (Tuning) to change anything · a connected ECU that
         is verified on this device

What it does
  DashForge can read every setting and table in your ECU for free. Changing them (writing to the
  ECU and burning) needs three things: the ECU connected, the ECU verified on this device, and the
  DashForge Plus or Pro unlock. Until all three are true, every tuning screen is read-only and
  says why.

How to use it
  1. Connect to the ECU.
  2. Verify it: ☰ Menu ▸ Tuning ▸ Set up & verify this ECU — <status>… (see section 2.4
     "Verifying your ECU"). It takes about a minute and needs an MSQ saved from your tuning
     software.
  3. The first time write access comes on, DashForge shows "Before you tune": "Changing your ECU's
     tune can damage your engine or make the car unsafe. You're responsible for every change you
     make. Keep a backup, change one thing at a time, and don't tune while driving on public
     roads." Tap "I understand". It can't be skipped, and it never shows again.
  4. Get DashForge Plus or Pro (☰ Menu ▸ Diagnostics & app ▸ Unlock / codes…) to write and burn.

Notes
  - Every screen opens read-only, even when you're verified and unlocked. Tap "Edit: off" to turn
    editing on ("Edit: ON"). Without DashForge Plus or Pro the button reads "🔒 Edit" and opens the
    unlock screen.
  - RAM and flash: the ECU runs from RAM. A change you make goes into RAM, works straight away,
    and is lost when the ignition is turned off. "Burn" copies it to flash so it stays.
  - Every value DashForge writes is read back from the ECU and compared. If it doesn't match you
    see a warning ending "— NOT what was written. Do not burn": in Settings "⚠ … read back as …,
    not … — NOT what was written. Do not burn; re-check.", in tables "⚠ read back …, not … — NOT
    what was written. Do not burn."
  - Every burn is checked: each burned page is read back and its CRC is compared with the ECU's
    own. Success reads "✓ Burned N pages — the ECU acknowledged the burn and its page CRC matches."
    and the toast "Burn verified ✓". If a page fails it stays marked as unburned.
  - A DashForge Plus or Pro unlock for tuning can be tied to one car. On another car writes are
    refused with "🔒 Your unlock is for a different car. To move it to this one, email support
    with this car's id (Menu ▸ Diagnostics & app ▸ Unlock / codes). Nothing written."
  - Every write re-checks the link, the verification, the unlock and that it's still the same ECU.
    A refusal always ends "nothing written" and names the reason.
  - Keep an MSQ backup from your tuning software as well.

--------------------------------------------------------------------------------------------------
7.1.1  The write-access note at the bottom of the Tuning menu
--------------------------------------------------------------------------------------------------
Where:   ☰ Menu ▸ Tuning ▸ (a grey line under "Tuning tools ▸")

What it does
  One line tells you what this ECU allows right now. You'll see one of four versions:
  - Not verified: "Read-only until this ECU is verified — Tuning ▸ Set up & verify this ECU (about
    a minute, with an MSQ saved from your tuning software). Verifying turns on editing and MSQ
    import / export."
  - Verified: "Verified for editing on this device: screens open read-only — tap Edit to change
    values, Burn to keep. Every write is read back; each burn is CRC-checked. Keep an MSQ backup."
  - Verified MS1: as above, plus "An MS1 holds one settings page in RAM, so burn your changes
    before moving to a table or setting on another page." and "each burn is checked against a
    fresh read of the flash".
  - Older firmware kept editable: "⚠ This ECU hasn't been verified on this device. Editing stays
    on because this firmware was cleared before verification existed — verify it in Tuning ▸ Set
    up & verify this ECU …". Verify it anyway when you can.

Notes
  - The note is about verification only. DashForge Plus or Pro is checked separately when you tap
    Edit.
  - rusEFI ECUs are read-only in this version, whatever the note says.
  - An ECU set up from your own INI also needs "Turn on editing" in setup after it's verified.
    Until your first Burn, writes are refused while the engine may be running: edit with it off.

--------------------------------------------------------------------------------------------------
7.1.2  Unburned changes: the reminders
--------------------------------------------------------------------------------------------------
Where:   The top of every menu level · leaving Settings or Tables & curves

What it does
  DashForge keeps track of the pages you changed in RAM and haven't burned, across every editor.

How to use it
  1. When you leave an editor with unburned changes, it asks "Leave without burning?" — "Your
     changes are live in RAM but go away at key-off unless you Burn. The dash menu keeps a burn
     reminder until then." Tap "Stay" to go back, or "Leave" to keep them in RAM for now.
  2. Until you burn, a red row sits at the top of every menu level: "⚠ N unburned pages — tap to
     burn". Tap it, then "Burn" in "Burn N pages to flash?" to burn them all at once (each page is
     CRC-checked).
  3. Turning the ignition off and on clears the reminder: the ECU has gone back to its flash.

Notes
  - ECU verification won't run while there are unburned changes: burn them or cycle the key first.
  - No burn runs while a quick tune is in RAM: "A quick tune may be in RAM — revert it (or cycle
    the key) before burning. Nothing burned." (see 7.9)
  - While VE auto-tune has a session open, VE table 1 (and the MS3 idle VE table) is held back from
    these burns; burn it from the session's Review (7.5.4).

--------------------------------------------------------------------------------------------------
7.1.3  MS1: one page in RAM
--------------------------------------------------------------------------------------------------
Needs:   DashForge Plus or Pro (Tuning) · an MS1 / MSnS-Extra ECU

What it does
  An MS1 keeps only one page of settings in RAM at a time. Writing to a second page would burn the
  first.

Notes
  - Burn (or drop) your changes on one page before you open a table or setting on another. If you
    don't, the read fails with "An MS1 keeps one page in RAM: burn (or drop) changes on another page
    before opening this one."
  - A whole tune can't be tried in RAM on an MS1: "An MS1 holds only one page in RAM, so a whole
    tune can't be tried without burning it." Use "Burn" in the Tune library instead (7.8.2).

==================================================================================================
7.2  The Tuning menu
==================================================================================================
Where:   ☰ Menu ▸ Tuning ▸
Needs:   Free · the firmware your ECU runs (or ran last time) decides what's listed

What it does
  Everything for your ECU's tune in one place. The rows depend on the firmware.

How to use it
  1. Top: the everyday tables and settings, whichever this firmware has: "VE table 1…", "Timing
     table 1…", "AFR target table 1…", "Warmup enrichment…", "Accel enrichment…", "Idle control…".
     Each opens straight into that table or settings group. Back returns to the menu.
  2. "VE auto-tune…" (7.5), where the firmware has a 16×16 VE table 1.
  3. "Cranking tables / tuner" (7.6), on MS3 and MS2/Extra.
  4. The firmware's own menus, with the same sections and names as your tuning software (on MS3,
     for example, "Fuel Settings ▸", "Ignition Settings ▸", "3D Tuning Maps ▸"). Inside, each row
     opens its settings group or table.
  5. "All settings (A–Z)…" lists every settings group. "All tables & curves…" lists every table
     and curve.
  6. "Tuning tools ▸" (7.7), then the write-access note (7.1.1).
  7. Below that: "Tune library…" (7.8), "Set up & verify this ECU — <status>…" (section 2.4),
     "Tune health probe (tables + temps)…" and "Settings probe (check vs MSQ)…" (7.10).

Notes
  - The verify row shows its status: "not set up", "N of 3 checks passed" or "✓ verified".
  - A row your tuning software would grey out on this setup is shown muted as "<name> — Off in this
    setup". Tapping it says: "Off in this setup: your tuning software greys this out because of how
    the ECU is set up (another setting turns it off). Turn that setting on first, then this opens."
  - Rows your tuning software hides on this setup aren't shown at all.
  - If the app has no menu layout for this firmware, you get "Settings…" and "Tables & curves…"
    instead of the firmware's menus and the two "All …" rows.
  - "This firmware's menu isn't available." or "Nothing in this menu can be opened here." mean the
    menu has nothing DashForge can open (for example, summaries or pin lists).
  - ☰ Menu ▸ Find a setting… also searches the firmware's menus by name.
  - Without a connection the menus still open (from the last firmware seen), but values can't be
    read.

==================================================================================================
7.3  Settings
==================================================================================================
Where:   ☰ Menu ▸ Tuning ▸ All settings (A–Z)… · a settings row in the firmware's menus ·
         "Settings…" (no menu layout, or an offline tune in the Tune library)
Needs:   Free to read · DashForge Plus or Pro (Tuning) + verified ECU to change · ECU connected
         (or an offline tune)

What it does
  Shows a settings group with the same labels as your tuning software, reads the values from the
  ECU, and (with Edit on) lets you change them.

How to use it
  1. Tap a group in the list. The screen shows "Reading <group> from the ECU…", then each setting
     with its value on the right.
  2. Tap "Edit: off" in the top bar. It turns to "Edit: ON" and the values you can change are
     highlighted.
  3. Tap a value:
     - A choice opens a list of the options the firmware allows. Tap one.
     - A number opens a box with "Allowed: <min> – <max>" (when the firmware gives limits). Type
       the value and tap "Set".
  4. The ECU is written and read back. The status line shows "<setting> → <value> (RAM). Burn to
     keep."
  5. Tap "Burn" (top bar) when you're happy. "Burn N page(s) to flash?" explains it writes every
     page you changed (here or in Tables & curves) and checks each CRC. Tap "Burn".

Notes
  - Values are shown in your units (temperatures, pressures), as set in ☰ Menu ▸ Dashboard ▸ Units….
  - A setting greyed out (faded) is one your tuning software greys out on this setup; it can't be
    changed until the setting that turns it on is on. Settings your tuning software hides aren't
    shown.
  - "(computed)" values are worked out by the ECU and can't be edited.
  - A value outside the limits is refused: "Out of range — nothing written. Allowed: …".
  - One write at a time: "Wait — the last change is still being written."
  - Some pages are never burned by the ECU. A change there shows "(RAM only — this page is never
    burned; it lasts until key-off)."
  - Help text: shown in the edit box only for an ECU set up from your own INI. The built-in
    firmwares have no help text.
  - There's no search inside Settings. Use ☰ Menu ▸ Find a setting… to find a group or table by
    name.
  - If the ECU isn't verified, there's no Edit button here.
  - Not connected: "Connect to the ECU to read values. Showing the group list only."
  - On an offline tune the title reads "Settings (offline) — …", "Burn" becomes "Save", and Save
    writes your edits to the tune file (7.8.3).
  - Leaving with unburned changes asks "Leave without burning?" (7.1.2).

==================================================================================================
7.4  Tables & curves
==================================================================================================
Where:   ☰ Menu ▸ Tuning ▸ All tables & curves… · an everyday table row · a table row in the
         firmware's menus · "Tables & curves…" (no menu layout) · "Tables…" (an offline tune)
Needs:   Free to read · DashForge Plus or Pro (Tuning) + verified ECU to change · ECU connected
         (or an offline tune)

What it does
  Shows any table as a coloured grid and any curve as a graph, straight from the ECU. It follows
  the engine live, and with Edit on you can change one cell, a block of cells, or a curve point.

How to use it
  1. Pick a table from the list. Curves are listed under "Curves (idle, warm-up, corrections)".
  2. The grid has RPM along the bottom and load up the side, with high load at the top as in your
     tuning software. Each cell is coloured by its value and shows the number. Drag with one finger
     to move around a big table.
  3. With the engine running, the cell the engine is on is highlighted, and a line above the grid
     reads "▲ <rpm> rpm · <load> · <value>". On a VE table it adds the measured AFR against the
     target and the difference in %.

Notes
  - Tables your tuning software hides on this setup aren't listed.
  - On an AFR target table, "Show AFR" / "Show λ" switches between AFR and lambda. It only changes
    the display, not the tune.
  - "Some numbers here are raw (their scale depends on another setting)." means those values aren't
    converted; the live marker is hidden then.
  - Not connected: "Connect to the ECU to read tables. Showing the list only."
  - There's no undo, no smoothing and no 3D view in this editor. To go back, use a saved tune
    (7.8) or turn the ignition off before burning.
  - A table that can't be encoded shows no Edit button ("This table isn't editable on this
    firmware.").
  - While VE auto-tune is tuning VE table 1, editing it here is refused: "VE auto-tune is tuning
    this table: stop the session (Review) before editing it here. Nothing written."

--------------------------------------------------------------------------------------------------
7.4.1  Changing cells
--------------------------------------------------------------------------------------------------
How to use it
  1. Tap "Edit: off" so it reads "Edit: ON". A tool bar appears under the grid.
  2. One cell: tap it. A box titled with the table, RPM and load opens. Type a value, tap "Set".
     The cell is written and read back ("Cell → <value> (RAM). Burn to keep.").
  3. The cell the engine is on: use the "−" and "+" on the live line above the grid. Each tap moves
     it one step. The cell stays picked for 5 seconds after a tap, so the RPM drifting doesn't move
     your edit to another cell.
  4. A block: press and hold a cell, then drag to stretch a rectangle (the grid scrolls at the
     edges). The status line shows how many cells are selected.
  5. With a block selected, use the tool bar:
     - "Step": the size of one "−" / "+" step. On a VE table it's a percent (default 1 %); on an
       AFR table 0.1; on a timing table 0.5; otherwise 1. DashForge remembers your step per table.
     - "−" / "+": move every selected cell down / up by one step.
     - "×%": "Multiply selection by %" ("102 = +2%, 98 = −2%"). Type and tap "Apply".
     - "Set": "Set selection to…" one value. Type and tap "Set".
     - "Interp": fills the block smoothly between its four corner cells.
     - "Clear": drops the selection.
  6. Changed cells are marked on the grid. Tap "Burn" to make them permanent: "Burn N changed pages
     to flash?" Tap "Burn".

Notes
  - The tool bar's "−" / "+" only work on a selection ("Select cells, or use the live +/- to tune
    the operating cell"); the live line's "−" / "+" only work on the engine's cell.
  - Cells pushed past the firmware's limits are held at the limit: "N cells held to the allowed
    range".
  - A block is written in parts. If the write stops part-way, the grid is read again and the status
    says how many cells hold the new value: check it before you burn.
  - Coming back to the table list turns Edit off again. Your changes stay in the Burn list.

--------------------------------------------------------------------------------------------------
7.4.2  Curves
--------------------------------------------------------------------------------------------------
How to use it
  1. Open a curve from the list. It shows as a graph with its points.
  2. With the engine running, a cursor shows where the engine is along the curve.
  3. Tap "Edit: off" → "Edit: ON". Tap a point to type a value, or drag a point up or down and let
     go. Each change is written and read back ("Point → <value> (RAM). Burn to keep.").
  4. Tap "Burn" to keep the changes.

Notes
  - If a write fails, a dragged point goes back to where it was.
  - "<curve> — read-only" means the curve can't be changed on this firmware.

==================================================================================================
7.5  VE auto-tune
==================================================================================================
Where:   ☰ Menu ▸ Tuning ▸ VE auto-tune… · the dash banner "● VE auto-tune … — tap to open" while a
         session runs
Needs:   DashForge Pro (VE auto-tune) to open the screen · DashForge Pro (Tuning) + verified ECU to
         write · a live ECU connection (not an offline tune) · a firmware with a 16×16 VE table 1
         (MS3, MS2/Extra, Speeduino) · a wideband O2 sensor the ECU streams, plus its AFR target,
         RPM, load and coolant · a warm engine

What it does
  Learns your fuel table while the engine runs, parked or on the move: the car doesn't have to be
  moving to start. It compares the wideband reading with the ECU's AFR target, allows for the
  sensor's delay, and moves VE table 1 cells in RAM a little at a time, within safety limits.
  Nothing is burned until you review the changes and tap "Burn". You can also tune from saved logs,
  or watch only ("dry run").

How to use it
  1. Open the screen. It reads VE table 1 and its axes ("Reading VE table 1 and its axes…"), then
     shows "Ready. Tap Start with the engine running and warm."
  2. Decide on the switches in the bottom strip (7.5.2), such as closed-loop EGO.
  3. Tap "● Start" with the engine running and warm. The first time (with writing on) you must
     read "Before your first auto-tune session" and tap "I understand — start".
  4. Hold the engine steady in the areas you want tuned: it learns whichever cells the engine is
     running in, so cells under load need the road or a dyno. The table colours show the change;
     the big readout shows the AFR against target.
  5. Tap "Pause" to stop learning without ending the session ("● Continue" to go on), or "Stop" to
     end it. Stop opens Review (7.5.4).
  6. In Review, tap "Burn" to keep the new table, or "Revert all" to put the starting table back.

Notes
  - The session keeps running if you leave the screen, so you can drive with the dash in front. The
    dash banner reads "● VE auto-tune tuning · N cells changed, unburned — tap to open".
  - Before the first write, the starting table is saved as a VE snapshot (an undo you can restore
    from VE analyze's Revert in the Log viewer). If it can't be saved, nothing starts: "Couldn't
    save an undo of the starting table — nothing started."
  - If the ECU can't be written (not verified, for example) you get "Can't write to this ECU" with
    the reason, and can tap "Dry run" instead: it watches and suggests, and writes nothing.
  - It won't start when: it's an offline tune ("VE auto-tune needs the car: it doesn't run on an
    offline tune."); the firmware has no usable table ("This firmware has no 16×16 VE table 1 the
    tuner can use."); there's no wideband data ("This firmware doesn't stream an AFR channel the
    tuner can read."); there's no target ("This firmware doesn't stream its target AFR, which the
    tuner compares against."); or a quick tune is in RAM ("A quick tune is in RAM — revert it
    first, so the session starts from your daily tune.").
  - Tunes with a second fuel table or a secondary fuel load are handled where the app can tell
    which table is fuelling; otherwise it says why and won't start.
  - The session pauses itself, with the reason, on knock, high EGT (if set), a dropped link
    ("The link dropped: nothing is written until it's back and you tap Continue."), a write that
    doesn't read back, or the change limit ("The session's change limit was reached: review before
    going on.").
  - If the app closes mid-session, the next visit asks "An auto-tune session was left open":
    "Continue", "Review" or "Revert and discard". The dash shows "An auto-tune session was left open
    — tap to review it".
  - While a session is open, loading a whole tune from the Tune library is refused. Finish it first.
  - If you're driving, watch the road. Tune with a passenger watching the screen, or use the HUD
    coaching (7.5.5).

--------------------------------------------------------------------------------------------------
7.5.1  The screen
--------------------------------------------------------------------------------------------------
What it does
  The table fills the screen; the top bar has the big AFR-against-target readout, "● Start",
  "Pause", "Stop", "Follow", "Select" and "Review ▸". The strip at the bottom has the switches and
  settings; the status line is under it (tap it for details). On a phone held upright the readout
  sits under the bar and Start / Pause / Stop are along the bottom.

How to use it
  1. Tap a cell to see its details: samples so far and how many it needs, its error, and why it
     hasn't moved yet (for example "Waiting for more samples here.").
  2. Press and hold a cell to lock it (it's never changed) or unlock it.
  3. "Follow" ("Follow ●" when on) shows a bigger patch of cells around where the engine is running.
  4. "Select" lets you lock or unlock many cells: "Tap cells", "Area (2 corners)", "Select
     dialled-in" (cells already within target), "Clear", then "Lock selected" or "Unlock". Tap
     "Done" to finish.

Notes
  - A green corner on a cell means "dialled in": the AFR is within 1 % of target there (set in
    "Safety ▸").
  - Locks stay with this car and this table until you unlock them.
  - Dashed outlines near the engine's cell mark cells that still need data.

--------------------------------------------------------------------------------------------------
7.5.2  The switches and settings strip
--------------------------------------------------------------------------------------------------
Settings on this screen
  - "Closed-loop EGO: on": tap to turn the ECU's closed-loop O2 correction off for the session
    ("Closed-loop EGO: OFF for the session ●"). Shows "off in your tune" if it's already off.
  - "Long-term trim: on" (MS3): the same for long-term trim.
  - "EGO: can't switch here ⓘ": this firmware has no "No correction" mode; the tuner allows for
    the EGO correction instead.
  - "Writing to ECU" / "Dry run (watch only)": tap to choose before you Start (stop the session to
    change it). "🔒 Writing to ECU" means DashForge Pro (Tuning) is locked.
  - "Warm-engine hold: <temp>" / "Warm hold: OFF": with the hold on, nothing is learned until the
    coolant reaches the Window's minimum (about 71 °C / 160 °F by default). Turning it off asks
    "Tune a cold engine too?" first: a cold engine teaches warm-up enrichment, not the VE table.
  - "Delay ▸": the sensor delay (how long the wideband takes to see the fuel). Pick your sensor
    position and wideband controller, engine size, distance and pipe size, or tap "Measure my
    delay ▸": parked, warm, in neutral, hold idle, 2000 and 3000 rpm as asked and blip the throttle
    each time it says "Blip now!". Then "Use measured" or "Keep my settings".
  - "Window ▸": where tuning happens: coolant range, RPM and load range, TPS range, waits after
    accel enrichment, overrun and engine start, and "Tune idle (below 1000 rpm, lowest two load
    rows)".
  - "Safety ▸": "Most a cell moves per update (%)" (default 3), "Most a cell moves in a session
    (%)" (default 15), "Most a boost / high-RPM cell leans out in a session (%)" (default 3),
    "Boost threshold (kPa)", "Pause for a review after this many cells change", "Samples a cell
    needs before it moves", "Pause above this EGT (as your ECU reports it; blank = off)", "Dialled
    in when the AFR is within (% of target)", automatic locking of dialled-in cells, and "How
    readily cells change" ("Easy (moves fastest)" to "Hard (moves slowest)").
  - "From a log ▸": tune from saved logs (7.5.3).
  - "Idle VE ▸" (MS3, when the tune uses its idle VE table): apply what was learned at idle to the
    idle VE table. It's burned or reverted together with VE table 1 in Review.

Notes
  - Switched settings are changed in RAM only and are never burned. They're put back when the
    session ends, when you leave the screen with no session running, or at the next key cycle. If a
    restore fails: "The setting switched off for auto-tune couldn't be restored: … Open VE
    auto-tune to try again (a key cycle also restores it)."
  - While a setting is switched off, no burn of its page is allowed, and the dash shows "A setting
    is switched off for VE auto-tune — tap to open and restore it".
  - Setting names in these sheets that are ECU settings use your tuning software's labels.

--------------------------------------------------------------------------------------------------
7.5.3  Tuning from saved logs
--------------------------------------------------------------------------------------------------
Needs:   The same as 7.5 (the ECU connected, so the table can be read) · datalogs that include AFR,
         the AFR target, RPM, coolant and load

How to use it
  1. Pause or stop the session first, then tap "From a log ▸".
  2. In "Tune from saved logs", tick one or more logs and tap "Analyze".
  3. A banner shows how many cells the logs suggest (shown dashed on the table).
  4. Tap "Apply to RAM" (then "Apply") to write them, "Merge into session" to add the logs'
     samples to the live session, or "Discard".

Notes
  - Nothing is written until you apply, and nothing is burned until Review.
  - "No saved logs": turn on logging while the engine runs (the dash's log button), and log the AFR
    target too.
  - "Nothing to suggest": the logs didn't have enough steady data in any cell.
  - A log that's missing a needed channel is listed with the reason (for example "no AFR target in
    it (log the target AFR to tune from a log)").

--------------------------------------------------------------------------------------------------
7.5.4  Review, burn and revert
--------------------------------------------------------------------------------------------------
How to use it
  1. Tap "Review ▸" (or "Stop"). "Review the session" lists every changed cell as "<rpm> rpm ·
     <load>: before → after (change %)". "⚠" marks a cell more than 10 % leaner than it started.
  2. Optional, when stopped or paused: "Smooth changed cells…" runs one gentle smoothing pass over
     the changed cells only (locked cells are left alone). It shows what it would do first, then
     writes to RAM.
  3. Tap "Burn", then "Burn" in "Burn the tuned table?". It restores the switched settings (EGO,
     LTT) first, then burns VE table 1 (and the idle VE table, if applied) and checks the CRC.
     "Burned and verified. Start a new session any time."
  4. Or tap "Revert all", then "Revert": the starting table goes back into RAM and the switches are
     restored. Locked cells stay locked.
  5. "Keep for later" (or "Back" while running) closes Review and keeps the session.

Notes
  - "Unlock all (N)" in Review unlocks every locked cell on this car's table.
  - A burn stops the session first.

--------------------------------------------------------------------------------------------------
7.5.5  Coaching on the HUD
--------------------------------------------------------------------------------------------------
Where:   On the HUD device: ☰ Menu ▸ Dashboard ▸ Display ▸ HUD & display… ▸ "Show VE auto-tune's
         coaching while the head unit tunes" (on by default)
Needs:   DashForge Pro or DashForge Track and a second device set up as the HUD (see 6.4)

What it does
  While a session is open on the head unit, the HUD device swaps its dashboard for a full-screen
  coaching view: the 5×5 cells around where the engine is running, "AFR / TARGET" with "ON TARGET" or
  "x% LEAN" / "x% RICH", and an arrow to the next cell that needs data ("more RPM", "less load"…).

Notes
  - It shows "PAUSED", "NOT RUNNING" or "WAITING FOR A WARM ENGINE" when it isn't learning.
  - The HUD goes back to its dashboard when the session closes.

==================================================================================================
7.6  Cranking tables / tuner
==================================================================================================
Where:   ☰ Menu ▸ Tuning ▸ Cranking tables / tuner
Needs:   Free to look · DashForge Plus or Pro (Tuning) + verified ECU to write · ECU connected ·
         MS3 or MS2/Extra only (on other firmware it opens Tables & curves instead)

What it does
  Shows the cranking tables against coolant temperature (cranking pulse, priming pulse and
  afterstart enrichment, with your tuning software's names) and lets you trim the bin for the
  engine's current coolant temperature, plus the cranking advance.

How to use it
  1. Connect, then open the screen. It reads the tables ("Read OK — table cross-checks your tuning
     software."). "↻ Re-read tables from ECU" reads them again.
  2. The row nearest the live coolant temperature is highlighted ("Live coolant: …").
  3. Under "Adjust current bin — writes to ECU", use "−" / "+" on the cranking and afterstart rows.
     "Step: ±5" cycles the step through 5, 1 and 10. If Optimize (suggest) has a suggestion for
     this bin, "→ sug" sets it.
  4. Tap "Apply to RAM". It writes, reads back and shows "✓ Verified … Live for the next crank;
     Burn to make permanent."
  5. Tap "Burn to flash", then confirm, to keep it.
  6. "Cranking advance (ignition) — writes to ECU" works the same way in 1° steps ("Apply to RAM",
     "Burn to flash").

Notes
  - Values you stage aren't sent until "Apply to RAM". "Burn to flash" with staged values writes
    and checks them first, then burns.
  - Burning with the engine running can cause a brief stumble (normal).
  - On a mismatch: "✗ MISMATCH … Do NOT burn; re-read and retry."
  - Cranking advance is held to 0–25° on this screen.

==================================================================================================
7.7  Tuning tools
==================================================================================================
Where:   ☰ Menu ▸ Tuning ▸ Tuning tools ▸
Needs:   Depends on the tool and the firmware (below)

What it does
  The specialist tools, shown only where this firmware has the settings they need:
  - "Closed-loop EGO…": MS3, MS2/Extra, Speeduino.
  - "Captured starts" and the "Auto-capture starts" switch: every firmware.
  - "Optimize (suggest)" switch: where the app finds the cranking settings (MS3, MS2/Extra,
    Speeduino, MS1).

--------------------------------------------------------------------------------------------------
7.7.1  Closed-loop EGO…
--------------------------------------------------------------------------------------------------
Needs:   Free to look · DashForge Plus or Pro (Tuning) + verified ECU to switch · ECU connected

What it does
  Turns the ECU's closed-loop O2 correction off (and back on) in one tap, so a VE-tuning log shows
  the raw table, not the correction hiding the error. The wideband stays on and AFR keeps reading.

How to use it
  1. The screen shows the sensor type and the correction mode, with your tuning software's labels.
  2. Tap "Disable correction (for tuning)". It writes RAM only: "✓ Correction OFF — log now, then
     re-enable. (RAM; Burn to persist.)"
  3. Tap "Enable correction" to put your mode back. If the app doesn't remember it, it asks
     "Enable correction as…".
  4. "Burn" makes the change permanent. Usually you leave it RAM-only while tuning.

Notes
  - Some older firmware builds have no "No correction" mode: turn EGO off in your tuning software.
  - If the sensor is disabled, it says "sensor is DISABLED; enable Wideband in your tuning software
    to read AFR".
  - VE auto-tune has its own EGO switch that is always put back (7.5.2).

--------------------------------------------------------------------------------------------------
7.7.2  Captured starts
--------------------------------------------------------------------------------------------------
Needs:   Free · ECU connected while you start the engine · a wideband for the AFR figures

What it does
  Every engine start is recorded automatically: a fast trace of the crank and catch, with a score
  (crank time, AFR range, flare, stumbles, whether it died).

How to use it
  1. Open "Captured starts". Each line reads "<when> • crank <s>s • AFR <min>–<max>" (or "did not
     catch", "DIED").
  2. Tap a start to see its graph. The legend reads "White = RPM   Green = AFR   Gray dashed = AFR
     target   Faint line = start detected   (touch graph to scrub)". "Share this capture (.csv)"
     sends it.
  3. "Compare two starts…": pick "Start A", then "Start B", to see them overlaid with the
     differences.
  4. "Optimize cranking…" opens the optimizer (7.7.4).
  5. "Delete all captures" removes them all (this also resets the optimizer's history).

Notes
  - "No starts captured yet." Connect on the dashboard, then crank the engine.
  - "AFR: sensor warming" means the wideband wasn't reading yet during that start.

--------------------------------------------------------------------------------------------------
7.7.3  Auto-capture starts
--------------------------------------------------------------------------------------------------
Where:   ☰ Menu ▸ Tuning ▸ Tuning tools ▸ Auto-capture starts: ON ● / OFF ○
Needs:   Free

What it does
  Turns automatic start capture on or off. It's on by default. While a start is being captured,
  the dash banner shows "capturing start…".

--------------------------------------------------------------------------------------------------
7.7.4  Optimize (suggest)
--------------------------------------------------------------------------------------------------
Where:   ☰ Menu ▸ Tuning ▸ Tuning tools ▸ Optimize (suggest): ON ● / OFF ○ · Captured starts ▸
         Optimize cranking…
Needs:   Free (suggestions only; it never writes) · captured starts with a few different cranking
         values

What it does
  Learns from your captured starts which cranking fuel gives the shortest crank at each coolant
  temperature, and suggests a change. It's separate from auto-tune: it only suggests.

How to use it
  1. Turn it on: "Optimize ON — showing suggestions (Auto-tune is separate)". Off by default.
  2. With the engine off, the dash banner shows advice for the current coolant bin, for example
     "Shorter starts with richer fuel — increase … at the … bin".
  3. "Optimize cranking…" shows the graph per coolant bin: "Dots = observed starts • red = fitted
     trend • amber = extrapolated best." Pick the cranking or afterstart table, then a bin.
  4. Change the value yourself in Cranking tables / tuner ("→ sug"), or on Speeduino / MS1 with
     the "Edit <curve>…" button, which opens the curve in Tables & curves.

Notes
  - Change a bin's fuel by a few % between starts to build the trend. "Need 2+ different … values
    in this bin to fit a trend."
  - Starts captured on another firmware aren't mixed in: "These starts were captured on another
    firmware than the one open now."

==================================================================================================
7.8  Tune library
==================================================================================================
Where:   ☰ Menu ▸ Tuning ▸ Tune library… · share a .mst or .msq file to DashForge from another app
Needs:   Free to save, view, share, rename, delete and back up, and to export an MSQ (verified
         ECU) · DashForge Pro (Tune import) to bring a .mst or .msq file in · DashForge Plus or
         Pro (Tuning) + verified ECU to load a tune onto the ECU · DashForge Pro (Offline tune
         editing) + verified firmware to edit a tune offline

What it does
  Keeps whole tunes as .mst files in Documents/DashForge/Tunes. You can save the ECU's tune, load
  a saved one back (seeing exactly what changes first), open one without the car, and convert to
  and from MSQ files for your tuning software.

How to use it
  1. The top of the screen: "＋ Save current tune", "⤵ Import a .mst file…", "⤵ Import an MSQ…"
     and "Set up & verify this ECU (MSQ import / export)…".
  2. Below, your saved tunes, newest first, with date and place. Tap a tune to load it (connected)
     or open it offline (not connected).
  3. Tap "⋮" next to a tune for: "Load onto ECU (diff)…" or "Open offline (view / edit)…",
     "Rename", "Delete", "Share…" and "Export as MSQ…".

Notes
  - Tune files copied into the DashForge folder from outside the app show 🔒 without DashForge Pro
    (Tune import). Tunes already in the folder when DashForge is installed, or when you give it
    its folder back (1.6), count as your own.

--------------------------------------------------------------------------------------------------
7.8.1  Saving the ECU's tune
--------------------------------------------------------------------------------------------------
Needs:   Free · ECU connected

How to use it
  1. Tap "＋ Save current tune". It reads every tune page off the ECU.
  2. Edit the name so you can tell your tunes apart (for example "daily", "track-e85"), then tap
     "Save". You see "Saved “<name>” (N pages) → <folder>".

Notes
  - "No saved tunes yet." Load a tune onto the ECU (for example with your tuning software), then
    save it here.

--------------------------------------------------------------------------------------------------
7.8.2  Loading a tune onto the ECU
--------------------------------------------------------------------------------------------------
Needs:   DashForge Plus or Pro (Tuning) · verified ECU · ECU connected · engine at idle or off
         (1200 rpm or less) · the tune saved from the same firmware

How to use it
  1. Tap the tune (or "⋮" ▸ "Load onto ECU (diff)…").
  2. DashForge reads the ECU's current tune and shows "Apply “<name>”?" with what differs: each
     changed setting as "old → new" (up to 40, then "… +N more"), and how many pages will be
     written. Only the pages that differ are written.
  3. Tap "Write to RAM" (live now, reverts on power-cycle), "Burn" (write and make permanent) or
     "Cancel".
  4. A burn backs up the ECU's current tune first ("Previous tune backed up as “backup-…”") and
     ends "Tune burned ✓" with every page CRC-checked.

Notes
  - Without DashForge Pro or verification you still see the full difference, as "This is a preview
    only — … (Nothing has been changed.)".
  - "Already loaded": the tune is identical to the ECU's.
  - "⚠ Different firmware": the tune is from other firmware and can't be loaded. Open it offline
    to look at it, or convert it with your tuning software.
  - "Engine running": loading is blocked above 1200 rpm.
  - If the backup can't be saved you're asked first ("Couldn't back up your current tune" ▸ "Burn
    anyway").
  - "Written to RAM ✓" changes revert on the next power-cycle unless you open the tune again and
    choose Burn.
  - Loading is refused while a VE auto-tune session is open or one of its switches is off.
  - On an MS1 a multi-page tune can only be burned, not tried in RAM (7.1.3).

--------------------------------------------------------------------------------------------------
7.8.3  Working offline (without the car)
--------------------------------------------------------------------------------------------------
Needs:   Free to view · DashForge Pro (Offline tune editing) and the tune's firmware verified on
         this device to edit · no live ECU link (use ☰ Menu ▸ Connection ▸ Disconnect (stay on this
         tune) if you're connected)

How to use it
  1. Not connected, tap a tune (or "⋮" ▸ "Open offline (view / edit)…"). The library shows "●
     Offline — editing “<name>”".
  2. Use "Tables…", "Settings…" or "Tune health probe…". The editors work as usual, but "Burn"
     becomes "Save": "Save N page(s) to the tune file?" writes your edits back into the .mst.
  3. Tap "Close offline tune" when done. With unsaved edits it asks "Unsaved edits" ▸ "Discard &
     close" or "Keep editing".
  4. To put the edited tune in the car: connect, open the Tune library, tap the tune and choose
     "Write to RAM" or "Burn" from the difference list (7.8.2).

Notes
  - Not verified: "view-only until this ECU is verified (Tuning ▸ Set up & verify this ECU).
    Reconnect to apply."
  - Going back to the dashboard closes the offline tune. Save your edits in the editor first.
  - A tune from a firmware the app has no definition for can't be opened: "No descriptor".

--------------------------------------------------------------------------------------------------
7.8.4  Automatic backups
--------------------------------------------------------------------------------------------------
Needs:   Free · ECU connected

What it does
  DashForge saves your tune on its own in two cases, into the same library:
  - Before every burn from the Tune library: "backup-<date>". The last 10 are kept.
  - Once a day, the first time the ECU is connected with the engine at 1300 rpm or less:
    "daily-<date>". The last 5 are kept.

Notes
  - Older automatic backups are deleted to keep those numbers. Tunes you saved or named yourself
    are never deleted.
  - Burns from Settings, Tables & curves and the tools don't make a backup: save the tune first.
  - No daily copy is taken while VE auto-tune has a session open or a setting switched off.

--------------------------------------------------------------------------------------------------
7.8.5  MSQ import and export
--------------------------------------------------------------------------------------------------
Needs:   The tune's firmware verified on this device (all three checks) · export: Free · import:
         DashForge Pro (Tune import), and the ECU connected or a tune saved from it

How to use it
  1. Import: tap "⤵ Import an MSQ…" and pick an .msq saved from your tuning software. DashForge
     lays it over the ECU's current tune (or the newest tune saved from it), shows what it
     converted and what differs, and offers "Save to library". Nothing is written to
     the ECU: load it from the library to see the difference and burn.
  2. Export: "⋮" ▸ "Export as MSQ…". "Export" writes an .msq for your tuning software into the
     Tunes folder. "Review copy" marks it "CRITIQUE ONLY — DO NOT BURN" in its tune comment, for
     sending to someone to look over.

Notes
  - Not verified: "“…” isn't verified on this device yet. MSQ import / export unlock once it passes
    all three probes" with a "Set up & verify…" button.
  - "Different project settings": the MSQ was saved with other units / options than the MSQ used
    to verify. Match the project settings in your tuning software, or verify again.
  - "MSQ is incomplete": save the whole tune from your tuning software and import that.
  - "Different firmware release": same layout, but a point release can change what a value means.
    Tap "Import" only if you're sure.
  - The review mark is a signpost, not a lock: the tuning software can still burn it.

--------------------------------------------------------------------------------------------------
7.8.6  Importing .mst files, sharing, renaming, deleting
--------------------------------------------------------------------------------------------------
Needs:   Free to share, rename and delete · DashForge Pro (Tune import) to import a .mst or add a
         shared .msq to the library

How to use it
  1. "⤵ Import a .mst file…" brings in a tune someone sent you. On modern Android the app can't see
     files it didn't create, so use this (or share the file to DashForge).
  2. Sharing an .msq to DashForge asks "What should DashForge do with this tune?": "Set up this ECU"
     or "Add to tune library".
  3. "⋮" ▸ "Share…" sends the .mst through Android's share sheet.
  4. "⋮" ▸ "Rename" changes the name; "⋮" ▸ "Delete" removes every copy in the app's folders (this
     can't be undone).

Notes
  - "That file isn't a DashForge .mst tune (no pages found)."
  - Can't find your file in the picker? "In the picker, tap ⋮ ▸ Show internal storage. Or open the
    file from your file manager and choose DashForge."

==================================================================================================
7.9  Quick-tune buttons
==================================================================================================
Where:   On an imported dashboard that has quick-tune buttons · the "● Quick tune LIVE — tap to
         revert" pill · the same row at the top of the menu
Needs:   DashForge Pro (Imported dashboards) for the dashboard · DashForge Pro (Quick-tune) to
         load a tune (a revert needs no unlock) · verified ECU · ECU connected · engine at 1500
         rpm or less (for a revert too) · at least one tune saved in the Tune library

What it does
  A button on the dash that loads a saved tune (for example a track tune) into the ECU's RAM in one
  tap, without burning it. Your daily tune stays in flash: tap the button again to go back, or turn
  the ignition off and the ECU goes back to it by itself.

How to use it
  1. Build a dashboard with quick-tune buttons in the Dash Designer (dashdesigner.appforged.cc)
     and import it (see 4.1). The dashboard places and names the button; the
     tune is picked on the device.
  2. Tap the button the first time (or press and hold it any time). In "Quick-tune: <button> —
     pick a tune", choose a tune, leave "Ask before loading (recommended)" ticked, and tap "Bind".
     "Remove" unbinds it.
  3. The buttons show with the dashboard's top bar: tap the screen to bring it up, then tap the
     button. "Load <button>": "Load tune "<name>" into RAM? Live now, reverts to your daily tune at
     key-off. Nothing is burned." Tap "Load to RAM".
  4. It writes only the pages that differ and reads them back: "Loaded to RAM (read back ✓) —
     reverts at key-off". The button shows it's live, and stays on screen while it is.
  5. To go back, tap the lit button (or the pill): "Revert to daily" ▸ "Revert". "Reverted to daily
     (RAM, read back ✓)".

Settings on this screen
  - "Ask before loading (recommended)": the confirmation before each load. Untick it for a true
    one-tap button.

Notes
  - Above 1500 rpm: "RPM is … Tune swaps are blocked above 1500 rpm — return to idle or shut off."
    A revert says "RPM is … Reverting is blocked above 1500 rpm, like a swap — return to idle or
    shut off, then tap revert again."
    If RPM can't be read, the swap is blocked too ("RPM unavailable").
  - While a quick tune is in RAM, no burn is allowed anywhere, so a race tune can't become your
    daily one by mistake. Revert (or cycle the key) first.
  - A dashboard without the button shows the pill "● Quick tune LIVE — tap to revert" so a live
    quick tune is never hidden. It also sits at the top of every menu level.
  - After the app restarts with a quick tune loaded, it can't know what's in RAM: "⚠ A quick tune
    may still be in RAM — tap". Tapping asks "A quick tune may still be in RAM": turn the ignition
    off and on, then tap "The ignition was cycled" (or "Not yet"). Swaps are held until then.
  - The device must be unlocked to load ("Unlock the device to load a quick tune"); a revert
    doesn't need that, or DashForge Pro. A revert still needs the engine at 1500 rpm or less,
    with the rpm readable. At any time, turning the ignition off and on also goes back to your
    daily tune.
  - "No tune bound — long-press the button to pick one."
  - On an MS1 a multi-page quick tune can't be loaded into RAM (7.1.3).

==================================================================================================
7.10  Tune health probe and Settings probe
==================================================================================================
Where:   ☰ Menu ▸ Tuning ▸ Tune health probe (tables + temps)… · ☰ Menu ▸ Tuning ▸ Settings probe
         (check vs MSQ)… · Tune library ▸ (offline tune) ▸ Tune health probe…
Needs:   Free · a firmware the app has a definition for

What it does
  Two checks that DashForge reads your tune correctly. They're the same checks ECU verification
  runs ("① Settings probe (vs MSQ)", "② Tune health (connected)", "③ Tune health (saved tune)"),
  but running them here doesn't verify the ECU: use Set up & verify this ECU for that (section
  2.4). Use them to look into a problem, and send the report to support.

--------------------------------------------------------------------------------------------------
7.10.1  Tune health probe
--------------------------------------------------------------------------------------------------
Needs:   ECU connected, or an offline tune open

How to use it
  1. Tap "Run". It reads every page of the tune.
  2. Result: "✓ Healthy — N tables + M settings decode, temps sane." or a count of incomplete
     tables, settings that can't be decoded, temperature flags and missing pages.
  3. "Copy" copies the report; "Share" saves it and sends it.

What it checks
  - Every table's values and both axes can be read.
  - Axis scales that depend on other settings can be worked out.
  - Every temperature reads as a sensible value (catches °C / °F mix-ups).

Notes
  - Run it on a fresh connection. A missing page means the ECU refused or cut short that page.
  - On an offline tune, RAM-only pages (long-term trim, port usage) aren't saved in a tune: that's
    expected. A missing page means the .mst didn't capture it: save the tune from the ECU again.

--------------------------------------------------------------------------------------------------
7.10.2  Settings probe (check vs MSQ)
--------------------------------------------------------------------------------------------------
Needs:   ECU connected · an .msq saved from your tuning software for this ECU

How to use it
  1. Save a fresh MSQ of your current tune in your tuning software.
  2. Tap "Load MSQ…" and pick it ("Loaded N constants from MSQ (…). Tap Run.").
  3. Tap "Run". It reads the ECU and compares every setting and table with the MSQ.
  4. "Copy" or "Share" the report.

What the results mean
  - "✓ All N constants & tables match the MSQ — decode verified against your tuning software.":
    DashForge reads this ECU the same way your tuning software does.
  - "⚠ N mismatches (x%) — this MSQ likely doesn't match the current flash.": many differences
    usually mean the tune changed since the MSQ was saved. Save a fresh MSQ and run again.
  - "N settings read differently from the MSQ — the app may be reading them wrong.": a few
    differences. Tap "Share" to send the report to support.
  - "⚠ This MSQ was made by DashForge, so it can't check the app": use one saved by your tuning
    software.


##### 8. LOGGING, ANALYSIS AND DYNO #####

==================================================================================================
8.1  Datalogging ("● Start datalog")
==================================================================================================
Where:   ☰ Menu ▸ Logging & dyno ▸ ● Start datalog   (the row reads "■ Stop datalog" while a log
         runs)
         Dashboard top bar: "● Log" starts a log and "■ Rec" stops it. In portrait the button shows
         only "●" or "■".
Needs:   Free · a connected ECU (a row is written each time live data arrives) · GPS and an
         accelerometer fill their columns but aren't required (the columns are always there,
         blank without them)

What it does
  Records the ECU's live data to a file while you drive, so you can look at it later in the Log
  viewer (8.3) or on a PC. Each log is saved twice: as an .msl file (the datalog format PC tuning
  and log-viewing software reads) and as a plain .csv file that opens in a spreadsheet.

How to use it
  1. Connect to the ECU.
  2. Tap "● Log" on the dashboard, or ☰ Menu ▸ Logging & dyno ▸ "● Start datalog". A message says
     "Logging to" and the folder. A flashing "● Logging" label shows in the lower right corner of
     every screen while the log runs.
  3. Drive. You can open other screens: the log keeps running.
  4. Tap "■ Rec" (or "■ Stop datalog"). The message "Log saved — <rows> rows, <n> with data" tells
     you how many rows the file holds and how many carried real ECU data.

What a log holds
  - The channels picked in Datalog channels… (8.2), or a default set if you haven't picked any.
  - GPS ground speed and the age of that GPS fix, in every log (blank when there's no GPS fix).
  - Position (latitude and longitude): only during a lap-timer session, or in every log when the
    lap timer's "GPS position in every datalog" is on (see 13).
  - Forward and sideways g-force, once the device has learned which way the car points (blank
    without an accelerometer).
  - The lap number, during a lap-timer session.
  - Temperatures in the unit you picked in ☰ Menu ▸ Dashboard ▸ Units…, for the whole log.

Where the files go
  Logs go to Documents/DashForge on the device's storage, named by the date and time they started.
  On Android 6 to 10 the app asks once for storage permission. If you refuse, it still logs, to
  another folder it can write to, and the "Logging to" message names that folder.

Notes
  - Logging never starts by itself, with one exception: a lap-timer session with "Datalog with the
    session" on starts and stops a log with the session (see 13).
  - Starting a log with no ECU connected gives an empty file. The Log viewer then says "Header only"
    and "This log was recorded with no live ECU feed, so there's nothing to plot."
  - If Android restarts the dashboard screen while you're logging, you see "Android restarted the
    screen — logging continues in a new file". The drive is then split across two files.
  - "✕ Exit" stops the log. The file is written as you go, so a sudden power cut (key off on a head
    unit) loses only the last few seconds (at most about ten).
  - GPS speed in the log needs location permission with "Use precise location" turned on. Without
    it the dashboard shows "GPS speed needs precise location. Turn on "Use precise location" in
    DashForge's location permission." and the GPS columns stay blank.
  - The dashboard's own GPS and g-force sensors stop while another screen is in front. The GPS
    columns then fill only if that screen (Navigation, the lap timer or the performance meter) is
    using GPS. Keep the dashboard on screen when you log a pull for the dyno.
  - g-force needs an accelerometer. Many head units have none: the g columns stay blank, unless a
    HUD phone is linked, which sends its own g-force to the head unit.
  - After a reinstall on Android 11 or later, older logs in Documents/DashForge are hidden from the
    new install. ☰ Menu ▸ Logging & dyno ▸ "Show logs & tunes from before this install…" (shown
    only then) opens Android's folder picker: pick Documents ▸ DashForge. Picking another folder
    gives "That isn't the DashForge folder. Pick Documents ▸ DashForge."

==================================================================================================
8.2  Datalog channels
==================================================================================================
Where:   ☰ Menu ▸ Logging & dyno ▸ Datalog channels…
Needs:   Free · the list shows the channels of the ECU you connected to last, so connect once first

What it does
  Chooses which of the ECU's live channels the datalog records, plus two logging options.

How to use it
  1. Open the screen. On an ECU whose firmware can't tell board models apart, the first visit asks
     "Which <model family> model?". Pick yours so the channels get the right names. You can change
     it later in ☰ Menu ▸ Connection ▸ ECU model.
  2. Tick the channels you want. Type in "Filter channels…" to find one. The line under the box
     says how many are selected: "<n> of <total> channels selected".
  3. "Defaults" ticks the default set. "All" and "None" tick or untick every channel the filter is
     showing now.
  4. Tap "Save". You see "Saved — applies to the next log".

Settings on this screen
  - "Also write a timestamped EVENT log (knock, faults, rev-limit, launch, nitrous)": on by default.
    Saved as soon as you tick it. Read the event log at ☰ Menu ▸ Diagnostics & app ▸ Event log
    (knock / faults / limiters).
  - "Standard channel names": names the log's columns CLT, TPS, AFR and so on, as other datalog
    software does, instead of coolant, throttle, afr1. Off by default. Saved as soon as you tick
    it; it applies to the next log.

Notes
  - Channels carry the names your tuning software uses. A channel that is a spare input or output
    pin shows what it's wired to, as "(Known Alias: …)".
  - Channels the firmware keeps internal, or that aren't wired out on your board, aren't listed.
  - Changes apply to the next log you start, not to one that's running.
  - You need at least one channel: "Pick at least one channel".
  - Back with changes not saved asks "Save your channel picks?": "Save", "Discard" or "Keep
    editing".
  - One list serves every ECU. On a different firmware the app logs the same channels under that
    firmware's names (for example IAT). If none of your picks exist there, it logs the default set.
  - The default set holds the dashboard channels plus knock, knock retard, status and fault bits and
    the generic sensor inputs. VE analyze (8.3.4) and the virtual dyno (8.4) need RPM, TPS, AFR, AFR
    target, fuel load, MAP, barometer, IAT and road speed: they're all in the default set, so keep
    them ticked if you trim the list.

==================================================================================================
8.3  Log viewer
==================================================================================================
Where:   ☰ Menu ▸ Logging & dyno ▸ Log viewer…
Needs:   Free to view, find events, compare and share · no ECU needed to view a log
         "VE" / "VE analyze" needs a connected ECU (8.3.4) · "Dyno" needs DashForge Pro (8.4)
         "Share as a link" needs DashForge Track and internet access

What it does
  Lists the datalogs DashForge has recorded and opens one as a scrollable, zoomable graph of as many
  channels as you like, so you can review a drive in the car without a laptop.

--------------------------------------------------------------------------------------------------
8.3.1  The log list
--------------------------------------------------------------------------------------------------
How to use it
  1. Open the Log viewer. "Reading datalogs…" shows while it looks. The newest log is at the top.
     Each row shows the date and time, how long the log runs, its size and its folder.
  2. Tap a log to open its graph (8.3.2).
  3. Long-press a log for "VE analyze", "Share", "Share as a link (DashForge Track)" or "Delete".

Settings on this screen
  - "Share": sends the .msl and its .csv through any app on the device (email, cloud storage and so
    on).
  - "Share as a link (DashForge Track)": uploads the log and makes a web link. Pick how long "The
    link lasts" ("7 days", "30 days", "90 days", "A year" or "Until I revoke it"), then "Make the
    link". Anyone with the link can open it until it ends or you revoke it.
  - "Delete": asks "Delete log?" and removes the .msl and its .csv from every one of the app's
    folders. This can't be undone.

Notes
  - With no logs you see "No datalogs found." Record one with "● Log" on the dashboard.
  - Without DashForge Track, "Share as a link" says "Share links are part of DashForge Track: link
    this device on Navigation ▸ DashForge Track."

--------------------------------------------------------------------------------------------------
8.3.2  Reading a log's graph
--------------------------------------------------------------------------------------------------
How to use it
  1. The graph opens with AFR, AFR target, RPM, MAP and coolant (whichever the log has). The title
     shows the log's date and time and its length.
  2. Touch the graph and drag: a cursor line follows your finger, and a readout lists every plotted
     channel's value at that moment ("+<n> more" when they don't all fit).
  3. Pinch with two fingers to zoom in or out on the time axis, or use "Zoom+" and "Zoom-". "Reset"
     shows the whole log again.
  4. The bar under the graph plays the log like a video: "|◀" (to the start), "◀ 5s", "▶ Play" /
     "❚❚ Pause", "5s ▶", "▶|" (to the end). The "1x" button changes the playback speed: 1x, 2x, 4x,
     8x. The graph scrolls to keep the cursor in view.
  5. Back returns to the log list.

Settings on this screen (the buttons along the top; on a narrow screen the strip scrolls sideways)
  - "AFR vs target": plots AFR, AFR target, RPM and MAP. AFR and its target share a fixed 8 to 20
    scale so you can see one against the other; the target is the dashed line.
  - "Events": finds moments of interest (8.3.3).
  - "Channels": opens "Channels to plot". Tick the ones you want, then tap "Plot".
  - "VE": VE analysis from this log (8.3.4).
  - "Compare": lays a second log over this one (8.3.3).
  - "Dyno": plots a power curve from a pull in this log (8.4). Shows 🔒 and is dimmed until DashForge
    Pro is unlocked.
  - "Reset": zooms back out to the whole log.
  - "Share": shares this log (as in 8.3.1).

Notes
  - Each channel scales itself to its own range over the whole log, so traces stay steady as you
    scroll.
  - Where data is missing (a dropped link, a logging gap), the trace has a gap rather than a made-up
    line.
  - Road speed shows in the speed unit picked in Units. The file keeps it in the ECU's own unit
    (a Speeduino can send km/h); the viewer converts it.

--------------------------------------------------------------------------------------------------
8.3.3  Events and comparing two logs
--------------------------------------------------------------------------------------------------
How to use it
  1. Tap "Events". "Find events" offers:
     - "WOT pulls (throttle)": every stretch with the throttle at 70 % or more.
     - "AFR error (rich/lean)": every stretch where AFR is 1.0 or more away from its target.
     - "Channel high / low…": pick a channel ("Spike channel"), then "Highs (top of range)" or "Lows
       (bottom of range)". Highs are the top fifth of that channel's range in this log; lows are
       the bottom fifth.
  2. The events show as faint bands on the graph and in a numbered list with their start, end and
     peak value. Tap one to zoom to it with the cursor on its peak. "Show all" zooms back out.
  3. To compare, tap "Compare" and pick a second log from "Overlay a second log". Its traces show
     faded over the first, both lined up at their start, on the same scales. The title
     reads "A <first log> vs B <second log> (B faded)", and the cursor readout lists both.
  4. To remove it, tap "Compare" again and choose "✕  Remove overlay".

Notes
  - Very short events (under about half a second) are skipped, and events less than a second apart
    are joined into one.
  - Messages when a log can't be searched: "No TPS channel in this log", "No WOT pulls — TPS peaked
    at <n>%", "Log has no AFR + target channels", "No AFR excursions ≥ 1.0 — mixture stayed on
    target", "<channel> is flat — nothing to find".
  - "No other logs to compare" means there's only one log.

--------------------------------------------------------------------------------------------------
8.3.4  VE analyze (VE suggestions from a log)
--------------------------------------------------------------------------------------------------
Where:   Log viewer ▸ long-press a log ▸ "VE analyze", or the "VE" button on a log's graph
Needs:   Free to analyze and see the suggestions · a connected ECU (it reads your VE table) · a
         firmware with a 16×16 VE table 1 (MS3, MS2/Extra, Speeduino) · a log with wideband AFR and
         AFR target "Apply", "Revert" and "Burn" write to the ECU: DashForge Pro, and a verified ECU
         (Tuning ▸ Set up & verify this ECU)

What it does
  Replays a datalog against your VE table 1 and suggests a new value for each cell, from how far
  the measured AFR was from its target in that cell. The suggestions show as a coloured map of the
  table. Nothing changes on the ECU until you apply them.

How to use it
  1. Record a log of steady driving across the rpm and load range, with the wideband working.
     Closed-loop EGO correction is best turned off while you log (Tuning ▸ Tuning tools ▸
     Closed-loop EGO…), so the log shows the VE table's own fuelling.
  2. Connect to the ECU and open VE analyze on that log. It shows "Reading VE table + axes from
     ECU…", then the map.
  3. The line under the map says how many cells got a suggestion, how many samples were used or
     skipped, and the limits used. Tap a cell to see its current VE, the suggested VE, the change
     and the number of samples.
  4. "Settings" opens "Analysis settings": the largest change per cell ("Max change: 5%" to "Max
     change: 20%", 10 % to start) and the fewest samples a cell needs ("Min samples/cell: 8", 12
     or 20; 12 to start).
  5. "Exclude" turns on "Protect mode: tap cells to exclude from suggestions". Tap the cells you
     tune by hand; they keep their value. Tap "Exclude" again to stop.
  6. Check the suggestions against your tuning software, then tap "Apply". It asks "Apply <n> VE
     changes?", writes the whole VE table 1 to the ECU's RAM (live straight away) and reads it back.
     "✓ Verified — VE table is live in RAM. Burn to make permanent." confirms it.
  7. Drive and check. Tap "Burn" ("Burn VE table to flash?") to make it permanent, or "Revert" to
     put back an earlier table.

Settings on this screen
  - "Revert": opens "Restore a VE snapshot". A snapshot of the table is saved each time you Apply;
    restoring one writes it back to RAM and verifies it. Burn to make it permanent.

Notes
  - Samples taken during acceleration enrichment, fast throttle movement, at very low rpm, or
    with the AFR reading at the sensor's limit are skipped, so the suggestions
    reflect steady running.
  - It works out the fuel's stoich from the log when the log has both AFR and lambda, so E85 and
    methanol logs are judged correctly.
  - "⚠ Closed-loop EGO correction is ON — this log may reflect the controller, not the raw VE."
    means the suggestions may be too small: turn EGO off, log again, analyze again.
  - "Not connected — connect to the ECU to read the VE table." The analysis needs the live table.
  - "VE analyze needs a 16×16 VE table 1 — this firmware's definition doesn't have one it can
    read." shows on MS1 and on any firmware without such a table.
  - If a write reads back wrong you see "✗ Mismatch on <n> bytes — do NOT burn; re-read and
    retry." Don't burn: reopen the screen and try again.
  - "Burn" works only after a verified Apply: "Apply and verify first".

==================================================================================================
8.4  Virtual dyno
==================================================================================================
Where:   ☰ Menu ▸ Logging & dyno ▸ Virtual dyno…   (the saved runs)
         Log viewer ▸ a log's graph ▸ "Dyno"   (plot a pull from that log)
Needs:   DashForge Pro · a datalog (or a live capture, 8.5) with RPM and a wide-open-throttle pull
         in one gear · road speed from the ECU's VSS or from GPS · any firmware that logs RPM "Load
         this tune" also needs a connected, verified ECU

What it does
  Works out a power and torque curve from a full-throttle pull, using the car's acceleration, its
  weight and its drag (from the Vehicle profile, 10.1). It keeps your runs so you can lay them over
  each other and see what a tune change did. It's a comparison tool, not a certified dyno number.

--------------------------------------------------------------------------------------------------
8.4.1  Doing a pull
--------------------------------------------------------------------------------------------------
How to use it
  1. Set up the Vehicle profile (10.1) first, at least the mass. Until you save it, the result shows
     "⚠ DEFAULT" after the mass.
  2. Start a datalog (8.1), or arm Live dyno capture (8.5).
  3. On a flat, straight, safe and legal road, in one gear, go to full throttle from low rpm and
     hold it to near redline. Keep the dashboard on screen so the log gets GPS speed.
  4. Stop the log.

--------------------------------------------------------------------------------------------------
8.4.2  Plotting a pull ("Dyno — plot a pull")
--------------------------------------------------------------------------------------------------
How to use it
  1. Open it from a log's graph ("Dyno"), or from ☰ Menu ▸ Logging & dyno ▸ Virtual dyno… ▸ "New
     run" ("New run from which log?"). "Pick log" on the screen chooses another log.
  2. The app finds the best pull in the log by itself and draws its power and torque curves.
  3. Read the line under the chart: peak power and torque with their rpm, the average throttle,
     where the speed came from, the rpm range of the pull, and the air density, mass and drag used.
  4. Tap "Save run", give it a name, and tap "Save". It goes to the Virtual dyno list ("Saved to
     Virtual dyno ▸ overlay").

Settings on this screen
  - "Units": hp and lb·ft, or kW and N·m.
  - "Wheel/Crank": power at the wheels, or estimated at the crank (wheel power divided by the
    driveline efficiency in the Vehicle profile). Wheel power to start.
  - "Corr": weather correction. Each tap moves to the next: raw (none), SAE, DIN ("Correction:
    SAE"). It needs barometer and IAT in the log; without them it says "uncorrected — no usable
    baro/IAT in this log".
  - "Vehicle": opens the Vehicle profile (10.1). Saving it redraws the curve.
  - "Gating": "Dyno pull gating" sets what counts as a valid pull. "Start ≤ % of redline" (60 to
    start), "End ≥ % of redline" (90), "Gear tolerance (% ratio spread)" (8) and "Redline RPM (0 =
    auto)" (0 uses the highest rpm in the log).
  - In the "Save run" box, "Also snapshot the current tune (enables reload)" saves the ECU's tune
    with the run, so you can load it back later. It's ticked when the log was recorded on this
    connection; for an older log it reads "Also snapshot the ECU's current tune (it may differ from
    the tune that made this log)". It needs the ECU connected.

Notes
  - Warnings on the result line: "⚠ PART-THROTTLE" (the average throttle was under 80 %: do a
    wide-open pull), "⚠ PARTIAL range" (the pull didn't cover the gating range), "⚠ GEAR CHANGE in
    pull", "⚠ <n> spun samples dropped" (wheelspin: those samples are left out). "full-range ✓" and
    "single gear ✓" mean the pull is good.
  - Speed: the ECU's VSS is used when the log has it, checked and scaled against GPS
    ("VSS×1.0→GPS"). With no VSS the app uses RPM × a gear ratio it learns from GPS during a pull
    ("RPM×ratio"), and remembers that ratio for logs with no GPS. "GPS slip-checked" means GPS
    confirmed the tyres weren't spinning; "no GPS — slip unmeasured" means it couldn't check.
  - Slopes aren't allowed for: a hill changes the number. Use a flat road, or do the same pull in
    both directions.
  - "No clean pull found in this log — need a sustained rising-RPM sweep." Try a longer, harder
    pull, or change "Gating".
  - "No speed source in this pull. The log has no ECU VSS and no GPS, and no gear ratio is known
    yet." Drive one steady stretch with a GPS fix so the app can learn the ratio, then try again.
  - Saved runs are kept inside the app's own storage on this device. Uninstalling the app removes
    them.

--------------------------------------------------------------------------------------------------
8.4.3  Saved runs and overlays ("Virtual dyno")
--------------------------------------------------------------------------------------------------
How to use it
  1. Open ☰ Menu ▸ Logging & dyno ▸ Virtual dyno…. Saved runs are listed under the chart, each with
     its peak power and torque.
  2. Tick the runs to lay over each other on the chart. The line above the list says how many are
     shown, which run is the baseline, and whether the runs are wheel or crank power.
  3. Tap a run's name for its menu: "Load this tune", "Set as baseline", "Rename", "Delete".
  4. "Share" saves the chart with the ticked runs as a picture and opens the share menu. Tick at
     least one run first ("Tick at least one run to share.").

Settings on this screen
  - "New run": plot a pull from a log (8.4.2).
  - "Torque: on" / "Torque: off": shows or hides the torque curves.
  - "hp / lb·ft" / "kW / N·m": the units.
  - "Set as baseline": the baseline is marked ★; every other run shows its power difference from
    it, for example "(+6 hp)". The first run you save becomes the baseline.
  - "Load this tune": shown only for a run with a tune attached ("tune ✓") while a verified ECU is
    connected. It asks "Load this tune?", backs up your current tune first, then writes and burns
    every tune page and checks each one ("All <n> pages written, burned and CRC-verified.").

Notes
  - "⚠ mixed throttle (dimmed) — not directly comparable": some ticked runs weren't full-throttle.
  - "Load this tune" is refused across firmwares ("Wrong firmware for this tune"), with no live rpm
    reading ("Couldn't read the RPM"), and above 1200 rpm ("Engine running"). Have the engine off or
    idling.
  - "no-GPS" after a run means it had no GPS to check for wheelspin.
  - Until DashForge Pro is unlocked, "Virtual dyno…" and "Live dyno capture" show 🔒 and are greyed.
    Tapping one opens the unlock screen.

==================================================================================================
8.5  Live dyno capture
==================================================================================================
Where:   ☰ Menu ▸ Logging & dyno ▸ Live dyno capture   (a switch: "Live dyno capture: ON ●" /
         "Live dyno capture: OFF ○")
Needs:   DashForge Pro · a connected ECU sending RPM (and TPS) · road speed from the ECU's VSS or
         from GPS

What it does
  Watches the live data while you drive and turns every full-throttle pull into a saved dyno run by
  itself. You don't need to start a datalog.

How to use it
  1. Turn the switch on. You see "Live dyno armed — do a WOT pull in one gear; it captures
     automatically."
  2. Do a pull: full throttle in one gear, from above 1500 rpm up towards redline.
  3. When you lift (throttle under 50 %) or the rpm drops, the pull is scored and saved: "Dyno
     captured: <power> @ <rpm> — saved".
  4. Once you're back near idle, the app attaches the ECU's tune to the run ("Dyno: tune snapshot
     attached"), so you can load it back later.
  5. See the run in ☰ Menu ▸ Logging & dyno ▸ Virtual dyno… (8.4.3). Its name starts with "live".

Notes
  - A pull counts only at 80 % throttle or more. A pull shorter than about 1.5 seconds or 1200 rpm
    is ignored: "Dyno: pull too short — ignored".
  - "Dyno: captured a pull but no speed source (VSS/GPS) — ignored": there was no road speed. Keep
    the dashboard on screen (its GPS stops while another screen is in front), or use an ECU VSS.
  - The tune is attached only if nothing was written to the ECU since the pull and you return to
    idle within about two minutes.
  - The switch turns itself off when the app closes, and if DashForge Pro lapses.
  - The vehicle profile (10.1) sets the mass and drag, as for a pull from a log.

==================================================================================================
8.6  Performance meter
==================================================================================================
Where:   ☰ Menu ▸ Logging & dyno ▸ Performance meter…
Needs:   DashForge Pro (Performance meter) · this device's own GPS, with location permission and
         "Use precise location" · an accelerometer for g-force (optional) · no ECU needed

What it does
  Times acceleration and braking from this device's GPS speed, and shows live g-force on a friction
  circle from its accelerometer.

  It times:
    Standing starts: 0–30 mph, 0–60 mph, 0–100 km/h, 60 ft, 1/8 mile, 1/4 mile, 400 m, 1000 m
                     (the distance ones also show the trap speed)
    Roll-ons:        60–130 mph, 100–200 km/h
    Braking:         60–0 mph (the stopping distance)

How to use it
  1. Mount the device solidly, fixed to the car. g-force is only as steady as the mount.
  2. Open the meter and wait for GPS. The status line shows your speed, the state ("armed (launch
     to start)", "● RUN" or "rolling") and the GPS rate and accuracy, for example "GPS 1.0 Hz  ±4m".
  3. Standing runs start by themselves when you pull away from a stop. Roll-ons and braking time
     themselves as you pass through the speeds.
  4. Results show under "STANDING", "ROLL-ON" and "BRAKING", each with your best time. "Session
     history" lists your runs, newest first, with the peak g-forces.

Settings on this screen
  - "Reset run": clears the current results.
  - "Reset peaks": clears the live peak g-force ("Peak g reset").
  - "Set forward": tells the meter which way is forward. Hold a firm straight-line pull, then tap
    it. It also finds forward by itself from your first hard launch. Until it knows, it shows only
    the combined "horizontal g".
  - "Units: mph" / "Units: km/h": the units for speeds and distances (the same choice as in
    ☰ Menu ▸ Dashboard ▸ Units…).
  - "Clear bests": deletes every saved best time ("Clear best times?"). This can't be undone.
  - "Clear session": clears this session's run history; your best times stay.
  - "Level (hold still)": only on a device without a gravity sensor. Keep the device still while it
    levels.

Notes
  - With no accelerometer (common on head units) you see "No usable accelerometer on this device.
    Times still work from GPS; live g-forces are unavailable here." The times still work.
  - The line at the top says which g-force sensors it found, from "g-source: fused (linear-accel +
    gravity) — best" down to "g-source: none — no accelerometer. GPS times only.".
  - Without precise location you see "The performance meter needs precise location. Turn on "Use
    precise location" in DashForge's location permission." The GPS line shows "GPS off
    (permission?)", or "no GPS provider" on a device with no GPS.
  - Phone GPS updates about once a second. The meter works out the moment each speed was crossed
    between fixes, but a faster GPS gives better times. A gap in GPS of more than 2 seconds cancels
    the run.
  - It uses this device's own GPS, not the ECU's road speed and not an external Bluetooth GPS.
  - Turning the screen round, or moving the device in its mount, makes it find forward again.
  - Best times are kept until you clear them. The session history lasts until the app closes.
  - When windshield HUD projection is on, the whole meter is mirrored like the dashboard.
  - Until DashForge Pro is unlocked, the menu row shows "🔒 Performance meter…" and is greyed.
    Tapping it opens the unlock screen.


##### 9. TRIP / FUEL COMPUTER #####

==================================================================================================
9.1  Trip / fuel computer
==================================================================================================
Where:   ☰ Menu ▸ Trip / fuel computer…
Needs:   Free · a connected ECU (trips count only while live data arrives) · GPS with precise
         location for distance and economy · fuel used, economy and range need an ECU that sends
         fuel flow (MS3 does; MS2/Extra, MS1 and Speeduino don't)

What it does
  A trip computer like a car's own. It shows instant economy in large figures, and for the chosen
  trip the average economy, fuel used, distance, range and trip time. It also keeps a fuel level
  that the dashboard's fuel gauges can show.

How to use it
  1. Open "Settings" ("Fuel settings") and enter "Tank size". Range and fuel level need it.
  2. Drive with the ECU connected. Both trips count all the time.
  3. Tap "Trip A" or "Trip B" to pick which one is shown, reset and used for range.
  4. "Reset trip" asks "Reset trip A?" and sets that trip's distance, time and fuel back to zero.
  5. At the pump, after filling to full, tap "Filled up". Type how much you added (optional) and tap
     "Save". The tank is marked full ("Tank marked full").
  6. After a partial fill, or to match your car's fuel gauge, tap "Set level", type the percentage
     (or tap "Full", 75%, 50% or 25%) and tap "Set".

Settings on this screen
  - "Average": average economy for the shown trip.
  - "Fuel used", "Distance", "Range", "Trip time": for the shown trip (trip time as hours:minutes).
  - "Tank size": in litres or gallons, as picked in Units.
  - "Calibration factor (actual ÷ computed)": scales the fuel figure if fill-ups don't match. Leave
    it at 1 unless they don't. "Filled up" with the amount added sets it for you: "Calibrated: <x>
    gal added vs <y> computed. Cal <old> -> <new>".

Notes
  - No injector setup is needed. Fuel flow comes straight from the ECU's fuel-flow channel (MS3
    works it out from its own injector settings).
  - On an ECU with no fuel-flow channel you see "This ECU doesn't send fuel flow, so fuel used,
    economy and range stay blank. Distance (from GPS) and trip time still count while the ECU is
    connected."
  - "(Waiting for ECU fuel-flow data…)" shows until the first fuel-flow reading arrives.
  - Distance always comes from GPS, not the ECU's VSS, whatever "Road speed from" is set to. With
    no GPS fix, distance doesn't grow and economy stays blank. On a HUD phone the figures come from
    the head unit.
  - The automatic calibration works only on a fill to full, when the fill before it was also to
    full ("Filled up", not "Set level"), and after more than about 2 gallons (7.5 L) have been used.
  - "Set level" needs the tank size: "Set tank size first".
  - Range is worked out from the shown trip's average economy and never goes up between fills;
    "Filled up" or "Set level" lets it jump back up.
  - Economy, volume and distance each follow their own row in ☰ Menu ▸ Dashboard ▸ Units….
  - Nothing counts with no ECU connected, and trip time counts only while live data arrives.


##### 10. VEHICLE AND CALIBRATION #####

==================================================================================================
10.1  Vehicle profile
==================================================================================================
Where:   ☰ Menu ▸ Vehicle & calibration ▸ Vehicle profile…
         Virtual dyno ▸ "Dyno — plot a pull" ▸ "Vehicle"
Needs:   Free · no ECU needed

What it does
  Holds your car's physical details for the virtual dyno (8.4, 8.5) and the coast-down calibration
  (10.2).

How to use it
  1. Fill in the fields (metric units).
  2. Tap "Save".

Settings on this screen
  - "Mass incl. driver (kg)": the car with you in it. This matters most for the dyno's power figure.
    1150 to start.
  - "Tire rolling diameter (m)": 0.58 to start.
  - "Drag area CdA (m²)": aerodynamic drag (drag coefficient × frontal area). 0.62 to start.
  - "Rolling resistance Crr": tyre rolling resistance. 0.013 to start.
  - "Driveline efficiency (0–1)": the share of crank power that reaches the wheels. Used for the
    dyno's crank figure. 0.85 to start.
  - "Auto CdA/Crr from a coast-down log…": measures CdA and Crr from a log (10.2) and fills them in.
    Opened from the dyno it reads "Auto CdA/Crr from coast-down (this log)" and uses the log on
    screen. Review the values, then "Save".

Notes
  - A value outside a sensible range is reset to its starting value when you save. Mass must be 300
    to 5000 kg, tyre diameter 0.3 to 1.2 m, CdA 0.2 to 3.0, Crr 0.003 to 0.05 and efficiency 0.5 to
    1.0.
  - The dyno doesn't need your gear ratios: it learns the rpm-to-road-speed ratio from GPS during a
    pull and remembers it.
  - The performance meter, the trip computer and gear detection don't use this profile.
  - Wheel or crank power and the weather correction are set on the dyno screen (8.4.2) and kept
    with the profile.

==================================================================================================
10.2  Coast-down calibration
==================================================================================================
Where:   ☰ Menu ▸ Vehicle & calibration ▸ Coast-down calibration…
         Vehicle profile ▸ "Auto CdA/Crr from a coast-down log…"
Needs:   Free · a datalog with a clutch-in coast and road speed (the ECU's VSS or GPS) · no ECU
         needed to run it

What it does
  Measures your car's aerodynamic drag (CdA) and rolling resistance (Crr) from a coast in a log.
  With the clutch in, only drag and rolling resistance slow the car, so the way it slows gives both
  numbers. Measured values make the dyno's power figure more accurate than the starting guesses.

How to use it
  1. Enter your mass in the Vehicle profile (10.1) first: the result depends on it.
  2. Start a datalog (8.1). On a flat, straight road with no wind, get above about 30 km/h (20 mph),
     put the clutch in (or select neutral), take your foot off the throttle and let the car roll
     down by at least 20 km/h (12 mph), the longer the better. Then stop the log.
  3. Open Coast-down calibration and pick the log ("Log with a clutch-in coast").
  4. It shows the result, for example "Coast-down: CdA 0.61, Crr 0.012 (140 points, 95→40 km/h)",
     and what's in your profile now.
  5. Tap "Apply to vehicle profile" ("Vehicle profile updated"), or "Cancel".

Notes
  - It uses the longest clean coast it finds: throttle closed (under 5 %), speed falling the whole
    time, for at least 2 seconds.
  - Messages when it can't fit: "no speed channel (VSS or GPS) in this log", "no clean coast-down
    found (need throttle closed, speed falling ≥5 m/s)", "coast too short/noisy to fit",
    "ill-conditioned fit", and "fit out of range … — try a longer, flatter coast".
  - It uses the barometer and IAT in the log for the air density, when the log has them.
  - "No logs yet — record a drive with a clutch-in coast first."

==================================================================================================
10.3  Calibrate TPS
==================================================================================================
Where:   ☰ Menu ▸ Vehicle & calibration ▸ Calibrate TPS…
Needs:   DashForge Pro · a connected, verified ECU (Tuning ▸ Set up & verify this ECU) · MS3,
         MS2/Extra or Speeduino (any firmware whose definition has the TPS calibration settings)

What it does
  Sets the throttle position sensor's closed and wide-open points in the ECU, so TPS reads 0 % with
  your foot off and 100 % with the pedal on the floor.

How to use it
  1. Engine off, key on, ECU connected. The screen shows the live raw sensor reading and TPS %, and
     the ECU's current closed and wide-open points.
  2. Take your foot completely off the pedal, then tap "Set CLOSED (foot off pedal)".
  3. Press the pedal to the floor and hold it, then tap "Set WIDE-OPEN (pedal to floor)".
  4. Each Set writes to the ECU's RAM and reads it back: "✓ closed set to ADC <n>. Live now; Burn to
     make permanent."
  5. Tap "Burn" ("Burn TPS calibration?") to make it permanent.

Notes
  - Without DashForge Pro, the row shows 🔒 and is greyed; a tap opens the unlock screen.
  - On a firmware without TPS calibration (MS1, for example) the row reads "Calibrate TPS… — not on
    this firmware" and is greyed. Tapping it says "This firmware has no TPS calibration this app
    knows — calibrate TPS in your tuning software."
  - If wide-open reads no higher than closed, it warns "That usually means the pedal isn't actually
    at the floor, or the sensor wiring is reversed. Set anyway?". Check before you tap "Set anyway".
  - "Burn" is refused until wide-open is above closed: "Wide-open must be above closed before
    burning".
  - "✗ Mismatch — sent <n> but ECU read <m>. Do NOT burn; retry." means the write didn't take.
  - Before verification, writes are refused with "Read-only until this ECU is verified (Tuning ▸ Set
    up & verify this ECU) — nothing written." Without DashForge Pro: "🔒 Tuning isn't unlocked on
    this device — nothing written."
  - Cross-check the result in your tuning software.

==================================================================================================
10.4  Calibrate VSS
==================================================================================================
Where:   ☰ Menu ▸ Vehicle & calibration ▸ Calibrate VSS…
Needs:   Free · a connected ECU that sends road speed (VSS): MS3, Speeduino, or a firmware set up
         from your own definition file that has one; not MS2/Extra (as shipped with the app) or
         MS1 · this device's GPS with precise location for "Match to GPS"

What it does
  Corrects the ECU's road speed (VSS) inside the app, so the app shows true speed without changing
  the pulses-per-mile in your tuning software. It's an app setting only: nothing is written to the
  ECU.

How to use it
  1. Connect, then drive at a steady speed with a good GPS signal. The screen shows the VSS speed
     with the current multiplier, and the GPS speed.
  2. Tap "Match to GPS (drive a steady speed)". It shows "Matched: VSS <x> → GPS <y> gives ×<n>. Tap
     Save to keep."
  3. Tap "Save" ("VSS calibration saved").

Settings on this screen
  - "Enter multiplier…": type the multiplier yourself ("VSS multiplier ×").
  - "Reset to 1.0": back to the ECU's own speed.

Notes
  - Once saved, the multiplier applies everywhere the app shows the ECU's road speed. A value you
    try but don't save is dropped when you leave the screen.
  - "Need the car moving so VSS reads (raw VSS ≈ 0)": drive first.
  - "Need a fresh GPS speed above ~14 km/h" (9 mph): wait for a GPS fix and go faster. If the GPS
    line keeps saying "GPS: waiting for a fix…", check the location permission ("Use precise
    location").
  - "Match out of range — check VSS/GPS": the two speeds are too far apart to be the same thing.
  - On an ECU with no road speed the row reads "Calibrate VSS… — no VSS on this ECU" and is greyed.
    Tapping it says "This firmware doesn't stream a road speed (VSS) the app can read — calibrate
    VSS in your tuning software."
  - The virtual dyno checks VSS against GPS on every pull by itself. This calibration mainly fixes
    the gauges and the logs, and lets the dyno use VSS when there's no GPS.

==================================================================================================
10.5  Gear detection
==================================================================================================
Where:   ☰ Menu ▸ Vehicle & calibration ▸ Gear detection…
Needs:   Free · a connected ECU (live RPM) · road speed: the ECU's VSS when it reads, else this
         device's GPS

What it does
  Gets the dashboard's GEAR display working. MS3 and Speeduino work out the gear in the firmware,
  and the dashboard always shows that when it reports a gear. This screen checks the firmware's
  gear setup and says what's missing. For an ECU with no gear of its own (MS2/Extra, or gear
  detection not set up), it can learn your gears and show an estimate instead.

How to use it
  1. Connect. The banner at the top says whether this ECU reports gear:
     - "✓ This ECU reports gear (currently <n>)": nothing more to do.
     - "This ECU's gear channel reads 0 (N)": the firmware's gear detection isn't set up. Set it up
       in your tuning software, or use the estimate below.
     - "No gear channel on this ECU": use the estimate below.
  2. The "FIRMWARE GEAR DETECTION" section reads your tune and lists what's set and what's missing,
     with the fix in your tuning software.
  3. To use the estimate, set "Number of gears:" with "−" and "+" (1 to 8; 5 to start).
  4. For each gear, drive steadily in that gear and tap its "Capture". The row then shows the rpm
     that gear gives at 100 km/h (or 60 mph).
  5. Tick "Display-only gear estimate (when the ECU reports no gear: MS2, or gear detection off)".

Settings on this screen
  - "Capture": saves this gear's rpm-to-speed ratio from the live readings.
  - "Edit": type the rpm for this gear at 100 km/h (or 60 mph) yourself.
  - "Clear": removes this gear's capture ("Clear gear <n>?").

Notes
  - Nothing is written to the ECU. The captures also give the values to enter in your tuning
    software, so the firmware can work out the gear itself.
  - "Drive steadily in gear <n> first (need live RPM + road speed)": the car must be moving with a
    road speed (VSS or GPS) and RPM.
  - A gear the ECU reports always wins over the estimate.
  - The estimate is used only by the dashboard's GEAR display.
  - Without VSS, the estimate needs a GPS fix while you drive.

==================================================================================================
10.6  Output tests (inj / coil / idle)
==================================================================================================
Where:   ☰ Menu ▸ Vehicle & calibration ▸ Output tests (inj / coil / idle)…
Needs:   DashForge Pro · a live ECU connection (not an offline tune) · a verified ECU (Tuning ▸ Set
         up & verify this ECU) · engine off · MS3 or MS2/Extra (the firmware must have output-test
         settings; MS1 and Speeduino don't)

WARNING
  These tests drive real hardware. Firing an injector puts fuel in a cylinder; firing a coil makes a
  spark. Know what each output is wired to before you start.

What it does
  The same actuator tests your tuning software has: fire an injector or a coil, run the fuel pump,
  drive a spare PWM output, or command the idle valve or electronic throttle. It writes the
  firmware's own test settings to the ECU's RAM. Nothing is ever burned.

How to use it
  1. Engine off, key on, ECU connected. The banner shows the RPM and the state: "ARMED (engine off)"
     when tests can run, "LOCKED" when they can't, plus "● test running" while one is on.
  2. Each section ("Injector test", "Ignition coil test", "Fuel pump", "PWM output test", "Idle
     valve test", "Throttle (ETC) test") appears only when your firmware has it. The buttons and
     fields carry the names your tuning software shows.
  3. Tap a field to set a value, or a mode button to start a test. Each write is read back to check
     it ("<field> set.").
  4. Tap the red "■ STOP ALL" in the top bar to stop every firing output ("All tests stopped.").

Notes
  - Safety interlocks:
    - The engine must be stopped (a fresh RPM reading of about zero).
    - If the engine starts during a test, every output stops: "Engine started — outputs stopped for
      safety."
    - Leaving the screen stops every firing output.
    - "■ STOP ALL" is always available, and reports success only once the ECU confirms it.
  - The idle valve holds the position you commanded until you cycle the key. "■ STOP ALL" and
    leaving the screen stop the firing outputs and close the throttle test, but don't re-home the
    idle valve.
  - "⚠ STOP may have failed — an output may still be live. Retry, or cut power." Tap "■ STOP ALL"
    again, or turn the key off.
  - "Output tests locked" with "Output tests write to the ECU, so they need write access. Verify
    this ECU in Tuning ▸ Set up & verify this ECU (about a minute, any engine state)." Verify it
    first.
  - With the engine running, the tests stay locked: stop the engine first.
  - Without DashForge Pro, a test is refused with "🔒 Tuning isn't unlocked on this device —
    nothing written." Without it, the menu row shows 🔒 and is greyed; a tap opens the unlock
    screen.
  - "Not connected. Output tests need a live ECU link." / "Output tests need a live ECU connection
    (not an offline tune)."
  - "This firmware's descriptor exposes no output-test constants." means your firmware has no
    output tests the app can drive.
  - "Allowed: <low> – <high> — nothing written": the value is outside the firmware's own limits.
  - A value marked "shown by the ECU — set the interval instead" can't be set; change the field it
    is worked out from.

==================================================================================================
10.7  Road speed from: ECU (VSS) / GPS
==================================================================================================
Where:   ☰ Menu ▸ Dashboard ▸ Display ▸ "Road speed from: GPS  (tap to change)"
Needs:   Free · "GPS" needs this device's GPS (or a linked HUD device's) · "ECU (VSS)" needs an ECU
         that sends road speed

What it does
  Picks where the big road-speed number on the "Speed" dashboard comes from. Each tap switches
  between "GPS" (the setting to start) and "ECU (VSS)".

Notes
  - "ECU (VSS)" uses the ECU's speed (with your VSS calibration, 10.4). When the ECU sends no speed
    it falls back to GPS.
  - When the ECU's VSS reads 0 (stopped, or no VSS), the dashboard's gear estimate (10.5) also uses
    this speed.
  - These keep their own sources, whatever this is set to:
    - Trip / fuel computer (9.1): distance always from GPS.
    - Performance meter (8.6): always this device's own GPS.
    - Virtual dyno (8.4, 8.5): the ECU's VSS when the log has it, checked against GPS; otherwise
      RPM × a gear ratio learned from GPS.
    - Coast-down (10.2): the ECU's VSS when the log has it, otherwise GPS.
    - Calibrate VSS (10.4): shows both side by side.
    - Gear detection (10.5): the ECU's VSS when the car is moving, otherwise GPS.
  - Dashboards can also show "GPS Speed" and the ECU's "Speed (VSS)" as separate channels (☰ Menu
    ▸ Dashboard ▸ Assign channels…); those don't follow this choice either.


##### 11. CONNECTION MENU #####

==================================================================================================
11.1  Connect…
==================================================================================================
Where:   ☰ Menu ▸ Connection ▸ Connect…  (the same as "Connect" on the top bar)
Needs:   Free · USB host (OTG) or Bluetooth.

What it does
  Opens the "Connect to ECU" list and turns auto-reconnect back on if you'd paused it.

How to use it
  1. Tap "Connect…".
  2. Tap a USB device or a paired Bluetooth adapter. It's saved for next time.

Notes
  - An empty list says "Plug in the ECU (USB) or pair its adapter (Bluetooth) first."
  - On Android 12+ without "Nearby devices" the list shows "Bluetooth: allow Nearby devices to
    list your paired adapters". Tap it to allow.
  - See 2.3 for what happens after you pick.

==================================================================================================
11.2  Set up a new ECU…
==================================================================================================
Where:   ☰ Menu ▸ Connection ▸ Set up a new ECU…
Needs:   Free · the ECU powered (key on; the screen connects by itself) · your INI (unknown
         firmware only) and an MSQ.

What it does
  Opens "Set up this ECU" at "① Connect". See 2.2.

==================================================================================================
11.3  Disconnect (stay on this tune)
==================================================================================================
Where:   ☰ Menu ▸ Connection ▸ Disconnect (stay on this tune). Only shown while connected. The top
         bar's "Disconnect" does the same.
Needs:   Free · a connected ECU.

What it does
  Drops the link to the ECU without turning the engine off, so you can open a saved tune offline
  or run a probe. Auto-reconnect stays paused.

How to use it
  1. Tap "Disconnect (stay on this tune)".
  2. To link again, tap "Connect" / "Connect…", or re-plug the saved USB cable.

Notes
  - The status line says "Disconnected — auto-reconnect paused. Tap Connect… to reconnect."

==================================================================================================
11.4  Detect firmware…
==================================================================================================
Where:   ☰ Menu ▸ Connection ▸ Detect firmware…
Needs:   Free · a connected ECU (or one this device has linked to before).

What it does
  Shows "Detect firmware": what your ECU reports, its release, whether the app knows it ("✓ Built
  into the app" or "✓ Set up from your INI"), how many settings, tables and live channels the
  definition has, and whether it's verified on this device.

How to use it
  1. Tap "Detect firmware…".
  2. If the ECU isn't set up or verified, tap "Set it up" to open the setup screen. Otherwise tap
     "OK".

Notes
  - Not connected: it describes "the last ECU this device linked to".
  - "Connected, but the ECU didn't report its firmware…" is almost always the link: a Bluetooth
    baud that doesn't match (115200, or 9600 for an MS1), a loose cable, or another app holding
    the port.
  - Unknown firmware: "The app doesn't know this firmware yet. The gauges and logging use the
    built-in <family> profile for now. Set it up from your INI and MSQ for full support."

==================================================================================================
11.5  ECU type (Auto / Always MS1)
==================================================================================================
Where:   ☰ Menu ▸ Connection ▸ "ECU type: …  (tap to change)" (under the "Advanced" heading)
Needs:   Free.

What it does
  Chooses how the app first talks to the ECU. Each tap switches between the two:
  - "Auto (finds an MS1 by itself)": the default. MS3/MS2/Speeduino connect normally. After three
    failed tries on one adapter the app tries it once as an MS1.
  - "Always MS1 (MegaSquirt-I, 9600 baud)": always connect as an MS1.

Notes
  - Always MS1: "USB connects at 9600 baud; set a Bluetooth adapter to 9600 too."
  - If you're connected, reconnect for the change to apply.
  - Leave it on Auto unless an MS1 isn't found by itself.

==================================================================================================
11.6  ECU model
==================================================================================================
Where:   ☰ Menu ▸ Connection ▸ "ECU model: <model>" (or "ECU model: tap to choose"), under the
         "Advanced" heading.
         Only for MS3 and MS2 families.
Needs:   Free.

What it does
  The firmware signature can't tell hardware models apart, so you pick yours. It sets the right
  names for the ECU's channels and pins.
  - MS3: "MS3 / MS3X" or "MS3-Pro (Gold/EVO/Ultimate)".
  - MS2: "MS2", "MicroSquirt", "MicroSquirt-module" or "MSPNP2".

How to use it
  1. Tap the row. "Which <family> model?" opens.
  2. Tap your model.

Notes
  - The question also pops up once, the first time you open Warning banners, Notifications or
    Datalog channels. Dismissing it there keeps the first model ("Use <model>").

==================================================================================================
11.7  Confirm before exit while connected
==================================================================================================
Where:   ☰ Menu ▸ Connection ▸ Confirm before exit while connected (switch, under "Advanced")
Needs:   Free.

What it does
  When on (the default), leaving the app with Back or "✕ Exit" while connected asks "Leave
  DashForge?" first, so a stray tap can't drop the ECU mid-drive.

Notes
  - The question also warns when a quick tune is live in RAM, or auto-tune changes aren't burned.
    Tap "Stay" or "Leave".


##### 12. NAVIGATION #####

==================================================================================================
12.1  Navigation (map)
==================================================================================================
Where:   ☰ Menu ▸ Navigation ▸ Navigation (map)…
         Or tap "🧭 Navigation" on the dashboard's top bar, or swipe DOWN on the dashboard.
Needs:   DashForge Pro or DashForge Track · no ECU needed · GPS with precise location · internet (a
         saved map works without it) · a map source: your own Geoapify key, or DashForge Track

What it does
  A moving map that follows your car, in your gauge colours, with address search, routing and
  spoken turn-by-turn directions. Before the map can load, DashForge needs to know where to get
  it from: your own free Geoapify key, or DashForge Track (no key needed).

How to use it
  1. Open the map. The first time, the "Map source" box opens by itself (you can open it again
     any time with "Source").
  2. Pick one:
     - "DashForge Track: maps with no key of your own (enter your code)": opens the DashForge
       Track screen, where you link this device with your code (see 14.2). Once linked, the line
       reads "DashForge Track: maps with no key of your own (linked)" and tapping it switches the
       map to DashForge Track.
     - "My own Geoapify key": opens "Map keys". Paste your key in "Geoapify API key" and tap
       "Save". The message "Key saved" confirms it.
     - "Outside temperature key (Google)": only the key for the outside temperature (see 12.6).
       The map source stays as it was.
  3. Drive. The map follows the car. Tap the map to bring back the buttons; they hide again
     after a few seconds.
  4. To go back to the gauges: tap the "‹" tab on the left edge, swipe right starting from the
     left third of the screen, or press Back.

Getting a Geoapify key
  1. On a computer or phone browser, go to geoapify.com and create a free account.
  2. Create a project. Geoapify shows the project's API key.
  3. Copy the key and paste it in DashForge (Navigation ▸ "Source" ▸ "My own Geoapify key").
  The key is used for the map, address search, road names and routes. It stays on this device.
  Geoapify's free plan has a daily allowance; heavy use may need one of their paid plans.

Settings on this screen
  - "Source": the "Map source" box (above).
  - Long-press "Map": "Vector tile URL", the address the vector map looks is loaded from. Only
    change it if the map is blank in a vector look: "Template with {z}/{x}/{y} and {key}. Get the
    exact one from your Geoapify style's data.json ("tiles" field) if the map is blank in Vector
    mode." On DashForge Track this address is set for you ("The vector tile address is set by
    DashForge Track").

Notes
  - GPS: navigation uses this device's own GPS. Turn on Location in Android. Until a fix comes
    in, the map says "Waiting for GPS…". A head unit whose GPS is slow to lock can take a while
    to get there.
  - Permission: DashForge needs the location permission with "Use precise location" on. If it's
    missing the map says "Location permission needed — open the dashboard once to grant it.";
    if only approximate location was allowed it says "Navigation needs precise location — turn on
    "Use precise location" in DashForge's location permission."; with Location switched off it
    says "GPS provider off — enable location for navigation."
  - An external Bluetooth GPS receiver (13.1.5) is used by the lap timer, not by navigation.
  - Internet: the map tiles, search, routes and (for the four raster looks) the road name need
    a data connection. Tiles the map has already shown are kept on the device (up to about
    300 MB per raster look and 200 MB for the vector looks, oldest dropped first) and show
    again with no signal. A place the map has never shown stays blank offline: "No data
    connection. The map is kept for the places it has shown with data, and it hasn't shown this
    one yet."
  - Not unlocked: tapping "🧭 Navigation" opens the unlock screen. A swipe down only shows a
    short message ("🔒 Navigation — unlock it in Menu ▸ Diagnostics & app ▸ Unlock / codes").
  - On a device set up as the HUD client (HUD & display), opening the map needs the HUD unlock
    instead, and the map follows the head unit (see 12.5).
  - You can hide the "🧭 Navigation" button and use the swipe instead: ☰ Menu ▸ Dashboard ▸
    Display ▸ HUD & display… ▸ "Hide the 🧭 Navigation button (swipe down instead)".
  - The map credits (OpenStreetMap, Geoapify, and Google when the temperature shows) sit in the
    bottom-right corner. They're required by the map and weather services.

==================================================================================================
12.2  The map screen's buttons
==================================================================================================
Where:   On the map (12.1). Tap the map to show the button row; it hides after a few seconds.
Needs:   DashForge Pro or DashForge Track

What it does
  The row along the top of the map holds every map control. The bottom of the map shows a
  box with the road you're on, your compass heading (while moving), your speed, the outside
  temperature (12.6) and fuel economy (when the ECU sends fuel flow).

Settings on this screen
  - "HUD": turns windshield projection on and off: the map (not the buttons) is mirrored and
    the screen goes to full brightness. It's the same switch as "HUD projection (mirror the
    gauges, max brightness)" in ☰ Menu ▸ Dashboard ▸ Display ▸ HUD & display…, where you also
    pick which way to mirror.
  - "Trail:On" / "Trail:Off": draws a breadcrumb line of where you've just driven. Off at first.
  - "Data:On" / "Data:Off": "Data:Off" stops map downloads and shows only the map already saved
    on the device. Rerouting, raster road names and the outside temperature stop too; a search
    you start yourself with "Go" still uses the connection. Places with no saved map show "Data
    is off. Tap Data:Off to load the map."
  - "Head-on" / "North-up": "Head-on" turns the map so your direction of travel points up;
    "North-up" keeps north at the top (the starting setting).
  - "Go": opens "Navigate" to search for a destination (12.3). While a route is running, the
    button reads "Nav".
  - "Map": switches to the next map look. A message shows its name, for example "Map: Toner
    (bold)". Long-press it for the vector tile address (12.1).
    Raster looks: "Toner (bold)", "Toner grey", "Positron", "Dark". The road name for these is
    looked up online.
    Vector looks: "Vector: roads only", "Vector bold", "Vector light". DashForge draws the roads
    and its own street labels, and reads the road name from the map itself (no extra lookup).
    On DashForge Track only the three vector looks are offered; a raster look chosen earlier
    shows as "Vector bold".
  - "Source": the "Map source" box (12.1).
  - "✕" (Close navigation): leaves the map. With a route running, the dashboard comes forward
    and guidance carries on behind it.
  - "⌖ Recenter": appears at the top right after you drag the map away from the car. Tap it to
    follow the car again.

How to use it
  1. Drag to look around; pinch to zoom. The zoom level is remembered.
  2. Long-press the info box at the bottom to switch the outside temperature between °F and °C
     ("Temp in °F" / "Temp in °C"). The same choice is in ☰ Menu ▸ Dashboard ▸ Units… under
     Navigation ("Outside temperature"), along with "Nav speed", "Nav MPG box" and "Nav
     distances".

Notes
  - The map, its buttons and the turn banner use your dashboard colours, and switch with day /
    night like the gauges.
  - On a head unit set to "Broadcast to HUD", a double-tap on the map switches what the HUD
    device shows between the map and the gauges ("HUD → Nav" / "HUD → Gauges").

==================================================================================================
12.3  Navigate (search and routing)
==================================================================================================
Where:   On the map ▸ "Go" (or "Nav" while navigating)
Needs:   DashForge Pro or DashForge Track · a map source (12.1) · internet · a GPS fix

What it does
  Finds an address or place and plans a driving route there from where you are, with a turn
  banner on the map and spoken directions. It also keeps a Home address and your recent
  destinations.

How to use it
  1. Tap "Go". The "Navigate" panel opens with the keyboard.
  2. Type in "Address or place". After three letters, suggestions near you appear on the right.
     Tap one to start the route.
  3. Or type the whole address and tap "Go →" (or the keyboard's search key). The app says
     "Finding "<address>"…", then "Routing…", then "Navigating to <place>".
  4. To save Home: type the address and tap "Set home" ("Setting home…", then "Home set:
     <place>"). From then on the panel starts with "🏠  Home — <place>": one tap routes there.
  5. Your recent destinations are listed under Home when the field is empty.
  6. To stop: open the panel and tap "End nav" (top right). "✕" closes the panel without
     changing anything.

Notes
  - Off route: if the car stays more than about 50 m off the route for several GPS fixes, the
    app says "Off route — rerouting…" and plans a new route from where you are. This needs the
    data connection ("Data:On") and a working map source.
  - Arrival: within about 25 m of the destination, after the arrival prompt, navigation ends
    by itself: "Arrived at <place> — navigation ended".
  - Restart or key-off: the route in progress is saved. Opening the map again within 2 hours
    asks "Resume navigation?" / "Continue to <place>?" with "Resume" or "No". After 2 hours the
    saved route is dropped.
  - A route keeps guiding while you use the dashboard or other DashForge screens. If the whole
    app goes to the background (another app, the home screen, a locked phone), guidance pauses
    and picks up again, from where the car is then, when DashForge comes back.
  - An active route keeps guiding without a data connection; only a reroute or a new search
    needs one.
  - With the phone locked, the panel won't open: "Unlock the device to pick a destination".
  - On the HUD device the panel won't open while the head unit is sending its map: "Pick the
    destination on the head unit — this screen follows its route."
  - Turn directions come in the app's language when the map service has it.
  - Routes are for driving only.

==================================================================================================
12.4  Voice guidance
==================================================================================================
Where:   On the map ▸ "Go" ▸ the "Navigate" panel
Needs:   DashForge Pro or DashForge Track · a text-to-speech voice installed on the device

What it does
  Speaks each turn: a heads-up about 2 miles (3 km) before, again about 800 ft (250 m) before,
  and at the turn, then "You have arrived". The radio is turned down or muted while a prompt
  plays.

Settings on this screen
  - "Voice guidance" (tick box): spoken directions on or off. On at first; turning it on says
    "Voice guidance on".
  - "Voice…": lists the voices installed on the device. Tap one to hear a sample and use it.
    A voice marked "(needs data)" needs an internet connection to speak. "Install more…" opens
    Android's text-to-speech settings. "Done" closes the list.
  - "Mute radio" (tick box): turns the Media volume to zero while a prompt plays, then puts it
    back (never for more than 15 seconds). On at first. It only works when the voice plays on
    "Alarm" or "Notification" (next setting), not on "Media".
  - The channel button ("Alarm", "Media" or "Notification"): which sound channel the voice
    uses. Tap to cycle; each tap plays a sample. "Alarm" is the starting choice, so the voice
    can still be heard with the radio muted. Pick the one your device plays clearly.
  - "Prompt ducking: Normal (music resumes after a prompt)" / "Prompt ducking: Strong (radio
    lower; music apps stay paused)": how the radio makes room for a prompt. Try "Strong" if the
    radio isn't turned down enough during prompts.

Notes
  - Text-to-speech: Android needs a speech engine and a voice. With none, the app says "No
    speech engine on this device — install one … for voice guidance", or "No voice data —
    install/enable a text-to-speech voice in Android settings". Add one in Android Settings →
    System → Languages & input → Text-to-speech, then reopen the map.
  - If there's no voice for the app's language, guidance is spoken in English: "No <language>
    voice on this device: guidance is in English. Add one in Android's text-to-speech settings,
    then reopen the map."
  - Distances are spoken in the unit set in ☰ Menu ▸ Dashboard ▸ Units… ▸ "Nav distances".
  - Only the head unit speaks. A HUD device never repeats the prompts.

==================================================================================================
12.5  Guidance on the dashboard and on the HUD
==================================================================================================
Where:   Automatic while a route is running
Needs:   DashForge Pro or DashForge Track · map and next-turn elements in imported dashboards:
         DashForge Pro or DashForge Track · the HUD device: DashForge Pro or DashForge Track on both
         devices, and the same Wi-Fi

What it does
  A running route isn't tied to the map screen. It carries on behind the dashboard and the
  app's other screens, keeps speaking, and shows on the dashboard and on a HUD device.

How to use it
  1. Start a route on the map (12.3), then go back to the gauges ("‹", swipe right, Back or
     "✕"). Guidance keeps going.
  2. Imported dashboards can include a live map and a next-turn element (made in the Dash
     Designer). The map element uses the same map source, look, zoom and orientation as the
     map screen and draws the route; the next-turn element shows the arrow, distance and street
     of the next turn, and stays empty when you're not navigating.
  3. HUD device: set the head unit to "Broadcast to HUD" and the second phone or tablet to "HUD
     client (receive)" (☰ Menu ▸ Dashboard ▸ Display ▸ HUD & display…), and pair them. Open
     Navigation on the HUD device, or double-tap the head unit's dashboard or map to switch the
     HUD between the map and the gauges. The HUD device then shows the head unit's map,
     position, route and turn banner, in the head unit's look and colours.

Notes
  - Built-in dashboards have no map or next-turn element; these come with imported dashboards.
  - A dashboard map element shows "🔒 Map isn't unlocked" without the Dashboard maps unlock,
    "Waiting for GPS…" before a fix, and "Map needs a Geoapify key or DashForge Track
    (Navigation ▸ Source)" with no map source. On the HUD device it shows "Map: head unit
    only".
  - The HUD device can't pick destinations: the head unit routes, the HUD follows.
  - If the head unit stops sending (you closed its map with no route running, or the Wi-Fi
    dropped), the HUD's map carries on from its own GPS: "○ Using this device's GPS — the head
    unit isn't relaying". Before anything arrives it shows "HUD nav client — waiting for head
    unit…".
  - The HUD link needs the "Nearby devices" (local network) permission on Android versions
    that ask for it: "Allow Nearby devices so the HUD link can use Wi-Fi". Tap the message to
    allow it.

==================================================================================================
12.6  Outside temperature on the map
==================================================================================================
Where:   ☰ Menu ▸ Navigation ▸ Outside temperature on the map (Google Weather) (switch)
         On a head unit the row reads "Outside temperature on the map (Google Weather, from your
         HUD phone)".
         The key: on the map ▸ "Source" ▸ "Outside temperature key (Google)"
Needs:   DashForge Pro or DashForge Track · a Google Maps Platform key with the Weather API ·
         internet · a phone or tablet (a head unit gets it from a HUD phone, which needs DashForge
         Pro or DashForge Track on both devices, 6.4.10)

What it does
  Adds the outside temperature, from Google Weather for your position, to the info box at the
  bottom of the map. It's checked every 10 minutes, or after you've moved 5 km.

How to use it
  1. Get a Google Maps Platform key from Google and turn on the Weather API for it.
  2. On a phone or tablet: open the map ▸ "Source" ▸ "Outside temperature key (Google)", paste
     the key in "Google Maps Platform key (outside temperature; optional)", tap "Save".
  3. Make sure the switch ☰ Menu ▸ Navigation ▸ Outside temperature on the map is on (it's on
     at first) and "Data:On" is set on the map.
  4. Long-press the info box to switch °F / °C (or ☰ Menu ▸ Dashboard ▸ Units… ▸ "Outside
     temperature").

Notes
  - Head units: Google doesn't allow its weather service on a car's own screen, so a head unit
    never fetches the temperature itself. Set up a phone as the HUD device (☰ Menu ▸ Dashboard
    ▸ Display ▸ HUD & display… ▸ "HUD client (receive)") and enter the Google key on the phone.
    The phone fetches the temperature for its own position and sends it to the head unit. On a
    head unit the key field says "Google key (not used on a head unit — enter it on the HUD
    phone)".
  - Whether this device counts as a head unit is set in HUD & display ▸ "This device": "Auto",
    "Head unit" or "Phone or tablet". Change it if Auto guessed wrong.
  - With no key, or the switch off, nothing is sent to Google and no temperature shows.
  - Keys stay on the device you enter them on.
  - "Weather: Google" appears in the map credits while the temperature shows.


##### 13. LAP TIMER #####

==================================================================================================
13.1  Lap timer
==================================================================================================
Where:   ☰ Menu ▸ Navigation ▸ Lap timer…
         Starting and ending a session can also be done with "⏱ Laps" on the dashboard (13.1.3).
Needs:   DashForge Pro (Lap timer) or DashForge Track · GPS with precise location · ECU only for the
         datalog and ECU figures · accelerometer for g · DashForge Track for the delta, predicted
         lap, HUD delta, per-lap g and ECU figures and the shared track list (with DashForge
         Pro alone you get lap and sector times without these)

What it does
  Times laps and sectors from GPS. You drop a start / finish line where you are as you drive
  over it; after that, every crossing in the same direction ends one lap and starts the next.
  It shows the running lap, last and best lap, the gap to your best lap at the same point
  ("delta") and a predicted lap time, saves every lap as it finishes, and finds a track you've
  timed before by itself when you're within 3 km of its line.

What's on the screen
  - The top line: the track, the GPS ("GPS 1 Hz ±5 m", "GPS (external) 10 Hz", or "GPS:
    waiting") and the g-force reading ("g +0.12 long +0.30 lat", "g: learning the car's
    direction" or "g: no sensor").
  - A coloured panel that says what the timer is waiting for, for example "No track here yet",
    "Ready: <track>", "⏳ <track>: start / finish line marked, awaiting the 1st lap" or
    "⏱ <track>: lap 3 running".
  - The running lap time (big), the delta (green when ahead, red when behind), "Predicted
    <time>", and a line "Lap 3   Last 1:32.41   Best 1:31.88".
  - "THIS SESSION": every finished lap, newest first, the best one in green.

--------------------------------------------------------------------------------------------------
13.1.1  Setting the start / finish line
--------------------------------------------------------------------------------------------------
How to use it
  1. Mount the device firmly and open the lap timer. Wait until the top line shows a GPS rate
     instead of "GPS: waiting".
  2. Drive over your start / finish spot and tap "Start / finish here" as you cross it. The
     line is laid square to your direction of travel, about 30 m wide.
  3. The session starts at once, and lap 1 with it: "Start / finish line set on <track>: lap 1
     started". The new track is named "Track <date and time>"; rename it in "Tracks…" (13.2).
  4. Each time you cross the line in the same direction, a lap ends and the next begins.

Notes
  - You must be moving (above roughly 11 km/h / 7 mph) when you tap. Otherwise: "Drive over
    the line's spot and tap as you cross it: the line is laid square to your direction of
    travel."
  - A line only counts in the direction you were driving when you dropped it. Crossing it the
    other way, or passing beside its ends, doesn't count; the app says "Passed <n> m from the
    start line without crossing it: the wrong way, or past its ends".
  - Moving the start / finish line on a track clears that track's best lap (old laps aren't
    comparable): "Start / finish moved: <track>'s best lap starts again from the next
    session."
  - Dropping a line more than 2 km from the selected track makes a new track.
  - To move a line, end the session first: "End the session to change the track's lines."

--------------------------------------------------------------------------------------------------
13.1.2  Sectors and stages
--------------------------------------------------------------------------------------------------
How to use it
  1. Sector lines: drive the lap and tap "Add sector here" at each split point ("Sector line 2
     added"). This works during a session, so lap 1 is a good time to lay them. A track has
     up to 8 sector lines. Sector times appear under each lap.
  2. A stage (point to point, such as a hill climb): after the start line, drive to the end and
     tap "Finish here (stage)". The track becomes a stage: "Finish line set: <track> is now a
     stage (start to finish)". Its runs are timed start to finish.
  3. To remove the sectors: "Tracks…" ▸ the track ▸ "Clear its sector lines".

Notes
  - Set the start / finish line first, or the app says "Set the start / finish line first."
  - Moving a stage's finish line clears the track's best time.

--------------------------------------------------------------------------------------------------
13.1.3  Starting and ending a session
--------------------------------------------------------------------------------------------------
How to use it
  1. On a track you've already set up, tap "Start session". The app picks the saved track
     nearest you (within 3 km) and says "Track: <name>" if it changed. Lap 1 starts when you
     next cross the start / finish line ("Session started: cross the start line").
  2. If no saved track is near and this device is linked to DashForge Track, it looks in the
     shared track list first ("Looking for tracks near here…"). If there's still none: "No
     track here" — drop a line with "Start / finish here" instead.
  3. To end: tap "End session" and confirm "End the session?" with "End". "Its laps are saved
     (Sessions…)."
  4. From the dashboard: tap "Start / end button on the dashboard: off" on the lap timer to turn
     it on. The dashboard's top bar then has "⏱ Laps" (just "⏱" in portrait). Tap it to start a
     session on the track here, and "⏹ Laps" to end it ("End the lap session?" ▸ "End").

Notes
  - A session keeps timing whichever DashForge screen is in front: the dashboard, the map,
    settings. The lap timer screen keeps the screen on while it's open.
  - The dashboard button needs the start / finish line already set: "No track here: drop its
    start / finish line in the Lap timer first (☰ ▸ Lap timer)."
  - A session ends by itself after 20 minutes with no line crossed, or 10 km from the track:
    "Session ended by itself".
  - If the GPS drops out for more than 5 seconds mid-lap, that lap isn't timed: "GPS lost: lap
    dropped".
  - Banners on the screen announce each lap ("Lap 3  1:32.41  best"), and "(track record)" for
    the best lap ever on that track.

--------------------------------------------------------------------------------------------------
13.1.4  Datalog with the session · GPS position in every datalog
--------------------------------------------------------------------------------------------------
Settings on this screen
  - "Datalog with the session: on (every channel, played back with each lap)" / "...: off":
    starts a datalog with each session (if one isn't running) and keeps each lap's rows, so
    "Laps on the map" (13.4) can play every channel back. It takes effect from the next
    session: "It applies from the next session: end this one first."
  - "GPS position in every datalog: on" / "GPS position in every datalog: off (only during a
    session)": with it off, the GPS position goes into datalogs only while a lap session runs.

Notes
  - The datalog needs ECU data: a connected ECU, or a HUD phone receiving the head unit's data.
    With none yet: "No ECU connected yet: the datalog starts when it connects." If it can't
    start: "The datalog couldn't start: it's tried again every 10 s (Diagnostics has why)."
  - Ending a session that started its own datalog also ends that datalog: "Session ended: its
    datalog is saved too".
  - On Android 6–10 the app may ask for storage permission to write the datalog.

--------------------------------------------------------------------------------------------------
13.1.5  External GPS (Bluetooth)
--------------------------------------------------------------------------------------------------
Where:   Lap timer ▸ "External GPS: none (this device's GPS)"
Needs:   DashForge Pro (Lap timer) or DashForge Track · a Bluetooth GPS receiver that sends standard
         NMEA over the serial profile · Bluetooth · the "Nearby devices" permission

What it does
  Uses a fast (10–25 Hz) Bluetooth GPS receiver instead of the device's own GPS. Phone GPS
  (usually 1 Hz) gives lap times to a few hundredths on a steady line; a fast receiver is more
  precise.

How to use it
  1. Pair the receiver in Android's Bluetooth settings first.
  2. Tap the "External GPS: …" button and pick the receiver from the list ("External GPS
     (Bluetooth)"). Pick "None: this device's own GPS" to go back.
  3. The button shows its state, for example "External GPS: <name> · connected · 10 Hz".

Notes
  - While the receiver is sending, the device's own GPS is ignored for timing. It reconnects
    by itself if the link drops.
  - It runs while the lap timer is open or a session is running. Navigation always uses the
    device's own GPS.
  - With nothing paired: "No paired devices: pair the receiver in Android's Bluetooth settings
    first (a 10–25 Hz NMEA receiver)."
  - Without the permission the button shows "needs the Nearby devices permission".
  - Receivers that only use their own Bluetooth Low Energy protocol aren't supported.

--------------------------------------------------------------------------------------------------
13.1.6  g-force
--------------------------------------------------------------------------------------------------
What it does
  Braking, acceleration and cornering g for each lap, the heat map and the friction circle
  come from the device's accelerometer. The app works out which way the car points by itself
  from GPS after a few accelerations and stops ("g: learning the car's direction").

Notes
  - Keep the device fixed in its mount. If it moves, the direction is learned again.
  - Many head units have no accelerometer ("g: no sensor"). If a HUD phone is connected, the
    head unit uses the phone's g instead, shown as "(HUD phone)" after the reading.
  - Lap times work without g; only the g figures are missing ("No g on this lap: the phone
    needs to stay fixed in its mount" on the lap map).

==================================================================================================
13.2  Tracks…
==================================================================================================
Where:   ☰ Menu ▸ Navigation ▸ Lap timer… ▸ "Tracks…"
Needs:   DashForge Pro (Lap timer) or DashForge Track · the shared track list and "Submit to the
         track list": DashForge Track · internet for the track list

What it does
  Lists your saved tracks with their distance from you, "✓" on the one in use, "(track list)"
  for tracks from the shared list, "(awaiting approval)" for ones you've submitted, "· stage"
  for stages and "· <n> sectors".

How to use it
  1. Tap a track for: "Use this track", "Rename", "Clear its sector lines", "Delete" and
     "Submit to the track list".
  2. "Delete several…": tick the tracks to remove, then "Delete…". Tick "Their saved sessions
     too (on this device and in the cloud)" to remove their sessions as well.
  3. "Submit to the track list": sends a track you made to be checked, then shared with
     everyone near it. Give it its real name first with "Rename". "Sent: it'll be in the track
     list once it's checked."

Notes
  - The shared track list (DashForge Track): while linked, the lap timer fetches the tracks
    within 50 km of you once a day, and whenever you start a session with no track nearby.
    They're kept on the device, so they're found with no signal at the track.
  - Without DashForge Track: "The track list is part of DashForge Track: link this device
    first."
  - Only tracks you made can be submitted: "<track> is already from the track list."
  - Deleting a track while linked removes its lines and best lap on your other devices too, at
    their next sync. The track in use can't be deleted during a session: "<track> is in use:
    end the session first."
  - Changing a track (except renaming) needs the session ended: "End the session first."

==================================================================================================
13.3  Sessions…
==================================================================================================
Where:   ☰ Menu ▸ Navigation ▸ Lap timer… ▸ "Sessions…"
Needs:   DashForge Pro (Lap timer) or DashForge Track · per-lap g and ECU figures and "Share as a
         link": DashForge Track

What it does
  Lists saved sessions, newest first: "<date> · <track> · <n> laps · best <time>". Laps are
  saved as they finish, so a key-off never loses a session.

How to use it
  1. Tap a session to see every lap: its time, "best", and its sector times.
  2. With DashForge Track, each lap also shows its g figures (brake, accel, lateral, and how
     much of the lap was "at the limit"), AFR range and seconds lean, coolant, intake air,
     boost and lowest oil pressure (from the ECU, when it sends them), and marks for lean spots
     and oil-pressure dips in corners.
  3. "Laps on the map": opens the session on the map (13.4).
  4. "Share as a link": makes a web link to the session (14.7).
  5. "Delete": "Delete this session?" — "Its laps go for good."

Notes
  - "Last lap on the map" on the lap timer opens the lap just finished (or the newest saved
    session's last lap) against your best. With no finished lap: "No finished lap yet: the
    map opens once a lap is done."
  - Per-lap temperatures and pressures are shown in °C and kPa.

==================================================================================================
13.4  Laps on the map
==================================================================================================
Where:   Lap timer ▸ "Last lap on the map", or Sessions… ▸ a session ▸ "Laps on the map", or
         Cloud files ▸ a lap session (14.5; from there it needs only DashForge Track)
Needs:   DashForge Pro (Lap timer) or DashForge Track · the map under the laps: a map source (12.1)
         and internet · the g colours: g recorded with the laps · channel playback: "Datalog with
         the session"

What it does
  Draws two laps of a session over the map: lap A coloured as a heat map, lap B in grey. Below
  it, a channel plotted by distance for both laps with the time gap between them, and each
  lap's friction circle.

How to use it
  1. The two buttons at the top pick the laps ("A: lap 3  1:32.41", "B: lap 5  1:32.90").
     The line under them says how far B is from A ("B is +0.49 s on A").
  2. "Colour:" picks the heat map for lap A: "Speed", "Total g", "Brake / accel" or "Lateral
     g".
  3. "▶ Play" drives a marker round lap A at its own pace ("❚❚ Pause" stops it). The "1×"
     button cycles the speed: 1×, 2×, 4×.
  4. Drag along the map or the graph to move the marker by hand.
  5. Pick the graph's channel: "Speed", "Long g", "Lat g", "RPM", "Throttle", "AFR", or
     "Datalog…" for any channel the session's datalog recorded.
  6. "FRICTION CIRCLE (A in colour, B in grey; rings at 0.5 g and 1 g)" shows each lap's g.

Notes
  - The time gap is B minus A at the same distance into the lap: above the line, B was behind.
  - Lean spots and oil-pressure dips are marked on the map.
  - Without a map source the laps still draw, on a plain background.
  - "No datalog with these laps: start a session with Datalog with the session on." — the
    "Datalog…" channels need 13.1.4.
  - "This session couldn't be read, or has no lap traces." — the session has no saved trace.

==================================================================================================
13.5  Lap channels on the dashboard and the HUD delta
==================================================================================================
Where:   ☰ Menu ▸ Dashboard ▸ Assign channels…
Needs:   DashForge Pro (Lap timer) or DashForge Track · the delta and predicted lap: DashForge Track
         · the HUD: DashForge Pro or DashForge Track on both devices

What it does
  While a session runs, any dashboard gauge or readout can show "Lap", "Lap time", "Lap delta",
  "Predicted lap", "Last lap" and "Best lap", plus "Long g", "Lateral g" and "Combined g". A HUD
  device gets the head unit's session over the HUD link and shows the same channels, so the
  delta can sit in your line of sight.

How to use it
  1. Assign the lap channels to gauges on the dashboard you'll use on track.
  2. On a HUD set-up, start the session on the head unit. The HUD device shows its lap and
     delta live.

Notes
  - "Lap delta" is minus when you're ahead of your best lap, plus when behind.
  - Without DashForge Track the delta and predicted lap stay blank; the
    lap timer shows "Delta: DashForge Track" in their place. Lap and sector times work with
    DashForge Pro (Lap timer) alone.
  - An imported dashboard's map element also draws a running session's lines.


##### 14. DASHFORGE TRACK #####

==================================================================================================
14.1  What DashForge Track includes, and your link code
==================================================================================================
Where:   ☰ Menu ▸ Navigation ▸ DashForge Track (map source, devices)…
Needs:   DashForge Track · internet

What it does
  DashForge Track is a subscription. It works on its own: you don't need DashForge Pro. Track
  unlocks navigation (the map, search and routing in three vector looks, with no Geoapify key of
  your own) and the map and next-turn elements in dashboards; the lap timer with the delta, the
  predicted lap and the shared track list; the HUD on a second device; cloud sync and backup
  across your devices, share links and your files on the web; and a dashboard design emailed to
  you each month. One subscription covers up to 3 devices, for example the screen in your car,
  a HUD phone and one more.

How to use it
  1. Subscribe on the DashForge website, dashforge.appforged.cc. There's no free trial. Your link
     code looks like DFM-7K4Q-9XPA. It's shown when checkout finishes and on your account page.
  2. Link each device with that code (14.2).
  3. Your code, your devices and cancelling are on your account page at dashforge.appforged.cc.

Notes
  - Track and Pro are separate. Track doesn't include Pro's tuning, imported dashboards (other
    than the monthly design), performance meter, virtual dyno or VE auto-tune; Pro doesn't
    include Track's map with no key, cloud features or lap-timer delta.
  - The app only takes the code; buying, renewing and cancelling happen on the website.

==================================================================================================
14.2  Linking this device
==================================================================================================
Where:   ☰ Menu ▸ Navigation ▸ DashForge Track (map source, devices)…
         Also from the map: "Source" ▸ "DashForge Track: maps with no key of your own (enter your
         code)"
Needs:   DashForge Track · internet

What it does
  Links this device to your subscription, shows the subscription and its devices, and lets you
  remove a device or unlink this one.

How to use it
  1. Under "LINK THIS DEVICE", type your code in "Your code, like DFM-7K4Q-9XPA" (spaces,
     dashes and small letters are fine) and tap "Link this device". It shows "Linking…".
  2. When it works: "Linked: DashForge Track is this device's map source". "THIS DEVICE" now
     reads "Linked as <device name>", with the subscription's state and its renewal or end
     date, for example "Active · renews <date>" or "Cancelled · ends <date>".
  3. Linking a 4th device: the app asks "3 devices are linked. Replace one with this device?"
     and lists them with "(last used <date>)". Tap the one to replace: it's removed and this
     device takes its place straight away. "Cancel" leaves things as they are.
  4. "DEVICES" lists every linked device, "(this device)" marked. "Remove" next to another
     device asks "Remove <device>?": "It stops loading the map within a day, and its place is
     free for another device."
  5. "Check now" asks the server for the subscription's state ("Up to date").
  6. "Unlink this device" ▸ "Unlink": "The map stops loading here until it's linked again with
     your code. Its place is free for another device."

Notes
  - Linking sends your code, a random install id (the server keeps only a one-way hash of it)
    and the device's make and model, which is the name you see in the device list.
  - Linking the same device again doesn't use another place.
  - A code can link at most 10 new devices a day: "This code has linked too many devices today.
    Try again tomorrow."
  - Wrong code: "That code wasn't found. Check it and try again."
  - The device stays linked offline: it renews its link by itself (every day) whenever it has
    a connection, and a link in hand keeps working until it runs out, so the map never locks
    out mid-drive. Track's features on the device itself (navigation, dashboard maps, the HUD,
    the lap timer's extras and the monthly dashboard) keep working for up to 7 days offline
    after the last check-in; the map still needs a connection to load new places.
  - When the subscription ends: the device keeps working until its current link runs out (up
    to a day), then the Track map, sync, cloud files and new share links stop, with "DashForge
    Track has ended on this subscription. Renew at dashforge.appforged.cc." Renewing on the
    website brings it back; "Check now" picks it up at once. Share links you made stop working
    about 30 days after the paid period ended.
  - Messages from the DashForge Track server are shown in English.

==================================================================================================
14.3  Maps with no key of your own
==================================================================================================
Where:   DashForge Track screen ▸ "MAP SOURCE": "DashForge Track" / "My own Geoapify key"
         Or on the map ▸ "Source"
Needs:   DashForge Track (linked) · internet

What it does
  The map, address search, road names and routes come through the DashForge server, so you
  don't need a Geoapify key.

How to use it
  1. Link this device (14.2). Linking makes DashForge Track the map source.
  2. To switch back and forth, tap "DashForge Track" or "My own Geoapify key" under "MAP
     SOURCE". Until the device is linked, DashForge Track shows "Link this device below to load
     the map."; "My own Geoapify key" with no key set shows "No Geoapify key is set: add one on
     the Navigation screen (Source)."

Notes
  - On DashForge Track the map uses the three vector looks only ("Vector: roads only", "Vector
    bold", "Vector light"); the vector tile address is set for you.
  - Privacy: "With DashForge Track, map searches and routes go through our server to the map
    service. It keeps no record of where you searched or drove, only how many map requests each
    device made each day, kept for a week."
  - Each device has a daily map allowance covering map tiles, searches, reverse lookups (road
    names) and routes, and the subscription has a shared daily cap. Past it, new map tiles stop
    loading too, and searches fail with "Lookup failed: Daily map limit reached for this
    device; it resets at midnight UTC."
  - When the map can't load, the map says "No map: DashForge Track" with the reason, for
    example "Checking the DashForge Track subscription: connect to the internet." or "Link this
    device on Navigation ▸ DashForge Track."
  - Saved map tiles keep showing with no signal, the same as with your own key (12.1).

==================================================================================================
14.4  Cloud sync and backup
==================================================================================================
Where:   DashForge Track screen ▸ "CLOUD SYNC AND BACKUP" (shown once the device is linked)
Needs:   DashForge Track (linked) · internet; the automatic sync needs Wi-Fi

What it does
  Keeps these in step across your linked devices and backs them up: dashboards you imported,
  tunes (the tune library's .mst files and exported .msq files), datalogs, captured starts,
  and the lap timer's tracks, best laps and sessions. App settings, keys and the vehicle
  profile are not synced.

How to use it
  1. "Sync now" runs a sync at once. When it finishes, a message says what happened, for
     example "3 uploaded, 1 downloaded", and the line above shows "Last sync <date>: <result>".
  2. "Sync by itself every 6 h on Wi-Fi: on" / "...: off" turns the automatic sync on or off.
     It's on at first. It runs when you return to the dashboard, at most every 6 hours, only on
     a network Android doesn't count as metered.
  3. After a sync, "Cloud allowance: <used> of <total> MB used (datalogs and lap sessions)"
     shows how full your allowance is.
  4. "Delete my data from the cloud…" ▸ "Delete": "Every synced dashboard, tune, datalog, start
     and lap session is deleted from the cloud for good, and the automatic sync turns off. The
     copies on your devices stay." Your tracks and best laps go too, and your share links end.
     Tracks you submitted to the shared track list stay in the list. Your account details (your
     email address and payment reference) aren't deleted by this.

What syncs where
  - Dashboards, tunes, captured starts, tracks and best laps download to every linked device.
  - Datalogs and lap sessions are backed up but not downloaded to your other devices: get one
    from "Cloud files…" (14.5) when you want it.
  - A datalog still being recorded isn't uploaded until it's finished.

Conflicts and limits
  - A tune is never overwritten. If it changed on two devices, both are kept: the other one
    lands beside yours as "<name> (from <device>)". Other items take the newer copy only when
    yours hasn't changed since the last sync; if both changed, both are kept.
  - Tunes and dashboards are always kept, with a tune's last 5 versions. Datalogs and lap
    sessions use your cloud allowance; when it's full the oldest are removed first ("Removed
    from the cloud to make room: <name>").
  - Deleting a file on one device doesn't delete the cloud copy, and the sync won't bring it
    back to that device. To remove it from the cloud, use Cloud files (14.5). Tracks are the
    exception: deleting one removes it everywhere.

Notes
  - Only one sync runs at a time: "A sync is already running".
  - A phone's hotspot often counts as metered, so the automatic sync may not run on it; use
    "Sync now".
  - Your data is stored with our hosting provider in the EU.

==================================================================================================
14.5  Cloud files…
==================================================================================================
Where:   DashForge Track screen ▸ "Cloud files…"
Needs:   DashForge Track (linked) · internet

What it does
  Shows everything synced from your devices, by type, newest first, with the device it came
  from and "On this device" or "Only in the cloud".

How to use it
  1. Pick a type at the top: "Datalogs", "Lap sessions", "Tunes", "Dashboards", "Tracks",
     "Starts" (each with its count).
  2. Tap a file for what you can do with it:
     - Datalogs: "Open" (in the log viewer) or "Download and open" if it's only in the cloud;
       "Share as a link".
     - Lap sessions: "Laps on the map" (13.4) or "Download and open"; "Share as a link".
     - Other types only in the cloud: "Download to this device".
     - Tunes: "Earlier versions…" lists the stored versions ("Version 4 (current) · …"). Tap
       one, then "Save it": it's saved in the tune library beside your tune as a new name.
       Nothing is replaced.
     - Every file: "Delete from the cloud…" ▸ "Delete from the cloud?": "<name>" is deleted from
       the cloud for good, every version. If a datalog or lap session isn't on any device, it's
       gone for good.
  3. "Open on a computer…": see 14.6.

Notes
  - Not linked: "Cloud files are part of DashForge Track: link this device on Navigation ▸
    DashForge Track."
  - A downloaded datalog lands in the app's own logs folder and appears in the log viewer.
  - One download at a time: "Wait for the last one to finish".

==================================================================================================
14.6  Cloud files on a computer (files.appforged.cc)
==================================================================================================
Where:   DashForge Track screen ▸ "Cloud files…" ▸ "Open on a computer…"
Needs:   DashForge Track (linked) · internet · any web browser

What it does
  Opens the same cloud files in a browser, where you can download, open, look through tune
  versions and delete them.

How to use it
  1. In the app tap "Open on a computer…". It shows "On a computer, go to files.appforged.cc
     and enter this code:" with a code like ABCDE-FGHJK.
  2. On the computer, go to files.appforged.cc, type the code under "Sign in with a code from
     the app" (the box shows ABCDE-FGHJK) and click "Sign in".
  3. The page lists your files by type with "Download", "Versions" (tunes), "Open" (datalogs)
     or "Laps" (lap sessions), both in a viewer with graphs and the map, and "Delete".
  4. Click "Sign out" when you're done.

Notes
  - "It works once, for 10 minutes. Don't share it: it opens your files. You stay signed in
    there for 12 hours (or until you sign out); removing this device from your subscription
    signs it out."
  - An old or used code: "That code didn't work. Codes work once, for 10 minutes: make a new
    one in the app."

==================================================================================================
14.7  Share links (share.appforged.cc)
==================================================================================================
Where:   Lap timer ▸ "Sessions…" ▸ a session ▸ "Share as a link"
         ☰ Menu ▸ Logging & dyno ▸ Log viewer… ▸ long-press a log ▸ "Share as a link (DashForge
         Track)"
         DashForge Track screen ▸ "Cloud files…" ▸ a datalog or lap session ▸ "Share as a link"
         Manage them: DashForge Track screen ▸ "Shared links…"
Needs:   DashForge Track (linked) · internet

What it does
  Uploads a datalog or a lap session and gives you a web link anyone can open in a browser,
  with no app and no account.

How to use it
  1. Tap "Share as a link". Under "The link lasts" pick "7 days", "30 days", "90 days", "A year"
     or "Until I revoke it", then tap "Make the link" ("Making the link…").
  2. "Link ready" shows the link: "Anyone with the link can open it, until it ends or you
     revoke it." Tap "Share…" to send it with another app, or "Copy".
  3. "Shared links…" lists your open links: "<title> · ends <date>" (or "no end") "· <n>
     views". Tap one for "Share…" or "Revoke" ("Link revoked: it no longer opens.").

What the viewer sees
  A web page at share.appforged.cc: for a datalog, graphs of its channels and the drive on a
  map; for a lap session, the laps on a map with playback, and two laps compared. An ended or
  revoked link shows "This link has ended."

Notes
  - Only datalogs and lap sessions can be shared, up to 30 MB each: "That one's too large to
    share as a link (30 MB at most)."
  - You can have up to 100 links open at once.
  - A datalog holds your GPS positions, so a shared drive shows where you went.
  - Not linked: "Share links are part of DashForge Track: link this device on Navigation ▸
    DashForge Track."
  - Links end about 30 days after the subscription's paid period ends, and all of them end at
    once if you use "Delete my data from the cloud…".


##### 15. DIAGNOSTICS & APP MENU #####

==================================================================================================
15.1  Unlock / codes…
==================================================================================================
Where:   ☰ Menu ▸ Diagnostics & app ▸ Unlock / codes…  Also opens when you tap a 🔒 feature.
Needs:   Free.

What it does
  The "Unlock" screen lists the tiers (DashForge, DashForge Plus, DashForge Pro and DashForge
  Track), takes a Plus or Pro key or an unlock code, and lists the codes on this device. Opened
  from a locked feature, it says "<feature> is part of DashForge Pro" and what the feature does.
  For navigation, dashboard maps, the HUD and the lap timer it adds "Also included in DashForge
  Track, with or without Pro."

How to use it
  1. Tap "I have an unlock code".
  2. Type or paste your Plus or Pro key from the website (DFP-XXXX-XXXX-XXXX) into "Enter unlock
     code" and tap "Unlock". (A longer code that starts with "DF1." from support works the same
     way.)
  3. A Pro key activates online, once on each device: "Activating…", then "✓ DashForge Pro is
     activated on this device". After that it works offline. A "DF1." code shows "✓ Unlocked".
     The key or code appears under "This device".
  4. No key yet? Tap "How to get one": "DashForge Pro and DashForge Track are bought on our
     website, dashforge.appforged.cc. Your Pro key or link code is shown when checkout finishes
     and on your account page there. A Pro key (DFP-…) goes in "I have an unlock code" and
     activates Pro on up to 3 devices (it needs the internet once; free a place on the account
     page); a Track link code goes in Menu ▸ Navigation ▸ DashForge Track (map source,
     devices)…" (see 14.2). You can long-press the text to copy the website address.

Settings on this screen
  - "This device": each code, what it unlocks, and its end date if it has one.
  - "Install id: …": names this device, for a code made for this device only.
  - "This car: …": this ECU's id, for a code tied to one car ("connect to the ECU to identify
    it" when not connected).
  - Long-press a code to remove it ("Remove this code?" ▸ "Remove"). It stops working on this
    device the next time the app starts, so you can use it on another device.

Notes
  - A code can be tied to one device, one car, or both. A car-tied Tuning unlock only writes to
    that car's ECU. It follows your own changes to that car, but never unlocks a friend's.
  - Write refusals that mention the car: "🔒 Your unlock is for a different car. To move it to
    this one, email support with this car's id…", "Still identifying this ECU — try again in a
    moment.", and "🔒 This ECU can't be told apart from others…".
  - Pro key errors: "Activating needs the internet once. Connect this device and try again.",
    "That Pro key wasn't found. Check it and try again.", "That Pro key was refunded, so it can't
    be activated.", "This device's install id couldn't be read, so the key can't be activated
    here. Restart the app and try again." and "Activation didn't work: <reason>".
  - A Plus or Pro key works on up to 3 devices. To move it to a new one, remove an old device on
    your account page at dashforge.appforged.cc; that device loses it the next time it's online.
  - A Plus key activates the same way as a Pro key. After an upgrade to Pro on the website, each
    device with the key switches to Pro by itself within a day of being online (see 1.5).
  - Code errors: "That code isn't valid — check it was copied whole.", "That code is for a
    different device.", "That code has expired."
  - Keys and codes aren't copied by Android backups. Enter them again on a new device.
  - A code with an end date keeps working for 30 days after it, for devices with a wrong clock or
    that are rarely online.
  - A refunded key or code (a chargeback counts as a refund) switches off the next time the app
    starts after the device has been online, never mid-drive. A dispute decided in your favour
    brings access back. Its line under "This device" is marked " · refunded", and entering it again
    says "That code was refunded, so it no longer unlocks anything." The app checks the list of
    refunded codes when it starts (if it's online) and every 6 hours while it runs.
  - DashForge Track isn't entered here. Link it in ☰ Menu ▸ Navigation ▸ DashForge Track (map
    source, devices)… (see 14).

==================================================================================================
15.2  Check-engine log
==================================================================================================
Where:   ☰ Menu ▸ Diagnostics & app ▸ Check-engine log. Also: tap the check-engine banner.
Needs:   Free · an MS3 with a built-in definition, connected, for new entries.

What it does
  While a fault is active, an amber banner on the dashboard names it: "⚠ CHECK ENGINE: <faults>"
  (with the sync reason for a loss of sync). Each new fault is written to the check-engine log
  with the time and a snapshot (RPM, coolant, MAP, TPS, battery, AFR). The log survives a
  restart, so you can see later what tripped the light.

How to use it
  1. Open the log. The newest entries are listed (up to 100).
  2. "Dismiss alert" hides the banner until a new fault appears.
  3. "Clear log" asks "Clear the check-engine log?" ▸ "Clear". This can't be undone.
  4. "Close" goes back.

Notes
  - Faults it names: MAP, IAT and coolant sensors, TPS, battery voltage, O2 / AFR sensor, loss of
    sync, EGT sensor, flex-fuel, MAF, knock and cam sensors, oil and fuel pressure, EGT and AFR
    safety shutdowns, water-injection low, safety shutdown.
  - The ECU keeps a fault latched until a key cycle or until it's cleared in your tuning
    software. Dismissing only hides the banner.
  - Other firmwares don't show the banner or add entries.

==================================================================================================
15.3  Event log (knock / faults / limiters)
==================================================================================================
Where:   ☰ Menu ▸ Diagnostics & app ▸ Event log (knock / faults / limiters)
Needs:   Free · a connected ECU · the event log switched on (it is by default).

What it does
  Records what just happened, on top of the datalog: check-engine faults starting and clearing,
  knock (with its peak retard), the rev limiter, launch / 2-step and nitrous. Each line has the
  time and a snapshot (RPM, MAP, coolant, TPS, AFR). It survives a restart.

How to use it
  1. Open it. The newest events are listed (up to 200).
  2. "Turn OFF" / "Turn ON" switches recording ("Event log OFF" / "Event log ON").
  3. "Clear log" asks "Clear the event log?" ▸ "Clear". This can't be undone.

Notes
  - Only events your firmware reports are recorded. A channel the firmware doesn't have is
    skipped.
  - The same switch is in ☰ Menu ▸ Logging & dyno ▸ Datalog channels… ("Also write a timestamped
    EVENT log (knock, faults, rev-limit, launch, nitrous). Saved as you tick it.").
  - While the event log is OFF nothing is recorded, warning lines from Warning banners (5.1)
    included.
  - Empty: "No events recorded yet. Events are captured while connected when the event log is
    on".

==================================================================================================
15.4  Share diagnostics
==================================================================================================
Where:   ☰ Menu ▸ Diagnostics & app ▸ Share diagnostics
Needs:   Free · an app to share with (email, messaging, file manager).

What it does
  Sends the app's diagnostics log (and the auto-tune log, if there is one) through Android's
  share sheet. The copy is cleaned first: no Bluetooth or network addresses, no navigation
  destinations.

Notes
  - "No diagnostics captured yet." means there's nothing to send.
  - With no share app: "No app to share with. File: Android/data/…/files/diag/diag.log".
  - For a fuller picture, use "Send details to support" (15.5).

==================================================================================================
15.5  Send details to support — screens, probes, logs
==================================================================================================
Where:   ☰ Menu ▸ Diagnostics & app ▸ Send details to support — screens, probes, logs
         Also: "Send to support" / "Send details to support" on the setup screen.
Needs:   Free · an email app (or a way to copy a file off the device).

What it does
  Bundles what support needs into one zip and hands it to your email app, addressed to
  support@appforged.cc. You choose what goes in; nothing is sent until you tap Send.

How to use it
  1. Tap the row. "Send details to support" lists what can go in. Tick or untick each:
     - "Your INI…" and "Your tune…" (the MSQ from setup and the latest tune saved from this ECU).
       Unticked from the menu, ticked from the setup screen.
     - "Screenshots of the app's screens".
     - "Check reports for this ECU (they list some of your tune's values)".
     - From the setup screen also: "The connection trace and the timeline" and "The device probe
       and the render test".
     - "The diagnostics log, cleaned (no Bluetooth addresses, network addresses or
       destinations)".
  2. Tap "Continue". "Collecting the details…" shows while it builds.
  3. Choose your email app. The email starts with "What happened (please describe):": write a
     line or two there, then tap Send.

Notes
  - No email app: "Saved for support". The zip goes to Documents/DashForge/Support. Copy it to a
    phone or computer and email it to support@appforged.cc with the subject the message shows.
  - The screenshots are of DashForge's own screens only.

==================================================================================================
15.6  Sensor & GPS probe…
==================================================================================================
Where:   ☰ Menu ▸ Diagnostics & app ▸ Sensor & GPS probe…
Needs:   Free · the location permission for the GPS part.

What it does
  Shows what this device's sensors and GPS really provide: the accelerometer live (values, rate,
  and whether it's "REAL & responsive ✓" or "STUBBED? values not changing — likely unusable"),
  the gyroscope, GPS fixes, rate, Doppler speed and accuracy, and every sensor the device has.

How to use it
  1. Open it. Allow location if asked.
  2. Drive a little, with some acceleration and braking.
  3. Tap "Log snapshot to diagnostics" ("Logged to diagnostics ✓").
  4. To have support look at it: ☰ Menu ▸ Diagnostics & app ▸ Send details to support.

Notes
  - "No accelerometer on this device → performance meter would be GPS-only (times yes, live
    g-forces no)."
  - "GPS not started (permission?)" means location isn't allowed.
  - Slow fixes show "(~<n> ms between fixes → coarse timing)": timed runs will be less exact.

==================================================================================================
15.7  Device info / hardware probe…
==================================================================================================
Where:   ☰ Menu ▸ Diagnostics & app ▸ Device info / hardware probe…
Needs:   Free.

What it does
  A read-only report of this device: model, Android version, CPU and memory, screen and refresh
  rate, USB, Bluetooth, GPS, sensors, storage, and whether a file picker and an email app exist.
  It also runs a render test: it feeds a dashboard changing values and measures how smoothly the
  screen draws it.

How to use it
  1. Open it. The render-test line shows fps, the worst frame and the jank %.
  2. Tap "Dash ▾" to test another built-in dashboard, or the active one.
  3. Tap "Copy" or "Share" to send the report.

Notes
  - If the test sits well below the target fps, this device can't repaint the whole dash fast
    enough. That's what makes needles look twitchy. Try a simpler dashboard.
  - No share app: "No share target — use Copy instead".

==================================================================================================
15.8  About…
==================================================================================================
Where:   ☰ Menu ▸ Diagnostics & app ▸ About…
Needs:   Free.

What it does
  Shows "DashForge <version>", the dashboard in use, and the firmware your ECU reports ("(none
  seen yet)" before the first connection). It points to the Dash Designer
  (dashdesigner.appforged.cc) and support@appforged.cc.

How to use it
  1. Tap "Credits & privacy" for 15.9, or "Close".

==================================================================================================
15.9  Credits, licences & privacy…
==================================================================================================
Where:   ☰ Menu ▸ Diagnostics & app ▸ Credits, licences & privacy…  Also from About….
Needs:   Free · internet for the privacy policy.

What it does
  Lists the credits and licences: firmware definitions (built from each firmware's INI; the INI
  files' help text isn't included), maps and weather (OpenStreetMap data, OpenMapTiles vector
  tiles, Geoapify for tiles, search and routing, the Google Weather API for the outside
  temperature), and trademarks.

How to use it
  1. Tap "Privacy policy" to open dashforge.appforged.cc/privacy/ in a browser.

Notes
  - No browser: "Open https://dashforge.appforged.cc/privacy/ in a browser".


##### 16. WHICH FEATURES NEED WHICH SENSORS #####

==================================================================================================
16.1  Your Android device
==================================================================================================
Where:   Check what yours has: ☰ Menu ▸ Diagnostics & app ▸ Sensor & GPS probe… (15.6) and
         ☰ Menu ▸ Diagnostics & app ▸ Device info / hardware probe… (15.7).

What it does
  Android devices differ. A phone usually has everything below. A head unit often has no
  accelerometer and a slow or weak GPS. This list says which features use each part of the device,
  and what happens without it.

GPS (location permission, with "Use precise location" on)
  Used by:  Navigation (12), the lap timer (13), the performance meter (8.6), GPS road speed
            (6.8), the trip computer's distance, economy and range (9), Calibrate VSS "Match to
            GPS" (10.4), gear detection when the ECU has no road speed (10.5), the dyno's speed and
            wheelspin check (8.4), and the GPS columns in datalogs (8.1).
  Without:  Navigation and the lap timer can't run ("Waiting for GPS…", "The lap timer needs
            precise location (GPS)."). The performance meter has no times. Trip distance stays at
            zero. With only approximate location: "GPS speed needs precise location…".
  Tips:     Head-unit GPS can take minutes to lock and update slowly; a phone's is usually better.
            For the lap timer, a 10–25 Hz Bluetooth GPS receiver is more precise (13.1.5).
            Navigation and the performance meter always use the device's own GPS.
            The dashboard's GPS pauses while another screen is in front. Keep the dashboard on
            screen while you log a dyno pull (8.1, 8.5).

Accelerometer (plus Android's gravity and linear-acceleration sensors, where the device has them)
  Used by:  live g-force in the performance meter (8.6), the lap timer's g figures, heat map and
            friction circle (13), the g columns in datalogs (8.1). The app also counts a device
            with no accelerometer as a head unit (1.4).
  Without:  times still work; only the g figures are missing ("g: no sensor", "No usable
            accelerometer on this device. Times still work from GPS; live g-forces are unavailable
            here."). A head unit with none can use a HUD phone's g instead (6.4.10).
  Tips:     Mount the device firmly. If it moves in its mount, the app learns the car's direction
            again. Without a gravity sensor, the performance meter shows "Level (hold still)".

Screen rotation (the device's motion sensor)
  Used by:  "Screen rotation" (6.5). A head unit fixed in the dash usually stays in landscape.

Bluetooth (Android 12 and later also ask for the "Nearby devices" permission)
  Used by:  Bluetooth ECU adapters (1.3), an external Bluetooth GPS (13.1.5).
  Without:  use a USB cable for the ECU ("No USB or Bluetooth" if the device has neither).

USB host (OTG)
  Used by:  USB ECU cables (1.3). A phone or tablet needs a USB OTG adapter.

Wi-Fi Used by:  the HUD link between the device connected to the ECU and a second device (6.4). Both
  must be on the same network. 5 GHz works much better than 2.4 GHz. No internet is needed for the
  link.

Internet
  Used by:  the navigation map, search and routing (12; places the map has already shown still
            display offline), the outside temperature (12.6), downloading a language (6.2),
            everything in DashForge Track (14), the shared track list (13.2), the privacy policy
            page (15.9), and emailing support (15.5).
  Not needed for: connecting to the ECU, the dashboard, logging, tuning, the tune library, the HUD
            link.

A text-to-speech voice
  Used by:  spoken navigation directions (12.4). Without one the app says so, and directions are
            shown but not spoken. With no voice for your language, they are spoken in English.

The head unit's day / night signal
  Used by:  "Day / night: Auto" (6.1). Without it, Auto follows Android's dark theme. Pick "Day"
            or "Night" by hand, or run Night / illumination signal… (6.3) for support.

A battery
  Used by:  the battery icon (6.7). Most head units have none, so nothing shows.

"Display over other apps" permission
  Used by:  a dedicated HUD device starting itself on power-up (6.4.7).

Not used
  DashForge doesn't need a gyroscope, compass, light sensor or barometer. The map's heading comes
  from GPS. The Sensor & GPS probe shows a gyroscope only for information.

==================================================================================================
16.2  What your ECU must send
==================================================================================================
What it does
  Some features depend on what your ECU and its sensors provide, not on the Android device.

  - A wideband O2 sensor, streamed with its AFR target: VE auto-tune (7.5), VE analyze (8.3.4),
    the AFR figures in captured starts (7.7.2) and the "AFR vs target" graph (8.3.2).
  - A 16×16 VE table 1: VE auto-tune and VE analyze (MS3, MS2/Extra, Speeduino; not MS1).
  - A road speed (VSS) channel: "Road speed from: ECU (VSS)" (6.8), Calibrate VSS (10.4). MS3,
    Speeduino and firmwares set up from your own INI with a VSS have one; the built-in MS2/Extra
    and MS1 definitions don't.
  - A fuel-flow channel: fuel used, economy and range in the trip computer (9). Among the built-in
    firmwares, only MS3 sends it.
  - A gear channel: the GEAR display (10.5). MS3 and Speeduino work out the gear themselves when
    it's set up; otherwise DashForge can estimate it.
  - Fault bits: the check-engine banner and log (15.2) need an MS3 with a built-in definition.
  - Output-test settings: output tests (10.6) on MS3 and MS2/Extra.
  - TPS calibration settings: Calibrate TPS (10.3) on MS3, MS2/Extra and Speeduino.
  - The cranking tables: the cranking tuner (7.6) on MS3 and MS2/Extra.
  - rusEFI: the dashboard, datalogging and reading the tune. Editing isn't available yet.


##### 17. TROUBLESHOOTING #####

Each entry starts with what you see (the app's own message, in quotes, or the problem), then what
to do. The section numbers point to the full explanation.

==================================================================================================
17.1  Connecting to the ECU
==================================================================================================
  "Tap Connect" / "No adapter selected — pick your USB/Bluetooth adapter."
    Tap "Connect" on the top bar and pick your adapter in "Connect to ECU" (2.3).

  "Plug in the ECU (USB) or pair its adapter (Bluetooth) first."
    The list is empty. Plug the cable in with the key on, or pair the Bluetooth adapter in
    Android's Bluetooth settings first. DashForge only lists paired adapters (1.3).

  "USB device not attached — tap Connect"
    Key on, cable seated, then tap "Connect".

  "Waiting for USB permission…" / "USB access wasn't allowed…"
    Answer Android's question with Allow. If you refused, tap "Connect" (or "Allow USB access") to
    be asked again.

  "Bluetooth is off — turn it on to connect"
    Turn Bluetooth on.

  "Allow Nearby devices so DashForge can reach your Bluetooth adapter"
    Tap the status line and allow it. If Android won't ask again, allow "Nearby devices" in
    Android's settings for DashForge.

  "No ECU data — check module baud (…)" / "Bluetooth is linked but the ECU is sending no data…"
    The Bluetooth adapter's own baud rate must match the ECU: usually 115200, 9600 for an MS1. You
    set it in the adapter, not in DashForge (1.3).

  "No ECU data — check baud (…)" / "Linked but the ECU is sending no data…"
    Check the cable and adapter, and that the ECU's serial speed matches.

  "Connected — no signature yet (…)"
    The link works but the ECU didn't say what it is. Check the cable or adapter. On a Speeduino
    linked through its secondary serial port, set that port to the tuning-software protocol.

  "Connected — no reply from the MS1 (check the link is 9600 baud)" / "MS1: no answer"
    Set the adapter to 9600. If an MS1 still isn't found, set ☰ Menu ▸ Connection ▸ "ECU
    type" (under "Advanced") to "Always MS1" (11.5).

  "No ECU data over the <chip> adapter — send details to support"
    CH340 / CP210x adapters are new. Send details to support (15.5) and use an FTDI or CDC
    adapter, or Bluetooth, meanwhile.

  "<chip> adapter not supported yet"
    PL2303 adapters don't work. Use an FTDI or CDC adapter, or Bluetooth.

  "Disconnected: garbled data from the adapter (check the baud rate)"
    A baud rate mismatch. See the baud entries above.

  "Disconnected — auto-reconnect paused. Tap Connect… to reconnect."
    You tapped Disconnect. Tap "Connect", or re-plug the USB cable (2.3).

==================================================================================================
17.2  Setup and verification
==================================================================================================
  The dashboard keeps asking me to set up or verify the ECU. Until the ECU is verified on this
    device, editing and MSQ import / export stay off (editing stays on for a grandfathered firmware,
    2.4), and the reminder comes back at each start. Tap "Set up now" or "Verify now" (2.2, 2.4).
    "Later" only puts it off.

  "“<file>” is for “<a>”, but your ECU reports “<b>”. Choose the INI for <b>."
    The INI is for a different firmware. Use the INI that matches what your ECU reports.

  "“<file>” was made by DashForge, so it can't check the app. Save one from your tuning software."
    Verification needs an MSQ saved by your tuning software while connected to this ECU.

  "⚠ <n> mismatches (…) — this MSQ likely doesn't match the current flash…"
    The tune changed since the MSQ was saved. Save a fresh MSQ and run again.

  "A quick tune is live in the ECU's RAM…" / "Page(s) … have changes that aren't burned…"
    Verification needs RAM to hold your burned tune. Revert the quick tune or burn the changes,
    or cycle the key and tap the button that says so (2.4).

  "The app was updated. Check this ECU again — about a minute, no files needed."
    Tap "Check now".

  "The ECU reports a new firmware release (…), so this check needs a fresh MSQ…"
    You updated the ECU's firmware. Save a new MSQ from your tuning software and verify again.

  I can't find my INI or MSQ in the file list.
    Android 11 and later only let the app search a folder you pick. Tap "Pick a folder to search",
    or open the file from your email, messaging or file app and choose DashForge (1.6, 2.2.2).

==================================================================================================
17.3  Editing and burning
==================================================================================================
  "Read-only until this ECU is verified (Tuning ▸ Set up & verify this ECU) — nothing written."
    Verify the ECU (2.4).

  "🔒 Tuning isn't unlocked on this device — nothing written."
    Writing to the ECU needs DashForge Pro: ☰ Menu ▸ Diagnostics & app ▸ Unlock / codes… (15.1).

  "🔒 Your unlock is for a different car…"
    Your Tuning unlock is tied to another car. Email support with this car's id, shown in Unlock /
    codes… under "This car" (15.1).

  "Still identifying this ECU — try again in a moment. Nothing written."
    Wait a few seconds after connecting, then try again.

  "⚠ … read back as …, not … — NOT what was written. Do not burn; re-check."
    The write didn't take. Don't burn. Reopen the screen to read it again (7.1).

  "A quick tune may be in RAM — revert it (or cycle the key) before burning. Nothing burned."
    Tap the "● Quick tune LIVE — tap to revert" pill, or turn the ignition off and on (7.9).

  "An MS1 keeps one page in RAM: burn (or drop) changes on another page before opening this one."
    Burn the other page first, or cycle the key to drop the changes (7.1.3).

  A red "⚠ <n> unburned pages — tap to burn" row stays at the top of the menu.
    Your changes are in RAM only. Tap it and "Burn" to keep them, or cycle the key to drop them
    (7.1.2).

  "Engine running" when loading a tune
    Loading a whole tune is blocked above 1200 rpm. Idle or switch off, then load (7.8.2).

  "RPM is … Tune swaps are blocked above 1500 rpm — return to idle or shut off." / "RPM is …
  Reverting is blocked above 1500 rpm, like a swap — return to idle or shut off, then tap revert
  again."
    Quick-tune buttons only work at 1500 rpm or less (7.9).

==================================================================================================
17.4  The dashboard and display
==================================================================================================
  "No dashboard to the right — set one in Menu ▸ Dashboard ▸ Dashboards."
    Only one page is set. Add pages in Dashboards (4.1).

  "🔒 Imported dashboards aren't unlocked — showing a built-in (Menu ▸ Diagnostics & app ▸ Unlock /
    codes)" Imported dashboards need DashForge Pro (15.1). The built-in dashboards are free.

  "This is not a valid .msdash file — the JSON could not be read." / "This is not a .msdash
  template…"
    The file was damaged or isn't a dashboard. Export it again from the Dash Designer, and don't
    open or re-save it in another app on the way (4.2).

  "This dashboard says it was signed by DashForge, but its signature doesn't check out…"
    A monthly DashForge Track design was changed or damaged on the way. Download it again from
    the email it came in (4.1).

  "Unsupported dashboard schema … Update the app to open this dashboard."
    The dashboard was made for a newer DashForge. Update the app.

  "The dashboard file is too large (… KB; the limit is … KB)."
    Use smaller pictures (mood figures, background images) in the designer, then export again.

  "No .msdash file found" / the file picker doesn't show my dashboard
    Copy the file into the Download folder and try again, or open it from a file manager (or share
    it from email or a messaging app) and choose DashForge (4.1).

  A gauge shows "--"
    There's no ECU data, or this firmware doesn't have that channel. Check the connection, or pick
    another channel in Assign channels… (4.3).

  Day / night "Auto" doesn't follow my headlights.
    Pick "Day" or "Night" by hand for now, and run Night / illumination signal… (6.3). Send the
    result to support.

  The screen looks grey at night on an LCD head unit.
    HUD & display… ▸ "Screen brightness" ▸ "Manual (separate day / night)", and lower "Night (deep
    black)" (6.4.9).

  Needles look jumpy or the dashboard stutters.
    Run Device info / hardware probe… (15.7). If the render test is well below its target, try a
    simpler dashboard.

==================================================================================================
17.5  Logging, dyno and timing
==================================================================================================
  "Log saved — <n> rows, 0 with data" / the log viewer says "Header only"
    The log ran with no ECU connected. Connect first, then start the log (8.1).

  "No datalogs found." after reinstalling the app
    On Android 11 and later, use ☰ Menu ▸ Logging & dyno ▸ Show logs & tunes from before this
    install… and pick Documents ▸ DashForge (1.6).

  The GPS columns in my log are empty.
    Allow location with "Use precise location". Keep the dashboard on screen: its GPS pauses while
    another screen is in front (8.1).

  "No speed source in this pull…" / "Dyno: captured a pull but no speed source (VSS/GPS) — ignored"
    The dyno needs road speed. Keep the dashboard on screen with a GPS fix while you log, or use
    an ECU with VSS (8.4, 8.5).

  "⚠ PART-THROTTLE …", "⚠ GEAR CHANGE in pull" or "⚠ PARTIAL range"
    Redo the pull at full throttle, in one gear, from low rpm to near the redline (8.4.1).

  "No usable accelerometer on this device…" / "g: no sensor"
    Normal on many head units. Times still work. For g, use a phone, or link a HUD phone (6.4.10).

  "This ECU doesn't send fuel flow, so fuel used, economy and range stay blank."
    Only MS3 sends fuel flow among the built-in firmwares. Distance and trip time still count (9).

==================================================================================================
17.6  Navigation, lap timer and GPS
==================================================================================================
  "No Geoapify key — tap Source to paste one."
    Add a map source: your own Geoapify key, or link DashForge Track (12.1).

  "Waiting for GPS…"
    Turn on Location and give the device a clear view of the sky. A head unit can take a while.

  "Navigation needs precise location — turn on "Use precise location" in DashForge's location
  permission."
    Android Settings ▸ Apps ▸ DashForge ▸ Permissions ▸ Location: allow it and turn on "Use precise
    location".

  "No data connection. The map is kept for the places it has shown with data, and it hasn't shown
  this one yet."
    Connect to the internet. Places you've driven with data stay on the device for next time.

  "Data is off. Tap Data:Off to load the map."
    Tap "Data:Off" on the map to turn downloads back on (12.2).

  "No speech engine on this device…" / "No voice data…"
    Install a text-to-speech voice in Android's settings, then reopen the map (12.4).

  The radio isn't turned down during directions.
    In the "Navigate" panel, tick "Mute radio", use the "Alarm" channel, or pick "Prompt ducking:
    Strong" (12.4).

  "Passed <n> m from the start line without crossing it: the wrong way, or past its ends"
    Cross the line in the direction you were driving when you set it, or set it again (13.1.1).

  "GPS lost: lap dropped"
    The GPS dropped out for more than 5 seconds. Improve the mount's view of the sky, or use a
    10–25 Hz Bluetooth GPS (13.1.5).

==================================================================================================
17.7  The HUD link
==================================================================================================
  "Not paired with a head unit: Menu ▸ Dashboard ▸ Display ▸ HUD & display"
    Tap the status line to open HUD & display, then pair the devices under "Pairing" (6.4.3).

  "The head unit's data doesn't match this HUD's pairing code: check it in Menu ▸ Dashboard ▸
  Display ▸ HUD & display"
    The head unit has a new code, or it was mistyped. On the HUD device tap "Un-pair" and type the
    code the head unit shows now (6.4.3).

  "Waiting for head unit on Wi-Fi (:45654)" never changes.
    Both devices must be on the same Wi-Fi network (compare "This device's Wi-Fi IP: …"), with the
    router's AP / client isolation off. The head unit must be set to "Broadcast to HUD", and both
    paired and unlocked.

  The HUD freezes for a second or more every few seconds.
    Move the hotspot or router to 5 GHz Wi-Fi. On a travel router, set DTIM to 1 and turn client
    power saving off (6.4.3).

  "🔒 HUD isn't unlocked on this HUD device"
    The HUD needs DashForge Pro or DashForge Track on each device, the HUD device included (6.4.1).

  "HUD linked — waiting for ECU data" / "Head unit has no ECU data"
    The HUD link works. Connect the head unit to the ECU.

==================================================================================================
17.8  DashForge Track
==================================================================================================
  "That code wasn't found. Check it and try again."
    Type the code again: it's shown when checkout finishes and on your account page (14.2).

  "3 devices are linked. Replace one with this device?"
    A subscription covers 3 devices. Pick the one to replace, or "Cancel" (14.2).

  "DashForge Track has ended on this subscription. Renew at dashforge.appforged.cc."
    Renew on the website, then tap "Check now" on the DashForge Track screen.

  "Lookup failed: Daily map limit reached for this device; it resets at midnight UTC."
    Each device has a daily map allowance (tiles, searches, road names and routes), and the
    subscription has a shared cap. Past it, new map tiles stop loading too. It resets at
    midnight UTC.

  The automatic sync never runs.
    It only runs on a network Android doesn't count as metered. A phone's hotspot usually counts as
    metered. Tap "Sync now" (14.4).


##### 18. GETTING HELP #####

==================================================================================================
18.1  Before you contact us
==================================================================================================
  1. Search for it: ☰ Menu ▸ Find a setting… finds any menu row or setting by a word in its name.
  2. Look up the message you see in Troubleshooting (17). Most messages in DashForge also say
     what to do next.
  3. Check what your device has: ☰ Menu ▸ Diagnostics & app ▸ Sensor & GPS probe… (15.6) and
     Device info / hardware probe… (15.7). Many "it doesn't work" problems come down to a missing
     sensor, a permission, or a weak GPS (16).

==================================================================================================
18.2  Contacting support
==================================================================================================
Where:   ☰ Menu ▸ Diagnostics & app ▸ Send details to support — screens, probes, logs
Needs:   Free · an email app, or a way to copy a file off the device.

How to use it
  1. Make the problem happen once more, if you can, so it's in the diagnostics log.
  2. Open Send details to support. Tick what support should see (15.5). Leave your INI and tune
     unticked unless the problem is with your ECU set-up or tuning.
  3. Tap "Continue" and choose your email app.
  4. Under "What happened (please describe):", write what you did, what you expected and what
     happened instead. Then tap Send.

Notes
  - The email goes to support@appforged.cc. You can also write to that address directly.
  - Nothing is sent until you tap Send in your email app.
  - With no email app, the bundle is saved in Documents/DashForge/Support. Copy it to a phone or
    computer and email it from there.
  - For a problem with the HUD link, send details from both devices.
  - Unlock codes: support also issues codes and moves a car-tied unlock to another car. Your
    install id and car id are on the Unlock / codes… screen (15.1).
  - The privacy policy is at dashforge.appforged.cc/privacy/.


End of the DashForge user guide.