Frequently asked questions

Pitboard is an Android-first vehicle intelligence platform with a browser-based dashboard designer called Pitboard Studio. It combines configurable dashboards, OBD-II telemetry, vehicle records, maintenance information, trip and performance data, diagnostics, and Community sharing in one account-based system.

Pitboard is manufacturer-neutral. Standard OBD-II functions are designed to work with vehicles that expose the required SAE data, but the exact signals available vary by vehicle, model year, powertrain and control module. Manufacturer-specific data is handled separately from the standard PID catalogue.

Pitboard targets standalone Android phones and tablets as well as compatible Android automotive displays. Pitboard Studio includes common landscape and portrait display profiles, ultra-wide layouts and custom dimensions. Android version, Bluetooth hardware, GPS hardware, USB support and vendor firmware can affect compatibility.

Core vehicle functions are designed to work locally. OBD telemetry, dashboards, trip recording, motion sensors, diagnostics and maintenance data should not require a continuous Internet connection. Internet access is used for account services, Community sharing, cloud features, software delivery and other online services.

1. Download the Pitboard APK using Chrome or another browser that supports Android APK downloads.
2. If Android blocks the installation, allow that browser or file manager to install unknown apps.
3. Open the downloaded APK and complete the Android installation prompt.
4. Launch Pitboard and grant only the permissions required by the features you intend to use.

Android menu wording varies by manufacturer and Android version.

Studio is rendered in a desktop browser while the APK is rendered on Android. Font metrics, display density, scaling, vendor firmware and graphics hardware can introduce small differences. Always judge final sizing on the actual target device after installing a fresh build.

This is a development/test APK distributed directly by Pitboard rather than through Google Play. Android may show a Play Protect or unknown-app warning. Choose Install anyway to continue. You may also need to allow your browser or file manager to install unknown apps.

The downloadable Compatibility Test APK scans the Android device locally and creates a capability report. It checks display resolution and density, refresh rate, multitouch, cameras, GPS hardware, Bluetooth Classic, Bluetooth LE, USB Host and built-in sensors including accelerometer, gyroscope, magnetometer, rotation vector, gravity, linear acceleration and barometer.

When the live test finishes, choose Copy & Open Pitboard. Paste the complete capability report into the Compatibility Test page and upload it. Pitboard reads the Installation ID and hardware profile, then opens Pitboard Studio. Studio asks Is this the device you want to register? The device is attached to your account only after you choose Yes.

Both. The static scan records the sensor's advertised timing information, and the live test measures the actual delivered accelerometer and gyroscope sample rate over ten seconds. That observed rate is more useful when deciding whether a device is suitable for performance-oriented motion widgets.

The test checks whether a GPS provider is present and whether location permission has been granted. Live GPS sampling is currently kept in safe mode while Pitboard validates vendor-specific Android location behaviour across different tablets and head units.

The Compatibility Test creates a Pitboard-specific installation ID for that app installation. It is intended to become the device-registration key for the account backend. Pitboard does not need to use the device IMEI, Wi-Fi MAC address, hardware serial number or other invasive hardware identifiers.

After a pasted capability report is confirmed in Pitboard Studio, the device profile is stored on that user's account. Studio can then use the registered capability profile when determining which hardware-dependent widgets are available. Unsupported options can remain visible but be grayed out with a clear reason, while limited capabilities can show a warning instead of being blocked outright.

Keeping the widget visible tells the user that the feature exists and explains why it cannot be used on the selected device. This avoids making a feature appear to have vanished and makes it clear that choosing a different registered device or compatible external sensor may unlock it.

Yes. A tablet may have a slow or missing built-in motion sensor while a validated external sensor provides the required data. Pitboard will track built-in device capability separately from validated accessories so Studio can use the best available source.

No. Camera capability is inspected without reading photos. The test does not read contacts, messages, IMEI, Wi-Fi MAC addresses or hardware serial numbers. Location permission is used only when you choose to run the live GPS test.

Yes. The device-registration design includes a re-test path so a capability profile can be refreshed after an Android update, hardware change or external-sensor change without creating a second account device unnecessarily.

Mount the device rigidly to the vehicle. The accelerometer measures every motion of the device itself, so a flexible gooseneck, loose vent clip, magnetic mount that can rock, or mount with rubbery movement can create false acceleration, braking and cornering readings. A short, solid dashboard, console or windshield mount is preferable.

