<details>
<summary>Prompts Used</summary>
User: On the single notification view (focusing a notification on the bottom bar, or in the notifications app), the page title "Notification" and the notification itself can overlap, depending on configured font size.
Opus 5.5:
> I fixed the overlap in the single-notification view, but I haven't checked it on the glasses. The build and typecheck pass.
>
> **Cause:** In `drawDetailContent` (`app/ui/notifications.ts`), the "Notification" title was drawn at y=21, but the icon and the app-name/time line under it were at fixed spots (y=36 and y=42). Only the body text below them moved with the font. Small-font line heights go up to 21px, and once the line height passes about 15px, the title runs into the app-name line.
>
> **Fix:** The header now sits below the title's text line: 3px below it, then a row as tall as the icon or the text line, whichever is bigger. The app name is centred vertically against the icon, and the body starts 4px below that row. At the 12px default everything lands exactly where it did before, so only larger fonts look different. The menu on the right was never affected.
>
> This covers both places you hit it: the bottom-bar tray and the Notifications app's detail view. The pop-up for a new notification uses the same view, so it gets the fix too.
>
> One thing I left alone: this title sits at (24, 21), but list screens like the Notifications list put their title at (18, 10). So the title jumps a little when you open a notification from the list. Moving it to (18, 10) would make the two match and give large fonts about 11px more room. Say if you want that.
<hr>
User: Thanks. Next up, in the Customization section of the Settings app, reorder the settings so that Font is first.
Opus 5.5:
> Font is now the first row in Settings > Customization, whichever app-switcher position is set (left/right, bottom or popup). The other rows keep their order: app switcher position, then the bottom/popup-only rows, then Battery indicators, Animations and Time format.
>
> The change is in `customizationRows()` in `app/ui/dashboard/settings-menus.ts`. Nothing else relies on the row order, and the build passes. I haven't installed it on a device.
</details>
Fix missing submenu indicators and change their appearance. Clean up
styling in the Terminal app and move Settings to the top-level menu.
Remove right padding from the bottom bar.
The same NativeScript conversion leak as the frame path (see
java-direct-buffer.ts) applied to every other ArrayBuffer handed to a
Java ByteBuffer parameter:
- Shell scenes (submitShellScene on the bridge and the preview display),
submitted on every shell render, which the frame-path fix predates.
These now go through a reused JavaDirectBuffer like frames do.
- Glyph, firmware-glyph and image atlas registration, Mapbox image
decode, the preview placeholder bitmap, firmware hash/write, binary
file writes and the EvenHub privacy-policy download, plus the Kotlin
protocol smoke test. These are rare or large, so they cross through a
new copyToJavaByteBuffer: a fresh Java direct buffer per call that is
freed normally, rather than one pinned for the life of the isolate.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
connect() registers window surfaces in a loop that reads the foreground
window once, before the loop, then awaits each surface's configure call
before queuing its visibility. On a fresh process restoreOpenApps runs at
the same time and focuses windows as it relaunches them. The bridge runs
Java calls in order, so a visibility decided before the await lands after
the focus change's own calls and undoes them: the old foreground can stay
visible and cover the new one, and a later window switch doesn't clear
it, because a switch only hides the window being left.
configureWindowSurface now also accepts visibility as a function, asked
after the configure call, when the visibility call is queued. The display-
attach loops (glasses and preview), the display-mode, per-app layout and
vertical-position changes, and an in-process window's height-mode change
pass one. Launch paths that pass a literal false are unchanged.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Passing a JS ArrayBuffer to a Java ByteBuffer parameter leaks it in
@nativescript/android 9.0.4 through 9.1.1: JsArgConverter wraps the backing store with
NewDirectByteBuffer and takes a JNI global ref that it never deletes. The
ref keeps the ByteBuffer reachable, so makeInstanceWeakAndCheckIfAlive
always answers "alive", the JS finalizer re-arms, and V8 never frees the
ArrayBuffer. submitSurfaceFrame passed a fresh copy of each frame this way,
so every frame leaked a full surface (576x260, 640x452 or 640x480 bytes)
plus one global ref, including frames that Java then discards as unchanged.
The draw-list buffer and buzzer payloads leaked the same way.
Each payload now goes through a reused Java direct ByteBuffer
(app/native/java-direct-buffer.ts): JS writes into it through an
ArrayBuffer.from view, and the Java object itself is passed, which takes
NativeScript's ordinary object path. Every consumer (SurfaceCompositor
applyAndComposite, playBuzzerSequence) copies before returning, so one
buffer per JS context is safe.
Covered: the communicator bridge (frames, draw lists, buzzer, which also
carries EvenHub tones), the preview-only display, and all eight worker
apps. Workers submit through the Android getActiveDisplay() (frames) and
worker-buzzer (tones), so the reused buffers live there rather than in
each worker; the worker sources are shared with iOS, whose active display
takes the ArrayBuffer itself. The
smaller one-off crossings (glyph and image atlas registration, the gray
preview helper, firmware and file writes) are left as they are.
tests/java-direct-buffer.test.cjs covers the helper against a fake
ByteBuffer, and the Android worker-buzzer test stubs it.
(Rebased onto main by James Babcock: worker changes moved into
active-display.ts and worker-buzzer.ts.)
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The native session already clears silent mode on touchpad input and re-reads it on every battery poll, so the TypeScript-side clearing duplicated that. The display-target trigger was also wrong: the communicator stays up in silent mode, so it cleared the flag on the next shell render.