EDGE-03: smart-glasses adapter framework and official Meta DAT integration #4

New issue

Open

opened 2026-09-23 05:58:10 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-09-23 05:58:10 +00:00

(Migrated from github.com)

Canonical source lives here. Foundation #1; Android backend #3. Cover common glasses through native or companion adapters without claiming every device exposes the same capabilities.

Runtime topology

Android-installable glasses: native Common Lisp host only after vendor installation and actual device ABCL/ART tests pass.
XREAL/VITURE display/compute configurations: use a verified companion/compute-host adapter, with per-model display/input/tracking capability discovery.
Vuzix/RealWear families: determine exact installable models and supported vendor APIs; catalog entries are not verified compatibility.
Meta: Android companion integration through official Meta Wearables Device Access Toolkit; do not assume a sideloadable on-glasses Lisp runtime.

Meta implementation

The official Android repository checked 2026-09-23 documents DAT 0.9.0 with camera/display artifacts. The 2026-08-03 changelog replaces DeviceSession.addStream with addCamera and the camera-owned stream. Verify/pin actual SDK and device compatibility at implementation time; do not copy obsolete APIs. Model-specific displays exist in the SDK, but not every Meta model has a display. Discover rather than hard-code blanket assumptions.

Implement registration/permissions, session state, photo/video streams, model-supported display/input, backpressure, cancellation, disconnect/reconnect and revocation. Sensor operations require explicit user permission, recording indicators, scoped authorization and actual-effect rechecks. Expose SDK analytics/crash-reporting controls intentionally. Never use private/bypass firmware paths.

Acceptance

Adapter interface and exact model/firmware/SDK/host compatibility matrix.
Official SDK build, registration and permission flow tested.
Camera/display/input only advertised when actually available and authorized.
Stream/display/session cleanup on disconnect, denial, revocation and process death.
Vendor mock tests plus separate physical-device evidence; mocks cannot close hardware gates.
Generic fixes upstream; downstream UI consumes the adapter without source copies.

References: https://github.com/facebook/meta-wearables-dat-android ; https://github.com/facebook/meta-wearables-dat-android/blob/main/CHANGELOG.md ; https://docs.xreal.com/

Current GlassesHosts.kt contains forwarding facades only; it is not an implemented vendor adapter.

Canonical source lives here. Foundation #1; Android backend #3. Cover common glasses through native or companion adapters without claiming every device exposes the same capabilities. ## Runtime topology - Android-installable glasses: native Common Lisp host only after vendor installation and actual device ABCL/ART tests pass. - XREAL/VITURE display/compute configurations: use a verified companion/compute-host adapter, with per-model display/input/tracking capability discovery. - Vuzix/RealWear families: determine exact installable models and supported vendor APIs; catalog entries are not verified compatibility. - Meta: Android companion integration through official Meta Wearables Device Access Toolkit; do not assume a sideloadable on-glasses Lisp runtime. ## Meta implementation The official Android repository checked 2026-09-23 documents DAT 0.9.0 with camera/display artifacts. The 2026-08-03 changelog replaces `DeviceSession.addStream` with `addCamera` and the camera-owned stream. Verify/pin actual SDK and device compatibility at implementation time; do not copy obsolete APIs. Model-specific displays exist in the SDK, but not every Meta model has a display. Discover rather than hard-code blanket assumptions. Implement registration/permissions, session state, photo/video streams, model-supported display/input, backpressure, cancellation, disconnect/reconnect and revocation. Sensor operations require explicit user permission, recording indicators, scoped authorization and actual-effect rechecks. Expose SDK analytics/crash-reporting controls intentionally. Never use private/bypass firmware paths. ## Acceptance - [ ] Adapter interface and exact model/firmware/SDK/host compatibility matrix. - [ ] Official SDK build, registration and permission flow tested. - [ ] Camera/display/input only advertised when actually available and authorized. - [ ] Stream/display/session cleanup on disconnect, denial, revocation and process death. - [ ] Vendor mock tests plus separate physical-device evidence; mocks cannot close hardware gates. - [ ] Generic fixes upstream; downstream UI consumes the adapter without source copies. References: https://github.com/facebook/meta-wearables-dat-android ; https://github.com/facebook/meta-wearables-dat-android/blob/main/CHANGELOG.md ; https://docs.xreal.com/ Current `GlassesHosts.kt` contains forwarding facades only; it is not an implemented vendor adapter.