Developer options

Developer options are advanced support shortcuts in Settings. Most runners do not need them during normal use.

Use this area only when Kinni support or development asks you to gather diagnostic information. Some shortcuts can show low-level Bluetooth details, export local app data, or reset parts of the app.

1. Open Kinni.
2. Go to Settings.
3. Scroll to Developer options.
4. Turn on Show developer options.

Kinni then reveals extra shortcuts such as Bluetooth scan, Share database, and Danger zone. Beta, internal, or local builds may show additional debugging actions that are not visible in the store version of Kinni.

Support may ask you to use Bluetooth scan when a device needs a lower-level Bluetooth check. This is different from connecting to a treadmill from the Run screen.

Use it only when support asks:

1. Open Settings → Developer options.
2. Turn on Show developer options.
3. Tap Bluetooth scan.
4. Tap Scan.
5. Wait for nearby Bluetooth devices to appear.
6. Tap the device support asked you to inspect. The device may show a name, or it may only show a device identifier.
7. Tap Discover.
8. Share the requested screenshots or details with support.

The Discover screen can show Bluetooth GATT details such as:

• service names or UUIDs;
• whether a service is primary;
• characteristic names or UUIDs;
• characteristic properties, such as readable, writable, notifiable, or indicatable;
• descriptors;
• optional decoded values when Kinni can read and display them.

This can help support inspect Bluetooth devices such as treadmills, foot pods or other Running Speed and Cadence sensors, heart-rate monitors, and other nearby BLE devices involved in an investigation.

Do not confuse Developer-options Bluetooth scan with the Run-screen Diagnostics or FTMS Checker flow.

• FTMS Checker is for a connected FTMS treadmill. It can run treadmill-specific diagnostic probes and may move the belt or change incline.
• Bluetooth scan is a lower-level support tool. It lists nearby Bluetooth devices and can inspect the services and characteristics a selected device exposes.

If support asks for an FTMS Checker report, use Use the FTMS Checker. If support asks for a Bluetooth service list, GATT details, characteristics, or Discover results, use Developer-options Bluetooth scan.

If the device is a treadmill or is near a treadmill:

• stand off the belt;
• keep the treadmill stopped;
• keep the area around the treadmill clear;
• keep the safety key or emergency stop within reach if the treadmill is powered on.

When sharing screenshots, avoid posting private details publicly. Device identifiers, account details, nearby device names, and decoded Bluetooth values may be useful for support but should be shared only through the support channel support asked you to use.

Support may ask you to use Share database when they need to investigate a local-data issue.

1. Open Settings → Developer options.
2. Turn on Show developer options.
3. Tap Share database.
4. Tap Share database again on the export screen.
5. Send the file only through the approved support channel.

The exported file is Kinni’s local SQLite database from your device. It can include local training, account, session, workout, support, and app-state data. Do not share it publicly.

If Kinni says your device cannot share the file, contact support. They may give you manual instructions for copying the file from your phone or tablet.

You can also review App analytics and diagnostics to understand related diagnostic screens such as Database statistics.

Danger zone contains destructive reset and recovery tools. Do not use it unless support or development gives you a specific instruction.

Depending on your build, Danger zone can include actions that:

• reset app settings;
• clear stored sessions or records;
• clear saved custom workouts;
• import or overwrite the local SQLite database;
• clear authentication or stored app state;
• send a test event for crash-reporting checks.

These actions can remove local data, change app state, sign you out, or replace the local database. If you are not sure why you are being asked to use Danger zone, stop and ask support first.

Beta, internal, or local builds may show additional Developer options actions. For example, non-production builds may include a Create session shortcut for development testing.

Do not use these actions unless support or development asks you to. They can create artificial data or change the app state in ways that do not match a normal run.

Stop and ask support before continuing if:

• you cannot identify the Bluetooth device support asked about;
• Discover fails or shows an error;
• the app asks you to share a database file and you are unsure where to send it;
• a Danger zone action sounds destructive or does not match the instruction you were given.

Developer options are there to help support investigate specific problems. They are not needed for normal training, connection, or session management.