A three-day all-day event showed only under its first day, so on day three
the app had nothing under Today. An event that began on an earlier day and is
still going is now listed under today, and an event covering more than one
day shows its span ("Mon 16 – Wed 18 Nov").
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A multi-day all-day event that started yesterday read as yesterday's
("Mon Nov 16 (all day)"), so the assistant left it out of today's plans;
timed events had no end time. Format the span: the last day of an all-day
event (ends are exclusive) and the end time of a timed one.
The date formatting moves into a pure app/assistant/date-format.ts with
unit tests.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The glanceboard head-tilt option was more complicated than necessary,
because it wanted the user to take two angle measurements, a baseline
angle and a tilt angle. That was a workaround to not knowing the
accelerometer's orientation/calibration, but actually, we do know those.
(Except, as it turns out, on the G1, the accelerometer orientation is
different than it is on the G2, and there was a bug where EvenHub apps
got their accelerometer readings in the wrong orientation. So for
example the EvenHub Level app didn't work correctly.)
HIGH negotiates a ~5s supervision timeout that kills the link on any
>5s BLE gap and can strand an arm in a half-open state where it stops
advertising (recoverable only by a 5-tap reset). Mirrors the ring fix
in connectRing, which removed HIGH for the same reason. BALANCED keeps
a longer supervision timeout; the firmware's own fast-profile request
still negotiates speed for transfers.
autoConnect only connects on a fresh advertisement, so an arm stuck in a
half-open state (stopped advertising after a dropped link) is never reached.
Retry with a direct connect: its aggressive scan catches a briefly-advertising
arm and the cached bond can recover the half-open link. Adds a
g2.connect-fallback-direct counter for diagnostics.
Direct connect (autoConnect=false) is supervised less patiently by Android's
BLE stack; the ring already requires autoConnect=true for this reason, and the
glasses arms showed the same short-lived direct-connect drops. Switch both
arms' beginConnect and connect to autoConnect=true.
Most of the builtin apps had some padding between the window edge and
their content, because they expect to be displayed with a line border on
their edge. We added a customization option to remove the border, so,
that padding is not always necessary. Make the layouts dynamically
adjust, to omit the padding when it isn't needed.