enricobuehler a7d4a93ff2 fix(gamepad/android): make the exit chord usable again — shorter hold + on-screen hint ...

The Select+Start+L1+R1 close-stream chord read as broken after 48933dc4
changed it from an instant quit to a 1.5 s arm-and-hold: a normal quick
press did nothing and there was no on-screen cue that a hold was now
required. Keep the accident-prevention hold (an errant brush of the four
buttons still shouldn't kill a session), but make it usable:

- Shorten EXIT_HOLD_MS 1500 -> 1000 ms — still rejects a brush, feels
  responsive.
- GamepadRouter gains onExitArmed(Boolean): fires true when the chord
  completes and the countdown starts (once per cycle, past the
  pendingExit guard), false on an early release or when the timer
  elapses.
- StreamScreen shows a "Hold to quit…" pill (top-center) while armed, so
  the hold is discoverable; the callback is detached in onDispose before
  router.release() so its disarm can't poke Compose state during
  teardown.
- MainActivity: drop the now-stale "~1.5 s" dispatch comment.

Verified on this Mac: :kit + :app compileDebugKotlin clean; Android lint
clean for all three touched files (the kit lint baseline errors are
pre-existing, unrelated). On-glass on a real phone + pad still owed (the
1 s hold firing the exit, early-release cancelling, the hint showing /
hiding) — per the Android-input-regressions-only-show-on-hardware
history, and the original hold path was never exercised on a device.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-07-15 18:25:10 +02:00

..

kotlin/io/unom/punktfunk/kit

fix(gamepad/android): make the exit chord usable again — shorter hold + on-screen hint

2026-07-15 18:25:10 +02:00

AndroidManifest.xml

feat(android): scaffold the native Android client (Rust-heavy JNI bridge)

2026-06-15 01:38:35 +02:00