Commit Graph
304 Commits
Author SHA1 Message Date
James Babcock 061f50e711 Update version to 0.6.4 2026-09-02 00:31:42 -07:00
James Babcock 76825f68a7 Flashing uses 2.2.9 as base version 2026-09-02 00:30:50 -07:00
James Babcock c7d4e7a630 Remove some prototype/unfinished features from the Watch app
Double twist gesture: I wasn't able to get this to trigger, and it
conflicted with a Wear OS builtin gesture.

Swipe left/right remapping: Some parts of the glasses UI are written to
assume that if you're using watch inputs, you have access to left/right
navigation, so letting these be remapped effectively broke them.

Tap zones: An interesting idea, but turned out to be bad UX in practice.
Swipe works much better because you're looking at the glasses screen,
not the watch, while using it.

Natural swipe toggle: Inverted swipe makes sense for touch scrolling,
but didn't make sense in this context.
2026-09-01 23:18:38 -07:00
James Babcock 984c65a90e Watch app uses ambient mode, looks correct when idle, doesn't lose taps when woken 2026-09-01 22:32:24 -07:00
James Babcock fddb6ea886 Long-press and short-then-long with a context menu open switches between context menus 2026-09-01 21:38:52 -07:00
James Babcock c364099a8c Files app: Gamma correct and dither images when viewing 2026-09-01 21:17:42 -07:00
James Babcock a72e29a04f Compass has higher sample rate, and distinguishes map north from true north 2026-09-01 14:37:09 -07:00
James Babcock eb8a863222 Debug speed metrics include bytes/frame 2026-09-01 11:57:13 -07:00
James Babcock b1493a353d Context menus are centered and include window title 2026-09-01 00:58:28 -07:00
James Babcock 5158bc86ff Version 0.6.3 2026-09-01 00:38:48 -07:00
James Babcock 85508b87ca Add "Show BLE bandwidth usage" option to developer settings 2026-09-01 00:33:07 -07:00
James Babcock 641e8e322e Ehpk app permission prompts scroll if too long 2026-08-31 23:59:00 -07:00
James Babcock 052398d401 Update EvenHub compatibility layer to support new functionality (context menus and some other things) from 0.0.14 2026-08-31 23:42:22 -07:00
James Babcock 216dc59255 Add support for short-then-long gesture to watch input and simulated inputs 2026-08-31 20:42:49 -07:00
James Babcock 6483d00647 Add support for the new short-then-long-press gesture 2026-08-31 20:31:08 -07:00
James Babcock 596c767446 Update custom firmware to one based on 2.2.9
Based on g2flash commit 784846b6fab960bfed8994cbdec8d97d24988b0f.
2026-08-31 14:42:00 -07:00
James Babcock a37dae0fb4 Fix typo in changelog 2026-08-30 23:59:46 -07:00
James Babcock 3150f1e2bb Version 0.6.2 2026-08-30 23:57:23 -07:00
James Babcock b0238df174 Simulated watch and ring touchpads don't have arrow-buttons; simulated ring has decorative markings 2026-08-30 23:54:51 -07:00
James Babcock d9baf678fc Changelog entry for terminal activity indicator branch 2026-08-30 23:50:58 -07:00
James Babcock 9fbb327e31 Merge branch 'terminal-activity-from-output' 2026-08-30 21:27:15 -07:00
James Babcock e98f19d7e4 Add "Use microphone control" option to developer settings 2026-08-30 21:18:32 -07:00
James Babcock 8a86cf28e1 Fix issue where you could want up without the official Even font extracted, if you skipped onboarding 2026-08-30 20:38:14 -07:00
James Babcock 54005ae95a Preview mode uses phone mic 2026-08-30 20:04:33 -07:00
James Babcock 01527adda9 Simulated Ring input is touchpad-style 2026-08-30 19:50:37 -07:00
James Babcock 602f66f15b Make preview-only mode work 2026-08-30 19:17:30 -07:00
James Babcock 2d45b65098 Scripts to push/pull config take arguments 2026-08-30 16:28:48 -07:00
James Babcock c1d70abf5e Update version to 0.6.1 and update CHANGELOG 2026-08-30 15:36:07 -07:00
James Babcock 7ebf921299 Fix a race condition that sometimes caused apps to skip their first paint after launch 2026-08-30 15:35:19 -07:00
James Babcock ccd28b7ac9 Move Roam settings out of the Settings app and into the Roam app itself 2026-08-30 15:34:33 -07:00
James Babcock cd25ec60f1 Calendar app shows day-of-the-month in its icon on the launcher and sidebar 2026-08-30 15:16:49 -07:00
James Babcock 061b2eb215 Update the launcher, Files app and builtin games to better handle watch swipe gestures 2026-08-30 15:03:53 -07:00
James Babcock 0eddd862ad Update newest-recognized-firmware-version to 2.2.9.22 2026-08-30 14:19:20 -07:00
James Babcock 774c534c79 Merge commit 'refs/pull/20/head' of https://github.com/jimrandomh/faceclaw into dev 2026-08-30 14:11:58 -07:00
James Babcock 80d688dd4e Move and rename DashboardInputEvent->InputEvent 2026-08-30 13:02:44 -07:00
James Babcock 3e8be93833 Add a settings import/export receiver
If you install a signed release build and want to switch to an unsigned
debug build, that involves an uninstall and reinstall, which by default
will lose your configuration. Modify scripts/pull_config.sh and
scripts/push_config.sh so it works on release builds, not just debug
builds, and update README.md to tell you to export your config before
doing this kind of upgrade.
2026-08-30 12:25:06 -07:00
James Babcock f4c43090f5 Add a CHANGELOG file 2026-08-30 11:15:42 -07:00
Chris Lee ec12a4845b Fix onboarding firmware-check: kind mismatch broke every real result
classifyOnboardingFirmware() (firmware-compat.ts) returns kind values of
"custom" | "flashable-stock" | "newer-stock" | "unknown", but
applyClassification()'s switch (onboarding-firmware-check-view-model.ts)
checked for "flashable" / "newer" -- names borrowed from the unrelated
CheckPhase type used a few lines later via setPhase(). Since kind was
typed as plain string, nothing caught the mismatch at compile time.

