Meta SHIPPED version 1.0.1 of its Wearables Device Access Toolkit (DAT) on October 9, and its OWN Android changelog names TWO DEFECTS in the 1.0.0 release that preceded it. Both sit in the CAMERA path, the part of the SDK third-party developers lean on MOST.
What the changelog says
The 1.0.1 entry lists EXACTLY two FIXES and nothing else: “Buffer CORRUPTION while streaming compressed HEVC buffers, causing sporadic frame FREEZES,” and “Several performance issues on Stream causing LAG and stutter.” There are NO new APIs, no deprecations and no behavior changes in the entry.
Version 1.0.0 is dated September 24, 2026, which puts the FIX 15 DAYS after the SDK’s first STABLE release. As MIXED reported, the iOS counterpart received a MATCHING 1.0.1 tag the SAME day, and the Android core artifact appeared on Maven Central shortly after the release commit.
Why it matters
DAT is the ROUTE every third-party app uses to reach the camera, and on Meta Ray-Ban Display the display, across Ray-Ban Meta, Oakley Meta and Meta Ray-Ban Display glasses. A corrupted HEVC stream is therefore not an INTERNAL issue: ANY app built on 1.0.0 that streams compressed video from the glasses could have shown FROZEN frames to a WEARER.
What Meta does NOT say is equally important. The changelog gives no COUNT of AFFECTED apps, no date when the fault was introduced, and no indication of whether any shipping app actually surfaced the freezes to users. Developers building on 1.0.0 should treat the UPGRADE as the PRACTICAL takeaway.
Context
The 1.0.0 release was a LARGE one. It added experimental Inputs, Motion, Speech, voice invocations, STANDALONE photo capture and camera AUDIO streaming, plus DEVICE-STATE accessors such as battery level, thermal level and hinge state. Experimental features, per Meta’s own note, can be built and tested against, but apps using them CANNOT be published yet.
A QUICK point release that touches only STREAMING stability suggests Meta is prioritizing the CORE camera pipeline before the developer STORE opens more broadly. That is the RIGHT order, but it also means the first “stable” DAT was not quite STABLE where it counted.
Sources: Meta DAT Android changelog; MIXED.