1. Choose the mounting orientation you will actually drive with before calibrating Pitboard: Screen faces driver / upright or Screen faces up / flat. Pitboard uses that selection when it builds the vehicle-relative motion axes.
2. Keep the device fixed squarely to the vehicle. Do not allow it to swivel during a run.
3. When any accelerometer-dependent widget is present, Pitboard automatically adds an Accelerometer Calibration control. With the vehicle stationary, tap CALIBRATE and keep the tablet still for about half a second. The current mounting angle becomes zero for pitch/roll, and the same calibration removes the stationary gravity offset from the G-force axes.
4. If the mount or device orientation changes, calibrate again.
5. For best repeatability, keep the same device, mount and orientation between sessions.

Built-in phone/tablet sensors are useful for driver-reference data, but mount flex, road vibration and Android sensor hardware can affect the result. They are not a substitute for calibrated motorsport instrumentation.

Position the outward-facing camera where it has a clear, stable view through the windshield without obstructing the driver's view, controls, instruments or any airbag deployment area. Check the camera preview before driving. Avoid placing the lens directly against reflective trim, bright dashboard surfaces or a dirty section of glass.

Keep the device securely restrained so it cannot become a projectile in a hard stop. Provide reliable power for long sessions and allow airflow around the device because continuous screen use, GPS, OBD, sensors and video recording can generate substantial heat.

Add Camera Preview in Pitboard Studio and resize it like any other widget. Select the rear/outward-facing or front/driver-facing camera, choose Fill or Fit, and enable mirroring if required. The installed Android dashboard asks for camera permission only when the dashboard contains a Camera Preview widget.

The Studio shows a camera-layout preview. The installed APK uses the actual Android camera feed, subject to the device's WebView and camera implementation.

Pitboard includes the same proven DJI BLE control process used by Dually Studio. It controls the action camera over Bluetooth Low Energy only. It does not join the camera's Wi-Fi network and does not show a live DJI video preview, so using the DJI widget does not take over the tablet's normal network connection.

1. In Pitboard Studio open Action Cams and add DJI Osmo. Resize it like any other widget. Battery %, time remaining, camera mode and camera status can be shown or hidden in Properties.
2. If you also want a small record button elsewhere on the dashboard, add DJI Lightweight Record Controller. It shares the same camera connection as the full DJI widget; it does not create a second Bluetooth session.
3. Build and install a fresh dashboard APK. Turn on the DJI camera and keep it close to the Android device during the first connection.
4. Allow Pitboard's Nearby devices permission when Android asks. Android 11 and older may request Location permission because those Android versions require location permission for BLE scanning.
5. Press SCAN. One press can perform up to three scan windows. The first compatible DJI camera advertisement found is selected automatically.
6. When a camera is found, CONNECT turns green. Press CONNECT and wait for the widget to reach DJI BLE READY.
7. When the BLE connection is ready, PAIR turns green. Press PAIR. If the camera asks for confirmation, approve it on the camera.
8. After pairing succeeds the widget shows READY, DISCONNECT becomes active, and RECORD can start or stop camera recording.

Pitboard remembers the successfully paired camera and attempts to reconnect to it automatically on later dashboard launches. If the camera was replaced, reset, or is not found, use SCAN again.

The current protocol recognises DJI Osmo Action 4, Osmo Action 5 Pro, Osmo Action 6 and Osmo 360 identifiers. DJI firmware can change Bluetooth behaviour, so verify camera control with the exact camera and firmware version you intend to use before relying on it at an event.

• SCAN: searches for compatible DJI BLE advertisements and automatically selects the first camera found.
• CONNECT: opens the DJI Bluetooth GATT connection and prepares its notify/write services.
• PAIR: performs the DJI protocol handshake after the BLE connection reports ready.
• RECORD / STOP: starts or stops recording on the paired camera.
• DISCONNECT: closes the DJI Bluetooth session without affecting other Pitboard Bluetooth devices such as OBDLink.
• Battery: camera battery percentage when reported by the camera.
• Time Remaining: recording/storage time remaining when reported by the camera.
• Mode: the current DJI capture mode such as Video, Timelapse or SuperNight.
• Camera Status: the current protocol state or camera activity.

The DJI connection is independent of Pitboard's built-in Camera Preview widget. Camera Preview uses the Android phone/tablet camera; DJI Osmo controls an external DJI action camera over BLE.

