Meta's own changelog says its glasses toolkit 1.0 froze camera frames
Meta shipped version 1.0.1 of its Wearables Device Access Toolkit on October 9, and the Android changelog names two defects in the version before it. Both are in the camera path: "Buffer corruption while streaming compressed HEVC buffers, causing sporadic frame freezes" and "Several performance issues on Stream causing lag and stutter". The file was read at 21:37 UTC on October 10.
The Meta AI app icon, seven purple and blue petals arranged in a ring on white. The Meta AI app is where glasses are registered before a third-party app can open a session with them. Image: Meta
That toolkit is the route every third-party app takes to the camera and display on Ray-Ban Meta, Oakley Meta and Meta Ray-Ban Display, so a corrupted buffer in the HEVC stream is not an internal matter. Meta does not say how many apps saw it, when the fault was introduced, or whether any shipping app showed the freezes to a wearer.
Meta shipped the fix 15 days after 1.0
The commit titled "Release 1.0.1" landed at 18:23:02 UTC on October 9 on the Android repository, and Maven Central lists com.meta.wearable:mwdat-core:1.0.1 as published at 20:17 UTC the same day. The iOS twin's 1.0.1 tag is stamped 19:51:53 UTC. Version 1.0.0 is dated September 24 in both changelogs, which puts 15 days between the release and the repair.
The camera work those two faults sit on arrived in 1.0.0 itself. That release added Camera.photo for standalone high-quality photo capture with a PhotoTransferProgress report while the image moves, and StreamConfiguration.audioCodec with Stream.audioStream to carry audio frames alongside video. Both are marked experimental in Meta's own list.
1.0.0 was a large release by the toolkit's standards, and most of it was new surface rather than repair. It added experimental modules for inputs, motion and on-device speech transcription, a voice-invocation stream that lets the Meta AI app hand an app a launch request, and battery, charging, don, hinge and thermal state on the Device object. It also added a mock display preview that renders a Ray-Ban Display session on the phone, so a developer can click through an interface without a pair of glasses in front of them. The release before it, 0.9.0, landed on August 3.
iOS got the same version number and no API changes
The iOS changelog entry for 1.0.1 reads, in full, "No developer-facing changes." That is a statement about the API surface rather than about the binary, and Meta published the iOS release on the same day as the Android one.
Both changelogs carry the same standing warning above every entry: the public API has semantic versioning guarantees, but experimental features "can be built and tested against, though apps using them cannot be published yet". That line has been there since before 1.0 and is the constraint a React Native wrapper for the toolkit ran into on October 4.
The repositories are small by Meta standards: 563 stars on the iOS side and 375 on Android when both were read at 21:37 UTC on October 10. Seven artefacts now sit under com/meta/wearable/, covering core, camera, display, inputs, motion, speech and a mock device. The commit that moved the toolkit to Maven Central in the first place is dated September 14, so the whole public distribution history of this thing fits inside four weeks. For a developer, the practical news is that a frame-freeze fault in the September release now has a fix with a version number on it, four weeks into the toolkit's public life on Maven Central.
