# Lappy v0.0.5

The USB/battery icon, voltage and USB? text are removed from the status bar. The current power policy is manual PWR shutdown; unplugging USB simply continues on the battery. There is no ignition/USB-loss calculation, grace countdown or automatic source-based shutdown.

Battery hold is enabled during startup. Hold PWR for one second to stop new measurements, save settings and Drag PBs, record the trip summary, and drain/sync/close the recording. After saving and button release, Lappy blanks the display and releases battery hold. BOOT retains mode/settings controls. PWR held during startup is ignored until its first release, and short PWR presses do nothing.

Saving runs in a worker and displays SAVING… / Please wait. If PWR is still held, successful completion shows SAVED / Release PWR to switch off. A failed settings/PB/recording save keeps battery hold on and shows SAVE FAILED / Hold PWR to retry. Active Drag attempts are invalidated; retained completed PBs are preserved. The SD writer acknowledges actual close/unmount, rather than releasing power after an arbitrary deadline. A missing card permits settings/PB save, but cannot provide a session recording.

If USB remains connected, it can keep the electronics powered after recording closes and the screen goes blank. A fresh long PWR press restarts in that situation; battery-off startup uses the physical PWR button. The console stop command follows the same save path. Diagnostic battery voltage is retained without being used as a shutdown trigger. Dragy battery percentage remains in Diagnostics.

The native simulator adds PWR — hold and the P key and shares the debounce/save orchestration. Tests cover startup/short/long presses, save ordering, active runs, preserved PBs, duplicate requests, held-button completion, save failures, retries, screen-off and restart. All seven Drag tests, manual-calendar tests, nine Python tests, both firmware builds and 54 UI renders pass. Physical battery handover, PWR wiring and real storage shutdown remain to be verified on arrival.

Previous v0.0.1–v0.0.4 archives remain unchanged. The current roadmap/design brief supersede their power policies. Track timing remains a preview.