Meta Closes Smart Glasses Recording Loophole After LED Bypass

Cover the little white light on a pair of Ray-Ban Meta glasses mid-recording, and until this week, the camera kept rolling anyway. Meta has now shipped a fix that shuts the camera off the moment that light gets blocked — closing a loophole that turned a supposed safety feature into something closer to theater.

The problem was timing, not the light itself

Meta's smart glasses have always had a rule: if you cover the capture LED before you start filming, the camera refuses to record. That part worked fine. The gap was what happened after. Start a recording first, then slide a finger or a strip of tape over the light, and the glasses kept capturing video with no visible signal to anyone standing nearby. The one thing the LED exists for — letting bystanders know they're on camera — simply stopped working the moment someone wanted it to.

It's the second time this summer Meta has had to patch this exact category of problem. An earlier update dealt with people physically drilling the LED out of the frame. This one deals with people just putting a finger over it.

What actually changed

Alex Himel, who runs Meta's wearables division, announced the update in a Threads post on August 27. He was fairly candid about why it took a second pass:

"The camera won't start recording if the LED is blocked, but some people try to bypass this by starting a recording and then covering it up. A fix for this is starting to roll out – the camera will now stop working if the light is covered during a recording."

The rollout covers the full lineup: Ray-Ban Meta, Oakley Meta, and the newer Meta AI glasses. Practically, that means:

• Recording stops automatically the instant the LED is physically obstructed, whether by a finger, tape, or anything else.
• The restriction applies mid-recording now, not just at the start — closing the exact gap people had been exploiting.
• It builds on the earlier fix that blocked recording when the LED had been physically removed or damaged.

Himel framed the workaround as a fringe behavior, not a mainstream one: "Only a tiny minority of people try to get around these protections, and the fact they have to go to these lengths shows our efforts are working." He added that more updates are coming to keep the capture light "reliably" alerting bystanders.

Regulators think the light was never the real fix

That framing is where things get more interesting, because European regulators have spent the summer arguing the LED was never the actual problem. France's CNIL warned in May that camera-equipped smart glasses risk creating surveillance that is "almost invisible and omnipresent," and its underlying complaint isn't about hardware indicators at all — it's that bystanders caught on camera have no practical way to consent to being filmed in the first place. A blinking light doesn't fix that; it just tells you filming is happening, not that anyone asked permission.

The European Data Protection Board, which coordinates privacy regulators across the EU, has a report on smart glasses expected by the end of the summer, after which it says it will weigh further action. In other words, Meta closing this particular loophole addresses a real, concrete bug — but it's arriving into a regulatory conversation that's already moved past "is the light visible enough" and onto "should filming strangers without consent be this easy at all."

Why this keeps happening

Software-only recording indicators are inherently a game of whack-a-mole. Any signal generated by the device itself can, in theory, be suppressed by the person wearing the device — that's just the nature of putting the control and the notification on the same object. Meta's two fixes this summer (blocking removed LEDs, then blocking covered ones) both patch specific exploits rather than the structural issue underneath them.

For now, the update rolling out this week narrows the gap noticeably for anyone who isn't deliberately trying to circumvent it. Whether that satisfies regulators who've already flagged consent, not visibility, as the real gap is a separate question — and one Meta probably won't be able to patch its way out of with firmware alone.