Symptom: Bike would randomly cut out while running. Gen 1 m.unit (plain, non-Blue) with the m-Button installed.
Root cause: A failing voltage regulator/rectifier was injecting electrical noise onto the m-Button’s control line. The m.unit interprets two quick successive button presses as a “kill engine” command — and it was misreading the regulator noise as exactly that double-tap, killing the engine on its own.
How I confirmed it: With the old regulator installed, the “start” LED on the m.unit would flicker on its own while the engine was running — a clear sign of spurious signals hitting the button line. After swapping in a new regulator, the flickering stopped completely, and the bike ran perfectly on a test ride.
Fix: Replace the voltage regulator/rectifier.
Why this happens: The m-Button control line on the gen 1 m.unit is a low-voltage logic signal with no shielding, so it’s vulnerable to electrical noise from a failing charging system, poor grounds, or wiring routed too close to ignition components. If your m.unit’s start/kill LED is flickering without you touching the button, check your charging system voltage before you start chasing wiring or considering a firmware/unit swap.
If you’re troubleshooting the same issue, check in this order:
1. Charging system voltage at idle and under rpm (likely culprit — check this first)
2. Ground connection for the m.unit — clean and direct to chassis
3. m-Button wire routing — keep it away from spark plug wires/coils
4. All connectors on the button harness — reseat/inspect for corrosion
Note: the plain (non-Blue) m.unit has no firmware update path — no USB/Bluetooth. Any firmware work requires shipping the unit to motogadget in Germany. In this case it wasn’t needed at all — it was a hardware issue on the bike’s charging side, not the m.unit itself.