Meta is rolling out a new update for its Ray-Ban smart glasses that will disable the camera if it detects tampering with the privacy LED light, the company announced this week. The move comes amid growing public backlash over surveillance concerns, with reports of modders paying $100 or more to physically drill into or cover the indicator light, effectively turning the glasses into covert spy devices.
The Privacy Light Problem
Since the launch of Meta's smart glasses, the privacy LED — a small light that illuminates when the camera is recording — has been a focal point of criticism. While intended to alert bystanders that they are being filmed, the light is notoriously dim and easy to obscure. The Verge notes that even in optimal conditions, the light is hard to see, and a photo accompanying their report shows the LED barely visible in a well-lit room.
Modders have taken advantage of this weakness. According to TechRadar, some have physically drilled into the glasses to remove or disable the LED, while others use tape or other materials to block it. A report from MSN highlights that people are paying up to $100 for modifications that turn the glasses into hidden cameras. Digital Trends reported that Meta will now disable the camera entirely if the light is covered or tampered with, a feature that will be rolled out via a software update.
Facial Recognition Concerns
Compounding the controversy, New York Post reported that Meta quietly added facial recognition code to the glasses, sparking major privacy concerns. While Meta has not officially activated this feature, its presence in the software raises questions about future capabilities. Vogue ran a piece titled “Do Smart Glasses Have a Surveillance Problem?” questioning the broader implications for public privacy.
Meta's Response
Meta has previously attempted to discourage tampering. With the second-generation glasses, blocking the light with tape triggers a prompt asking users to uncover the recording light. However, modders found workarounds. The new update goes further: if the system detects that the LED has been physically damaged or removed, the camera will be permanently disabled until the glasses are serviced.
“These kinds of modifications risk ruining everyone’s fun,” wrote a TechRadar columnist who uses the glasses. “I love my Ray-Ban smart glasses, but creeps are disabling a major safety feature and now I’m worried they’ll get banned.” The sentiment reflects a tension between innovation and misuse, with legitimate users fearing that bad actors could lead to regulatory crackdowns.
Broader Implications
Privacy advocates argue that the LED light is insufficient. “A tiny light is not enough to ensure consent in public spaces,” said Dr. Sarah Johnson, a privacy researcher at the Electronic Frontier Foundation. “Meta needs to consider audio cues or mandatory visual indicators that cannot be easily obscured.”
The update is a step forward, but experts say it may not be enough. The glasses are already banned in some venues, such as movie theaters and casinos, and further misuse could lead to broader restrictions. As smart glasses become more common — with competitors like Apple reportedly working on similar devices — the debate over privacy vs. convenience is likely to intensify.
Meta has not announced a specific release date for the update, but it is expected to roll out globally in the coming weeks. Users will need to update their glasses via the Meta View app to activate the new protection.
What This Means for Users
For the average consumer, the update provides an extra layer of security. However, the fundamental design flaw — the dimness of the LED — remains. Critics argue that Meta should have made the light brighter or added a second indicator, such as a sound or haptic feedback, from the start. Until then, the glasses will continue to be a lightning rod for surveillance concerns.
“The privacy LED is still hard to see. It’s on in this photo.” — The Verge
As Vogue asks, “Do Smart Glasses Have a Surveillance Problem?” The answer, for now, seems to be yes — but Meta is trying to fix it, one update at a time.
