Glasses running an older Faceclaw firmware revision cannot be upgraded at all. The flash asks for confirmation on the lens first, and that firmware never shows the prompt, so the one path off it is closed. Measured on revision 13 (base 2.2.9.22). showPrompt writes the EvenHub create-prompt page to the right arm and waits for an ack. The lens accepts the write at the GATT layer and then answers nothing and displays nothing: four attempts, four onWriteCharacteristic status=0 length=165, no reply. buildCreatePromptPage documents its geometry as stock-firmware-safe "so this works before flashing", and that does not hold there. Three faults, each only visible once the previous one is fixed. An unacked prompt page was fatal. Flashing is the only way off that firmware, so failing here leaves the glasses permanently unupgradable. An unacked page now falls back to the phone-side confirmation that the low-battery retry already uses, on a screen that says what is being given up: the on-lens step is what proves the glasses are the wearer's. connectArm made a single attempt. The lens is routinely unavailable for a moment just after a previous link to it closed, which is exactly the state a retry is in, so the fallback failed instantly with "could not connect to the right arm". FaceclawFirmwareFlasher.connectLensResilient already retries within a window for this reason; connectArmResilient mirrors it and reports each attempt. That retry then tripped the lost-connection latch. Disconnecting between attempts fires onConnectionStateChange, which set rightLost AND finished and counted down the selection latch, so a successful second attempt still aborted with "Lost connection to the glasses". The callback now ignores drops while the arms are still being established. Logging, because a failed flash used to leave almost nothing to read. emitLog reached logcat, but emitState, emitProgress and emitComplete on the flasher, and emitState and emitResult on the prompt communicator, went only to the in-app listener, so the line carrying the reason existed only on the phone screen. Seven `catch (Exception ignored)` blocks across the two classes now log with the Throwable, matching the call sites elsewhere that already do. tests/flash-prompt-fallback.test.cjs covers the decision at its seam through the existing load-typescript loader. The first test fails against the current view model and passes with this change; the second is a regression guard and passes either way, so an unrelated failure cannot quietly skip the on-lens confirmation. Verified on hardware: both lenses flashed through this path after it had been a dead end.
Main-screen UI
Android and iOS share remote-controls.xml, remote-controls.css, and
RemoteControlsViewModel: tab order and selection, screen-size choices,
brightness/Auto settings, watch labels, ring markings, and microphone/keyboard
buttons. Import the stylesheet at the top of each platform's application CSS
(before any rules), so the NativeScript CSS pipeline includes it.
Android's MainViewModel extends that shared model and connects it to
dashboardController. iOS loads the same XML with Builder.load and connects
it to IosPreviewController. Keep platform-specific transport, page lifecycle,
and navigation in those adapters. Android uses NativeScript gesture events;
iOS feeds raw touches to PhoneGestureRecognizer, so the discrete pad gesture
bindings in the XML are Android-only to avoid delivering each gesture twice.
The iOS shell uses the same portrait preview-above-controls layout and 345-DIP
landscape controls column. It respects safe areas, uses the same overflow menu
labels/order, and retains device diagnostics under the connection status.
Conversations and Record screen are disabled on iOS because their storage and
recording services are currently Android-only. Take screenshot opens the iOS
share sheet. Text settings still use native dialogs. Keyboard input uses the
shared keyboard-input-panel.xml multiline editor and shell keyboard session,
with separate Agent and App destinations when available. iOS keeps the editor
above the software keyboard in both orientations.
Voice input uses the glasses microphone when connected and the phone's default audio input in preview mode. The phone path requires both Speech Recognition and Microphone permissions and stops when Faceclaw leaves the foreground; connected-glasses capture retains its existing background behavior.
The iOS microphone and keyboard image assets are 3x rasterizations of the Android vector drawables with the same names; regenerate them from those vectors if the icon designs change.