Advanced Settings "In the meta app" vs "Internal"

[julienguegan]

Hello !

Thank you for this application, it is really great and awesome 😄 I see that in the Advanced settings, there is a lot of cool things that I would like to better understand and make it works, especially variables in "Internal" section (for example, "motion data stream" in video/live or "posture detection" in the health/fitness) but there is a small note saying Not in the Meta app The glasses read them, but only matter to Meta's own testing what does it means exactly ? We can't have this data at all ? If the glasses have an IMU, it means the data exists we should be able to have it, correct ?

If you have more information about all of this, it would be great !

[julienguegan]

update on this, by vibecoding a bit and rebuilding the app myself, it seems I could get back the data I wanted ... May be vibecoding a bit more could help me understand the whole system and how it works 👍

[macedonga]

Thanks, and nice that you got the data out. That note is misleading, sorry: from what I found in the firmware, some of the Internal settings do nothing on these glasses, and Motion data stream and Posture detection are two of them. The motion data Visor reads is the log that comes with each capture; you can see it in a capture's details in the gallery. What data did you get from your build, and how? If it's useful to others, I'd like to add it.

[julienguegan]

Yes you are right, the motion data exists from the beginning in the app as a metadata of a video capture. You have to click on the video and swipe down to see the metadata, there we can see tilt, movement, acceleration, rotation ... In the end, my vibecoding session just add the possibility to save/share those data as a .csv (don't know if it is useful ?). Indeed, activate/desactivate 'motion_data_stream' in the settings does not change the fact that those metadata on motion appear or not.

I see that there is some autocapture settings, I did not test on the official META AI app but my assumptions is that you could trigger automatically the video capture based on motion data. And those motion data should not only be associated with video but available as a streaming service (could be cool for an activity recognition feature). There is an issue opened in the official github meta/meta-wearables-dat-android#200