Commit Graph
292 Commits
Author SHA1 Message Date
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
James Babcock fe28a6de4b Add missing scripts/before_build.sh 2026-08-28 21:23:22 -07:00
James Babcock 6cd7d5fff9 Watch display shows if glasses are charging or silent mode 2026-08-28 18:36:35 -07:00
James Babcock ed8302bc6b Refactor build scripts 2026-08-28 12:02:59 -07:00
James Babcock f858f10ce2 Wear watchface design
Makes the button-row appear and disappear with a slide-in/out gesture.
Rearranges the other UI elements for a more watchface-like view.

<details>
<summary>Prompts used</summary>

In faceclaw/wear, we have an Android Wear watch app which can be used as a glasses controller. Currently, its UI is a bit chaotic: we have a bottom row of buttons, the time, a foreground-window title, some help text, and a ring of indicators. The core interaction is tapping, double tapping, long tapping, and swiping (which have the same effect as on the R1 ring), which aren't location sensitive except that they can't hit the row of buttons. There is also a crown, which can be rotated as a prev/next input.

First, let's make a crown-direction setting (in the Watch section of the on-glasses Settings app), which is a toggle that can swap which crown-rotation direction is considered next vs prev. The default will be off, which will be opposite the direction that is currently default.

Next, we will make it so that the row of buttons is hidden by default. They will slide in from the bottom when the user swipes up from off-screen (distinguished from a swipe-up gesture sent to the glasses by the starting position of the swipe). They will slide out with a swipe down starting from anywhere below the top of the buttons (distinguishing from a swipe-down gesture sent to the glasses by the starting position of the swipe).

Next, we will remove the circle and four arrows; change the time from being small, curved and at the top of the screen to being larger, straight and vertically centered. We'll delete the gesture current hint ("● select  ●● back"), and take the current foreground-window display (which is currently either "Disconnected", "Screen off", or an app title) and place it below the time. When the current state is "Screen off", it will display as "●● Wake". We'll then make it so that when the glasses screen is off, all gestures except for double tap (which wakes the screen) are ignored.

gpt-5.6-Sol:

> Implemented the Wear controller redesign.
>
> - Added on-glasses Settings → Watch toggle: “Clockwise crown = next.” Default off maps clockwise to previous, opposite the former default.
> - Replaced the obsolete “Watch input wakes display” setting.
> - Bottom buttons are hidden initially, slide up from a bottom-edge swipe, and dismiss with a downward swipe anywhere in the tray.
> - Removed the ring, arrows, and gesture hint.
> - Added a large centered straight clock with foreground status beneath it; screen-off status is now “●● Wake.”
> - While the glasses display is off, non-double-tap gestures are ignored locally and defensively on the phone.
> - Updated faceclaw/wear/README.md and faceclaw/wear/PROTOCOL.md.
>
> Verification:
>
> - TypeScript type-check passed.
> - All 59 tests passed.
> - git diff --check passed.
> - Wear Gradle compilation could not start because the sandbox blocks Gradle’s local lock socket/cache access.

</details>
2026-08-28 10:28:37 -07:00
James Babcock f3ad55ca3d Merge branch 'calculator' of https://github.com/kalanihelekunihi/faceclaw into calculator 2026-08-26 00:49:20 -07:00
James Babcock b9e5e56ac8 Refine the UI of the main screen bottom area
<details>
<summary>Prompts Used</summary>
Thanks. Next up, we're going to work on the main screen bottom input area.

We will have a distinct state for keyboard-input mode (ie when you select a setting with a text field). While in that state, we'll hide other inputs (ie the simulated watch and ring input buttons) and put the text input (which is currently a modal on top of the screen preview) in the space below the screen preview. If it doesn't fit, given the reduced screen height while the keyboard is open, it will overlap the screen preview. When leaving a text-input screen, we will close the keyboard.

When the keyboard isn't open, we will have a tab bar-style row of buttons underneath the screen preview, with three tabs: Settings, Watch, and Ring. The Settings tab will have brightness and screen size options (we will drop the options in the Phone Display section of the Settings app which would hide these settings). The Ring tab will have a set of buttons corresponding to simulated R1 ring inputs (the main page has recently had this, but currently doesn't seem to). The Watch tab will have a simulated watch face for simulated Android Wear watch inputs (this is currently on the main page).