Effect: any device that successfully reported a firmware version (stock,
flashable-stock, or newer-stock alike) fell through to the switch's
default case and showed "Connected, but couldn't read a firmware
version" -- the hard-block message meant for when the probe gets no
data at all. Confirmed on real hardware (glasses on 2.2.9.22): the BLE
probe read the version correctly every time, logged it correctly, and
the UI still reported it as unreadable.

Fix: match the real OnboardingFirmwareKind strings, and tighten the
parameter's type from `string` to `OnboardingFirmwareKind` so this
category of typo fails to compile instead of failing silently.
2026-08-30 10:19:35 -04:00
James Babcock d542acb891 Merge branch 'main' of https://github.com/jimrandomh/faceclaw 2026-08-30 00:42:27 -07:00
James Babcock 6c46f2f7cc EvenHub app stores login token instead of password 2026-08-30 00:35:55 -07:00
James Babcock ac1529d397 Bump version number to 0.6 2026-08-29 23:38:40 -07:00
James Babcock f6d4c4365f Update firmware to include microphone-config patches 2026-08-29 20:22:42 -07:00
James Babcock e1c4628566 Merge branch 'main' of https://github.com/jimrandomh/faceclaw into calculator 2026-08-29 20:13:48 -07:00
James Babcock 17d5f75490 Fix aspect ratio on screenshots 2026-08-29 15:24:11 -07:00
James Babcock 4415c645f7 Add sync-site script 2026-08-29 15:21:53 -07:00
James Babcock 20677116ca Add a GitHub Pages website 2026-08-29 15:02:22 -07:00
James Babcock aebb88f917 Small fixes in README and build script wiring 2026-08-29 13:26:01 -07:00
James Babcock 63b7a13df1 Gate R1 direct connection behind a dev setting
<details>
<summary>Prompts Used</summary>
Currently we receive user input events from the R1 ring mainly via the G2 glasses, which have their own connection to ring, and we also try to connect to the ring directly; but the direct connection currently winds up not workign reliably. Let's add a "Ring connection mode" to the Developer section of the Settings app, with options "Only via glasses" (new default) and "Direct". If the "Only via glasses" option is selected, we don't open a bluetooth connection to the ring at all.

