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.