Yes. When Start / stop camera with data logging is enabled on the Data Logger and the Camera Preview has logger synchronization enabled, starting a logging session also starts video recording and stopping the logger stops the video. The CSV and video use the same session timestamp so they can be matched later.

Video is recorded without microphone audio by default. Camera availability and recording support vary across Android devices, so confirm the live preview and a short test recording on the actual target phone or tablet before relying on it for an event.

Give the device a clear view of the sky for GPS, keep it away from excessive heat, prevent the mount from vibrating against trim, clean the camera lens and windshield, and verify that Android has not disabled camera, location or sensor permissions. Do a short stationary and low-speed test after changing the mount.

OBDLink LX, MX and MX+ are the primary supported adapter families. Android normally uses Bluetooth Classic for LX and compatible OBDLink models. MX+ also provides broader platform compatibility. Generic ELM327-compatible adapters may work, but quality, command support and connection stability vary widely.

Pitboard now uses the same proven Bluetooth Classic connection sequence as Dually Studio. Pair the OBDLink LX in Android's Bluetooth settings first; Pitboard does not create the Bluetooth bond itself. On Android 12 and later, allow Pitboard's Nearby Devices permission when prompted so it can inspect the paired adapter and stop Android discovery before opening the serial connection.

1. Plug the OBDLink LX into the vehicle and switch the ignition on.
2. Open Android Bluetooth settings and pair OBDLink LX. It should remain listed as a paired device.
3. If you used the official OBDLink app to test it, close that app before opening Pitboard. If it continues holding the adapter connection in the background, force-stop it from Android settings.
4. Open the Pitboard dashboard and allow Nearby Devices if Android asks.
5. Pitboard searches the paired-device list for OBDLink LX or another device beginning with OBDLink, enumerates the adapter's published Bluetooth UUIDs, probes them using both secure and insecure RFCOMM, then opens the standard Bluetooth Classic SPP connection. If secure SPP fails, Pitboard automatically retries using insecure SPP.
6. The OBD Status widget automatically connects at startup. It also provides RECONNECT when disconnected and DISCONNECT when connected.

Usually not. OBDLink LX normally allows one active application connection. Close OBDLink, Torque, scan tools and other applications that may already own the adapter before starting Pitboard. If the official OBDLink app has just been used, fully close it or force-stop it before pressing RECONNECT in Pitboard.

1. Confirm the ignition is on and the OBDLink LX is fully seated in the diagnostic port.
2. Confirm OBDLink LX appears under Android's already-paired Bluetooth devices.
3. Close or force-stop every other OBD application, especially the official OBDLink app after using it for testing.
4. On Android 12 or later, verify Pitboard has Nearby Devices permission.
5. Use RECONNECT on the Pitboard OBD Status widget.
6. If it still does not connect, unplug the OBDLink LX, wait several seconds, plug it back in and allow it to boot, then press RECONNECT again.
7. If necessary, reboot the Android device. The official OBDLink app is useful as a hardware test, but close it again before returning to Pitboard.

Pitboard Studio includes a broad SAE Mode 01 catalogue for standard engine, emissions, temperature, pressure, fuel, oxygen-sensor, torque and related data. A vehicle does not necessarily support every standard PID. Pitboard should only display a value when the connected vehicle and adapter actually provide it.

Manufacturer-specific signals are kept separate from the standard SAE catalogue because formulas, module addresses and availability differ between brands and models. Pitboard is designed so validated extended PID packs can be added without pretending they are universal signals.

Where the widget supports unit conversion, select the desired units in its properties. Examples include MPH or km/h and Fahrenheit or Celsius. The numeric value and scale should be converted rather than simply changing the printed unit label.

Yes. Motion-oriented widgets can use compatible built-in accelerometers, gyroscopes and rotation sensors. Availability and quality depend on the Android hardware. Mounting angle, vibration and sample rate all affect the result.

Yes. Pitboard is designed to support external motion sensors such as compatible WitMotion hardware. USB or serial connections are normally preferable when the Android device supports them because they avoid Bluetooth contention and usually provide predictable startup behaviour.

Whenever a dashboard contains an accelerometer-dependent widget, Pitboard Studio automatically adds an Accelerometer Calibration control. Mount the tablet exactly as it will be used in the vehicle before calibrating. The tablet does not need to be perfectly vertical or perfectly flat because calibration treats its current installed angle as the vehicle's zero reference.

