meta-wearables-dat-android

I had to add a ProGuard consumer rules file to work around this. Is this safe, or is this pointing to the 0.4.0 release having issues? If this is required and safe to do, these consumer rules should be included in the AARs.

Hi Meta Wearables team, Thank you for providing this SDK and making it available to developers. I'm excited to build with the Ray-Ban Meta glasses! I've been working on integrating the camera streaming feature into my Android app, but I'm encountering a persistent issue with the Bluetooth Classic (RFCOMM) connection. I've done extensive debugging and verified all the prerequisites mentioned in the documentation, but the problem persists. I would really appreciate any guidance or insights you could provide. Thank you in advance for your help! What I was trying to do I was trying to stream video from my Ray-Ban Meta glasses to my Android app using the Meta Wearables Device Access Toolkit (DAT SDK version 0.3.0). I followed the official CameraAccess sample app and configured it with my registered APPLICATION_ID from the Wearables Developer Center. What happened instead When I tap "Start Streaming", the app shows a loading spinner indefinitely. The stream never starts - it stays stuck in StreamSessionState.STARTING and never transitions to STREAMING. Additionally, the glasses become very hot (overheating) during these failed connection attempts. The exact steps to reproduce the issue 1 ) Setup: Phone: Solana Saga (Android 14) Glasses: Ray-Ban Meta (firmware up to date) SDK: Meta Wearables DAT 0.3.0 Sample app: CameraAccess from official GitHub repository 2 ) Configuration: Added APPLICATION_ID in AndroidManifest.xml using a string resource (to avoid Integer/String type casting issue) Developer Mode enabled in Meta AI app Glasses paired via Bluetooth and connected to Meta AI 3 ) Steps: Launch CameraAccess app Tap "Connect my glasses" → Successfully redirected to Meta AI and authorized Return to CameraAccess → "Start Streaming" button is enabled Tap "Start Streaming" Result: Infinite loading spinner, no video displayed 4 ) Observed in logs (adb logcat): 5 ) What works: App registration with Meta AI ✅ Device detection (glasses appear as connected) ✅ Data synchronization (RLDrive sync messages) ✅ BTC lease creation ("BTC lease created for ACDC app") ✅ 6 ) What fails: RFCOMM/Bluetooth Classic socket connection for video streaming ❌ Additional notes The glasses overheat significantly during the failed connection attempts The RFCOMM connection fails repeatedly even after: 1. Restarting the glasses (fold/unfold, power cycle) 2. Restarting both apps (Meta AI and CameraAccess) 3. Re-pairing Bluetooth Low-speed BLE connection works fine (sync data flows normally) Only the high-speed BTC/RFCOMM connection for video streaming fails Expected behavior** After tapping "Start Streaming", the app should transition to StreamSessionState.STREAMING and display the live video feed from the glasses camera.

Environment Samsung Galaxy S23 Meta Glasses SDK version - 0.4.0 Meta Glasses model: Ray-Ban Meta Smart Glasses Our own integration and the demo CameraAccess app Actual Behavior Both in our integration and in the sample CameraAccess app there is a significant initial delay (5-10 seconds) between receiving first frames from the glasses camera and the preview becoming responsive (e.g. following the movement of my head). After that time, it looks like the streaming catches up and then the frame rate stabilises. Lowering the streaming quality or frame rate doesn't help much. I'm using the default settings: There is also a significant delay when we invoke at the beginning of streaming. Expected Behavior** The streaming should deliver a stable frame rate from the beginning, without delay. It is crucial when the user's goal is to take a picture.