The previous commit's comment and test said Android starts the app in the
background (a home-widget update, a notification-listener rebind) with
the glasses session running. A background start alone doesn't connect
the glasses; only the main page does. The state that breaks voice is
the Activity being destroyed afterwards: swiping the app away in Recents
destroys it while the foreground service keeps the process and session
running, and NativeScript then clears both foregroundActivity and
startActivity. On Android 12+ Back on the main page only moves the task
to the back, so the Activity survives it. Comment and test wording only.
ensurePermissions looked up the Activity before checking whether any
permission was missing, and getActivity() throws when there is none.
Android starts the app in the background with no Activity (a home-widget
update, a notification-listener rebind), and the glasses session runs
from there until the app is opened. So in that state every "Hey Even"
failed in ensureVoicePermissions even though the mic permission was
granted, and the voice dialog kept showing the idle "Voice control
stopped.". The same throw hit ensureBlePermissions.
The Activity is now only looked up when a permission actually has to be
requested. A capture that fails to start for any reason other than a
denied permission now says so in the dialog instead of leaving the idle
status up.
Review fixes for the charging-case battery:
- The case reports whether the glasses are docked. An empty caseInfo
(the reply out of the case) now parses as "not docked, no level"
instead of nothing, and undocking is reported even when the level and
charge state are unchanged. TS keeps the last level but clears
caseCharging while the glasses are out of the case.
- The phone line shows the charging mark only while it is live: G2 and
Case only with a link to the glasses (connected or charging), and Case
only while docked. Levels stay as the last known ones.
- The session-start case read waits until the layout is up, so a
firmware that ignored it could no longer hold up the first frame. When
the glasses are already charging at connect, the charging-mode read is
the only one; the old duplicate read and its "late ACK" log are gone.
- Case dedup state resets on every connect, as wearState does, so each
session's read reaches TS.
- caseCharging uses > 0 like the headset, and is normalized to 0/1.
- iOS now feeds the reading into the shell battery state, and the
assistant's describeState includes the case level.
- The batteryLine accessors move above connectionStatusLabel's doc
comment.
A line under the mirror lists each device whose level is known, e.g.
"G2 100% · Case 98% ⚡ · R1 72%" (⚡ = charging), in portrait and
landscape. The case level joins the shell's battery state beside the
glasses and R1 (it is not drawn in the glasses' top bar) and reaches the
page through the dashboard snapshot. Like the glasses level it is kept
across disconnects: the case only reports while the glasses are docked
and only drains while charging them.
- "Whisper server (self-hosted)" transcription provider for OpenAI-compatible
Whisper servers (vLLM, speaches, LocalAI) over plain HTTP batch requests,
with URL, model, language and key settings (Voice). Pause-ended spans are
one request each, finalized in audio order, with provisional text while a
span is open. See notes/whisper-server.md.
- Transcribe (and other continuous capture) works on iOS with a cloud or
Whisper-server provider; push-to-talk shares a running capture.
- Transcribe saves each session's audio as transcribe-<time>.wav in Downloads
(setting "Save Transcribe audio", on by default), written as it is captured
so a crash leaves a playable file; a saved transcript uses the same stamp.
- Calculator stops continuous listening when its window closes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Rename IosAudioPacketListener.onAudioPacket to onNsDataAudioPacket. The
selector collided with FaceclawAudioPacketListener's, Kotlin/Native mangled
one of the two depending on export order, and the first glasses audio packet
aborted the app with "unrecognized selector".
- Closing a window (e.g. Transcribe from its system menu) aborted the app: the
menu pop re-renders the window, that frame is queued behind the surface
removal, and Kotlin's compositor throws on the unknown surface. The bridge now
tracks which surfaces Kotlin holds and drops stale calls inside the queue,
submit re-checks the window is still open, and the IosGlassesSession surface
wrappers log and drop compositor errors instead of aborting.
- Only connect to the R1 ring from the phone in "Direct" mode, as Android does.
iOS always tried; the failing connect retried every few seconds and starved
the glasses link, so the glasses image lagged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A double tap that wakes the display (a screen-off double-click, or the
firmware's display-wake) now focuses the foreground window instead of the app
switcher. "Wake into last app" (Display settings, on by default) turns it back
to the switcher. Lock screen, put-on, notification and wakeword wakes are
unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>