> Done. Build + typecheck pass.
>
> **Changes:**
>
> - `app/ui/dashboard-settings.ts:393` — new `ringConnectionModeSetting` (`ConfigSettingEnum<RingConnectionMode>`), values `"glasses"` (default, displayed "Only via glasses") and `"direct"`, stored under `developer.ringConnectionMode`.
> - `app/ui/dashboard/settings-menus.ts:182` — added it as the first row of the Developer section.
> - `app/g2/dashboard-controller.ts:988` — `connect()` now computes `ringAddress = mode === "direct" ? addresses.ring : ""` and passes that to `FaceclawCommunicatorBridge` (and into the connect log line).
>
> The gate works by handing the Java communicator an empty ring address: `FaceclawBleCommunicator.hasRingAddress()` then returns false, so `tryConnectRing`/`shouldAttemptRingConnect`/the teardown `disconnect(ringAddress)` all short-circuit — no GATT connection to the ring is ever opened, and the retry loop never fires. Gestures still arrive over the glasses' own link to the ring, unchanged.
>
> Since the mode is read at connect time, changing it while connected takes effect on the next connection; the setting's description says so. If you'd rather it apply live (drop/raise the ring link without cycling the glasses), that needs a small new Java method on the communicator — say the word and I'll add it.
</details>
2026-08-29 11:41:49 -07:00
James Babcock 268fe24093 Merge pull request #19 from jimrandomh/fix-18
Fix mic drop issues
2026-08-29 10:17:54 -07:00
James Babcock 756ee4e63b Fix mic drop issues
<details>
<summary>Prompts Used</summary>
Investigate and fix the bug in https://github.com/jimrandomh/faceclaw/issues/18

> Fixed. Here's what was going on and what changed.
>
> ## Root cause
>
> The issue's diagnosis was right, and the underlying flaw is a bit broader than the holder set: **`captureHolders` is phone-side bookkeeping, but the mic enable lives in the glasses' EvenHub session.** That enable dies — silently, from the phone's point of view — on a transport drop, the charging case, an EvenHub screen-off suspend, or a refused enable (`startG2AudioCapture` returns false when the display path isn't warm, and the Java worker then exits while the JS side still believes it started).
>
> `acquireCapture()` answered "is the mic running?" from the holder set, so a single stranded holder (a Transcribe window that was open when the link dropped) made every later request — wakeword assistant included — return early onto a stream that no longer existed, for the life of the process.
>
> The reported repro hits it via `resumeEvenHubSession()`, which resets `audioCaptureActive` and replays the prelude without re-enabling the mic; nothing on either side cleaned up.
>
> ## The fix
>
> **Java** — expose the real state of the stream instead of inferring it:
> - `FaceclawBleCommunicator.isAudioCaptureActive()` (`App_Resources/.../FaceclawBleCommunicator.java:363`) — true only while the session is up, not shut down, and the enable has been acked. Every teardown path already clears that flag.
> - `FaceclawVoiceController.isCapturing()` — `started` plus the communicator's view, with a lock-guarded `audioStarted` so the mic-warmup window doesn't read as dead.
>
> **`app/native/voice-control.ts`** — the bridge now asks `micIsLive()` rather than trusting the set, and tears a dead capture down before starting a new one. Added `handleSessionEnded()` (parks live holders, drops the local state) and `resumeCapture()` (restarts them on the next session); `releaseCapture`/`stop` clear the parked set. The raw-PCM tap for EvenHub mic apps had the identical staleness bug (`if (this.rawActive) return true`) and is covered the same way.
>
> **`app/g2/dashboard-controller.ts`** — wired the two session boundaries: any phase leaving `connected` parks the capture, and the first composited frame of the next session resumes it (a rendered frame is exactly the signal that a mic enable will be accepted). The screen-off EvenHub suspend is now deferred while a capture is held, so the screen timeout no longer kills a live transcription; a capture that races the suspend is parked by the same path.
>
> So Transcribe recovers on its own after a reconnect instead of sitting on a dead "Listening…", and the wakeword assistant is no longer blocked by anything left behind.
>
> ## Verification
>
> `./build.sh` (Java + webpack) clean, `tsc --noEmit` clean, `npm test` 61/61. Not committed.
>
> The behavior is all glasses-session state, which the test harness (pure modules only) can't reach, so it needs hardware. I wrote `notes/voice-capture-session-resume.md` with the five checks that matter — most importantly: Transcribe open → walk out of range → return → "Hey Even" should now get audio, and Transcribe should resume itself.
</details>
2026-08-29 10:16:52 -07:00