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.
The glasses relay the charging case's state on UX_GLASSES_CASE_APP_ID
(sid 0x81): GlassesCaseDataPackage{commandId=CASE_INFO, magicRandom,
caseInfo{soc, chargeStatus, lidStatus, inCaseStatus, errorCode}}, the
schema in g2-kit-unofficial's glasses_case.proto. The Even app reads it
with an empty caseInfo (ProtoBaseSettings.getGlassesCaseInfo).
Observed on G2 2.3.0.24 / Faceclaw/38: while docked the right temple
pushes a GlassesCaseInfo (flag 0x01, its own magic) on every change --
docking, lid, USB, each 1% -- and answers a read with full data; out of
the case a read comes back with an empty caseInfo. Docking pushes
{inCaseStatus=1} before the level, and proto3 drops zero fields, so a
missing soc means no level rather than 0%.
So read it once at session start (docked glasses may be fully charged
and never enter charging mode) and again on entering charging mode,
which clears the queue; pushes carry every later change. Every 0x81
frame is taken as state in onNotification (pushes skip the ack path by
flag). New readings reach TypeScript through
FaceclawBleCommunicatorListener.onCaseState (level, case-charging), on
Android and iOS. Captured frames are tests.
- 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>