Confirm Ray‑Ban Meta accidental wake patch in 10 minutes

Time needed about 20 minutes

The steps

1. Show device info in the companion appOpen the Ray‑Ban Meta companion app, go to the paired device entry or About page, and display the firmware and app build strings on-screen.You should see: The screen shows a firmware build string and the app version visible in a screenshot or screen recording.
2. Start screen recording of the appBegin a screen recording of the companion app showing the firmware and leave it running while you perform tests.You should see: The screen recording file begins with the app page showing firmware and app build text.
3. Set up external camera on the glassesPosition a second phone or camera aimed at the glasses so the temple LED and the glasses' sound are captured.You should see: External video shows the glasses' temple area clearly and records audio for chime detection.
4. Log timestamps for each attemptOpen a note app and write the exact clock time for each test attempt before you trigger it.You should see: A running text log lists times for each trigger you will match to video clips.
5. Run the wake-word testSay the configured wake word or phrase once and watch for LED, chime, or assistant UI.You should see: You either see the LED, hear a chime from the glasses, or see the assistant UI; record the outcome and time in your note.
6. Run the pocket or tabletop movement testPlace the glasses in a pocket or face-down on a table and perform the single movement reported by others (pull them out or bump the table once).You should see: The external video captures any LED or chime and you log the time and result.
7. Perform a touch or gesture testGive the single tap, press, or frame gesture you configure to wake the assistant once.You should see: A clear assistant indicator (LED/chime/UI) appears on video if the touch triggered a wake; log the time and gesture.
8. Trigger phone notifications and callsHave someone send a message or call while you wear the glasses, or trigger a notification from a second device you control.You should see: If the assistant wakes, the external video shows the LED/chime/UI and your note records the timestamp; if not, note 'no wake' at the time.
9. Test Bluetooth audio eventsStart and stop media playback or connect/disconnect Bluetooth audio from your phone while wearing the glasses and observe whether the assistant activates.You should see: You can see or hear any assistant wake on the recordings and log the event time and outcome.
10. Restart and repeat any failing testIf a test reproduces a wake, restart the glasses and phone, re-run that single failing test to confirm, then save the matching clips and the screen recording for the report.You should see: You have at least one short video clip showing the failing trigger with a timestamp and a separate screen recording or screenshot showing the firmware and app build.

Test Ray‑Ban Meta accidental wake patch

Confirm the patch by showing the glasses' firmware and the companion app build, enabling the assistant, running a short set of controlled triggers, and recording the exact wake indicators with timestamps. If any trigger wakes the assistant, save the clip and escalate to support with the build strings.

Check firmware and companion app build numbers

Open the Ray‑Ban Meta companion app, find the paired device entry or About page, and note the firmware and app build strings. Take a screenshot or start a screen recording so you can attach the exact text to your report; support needs those strings to map your report to a fixed build.

• Where to look: device page, About, or Settings in the companion app.
• What to record: screenshot or screen recording showing firmware and app build strings.

Run five repeatable test scenarios

Run these triggers in a quiet room, one at a time, and timestamp each attempt: wake word, pocket or tabletop movement, touch or frame gesture, phone notification or incoming call, and Bluetooth audio events. Note the clock time for every attempt so you can match it to video evidence.

• Do one attempt per trigger and wait 10 seconds between tries to avoid overlap.
• Use the exact wake word or gesture configured in the app.

What counts as a wake

Score a test as a true wake only when you see an explicit indicator: the glasses' LED, an audible chime from the glasses, assistant UI on the lenses, or a microphone-on icon in the companion app. Exclude phone vibrations, incidental movement, or ambiguous sounds.

• LED light visible on the temple in a video.
• Distinct chime coming from the glasses, not the phone.
• Assistant UI or prompt visible on the lenses or in-app.
• Microphone or listening icon in the app or device status.

Capture proof: what to record and how

Start a screen recording of the companion app showing the firmware, then make a short external video aimed at the glasses so LED and chime are visible. Keep clips 10–30 seconds long and include a timestamped note for each attempt so support can match clips to build strings quickly.

• Begin with the app screen showing firmware, then cut to the trigger and the indicator.
• If you cannot show the app, record the LED and chime with a visible clock on-screen.
• Log each attempt time in a short text note to map to clips.

Quick troubleshooting before filing a ticket

If a trigger reproduces a wake, restart the glasses and phone, update firmware and the app, toggle the assistant off and on, and re-pair. Re-run the failing test after each step to see if the issue cleared before you prepare your report.

• Restart: power the glasses fully off, wait 10 seconds, then power on.
• Update: install available firmware and app updates and re-check the build strings.
• Toggle assistant: disable then re-enable the assistant in-app.
• Re-pair: forget the device and pair it again only if other steps fail.

Compose a clear support report

A useful report includes the device model, app platform, firmware and app build strings, exact test steps with timestamps, one or two short video clips, and which troubleshooting steps you tried. That gives support what they need to reproduce the bug and decide next action.

• List each attempt as: time, trigger, outcome (LED/chime/UI) and attach the matching clip name.
• State the troubleshooting you tried and whether the issue still occurs in daily use.

How reports commonly fail

Support often rejects tickets that lack build strings, short timestamped clips, or clear steps. Long noisy videos and vague reports mean vendors cannot match an event to a build, so the ticket stalls. Provide compact, time-stamped proof and exact build text.

• Testing in noisy conditions or sending long clips without an app screen prevents triage.
• Vendors need reproducible steps and timestamps to verify a patch.

Decide next steps after testing

If tests never reproduce the wake, wear the glasses for a day and repeat the documented test if a wake appears. If wakes reproduce reliably after troubleshooting, file a support report with clips and builds and follow the seller's return or replacement policy if support cannot resolve it.

• Accept as fixed: no reproductions during controlled tests and normal use for a day.
• Escalate: reproducible wakes with video and builds go to support.

Further reading and tools

For a shorter checklist, use our 10‑minute test guide and consult the device page and app directory for related apps. Those pages help you identify interfering apps and link to device-specific notes you may need for the report.

• Ray‑Ban Meta device page: /devices/ray-ban-meta.
• Short test recipe: /articles/10-minute-smart-glasses-test.
• App directory: /apps.

Where this usually goes wrong

• App shows no firmware or version informationOlder app build, different menu location, or pairing state hiding device infoUpdate the companion app, reconnect the glasses, and screenshot whatever version text the app shows; include app version and OS in your report if firmware remains hidden.
• Wake appears only when phone notifications arriveNotification routing or phone-side assistant forwarding events to the glassesSilence notifications and re-run tests; if silencing prevents wakes, include phone OS, notification type and a test clip in your report and check phone assistant settings.
• LED blinks but no chime or assistant UIPartial indicator or inconsistent firmware status lightsRecord the LED and the app simultaneously and describe the LED behaviour precisely in your ticket; vendors treat partial indicators differently from full wakes.
• Update fails or device disconnects during firmware installIntermittent Bluetooth or low battery during updateCharge both devices, ensure stable Bluetooth range, restart both devices and retry the update; if it still fails, record the sequence and include it in the support ticket.

The checklist

• Show device info in the companion app
• Start screen recording of the app
• Set up external camera on the glasses
• Log timestamps for each attempt
• Run the wake-word test
• Run the pocket or tabletop movement test
• Perform a touch or gesture test
• Trigger phone notifications and calls
• Test Bluetooth audio events
• Restart and repeat any failing test

Frequently asked questions