When I first started using Ray-Ban Meta smart glasses, they transformed my daily life. As someone with a quadriplegic disability, the ability to access messages, make calls, and interact with the world using just my voice was liberating. For 12 months, the experience was rock solid. Then, in October 2024, it broke.
The bug: voice assistant fails after phone or WhatsApp calls
Since Meta firmware version 10.0, a critical bug has rendered the “Hey Meta” voice assistant and message readout features unresponsive after any phone or WhatsApp call. The only way to restore functionality? Physically remove and refold the glasses — something I cannot do independently. This is not a minor inconvenience. It’s a complete loss of access for disabled users like me.It’s more than a glitch — it’s an accessibility regression
This bug affects not just convenience but basic autonomy. A tool that once enabled me to live more freely has now become a daily frustration. I’ve tested this across three separate pairs of Ray-Ban Meta smart glasses. The issue has persisted through firmware versions 10.0, 11.0, 12.0, 13.0 and now 14.1. It continues despite all updates to the iPhone, iOS, and Meta View app.
A suspected Bluetooth handoff failure
From my experience and testing, I believe this is a Bluetooth session handling issue. After a call ends, the system seems to leave the audio channel in a semi-active state, as if the call is still ongoing. This prevents the assistant from reactivating — and in this half-awake state drains the battery on the glasses very quickly.
Apple is investigating. Meta is not
I’ve reported this issue to Meta repeatedly via the View app. There has been no response. No follow-up. No acknowledgement. In contrast, Apple has taken the problem seriously. They’ve gathered diagnostic logs from my iPhone and are actively investigating whether iOS audio routing or Bluetooth management on my iPhone could be contributing.
This contrast is telling. The hardware maker is silent. The iOS platform owner is trying to help.
This matters — especially for disabled users
This isn’t just a bug. It’s a serious accessibility failure. It’s a reminder that for disabled users, reliability isn’t optional — it’s everything. When voice fails, independence fails. And when a company like Meta doesn’t respond to repeated accessibility reports, it sends a message that disabled users aren’t being prioritised.
What needs to happen next
Meta must acknowledge and address this bug as an urgent accessibility issue. They must test scenarios involving disabled users and voice-only access. And they must provide a way to restore functionality without requiring physical interaction.
Until then, the Ray-Ban Meta smart glasses remain broken — not just technically, but in their promise to deliver true hands-free freedom through technology.
