Verify smart glasses firmware fixes with a checklist

Time needed about 30–90 minutes, plus 24–72 hours passive monitoring

The steps

1. Open the companion app and go to device detailsOpen the companion app and navigate to the device or settings screen that lists firmware, build or update history.You should see: You see a firmware or system version string and a last‑updated or last‑synced timestamp on the device card or in an About section.
2. Capture the glasses’ on‑device About screenOn the glasses, open Settings or About and display the firmware or build string; use your phone to take a clear photo or screen recording of that screen.You should see: A photo or video showing the device's firmware string and any visible timestamp.
3. Run the camera capture testOpen the glasses’ camera or capture app, take one high‑resolution photo and record a 10–20 second video of a high‑contrast scene.You should see: Photo and video files appear in the companion app or on your phone with correct timestamps and the image matches the scene.
4. Run the passthrough or live view testEnable passthrough or live view, point at a patterned object or digital clock, and record a 15–30 second phone video of what the wearer sees.You should see: The phone video shows continuous passthrough without freezes, black frames or persistent artefacts for the test duration.
5. Test audio input and outputRecord a 30‑second voice memo using the glasses' mic, then play an audio file from the glasses and note playback quality.You should see: The voice memo file is saved and plays back with clear audio; playback from the glasses is audible and free of distortion.
6. Run a tracking sweepUse an app or UI element that shows a reticle or pointer, then perform a smooth left‑to‑right head/eye movement while recording the display or taking notes on jumps or lag.You should see: The reticle follows movement smoothly with no sudden jumps or multi‑second drift during a 30‑second sweep.
7. Check connectivity and pairing resilienceTurn off Bluetooth or Wi‑Fi on the phone briefly, then turn it back on and observe reconnection in the companion app; re‑pair if reconnection fails.You should see: Connection is re‑established in the companion app within one minute and apps resume normally.
8. Run a short battery and thermal stress testCharge to at least 80%, then record a continuous 5–10 minute video capture while noting temperature and battery percent before and after.You should see: No spontaneous reboot, no dramatic battery percentage drop, and no severe performance throttling during the run.
9. Collect and name your evidence filesSave screenshots, phone videos and any exported diagnostics using a consistent filename pattern that includes device serial, firmware, test name and timestamp.You should see: A set of files with clear filenames and timestamps ready to attach to a support ticket or forum post.
10. Compose a concise support reportWrite a one‑line summary, then a bulleted block with Firmware, App, Serial, Time installed and numbered reproduction steps; attach your evidence files.You should see: Support or community responders can reproduce the issue from your steps or see the attached evidence and ask targeted follow‑ups.
11. Submit the ticket or update public threadSubmit the support ticket or post the update to a public thread, attaching the evidence and the short text file listing filenames and time windows.You should see: Your upload includes dated screenshots, recordings and any diagnostics so support can triage without requesting basic items.

Verify smart glasses firmware fix

Check the device and app show the updated firmware and a recent install time, then run a compact test sequence (camera, passthrough, audio, tracking, connectivity, battery) and collect dated evidence you can attach to support. Do version checks first, tests next, then save screenshots and recordings before changing device state.

Confirm the update installed on the device and app

Open the companion app and the glasses’ About or Device Info screen. Locate the firmware or build string and any install or synced timestamp in both places. Only proceed to functional tests after both the app and the glasses report a newer version or matching recent timestamps; otherwise capture screenshots as evidence.

• If the app shows a firmware string: copy it or screenshot it.
• If the glasses show only a build number: photograph or record that screen.
• Note timezone with any 'last updated' or 'synced' timestamps.

Run a prioritised test suite to prove behaviour changed

Start with the behaviour the vendor claimed to fix. Run camera capture and passthrough first, then audio, tracking, connectivity and a short battery/thermal run. Each test has one clear pass/fail observable you can record. Order tests to avoid obscuring failures with later reboots or re‑pairs.

• Camera capture: take a photo and a 10–20 second video; expected files appear with correct timestamps and the view matches the scene.
• Passthrough: record 15 seconds looking at a patterned object; expected smooth continuous passthrough with no freezes or persistent artefacts.
• Audio: record a 30‑second voice memo and play audio; expected clear recording and audible playback without distortion.
• Tracking: perform a 30‑second left‑to‑right sweep; expected pointer or reticle follows smoothly with no multi‑second drift.
• Connectivity: disconnect and reconnect Bluetooth/Wi‑Fi; expected reconnection in the app within one minute.
• Battery/thermal: 5–10 minute video capture at 80%+ charge; expected no spontaneous reboot and no unusually large battery drop.

Collect exportable evidence without developer tools