1. Park the vehicle and keep it stationary. Level ground is preferred.
2. Make sure the tablet is firmly mounted in its normal driving position.
3. On the running dashboard, tap CALIBRATE.
4. Keep the vehicle and tablet completely still while the control shows KEEP STILL.... Pitboard averages approximately 25 live accelerometer samples, about half a second at the normal 50 Hz update rate.
5. When the control changes to CALIBRATED, the current mounted position is treated as 0° pitch and 0° roll. Pitboard also removes the stationary gravity component from the vehicle-relative G axes and clears the previous scatter trail and motion peaks.

Use RECALIBRATE any time the tablet or mount is moved, the mounting angle is changed, the device is switched between screen-facing-driver and screen-facing-up positions, or the G-force / pitch / roll readings no longer sit correctly at rest. Calibration is intentionally established again after the dashboard app is restarted.

No. Pitboard is a vehicle information and driver-reference platform. Sensor accuracy depends on the vehicle, ECU update rate, adapter latency, sensor calibration, mounting and Android hardware. Use appropriate calibrated instrumentation when a certified measurement is required.

Pitboard Studio is the browser-based dashboard editor. It lets you choose a target display profile, place widgets on the canvas, adjust their properties, save projects online and build Android dashboard packages through the Pitboard builder.

Yes. Use one of the built-in profiles or define a custom width and height for the target display. Verify the physical Android device resolution and usable application area before finalising a dashboard.

Pitboard Studio is designed around analog and digital gauges, LED bars, live graphs, warning indicators, GPS tools, clocks, trip information, OBD diagnostics, motion displays, performance tools and other configurable dashboard elements. Availability in the shipping Android runtime can vary by development milestone.

Yes. Pitboard can change presets with a two-finger horizontal swipe on the installed Android dashboard. Swipe two fingers left to move to the next available preset and swipe two fingers right to move to the previous preset. The preset list wraps around, so swiping forward from the last available preset returns to the first.

The gesture deliberately requires both fingers to move together mostly horizontally. Pinch gestures, strongly vertical movement and touches that begin on buttons, sliders, text inputs or other interactive controls are ignored. Normal one-finger taps and control operation are unchanged.

Preset changes use a short slide-and-fade transition so the direction of the page change is visible without slowing the dashboard. The Preset widget does not need to be visible for the gesture to work. In Pitboard Studio, use Preset Swipe: ON/OFF beside Grid and Snap to enable or disable the gesture for that dashboard. It is enabled by default for new dashboards.

Sign in, open Pitboard Studio and use Save Online. The project appears under My Dashboards, where you can rename it, assign it to a vehicle, duplicate it, download a portable project file or reopen it in Studio.

Each online save can advance the stored revision so the account retains a history of the dashboard project rather than treating every save as an unrelated file. Revision history is intended to make ongoing dashboard development safer.

Build APK sends the current Pitboard project to the private Android builder, packages the supported runtime and produces one signed Android APK for the selected project and screen profile. When the build completes, Save APK downloads that file. Pitboard also provides a private temporary browser-install link for convenient installation on the target Android device.

No. PBS builds a single standalone Pitboard APK for the target Android device. There is no separate Pitboard companion app to download, install or keep in sync with the dashboard APK.

No. Pitboard is being built in staged milestones. Some Studio controls describe the intended production feature before every Android runtime path is complete. The project deliberately separates editor work, backend work and live Android verification so unfinished pieces are not presented as proven vehicle functionality.

Daily Driving and Race sessions have different jobs. Daily Driving is intended for longer recordings where file size, heat and battery use matter, while Race is intended for shorter sessions where motion detail and timing analysis matter more.

Daily Driving defaults to 5 samples per second and can be set from 1-10 Hz. Race defaults to 20 samples per second and can be set from 1-50 Hz. Pitboard enforces those maximums in the installed Android runtime as well as in Studio.

No. The logger rate controls how often Pitboard writes a row. It cannot make the underlying source update faster. A GPS receiver producing 5 or 10 fixes per second, or an OBD value that the ECU and adapter update more slowly, still has that real source rate. Logging faster records the newest available value at each logger interval. The analyser reports observed channel rates and gaps so you can see what was actually delivered.

