Choose the optional sensor workflow

Open More → Connections. If Sensor Lab is not already visible, expand Optional tools and choose Open on Sensor Lab recordings. Existing recordings, saved sensor interest or consent keep it directly visible. Sensor interest is also available in Profile → Optional setup; interest does not grant consent.

Sensor Logger file import

Secure the phone or Watch before driving and start or stop only when parked or outside the vehicle. Export one Zipped CSV recording at a time. The selected file is cached in this browser and retained privately in account storage until you delete that recording.

Location supports route, speed and repeated-loop estimates. Accelerometer and gyroscope channels provide relative motion only. Heart rate is optional and is not required for driving analysis.

Choose the Sensor Logger recording mode that matches the devices you secured before the session:

• iPhone Only Mode records the mounted phone channels.
• Phone & Watch Mode combines the mounted phone with a worn Watch in one integrated workflow.
• Watch Only Mode records the worn Watch when no phone recording is available.

Keep the exported channels together. Driver OS uses their timestamps and device metadata to distinguish phone, Watch and combined recordings; it does not treat one device as if it measured the other.

Driver OS native companion

The iPhone and Watch companion is internal-only. Private cloud delivery requires an enabled internal build, account eligibility and separate consent. It is the destination for complete recordings used in analysis. Native release defaults remain off. Only the explicitly signed Owner Internal archive may enable the private cloud delivery override; accepted-slice sync remains off. This is not a public native release.

Older native recordings retain their existing private cloud delivery behavior. Private cloud storage has its own consent. When that consent and the Owner Internal override are enabled, a new raw phone or Watch source may be retained privately for analysis and research even when it is rejected or ambiguous. Cloud delivery does not accept the source, link it to a race or turn it into an analytical slice. Idle, walking, stationary, removed-Watch, unusable and ambiguous recordings do not become accepted analytical evidence.

For those older recordings, the companion keeps a local copy until the private cloud receipt is verified. Only then can receipt-first cleanup remove that exact device copy. If upload or cleanup is interrupted, the local copy remains available for retry; unrelated recordings must remain untouched.

Expanded internal recordings

Expanded internal builds record supported motion, magnetic field, compass, attitude, altitude and movement context in a private local recording. Race telemetry controls motion collection; Location is separate. Heart rate is unavailable and Driver OS does not request Health access. A missing or denied individual sensor does not stop the other available channels.

Use Start race, Stop race, optional Kart number, and Cancel recording while safely stationary. Open Advanced → Recording information on the iPhone to verify retained observations and inspect channel availability, permissions, sample rates, gaps and errors. The view can prepare a private export or confirm deletion of that exact local recording.

Each new Start opens Recording setup on the device you use. Review the remembered phone and Watch choices, adjust placement, wrist, motion or GPS if needed, then choose Confirm & start. Your confirmed choices become the next defaults and stay attached to that race. Canceling the review starts nothing and keeps the previous defaults. The receiving device uses the same confirmed setup without a second prompt. Update both apps and open them once before using this setup together; remembered compatibility allows later offline use.

Turn both motion and GPS off for a device you want excluded. Selecting both devices requests both sources; verify their actual recording state before locking the phone. A force-closed or unavailable app may not contribute sensor data. Recording information distinguishes verified saved files from sensor quality and reports invalid sample timing without changing the original observations. Updated internal recordings preserve the actual acquisition end and the shared race stop separately. Full-source diagnostics include the complete recording; the recorded race overlap is a separate derived view. A late or failed phone start can produce an explicit no-contribution result.

Expanded recordings stay local unless expanded private cloud delivery is separately enabled for the native build and your account. A Watch recording must first transfer to the paired iPhone and receive its exact verified receipt. That phone receipt proves transfer to the iPhone; a separate receipt verifies cloud storage. New eligible, finalized recordings then upload through the iPhone. An older full recording requires explicit authorization for that exact source under the current consent. Limited previews remain excluded.

Ready to upload, Uploading and Verifying cloud recording are unfinished states. Stored in cloud requires every part and the exact final receipt to be verified. Interrupted uploads remain local and can retry when the iPhone app is available again; background completion is not guaranteed. Expanded local copies remain retained after verification. Cloud delivery makes the full source available for analysis. It does not promote the source into accepted telemetry or enable accepted-slice sync.

In the compact native Sessions screen, choose the optional Event, Session type and vehicle for the next recording, or create an Event. Open full Sessions in Driver OS uses the existing signed-in web handoff for history, edits and comparisons. Finish the active recording before opening the web app or changing its context. Event selection and recording remain available offline; web handoff requires connectivity.

Indoor metal and motors can distort compass readings. Calibration and heading accuracy remain visible; a repeated shape is not proof of kart heading, steering, a racing line or lap timing. Walking and step information describe device movement, not race performance. Actual channel support and continuity still require physical testing.

Safe operating boundary

• Mount devices before moving.
• Never interact with a phone or Watch while driving.
• Treat routes, speed, braking and motion labels as estimates.
• Official timing remains authoritative.

Using the companion at indoor K1 races

Continue using it for kart context and optional recording when that is convenient. Save the kart number while safely stationary before each race, wear the Watch, and identify whether the phone is mounted, carried, stationary or excluded. Check the assignment in Sessions after the official result arrives.

Recording every indoor race is not required for official-timing analysis. Current native motion evidence has not established a useful lap-performance measurement, and a stationary phone does not measure the kart. More ordinary recordings can document delivery reliability, but they do not replace independent lap-crossing timing and separately labeled idle, handling, staging and racing intervals. A controlled validation visit remains a separate decision. Outdoor GPS has its own future accuracy and reliability gate.

Setup choices and recovery

Onboarding saves sensor interest only. It never turns on sensor processing or private cloud delivery. Review their separate consent controls in Connections → Sensor Lab. The native companion remains private testing with no public download; web eligibility does not guarantee a TestFlight invitation. Accounts aged 13–17 cannot use native capture.