meta-wearables-transport-reliability

Design and review Meta Wearables DAT transport reliability across Bluetooth, Wi-Fi, and audio routes.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/shotcowboystyle/meta-wearables-ops-plugin --skill meta-wearables-transport-reliability-shotcowboystyle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-wearables-transport-reliability
Source: https://github.com/shotcowboystyle/meta-wearables-ops-plugin/tree/main/.agent/skills/meta-wearables-transport-reliability
Command: npx skills add https://github.com/shotcowboystyle/meta-wearables-ops-plugin --skill meta-wearables-transport-reliability-shotcowboystyle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Building reliable connectivity between a companion app and Meta smart glasses is hard: Bluetooth control, Wi-Fi media transport, HFP/A2DP audio, backpressure, thermal limits, and disconnect recovery each fail differently, and teams often conflate a stable link with proven camera, Display, or audio capability. ## Core Features & Use Cases - Transport classification and auditing: Classify each hop as Bluetooth control, Wi-Fi/local network, HFP, A2DP, or Internet, and audit iOS Info.plist/Bonjour and Android Manifest/permissions/Gradle artifacts against the actual DAT version. - Reliability and recovery design: Define bounded queues, drop/coalesce policies, thermal and power fallbacks, and typed failure/recovery tables without blind retry loops. - Evidence-based verification: Produce source/static/compile/mock/connected/physical/signed evidence with explicit Wi-Fi parity and processing-location status. - Use Case: When an Android app drops frames during glasses camera streaming, use this Skill to classify the failing hop, audit the resolved Maven artifact and permissions, and produce a recovery table with physical-device evidence. ## Quick Start Use the meta-wearables-transport-reliability skill to diagnose why my Android DAT app loses the glasses camera stream after a few minutes and produce a failure and recovery table.

Frequently Asked Questions about meta-wearables-transport-reliability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug connection drops between my app and Meta smart glasses?

Classify each hop as Bluetooth control, Wi-Fi/local network, HFP, A2DP, or Internet, then record the first observed failure state before attempting one bounded recovery. The Skill provides a failure classification chain from configuration through thermal/power to isolate the actual failing layer.

How do I set up Wi-Fi streaming for Meta Wearables DAT on Android?

The reviewed DAT Android 0.9 changelog and setup docs do not establish an iOS-equivalent Wi-Fi transport contract, so mark it source-conflict or to-verify. Resolve the exact Maven artifact and docs, then test the named target rather than inferring support from an INTERNET permission.

Does a stable Bluetooth connection prove camera or Display capability on Meta glasses?

No. Bluetooth connection, registration, or link stability never proves camera, Display, HFP, Wi-Fi, or physical input capability. Each capability requires its own connected and physical evidence run on the exact glasses, firmware, and app build.

What audio routes do Meta smart glasses support for microphone and playback?

The full DAT reference documents glasses microphone input through HFP as 8 kHz mono and Bluetooth audio output through A2DP. Treat HFP and A2DP as separate paths, and never label a phone microphone or A2DP playback as a glasses microphone.

Why does my glasses streaming app overheat or stop during long sessions?

Battery, thermal, peak-power, doff/fold, and timeout states require typed handling with visible fallbacks and bounded recovery. Never auto-retry a thermal or power shutdown; define stop order, queue budgets, and a duration-tested run for the named workload.