[Feature Request / Bug?] Native recording kills A2DP stream

When you start a native video recording on the glasses, the firmware takes exclusive control of the audio pipeline and drops the Bluetooth A2DP connection. Music stops. The recording ends, music resumes. This isn't a bandwidth issue — camera writes to onboard storage, speakers run over a separate Bluetooth profile. These are independent subsystems. The firmware is just not designed to keep them alive simultaneously.

The SDK workaround (stream video to phone, record locally there) preserves music but caps you at 720p over Bluetooth and requires the phone to stay active. That's a real tradeoff.

The underlying ask is simple: **don't reset the A2DP session when onboard recording starts.** Or expose enough audio session control in the SDK that developers can manage this themselves.

Use cases this unlocks immediately:

- Hands-free lab work / protocol recording with background audio cues

- Fitness and sports recording where music is part of the activity

- Content creators who want ambient audio or a backing track in their POV footage workflow

- Any scenario where the glasses are doing two jobs at once — capturing and playing

This feels like a firmware change rather than an SDK change, which means it could ship without a new toolkit release. Has anyone found a workaround? And has Meta commented anywhere on whether audio session isolation is on the roadmap?

Tagging this as a feature request but genuinely curious if others are hitting this wall.