Meta CTO explains why the smart glasses demos failed at Meta Connect — and it wasn’t the Wi-Fi

Spread the love

Meta Chief Technology Officer Andrew Basworth took to explain more technical details on her Instagram, why the company’s developer conference this week has failed multiple demos of Meta’s new smart-glass technology in Meta Connect.

Meta launched on Wednesday Its existing Re-Ban Meter with an upgrade version of three new pairs of smart glasses, a new Meta Ray-Ban display It brings a vest controller and sports-centric Okale Meta VanguardThe

However, at different points during the event, live technology demos failed to work.

In one, the cooking creator Jack Mankuso asked his Ray-Ban Meta glasses how to start with a specific sauce recipe. After repeating the question, “What do I do first?” Without a response, the AI ​​moves on the recipe, forcing him to turn off the demo. He then returned it to Meta CEO Mark Zuckerberg and said that he thought Wi-Fi could become a riot.

Jack Mancuso on Meta Connect.Figure Credit:Meet

In another democut, glasses failed to take a live WhatsApp video call between Bosworth and Zuckerberg; Zuckerberg had to give up in the end. Basworth walked on the stage, joking about the “ruthless” Wi-Fi.

“You practice these things a hundred times and then you never know what will happen,” Zuckerberg said at the time.

After the event, Basworth went to him Instagram For the Q&A sessions about the new technology and live demo failure.

TechCrunch event

San Francisco
|
October 27-29, 2025

Later, he explained that it was not really Wi-Fi, which caused the chef’s glasses to cause this problem. Instead, it was a mistake in the resource management plan.

Figure Credit:Instagram (screenshot)

“When the chef said,” Hey, Meta, Live AI, ‘It started every Ray-Ban Mater Live AI of the building. And there were lots of people in that building, “Basworth explained. “Obviously this didn’t happen to the rehearsal; we had nothing to do,” he said that the glasses were triggered by the number of the glasses.

Although alone was not enough to create obstacles. The second part of the failure had to do with how the live AI traffic was chosen to route to its development server to disconnect it during the demo. However, when it did, it did it for everyone in the building on access points, including all the headsets.

Basworth added, “So we originally dodos ourselves with that demo.” (A DDS attack, or disbelieve in service attacks, is a where the traffic floods printed on a server or service, slows it or make it unavailable.

On the other hand, the issue with a failed WhatsApp call was the result of a new bug.

The call of the smart glasses went to sleep at the moment of the call, Basworth said. When Zuckerberg woke up the display, it did not show him the answer notification. CTO said that it was a “race condition” bug, or where the results were simultaneously trying to use the same resource depending on the unexpected and accumulated period of two or more different processes.

Basworth mentioned, “We never ran to that bug before.” “This is the first time we’ve ever seen it it is right now, and it is a horrible, terrible place to show that bug” “He emphasized that, of course, the company knows how to handle the video calls and the company was” bombad “about the bug.

Despite the issues, Basworth said he was not concerned about the outcome of these problems.

“Obviously, I don’t like it, but I know the product works i

Leave a Reply

Your email address will not be published. Required fields are marked *