The Android dashboard stores CSV files in its private external Documents area under PitboardLogs. Daily files use names such as Pitboard-Daily-YYYYMMDD-HHMMSS.csv; Race files use Pitboard-Race-YYYYMMDD-HHMMSS.csv. Pitboard remembers the newest log so it can be opened again after the logger has stopped or the dashboard has been reopened.

After at least one log has been saved, the Data Logger enables OPEN LAST LOG and EMAIL LOG. Open Last Log launches the built-in Pitboard Race Analysis view and loads the newest CSV. Email Log opens Android's share/email chooser with that CSV attached, so you can send it to yourself, a tuner, engineer or another computer without hunting through Android storage folders.

Pitboard Race Analysis is the Pitboard-branded version of the Dually Studio Race Analysis tool. It can open normal Pitboard CSV logs and compatible legacy Dually session logs. The tablet and desktop versions use the same analysis front end so the workflow and calculations remain consistent.

Features include GPS route replay, linked telemetry graphs, synchronized cursor readouts, second-log comparison, closed-circuit lap timing, point-to-point run timing, user-drawn start/finish gates, braking-zone review, channel minimum/mean/maximum statistics, observed sampling-rate and gap reports, and CSV/JSON exports. Available channels depend on what the original log actually recorded.

Yes. The Pitboard repository includes the standalone Pitboard Race Analysis desktop source. Windows builds produce an installer and portable EXE. The Mac build targets Apple-silicon Macs and produces a DMG and ZIP. The analyser works locally; opening a CSV does not upload the telemetry to Pitboard.

Yes. In Pitboard Race Analysis choose Open data log. Android opens its document picker so you can select another CSV accessible to the tablet. The desktop versions use the normal Windows or macOS file picker.

The analyser is only as accurate as the recorded sources. GPS lap and run times are interpolated from GPS fixes and are not transponder timing. OBD values are limited by ECU and adapter update rates. Motion data depends on the phone/tablet or external sensor, mounting rigidity, orientation and calibration. Use the channel-quality page to inspect actual rates and gaps before drawing conclusions from a session.

Acceleration timers such as 0-60 MPH, 1/8 Mile, 1/4 Mile and Custom Speed Timer need a way to arm, manually start and reset a run. When you add the first performance timer to a dashboard page, Pitboard Studio automatically adds one Performance Controls widget if that page does not already have one.

You do not need a separate control widget for every timer. One Performance Controls widget controls all performance timers on the current dashboard page. You can move and resize it like any other widget.

ARM prepares the performance timers for an automatic launch. Pitboard first shows KEEP STILL while it establishes a stationary accelerometer baseline. When the baseline is ready, the status changes to ARMED. Launch normally and Pitboard starts the timer from the detected acceleration event.

START begins the performance timers immediately and is useful for a manual test or troubleshooting. RESET clears the current performance results and the current-session maximum-speed value so the next run starts from zero.

Performance timers always start in READY when the dashboard opens. They do not auto-arm and they do not react to vehicle or tablet movement until you press ARM. This prevents moving or handling the device during startup from accidentally starting a run.

If the timer stays ARMED or never detects the launch, check these items:

1. Do not use Auto Detect while troubleshooting. In the performance widget's sensor-source setting, explicitly select the tablet or phone sensors when you are using the device's built-in accelerometer. This removes source-selection ambiguity.
2. Press ARM and keep the vehicle and device still until KEEP STILL changes to ARMED. Pitboard collects a short stationary baseline before it will accept a launch.
3. Make sure the phone or tablet is mounted rigidly. A loose mount, vibration or moving the device during the baseline can keep Pitboard in KEEP STILL or produce a poor launch reference.
4. Confirm the selected phone/tablet actually has a working accelerometer and that Android is providing live motion data.
5. The automatic launch trigger looks for a clear acceleration change. If you want to verify the rest of the timer immediately, press START manually.
6. Launch detection starts the clock, but the timer still needs a valid selected speed source to finish the run. Verify GPS and/or OBD speed is updating for 0-60 and other speed-based tests.

For the most repeatable phone/tablet setup, explicitly choose Tablet/Phone Sensors, use a rigid mount, remain still until ARMED appears, and only then launch.

Nothing is armed automatically at dashboard startup. After you press ARM, Pitboard collects approximately 50 stationary accelerometer samples to establish a baseline. Once the status changes to ARMED, it watches for a launch impulse from the mounted device. A confirmed acceleration change starts all armed performance timers together. The timer then uses the configured live speed source for speed targets, elapsed distance and trap speed.

