Skip to main content
zerologs

zerologs/beta

Early builds, for riders who tinker

Things land here before they are finished. You get them first and see how they work; we get your bug reports. Expect rough edges, honest changelogs and nothing that writes to your motorcycle.

now in previewclosed test · Google Play

ZeroLogs for Android

Your Zero’s battery and every cell live, a ride cockpit made to be read at a glance, rides that start and stop by themselves, and the motorcycle’s own logs downloaded over Bluetooth — offline first, uploaded when there is a network.

  • Android 7.0+
  • Gen2 · Bluetooth Classic
  • read-only allowlist
  • offline queue
  • tyre sensors (BLE)
Join the test

How the data moves

Your Zero
answers reads over Bluetooth
reads only, from a fixed allowlist
ZeroLogs app
cockpit, ride recording, offline queue
HTTPS, when there is a network
zerologs.bike
rides, charges, battery health, parsed logs

Rides recorded with the app stay on the phone too, so they show offline. A ride recorded while the motorcycle is connected merges the phone’s GPS with the bike’s own readings.

On the wire (Gen2)

Bluetooth Classic, Serial Port Profile on RFCOMM channel 1, no login. Every message is one frame; a read is 20 bytes and the reply repeats its tag. Live values come from a round robin of MbbR, PwPk and DSt1–3, one request in flight at a time.

F1 F2 F4 F8start
npayload words
PwPkASCII tag
…payload (none on a read)
F8 F4 F2 F1end
CRC-32check

Every command, every reply field and a whole log download, measured on real captures: the Bluetooth protocol.

What the app may ask your Zero

One allowlist decides every frame the app can send, and it is reads only. A read that carries a payload is refused, because a payload is a parameter we do not understand.

PrVrprotocol version
GbkiVIN, make, model, part number
PwPkpack voltage, cell voltages, SoC, current, temperatures
BtStbattery state
MbbRmotor, controller, speedometer, armed and kickstand bits
DSt1–3the dash: trips, range, motor °C, error code, charge time
MbbDthe motorcycle’s log, one 256-byte block per request
BmsDthe battery’s log, the same transfer
Ecusevery controller: model year, hardware and firmware part numbers
Errsthe active fault codes
CmChonly “read from address 0”, before a log download
never sent: Upld, Hash (firmware) · every other CmCh (drive parameters, test mode, boot bank)

Gen3 will get the same treatment: read and acknowledge types only. Ride modes stay out entirely, because the same message type is written back to change a mode.

Which Zero gets what

  • S, SR, DS, DSR up to 2023 · FX, FXS, FXE
    link
    Bluetooth Classic (SPP)
    live battery
    yes
    log download
    yes
    rides
    phone + bike
  • SR/F, SR/S, DSR/X, S/F · S, SR, DS, DSR from 2024
    link
    Bluetooth LE — planned
    live battery
    later
    log download
    later
    rides
    phone
  • XB, XE, LS1
    link
    none known
    live battery
    —
    log download
    —
    rides
    phone

No Zero at hand? You can still test the ride recorder: it works with the phone alone.

What Android will ask, and why

  • Nearby devices
    Talk to the Zero you paired through Android’s own pairing dialog, and listen to tyre pressure sensors. The scan is flagged never-for-location.
  • Location — while using the app
    Only while a ride records, with a notification on screen the whole time. No background location.
  • Notifications
    A recording in progress, a log download, an upload done.

Join the test

Google lets a new app go public only after a closed test with at least 12 testers who stayed in for 14 days in a row. That is the whole reason this test exists — and why staying in matters as much as joining.

day 1day 14 → production
  1. 1

    Join the testers group

    With the Google account you use on your Android phone, press Join group. It is only a list: nobody posts in it, and only we can see who is in it.

    Open the group
  2. 2

    Become a tester

    Same Google account, accept the test. If Play says the app is not available, give it a few minutes after joining the group and reload.

    Accept the test
  3. 3

    Install ZeroLogs

    Install from Google Play, sign in with your zerologs account (or create one in the app), pair your Zero. Test builds arrive as ordinary Play updates.

    Get it on Google Play

What we ask of testers

  • An Android phone (7.0 or newer) with Google Play.
  • Stay in the test, and in the group, for at least 14 days.
  • Use it: pair your Zero, record a ride, download a log.
  • Tell us what breaks or confuses you: Menu → Feedback in the app, or the contact form. A screenshot and the time it happened help most; the app keeps a technical log you can share from Log, top right of the Bike tab.

Your data

Your Google account’s email is in the testers group, where only the group’s managers — us — and Google Play can see it. Leave the group to leave the test. What the app collects, and why, is in the privacy policy.

On the bench

Gen3 over Bluetooth LE is planned for the app. Whatever comes next lands on this page first.

Not affiliated with Zero Motorcycles, Inc.