Use screenshots, companion app screen recordings, exported diagnostics and phone video of the glasses’ view. Save files with consistent filenames and visible timestamps. If the app offers a diagnostics export, save it and attach it to your report before you change the device state.

• Always screenshot the companion app showing firmware and the install timestamp.
• For camera issues: attach a still photo and a 10–20 second video recorded through the glasses or of the glasses' output.
• For intermittent bugs: show a visible clock or phone status bar in recordings so log timestamps are unambiguous.
• If no export option exists: screenshot the diagnostics screen or film it while reproducing the fault.

Filename templates and a phone‑video method

Use a consistent naming scheme so support sorts files quickly. Show the time on a clock or lock screen during recording; start recording, reproduce the bug, stop recording. The visible time proves when you ran the test and helps correlate vendor logs.

• Filename pattern: serial_firmware_testname_YYYYMMDD_HHMM.ext
• Include a short text file listing reproduction steps and start/stop times for each test.

Decide whether the issue is fixed or still flaky

Set acceptance criteria before testing: how many consecutive successes or how long you will monitor. Require consecutive successful reproductions for an immediate pass and 24–72 hours of normal use to catch long‑run faults. For intermittent issues, record trials and report a simple failure rate.

• Immediate: three consecutive clean reproductions of the bug scenario is a reasonable acceptance test.
• Flaky: log attempts and compute failures/attempts; share that rate with support.
• Monitor: watch behaviour during routine use for 24–72 hours to catch thermal or long‑run issues.

What to include in a support ticket or forum post

Start with a one‑line summary, then a bulleted block with Firmware, App, Serial, Time installed and a numbered reproduction sequence. Attach screenshots, phone videos and any exported diagnostics. Put the most important facts at the top so responders can reproduce the issue or inspect the evidence immediately.

• Include exact firmware strings copied from device and app, companion app version, and timestamps.
• Provide a 3‑step reproduction sequence and attach the media files referenced.
• List filenames and the time window each file covers in a short text file.

Why checks fail and how to avoid common mistakes

The usual failure is assuming an OTA message equals a completed migration. Owners run one quick test, then declare the bug fixed while the update either staged but didn’t commit or the issue needs long‑run testing to appear. Avoid this by capturing firmware strings, running targeted tests first, and exporting diagnostics before any reset or re‑pair.

• If you skip the device firmware screenshot, support will ask for it and reopen the case.
• Export diagnostics before state‑destroying actions like factory reset.
• Structured, repeatable attempts are required for intermittent issues; random checks do not prove anything.

Privacy, warranty and when to escalate

Do not post raw footage of other people without their consent; blur or crop faces for public posts. Do not use unsupported hacks or unofficial firmware; those actions can void warranty and complicate support. Escalate to repair if hardware fails checks or the vendor diagnostics indicate out‑of‑warranty hardware.

• Red flag for repair: repeated reboots under normal use or rapid battery drop to zero minutes.
• Red flag for warranty void: installing unofficial firmware or circumventing the companion app update flow.
• Redact full serials in public posts but be ready to provide them to official support privately.

Next step you can take tomorrow

Run the checklist: capture the firmware string and an app screenshot, then run the camera test and save a short video. If tests pass, update any public thread. If anything fails, file a ticket with the template above and attach your evidence.

• If you use Ray‑Ban Meta, see our device page for model‑specific companion app notes: /devices/ray-ban-meta
• Compare companion apps that expose diagnostics in /apps when you need to export logs.

Where this usually goes wrong

• Companion app shows update complete but device still reports old firmwareThe update staged on the device or the final migration step and sync did not complete.Reboot the glasses, force a sync in the app if possible, capture screenshots before and after, and report both with timestamps to support.
• Camera files appear but show corrupted frames or intermittent artefactsA codec or timing regression in the new firmware or thermal/throttling issues affecting the camera pipeline.Run a continuous camera stress capture for 5–10 minutes, record a phone video of the artefacts, and attach both the raw files and the phone video to support.
• Audio records locally fine but remote calls show poor audioA different audio stack is used for calls and the firmware change affected that pathway.Reproduce the issue on a call with consent, record the call, and include both local recordings and the call capture when reporting.
• Issue disappears after re‑pairing or factory resetA stateful migration step did not apply during the OTA or corrupted settings persisted.Export diagnostics before performing state‑destroying actions; perform reset only after exporting and attach those diagnostics to the ticket.

The checklist

• Open the companion app and go to device details
• Capture the glasses’ on‑device About screen
• Run the camera capture test
• Run the passthrough or live view test
• Test audio input and output
• Run a tracking sweep
• Check connectivity and pairing resilience
• Run a short battery and thermal stress test
• Collect and name your evidence files
• Compose a concise support report
• Submit the ticket or update public thread

Frequently asked questions