The detector is designed to tolerate different phone and tablet mounting orientations, but a solid mount and a clean stationary baseline are still important.

Accuracy depends on GPS update rate, antenna placement, OBD latency, sensor quality, mounting, calibration and the timing algorithm. Use Pitboard performance tools for driver reference and analysis, not as certified drag-strip or official competition timing equipment.

Sky view, antenna placement, buildings, trees, tunnels, weather, Android hardware and time since startup all affect GPS quality. Wait for a stable fix before relying on lap timing, speed testing or location-based statistics.

Add GPS Lap Timer from the Performance section in Pitboard Studio. Choose a predefined US track from Track / Layout, or choose Custom Start / Finish. For a predefined track, Pitboard loads its stored start/finish location automatically. For Custom mode, wait for a good GPS fix, stop at the start/finish line with the vehicle pointing in race direction, and tap SET LINE. Pitboard stores that custom position and direction for future launches of that dashboard.

Tap ARM before the session. Crossing the selected start/finish gate starts the timer. Each subsequent valid crossing completes the current lap and immediately starts the next one. LAST, BEST and the lap count update automatically. Best lap is stored separately for each selected track. RESET clears lap results but keeps the selected track or saved custom start/finish line. Gate width and minimum lap time are adjustable in Studio to help reject GPS jitter and false crossings.

When Show track map / live GPS position is enabled, predefined tracks with stored geometry show the circuit outline directly in the lap-timer widget. The start/finish is marked in red and the tablet's current GPS position is shown as a green dot. Tracks without a stored outline, and Custom Start / Finish mode, use a live GPS breadcrumb trace so the map builds as the vehicle moves.

LAST is the most recently completed result. BEST is the best completed result for the applicable session or stored context. Exact persistence depends on the individual performance widget and runtime implementation.

The selected inertial source measures longitudinal and lateral acceleration. For meaningful results, mount the sensor rigidly, orient its axes correctly and calibrate while stationary on level ground. Vehicle pitch, vibration and sensor filtering can affect the displayed value.

Use acceleration, braking and lap-timing features only in a legal controlled environment or closed course. Do not interact with dashboard controls while driving on public roads.

My Garage stores vehicle-specific information such as year, make, model, VIN, odometer, engine, transmission, fluids, filters, tire sizes, maintenance tools and notes. Dashboards can be assigned to a vehicle so projects and ownership records stay organised.

Community dashboards are user-shared Pitboard designs. The owner keeps the original dashboard. Another signed-in user can add an independent copy to My Dashboards without being able to edit the original owner's project.

1. Save the dashboard online.
2. Open My Dashboards.
3. Open the dashboard's details.
4. Select Share with Community.

You can later remove the dashboard from Community without deleting it from your account.

Yes. Signed-in users can upload supported PNG, JPEG or WebP images to the Community wallpaper and artwork sections. Only upload material you own or have permission to distribute. Do not upload personal documents, credentials or private vehicle information.

The user who shared an item can remove their own content. Pitboard administrators can remove Community material when necessary for moderation, safety, copyright or platform housekeeping.

Everyone can read the forums. Signed-in members can start discussions and reply. Users can edit or remove their own content, while administrators can pin, lock, edit and remove forum content through Forum Moderation.

Do not post passwords, private keys, payment credentials, security tokens, home addresses, full diagnostic exports containing personal information, or other secrets. Remove private information from screenshots and attachments before posting to the Forums or Community.

The current account backend stores Pitboard account, Garage, dashboard, forum and Community metadata in private server storage protected from direct web access. Sensitive SMTP credentials are encrypted before storage.

The platform is designed for subscriptions and paid feature entitlements, but billing and licensing modules should only be considered active when their Admin status explicitly reports that they are configured and ready.

Include the Pitboard or Pitboard Studio version, Android version, device model, OBD adapter model, vehicle year/make/model when relevant, affected widget or feature, exact error text, and clear steps to reproduce the problem. Screenshots and logs are useful after private information has been removed.

Use the Bugs and Known Issues forum category. That keeps reproducible reports, workarounds and confirmed fixes together instead of scattering them through unrelated discussions.

Use the Contact page for account, billing or support questions that should not be posted publicly.