Last verified: 2026-08-15
R-Speedo is a PWA and Android EV dashboard that uses phone GPS and, when available, Bluetooth telemetry from supported motor controllers, vehicle modules, BMS devices, and sensors.
No. GPS-only mode supports speed, route, distance, basic trip/report features, and GPS-based Dragger attempts. Bluetooth is required for controller, battery-cell, current, fault, tire-pressure, and other hardware telemetry.
Some dashboard and locally stored trip features can continue without a live connection. Maps, route search, account/license refresh, live riders, charging-station/workshop updates, analytics upload, leaderboard sync, and other server-backed features require connectivity.
R-Speedo includes integrations for Votol and Fardriver controllers, read-only VESC controller telemetry, Gesits read-only telemetry, the independent Polytron ESP32 Votol CAN module path, JK/Daly/ANT/JBD BMS devices, supported BLE TPMS formats, and Cervo clock/navigation mirroring. Exact compatibility depends on model, firmware, protocol, adapter, browser, and operating system. See compatibility.
There is an experimental Polytron profile for an external ESP32 Votol CAN module that sends BLE JSON as Votol_BLE. It is independent of Polytron, and writing controller settings is unavailable.
The PWA runs from a browser and can be installed where browser support allows. Bluetooth requires Web Bluetooth support, and background execution is limited by the browser and operating system. The Android APK uses native Bluetooth, background recording, file handling, start-on-boot, account/offline-license integrations, and an Android telemetry widget.
Safari can be used for GPS-only web features where location support is available, but Safari does not provide native Web Bluetooth telemetry. Bluefy or another WebBLE browser may work as an experimental user-tested workaround. A native iOS test/sideload target exists, but there is no public native iOS release.
Layout 8 Dragger is a GPS-based performance mode. It measures split times, compares against personal best or a rival ghost, syncs eligible runs to a leaderboard, and exposes public evidence without raw coordinates. It is not official race timing equipment. See reports and data.
Layout 9 compares paired local road pulls and can analyze time, energy, voltage sag, temperature, and minimum wheel-power/torque estimates when enough data is available. Readiness, cooldown, road, wind, slope, vehicle configuration, GNSS, and telemetry quality affect the result. It is not a chassis dynamometer.
Layout 10 lets users arrange telemetry, media, map, camera, image, text, and icon widgets on up to five local portrait or landscape canvases. Canvas configuration can be exported or imported as JSON; locally selected image assets remain local unless the user exports or shares them.
For a supported Alva Cervo BL-CERVO head unit, R-Speedo can synchronize time and mirror Layout 6 navigation. This integration does not edit the vehicle controller.
The R-Speedo hardware Shop is available only in Indonesia. Current products, availability, IDR prices, and the WhatsApp handoff are shown by the app, so copied listings may become outdated.
The Android APK can update a home-screen widget with a compact ride, parked, charging, completed-charge, or last-status snapshot. It keeps a last-known-good view instead of replacing it with invalid data.
When R-Speedo has enough battery/charging information, it can show an active or completed charge session with SOC, ETA, energy added, estimated cost, voltage, temperature, and cell-delta warnings. Accuracy depends on the telemetry source and configuration.
APK access is managed through an R-Speedo account and purchase/activation status. Pricing and payment methods can vary, so use the current information shown in the app instead of relying on a copied price.
EV analytics uses an anonymous app-device identifier with privacy guards and reduced location-derived metrics. Web/PWA and Android controls can differ, so review the current in-app consent text. Analytics is separate from optional live-rider location sharing. See privacy.
Do not treat it as the only safety-critical instrument. Phones, GPS, Bluetooth, background execution, configuration, and third-party hardware can fail or drift. Follow manufacturer limits and local regulations.
The displays may use different sensors, calibration values, sampling intervals, filters, capacity settings, start detection, or estimation models. See the EV telemetry guide.
Open a GitHub issue with the exact model, revision, Bluetooth name, platform, and observed result. Do not include credentials, license tokens, raw traces, or location history.