jayecu v0.3.30

Firmware 0.4.21 (build ac9f7bf)

• Key-on is a power-on. With USB holding the ECU up, key-off used to leave every module and sensor as
  it was, and the next key-on carried on from there. Now key-off puts every module back to its power-on
  state and key-on re-reads every sensor from scratch. Only what survives a real power loss carries over:
  the tune, learned trims, knock learning and stored fault codes.
  • Found on a car: the battery terminal let go under the starter mid-crank. At key-on the start switch
    still read "pressed" for its first few samples, the start sequence took that for a press, and the
    engine cranked with nobody on the key.
• A start press has to be seen. The start button must read released with the key on before any press
  counts, with Engine Start on or off. A button already pressed at key-on (held, stuck, or stale) never
  starts a crank: let it go and press again.

Studio 0.3.30

• Manual: the start sequence chapter explains that a start press has to be seen (the button must read released with the key on first).

Firmware kits for jaytek_v1 and proteus_f7. No settings layout change from 0.4.20, so a tune comes across as it is.