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.
Tests
Faceclaw's pairing logic (app/g2/glasses-hardware-identity.ts,
ble-proximity.ts, even-advertisement.ts, pairing-candidates.ts,
glasses-artwork.ts) is written without NativeScript imports so it can run
under plain node. The tests here cover hardware-identity decoding, proximity
estimation, the advertisement parsers, and left↔right pair grouping.
Run with:
npm test
That compiles the pure modules with the project's TypeScript into
.test-build/ (git-ignored) and runs node --test tests/. No extra
dependencies are needed — the tests are plain .test.cjs files that use
node:test and node:assert.
The shared Kotlin suite runs separately from the Node tests:
npm run test:kotlin
npm run test:kotlin:ios
It includes the migrated compass, R1 battery, gesture and texture Java fixtures, which now call the Kotlin implementation from Android host tests. Common tests also run as native iOS simulator binaries. See the Kotlin README for SDK requirements, source layout and coverage. The compass and battery fixtures retain the golden packets shared with firmware tests.
The native iOS EvenHub probe runs separately on a booted simulator:
node tests/ios-evenhub-native.cjs <simulator-UUID>
It compiles the production WKWebView host into an isolated app and checks local and remote loading, document-start injection, assets, storage and navigation. It then opens Safari to background the probe and verifies that injected timeouts, intervals and animation callbacks still fire, and cancelled timers stay cancelled. A short UIKit background task keeps the test process running without glasses. This covers the ticker's background behavior; sustained execution with BLE and a locked physical phone still requires device testing.
The native Android EvenHub probe runs on a booted emulator or attached device:
node tests/android-evenhub-native.cjs [adb-serial]
It compiles the production EvenHub WebView classes into an isolated APK (with the
Kotlin compiler and AndroidX artifacts a prior ./build.sh cached), installs it,
and checks per-package WebView profiles, that the bridge reaches only the app's
own main frame (not its iframes or pages it navigates to), that host scripts and
timer ticks stay out of other sites, and that a renderer crash leaves the process
running.