<details>
<summary>Prompts Used</summary>
Thanks. Next up, let's make soem refinements to the watch app UI.
We'll remove the glasses-battery indicator from the watch UI (it's already on the glasses screen so not needed there).
We'll merge the connection status into the current-app display; rather than one line saying "Connected" and one line saying "Display off" or an app name like "Launcher", we'll merge these into one indicator (in the second line's position), which is "Screen off" or an app name if connected, or a connection status otherwise.
We'll make rotating the crown scroll/select in the same way that swiping up/down on the ring or glasses touchpad does. Apps that want to pay attention to the exact source and details of an input should be able to, but apps that don't pay attention should get sensible behavior by default. (There might already be some code attempting to do this, but currently in my testing the crown has no effect)
> All three refinements are in, and the wear app builds cleanly. Here's what changed:
>
> **Battery indicator removed.** The glasses-battery readout is gone from both places it appeared: the touchpad's status line and the Status screen's connection chip (which now says just "Connected", with "· charging" kept since that signals glasses-in-the-case rather than battery level). The watch-side `PhoneState.battery` field was dropped too since nothing reads it now — the phone still publishes it in the state item (documented in PROTOCOL.md), so nothing changes on the wire.
>
> **Merged status/current-app indicator.** The touchpad's separate top `StatusRow` ("● Connected · 78%") is removed, and `statusLine`/`focusLine` in Common.kt are merged into one `padLine()` used in the centre position: when connected it shows "Screen off", "Locked", "Listening…", or the foreground app name ("Launcher" when nothing's open); otherwise it shows the connection state ("No phone", "Open Faceclaw on phone", "Connecting…", "Glasses disconnected", …). The old status dot's color coding survives as the text color — app names render in the normal text color, problem/busy/off states in the red/amber/gray tones — so the at-a-glance signal isn't lost.
>
> **Crown scrolling.** The pipeline you suspected does exist and the phone side of it is already exactly what you described: crown steps arrive as `scroll-up`/`scroll-down` carrying `source: "watch"`, so apps that inspect the source can, and apps that just switch on the event type get the same behavior as a ring/touchpad swipe. I traced that path end-to-end and found no phone-side gap. The break is on the watch: rotary events are only delivered to a *focused* Compose node, and RemoteScreen requested focus once via `LaunchedEffect(Unit)` with a plain `FocusRequester` — fragile against the nav host and never re-run after anything steals focus (the keyboard activity round-trip, ambient mode, screen off/on). It now uses `rememberActiveFocusRequester()` (Google's documented rotary pattern, present in the bundled wear-compose 1.4.1, with the required `@OptIn(ExperimentalWearFoundationApi)`), plus a lifecycle observer that re-requests focus on every `ON_RESUME`. The accumulator/sensitivity logic is unchanged.
>
> One caveat on the crown: since I can't reproduce the failure off-hardware, this fix targets the most likely cause (focus never landing or being lost). Worth a quick on-device check — and if the crown *still* does nothing, the useful datapoint would be whether `adb logcat` on the phone shows `sys-event .../SCROLL_*` lines when you turn it, which would split watch-side from phone-side cleanly.
</details>
Faceclaw for Wear OS
A watch remote for Faceclaw: everything the Even R1 ring can do, plus the things it can't. Runs on a Wear OS 3+ watch (API 30) paired with the phone that runs Faceclaw. It is a remote, not a standalone app — without Faceclaw on the phone it only tells you to install it.
What it does
The pad (the home screen; the whole display is the touch surface):
| On the watch | On the glasses |
|---|---|
| tap | select |
| double-tap, or a two-finger tap | back, everywhere: closes menus, leaves a settings column, leaves a folder or the launcher grid, returns to the sidebar (and from the sidebar turns the display off, as the ring does) |
| press and hold | the app's context menu (a long press, held until you lift your finger) |
| swipe ↑ ↓ ← → | spatial navigation, with no mode to enter first: the launcher highlights one app and the swipe moves it by a row or a column; the settings panel moves between its columns and down its lists; the sidebar moves up and down; Music skips to the previous / next track. Right goes into things (sidebar → window, section → items) and left comes back out (first column → sidebar). Anywhere without a spatial meaning, up/down scroll, right selects and left goes back. One step per swipe (long swipes used to repeat, which overshot lists whenever the display lagged); use repeated flicks, the crown, or a two-finger page swipe to cover distance. "Natural swipe" flips the vertical sense; left/right can be remapped in settings. |
| rotate the crown | up / down (one step per detent-ish, sensitivity adjustable) — in the launcher that is rows, elsewhere scrolling |
| two-finger swipe up / down | scroll a page (3 steps) |
| twist the wrist twice (two brisk flicks, either direction) | back — from the gyroscope; on by default, sensitivity adjustable |
| tip taps — tap your index finger against your thumb | select; two quick taps = back. From the accelerometer; off by default (experimental): on a wrist, ordinary hand movement produced phantom selects in testing. Turn on in Watch settings; needs ~¼ s of stillness before a tap counts, and both motion gestures are ignored while the watch is off the wrist or buzzing. |
| Tap zones mode | tap the top / bottom third to scroll, the middle to select — for when swiping is awkward |
The R1 ring's scheme is untouched: the ring only has up/down, tap, double-tap and hold, so on the glasses it still works in the stock two-step way (pick a launcher row, tap, pick the app). Watch input is tagged as its own source, so the same screens give the watch the direct scheme above without the ring ever seeing a difference.
Side buttons (when the app is in front): button 1 tap = select, hold = long press; button 2 = back; button 3 = "Hey Even". You can also set the watch's button shortcut to open Faceclaw.
Bottom row buttons: Assistant, Type into app, Apps, Status.
- Assistant — ask the assistant using the watch's microphone (system speech recognition) or the Wear keyboard, and read the reply on the watch as it streams, mirrored from the glasses overlay. The watch buzzes when the reply finishes. "Hey Even" instead opens the glasses' own voice dialog, which uses the glasses mic.
- Type into app — dictate or type text into the foreground app (the terminal, for instance), the same path finalized voice input takes.
- Apps — the sidebar's open windows (tap to switch, × to close) and the full launcher, including installed EvenHub apps.
- Status — connection and battery, display on/off, lock/unlock, connect / disconnect, and whether Faceclaw is running on the phone; watch settings (haptics, keep screen on, swipe direction, tap zones, horizontal swipe actions, tip taps and their sensitivity, crown sensitivity).
The pad keeps the watch display awake while it is showing (Watch settings > "Keep screen on", default on). Wear OS otherwise dozes within seconds of the wrist dropping and freezes the app, so the remote would need a wake-up tap before every gesture.
Phone-side switches live in Faceclaw's Settings > Watch: turn watch control off entirely, decide whether watch input wakes a dark display (on by default — the ring only wakes it with a double-tap), forbid unlocking from the watch, or stop mirroring assistant replies.
The watch buzzes differently when the phone refuses or doesn't answer a gesture (glasses disconnected, locked, watch control off); the pill at the bottom of the pad says why.
Building and installing
The watch app is a separate Gradle project (Kotlin + Compose for Wear OS). It needs the same Android SDK the phone build uses and a JDK 17+:
cd wear && JAVA_HOME=/path/to/jdk ANDROID_HOME=~/Library/Android/sdk ./gradlew :app:assembleDebug
The APK lands in app/build/outputs/apk/debug/. Install it on the watch over
adb (enable developer options on the watch, then ADB debugging and, for a
watch without USB, Wireless debugging / debug over Wi-Fi):
adb connect <watch-ip>:5555
adb -s <watch-ip>:5555 install -r app/build/outputs/apk/debug/app-debug.apk
Two things must match the phone app or the Data Layer silently won't route:
- Application id
com.faceclaw.app— already set inapp/build.gradle.kts. - Signing key. Debug builds of both apps use the shared Android debug
keystore (
~/.android/debug.keystore) on the machine that builds them, so building both on the same computer just works. For release builds, sign the watch APK with the same keystore as the phone APK.
There's no Play Store listing; sideload.
Troubleshooting
- "No phone connected" — the watch has no Bluetooth link to any phone.
- "Install Faceclaw on the phone" — a phone is connected but no app there
advertises the
faceclaw_phonecapability: the phone build predates the watch integration, or the app ids / signing keys differ. - "Open Faceclaw on the phone" — the phone app is installed but its dashboard isn't running (Play services started the process just for our message). Open Faceclaw once; it keeps running with its foreground service while connected to the glasses.
- "The glasses are not connected" — tap Status > Connect.
- Nothing happens and no message: check Settings > Watch on the phone.
Gestures the watch itself owns — the edge swipe-to-dismiss, the OS-level double-pinch / "universal" gestures on some watches — are not available to apps and aren't remapped here.
Protocol details: PROTOCOL.md.