> Done — builds and typechecks cleanly. Here's the shape of it:
>
> **Keyboard-input mode**
> - When a text setting becomes active, the whole tabbed controls area collapses (`controlsVisibility` on the `rc:remote-controls` instances in both orientations), leaving the space below the preview for the editor.
> - The text editor overlay is now anchored to the **bottom** of the page instead of the top. Combined with the keyboard resizing the page, it sits in the space below the preview and only rides up over the preview when the keyboard leaves too little room. To make that resize behavior deterministic, I added `android:windowSoftInputMode="adjustResize"` to the activity in the manifest (previously unset, so Android picked pan-vs-resize itself; note this applies app-wide, which is generally the better behavior for the other pages with text fields too).
> - When the glasses navigate away from the text-input screen (`activeTextSettingId` goes null), the page now dismisses the soft keyboard, and the tab area comes back.
>
> **Tab bar** (`remote-controls.xml` rewritten)
> - Three tabs — Settings, Watch, Ring — as a segmented row of buttons; the selected tab is remembered across page navigations (module-level, in-memory), defaulting to Watch.
> - **Settings**: screen-size picker (labeled row) and the brightness slider + Auto switch, now always shown.
> - **Watch**: the simulated watch face unchanged (touchpad with d-pad overlay and legend) plus the Back/Menu row.
> - **Ring**: a 3×2 grid of larger labeled buttons for the R1 inputs — ▲ Up, ▼ Down, ● Click, ●● Double, ‒ Hold, and Hey Even (the wakeword, which moved here from the old shared action row since it's a ring-scheme input).
>
> **Settings app**: `showBrightnessControlSetting` and `showScreenSizeSetting` are deleted outright (definitions, menu items, and the view-model visibility getters). The Phone display section keeps Preview color and Touch mirror. Users' old stored values for the deleted keys are simply orphaned, which is harmless.
>
> Things worth checking on hardware: the editor's position with the keyboard open (especially on a short screen where it should overlap the preview), keyboard dismissal when backing out of a text setting on the glasses, and dark-mode contrast of the tab buttons (I inverted the selected/unselected colors for `.ns-dark`).
<hr>
Keyboard-open view: Looks good. One minor (preexisting) issue: The input title (eg "Agent bridge port") appears twice.

Keyboard-closed view: It looks like the tabs are vertically centered when they should be closer to the screen preview; and, the tab contents don't seem to be visible at all.

> Both issues fixed, verified on the tablet, and the fixed build is installed on both devices.
>
> **Tab bar centered / contents invisible** — I reproduced it on the tablet and traced it with a native view-hierarchy dump. The visibility bindings and tab switching were actually working fine; the bug was a NativeScript layout quirk: a `GridLayout` with no `rows` attribute gets a single implicit row that behaves like `*` (star). The old page measured the controls inside an `auto` grid row (unbounded, so the star row collapsed to content), but the restructured page puts them in the outer grid's `*` row (bounded measure) — so the rows-less tab-bar grid ballooned to fill all remaining height, centered its buttons in the stretch, and left zero height for the tab contents below it. The fix is explicit `rows="auto"` on the tab bar, both Settings rows, and the Back/Menu row in `remote-controls.xml`. Verified all three tabs on-device: Watch shows the touchpad + Back/Menu, Settings shows the screen-size picker and brightness row, Ring shows the six input buttons, all sitting directly under the preview.
>
> **Duplicate input title** — for a single-field edit, the editor title and the field's own label are the same string (`editorTitle` defaults to the field label), and the page rendered both. The per-field label is now only shown when a second field exists (where the labels actually distinguish the fields); single-field edits show just the one heading.
>
> One thing I noticed but couldn't test while disconnected: the keyboard-mode change is untouched except for that label, so it should still look as you saw it. There's also a pre-existing console error on page load — `keyboardType="text"` is not a valid NativeScript keyboard type (only email/number/etc. are), so the binding logs an error and falls back to the default keyboard. Harmless, but the clean fix would be to leave `keyboardType` unset for plain text; happy to do that if you want.
<hr>
Thanks, that is now working. Next up let's add a microphone button to the tab bar, as the rightmost button. Use an icon rather than text, and make it narrower than the others. The button will leave the tab selection unchanged, and trigger as if the wakeword ("Hey Even") was spoken. This will replace the "Hey Even" button in the Ring section.

In the Watch section, we will vertically center the emulated-watch UI within the remaining space beneath the tab bar, and set a maximum width corresponding to an aspect ratio for the simulated watch face of 1.5:1.

> Done and verified on the tablet; both devices have the new build.
>
> **Mic button** — added as a fourth, narrower (56dp) column at the right end of the tab bar, showing the 🎤 emoji. It uses the plain tab style, never shows the selected state, and taps route to the existing `onSyntheticMicTap` (ring "wakeword"), leaving the tab selection untouched. The "Hey Even" button is gone from the Ring tab, which now has just the five ring inputs (Up / Down / Click on the top row, Double / Hold below).
>
> **Watch tab centering + aspect cap** — the component root is now a `rows="auto,*"` grid (tab bar on top, the three sections sharing the star cell), and the portrait page gives the controls the full star row (with Stop recording moved to an `auto` row beneath, so it still appears when recording). The watch section — face plus the Back/Menu row — is `verticalAlignment="center"` in the leftover height and width-capped at `min(available width, 1.5 × 230dp face height ≈ 345dp)` via a new `watchFaceWidth` getter that recomputes on orientation change (in landscape the side panel's 328dp effectively governs). Verified on the tablet: the face sits centered between the tab bar and screen bottom at the capped width, and Settings/Ring stay top-aligned.
>
> One aesthetic note: on the Samsung tablet the 🎤 emoji renders as a gray studio mic rather than a colorful one — legible, but if you'd rather have a crisper icon I could switch to a font-icon or a tinted drawable.
<hr>
Thanks. For the microphone button, let's use `~/Downloads/noun-microphone-1368757.svg`.

> Done — the mic button now uses your Noun Project SVG instead of the emoji, verified on the tablet and installed on both devices.
>
> Since NativeScript Buttons are text-only, I converted the SVG's two paths into an Android VectorDrawable (`App_Resources/Android/src/main/res/drawable/ic_tab_mic.xml`, with a comment crediting the source file) and made the mic control a button-styled GridLayout tile holding a tinted `Image`. It keeps the 56dp width and the `.tab-button` look, plus a small `android-elevation` so it casts the same shadow as the real MaterialButtons beside it. The icon tints `#333333` in light mode and `#cccccc` in dark mode via `tint-color`, matching the tab label colors, and the tap still fires the wakeword without touching tab selection.
>
> One licensing note: Noun Project icons are CC BY unless you have a Pro license — if you don't, the icon's creator should be credited somewhere user-visible (e.g. an about/credits page) before a public release.
<hr>
(I do have a Nounproject pro license)
Thanks, the icon renders correctly, but it's off-center (top and left rather than centered on both axes), and the height and drop shadow of the mic button now doesn't match the other buttons in the tab strip.

> Fixed and verified on the tablet; both devices have the build.
>
> Two things were wrong, both variations of the same NativeScript grid quirk from before:
>
> - **Off-center icon**: the tile's row was effectively auto-sized — row heights are locked in at measure time, and inside the tab bar's `auto` row the tile was measured unbounded, so its cell hugged the 20dp icon and the layout-time stretch dumped the leftover space below/right of it. Giving the tile an explicit `height: 48` bounds its measure, so its `rows="*"` cell genuinely fills and the icon's center alignments work — confirmed by native bounds (icon at exactly (72−30)/2 within the tile on both axes).
> - **Height/shadow mismatch**: MaterialButtons render 48dp tall inside a 60dp layout box (6dp built-in top/bottom insets), while the tile was stretching to the full 60dp row. It now gets `margin: 6 2` plus the 48dp height, so its edges and its elevation shadow align with the neighboring buttons.
>
> The 48dp is derived from the tab buttons' current font/padding metrics, so if the tab-button styling ever changes materially, that value would need to follow — I left a comment in `app.css` tying them together.
</details>
2026-08-26 00:44:22 -07:00
James Babcock b99aa85964 Move phone screen connection status and warnings to the top bar
<details>
<summary>Prompts Used</summary>
On the main page, there's a triple-dot menu. Its icon is currently black-on-dark (this is true on both a light-mode device and a dark-mode device; the top bark has a dark background in both cases). Make that icon white instead.

We have a connection-status indicator on the main page, that says "Disconnected" or "Connected" or "Reconnecting". Let's move this onto the top-bar, as white text, right-aligned next to the triple-dot menu.

We have several problem-status warnings, eg for not having battery-optimization permission, that appear on the main page in the form of a large button below the screen preview. Let's convert all of thes into a yellow triangle ! icon that appears on the top bar, in between the connection-status indicator and the triple-dot menu. Tapping it will open a modal that shows the message that was previously shown, with a button to do the suggested action.

> All three changes are in, and the project builds and typechecks cleanly. Here's what I did:
>
> **White overflow icon** — The root cause is that NativeScript builds its toolbar programmatically, so the `theme` overlay in `NativeScriptToolbarStyle` (an XML-inflation-time attribute) never applied, and the overflow icon fell back to the light activity theme's dark `textColorSecondary`. I added an `actionOverflowButtonStyle` with a white `android:tint` to `AppThemeBase` in `App_Resources/Android/src/main/res/values/styles.xml`, so the icon is white on every page's bar (they all share the dark #424242 background), in both light and dark device themes.
>
> **Connection status in the top bar** — The ActionBar now has a custom titleView (`main-page.xml:5`): "Faceclaw" on the left, and a right-aligned white status label next to the menu. Since the old status string could be a whole sentence ("Reconnecting after ...", "Failed: ..."), the bar shows a short label derived from the connection phase — Connected / Connecting / Reconnecting / Disconnected / Charging / Disconnecting / Failed — and tapping it opens an alert with the full status message, so failure details aren't lost. The old status label below the controls is removed.
>
> **Warnings → ⚠️ icon + modal** — The three inline warning blocks (Even-app conflict, firmware, battery optimization) are gone from the page body in both portrait and landscape. A yellow warning-triangle emoji now sits between the status label and the overflow menu whenever any warning is active. Tapping it opens an in-page modal (same overlay pattern as the existing text-setting editor) titled "Attention needed", listing each active warning with its original message and action button, plus a Close button. The modal closes when you take an action, and auto-closes if the last warning clears while it's open. One side effect: the landscape layout previously showed the firmware warning without its install button — in the modal it now has the button like everything else.
>
> Worth an on-device check: the overflow-icon tint (theme change, so a full reinstall rather than hot reload), and that the titleView labels sit vertically centered against the toolbar height.
<hr>
Thanks. That all looks good, except there are some stylign issues on the warning modal. On a wide tablet, the modal is full-width, which is too wide. When the device is dark-mode, the "Attention needed" title is white-on-light-gray. The title and the warning text need some left/right padding between them and the edges of the modal.

> All three styling issues are fixed and the build is clean:
>
> - **Too wide on tablets**: the modal's width now comes from a `warningsModalWidth` getter in the view model — screen width minus the margins on phones, capped at 480 DIPs on tablets — and it's centered horizontally. It re-computes on orientation change along with the other layout metrics.
> - **White title in dark mode**: the theme's `.ns-dark .h2` rule was beating my `.warnings-modal Label` rule on specificity. I added a `.ns-dark .warnings-modal Label` selector so all text in the modal stays dark-on-light in both modes (the modal deliberately keeps its light look, matching the text-setting modal).
> - **Missing edge padding**: NativeScript ScrollViews don't apply their own padding to their content, so the `padding: 16` on the modal was silently doing nothing. It now lives on an inner `warnings-modal-content` StackLayout; the border/background/margin stay on the ScrollView.
>
> One note: the text-setting editor modal (`system-name-modal`) uses the same `h2`-on-light-background pattern, so its title likely has the same white-on-light problem in dark mode — I left it alone since you only flagged the warnings modal, but it'd be the same one-line fix if you want it.
</details>
2026-08-25 23:09:21 -07:00
James Babcock b33d858fbc Merge branch 'main' of https://github.com/jimrandomh/faceclaw into android-wear-integration 2026-08-25 22:29:42 -07:00
James Babcock 3089bee76b Merge pull request #16 from jimrandomh/onboarding-flow-fixes
Various fixes to the onboarding flow
2026-08-25 22:29:20 -07:00
James Babcock 816c4709ae Add links to the GPL and privacy policy to the "Before You Continue" page
<details>
<summary>Prompts Used</summary>
Let's add two links to the footer of the "Before you continue" page: A link to the license (GPLv3, contained in LICENSE), and a link to the privacy policy (PRIVACY).
<hr>
Continue

> Done — the build passes. The "Before You Continue" page (step 2 of onboarding) now has a footer with two tappable links, "License (GPLv3)" and "Privacy Policy", centered between the disclaimer text and the Back/Agree buttons. They're only visible on that step, so the splash and firmware steps are unchanged.
>
> What I added:
>
> - **`app/phone-ui/document-page.xml` / `.ts`** — a new phone-side viewer page with an ActionBar (title + back button) and a scrollable label. It reads the doc from `about/<fileName>` in the app bundle; webpack already copies LICENSE and PRIVACY there (webpack.config.js:12), since the glasses-side Settings About section uses them too.
> - **`onboarding-page.xml`** — a third grid row with the two links, bound to `footerVisibility` so it collapses on steps 1 and 3.
> - **`onboarding-view-model.ts`** — `onLicenseTap`/`onPrivacyTap` handlers that navigate to the document page, and the `footerVisibility` getter wired into `publish()`.
> - **`app.css`** — link styling (blue, underlined, padded for a comfortable tap target, lighter blue in dark mode) and a modest 13pt size for the doc text since both files are hard-wrapped plain text.
>
> Untested on hardware: worth a quick visual check that the links look right in dark mode and that the LICENSE text (which is 80-column preformatted) reads acceptably in the proportional font.
</details>
2026-08-25 22:26:30 -07:00
James Babcock a7a5005e8d Move the "Disconnect the Even App" page to before pairing rather than after, and make some minor changes to it 2026-08-25 21:29:06 -07:00
James Babcock b74868bfb3 Flasher only uses right lens for confirmation, rather than confusedly trying to check via each lens separately 2026-08-25 21:14:50 -07:00